From customer onboarding to the general ledger, OREBAN gives financial institutions a configurable foundation for running modern banking operations.
Onboard customers, classify them, open the accounts they hold and control what happens to those accounts through their entire life — without moving between disconnected systems.
Define how each product behaves — who qualifies for it, what it charges, how interest accrues and how it posts to the ledger. Products evolve through configuration rather than a development cycle.
Run the full lending cycle against the same customers, accounts and ledger the rest of the institution uses, so lending is never a separate book to reconcile at month end.
Activity across the institution resolves into double-entry postings against your Chart of Accounts, with the controls a finance team needs to close a period with confidence.
Cash handling, approvals and daily processes belong inside the core rather than in manual work happening beside it — with roles and permissions determining who can do what.
Connect payment rails, identity services and other financial infrastructure while keeping the core independent of individual providers, so changing a provider does not mean changing your core.
Migration is treated as an accounting exercise, not a data dump. Balances are mapped, validated and reconciled before the institution begins operating on OREBAN.
Channels sit on top of the API layer. Products, lending and operations run against the same accounting core. Providers connect through the integration layer instead of into the core itself.
Built by your team on OREBAN’s APIs
Authenticated access to the core
Configured to your institution’s rules
Every action resolves to a double-entry posting
Providers connect here, not to the core
Every posting in the core is traceable back to the transaction, account and operator that produced it.
What institutions ask once they start looking at the core itself.
OREBAN is the core. Customers, accounts, products, lending, operations and the general ledger all run inside it, and your channels connect through the API layer. Institutions moving off an existing core do so through the migration and cutover process.
Yours. The product engine is built so interest, fees, limits, eligibility and accounting behaviour are configuration rather than development work. We set the first products up with you during implementation and hand the controls over.
Yes. Branch attribution runs through operations and accounting, so tills, vaults, cash movements and postings carry the branch dimension into financial reporting.
Through the API layer. Mobile banking, internet banking, agent applications and internal tools call the Customers, Accounts, Transactions and Loans APIs, and subscribe to webhooks for core events.
We will take you through the modules that matter for your institution and show you how each one is configured in practice.