Skip to content
← All insights
Systems

Reconciling a system that has no memory

When the source system only knows today's balance, the first job is to give it a past. Notes from building Recon3.

A stack of nightly snapshot sheets recedes into the past; a signal trace runs along their edges, flat except for one flagged night. TONIGHT D0 D−1 D−2 D−3 D−4 D−5 D−6 GO-LIVE DIGI-DNA · NOTES 2026-10-23 A PAST PLATE

Plenty of operational software only knows the present. A point-of-sale house-account app will tell you what a member owes right now, and nothing about what they owed last Tuesday. That is fine for the front desk and useless at month end, when the books need to tie to a specific date.

Give it a past

The first move in Recon3 was not reconciliation at all. It was memory: an immutable nightly snapshot of every balance, from go-live forward. Re-running a date never overwrites a good run. Once the system has a history, reconciliation becomes arithmetic instead of archaeology.

A source system that knows only today's balance writes one sealed snapshot each night into a row of days. Below, the accounting receivable for the same days. The nightly difference is traced underneath against a dollar threshold and a percentage threshold; only the night that breaks both is flagged. A separate card-processor cross-check records the basis of every match. SOURCE · HOUSE ACCOUNTS TODAY'S BALANCE NIGHTLY CAPTURE SNAPSHOTS · IMMUTABLE D−6 D−5 D−4 D−3 D−2 D−1 D0 Δ Δ Δ Δ Δ Δ Δ $ THRESHOLD % THRESHOLD 0 RECEIVABLE · ACCOUNTING DIFFERENCE · NIGHTLY FLAG CARD PROCESSOR 7 / 7 MATCHED, FIRST DAY BASIS KEPT 1 2 3 4 5 DIGI-DNA · NOTES 2026-10-23 SNAPSHOT LEDGER FIG. 1
Fig. 1The snapshot ledger. (1) The source knows only today. (2) One sealed snapshot per night; re-runs never overwrite a good run. (3) The difference to the receivable is recorded nightly. (4) A day is flagged only when it breaks both thresholds. (5) Charges are cross-checked against the card processor, with the match basis kept.Full-size drawing for Fig. 1 (SVG)

Flag what matters

The receivable for the same date comes from accounting, and the difference is recorded every night. A day is flagged only when it breaches both a dollar threshold and a percentage threshold. One rule alone floods finance with noise; both together surface the days that genuinely break.

Refuse to guess

The hardest design decision was what to show when the data disagrees with itself. If reconstructed ageing does not tie to the source system's own total, Recon3 reports the balance unaged rather than display buckets that contradict each other. An honest blank is worth more than a confident wrong answer.

An honest blank is worth more than a confident wrong answer.

Recon3 snapshot run history: one row per capture with status, account count, control total and duration, including a partial run and a failed run with their notes.
Fig. 2Snapshot runs in Recon3: every capture logged with its control total. The failed and partial re-runs sit beside the good runs and never replace them.Screenshot of the running system on synthetic demo data; no client records shown. Client: Toler's Cove Marina, shown as a separate entity; no endorsement implied.

Cross-check independently

Charges are matched against card-processor payments, and the basis for every match is recorded. On the first day of real data, seven of seven matched. The point is not the score. The point is that the system can show its work.

Build the system behind the outcome.

Start a Strategic Build →