Tax Provision True-Up Documentation
The tax provision booked at year-end is an estimate, and once the actual tax return is filed, usually months later, the difference between what was estimated and what the actual return shows, the true-up, has to be identified, explained, and booked as an adjustment, and doing that comparison manually across every line of a complex return against the prior provision workpaper is slow and easy to get only partially right, especially distinguishing a true-up caused by a genuine estimate refinement from one caused by an actual error in the original provision that needs its own follow-up. An auditor reviewing the true-up doesn't just want the adjustment booked, they want to know why each material piece of it happened, and 'the return was different from the estimate' isn't an answer that holds up.
STARTING PRICE
From €299
Standard tier · Multi-step workflow with AI extraction/decisioning and 2-3 integrations.
Get a quote →Saves roughly 6-12 hrs per true-up cycle, plus a stronger auditor walkthrough with less iterative back-and-forth.
How the automation works
We compare the filed tax return against the original provision estimate line by line, identifying every material difference and, where possible, its specific cause, a return position that differed from the provision's initial estimate, updated information not available at provision time, an outright error in the original calculation. Each true-up component is documented individually with its cause, not booked as a single net adjustment with no explanation behind it, and any true-up item classified as caused by a genuine error in the original provision, distinct from a routine estimate refinement, is flagged specifically, since that distinction matters for evaluating whether the provision process itself needs a control improvement, not just booking the correction. Variance explanations distinguish between timing differences that reverse in a future period and permanent differences that won't, since conflating the two produces a true-up narrative that doesn't actually explain the underlying driver to a reviewer.
Process flow
- 01
Compare filed return to provision estimate ai
The filed tax return is compared line by line against the original provision estimate's workpapers to identify every material difference.
- 02
Determine cause of each difference ai
Each identified difference is analyzed for its likely cause, an estimate refinement, updated information, or an error in the original calculation.
- 03
Classify and flag genuine errors ai
True-up items caused by a genuine error in the original provision are flagged specifically, distinct from routine estimate refinement, for process review.
- 04
Document each component individually output
Every true-up component is documented individually with its cause, rather than booked as one net adjustment with no supporting explanation.
- 05
Prepare true-up entry for review output
The documented true-up adjustment, with its component-level explanation, routes to your tax team for review and posting.
Inputs
- Filed tax return
- Original provision estimate workpapers
- Updated information available since provision time
- Prior period true-up patterns for comparison
Outputs
- Line-by-line return-to-provision comparison
- Cause-documented true-up components
- Genuine-error flags distinct from estimate refinement
- Reviewer-ready true-up entry with full explanation
Works with
Prefer a fully custom build instead of an off-the-shelf integration? We scope both options during your free consultation — most jobs like this one work fine on standard connectors, but higher-volume or non-standard systems sometimes need bespoke API work, reflected in the complex tier.
Where this goes wrong if you get it wrong
- A true-up booked as a single net adjustment with no component-level explanation, the return was different from the estimate by this amount, gives an auditor nothing to evaluate and typically triggers a request to break it down anyway, documenting each component's cause up front avoids that back-and-forth.
- Treating every true-up as a routine estimate refinement, even when a piece of it is actually caused by a genuine calculation error in the original provision, misses the chance to identify and fix a process gap in how the provision itself was prepared, the classification between refinement and error matters beyond just booking the number correctly.
- A large true-up that recurs in a similar pattern year after year, without anyone asking why the estimate keeps missing in the same direction, suggests a systematic bias in the provision methodology, comparing the current true-up against prior periods' patterns can surface that kind of recurring issue that a single-year view would miss.
- This process documents and explains the true-up based on the comparison, it does not make the underlying tax technical determination on an ambiguous return position, a difference driven by a genuinely uncertain tax position still needs your tax team's judgment on how to characterize and disclose it.
Frequently asked questions
Does this book the true-up entry automatically?
It documents and prepares the true-up entry with full component-level explanation for your tax team's review and posting; the actual booking decision and entry remain your team's responsibility.
How does this distinguish a true-up caused by an error from a normal estimate refinement?
Each component of the difference is analyzed for its likely cause, and items attributable to a genuine calculation error in the original provision are flagged specifically, since that distinction is relevant for process review, not just for booking the adjustment.
Can this catch a recurring pattern in our true-ups across years?
Yes, current true-up components are compared against prior periods' patterns, surfacing a recurring bias or systematic estimate gap that a single-year comparison alone wouldn't reveal.
Does this replace our tax team's judgment on uncertain positions?
No, a difference driven by a genuinely uncertain tax position still requires your tax team's technical judgment on characterization and disclosure; this documents the comparison and explanation to support that review.