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.”

From actuals.io
General ledger · October journals5 of 7 made by hand

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.”

Nart Wielaard, Accountant.nl, translated on the Actuals blog
A small figure walks towards a high wall of grey stones; one stone in the wall is green

Drag through the year. Both sides get the same nine differences every month.

Netted into a suspense balance €0
Items inside
0
Owner
Nobody
Oldest
—
Flagged per transaction, with an owner 3 open
    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

    Corrected after posting
    • JE-1018Revenue, Adyen settlement
    • JE-1031Correction revenue, see Excel v7
    • JE-1036Miscellaneous adjustment
    • JE-1040Suspense clearing
    • JE-1042Reversal of JE-1031
    • JE-1047Accrual refunds, estimate

    Raw events in the ledger, fixed by hand during close.

    Established before posting
    • JE-1018Revenue, Adyen48,211 transactions
    • JE-1019PSP fees48,211 transactions
    • JE-1020Refunds1,904 transactions
    • JE-1021Chargebacks37 transactions
    • JE-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.

    “Correct period allocation without manual corrections”Cut-offs, accruals and revenue timing are set before data reaches the ERP.
    “No unresolved mismatches carried forward”An unexplained difference stays visible in Actuals until someone resolves it.
    “Replay balances, journals, and adjustments on demand”Every adjustment keeps its trail, so a journal can be explained months later.

    Quotes from actuals.io/product and the Actuals blog. The ledger above is illustrative.

    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.

    Three closes ago12
    Two closes ago12
    Last close12

    Tired of correcting the same thing twice? The 15-minute Actuals scan shows where your corrections start, before they reach the ledger.