Match a ledger against its counterpart on a cadence, explain each variance in plain language, flag the breaks, and hand a human a ready-to-post correction — flow8 prepares the fix, a person commits it. Runs on your infrastructure, against your systems of record, with a full audit trail.
Two systems that are supposed to agree quietly drift apart: the ledger says one thing, the bank says another; the order shipped but the invoice never matched; a decision was approved but the outcome never landed. Today a person finds the gap days or weeks later by eyeballing spreadsheets, then spends the rest of the day reconstructing why it broke and hand-typing the fix. The break is expensive precisely because nobody is watching the two sides on a cadence.
The moment you try to close that gap with an off-the-shelf "AI reconciliation agent," you hand a model the authority to mark items matched and auto-post journal entries and adjustments — to move money on its own judgement. That is exactly the authority you cannot hand a model.
Fast — this is the most battle-tested shape on flow8, already running in production against a live ledger. A pilot points at your two sources with the kill-switch on and runs shadow-first, so you see explained variances and pre-drafted corrections before any reach a person — reconciling in days, not a quarter.
The same pipeline serves every pair of sources that must tie out — one reconciliation or ten.
The two sides are re-matched every cadence — hourly to weekly — so a break surfaces while it is still cheap to fix, instead of being discovered days or weeks later at close.
Not a raw red cell but a classified break: kind (amount mismatch / missing counterparty / wrong account / timing), the signed delta, and a plain-language reason a reviewer can act on in seconds.
The journal posting, the adjusting entry, the matched pair — rendered ready to review. The human approves in seconds instead of reconstructing the fix from scratch.
Money and identity corrections are prepared as draft rows and flagged for a person. The audit trail shows 'flow8 prepared, a human committed' — nothing consequential fires on its own.
One human task per unhealthy unit, deduped against the database — no duplicate tickets on re-runs, and no break that slips because two people each thought the other had it.
A live rollup of what's matched / unmatched / proposed / blocked, recomputed every run, with a single throttled digest when something alert-worthy crosses — one surface to watch, not ten inboxes.
The model proposes; a human executes; nothing touching money or identity ever auto-posts. It is the same secure spine every flow8 Solution runs — here worn as a continuous reconciler.
proposed correction on a shared, tamper-evident actions ledger — not a posting.proposed row on the shared actions ledger, keyed idempotently to the unit.
draft, not act
Continuous Reconciliation watches two sources that must agree — a ledger and a bank feed, an order table and a fulfillment record, a decision log and its realized outcome — and re-matches them on a cadence. It pulls only new units since a stored cursor plus their expected counterparts, runs the injection pre-scan on every untrusted memo and reference, and computes the objective variance in deterministic Code. A schema-locked LLM then acts purely as a suggester — proposing the matched counterpart and explaining the gap — while the binding verdict is made in code.
Because the matching math is Code and never a model, because money corrections are capped at prepare-only by construction, and because the evidence row is written before any side-effect on a hash-chained, signed ledger, you get continuous reconciliation without ever handing a model the authority to post. A healthy-looking LLM score over failing evidence is forced to review, and a closed-period or debits≠credits rule blocks the entry regardless of what the model said. Off-the-shelf agents give a model authority first and bolt on guardrails later — flow8 makes the guardrail the architecture.
proposed row plus a flag, and a human commits the journal posting inside the action gate. The matching verdict is computed over fields the unit's owner cannot freely author, so an attacker-authored 'mark this matched' in a memo can never trigger a posting.Not rebuilt from scratch — composed from the same governed building blocks every flow8 Solution shares, so it ships in days.
Any business whose work has two sources of truth that must agree — swap the two source schemas and the rule set, and the spine is identical.
Adopt this one and it plugs into the spine the others already speak.
Watch a cadence of drift turn into explained variances and pre-drafted corrections your team approves in one click — drafts only, no postings, full audit trail. When you're ready, flip on the human-task queue and add the signed governance ledger or a three-way match on the exact same pipeline.
Book a demo →