Load
Month-end is a different system.
Settlement, statements and disbursement land together, against the same connection pool as the customer-facing API. The architecture that is fine for 29 days fails on the 30th, predictably, every month.
Industry — regulated fintech
The ledger is the product. Everything else is a view of it.
Wallets, lending books and payment rails fail in the same place: a ledger that was modelled for the first year and never re-modelled for the tenth. We rebuild that core while the business keeps running on it.
Softrear builds and modernises regulated financial systems — wallets, ledgers, settlement and reporting — using immutable append-only models, strangler migrations with reversible cutovers, and audit trails built to satisfy a regulator rather than a demo.
48h
is when month-end breaks most wallets
7 yr
audit retention most regulators expect
4 min
the longest window operations will accept
1
reconciliation break is one too many
What actually breaks
Audit
Mutable rows and an audit table nobody trusts.
If the ledger can be updated, the audit trail is a story about the data rather than the data. Append-only is not a preference here; it is the only model that survives an examination.
Migration
The rewrite everybody quotes and nobody survives.
A two-year rewrite is a two-year period with no regulatory headroom. Incremental extraction behind a gateway gets you a working system every fortnight instead of a promise.
Reconciliation
Breaks found by a human, at the end of the month.
By the time a spreadsheet finds the break, the counterparty has moved on. Continuous reconciliation with alerting turns a month-end investigation into a same-day fix.
What we build
From the sensor to the invoice.
Append-only ledger design
Immutable entries, derived balances, and aseven-year archive path that does not slow the hot table down.
Settlement & reconciliation
Continuous matching with exception queues, so breaks surface the same day and land on someone’s desk with context.
Regulatory reporting
Generated from the ledger, reproducible for any historical date, and explainable line by line.
Strangler migration
A gateway in front of the legacy core, one bounded context extracted at a time, every cutover rollback-tested.
Customer apps
Wallet, onboarding and KYC flows built by the same team that owns the API behind them.
Security & access control
Least privilege, key management, mTLS between services, and an access log that answers who saw what.
Case study — A regulated e-money and wallet provider
A ledger split out from under a live wallet, without a maintenance window.
A regulated wallet whose month-end load had outgrown a single deployable. We split the ledger, rebuilt the app, and cut over without a maintenance window.
Read the build →- Duration
- 14 weeks + run
- Team
- 2 senior · 3 mid · 1 SRE
- Stack
- Flutter · Spring Boot · Postgres · AWS
- Engagement
- Dedicated team
Start with a ledger and load review.
Two weeks, fixed scope. We model your peak, read the ledger schema, and hand you a written migration path with the risks named — whether or not you build it with us.
Book the reviewStandards we work to
- PCI DSS scope containment
- Strong customer authentication where applicable
- Reporting and retention requirements set by your regulator
Tell us what’s stuck.
A senior engineer reads every one of these. If we’re not the right fit we’ll say so, and point you at someone who is.
Start the conversation
No spam, no drip sequence. A senior engineer replies within one business day.