Recon Pillar

The Truth Emerges Here

Each partner's statement format is configured once, then matched automatically from then on. Your team reviews the breaks — not the thousands of lines that already agreed. The same matching engine reconciles tap-card logs against bank files, or pit-head manifests against port receipts.

Explore Live Demo → Book a Demo

Core Capabilities

Find the Break This Week,
Not Next Quarter.

Month-end reconciliation is where errors are found weeks after they happened, and where a finance team quietly loses several days it will never get back. Recon exists to make that a scheduled job rather than an event.

One Setup Per Partner

Every partner sends a different layout. Map each one to your records once, and every statement from then on is matched automatically — no re-cutting spreadsheets each month.

Multi-Currency Matching

Match across currency pairs with sensible tolerance, so a payment made in one currency and settled in another does not turn into a false exception someone has to investigate.

Exception-First Reporting

You see only what did not match. No scrolling past thousands of correct rows to find the handful that matter — your team spends its time resolving breaks rather than hunting for them.

Multi-Account Reconciliation

Reconcile float, fee and client accounts together in a single pass, so a movement between them is not counted as a break on both sides.

Date & Amount Tolerances

Settlement timing and rounding differ in the real world. Set the tolerance you are comfortable with per partner, and stop treating known timing differences as findings.

ISO 20022 On Roadmap

Direct ISO 20022 bank statement ingestion is on the roadmap, removing the file-conversion step between your bank and your reconciliation.

Across Industries

Match Any Two Records,
Not Just Bank Statements.

Recon is a general matching engine: configure two sources, define the tolerance, and let it find the exceptions. What the sources represent is up to you.

Finance & Payment Rails

Bank and processor statements matched against the ledger automatically, on a schedule — exceptions surfaced, not thousands of agreeing lines.

Transit & Logistics

Tap-card reader logs matched against bank clearing files on the same automated schedule as any other partner statement.

Mining & Resources

Pit-head loading manifests matched against port arrival receipts — the same exception-first workflow, applied to tonnage instead of currency.

Workflow

Three Steps, and Only
One of Them Is Yours.

RECEIVE

Partner statements arrive in whatever format they use

→

MATCH

Matched against your records automatically, on schedule

→

RESOLVE

Your team sees only the breaks, and closes them

Sample Output

See Only What Needs Attention

Partner Ref	Partner Amount	Partner Date	Ledger Match	Ledger Amount	Status
PF-2026-001892	R 1,250.00	2026-06-14	TXN-7893422001	R 1,250.00	✓ MATCHED
PF-2026-001893	R 8,750.50	2026-06-14	TXN-7893422018	R 8,750.50	✓ MATCHED
PF-2026-001894	R 450.00	2026-06-15	—	—	⚠ EXCEPTION
PF-2026-001895	R 12,000.00	2026-06-15	TXN-7893422031	R 12,000.00	✓ MATCHED
PF-2026-001896	R 3,200.00	2026-06-15	TXN-7893422035	R 3,195.50	⚠ AMOUNT DIFF
—	—	—	TXN-7893422040	R 980.00	○ UNMATCHED

Sample output — 3 exceptions out of 6 entries surfaced instantly. Finance team resolution time: 3 items, not 6.

The Truth Emerges Here

Find the Break This Week,Not Next Quarter.

Match Any Two Records,Not Just Bank Statements.

Three Steps, and OnlyOne of Them Is Yours.

See Only What Needs Attention

Find the Break This Week,
Not Next Quarter.

Match Any Two Records,
Not Just Bank Statements.

Three Steps, and Only
One of Them Is Yours.