Settlement Reconciliation Agent
Reconciles each bank settlement run to the transaction ledger.
- Industry
- Banking
- Department
- Finance
- Team
- Accounting Operations
- Kind
- Investigator
- Approver
- Financial Controller
- Code
- FIN-17
It reconciles every settlement the bank receives or pays through the card schemes, the real-time and batch payment systems and ATM networks against the transactions the core banking and card systems recorded for that cycle. It explains each variance as cut-off timing, interchange or scheme fees, rejects and returns, chargebacks or duplicates, proposes the adjusting entries and closes the cycle once every variance is explained or approved. **The problem it solves:** Why a scheme's or payment system's settled amount for a cycle differs from the bank's recorded total: which transactions fall either side of the cut-off, what fees were deducted, which items were rejected, returned or charged back, and how long each variance has been open.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the payments hub: the scheme and payment-system settlement reports and the transactions recorded for each cycle..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Financial Controller with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the core banking system: it posts the approved adjusting entries and closes the settlement cycles. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The settlement manual: settlement cycles and cut-offs for each scheme and payment system, interchange and scheme fee schedules, reject and return codes, chargeback settlement, settlement account mapping and escalation times.
Reads from
the payments hub: the scheme and payment-system settlement reports and the transactions recorded for each cycle.
Acts in
the core banking system: it posts the approved adjusting entries and closes the settlement cycles.
Hands back
A list with one entry per scheme and cycle, each with scheme_or_system, cycle_label, settled_amount_usd, ledger_total_usd, difference, reconciled (true or false), variances (a list with amount_usd, class, evidence and hours_open) and adjusting_entries (a list).
Asks a person when
A fee is 1000 USD or more or off schedule, a variance is classed as a duplicate, chargeback or unknown, a cycle is missing, or a cycle has been open over 24 hours.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Variance tolerance (USD) | 2 | Smaller variances are rounding. |
| Cut-off grace (minutes) | 15 | Transactions this close to a cut-off are tested as timing. |
| Post fees below (USD) | 1000 | Fees matching the schedule below this post without approval. |
| Escalate unreconciled cycles after (hours) | 24 | Older open cycles are escalated. |
| Expected cycles a day | 6 | Fewer means a cycle is missing. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Test every variance against the cut-off first, using a 15-minute grace either side.
- Fees matching the scheme schedule below 1000 USD post; others need approval.
- Classify each variance as cut-off timing, fee, reject or return, chargeback, duplicate, missing cycle or unknown, with evidence.
- A variance under 2 USD is rounding.
- Escalate any cycle open over 24 hours and any day with fewer than 6 cycles.
See the Settlement Reconciliation Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.