Skip to content

Close exceptions

Find the difference. Find the reason. Resolve it.

Rebase investigates close exceptions across your ledger, subledgers and supporting systems, traces the underlying cause and prepares the resolution for accounting review.

Go from “this doesn't tie” to a supported next step without tracing the issue across systems by hand.

See an exception investigatedTalk to us
An illustration of a March 2026 clearing account exception investigated by Rebase. 1250 Settlement clearing, which takes customers' card payments and is cleared as the processor's payouts land at the bank, holds 14,220.00 on 31 March. 12,800.00 of it is the payouts for 30 and 31 March, which land on 1 April: timing, with no entry needed. Rebase traces the other 1,420.00 to the processor's fees, netted from every payout in March and never booked, and prepares journal entry JE-4473, debit 6815 Payment processing fees and credit 1250 Settlement clearing for 1,420.00, which waits on a senior accountant's approval. Booking the fees each month is left to the team.

The work behind the exception

Finding the difference is only the beginning.

Close software can tell accounting that an account does not reconcile. Someone still has to find which records caused the difference, why it happened and what should change.

An illustration of the same exception worked two ways: by hand, eleven steps across the clearing workbook, the ledger, the processor's settlement report and the bank; and by Rebase, which separates the 12,800.00 that is in transit from the 1,420.00 that is not, follows five records to the fees nobody booked, and prepares one entry.

Worked example

From exception to resolution.

March's settlement clearing, followed from the balance that should have been in transit to the entry that clears it.

An illustration of the March 2026 settlement clearing exception in seven stages. Rebase detects that 1250 holds 14,220.00; separates the 12,800.00 of payouts for 30 and 31 March, which land on 1 April, from 1,420.00 left unexplained; traces the processor's settlement report through its 21 March payouts and the matching bank deposits to the credits in 1250, and finds nothing posted to 6815 Payment processing fees; determines the cause, fees netted from the payouts and never booked; prepares journal entry JE-4473; routes it to Alex Chen, Senior Accountant, who can accept, edit or reject it; and once approved posts it to Business Central on 31 March, after which 1250 holds the 12,800.00 in transit and clears on 1 April.

Common close exceptions

The exceptions every close turns up.

Not only balances that don't tie: activity in the wrong period, movements nobody has explained, entries without support. Open one to see what Rebase does with it.

  • Missing postingThe source transaction exists, but the ledger has no entry for it.AWS 12,480.00 · paid 14 Mar, never recorded · JE-4471
    What Rebase does

    Traces the source record, searches the ledger for it by amount, date and counterparty, and confirms the entry is missing rather than posted somewhere else.

    Typically reads Plaid, Business Central, and Gmail.

    Bank ✓ · invoice ✓ · ledger ✗ → posting missing · JE-4471 prepared

  • DuplicateOne source event appears twice.Ramp 2,140.00 · charged twice on 6 Mar · refunded 9 Mar
    What Rebase does

    Matches references, amount, counterparty and timing, and tells a genuine repeat from a duplicate before anything is reversed.

    Typically reads Ramp and Business Central.

    Same merchant, card and amount, 40 seconds apart · refund matched 9 Mar

  • Wrong account or codingRecorded, but in the wrong account, department or entity.INV-88213 · 7,200.00 · posted to 2100, not 2000
    What Rebase does

    Compares the posting with its source document, the posting setup and how the same vendor or item was treated before.

    Typically reads Business Central, Source documents, and Posting setup.

    Brightwater Freight · posting group maps to 2100 · reclass RB-3F2A1C

  • Cut-off and timingActivity in the wrong period, or two valid records on different dates.Receipt 12,400.00 · ledger 31 Mar, bank 1 Apr · no entry
    What Rebase does

    Establishes when each side happened and was recorded, and whether the difference clears by itself, belongs in another period, or needs an entry.

    Typically reads Plaid and Business Central.

    Deposit in transit · clears 1 Apr · nothing to adjust

  • Unexplained movementAn account moved past your threshold, and nobody has said why.6510 · Travel +65.4% on February · 3 offsites, 41 transactions
    What Rebase does

    Compares the month with the last and with the budget, drills into the transactions behind any movement over your threshold, and explains it or raises it.

    Typically reads Business Central, Ramp, and Budget.

    3 offsites · 41 transactions · explained, nothing to adjust

  • Missing support or approvalAn entry or a balance without the evidence or the approval your policy asks for.Kestrel Print 3,180.00 · paid 24 Mar · no invoice
    What Rebase does

    Searches the connected systems and the AP inbox for the document, asks the owner when it is not there, and flags manual entries posted without the approval your policy requires.

    Typically reads Business Central, Gmail, and The account owner.

    No invoice in Business Central or the AP inbox · requested from the owner · waiting on source

Not every difference needs a journal.

Three of March's exceptions, three different answers. Rebase works out what happened before it decides what should change.

An illustration of three March exceptions and what each needed: 12,800.00 of card payouts in transit, a timing difference that needs no adjustment; Brightwater Freight's 7,200.00 invoice in the wrong account, for which a reclassification is proposed; and a 3,180.00 payment to Kestrel Print with no invoice, which needs the source document.

Rebase explains a difference before it proposes to remove one.

Every resolution shows its working.

The exception's record holds why it happened, what proves it, how it was treated, who approved it and what reached the ledger.

An illustration of the record of the March settlement clearing exception: its cause, the processor's fees netted from the payouts and never booked; its evidence, the settlement report and the 21 bank deposits; its treatment, a March expense; the entry JE-4473; its approval by Alex Chen, Senior Accountant, on 31 March; and its posting to Business Central the same day, after which 1250 holds only what is in transit.

When evidence is incomplete, Rebase surfaces the uncertainty instead of inventing a resolution.

Investigation is the step in the middle.

A reconciliation raises the exception; a person approves what it calls for; the ledger moves. This page is the part in between.

An illustration of the March settlement clearing exception through the close: 14,220.00 found in 1250 on 31 March; its cause established, 12,800.00 in transit and 1,420.00 of fees never booked; entry JE-4473 prepared; approved by Alex Chen; posted to Business Central on 31 March; and 1250 left holding the 12,800.00 in transit.

  1. Reconcile

    Difference detected

    1250 · 14,220.00 · 31 Mar

    On Reconcile accountsSee a reconciliation

  2. Investigate

    Cause established

    12,800.00 in transit · 1,420.00 fees

  3. Adjust

    Accounting treatment prepared

    JE-4473 · Dr 6815 / Cr 1250

    On Prepare accrualsSee an adjustment prepared

  4. Review

    Human approval

    Approved · Alex Chen

    On Prepare accrualsSee the approval record

  5. Post

    ERP updated

    Business Central · 31 Mar

  6. Verify

    Account reconciled

    1250 = 12,800.00 in transit

    On Reconcile accountsSee a reconciliation record
The productRebase Autonomous CloseReconcile accounts, investigate exceptions, prepare adjustments and move the close forward across the finance stack you already use.Explore Autonomous Close

Bring us an exception that slowed your last close.

We'll show you how Rebase would trace it across your systems, establish the cause and prepare the next step for review.

Book a working session