Skip to content

Exelixis Inc: income tax expense or benefit

Income tax expense or benefit for Exelixis Inc. Inspect selected reporting periods, original units and SEC filing links; download the financial history.

All Exelixis Inc financial histories

What this measure means

Current and deferred income tax expense or benefit for continuing operations. This accounting expense differs from cash taxes paid.

Exact concept: us-gaap:IncomeTaxExpenseBenefit. Each value covers an annual-duration reporting interval, shown with both start and end dates. Different units remain separate; no currency conversion or interpolation is applied.

Coverage of this history

Selected reporting periods run from 2009-01-01 to 2026-01-02. The SEC response was captured on 2026-09-20.

Selected filing history

Income tax expense or benefit in original reported units, latest-filed observation per period
Period startPeriod endValueUnitFiledSource filing
2025-01-042026-01-02158,636,000USD2026-02-1010-K · 0000939767-26-000021
2023-12-302025-01-03160,373,000USD2026-02-1010-K · 0000939767-26-000021
2022-12-312023-12-2949,756,000USD2026-02-1010-K · 0000939767-26-000021
2022-01-012022-12-3052,070,000USD2025-02-1110-K · 0000939767-25-000019
2021-01-022021-12-3163,091,000USD2024-02-0610-K · 0000939767-24-000028
2020-01-042021-01-0119,056,000USD2023-02-0710-K · 0000939767-23-000019
2018-12-292020-01-0377,097,000USD2022-02-1810-K · 0000939767-22-000026
2018-01-012018-12-28-237,978,000USD2021-02-1110-K · 0001628280-21-001852
2017-12-302018-12-28-237,978,000USD2020-02-2510-K · 0000939767-20-000035
2016-12-312017-12-294,350,000USD2020-02-2510-K · 0000939767-20-000035
2016-01-012016-12-310USD2017-02-2710-K · 0000939767-17-000019
2016-01-022016-12-300USD2019-02-2210-K · 0000939767-19-000042
2015-01-032016-01-0155,000USD2018-02-2610-K · 0000939767-18-000023
2015-01-012015-12-3155,000USD2017-02-2710-K · 0000939767-17-000019
2014-01-012014-12-31-182,000USD2017-02-2710-K · 0000939767-17-000019
2013-01-012013-12-31-96,000USD2016-02-2910-K · 0000939767-16-000149
2012-01-012012-12-31107,000USD2015-03-0210-K · 0000939767-15-000013
2011-01-012011-12-311,295,000USD2014-02-2010-K · 0000939767-14-000009
2010-01-012010-12-31-72,000USD2013-02-2110-K · 0000939767-13-000008
2009-01-012009-12-31-1,286,000USD2012-02-2210-K · 0001193125-12-072782

Related financial histories

Inspect the source

Entity
Exelixis Inc / CIK 0000939767
Captured
2026-09-20T05:09:57.607Z
SEC response SHA-256
b40a0786dfded352f7cc62e7f28a3bdc48963ef599330965662e3903bf485ed6

Current SEC company facts · Download the original response snapshot (gzip) · Download the selected JSON

Latest-filed annual-report facts per unit and reporting period at capture time. Duration facts cover 300 to 400 days. This selection can include restatements and is not a point-in-time backtest dataset. Missing concepts are omitted, never zero-filled. Values retain original units and are not currency converted. Extended concepts require compatible unit shapes and at least three reporting ends with changing values within one unit. Constant or incompatible added histories are omitted.

Public company accounting reference, not market prices, returns, an investment recommendation, or ALPHAC performance. Validate a separately constructed return series with the validation API; accounting values are not returns.

Use this in research

A financial period ends before its results become public. Use the filing date as a minimum availability boundary, inspect amendments, and retain the original filing vintage when testing historical signals. This latest-filed selection can contain information unavailable at the time.

These pages do not supply prices, total-return histories, corporate-action adjustments or a tradable universe. Build those inputs separately before evaluating a strategy. A profitable backtest can still reflect selection bias or costs that were left out.

Research methodology · Execution and cost assumptions · Check backtest overfitting

Build with the open-source tools

Use these accounting records as inspectable inputs. When you have constructed a return series, the validation tools can help test its statistical evidence and preserve the result with its limitations.

Read the published dataset with Python
import json
from urllib.request import urlopen

with urlopen("https://canlicapital.com/company-data/0000939767.json") as response:
    record = json.load(response)
print(record["fetched_at"])
print(record["policy"])
for concept in record["concepts"]:
    print(concept["tag"], next(iter(concept["observations"])))