Industries/Fintech & neobanks/Reconciliation Agent
Partner bank FBO reconciliationfintech & neobanks.
Partner bank CAMT.053 tags with end-to-end IDs are matched to customer liability sub-ledgers without exporting to a shared spreadsheet. Ops downloads CAMT.053 and compares to internal ledger CSV.
Scenarios in fintech & neobanks
Partner bank vs product sub-ledger
FBO and operating accounts must tie to customer liability accounts daily. Structured tags match end-to-end payment IDs; breaks grouped by product.
Onboarding velocity vs compliance depth
Head of finance approves write-offs and timing items.
Partner bank FBO reconciliation
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
Works with our BaaS sponsor's file formats?
File layouts are mapped in pilot; we do not assume a single canonical format across sponsors.
API-first?
Yes — webhooks and APIs are common for high-volume fintechs after read-only file prove-out.
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.