Bank
Every bank line, reconciled on the day it lands
The Bank RECONs match every bank statement line, intraday position, fee, and outbound payment confirmation at the line item on the day it posts.
T+0
Bank-to-GL line-item match
Live
Cash position not snapshot
4–6 wks
Demo to live
The structural failure
Bank rec breaks where line items hide behind end-of-day totals
End-of-day sampling. Snapshot cash position. Unvalidated bank fees. Failed payments discovered at month-end. Four named failures appear in every enterprise Bank stack.
Failure 01
End-of-day sampling drift
Bank statement reconciliation runs end-of-day, sampled at the aggregate, with line-item differences hidden in totals. Offsetting errors cancel until they're unrecoverable.
Failure 02
Snapshot cash position
Treasury checks the bank balance once a day, plans against a snapshot. FX exposure shifts intraday; liquidity decisions get made on stale data; opportunities and risks are missed.
Failure 03
Unvalidated bank fees
Bank charges are accepted as-is, never reconciled against contractual fee schedules at the line item. Over-charges and unapproved fees pile up — recovered only by an annual fee audit, if at all.
Failure 04
Failed payments discovered late
pain.002 confirmations arrive but never get reconciled to outgoing payment runs. Returned, failed, or misrouted payments age in suspense; the audit trail of the payment chain is incomplete.
The Bank RECON library
Each RECON covers one of your Bank reconciliation use cases end-to-end. Ingestion, matching, exception workbench, audit trail, write-back. Start with one. Build your Bank Layer over time.
01
From Reconciled to Reconciled with Confidence
Bank rec moves from "as good as scale allows" to "reconciled with confidence."
Every Bank match — statement reconciliation, intraday position, fee validation, payment confirmation — carries a confidence score. Long-tail patterns AI-authored, controllers approve once, exceptions raised on the day they appear. Bank rec stops being a month-end event and becomes a continuous operating condition.
95%+
Automation rate
100%
Line-item coverage
Hours, not weeks
Exception backlog
02
Revenue Recovery
Recover bank fee over-charges and routing losses
Bank charges validated against contractual terms at the line item. Over-charges and unapproved fees recovered systematically. Transaction-routing losses surfaced; short-pays at the bank reconciled against contract.
0.1–0.5%
Bank fees recovered
Continuous
Not annual fee audit
Contract-term
Validation per line
03
Audit-Ready Close
Every bank line logged immutably
Every match, every fee validation, every payment confirmation — logged with rule, timestamp, user, confidence, rationale. The bank evidence chain stays complete; GoBD, IFRS, and SOX become a byproduct.
100%
Line-item coverage
−30–50%
Year-end audit time
GoBD · IFRS · SOX
One trail
04
Real-Time Control of Working Capital
Treasury plans on live cash. The close becomes a confirmation
Intraday positions update continuously, not once a day. Bank-to-GL reconciled at T+0. Failed payments routed to remediation in hours. The cash picture matches reality minute by minute, and FX exposure stays visible.
Live
Intraday cash position
T+0
Bank-to-GL match
Same-day
Failed-payment recovery
Bank Data Sources
Read from the systems your Treasury and finance team already run
Native ingestion across SWIFT and ISO 20022 standards, plus ERP cash books and contractual fee schedules. Configured to your bank panel — not bent into a generic schema.
Sources we read
Bank statements
MT940 · CAMT.053
Intraday feeds
MT942 · CAMT.052
Payment files
pain.001 · pain.002
ERP bank book
GL · sub-ledger
Fee schedules
Contract · pricing
Read-from · write-to
Built for your data
Start with one RECON. Build your Layer over time
Reconciliation is inherently customer-specific. No two Treasury teams have the same bank panel, the same fee schedule, or the same intraday cadence. Every RECON ships with standardised behaviour and is customized for the cases the standard logic doesn't solve.
Live in 4–6 weeks
Read from · write to
The engine writes rules against your Bank data
Where bank-narrative patterns are non-obvious — different SWIFT formats, different reference conventions per bank — the engine drafts the match rule against your statements. Your Treasury and AP teams review and approve it.
Bank-panel-specific fee schedules & tolerance bands
Per bank, per currency, per account, per Flow. The fee model that matches your contracts — not a generic schedule we force on you.
Human-on-the-Loop on every exception
AI accelerates the matching; Treasury and finance teams own the decision. Every override logged with rule, user, timestamp, rationale — exportable for the auditor.
95%+
Automation rate confidence score on every match
Live
Intraday cash positionnot snapshot
0.1–0.5%
Bank fees recovered against contractual terms
−87%
Manual bank-rec work statement + intraday + payment exec
Validate the business case on your data