Finance Index
How do auto-reversing accruals work, and how do I keep accruals accurate and audit-ready?
Reference guide to accrual reversal accuracy audit, including ERP workflow, integration points, data sync, controls, and finance-system tradeoffs.
An auto-reversing accrual books the estimated expense in the closing period and automatically posts the opposite entry on day 1 of the next period. When the actual invoice posts, it nets against the reversal - the expense lands once, in the right period. The mechanism is simple; the discipline is in measuring estimate-vs-actual and cleaning up the misses.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Auto-reversing accruals | An auto-reversing accrual books the estimated expense in the closing period and automatically posts the opposite entry on day 1 of the next period. | Keeps evidence clear and reduces control risk. |
| Measurement | Run a monthly true-up: for each accrued item, compare the accrual to the actual invoice that arrived, compute variance by category, and feed the misses back into next month's method. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| ERP alignment | Every major ERP supports a reversal flag or reversal-date field on the journal entry that schedules the opposite posting for the next period automatically. | Keeps vendor records and payment decisions reliable. |
| Cleanup entry | Reclass the invoice (or the reversal) so both sides hit the same account, then fix the cause: the accrual coding should come from the PO or in-flight invoice coding, not the preparer's guess. | Keeps accounting records aligned with the ERP. |
| True-up | Take last month's accrual schedule, match each line to the actual invoice received, compute over/under by line and category, and book a catch-up for systematic bias. | Reduces payment errors, timing issues, and reconciliation cleanup. |
How do I measure and improve accrual accuracy?
Run a monthly true-up: for each accrued item, compare the accrual to the actual invoice that arrived, compute variance by category, and feed the misses back into next month's method. Big variances cluster in judgment accruals (services, unbilled work) - shifting those to receipt-backed or invoice-in-flight bases is the structural fix.
How do I set up auto-reversing journal entries for AP accruals?
Every major ERP supports a reversal flag or reversal-date field on the journal entry that schedules the opposite posting for the next period automatically. Make the flag mandatory in your accrual template - manual reversals are how stale accruals are born.
My accrual reversed but the actual invoice posted to a different account - how do I clean up the hanging debit?
Reclass the invoice (or the reversal) so both sides hit the same account, then fix the cause: the accrual coding should come from the PO or in-flight invoice coding, not the preparer's guess. Recurring mismatches mean the accrual schedule and AP coding rules disagree - align them once.
How do I do an accrual true-up / lookback analysis?
Take last month's accrual schedule, match each line to the actual invoice received, compute over/under by line and category, and book a catch-up for systematic bias. Quarterly lookbacks satisfy auditors; monthly ones actually improve the estimates.
We double-counted an expense - accrued IT and posted the invoice in the same period. How do controls prevent accrual double-counting?
The accrual schedule must be cut after the final posting sweep and must exclude anything posted by cutoff - sequence, not vigilance, is the control. Auto-reversal also caps the damage at one period. Systems with real-time posted-status visibility make the exclusion check a filter rather than a memory test.
Auditors are challenging our accrual methodology - what documentation do they expect?
A written methodology (basis per category, thresholds, data sources), the populated schedule with source references for each line, evidence of review/sign-off, and lookback results showing estimates track actuals. Auditors challenge undocumented judgment, not documented method.
What audit assertions does the AP accrual address?
Primarily completeness (all incurred liabilities recorded) and cutoff (in the right period), with valuation a close third (estimated at the right amount). The search for unrecorded liabilities is the auditor's mirror-image test of the same assertions.
Accrual reversal didn't happen because someone forgot to flag the JE - how do I catch stale accruals sitting in the GL?
Reconcile the accrued-liabilities account monthly with an aging of items by origination month; anything older than 60-90 days gets investigated. A standing rule - every accrual JE uses the auto-reverse template, no exceptions - prevents the problem; the reconciliation catches the leaks.
How do I review the accrued liabilities account for old balances that never cleared?
Build an item-level rollforward: opening balance, additions, reversals, closing, by accrual line. Investigate residuals - usually reversals posted to a different account, duplicate accruals, or estimates for invoices that never came (release those to income with documentation).
Should accruals be recorded at the entity level or top level in a multi-entity org - and who owns them?
At the entity level, where the expense and the audit live; top-level accruals create consolidation noise and orphaned balances. Entity controllers own their schedules against a shared methodology; the group controller reviews variance patterns across entities.
What is acceptable accrual accuracy - is there a benchmark for estimate vs actual variance?
Well-run teams hold aggregate accrual variance inside 5-10% of the accrual balance, with receipt-backed lines near-exact and judgment lines wider. The trend matters more than the level: variance should shrink as more of the schedule moves to system-backed bases.
How do I handle accruals under cash-basis books, or convert cash-basis AP to accrual at year-end?
Cash-basis books skip accruals by definition; the year-end conversion books the AP aging plus accrued items as the liability and adjusts the expense accordingly. SMBs doing this annually for tax or lender reporting should keep the open-invoice list pristine - it IS the conversion entry.
SOX auditor flagged our accrual process as a manual control risk - how do companies automate or strengthen accrual controls?
Move the inputs to system reports (received-not-invoiced, in-flight invoices), template the JE with mandatory auto-reversal, separate preparer from reviewer, and keep sign-off evidence. The control becomes "system-generated data plus documented review" instead of "spreadsheet a person built" - that reclassification is what the auditor wants.
Stampli perspective
Stampli reduces the accrual problem at the source: invoices captured and coded the day they arrive mean fewer unknowns to estimate, and complete in-flight visibility means the accrual basis is recorded amounts, not guesses. The immutable audit trail on every invoice - when it arrived, who approved, when it posted - supplies the documentation accrual testing asks for.