Agents
Reconciliation without the month-end scramble
The Reconciliation Agent matches transactions across systems continuously, clears what agrees, and puts a person on only the breaks that need judgement.
What it does
Agrees the numbers so people review the exceptions
Reconciliation is mostly confirming that records which should agree do agree. The agent takes that confirmation off people's desks. It pulls transactions from each side, matches them on the rules you set — exact, tolerance-based or many-to-one — and clears everything that ties out. What remains is a short list of real discrepancies rather than a full ledger to comb through by hand.
Exact and fuzzy matching
Ties records on identifiers, amounts and dates, with tolerances for rounding, timing and fees.
Many-to-one
Resolves batched settlements and split payments against the entries that make them up.
Continuous, not monthly
Runs as data arrives, so breaks surface daily instead of piling up for the close.
Inputs it accepts
What you feed it
Ledger extracts
General ledger and sub-ledger entries from your ERP or accounting system.
Bank statements
Statement files and feeds, including multi-currency and multi-account.
Payment and settlement files
Processor, gateway and settlement reports that need tying back to invoices.
Decisions it makes on its own
What it clears without asking
Inside the confidence and tolerance thresholds you set, the agent acts. It confirms matches, applies the rounding and timing tolerances you have approved, groups batched items against their components, and marks each cleared item with the rule that cleared it. Nothing it does is silent — every automatic decision is logged with the evidence, so a reviewer can confirm the logic at a glance.
Confirms clean matches
Ties out entries that agree within tolerance and marks them cleared.
Applies approved tolerances
Absorbs rounding, timing and fee differences you have signed off on.
Categorises breaks
Labels each discrepancy by likely cause to speed the human review.
What escalates to a human
Where judgement is still required
Unexplained breaks
A discrepancy with no matching entry or one outside tolerance is routed to a named owner with both sides shown side by side and the rule that failed.
Ambiguous matches
When more than one entry could plausibly match, the agent presents the candidates and its ranking rather than guessing.
Systems it connects to
Where it reads and writes
ERPs
Reads ledgers and posts cleared entries and adjustments back to systems such as SAP, Oracle, NetSuite and Tally.
Banks and processors
Ingests statement and settlement feeds from banks, gateways and payment processors.
Warehouses
Pulls transaction history from your warehouse for high-volume matching.
A worked example
A day of settlements
A processor sends one settlement of 84,200 covering 240 card payments, net of fees. The agent splits the settlement against the 240 invoices, absorbs the processor fee within the approved tolerance, and clears 238 of them. Two invoices do not appear in the settlement; the agent flags both as missing with the payment references attached and routes them to the receivables owner. By the time a person looks, the work is two lines, not two hundred and forty.
Questions
Frequently asked
- How are the matching rules set?
- In plain language, per reconciliation. You define what counts as a match, the tolerances allowed and which cases must always be reviewed, and you can adjust them as you learn.
- Does it post entries back to our ERP?
- It can, within the actions you authorise. Many teams start with the agent proposing postings for confirmation, then let it post cleared adjustments once the pattern is trusted.
- What audit trail does it leave?
- Every match and break records the entries involved, the rule applied and the identity that authorised any posting, so the reconciliation is auditable without extra work.
Reconcile a real ledger with us
Send a recent reconciliation and we will run the agent against it, show what it clears automatically and what it escalates, and why.