Industries/Regional banks/Reconciliation Agent
Correspondent and concentration accountsregional banks.
Concentration accounts at multiple correspondents reconcile with the same tolerance math your internal audit already documented for SOX. Multiple analysts work parallel spreadsheets with different matching rules per bank.
Scenarios in regional banks
Many cash accounts, one close deadline
Treasury reconciles correspondent, concentration, and trust accounts while controllers wait for cleared items. One rules engine applies consistent tolerances; exceptions cite bank and GL IDs across entities.
EDD backlogs on complex legal structures
Treasury director approves high-dollar adjustments.
Correspondent and concentration accounts
September operating account activity includes outgoing wire WIRE-88213 to Halvorsen Trade Partners GmbH.
What the agent checks
- Exact amount match within penny tolerance
- Reference token match (wire ID, lockbox, check number)
- Transposition heuristic when |bank − ledger| is divisible by 9
- Deposit in transit when ledger precedes bank within N days
- Duplicate payment detection on reference + amount
- Corporate card aggregation vs individual bank debits
How it works
- 1
Ingest bank and ledger
Parse BAI2, MT940, CAMT.053, or CSV bank files alongside GL cash detail. Normalize signs, dates, and references to a common matching key.
- 2
Auto-match within policy
Pair lines by exact amount, by reference token, and by fuzzy description within date windows you configure. One-to-many and many-to-one sets are scored and ranked.
- 3
Classify exceptions
Flag transpositions when differences divide by nine, deposits in transit when bank date follows ledger date, outstanding checks when only GL shows the payment, and duplicate payments when the same reference hits twice.
- 4
Propose journals
Draft adjusting entries with memo text that quotes bank and ledger amounts. Route to approvers by threshold and account sensitivity.
- 5
Close the period
Publish a reconciliation summary with matched balance, open items, and approved adjustments — ready for controller sign-off.
Questions
Multi-entity deployment?
Pilots scope entities and accounts explicitly; read-only feeds per entity are common in phase one.
Examiner-ready audit trail?
Each agent run logs steps with cited amounts and document references exportable for internal audit.
Does FinanceAI need live API access on day one?
No. Many pilots start with scheduled BAI2/MT940/CAMT.053 files and GL exports over SFTP. Read-only APIs come next once security review passes. The live demo uses the shared Aster Bank synthetic ledger.
What if Stellitron Intelligence is unavailable?
Every decision still runs through deterministic rules: amount matching, transposition checks, UBO percentage math, screening score thresholds, and flux materiality gates. Optional intelligence only improves extraction and narrative.