Finance &
Infrastructure
Financial infrastructure is the plumbing most organisations underestimate — until it fails at scale. Ledger design, reconciliation architecture, settlement mechanics, and FX operations are not back-office concerns: they are the foundations on which regulated financial operations stand.
Ledger Systems
A well-designed ledger system is the foundation of any financial services business. At scale, the gap between ledgers designed for transaction volume and ledgers designed for auditability, multi-currency operations, and regulatory reporting becomes painfully apparent.
Subite's approach to ledger systems starts with the accounting model — double-entry, multi-currency, with clear separation of internal and external positions — and works forward into the technical implementation choices that will either enable or constrain future growth.
- Ledger architecture design — double-entry, multi-currency, event-sourced
- Chart of accounts design for payment and e-money businesses
- Internal position and float management design
- Real-time balance calculation and exposure monitoring
- Regulatory capital allocation model design
- Ledger technology selection — build vs buy analysis
- Audit trail and regulatory reporting design
Reconciliation
Automated reconciliation is less a technology problem than a data discipline problem. Matching positions across card schemes, banking partners, processors, and internal systems requires rigorous data model design before any automation is meaningful.
Breaks happen at interfaces — between systems, between organisations, between time zones. Effective reconciliation design anticipates where breaks will occur and builds structured resolution workflows before they become operational fires.
- Reconciliation architecture design — multi-counterparty, multi-currency
- Scheme file processing and position matching framework
- Break management workflow design and escalation paths
- Nostro and vostro position management design
- Exception handling and root cause analysis framework
- Reconciliation tool selection and vendor advisory
- SLA design for settlement and reconciliation operations
Settlement
Settlement design choices — gross versus net, deferred versus real-time, single currency versus multi — have significant implications for liquidity requirements, counterparty risk, and operational complexity. Getting these decisions right at platform inception avoids expensive restructuring later.
For payment businesses operating across multiple settlement counterparties and jurisdictions, the settlement architecture is often the most consequential infrastructure decision in the platform.
- Settlement model design — gross vs net, deferred vs real-time
- Multi-party settlement architecture for platforms and marketplaces
- Settlement file processing and format design (ISO 20022, proprietary)
- Funding and pre-funding liquidity management design
- Intraday liquidity monitoring framework
- Settlement counterparty risk assessment
- Cutover and contingency planning for settlement changes
Treasury Operations
For payment companies and e-money institutions, treasury operations span safeguarding obligations, intraday liquidity management, and FX exposure. These are regulated functions requiring both technical infrastructure and robust governance frameworks.
EMIs and PIs operating under PSD2 carry specific safeguarding obligations that shape treasury structure. Getting this right from the start — both operationally and in terms of regulatory documentation — avoids costly remediation when regulators look closely.
- Safeguarding framework design — EMI/PI regulatory obligations
- Segregated account structure and bank relationship management
- FX treasury policy and execution design
- Cash position forecasting and liquidity management
- Intraday FX exposure monitoring framework
- Treasury technology selection and implementation advisory
- Regulatory reporting design for safeguarding and treasury