NSK AI
Solutions · Financial services
Plate I
NSK·SOL·01

Reconciliation

Two ledgers that ought to agree, and the small number of lines that do not.

Fig. 1 — The floor of the London Stock Exchange, c. 1910–1920. Library of Congress, no known restrictions.
Plate I
NSK·SOL·01
The problem

A bank closes the day by hand. Statements arrive in four formats and the core ledger in a fifth, and the differences between them are found by eye.

Most lines pair without argument. The value sits in the handful that do not, and those are the ones the team runs out of time for.

Drag the rule across the day.

Drag the rule across the day. Lines pair as it passes; what remains is the exception list.

Date
Reference
Statement
Ledger
State
04 AUG
40182
128,400.00
128,400.00
 
04 AUG
40183
96,220.15
96,220.15
 
04 AUG
40184
41,000.00
41,000.00
 
04 AUG
40185
7,318.40
7,318.40
 
04 AUG
40186
512,900.00
512,900.00
 
04 AUG
40187
23,004.65
23,004.65
 
04 AUG
40188
88,150.00
88,150.00
 
04 AUG
40189
64,720.00
64,270.00
 
04 AUG
40190
9,940.00
 
Paired 0
Exceptions 0
Remaining 9
Where it applies
Three places the same pairing engine is used.
01
The daily close

Statements against the core ledger, pairing first and exceptions after, so the close ends at a known list rather than a deadline.

02
Payments exceptions

Chargebacks, duplicates and failed settlements grouped by cause, with the rule that grouped them on the record.

03
Reporting packs

Regulatory and management figures assembled from source rows, each number traceable back to the entries behind it.

Fig. 2 — The floor of the New York Stock Exchange, shot with a camera hidden in the photographer’s sleeve. Library of Congress, no known restrictions.
A worked example
Lines a day
41,800
Paired without review
96.2%
Exceptions surfaced
1,580
Median time to close
1h 10m, from 6h 40m
Value held in suspense
−38%
Figures from one deployment, quoted with the client’s permission. Yours will differ.
Notes on compliance
01

Central-bank cybersecurity frameworks in each market, with PCI DSS scope held to the tokenised path.

02

Every pairing carries the rule that produced it and the operator who accepted it.

03

Records retained seven years; model output is advisory until an operator signs.

Deployment
Week 1–2
Read-only connection to statements and the core ledger
Week 3–6
Pairing rules learned from a year of resolved breaks
Week 7–8
Shadow running beside the manual close
Week 9
Operators accept or reject, each pairing explained
The other plates

Bring us the case you have not been able to close.

We will tell you which part of it is a model problem and which part is not.