Skip to main content

Bank reconciliation agent

A zero difference can still hide a bad match.

A bank reconciliation agent can compare authorized statement lines with cash-book records and explain candidate matches or unresolved differences. Exact identity, amount, currency and control-total rules come before model ranking. Qualified owners review exceptions and approve adjustments. A useful reconciliation shows how adjusted balances agree while keeping every item traceable, rather than relying on a zero difference alone.

Reconciliation job boundary

Propose the correspondence. Preserve both records.

The agent can remove repeated comparison work, but it cannot make an incomplete feed complete or turn balance agreement into accounting proof. Four boundaries keep each proposal tied to bank evidence, the book and accountable resolution.

01

Bank source record

Register the authorized institution, entity and account; statement identity and period; opening and closing balances; immutable line reference; transaction, value and settlement dates; signed amount and currency; description, counterparty and status; original artifact and every correction without overwriting what the bank supplied.

Required evidence: Access authority, institution and account token, legal entity, statement reference and digest, period and cutoff, opening and closing balance, line and provider event identifiers, original text and artifact, signed amount and currency, dates, status, sequence, correction, ingestion record and provenance.

02

Internal candidate population

Assemble only records eligible for the same entity, account, currency and period, including cash-book entries, receipts, payments, deposits, transfers, fees, interest, refunds, reversals and approved journals, while preserving original source, posting state, relationships and prior reconciliation status.

Required evidence: Book and ledger, account and currency, entry and journal identifiers, transaction and posting dates, amount and sign, counterparty and reference, payment or receipt records, source documents, approval and posting receipts, transfer pair, reversal chain, prior match, lock state and correction history.

03

Explainable match set

Apply exact identifiers and control totals first, then approved amount, date, reference and grouping rules; use bounded ranking only for ambiguous candidates; present every one-to-one, one-to-many or many-to-one member, rule, score, tolerance, conflict, alternative and missing item without silently consuming a record twice.

Required evidence: Candidate-set version, exact and fuzzy rules invoked, model or retrieval version where used, member identifiers, aggregate arithmetic, date windows, currency treatment, reference evidence, prior-use check, confidence or rank, alternatives, counterevidence, abstention reason and reviewer-ready explanation.

04

Resolution and receipt

Route unmatched, partial, stale, duplicate and conflicting items to qualified review; record confirmed or rejected matches and timing classifications; require separate authority for fees, corrections, write-offs or other book adjustments; capture posting receipts; recompute adjusted balances; and retain certification, reopening and visible correction.

Required evidence: Owner and qualification, materiality and age, investigation sources, disposition and reason, approved match members, timing-item status, adjustment proposal and journal, approval and segregation evidence, target receipt, adjusted bank and book schedules, difference, certification, close lock, reopen, correction and retained package.

Statement-to-close path

Reconcile the population, not just the total.

