Skip to content

PFIZER INC: deferred income tax expense or benefit

Deferred income tax expense or benefit for PFIZER INC. Inspect selected reporting periods, original units and SEC filing links; download the financial history.

All PFIZER INC financial histories

What this measure means

The deferred portion of income tax expense or benefit, arising from timing differences. It is not tax paid in the period.

Exact concept: us-gaap:DeferredIncomeTaxExpenseBenefit. 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 2007-01-01 to 2025-12-31. The SEC response was captured on 2026-09-19.

Selected filing history

Deferred income tax expense or benefit in original reported units, latest-filed observation per period
Period startPeriod endValueUnitFiledSource filing
2025-01-012025-12-31-2,133,000,000USD2026-02-2610-K · 0000078003-26-000026
2024-01-012024-12-31-2,102,000,000USD2026-02-2610-K · 0000078003-26-000026
2023-01-012023-12-31-3,442,000,000USD2026-02-2610-K · 0000078003-26-000026
2022-01-012022-12-31-3,764,000,000USD2025-02-2710-K · 0000078003-25-000054
2021-01-012021-12-31-4,293,000,000USD2024-02-2210-K · 0000078003-24-000039
2020-01-012020-12-31-1,575,000,000USD2023-02-2310-K · 0000078003-23-000024
2019-01-012019-12-31561,000,000USD2022-02-2410-K · 0000078003-22-000027
2018-01-012018-12-31-2,204,000,000USD2021-02-2510-K · 0000078003-21-000038
2017-01-012017-12-31-2,410,000,000USD2020-02-2710-K · 0000078003-20-000014
2016-01-012016-12-31-700,000,000USD2019-02-2810-K · 0000078003-19-000015
2015-01-012015-12-31-20,000,000USD2018-02-2210-K · 0000078003-18-000027
2014-01-012014-12-31320,000,000USD2017-02-2310-K · 0000078003-17-000014
2013-01-012013-12-311,726,000,000USD2016-02-2910-K · 0000078003-16-000077
2012-01-012012-12-31786,000,000USD2015-02-2710-K · 0000078003-15-000014
2011-01-012011-12-31236,000,000USD2014-02-2810-K · 0000078003-14-000018
2010-01-012010-12-312,109,000,000USD2013-02-2810-K · 0000078003-13-000006
2009-01-012009-12-31-9,590,000,000USD2012-02-2810-K · 0001193125-12-085703
2008-01-012008-12-31-1,331,000,000USD2011-02-2810-K · 0001193125-11-048877
2007-01-012007-12-31-2,788,000,000USD2010-02-2610-K · 0001193125-10-042425

Related financial histories

Inspect the source

Entity
PFIZER INC / CIK 0000078003
Captured
2026-09-19T14:51:02.160Z
SEC response SHA-256
bd072131f9dcf001f22e843fded5910c2c7fc178e2a739ce0c58b1934e84d566

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/0000078003.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"])))