AI financial close & reconciliation

Get to zero.
Prove how you got there.

TruZero reconciles bank, subledger and intercompany activity continuously, and explains every proposal in cited evidence a reviewer can disagree with line by line. Nothing reaches your ledger without a named person approving it.

Bring your own exception. We will work it live.

Bank to GL · UK Ltd Period 03 · illustrative
Balance per bank statement4,812,660.14
Deposits in transit+ 214,900.00
Outstanding payments− 386,142.55
Cutoff timing — SWIFT T+2− 124,500.00
Adjusted bank balance4,516,917.59
Balance per general ledger4,516,917.59
Unexplained difference0.00
Approved by S. Whitfield, Controller
Approval reference recorded · entry written to your ERP by your team, not by TruZero
4–8
Weeks
Scoped and live. Not a multi-quarter implementation programme.
0
Ledger writes
Adjustments stay proposals. Your ERP remains the system of record.
1
Parallel close
Run beside your existing process before anything is retired.
100%
Approved
No configuration removes the gate. It is not a setting.
The question worth asking

Ask them to explain a break, not a balance.

Every close platform can now draft a variance narrative. None of them explains the exception — why this specific item did not reconcile, in evidence a reviewer can contest and an auditor can test.

A variance narrative is written for the CFO. An exception explanation is written for the auditor. TruZero is built for the second one.

Lineage tells you where a number came from. It does not tell you why the item failed to match, what mechanism produced the difference, or whether this counterparty has done the same thing eleven times before. Those are the facts a preparer would have written by hand, and they are the ones a reviewer is entitled to disagree with.

WIRE-4492 · UK Ltd × Barclays CONFIDENCE HIGH
Root cause
Timing — cutoff difference
Mechanism
GL posted 2 March. Bank cleared 4 March. SWIFT settlement is T+2, so the item straddles the period cutoff. The amounts agree; the dates do not.
Entity-pair history
12 timing variances in 90 days on this entity and bank pair. All 12 resolved the same way and reversed in the following period.
Recommended action
Record as a reconciling item pending settlement, per treasury policy §3.1(b). Approval-ready — awaiting a named approver.
The gate

Agent-prepared, accountant-reviewed is a workflow. It is not a control.

Most AI close tools put a person in the queue. The agent does the work, a reviewer clicks approve, and the system writes. If the reviewer is skipped, the write still lands, because the approval was a step in a process rather than a condition of the operation.

In TruZero the approval is a precondition of the operation itself. Every data-modifying operation carries a human approval reference, stored one-way and chained into a trail that cannot be edited after the fact. There is no configuration that removes it, because it is not a setting. It is the architecture.

And TruZero writes nothing to your ledger at all.

Adjustments stay proposals. Your team posts them in your ERP, under your existing controls, on your existing approval chain. TruZero produces the reconciliation, the explanation and the evidence — it does not reach into the system of record to act on them.

How it works

One close spine, from source file to certified period.

Not a suite of modules you assemble. A single path the work travels, with each stage doing something the next one depends on.

01 Connect Common data model Bank, subledger and GL activity normalised, with lineage back to every source field.
02 Match Match Signals™ Candidate pairs judged on independent kinds of evidence — amount, date treatment, identifiers, counterparty. A proposal in a HIGH, MEDIUM or LOW band, never a raw score.
03 Triage Smart Triage™ · Impact Rank™ Unmatched items classified by likely root cause and grouped, so a systemic issue is worked once. The queue orders on dollar size, time to certification, entity risk and known patterns, and states its own reason.
04 Explain Decision Lens™ Every proposal carries its reasoning as cited evidence — the note a preparer would have written by hand. Not a score breakdown.
05 Investigate Investigation Trail™ Root cause with the mechanism behind it and the entity-pair history: what was examined, what has recurred, what the reviewer challenged. Written as the work happens.
06 Approve & certify Narrative Agent™ The close, variance and flux narrative drafted as work proceeds and adapted to the reader. Every draft is a proposal, edited and approved by a named person.
07 Learn Adaptive Intelligence™ Approvals and rejections return as labelled outcomes. Learning changes what is proposed, never who must approve.
Continuously Not a month-end batch The spine runs against activity as it arrives. The close stops being a five-day event and becomes a position you already hold on day one.
What it connects to

Your systems, your formats, your close calendar.

ERP
Native connectors for Oracle Fusion Cloud ERP and NetSuite. SAP and Workday through the connector framework.
Bank formats
BAI2, CAMT.053 and MT940, parsed with type codes read by range rather than whitelist, funds-type-aware field handling, and currency-implied decimal scaling. Trailer control totals are the completeness check.
Files
CSV and XLSX exports, with column mapping that survives a changed report layout.
Scope
Bank to GL, subledger to GL, and intercompany with FX, counterparty pairing, settlement, netting and dispute tracking.
Certification
Approvals roll up item to reconciliation to account to entity to period, with an evidence pack an auditor can re-perform.
Who it is built for

Controllers who carry the certification

You own the close calendar and you sign. The exception queue is where your week goes, and the evidence pack is what you defend.

Multi-entity finance organisations

More than one ERP, more than one bank, intercompany in more than one currency, and a consolidation that has to tie.

SOX, IPO-track and first-audit teams

Where the question is not whether the software matched it, but who approved it, on what evidence, and whether you can show it again.

Working session

Bring your own exception.

Send us a break your team argued about last close — a timing difference, an intercompany mismatch, a payment that would not clear. We will work it live and you can decide whether the explanation is one you would put in front of your auditor.

Direct: amitchopra@truzero.ai
No trial signup, no sandbox link. Sessions are run by the people who built the platform.