Field report

Production recon,
West Africa.

How a pan-African banking group's treasury moved nostro, GL and mobile-money reconciliation onto Kilter — on their own infrastructure.

75–85%
Auto-matched at Tier 1
strict ref + amount + date
4
Currencies reconciled
GHS · USD · EUR · GBP
30+
Nostro & wallet GLs
two-sided and one-sided
100%
Decisions audit-logged
hash-chained trail

Figures observed on pilot and production data; match rates vary with data quality and tier policy. Customer name withheld — reference calls available under NDA.

The bank

A correspondent-banking treasury in West Africa

The treasury operations team of a pan-African banking group's West African affiliate reconciles correspondent nostro accounts across four currencies, a busy mobile-money bridge GL, and card-scheme settlements — every business day.

Before Kilter, that meant spreadsheets: SWIFT statements exported on one side, core-banking GL extracts on the other, and analysts eyeballing thousands of lines for matches. Breaks were tracked in the same workbooks that created them, and month-end sign-off rested on whoever remembered the history.

The deployment

Self-hosted, inside the bank's own perimeter

Kilter installed on a single VM inside the bank's network. No data leaves the building — a hard requirement, and the reason the bank could approve the deployment without a cross-border data-transfer review.

Statements arrive as the correspondent sends them (MT940/950 and ISO 20022 camt); GL extracts come straight from the core banking system. The scanner picks both up, pairs them into sessions, and the matching engine proposes matches across confidence tiers. Strict Tier-1 matches (reference + amount + date) auto-confirm; everything else queues for a human decision — a policy the bank's ops team set, and Kilter enforces.

The results

From eyeballing lines to reviewing exceptions

On production data, 75–85% of statement lines auto-match at Tier 1 — hands-off. Analysts now spend their day on the exceptions: the aged break, the missing leg, the timing difference that needs a comment for audit. Open items roll forward across sessions until they clear, so nothing vanishes between Friday and Monday.

The mobile-money bridge GL — tens of thousands of debit/credit legs pairing across days — runs as a one-sided reconciliation with carry-forward matching, something the spreadsheet process simply could not do.

What the auditors got

Every decision on the record

Every confirm, reject, write-off and force-accept is logged with who, when, and why — in a tamper-evident, hash-chained audit trail. Month-end closes with a signed reconciliation certificate per account, generated from the data rather than assembled by hand.

Mandatory two-factor login, role separation between ops, audit and admin, and encrypted credentials came as defaults, not add-ons — which shortened the bank's own IT security review.

See it on your own files.

Send a SWIFT statement or GL extract and we'll show you your own match rate — before you commit to anything.

Book a 30-minute demo