A credible path proves which statement and book populations were compared, which differences are timing items, which require correction and who accepted the final schedule. The model may rank candidates inside that path, never replace it.

  1. 01

    Define account and cutoff

    Confirm legal entity, bank and book accounts, currency, statement identity and period, opening and closing balances, settlement and posting cutoff, expected feeds, materiality, tolerances, owners, approvals, close state and completeness controls.

    Owner
    Controller or authorized reconciliation owner
    Evidence
    Account mandate, entity and book mapping, statement digest, period, balances, source inventory, sequence and control totals, cutoff policy, tolerance version, reviewer and certifier assignments, segregation, lock and exception service levels.
  2. 02

    Preserve both populations

    Ingest original bank artifacts and internal records independently, retain values and lineage, validate entity, account, currency, sequence, balances and totals, detect duplicates and gaps, and hold partial or contradictory feeds before matching.

    Owner
    Finance data and control owners
    Evidence
    Original artifacts and payloads, access record, digests, ingestion receipts, line and entry counts, opening-plus-movement-to-closing calculations, missing ranges, duplicates, pending or settled status, normalization log, book extracts and corrections.
  3. 03

    Match exact before ranked

    Resolve unique provider and payment references, transfer pairs and exact approved combinations first; then rank permitted candidates within explicit date, amount, currency and grouping limits; prevent double use; expose alternatives and abstain when evidence is insufficient.

    Owner
    Deterministic matching service with bounded model assistance
    Evidence
    Rule order and versions, exact identifiers, candidate population and members, decimal arithmetic, windows and tolerances, model and retrieval versions, ranks, conflicts, prior-use guard, evaluation segment, abstention and queue receipt.
  4. 04

    Investigate and authorize

    Have qualified owners inspect original bank and business records, confirm or reject candidate sets, classify genuine timing items, request missing evidence, resolve duplicates and bank or book errors, and separately approve any ledger adjustment under current policy.

    Owner
    Qualified preparer and independent reviewer
    Evidence
    Full review packet, reviewer identity and role, investigation notes, external confirmation where required, decision and reason, timing classification, exception owner and due date, adjustment and supporting journal, approval, rejection and escalation.
  5. 05

    Recompute, certify, and observe

    Capture external posting receipts, recompute adjusted bank and book balances from retained items, prove any difference, age outstanding items, certify under named authority, lock the period without hiding unresolved work, and carry corrections and realized clearing into the next review.

    Owner
    Controller, close owner, and accountable system owner
    Evidence
    Posting receipt, final match graph, bank and book reconciliation schedules, outstanding-item rollforward, adjusted balances and difference, unresolved register, certification, close record, next-period clearing, reopen and correction history, access review, cost and outcome review.

Authority model

Let software compare. Keep financial authority named.

Reconciliation combines exact arithmetic, incomplete external descriptions and consequential accounting decisions. The system is safer when those responsibilities are separated rather than hidden behind one confidence score.

01

Deterministic record controls

Code should own exact account, entity, period, currency, sign, balance, sequence, duplicate, identifier, combination, tolerance, record-use, approval, posting-receipt and adjusted-balance checks.

  • Statement and book population counts, opening-plus-movement-to-closing calculations, stable identifiers, digests, missing sequences, duplicate payloads, settlement status and cutoff validation
  • Exact reference, amount and currency equality, approved date windows, one-to-one and grouped arithmetic, transfer-pair rules, prior-use prevention, tolerance application and deterministic tie handling
  • Role, segregation, threshold, period lock, idempotency, target receipt, adjusted bank and book schedules, zero-difference calculation, outstanding-item age and control-total alerts
  • Version binding, immutable events, visible supersession, export completeness, access expiry, restore reconciliation and evidence-retention checks
02

Bounded matching assistance

A model may extract references, normalize candidate text and rank plausible correspondences inside an approved population. It cannot create a missing bank line, infer business purpose as fact, decide accounting treatment, approve an adjustment or certify the account.

  • Reference, counterparty and memo extraction candidates with exact source spans, artifact digest, field confidence, validation, missing-page and unreadable-content states
  • Candidate ranking for permitted date, amount and textual ambiguity with all members, comparable historical decisions, changed conditions, alternatives, counterevidence and uncertainty
  • Possible one-to-many or many-to-one grouping suggestions whose aggregate arithmetic is deterministic and whose members remain individually inspectable and unused elsewhere
  • Exception summaries and evidence requests that cannot relabel a timing item, suppress an old difference, write a journal, alter bank evidence, learn from overrides without disposition or present likelihood as approval
03

Qualified financial authority

Authorized finance and accounting owners determine the reconciliation policy, investigate discrepancies, confirm matches, approve treatment and adjustments, post or reject journals, certify balances, reopen periods and answer audit, tax and control questions.

  • Entity and account ownership, cutoff, materiality, tolerance, aging, cash classification, foreign-currency, transfer, net-settlement, fee, interest, return, chargeback and stale-item policy
  • Source sufficiency, business purpose, transaction validity, duplicate or omission conclusion, bank-error communication, timing classification, collectability, write-off and other accounting treatment
  • Match confirmation or rejection, exception assignment, journal preparation and approval, posting, reversal, reconciliation certification, close, reopen, correction and external reporting
  • Professional judgment, control design, audit and tax response, legal hold where applicable, access review, incident response, expansion, rollback, provider change and retirement

Reconciliation-system components

