Reconciliation Agent

Two data sets.
Every mismatch found.

Invoices against purchase orders. Bank statements against accounts payable. Reconciliation Agent compares two data sets record by record and surfaces every anomaly — so nothing gets closed out with a silent discrepancy buried in it.

Record Matching Anomaly Reporting
Record Matching

Match records across
two independent sources

The agent pairs records from each side using configurable match keys — invoice number, PO reference, transaction date and amount — and classifies each pair as matched, partially matched, or unmatched.

  • Configurable match keys per reconciliation type — no fixed schema assumption
  • Handles many-to-one and one-to-many matches, not just exact 1:1 pairs
  • Partial matches (amount off by a rounding difference) are distinguished from true mismatches
  • Every classification includes the specific fields that did or didn't align
See It in TotalApp
totalapp.app / ma
Invoices vs. Purchase Orders
142 invoices matched exactly to their PO
! 6 invoices matched with a $0.01–$2 rounding gap
3 invoices have no matching PO on file
Only the 3 true mismatches need a human look.
Live in TotalApp
Anomaly Reporting

Every discrepancy,
one structured report

Unmatched and partially-matched records are compiled into a single report — what didn't align, by how much, and on which side — so a reviewer can close the gap without re-deriving the comparison by hand.

  • One report per reconciliation run — amount, count, and source of every discrepancy
  • Sortable by severity — a $2 rounding gap is not the same priority as a missing record
  • Exportable for month-end close documentation and audit trails
  • Re-runs automatically as new records arrive, without re-checking already-matched pairs
See It in TotalApp
totalapp.app / an
Reconciliation Report
i 151 records compared · 142 exact · 6 partial · 3 unmatched
INV-2291 — no PO on file, $4,200 exposure
Ready to export for month-end close documentation.
Live in TotalApp
Why It Matters

Nothing closes out with a hidden gap

The two-sided comparison every finance and ops team runs — done consistently, every time.

Configurable Match Keys

Define what counts as a match per reconciliation type — no fixed schema assumption.

Many-to-Many Matching

Handles split invoices, combined shipments, and other non-1:1 matching patterns.

Structured Anomaly Reports

Every discrepancy compiled into one sortable report — amount, source, and severity.

Audit-Ready Exports

Export reconciliation results directly into month-end close and audit documentation.