Banks
A bank's systems have usually been built up over many years by different teams. The card system keeps its own balances, the financing system keeps its own tables, and at the end of every day accounting has to reconcile all of them. Dara is designed for banks that want fewer of these layers, either by replacing the core or by starting with one specific product, such as a wallet or a credit card, on a core that everything else moves onto later.
Challenges we hear about
- 01
Balances spread across systems
Each subsystem keeps its own balance, and much of the finance department's time goes into reconciling them.
- 02
Every process change is a software project
Adding an approval step or moving an inquiry to a different stage means changing code in several services and waiting for a release slot.
- 03
Long time to market for new products
A new financing scheme or deposit type has to wait for development, because its rules are hard-coded.
- 04
Gaps in the audit trail
The history of changes is scattered across logs, and it is hard to reconstruct who did what, when and on what basis.
How Dara responds
- 01
One Financial Core for every module
No module keeps its own balance. Deposits, cards, wallets and financing read from the Financial Core and post their vouchers there.
- 02
Versioned processes
Steps and approvals are changed in the Process Designer and take effect when a new process version is published. In-flight cases continue on their own version.
- 03
Products built by configuration
Deposit categories are defined with policy switches, and financing products with a credit line and a contract, all without code changes.
- 04
Three-stage vouchers and a full history
Final vouchers cannot be edited, voucher sequence numbers run consecutively, and user actions are recorded for audit.
Recommended solutions
Talk to us about your organization
In a demo session we walk through your organization's scenarios on Dara's demo environment and answer your technical and finance teams' questions.