Where ERP Fits in a Bank
Banks already run some of the most sophisticated software in any industry. The core banking system holds customer accounts, posts deposits and withdrawals, calculates interest or profit on financing, and processes transfers around the clock. So when someone proposes an ERP for a bank, the first reaction is often skepticism: what is left for another system to do?
Quite a lot, as it turns out. Behind the customer-facing platform sits an organization with thousands of employees, dozens or hundreds of branches, a procurement budget for IT equipment and security services, a fleet of ATMs and vehicles, and a board that wants monthly management accounts against budget. None of that is what a core banking system was designed for. That back-office layer is where ERP belongs.
The same split applies to finance companies, insurers, exchange houses and payment firms. Each runs a specialist platform for its product, and each still needs a system to run the business itself. This guide covers where that boundary sits, what the ERP actually handles, the Saudi regulatory points that shape the project, a worked VAT example that catches many finance teams off guard, and a practical rollout sequence.
Core Banking vs. ERP: Drawing the Line
| Aspect | Core banking platform | ERP system |
|---|---|---|
| Main users | Branch staff, operations, customer service | Finance, HR, procurement, management |
| Master data | Customers, accounts, loans, deposits, cards | Chart of accounts, employees, suppliers, fixed assets |
| Transaction profile | Millions of small, uniform transactions | Fewer transactions, but varied and interlinked |
| Typical output | Statements, balances, interest and profit accruals | Financial statements, branch costs, payroll, budget variance |
The two systems are connected, not merged. The core platform sends summarized postings to the ERP general ledger, daily or at period end, so customer activity becomes accounting figures that can be combined with operating expenses. Trying to make one system do both jobs is a frequent reason projects in this sector go badly: the result tends to be a platform that does neither job well.
What the ERP Handles in a Financial Institution
General ledger and financial statements
The ledger receives summarized entries from the core system and adds everything else: salaries, rent, depreciation, provisions, professional fees. Saudi financial institutions report under IFRS as endorsed by SOCPA, which listed entities adopted from 2017 and other entities from 2018. The ERP needs a flexible chart of accounts mapped to statement line items, and a disciplined month-end close with clear ownership of each reconciliation.
Branch and department cost accounting
A bank with forty branches wants to know what each one costs to run: rent, staff, utilities, security, maintenance, and an allocated share of head office overhead. Cost centers make every expense land on a branch or department as it is recorded. Combine that with branch revenue from the core system and you get branch profitability, which is the basis for decisions about opening, relocating or closing locations.
HR and payroll
Financial institutions are major employers of Saudi nationals, and pay structures include allowances, bonuses and sales incentives. The ERP calculates payroll, applies GOSI contributions on basic salary plus housing, and produces the wage protection file. Since 1 March 2025 that file must be uploaded to Mudad within 30 days rather than 60. End-of-service awards follow Article 84 of the Labor Law: half a month's wage per year for the first five years and a full month per year after that, based on the last wage.
Procurement
Banks buy laptops and servers, cash-in-transit and guarding services, branch fit-outs, maintenance contracts and consulting. Every purchase should move through a requisition, an approval based on authority limits, a purchase order, a goods or service receipt, and invoice matching before payment. Internal audit will test exactly this chain, and it is the main control against internal fraud on the spending side.
Fixed assets
ATMs, safes, CCTV systems, servers, vehicles and branch buildings all need a register that shows location, custodian, accumulated depreciation and replacement timing. When an ATM moves from a closed branch to a new one, the register has to move with it, otherwise depreciation keeps landing on a cost center that no longer exists.
Budgeting and management reporting
The board approves an annual budget; management wants monthly budget-versus-actual by department and branch. When expenses carry the right cost center from the start, the variance report becomes a standard output rather than a week of spreadsheet work.
The Regulatory Frame in Saudi Arabia
SAMA Cyber Security Framework
The Saudi Central Bank issued its Cyber Security Framework on 24 May 2017, and it is mandatory for the financial institutions SAMA regulates. It covers governance, risk management, operations, technology and third-party security. In practice your ERP vendor will be asked about role-based access, audit trails, encryption, backup, business continuity and where data is hosted. Get those answers in writing during selection, not after signing.
Personal data protection
Employee records in the HR module are personal data under the Personal Data Protection Law, which came into force in September 2023 with enforcement starting after a one-year grace period in September 2024. The law also sets conditions on transferring personal data outside the Kingdom. Our article on ERP cybersecurity and PDPL covers the practical controls.
Segregation of duties
One user should never be able to create a supplier, approve its invoice and release the payment. The ERP must enforce that split through roles and keep a log of who created or changed each record and when. External auditors and the audit committee will ask for that log.
VAT: The Issue Most Finance Teams Underestimate
Financial institutions are unusual for VAT purposes. Many financial services where the consideration is an implicit margin, such as interest-based lending or financing at a profit margin, current and savings account management, and money transactions, are exempt. Explicit fees and commissions, such as transfer fees, card fees, statements and e-banking charges, are taxable at 15%.
That mix means the institution makes both exempt and taxable supplies and cannot recover all of the input VAT it pays. VAT on costs used only for taxable activity is recoverable; VAT on costs used only for exempt activity is not; VAT on shared overhead is apportioned. The default method uses the value of taxable supplies as a share of total supplies, and alternative methods need prior approval from ZATCA.
A worked example (hypothetical)
A finance company records SAR 80 million of supplies for the year: SAR 20 million in taxable fees and commissions and SAR 60 million in exempt financing income. Its recovery rate is 20 / 80 = 25%.
| Cost type | Input VAT (SAR) | Recoverable | Not recoverable |
|---|---|---|---|
| Card platform used only for fee-based services | 300,000 | 300,000 | 0 |
| Costs used only for exempt financing | 200,000 | 0 | 200,000 |
| Head office rent and maintenance (shared) | 400,000 | 100,000 | 300,000 |
| Total | 900,000 | 400,000 | 500,000 |
The SAR 500,000 that cannot be recovered becomes a cost, added to the expense or to the asset it relates to. The ERP makes this manageable only if each expense is tagged as taxable-use, exempt-use or shared when it is entered. Leave the tagging to quarter end and the tax team will spend days re-sorting invoices by hand. Because the provisional ratio usually differs from the final annual figure, the system also needs a clean way to post the year-end adjustment.
E-invoicing applies to the tax invoices the institution issues for its taxable fees. Under Phase 2, standard B2B and B2G tax invoices are cleared by ZATCA in real time before being shared with the buyer, while simplified invoices are reported within 24 hours.
What the Core-to-Ledger Posting Looks Like
A sound interface does not push every transaction into the ERP. It sends a summarized entry per day or period, split by product, branch and account. Suppose a hypothetical finance company's Khobar branch records SAR 180,000 in financing income and SAR 23,000 in service fees (before VAT) in a single day:
| Account | Debit | Credit | Cost center |
|---|---|---|---|
| Clearing account with core platform | 206,450 | Khobar branch | |
| Financing income (exempt) | 180,000 | Khobar branch | |
| Fee income (taxable) | 23,000 | Khobar branch | |
| Output VAT on fees at 15% | 3,450 | Khobar branch |
The clearing account should be reconciled to the source system every day. Any difference means something was missed or posted twice, and it needs to be resolved before the close. Daily reconciliation is what turns a two-week close into a few days.
Choosing an ERP for a Financial Institution
| Criterion | What to ask | Warning sign |
|---|---|---|
| Security and access | Role-based access by screen and action, exportable audit trail | Broad access for all users, logs that cannot be extracted |
| Integration | APIs to receive postings from the core or financing platform | Monthly file uploads keyed in by hand |
| VAT handling | Taxable, exempt and shared tagging; ZATCA e-invoicing | Apportionment done in spreadsheets outside the system |
| HR and payroll | GOSI, WPS/Mudad, end-of-service under Saudi rules | A foreign payroll engine that needs heavy customization |
| Hosting | Data center location, backup and continuity plans | Generic answers with no documentation |
| Local support | Arabic-speaking team that knows Saudi requirements | Support through a reseller in another time zone |
A Practical Rollout Sequence
- Define the boundary. Document what stays in the core platform, what moves to the ERP, and the level of detail in the summarized postings.
- Design the chart of accounts and cost centers. Map every branch and department to a cost center and every account to a statement line. Every later report depends on this.
- Bring security and compliance in early. They can stop the project late if their requirements are discovered late.
- Go live with finance and procurement first, then HR and payroll, then fixed assets. Phasing reduces risk and lets the team learn.
- Run payroll in parallel for one or two cycles and compare employee by employee before switching off the old process.
- Test with real scenarios, including awkward ones such as an employee who moved between branches mid-month or a supplier invoice that spans exempt and taxable use.
For the broader success factors behind any rollout, see our guide on successful ERP implementation.
Common Mistakes
- Pushing every banking transaction into the ledger. The ERP needs summaries by product, branch and account. Detail stays at the source.
- Leaving VAT until after go-live. Re-tagging a full year of expenses as taxable, exempt or shared is painful. Build it into the initial setup.
- Losing track of remote assets. Off-site ATMs drop out of physical counts unless each has a code, a location and a custodian.
- Granting broad access "temporarily". Temporary permissions tend to become permanent. Design roles correctly from day one.
KPIs Worth Tracking After Go-Live
- Cost-to-income ratio by institution and by branch, which is only possible with correct cost center tagging.
- Days to close from month end to approved accounts.
- Share of invoices matched to a purchase order, a direct measure of off-process spending.
- Open differences in the clearing account, by value and age.
- Provisional vs. actual VAT recovery ratio, to avoid a surprise at year end.
Where Tranquil Fits
Tranquil is a cloud ERP. It does not replace a core banking platform; it runs the back office around it. That includes accounting and finance, ZATCA e-invoicing with Phase 1 and Phase 2 compliance and real-time integration, and HR and payroll with bank integration for direct salary transfer and Muqeem integration for iqama and visa records. Asset management gives every asset a unique code and tracks its location, custodian and transfers between sites and departments, with automatic depreciation. Screens, reports, multi-level approvals and API integrations can be customized to connect with your existing platforms.
Frequently Asked Questions
Can an ERP replace a core banking system?
No. The core platform manages customers, accounts and their transactions. The ERP manages the institution itself: accounting, payroll, procurement and assets. They work together through an interface that posts summarized entries to the ledger.
Are banking services exempt from VAT in Saudi Arabia?
Only some. Margin-based services such as lending and account management are exempt, while explicit fees and commissions are taxable at 15%. That is why input VAT on shared costs has to be apportioned.
Does the SAMA Cyber Security Framework apply to the ERP vendor?
The framework binds the regulated institution, which is responsible for making sure its systems and third parties meet the requirements. Expect to be asked for evidence of the vendor's security controls before contract signature.
Which module should a financial institution implement first?
Usually the general ledger and cost centers, because every report depends on them, followed by procurement, then HR and payroll, then fixed assets.
Is Tranquil suitable for smaller finance companies and exchange houses?
Yes, for back-office work such as accounting, e-invoicing, payroll and assets. Contact the Tranquil team to discuss the interface with your operating platform and get a quote.