Skip to content

AUTOMATIC DATA PROCESSING, INC.: revenue

Revenue for AUTOMATIC DATA PROCESSING, INC. Inspect selected reporting periods, original units and SEC filing links; download the financial history.

All AUTOMATIC DATA PROCESSING, INC. financial histories

What this measure means

Revenue under this specific accounting concept. A missing value is not zero; filers can use other revenue concepts.

Exact concept: us-gaap:Revenues. 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-07-01 to 2026-06-30. The SEC response was captured on 2026-09-19.

Selected filing history

Revenue in original reported units, latest-filed observation per period
Period startPeriod endValueUnitFiledSource filing
2025-07-012026-06-3021,947,400,000USD2026-08-0510-K · 0000008670-26-000030
2024-07-012025-06-3020,560,900,000USD2026-08-0510-K · 0000008670-26-000030
2023-07-012024-06-3019,202,600,000USD2026-08-0510-K · 0000008670-26-000030
2022-07-012023-06-3018,012,200,000USD2025-08-0610-K · 0000008670-25-000037
2021-07-012022-06-3016,498,300,000USD2024-08-0710-K · 0000008670-24-000024
2020-07-012021-06-3015,005,400,000USD2023-08-0310-K · 0000008670-23-000030
2019-07-012020-06-3014,589,800,000USD2022-08-0310-K · 0000008670-22-000038
2018-07-012019-06-3014,110,200,000USD2021-08-0410-K · 0000008670-21-000027
2017-07-012018-06-3013,274,200,000USD2020-08-0510-K · 0000008670-20-000032
2016-07-012017-06-3012,372,000,000USD2019-08-0910-K · 0000008670-19-000021
2015-07-012016-06-3011,667,800,000USD2018-08-0310-K · 0000008670-18-000011
2014-07-012015-06-3010,938,500,000USD2017-08-0410-K · 0000008670-17-000010
2013-07-012014-06-3010,226,400,000USD2016-08-0510-K · 0000008670-16-000053
2012-07-012013-06-309,442,000,000USD2015-08-0710-K · 0000008670-15-000021
2011-07-012012-06-3010,595,400,000USD2014-08-0810-K · 0000008670-14-000015
2010-07-012011-06-309,833,000,000USD2013-08-1910-K · 0000008670-13-000015
2009-07-012010-06-308,927,700,000USD2012-08-2010-K · 0001206774-12-003634
2008-07-012009-06-308,838,400,000USD2011-08-2410-K · 0001206774-11-001935
2007-07-012008-06-308,733,700,000USD2010-08-2510-K · 0001206774-10-001881

Related financial histories

Inspect the source

Entity
AUTOMATIC DATA PROCESSING, INC. / CIK 0000008670
Captured
2026-09-19T14:43:41.606Z
SEC response SHA-256
84dcea82dead76b69090b0bd4b178bd386e3023ceda333ff26126d0eada25329

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