Build a match graph that can be reopened.

Statements, cash books, payment systems, document stores and ledgers hold different evidence. Four components preserve their independence while making each correspondence and unresolved difference reviewable.

01

Bank-source registry

Preserve access authority, institution, entity, account token, statement and period, balances, original artifact and payload, immutable line, identifiers, amount, currency, dates, description, status, sequence, duplicate, gap, correction and provenance.

Operating contract: Imported is not complete, pending is not settled, normalized is not original, a bank description is not business purpose, an available balance is not a ledger balance, and correction never erases the prior source.

02

Internal-record registry

Resolve book and bank-account mapping; preserve cash entries, receipts, payments, transfers, refunds, fees, interest, journals and documents; track approval, posting, reversal, prior reconciliation, period lock and correction without manufacturing missing evidence.

Operating contract: Posted is not cleared, balanced is not valid, a payment record is not a bank settlement, similar counterparties are not identical, an internal reference is not external confirmation, and a locked period is not error-free.

03

Match and exception engine

Run exact controls first; build versioned candidate sets; calculate grouped totals exactly; apply permitted ranking; prevent reused members; retain scores, rules, alternatives and counterevidence; and queue unmatched, partial, duplicate, stale and conflicting items.

Operating contract: Equal is not same event, close in time is not causal, highest rank is not approval, aggregate agreement is not member completeness, unmatched is not automatically an error, and an exception cannot disappear without disposition.

04

Resolution and close ledger

Assign qualified review, capture investigations and match decisions, separate adjustment approval, post through scoped and idempotent tools, retain receipts, recompute schedules, age outstanding items, certify, reopen, correct, export and evaluate.

Operating contract: Viewed is not reviewed, confirmed match is not adjustment authority, successful request is not posted journal, zero difference is not complete proof, certified is not immutable truth, and close never removes unresolved ownership.

Delivery path

Prove one account and period before widening access.

A matcher can look excellent when most lines have unique references while failing on net settlements, grouped deposits, reversals and old outstanding items. Begin with a bounded period where every member and difference can be reviewed.

  1. 01

    Observe one reconciliation

    Follow statement acquisition, completeness checks, internal extracts, manual and automated matching, investigation, adjustment, posting, balance proof, review, close, next-period clearing, correction, staff effort, provider cost, incidents and known harm.

  2. 02

    Define the match contract

    Name account, statement, period, bank line, book entry, member set, cutoff, status, exact rule, tolerance, candidate, match, timing item, exception, adjustment, reviewer, receipt, certification, correction and outcome fields and authorities.

  3. 03

    Run a shadow reconciliation

    Replay representative exact, grouped, split, transfer, pending, fee, interest, refund, reversal, returned, duplicate, foreign-currency, stale, missing, locked-period and adversarial cases without changing the book, then compare with qualified decisions.

  4. 04

    Release a controlled period

    Limit entity, account, currency, period, sources, rules and tools; require review for every non-exact match and every adjustment; verify access, idempotency, target receipts, manual bypass, queue ownership, outage recovery and stop authority.

  5. 05

    Review the next close

    Compare population completeness, match coverage and precision by segment, exception and stale-item age, adjustment quality, review effort, schedule integrity, close evidence, next-period clearing, security, staff impact, cost and harm before expansion or retirement.

Reconciliation safeguards

Six controls before a match reaches the schedule.

The strongest controls prevent cross-account matches, missing statement lines, double-used book entries, opaque tolerance, unauthorized adjustments and apparently balanced but unsupported schedules.

