Paid Invoice Near-Match Review Hold

Keep a small bank difference from triggering an edit to an already-paid customer invoice. Preparation only, not an account action.

What to provide

Invoice/payment IDs, paid status, bank reference, exact amounts and accountant instructions.

How it works

1. Compare exact amounts and IDs rather than treating close values as equal.
2. Keep bank fees, partial payments and missing records as hypotheses until sourced.
3. Flag the documented need for accountant review and the paid-invoice edit boundary.
4. Return an exception note without changing paid invoices or accepting a difference.

The output

invoice | paid_status | bank_amount | ledger_amount | difference | hypothesis | reviewer

Worked fictional example

Fictional paid invoice 100 and bank 99 differ by 1. A fee is a hypothesis without fee evidence. Do not alter the paid invoice to 99 just to balance the reconciliation.

Checks and limits

Keep source versions and original values. Unknowns stay unknown. Use qualified review for regulated, legal or hiring decisions. No live account compatibility test, send, share, schedule, ledger change or payment is authorized.

More bookkeepers workflows · How-to guides

Method: reviewed source. Demand lead: Oct12 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude38, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia100. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured. Checked October 12, 2026.