Packs
Core, domain packs, country packs, your company layer
Four layers, resolved in order. A lower layer can change only what the layer above exposes, and every core or pack release is tested against every company layer before it ships.
CoreIdentical for every customer in every country. Changed only by SMH releases.
Domain packsReconciliation families, records, exception catalogues, reports and KPIs of an industry. You license one or more.
Country packRails, schemes, switches, file templates, regulator rules and returns, residency, calendars, currency, languages, tax and e-invoicing.
Company layerYour participant codes, GL mappings, thresholds, delegation of authority, approval policies, own rules, reports and branding.
Why the layering pays
- Time to value: about 16 weeks to production when your country and domain packs exist.
- Regulatory change at scale: a new circular, scheme rule or tax format becomes one pack version, shipped with its own test evidence.
- Safe upgrades: your settings live in the company layer, never in core code, so upgrades do not overwrite them.
- Groups: entities in several countries on one platform, with a consolidated view from R3.
- Provenance: every setting on screen shows which layer set it, and each pack lists the official sources it implements.
Country packs
Local rails, local rules, local hosting.
Country packs carry each market's switches, schemes, regulator rules, calendars and currencies, so a bank in Karachi, Riyadh or Dhaka starts with its own world already configured. First packs: Pakistan, Saudi Arabia, Bangladesh (R1, Q1 2027); 28 countries by Q1 2029.
- Raast
- 1LINK
- PayPak
- mada
- sarie
- NPSB
- Aani
- Jaywan
- InstaPay
- Meeza
- Visa
- Mastercard
See it with your own files.
Book a walkthrough: we load sample files from two of your rails, run them through Recondora and show you every match, break and approval.