Entity, account, period, currency, and decimals
Use stable identifiers and exact decimals; bind bank and book accounts to one legal entity; preserve sign and original currency; separate transaction, value, settlement and posting dates; enforce cutoff and period locks; and reject cross-account or unexplained currency matches.
Source completeness and provenance
Retain original statements, events, extracts and digests; prove opening plus movement to closing totals; record access and ingestion; expose missing sequences, partial periods, duplicates and corrections; and never replace bank or book evidence with generated text.
Match hierarchy and versioning
Order exact identifiers before combinations and ranking; version date windows, tolerances, grouping, text rules, models, retrieval and evaluation; calculate every group deterministically; prevent member reuse; surface ties and alternatives; and bind decisions to effective versions.
Permission, segregation, and commit
Separate ingest, propose, confirm, investigate, adjust, approve, post, reconcile, certify, reopen and administer capabilities; scope credentials to entity, account and tool; enforce materiality and conflicts; use idempotency and receipts; log denials; review and revoke access.
Exceptions, age, and visible correction
Own unmatched, partial, duplicate, stale, returned, reversed, missing and conflicting items; distinguish timing from error; set age and escalation rules; require support for release or adjustment; roll items forward visibly; and preserve rejection, reopen and correction history.
Security, retention, and recovery
Minimize and encrypt financial and personal data, isolate tenants and environments, protect secrets, sanitize hostile artifacts, monitor access and tool use, back up and test restore, reconcile after replay, retain by qualified policy, support complete export and retire providers safely.

Outcome proof

Measure resolved evidence, not matches generated.

A system can maximize match count by loosening windows, hiding alternatives or consuming the same internal record twice. Proof follows both populations through candidate, review, adjustment, schedule, certification, clearing and correction.

Baseline

  • Statement lines and book records by entity, account, period, currency, amount, date, status, source, reference quality, one-to-one or grouped pattern, exact or ranked method, exception, age, adjustment, reviewer, certification, correction and known outcome
  • Current evidence by statement and digest, opening and closing balance, source counts and totals, internal extract and journal, match-rule and model version, candidate members, decision, adjustment approval, target receipt, schedule, close and next-period clearing
  • Manual statement retrieval, population proof, search, matching, grouping, investigation, evidence request, review, adjustment, posting, schedule preparation, certification, follow-up, correction and audit-support effort, queue age, interruption, provider fees and operating cost
  • Wrong entity, account, period, currency, amount, member, match, duplicate use, missing line, unsupported release, unauthorized adjustment, unreconciled difference, stale item, hidden correction, exposed data, failed recovery, control override and harm

Outcome evidence

  • More eligible lines reach review with intact bank and book evidence, deterministic controls, inspectable candidates, visible alternatives and owned exceptions while qualified owners retain match, adjustment and certification authority
  • Fewer cross-account, duplicate-use, unsupported, stale-rule or opaque-tolerance matches enter the schedule, and unmatched or partial items remain visible by cause, age, owner, next action and later clearing
  • Qualified reviewers spend less avoidable time assembling and re-entering evidence while retaining clear confirm, reject, split, group, investigate, adjust, hold, certify, reopen and correct authority, measured by difficult-case segment
  • Comparable periods expose population completeness, exact and ranked coverage, candidate precision, abstention, reviewer edit, exception age, adjustment and posting failures, adjusted-balance integrity, close burden, incidents, effort, cost and harm without assuming a financial result

Guardrails

  • Entity, account, statement, line, book entry, document, period, currency, rule, candidate, reviewer, journal or receipt is misbound; original evidence is lost; values are rounded or overwritten; or financial data crosses tenant, role or purpose boundaries
  • A partial feed appears complete, one record is consumed twice, aggregate totals hide wrong members, loose tolerances inflate coverage, stale descriptions drive matches, pending lines are treated as settled, transfer pairs are incomplete or a hostile artifact alters instructions
  • The model confirms matches, releases stale items, determines accounting treatment, approves or posts adjustments, certifies the account or learns silently from reviewer overrides; reviewers lack complete evidence, qualification or independent authority; or staff cannot stop and correct it
  • Outage loses candidates or receipts, replay duplicates decisions, restore changes schedules, unmatched items age unseen, period lock blocks necessary correction, evidence cannot be exported, access survives role change, metrics omit hard cases or expansion precedes a proven close

Agent fit

Use this pattern when one account can be proved line by line.

