Core Banking & Qard al-Hasan Fund
Dara's Financial Core is where money is recorded. Deposits, financing, cards, wallets and treasury do not keep balances of their own. Every operation with a financial effect becomes a voucher and is posted to this core, and every report that shows a balance reads it from here. For the finance team, the outcome is clear: the figure in the back office, in the customer app and in the period-end report is the same figure, and closing a period does not require reconciling several subsystems against one another.
Key capabilities
- 01Chart of accounts with up to six detail levels and conflict-free code allocation
- 02Vouchers in three stages: draft, provisional and final
- 03Consecutive, non-resettable voucher sequence numbers for each fiscal period
- 04Opening and closing entries, with a voucher preview before posting
- 05Financial reports, from the trial balance and account turnover to the balance sheet and income statement
- 06Modules post vouchers with an idempotency key, so there is no risk of double posting
- 07Treasury from the teller counter to the central vault, with cheques, petty cash and bank reconciliation
Chart of accounts and detail levels
Each company's chart of accounts starts with general and subsidiary account headings and goes down as far as six detail levels. Detail accounts are floating: a single detail account can be used under several headings, so there is no need to create a new code for every combination. Every deposit account, wallet and financing contract has its own dedicated detail account, which means a customer's detail account turnover is exactly the statement they see in the app. Codes are allocated in one atomic operation, so two users working at the same moment can never end up with the same code.
- General and subsidiary headings, plus up to six detail levels
- Floating detail accounts, usable under multiple headings
- General, subsidiary and detail account turnover by date range
Vouchers and fiscal periods
A voucher starts as a draft, moves to provisional, and becomes final once it is confirmed. These transitions are enforced by the system itself, and a final voucher cannot be quietly edited. Each period's voucher sequence numbers come from that period's own counter, so the numbers run consecutively with no gaps and no duplicates. Opening and closing entries can be previewed before posting, so the accountant sees exactly which voucher is about to be issued.
- System-controlled transitions from draft to provisional to final
- A dedicated counter for each fiscal period
- Preview of opening and closing entries
- Trial balance, balance sheet and income statement
Treasury
Cash positions are tracked from the branch teller counter all the way to the central vault. Chequebooks are registered, and each cheque moves through its 13-state lifecycle, from issue and hand-over to collection or return, with a matching voucher for every change of state. Petty cash funds and reconciliation against bank statements are handled in this area as well.
- Teller counter, branch vault and central vault
- Chequebooks and the 13-state cheque lifecycle
- Petty cash and bank reconciliation
How modules post vouchers
Any module with a financial effect, such as deposits or financing, sends its voucher posting request together with an idempotency key. If the same request arrives a second time for whatever reason, no second voucher is created. The shape of each voucher is defined in the Voucher Template Builder, so debit and credit formulas are not scattered across module code. When the finance team wants to change the account heading a fee is posted to, it edits the template.
- An idempotency key on every posting request
- Voucher templates with debit and credit formulas
- No module keeps its own balance
For Qard al-Hasan funds, the same core also takes the place of separate accounting software. Members' deposits, loans disbursed, installments received and the fund's expenses are all recorded in one chart of accounts, and the year-end report is built from the same data the teller works with every day.
The Financial Core is multi-company. Each company or fund has its own chart of accounts, fiscal periods and users, and their data is kept separate. Comparisons across companies are possible only as far as the user's permissions allow.
Platform modules behind this solution
Financial Core
Financial Core
Holds each company's chart of accounts, detail levels, vouchers and fiscal periods. Every account balance on the platform is read from here, and other modules record their financial effect only by posting vouchers to it.
Treasury
Finance & Payments
Cash positions from the branch teller counter up to the central vault, chequebooks and the 13-state cheque lifecycle, petty cash, and reconciliation against bank statements.
Voucher Template Builder
Financial Core
Accounting voucher templates with debit and credit formulas. Financial events from each module are turned into voucher lines through these templates, so accounting rules are not scattered across module code.
Central Scheduler
Infrastructure
Scheduled jobs from every module, such as the nightly calculation of installment late-payment penalties or daily scores, run from a single scheduler. The logic of each job stays with the module that owns it.
More solutions
See this solution on demo data
In a demo session we walk through your organization's scenarios on Dara's demo environment and answer your technical and finance teams' questions.