Accrual Reversals (last close)

Card class: Non-Hero • Category: Ecommerce Platform

Count of accruals booked at one period close that were reversed at the next. High counts signal estimate quality problems or accrual hygiene issues.

​

At a glance

The number of accrual journal entries posted at the prior period close that reversed into the current period. In Sage Intacct most accruals are booked as reversing journal entries (the reversal auto-posts on the first day of the next period) or as recurring entries cleared by hand. A clean ledger expects a handful of these every month. A spike means the estimates feeding your accruals are wrong, the accrual was a plug rather than a measured liability, or someone is booking round-number accruals at close to hit a target and unwinding them quietly the next day. The card counts the reversed cohort so the Controller can read estimate quality at a glance instead of reverse-engineering it from the GL detail.

​

Calculation

Calculated automatically from your Sage data by matching prior-close accrual journals to their reversals in the current period. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​

Worked example

A UK-based multi-entity ecommerce group on Sage Intacct, three trading entities (UK Retail Ltd in GBP, EU Distribution BV in EUR, US Wholesale Inc in USD), consolidated monthly. Annual group revenue ~£40M. Snapshot taken at the May 26 close, posted 6 Jun 26. Reporting currency GBP. Default reversal alert threshold of 10. Five things to notice:

1. 27 reversals is well above the threshold of 10, and the headline alone does not tell you whether that is a problem; the dimensional cut does. Twenty-seven reversals in one close is high for a £40M group. But the count splits into two very different stories. The marketing, carriage, bonus, and goods-received-not-invoiced accruals (22 of the 27) are legitimate, measured liabilities that reverse because the real invoice has now arrived. That is healthy accrual hygiene working exactly as designed. The five round-number true-up accruals are the signal worth chasing, because round numbers booked at close and reversed the next day are the classic shape of earnings management or a plug used to hit a covenant or a board number. The card does not accuse anyone; it surfaces the cohort so the Controller can ask the question.
2. Goods-received-not-invoiced (GRNI) at 9 reversals is the largest single source and it is usually benign. When goods are received against a purchase order in the Inventory Control or Order Entry module but the supplier invoice has not arrived by close, Intacct (or the AP automation) accrues the expected cost. The next period the real invoice posts and the accrual reverses. Nine of these is normal for a distribution business with active inbound. The thing to watch is not the count but the variance: if the accrued amount and the actual invoiced amount differ by more than a few percent consistently, the standard costs feeding the accrual are stale. Pair this with Landed Cost Variance vs Standard to see whether GRNI reversals are clean or hiding a costing drift.
3. The five round-number true-up accruals are the only entries here that deserve a name-and-explanation review. A measured accrual is rarely a round number. A marketing accrual is £12,840, not £15,000. When close accruals land on £15,000, £20,000, £50,000 and reverse the next day with no supporting calculation, the Controller should pull the JE memo and the preparer. Most of the time the explanation is innocent (a genuine estimate rounded for simplicity), but this is exactly the cohort an external auditor will sample first, so it is better for finance to have the answer ready before the audit than to be asked cold. Pivot by Department to see whether the round-number accruals concentrate in one team.
4. A rising trend matters more than the absolute count. Twenty-seven this close against a trailing average of, say, twelve is the real story. A climbing reversal count usually means one of three things: the business is growing and the volume of genuine accruals is scaling (benign), the estimates are getting worse and accruals are being corrected more often (estimate-quality problem), or close discipline is slipping and people are accruing-and-reversing to smooth results (control problem). The 30-day trailing comparison on the card is what separates a one-off spike from a structural drift. On this account the count had climbed from 14 to 27 over three closes, which prompted the review.
5. Pair with Manual JEs as % of Total to separate automated reversals from hand-keyed ones. Auto-reversing JEs created by the system (the GRNI accruals, the standard freight accrual) are low-risk because the process is repeatable and auditable. Manual reversals keyed by a person at close are the higher-risk cohort, because each one is a judgement call with no system control behind it. If the reversal count is high but the manual-JE share is low, the accrual machine is just busy, not broken. If both are high, that is the combination an audit committee should look at. On this account the two cards read together showed that 22 of the 27 reversals were system-generated and only 5 were manual, which materially de-risked the headline.

​

Sibling cards merchants should reference together

​

Reconciling against Sage

Where to look in Sage Intacct: The native Sage Intacct views to run side by side with this card:

General Ledger → All → Journal Entries filtered to the prior close period with reversing entries shown, then to the current period for the matching reversals Reports → General Ledger → Account Activity on the accrual liability accounts (typically the 2xxx accrued-liabilities nominal range) to see the post-and-reverse pattern across the period boundary General Ledger → Recurring Transactions to see the recurring JE templates that auto-reverse, distinguishing them from one-off manual accruals Interactive Custom Report (ICR) built on the GL data source filtered to state = Reversed and grouped by source batch, counting matched original-to-reversal pairs in the close window Audit Trail on the accrual batches to see who created, posted, and reversed each entry, which is the fastest way to attribute round-number accruals to a preparer

In Intacct the cleanest native equivalent is to filter Journal Entries on the reversing flag for the close period and tie each to its reversal in the next period. For Multi-Entity Console accounts run the GL Account Activity report at the same entity scope as the dashboard filter, otherwise reversals in entities outside the filter will not appear in the native report but will (if scoped in) on the card. Common reconciliation pitfalls:

• Recurring vs accrual reversals: Intacct’s recurring journals (rent, depreciation) also reverse or repeat. The card excludes pure-recurring templates by default; a native Journal Entries listing includes them, so the native count will usually read higher than the card.
• Reversal date vs original date: a reversal posted on the first day of the new period belongs (in this card’s logic) to the prior close that created the original. Native reports list it under the current period date, which can make the two appear to disagree until you align on which close “owns” the pair.
• Partial reversals: a manual JE that backs out only part of a prior accrual counts as one reversal on the card but may look like a fresh entry in a naive native listing. The card matches on the source-batch pointer, not on amount.

Why our number may legitimately differ from a Sage Intacct journal listing: Cross-connector reconciliation: The cross-connector value here is attribution. Sage Intacct knows that an accrual reversed; the commerce connectors know what actually happened in the period (the marketing spend, the freight cost, the bonus pool). When a reversal pattern correlates with a commerce-side signal (a marketing accrual that keeps reversing while ad spend in the Google Ads connector keeps climbing), the cause is usually a timing mismatch between when spend is committed and when the invoice lands. That is a fixable process problem, and seeing the two systems side by side is how the Controller finds it without a forensic GL trawl.

​

Known limitations / merchant FAQs

Are accrual reversals bad? No, most are healthy. The whole point of a reversing accrual is to book an estimated liability at close and unwind it cleanly when the real transaction lands. A business with zero reversals is probably not accruing properly. The card surfaces the count so you can read estimate quality and spot the small cohort of reversals that signal a problem, not so you can drive the number to zero. What count is normal? It scales with business size and accrual policy. A small single-entity SMB on Sage Accounting might see 3-8 a month; a £40M multi-entity group on Intacct might see 15-30. The threshold defaults to 10 but should be tuned to your baseline. What matters more than the absolute number is the trend and the manual-vs-automated split. Why do round-number accruals matter so much? Because measured accruals are almost never round. A real freight accrual is £4,317, not £5,000. Round-number accruals booked at close and reversed the next day are the textbook shape of an earnings plug, and they are the first thing an external auditor samples. The card does not assume bad intent; it surfaces the cohort so finance can document the basis before audit asks. Does this card prove someone is manipulating earnings? No. It is a hygiene and estimate-quality signal, not an accusation. A high count has many innocent explanations (a growing business, a lumpy invoice cycle, a one-off project accrual). It is a prompt to look, attribute, and document, which is exactly what good close governance does anyway. How does Sage Intacct handle reversing journals? Intacct lets you flag a journal entry to auto-reverse on the first day of the next period. The reversal posts automatically and carries a pointer back to the original batch, which is what this card uses to match pairs. Recurring transactions are a separate mechanism for entries that repeat every period; the card distinguishes the two. What about manual back-out JEs that do not use the reversing flag? The card matches these by source-batch reference and by memo where the preparer recorded the link. A truly orphaned manual back-out (no link, no memo) may not be matched, which is one reason to enforce a memo standard on reversing entries. This is the only category the card can miss, and it is a process-discipline issue rather than a card limitation. Sage Intacct vs Sage 50 / 200 on accrual reversals? Conceptually identical, mechanically different. Sage 50 and Sage 200 support reversing journals but expose the reversal link differently through their APIs, and the dimensional cut (Department, Class) is richer on Intacct. This connector targets Sage Intacct; if you are on Sage 50 or 200, reach out about connector availability and the reconciliation paths will differ. Does multi-entity change anything? The logic is identical per entity. Multi-Entity Console counts reversals per entity and sums for the consolidated view. The most useful operational read is per-entity, because a reversal spike concentrated in one subsidiary points straight at that team’s close process. Inter-entity accruals (booked in one entity, reversed in another) are matched across the consolidation. How fresh is the number? The card reads the GL at typical Intacct refresh cadence, around 5 to 15 minutes from the most recent posting. Because reversals cluster at the period boundary, the most meaningful read is in the few days after close once the auto-reversals have posted and any manual back-outs are keyed. Can a reversal leave the ledger out of balance? A correctly posted reversal is itself balanced, so no. But a partial or fat-fingered manual back-out can leave a residual. That is why this card pairs with Transaction Imbalances: if reversals are high and imbalances are non-zero in the same close, the reversal process itself may be introducing errors. What is the right action when the alert fires? Triage by source. Confirm the automated GRNI, freight, and payroll accruals reversed cleanly against real invoices (benign). Then pull the manual and round-number reversals, attribute each to a preparer via the Audit Trail, and confirm a documented basis exists. The action is documentation and attribution, not necessarily a fix, because most reversals are working as designed. Implementation Partner role on this metric? The Partner usually owns the accrual policy, the reversing-JE templates, and the close calendar. If this card disagrees with the Partner’s close pack, the cause is almost always a recurring-vs-accrual classification difference or a period-ownership difference on the reversal date. Align in the Vortex IQ field map and invite the Partner into the conversation early.

---

​

Tracked live in Vortex IQ Nerve Centre

Accrual Reversals (last close) is one of hundreds of KPI pulses Vortex IQ tracks across Sage and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.