Good reason to begin

  • The organization can bound one legal entity, bank and book account, currency and statement period and name the source, cutoff, matching, materiality, adjustment, review, segregation, certification, close, correction, baseline, cost, harm and stop owners.
  • Original statements and internal records retain stable identifiers, values and provenance; opening and closing balances and movement totals can be checked; the ledger supports scoped and idempotent posting with receipts; and reviewers can inspect every match member.
  • Representative exact, grouped, transfer, pending, fee, refund, reversal, returned, foreign-currency, duplicate, missing and stale cases plus qualified decisions and later clearing exist for shadow evaluation by segment.
  • The team can abstain, hold queues, revoke credentials, preserve manual reconciliation, investigate externally where required, reopen and correct visibly, reconcile after outages, export evidence, roll back rules and retire the agent safely.

Resolve before beginning

  • Legal entity, account ownership, bank-to-book mapping, statement authority, cutoff, currency treatment, matching rule, materiality, adjustment policy, reviewer qualification, segregation, reconciliation certification, close, retention or correction responsibility is unclear or disputed.
  • Statements or book records lack stable identifiers or original values, feeds cannot prove completeness, balances cannot be reconstructed, grouped members cannot be inspected, credentials cannot be scoped, posting lacks idempotency or receipts, or unresolved items have no owner.
  • The desired first step permits generated bank records, free-form cross-account search, hidden tolerance, direct match confirmation, automatic journal posting, silent stale-item release, autonomous certification or override learning and omits current sources, deterministic controls and qualified review.
  • The business case depends on unverified perfect matching, fraud detection, audit readiness, compliance, fully autonomous close, reduced headcount, exact savings, implementation time, loss prevention, cash improvement or financial outcome.

Source basis

Sources behind the control model.

  • 01

    United States Internal Revenue Service

    Publication 583, Starting a Business and Keeping Records

    The current December 2024 publication explains US federal small-business recordkeeping and gives a checking-account reconciliation process that compares deposits and checks, identifies charges and outstanding items, prepares adjusted bank and book balances and corrects errors. It is US-specific guidance, not an automated matching standard, accounting-policy decision, fraud determination, audit opinion or rule for another entity or jurisdiction.

  • 02

    IFRS Foundation

    Conceptual Framework for Financial Reporting

    Sets fundamental concepts for useful financial information, reporting-entity boundaries, recognition, derecognition, measurement, presentation and disclosure. It is not a bank-reconciliation algorithm, cash-account mapping, matching tolerance, adjustment approval or substitute for applicable IFRS Standards, another reporting framework, entity policy or qualified judgment.

  • 03

    NIST AI Resource Center

    Artificial Intelligence Risk Management Framework

    Provides voluntary Govern, Map, Measure and Manage functions for AI risk. NIST states that AI RMF 1.0 is being updated and a revised version is in progress. It does not certify a matcher, define banking or accounting policy, authorize access or adjustments, prove accuracy or satisfy legal, audit, tax, privacy, security or financial-control requirements.

  • 04

    National Cybersecurity Center of Excellence

    Software and AI Agent Identity and Authorization concept paper

    Frames identity, authorization, auditing and non-repudiation questions for a potential NCCoE project involving software and AI agents. Its public-comment period closed on 2 April 2026 and it remains an initial public draft, not a final standard. It supports examining scoped financial-tool identity but does not define segregation, validate a bank connection or prove secure operation.

[ WORKFLOW / SYSTEMS AUDIT ]
THE FIRST ENGAGEMENT

Start with one real workflow

A Systems Audit is the usual starting point. If the opportunity is already clear, we can move directly into a focused build.

Show Us the WorkflowStart with the free automation readiness checklist

OBSERVEQUANTIFYDECIDEBUILD

Continue with the work

Choose the next useful path.

Stay with the operating question. The technology can wait until the work is clear.

01

Explore governed agent patterns

Compare reconciliation with bookkeeping, invoice, accounting-intelligence and wider operational patterns before choosing an exact task boundary.

Open path02

Prepare source-linked bookkeeping records

Trace transaction candidates through evidence, approved policy, qualified review, controlled posting and source-to-ledger reconciliation.

Open path03

Control finance and accounting flow

Connect immutable source evidence, exact calculations, bounded extraction, qualified approval, controlled commit, reconciliation and close support across the wider operation.

Open path04

Preserve professional financial authority

Connect engagement and entity scope, source records, policy, qualified preparation and review, controlled commit, reconciliation, close and client correction.

Open path