Use case · Corrections nobody trusts
Which journal in your ERP do you trust least?
Every finance team has one. The correction from last quarter that nobody can explain anymore, the miscellaneous line that made the close balance, the suspense clearing that came back the next month.
“Most finance teams discover problems late and correct them under pressure.”
Click the journal you would least like to explain to your auditor.
Illustrative ledger. The three questions on each journal follow the Actuals blog on reconciliation errors.
Correct it yourself
The correction can be the error.
“A legitimate timing difference, such as an outstanding settlement that has not yet cleared, is mistakenly treated as an error and ‘corrected.’ The correction itself creates a real discrepancy where none existed.” From the Actuals blog
Pick an open item, then choose what you would do at close. The result shows what happens the month after.
Where corrections end up
A suspense account that never gets to zero.
“If those suspense accounts balance out to zero, everything is fine. But every accountant also knows that this is rarely the case.”

Drag through the year. Both sides get the same nine differences every month.
- Items inside
- 0
- Owner
- Nobody
- Oldest
- —
- Resolved so far
- 6
- Oldest open
- 12 days
Illustrative year. Actuals on its blog: “Flagged against this transaction ID and this journal, not netted into a suspense balance that nobody owns.”
How Actuals handles it
Fix it before the ERP, not in the ERP.
“Financial truth shifts from late correction during close to upstream control before numbers reach the ERP.” From actuals.io
JE-1018Revenue, Adyen settlementJE-1031Correction revenue, see Excel v7JE-1036Miscellaneous adjustmentJE-1040Suspense clearingJE-1042Reversal of JE-1031JE-1047Accrual refunds, estimate
Raw events in the ledger, fixed by hand during close.
JE-1018Revenue, Adyen48,211 transactionsJE-1019PSP fees48,211 transactionsJE-1020Refunds1,904 transactionsJE-1021Chargebacks37 transactionsJE-1022Accrual, period cut-off2,116 transactions
Final journals, each one traceable to the transactions behind it.
Drag the line. Left is the ledger corrected after posting, right is the same month established before posting.
Quotes from actuals.io/product and the Actuals blog. The ledger above is illustrative.
From the customer files
What three finance teams stopped correcting.

“When I joined, the accuracy of the data simply wasn’t there. Actuals fixed that. Now the data is accurate and that changes everything.”
VP Finance, CatawikiJournalisation, which would have been unrealistic to build internally, is handled structurally.
After an acquisition that increased transactions by 100x, they discovered millions moving into transitory accounts with no reconciliation and no clear audit trail.
A listed betting companyThe ERP, Oracle Fusion Cloud ERP, remains the system of record. Actuals adds transaction-level reconciliation and an audit trail.
Reconciliation lived in Excel and “made it hard to tell whether issues were one offs or structural problems repeating across thousands of orders.”
InterrailEvery order, payment, refund and settlement is now matched across systems.A test for your next close
Count your corrections. Then count them again.
“Count the manual adjustments made during close. A stable or growing count means matching and posting need attention.” From the Actuals blog.
Fill in how many manual adjustments you made in each of your last three closes. The verdict updates as you click.
Tired of correcting the same thing twice? The 15-minute Actuals scan shows where your corrections start, before they reach the ledger.


