Stratum
A daily close that finishes at four
Client identities and brand marks are anonymised. Names, logos and interfaces shown are not real companies or real projects.
- Sector
- Payments & settlement
- Location
- Manama, Bahrain
- Year
- 2025
- Kickoff to production
- 21 weeks
Clearing, settlement and exception handling for a regional processor that closed its books at midnight and guessed until then.
The processor settled 180,000 transactions a day across four schemes, and the day's true position only existed after an overnight batch. Breaks were found by a clerk the next morning, and one scheme file arriving late pushed the entire close into the evening.
Position, continuously
Presentments, refunds and chargebacks post to a running position through the day, so the number on the wall at three o'clock is the number the books close on.
Exceptions with a next action
Every break is classified (timing, amount, missing leg) and routed with the matching evidence attached, so a clerk decides instead of investigating.
Late files don't move the close
Each scheme file is ingested with its own state, so a delayed partner delays one reconciliation rather than the whole cycle.
The close moved from midnight to mid-afternoon and reconciliation headcount shrank, without a single settled position being restated.
What changed
- Daily close
- Afternoon
- Transactions settled daily
- 182k
- Reconciliation
- Exception-first
- Java
- Postgres
- Kafka
- Airflow
- Grafana
Tell us what's slowing you down.
Fifteen questions, one screen at a time, and a verdict at the end. No call needed to get it.