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.
| What it counts | The number of reversal documents posted against accrual journals at the last close. In S/4HANA Cloud, an accrual posted via the Manage Journal Entries app or transaction FBS1 (or the modern Accrual Engine) carries a planned reversal date, and the reversal posts as a distinct journal entry referencing the original. The card counts those reversal documents in the Universal Journal (ACDOCA, with the reversal-reference fields on the linked BKPF header) for the period boundary of the most recent close. |
| What “accrual” means here | Period-end estimates that have no invoice yet. Accrued expenses (services consumed, not yet billed), accrued revenue (earned, not yet billed), goods-received-not-invoiced (GR/IR), bonus and commission provisions, and utility or rent accruals. These are booked to keep the P&L in the right period under the matching principle, then unwound. |
| Reversal mechanism | Most accruals are entered as reversing journals: the original posts on the last day of the period, the reversal posts automatically on the first day of the next period. SAP’s Accrual Engine and the classic reversal-date field on FBS1 both drive this. Manual reversals (transaction FB08) also count if they unwind an accrual document. |
| Why count, not value | The headline here is operational hygiene, not money. A spike in the count signals either a larger-than-usual accrual workload at close or accruals that are being manually reversed late. The euro/pound value of accruals sits on related balance-sheet cards. |
| Company Code scope | Respects the selected Company Code filter. By default counts reversals across every Company Code visible to the connected SAP API role. Each Company Code closes on its own calendar, so the “last close” is resolved per Company Code and then summed. |
| Time window | 30D (the trailing 30 days, which captures the most recent close cycle and its reversals) |
| Alert trigger | >10 reversals in the window flags for review |
| Roles | owner, finance |
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.| Accrual type (booked at May close) | Reversal date | Company Code | Reversals counted |
|---|---|---|---|
| Accrued professional fees (audit, legal) | 01 Jun 26 | 1000 | 3 |
| Goods-received-not-invoiced clearing | 01 Jun 26 | 1000 | 4 |
| Accrued sales commission | 01 Jun 26 | 2000 | 2 |
| Accrued utilities | 01 Jun 26 | 2000 | 1 |
| Manual late reversal of an April accrual (FB08) | 12 Jun 26 | 1000 | 1 |
| Accrual Reversals last close (this card) | 11 |
- 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.| Card | Why pair it with Accrual Reversals (last close) |
|---|---|
| Period Close On-Time Rate (12mo) | Tells you whether closes are landing on deadline. A late close often means accruals and reversals were rushed or skipped. |
| Period Close Status by CompanyCode | Shows which Company Codes are open vs closed right now. Reversals only fire once the next period is open, so close status frames this count. |
| Period Close Past Deadline (any CompanyCode) | The real-time complement. A Company Code stuck past deadline is one where reversals may not yet have posted. |
| Manual Journals (FB50/FB60) as % of Total | Late manual reversals (FB08) and manual accruals both inflate the manual-journal ratio. High manual activity at close is a control concern. |
| Open / Unposted Journal Entries | If reversals are parked unposted, they will not show as accrual reversals until posted. This card catches the backlog. |
| Journal Imbalances (Debit/Credit) | A botched accrual or reversal can leave a one-sided posting. Pair to confirm the close is balanced. |
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.
| Reason | Direction | Why |
|---|---|---|
| Document vs line counting | Card lower | The card counts reversal documents; a raw line-item export counts lines. |
| Per-Company-Code close boundary | Either | Company Codes close on different days. A single calendar filter in a SAP report will not align with the card’s per-Company-Code “last close” resolution. |
| Manual vs engine reversals | Either | The card includes both Accrual Engine reversals and manual FB08 reversals of accruals. A report filtered to one source misses the other. |
| Late reversals | Card higher in the later window | A reversal that fires weeks late lands in the window that contains its posting date, not the window of the close it belongs to. |
| Unposted reversals | Card lower | Reversals parked in an unposted state are not yet in the Universal Journal, so they are not counted until posted. |