Automation & Integration

Reconciliation and month-end close, run on a schedule.

Two systems each hold a defensible version of the same number, and the close still has to land on its date. We build the process that makes them agree: matching, exception queues, scheduled runs, routed approvals and notification on break.

why they disagree · not this page · Data Engineering & Analytics

The next step

Book an assessment call

30 minutes · with the engineer who would scope the work

one-page recap within 2 business days of a call that progresses


Reconciliation loop — match, except, return Two sources — invoices and accounts payable, inventory and the general ledger — are read together and passed to a match engine, step 1. Matched items go straight to a resolved ledger, step 2. Unmatched items go to an exception queue, step 3. Reviewed exceptions return to the match engine, step 4. Which exceptions to re-match stays a human judgement call. Source AInvoices / AP Source BInventory / GL 1 Match engine matched 2 Resolvedledger unmatched 3 Exceptionqueue re-matched 4 Not automated: which exceptions to re-match stays a human call. Source AInvoices / AP Source BInventory / GL 1 Match engine matched 2 Resolvedledger unmatched 3 Exceptionqueue re-matched 4 Not automated: which exceptions to re-match stays a human call.
Source A and Source B stand for any two systems that hold the same number. Both feed a match engine. What matches resolves straight through. What doesn't goes to an exception queue, gets a human decision, and feeds back into the next scheduled run — a loop, not a one-time reconciliation. Not automated: which exceptions to re-match stays a human call.Full step-by-step description

The loop, step by step. Two systems hold their own version of the same number: Source A, an invoice register or an accounts-payable ledger, and Source B, an inventory system or a general ledger. Both are read on the same schedule. The four numbered steps are the loop itself:

  1. Both sources are passed to a match engine, which compares them line by line on the keys agreed at the start.
  2. What matches resolves straight through to the resolved ledger, with no person touching it.
  3. What doesn't match goes to an exception queue, with a reason attached. A named person decides it — write it off, correct a source record, or escalate it. That decision is the one step in this loop that stays human.
  4. Reviewed exceptions return to the match engine on the next scheduled pass, so an exception still open when the schedule fires becomes a notification, not a surprise at close.

For a lot of operations-heavy companies, this is a familiar week. The invoice total in the ERP doesn't match the one on the bank statement. The count in the warehouse system doesn't match the one in the general ledger. Nobody disputes that the numbers should agree. They just don't yet, so the days before close are spent chasing the difference by hand, in a spreadsheet that exists for exactly one week a month.

This is delivery history, not a pitch.

company delivery history · founder-asserted ·

We have done this work: invoice reconciliation, inventory reconciliation, month-end close process automation and, in the founder's own words, "any reconciliation process and systems". No client is named and no cycle time or match-rate figure is claimed here; neither is permissioned.

Any two systems that should agree

The pattern does not depend on which two systems are involved. It depends on there being two sources that each claim to be right, and a rule for what "agree" means between them. We have built this against invoice registers, inventory systems and other systems of record, matched on the keys that are reliable in practice rather than the ones that look reliable in a data dictionary.

Month-end close, on a schedule or a named decision

The close is the same problem on a deadline: cut-off, accruals, the reconciliations, consolidation, then the report. Each of those steps either runs on a schedule or waits on a named person's decision, never on whoever remembers to run it. What we do not automate is the judgement calls: whether an exception is a real break or an acceptable rounding difference is a decision for a person, every time.

Where this work stops

This work covers the process that makes two numbers agree on a date: the matching, the exception path, the schedule and the notification. It does not own why the numbers disagreed in the first place, which is a modelling and lineage question for Data Engineering & Analytics — see the rail note above.

How the loop runs

  1. Bring the two sides together. Both systems' versions of the same number are read on the same schedule: an invoice register against a bank feed, or an inventory count against the general ledger.

  2. Match what agrees, automatically. Lines that reconcile on the agreed keys resolve straight through, with no person touching them.

  3. Route what doesn't. A mismatch goes to an exception queue with a reason attached, not into a spreadsheet someone has to remember to check.

  4. Name an owner for every exception. A person decides it — write it off, correct a source record, escalate it. That decision is the one step in the loop that stays human.

  5. Notify on break. If a run fails or an exception ages past its window, a notification fires — the same notification-system pattern used across Automation & Integration — instead of the gap surfacing for the first time at close.

Continue

Start with a call about the close that still has to land on its date.

Book an assessment call

30 minutes · with the engineer who would scope the work

one-page recap within 2 business days of a call that progresses