Central Accounting Core (AccountingCore)
This module holds each company's chart of accounts, detail levels, vouchers and fiscal periods. The balance of every account is computed in real time from voucher lines, and every other module records its financial effect only by posting a balanced voucher to this core.
- Domain
- Accounting and Financial Core
- Target customers
- finance and accounting unit, finance managers, technical teams of other services
- Main capabilities
- chart of accounts, accounting vouchers, fiscal year and branches, complete financial reports, bank matching, financial services integration hub
AccountingCore is the platform's double-entry accounting engine: the chart of accounts, accounting vouchers, fiscal year, branches and financial reports in a single multi-company core. No balance is stored in this system. Every balance is computed in real time from the posted voucher lines, so the figures always agree with the recorded vouchers.
This service no longer holds deposit or financing operations; those are now run by the standalone Deposit and Financing services. The role of AccountingCore is that of the shared Financial Core to which all of the platform's financial services (Deposit, Financing, Collateral, Treasury, Wallet, Customer Loyalty, Fixed Assets, Sales, Investment and others) send their balanced vouchers. For finance managers and the board, this means a single source that is always balanced for the financial statements of the whole group, regardless of which product a transaction came from.
The main users are the accounting and financial control unit, the finance managers of each subsidiary, and the technical teams of other services, who post accounting vouchers or query accounts through its API.
Key capabilities
Chart of accounts and accounting parties
Tree-structured account coding, definition of account types, and management of individuals, legal entities and customers with batch entry and national ID uniqueness control
Accounting vouchers
Entry of vouchers and voucher lines, notes on vouchers, file attachments, custom extra fields, and definable voucher types
Opening and closing vouchers
Closing and reopening the fiscal year with an official voucher, following the rules for closing temporary accounts
Fiscal year and branch management
Multi-company and multi-branch operation, with a defined time range for each voucher
Complete set of financial reports
Balance sheet, income statement, cash flow statement, statement of changes in equity, multi-level trial balance, general, subsidiary and detail account turnover, account review, profitability analysis, and voucher reports by account, party, date, status and type
Bank statement matching
Mapping of bank statement rows to accounting headings for reconciliation
Reserve/commit/release pattern
For external payment flows (such as cards and payment gateways), before the transaction is finalized
Service-to-service integration hub
Dedicated connection points for the Deposit, Collateral and other product services, for automatic voucher posting and account inquiry
Service health monitoring dashboard
Business value
Without a shared Financial Core, each financial product keeps its own balances and reports, and reconciling them with one another becomes manual and error-prone. AccountingCore solves this by forcing every transaction through a balanced voucher (debit = credit) in a single database. For management, the result is real-time, reliable financial statements for the whole group, with no manual reconciliation between systems at period end.
Use cases
- A Qard al-Hasan institution or bank that reports several companies and branches under one Financial Core
- A financial holding that runs several fintech products (credit, cards, wallet, customer loyalty), all of which must appear on a single balance sheet
- Preparing regulatory reports and periodic balance sheets for the board or the supervisory body, directly from recorded data
- Monthly reconciliation of the company's bank accounts against its internal accounts
What sets it apart
- Balances are never stored. They are always computed from the actual voucher lines, so a mismatch cannot occur
- The reserve/commit/release pattern eliminates early or duplicate posting of transactions that are still being processed
- It is already the accounting backbone of more than ten live services on the platform
- Before posting, every voucher is required at the code level to be balanced (total debit = total credit)
Solutions that use this module
See this module 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.