Step 1 · Load the two files
Vendor, customer, bank — it is always the same job: two files, match, surface the difference.
▤Ledger Asystem export
| Ref | Posting Date | Amount |
|---|
| A-1004 | 12 Apr | 4,120.00 |
| A-1005 | 14 Apr | 915.50 |
| A-1006 | 15 Apr | 7,330.00 |
▥Ledger Bcounterparty statement
| Doc No. | Date | Value |
|---|
| D-1004 | 2026-04-12 | 4,120.00 |
| D-1005 | 2026-04-14 | 915.50 |
| D-1006 | 2026-04-15 | 7,300.00 |
Same data, different headers — A's Ref is B's Doc No., A's Amount is B's Value. The match breaks here, not on the numbers.
Map headers →
Header mapping — resolve name AND intent, then save it
Profile
Vendor balance recon ▾
Ledger A columnmaps toLedger B column
Ref intent: document id
⇄
Doc No. intent: document id
Posting Date ▾
⇄
Date ▾
Amount ▾
⇄
Value ▾
✓ Save mapping profile
Saved as Vendor balance recon — next run is one click. Map once; the tool remembers the setup.
Run · deterministic match — no model, just the rules you set
⠿ matching on mapped keys · Ref ⇄ Doc No., dates, amounts…
8,394matched
11in A not B
7in B not A
14amount mismatches
79% auto-clearedbefore an analyst touches it
Same input, same output, every time — deterministic. The analyst reviews only the flagged exceptions; the matched lines clear themselves.
Difference report — exceptions only · matched rows cleared
~2 min
5 years of data: ~2 FTE-days → ~2 minutes. Multiply across AP + AR teams — that is capacity returned.