Accounting engagement budgets, WIP and realization tables, 13 firms
Summary
Engagement-level tables exported from the practice management systems of 13 US accounting firms: budgeted and actual hours by role level, fee basis, WIP age, write-downs with their stated reasons and final realization. One row per engagement per year, with a weekly WIP snapshot table alongside. Hours are rolled up by role level and never by person, and client names, fee amounts and all return or ledger details are left out.
Collected to order. We collect it from US companies for your order. Scope, volume and timing are confirmed in writing before you sign.
Pricing on request
Request scope and pricingAt a glance
- Planned scope. Volume, sources and timing are confirmed in writing before you sign.
- Records
- 142Kengagement-year rows
- Size
- 420 MB
- Tokens, estimated
- 70M
- Years
- 2017 to 2026
- Firms
- 13
- Owner profile
- 13 US accounting firms, 15 to 90 staff each, Midwest, Northeast and West Coast
- Industry
- Accounting and finance
- Data type
- Finance and accounting operations
- Headcount
- 15 to 90 staff per firm
- Region
- United States (Midwest, Northeast, West Coast)
- Languages
- English
- Formats
- Parquet
- Updated
Sources
| System | Kind | Records |
|---|---|---|
| CCH Axcess Practice | Accounting and ERP | 88.2K engagement-years |
| Practice CS | Accounting and ERP | 40.9K engagement-years |
| Karbon | Projects and wiki | 12.7K engagement-years |
Good for
- forecasting engagement overruns and write-downs from early-season signals
- training agents to build engagement budgets by service line and role level
- evaluating tabular reasoning over budget against actual hours
- benchmarking anomaly detection on WIP aging and billing delays
Fields
| Field | Type | Description |
|---|---|---|
| engagement_id | string | Stable engagement-year id |
| firm_code | string | Code of the contributing firm |
| client_ref | string | Client code, stable across years |
| service_line | enum | audit, review, compilation, tax_compliance, advisory or outsourced_accounting |
| fiscal_year | int | Client fiscal year the engagement covers |
| fee_basis | enum | fixed, hourly or retainer |
| budget_hours | object | Budgeted hours by role level: partner, manager, senior, staff |
| actual_hours | object | Actual hours by role level |
| wip_age_days | int | Average days from time entry to billing |
| realization_pct | float | Billed value as a percent of standard value |
| write_down_reason | string | Reason recorded at billing, normalized text |
Example record
{
"engagement_id": "CF03-ENG-2024-01182",
"firm_code": "CF-03",
"client_ref": "[ACCOUNT_207]",
"service_line": "review",
"fiscal_year": 2024,
"fee_basis": "fixed",
"budget_hours": {
"partner": 6,
"manager": 18,
"senior": 42,
"staff": 60
},
"actual_hours": {
"partner": 9,
"manager": 31,
"senior": 58,
"staff": 71
},
"wip_age_days": 47,
"realization_pct": 81.4,
"write_down_reason": "Analytical procedures redone after the client restated Q4 inventory, extra manager review time not billed"
}Licenses available
Non-exclusive
Licensed to more than one buyer.
First look
One buyer gets 2 to 4 weeks to make an offer before anyone else sees the dataset.
What ships with it
- Datasheet: what it is, what it is good for, verified size, sources, years, format and limits.
- Provenance file: the owner shown by code, staff notice and consent status, exclusions, mapped to the EU AI Act Article 53 training-data summary and California AB 2013.
- Manifest with a hash for every file.
- QC report and de-identification report.
- Your own copy, with unique canary records.
How it is de-identified
Default exclusions removed, files flattened to text, identifiers found in three layers and replaced with consistent placeholders, and the result measured against a 99% bar for each identifier type in each source.