Accounting

Availableapp.erp.io/accounting/reconciliation

Reconciliation

Reconciliation is the weekly check that the ledger and the bank agree. Everything the system is unsure about is held in a queue and answered, rather than guessed.

Cadence
Weekly beats monthly
Automatic matches
Above a confidence threshold
Everything else
Held in a queue
Queue is
Persisted and answerable

How matching works

A bank line is compared against open invoices, open bills and unmatched journal entries. Amount, date proximity, counterparty name and reference all contribute to a score. Above a threshold the match is made automatically. Below it, the suggestion is kept — it goes into a queue where you accept or reject it, rather than being discarded.

That the near-misses are persisted rather than thrown away is the part that changes the working day. The queue is the list of decisions only a human can make, in one place, and it is short by the time you reach it because everything unambiguous has already been matched.

app.erp.io/accounting/reconciliation
Reconciliation

Bank — current · 18 to answer · balance ties to 12 Mar

Auto-matchFinish
Bank line
HARBOUR LOGISTICS +8,400.0011 Mar
ACME INC +1,240.0010 Mar
STRIPE PAYOUT +2,481.2012 Mar
Suggested match
INV-1042 · Harbour Logistics£8,400.00 · due 9 Mar96%
INV-1038 · Acme Inc£1,240.00 · due 1 Mar92%
2 candidates — settlement batchneeds a decision61%
The suggestion queue. Bank lines on the left, what the system thinks they settle on the right.

Working the queue

Start with the automatic matches

Scan them. They are usually right, and scanning is a different activity from deciding.

Answer the queue

Each row is accept, choose a different document, or split across several.

Split where a payment settles several invoices

One receipt against three invoices is normal and is supported directly.

Deal with what nothing matches

A receipt with no invoice is either a prepayment, a refund, or something that should have been invoiced and was not.

Check the balance ties

The reconciled balance against the statement. This is the actual test.

Never lower the automatic threshold to empty the queue

It is the obvious response to a long queue and it is the wrong one. Lowering the threshold does not make the uncertain matches correct; it makes them silent. A wrong automatic match is worse than an unanswered one, because nobody will look at it again. If the queue is consistently long, the cause is usually missing references on payments or a customer paying several invoices in one transfer — both fixable upstream.

What makes matching work well

Do thisEffect
Put the invoice number on the invoice prominentlyCustomers quote it as a reference, which lifts scores from good to certain.
Reconcile weeklyFewer open documents to match against, so fewer ambiguous candidates.
Write posting rules for recurring itemsSubscriptions and standing costs never reach the queue at all.
Record part-payments as they arriveA part-paid invoice matches its remainder cleanly later.
Treat processor payouts as settlementOtherwise every payout looks like an unmatched receipt. See [Commerce](/docs/modules/accounting/commerce).

What this does not do

No automatic write-off of small differences

A penny difference is still a difference and is shown rather than absorbed.

No bank-side confirmation

Reconciliation is against imported data. It does not call the bank to confirm.

No multi-currency matching

A receipt in one currency against an invoice in another is not matched automatically.

No reconciliation of non-bank accounts

The workflow is for bank and card accounts. Clearing accounts are reviewed in the ledger.

Questions

What if I accept a wrong match?

Unmatch it. The link is reversible and the audit trail records both actions.

Can somebody else finish a reconciliation I started?

Yes. The queue is shared, not personal.

Does the AI post anything here?

No. It scores candidates. Matching above the threshold is a deterministic rule you can see.