Accrual journals reversed in the last close. A high count points at over-accrual or shaky estimates.
At a glance
Accrual Reversals counts the accrual journals that were reversed as part of the last GL period close. Accruals are estimates booked at period-end for activity that has occurred but not yet been invoiced or recorded (unbilled revenue, goods received not invoiced, expenses incurred but not yet billed), and they are normally reversed at the start of the next period when the actual transaction lands. A modest, stable count is the healthy rhythm of accrual accounting. A high or rising count is the signal worth investigating: it can mean the team over-accrues, that estimates are consistently off, or that the same items are being accrued and reversed repeatedly because an underlying process is not capturing the actual cost in time. It is an estimation-quality lens on the close.
Calculation
Calculated automatically from your Oracle ERP Cloud 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 large-enterprise wholesaler runs Oracle ERP Cloud and closes monthly. The controller reviews accrual reversals across two consecutive closes: the February close (period ended 28 Feb 26) and the March close (period ended 31 Mar 26).
Four things to notice:
- The March count nearly tripled and crossed the alert line. Seven reversals in February was a normal close. Nineteen in March is a clear elevation that the controller should explain before signing off the close pack.
- The cause was a goods-received-not-invoiced backlog. A procurement integration delay meant supplier invoices were arriving late, so the team accrued for received goods at month-end, then reversed and re-accrued repeatedly as actuals trickled in. The reversals were the symptom; the late-arriving invoices were the cause.
- The fix is process, not journal hygiene. Speeding up the supplier-invoice capture (or tightening the receipt-accrual matching) reduces the need to accrue and reverse the same items. Simply reversing more carefully does not address why the estimates keep needing correction.
- Read it with the manual ratio. In March the Manual JEs as % of Total card also ticked up, because the accruals and reversals were being keyed by hand. The two cards together told a single story: a procurement-to-pay gap was forcing manual estimation churn at close.
Sibling cards merchants should reference together
Accrual Reversals is an estimation-quality lens on the close. Read it alongside the other close-discipline and journal-health cards.Reconciling against Oracle ERP Cloud
Where to look in Oracle ERP Cloud: The closest native equivalents in the Oracle Fusion UI are:Navigator → General Accounting → Journals → Manage Journals (filter to reversal journals for the last close period) Navigator → General Accounting → Period Close → Close Status (the close workflow including reversals) Reports and Analytics → OTBI → Financials → General Ledger - Journals Real Time (reversal-flagged journals as a dimension)Oracle Fusion can auto-generate reversal journals from accruals flagged for reversal, and the close process surfaces them. Counting the reversal journals tied to the last close period in Manage Journals, scoped to the same Business Units and Ledgers, should match this card. Common mistakes when comparing against Oracle’s own reports:
- Counting all reversals, not just accrual reversals. Journals can be reversed for many reasons (corrections, error fixes). This card focuses on accrual reversals tied to the close. Make sure your Oracle query isolates accrual-type reversals.
- Period boundary confusion. A reversal generated at the start of the next period to unwind a prior-period accrual can be attributed to either period. Confirm which period the card and your report assign it to.
- Counting lines vs headers. A single reversal journal can have many lines. The card counts journals (headers), not lines.