From monthly exports to a checked reconciliation workbook.

What the demonstration is showing

• Rules you can read.Four written rules decide how a receipt is allocated to invoices. Anything that does not satisfy a rule is held, with the candidates listed, rather than matched on a guess.
• Checks that can stop a run, and checks that flag it.A missing required column, an unreadable amount or a key that appears twice with different values stops the refresh, because no reliable result is possible. An exact duplicate row is counted once and reported. Control totals are compared to the general ledger, and a difference that is not explained is shown for investigation with the whole run marked as needing review.
• A reviewer who still decides.The workbook prepares the reconciliation and the exception list. A person reviews it, decides the treatment and signs off.
• Notes someone else can run from.Rules, check results, run details, a change log and a handover outline sit beside the output, not in one person’s head.

About this example

• “Applied” means allocated within this synthetic reconciliation. The demonstration does not post receipts or journal entries to any accounting system.
• The invoices dated before 1 September are the balances outstanding at the start of the example period.
• The example assumes no earlier partial payments, credits, write-offs or other opening adjustments against those invoices.
• It is a limited demonstration of one workflow, not a general-purpose production accounting engine.

A real engagement would be built in the environment your team already uses, often with formulas and Power Query, and only with a script or macro where that genuinely helps. The how it works page explains the steps, and the e-commerce reconciliation reference build shows a larger multi-source case.