Count of accrual reversals booked at the last period close. The number that tells the Controller whether month-end accruals were temporary estimates or quietly became permanent.
At a glance
The count of reversing accrual journal entries that posted at the most recent period close across the selected Company Codes. Month-end accruals (accrued expenses, accrued revenue, accrued bonus, goods-received-not-invoiced provisions) are booked as estimates in the closing period and reversed automatically on the first day of the next period when the real invoice or document lands. This card counts how many of those reversals actually fired. A healthy close reverses what it accrued. A close that accrues but never reverses is parking estimates on the balance sheet, which is exactly what auditors and the FD want to catch early.
Calculation
Calculated automatically from your SAP data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A mid-market manufacturer running SAP S/4HANA Cloud Public Edition with two Company Codes: 1000 UK Manufacturing Ltd (GBP) and 2000 EU Sales BV (EUR). The May close ran with a deadline of 05 Jun 26. The card window is the trailing 30 days ending 22 Jun 26, which captures the June-period reversals of the May accruals.
Five things to notice:
- The count is 11, just over the
>10alert threshold. The Nerve Centre flags it. The flag does not mean something is wrong, it means a human should glance at the list. In this case the volume is driven by a heavier-than-usual GR/IR clearing batch, which is benign. - One reversal is a late manual FB08 on 12 Jun 26. That is the interesting line. An April accrual was supposed to reverse on 01 May 26 but did not, so someone reversed it manually six weeks late. Late manual reversals are the signal worth investigating because they mean an accrual sat on the balance sheet for a full extra period, which can misstate two consecutive months.
- Each Company Code closes on its own calendar. CC 1000 and CC 2000 both ran their May close before the 05 Jun 26 group deadline, so both sets of reversals land in the same card window. If CC 2000 had run a soft close and deferred reversals, its count would appear in a later window instead.
- The card counts documents, not lines. A single GR/IR reversal journal can clear dozens of
ACDOCAlines, but it counts as one reversal. This keeps the number readable as “how many reversal events happened” rather than line-noise. - A count of zero after a close is its own red flag. If the prior period accrued (the balance-sheet accrual accounts moved) but this card reads zero, the reversals did not fire. That is the failure mode the card exists to catch: estimates that quietly became permanent because the reversal date was never set or the Accrual Engine run was skipped.
Sibling cards merchants should reference together
Accrual reversals are a close-hygiene signal. They make most sense read alongside the rest of the period-close family.Reconciling against SAP
Where to look in S/4HANA Cloud: The closest native equivalents inside the SAP Fiori launchpad are:Manage Journal Entries Fiori app filtered to reversal documents in the period after the close Display Journal Entry (transaction FB03) to inspect the reversal-reference link on any single document Reverse Journal Entry (transaction FB08) for manual reversals and to see what was reversed late Accrual Engine apps (Manage Accrual Objects / Run Periodic Accruals) if your tenant uses the modern Accrual Engine rather than classic FBS1 reversalsTo match this card, run Manage Journal Entries filtered to Posting Date in the first days of the period after the close, with the reversal indicator set, and count distinct reversal documents that reference an accrual journal. Group by Company Code to match the per-Company-Code resolution the card uses. Common mistakes when comparing against SAP’s own reports:
- Counting lines instead of documents. A GR/IR reversal can clear many
ACDOCAlines. SAP line-item reports return every line; the card counts reversal documents. Always deduplicate by document number. - Mixing accrual reversals with ordinary document reversals. Not every FB08 is an accrual reversal. A reversed billing document or a corrected manual entry is also an FB08, but it is not an accrual reversal. Filter to documents whose original was an accrual posting (reversing-entry flag or Accrual Engine source).
- Wrong period boundary. Accruals post in the closing period; reversals post in the next period. If you filter both to the same period you will under-count. The card resolves the close boundary per Company Code, so a single calendar filter will not match a multi-Company-Code group.