ERPNext Accounting Consultant, KSA

Designing the Saudi chart around statements, zakat and VAT

A Saudi chart of accounts has several readers. The auditor needs financial statements under the framework that applies to your company. The zakat or tax advisor builds the base for the annual filing from specific balance sheet and profit items. The VAT team needs clean input and output accounts. Charts inherited from older local packages often blur these lines, with provisions, related-party balances and long-term assets mixed into broad groups.

In ERPNext I separate concerns on purpose:

• Accounts follow the statement structure your auditor uses, with separate ledgers for items your advisor has to identify, such as provisions, long-term investments, related-party balances and capital movements. Which items matter for zakat is your advisor's decision; the chart simply keeps them visible.
• Cost centers carry branches, regions or projects that management holds to budget.
• Accounting dimensions add tags like contract, sales channel or related party where an account alone is not enough.

Account names can be held in Arabic and English, which helps when the same trial balance goes to an Arabic-speaking board and an English-speaking group finance team. I document the design so your advisor and auditor can review it before configuration. The general mechanics are on the ERPNext accounting page, and the requirement work behind it follows my requirements gathering method.

VAT templates, e-invoices and the return: keeping them in agreement

VAT in ERPNext runs on sales and purchase tax templates, item tax templates for zero-rated or exempt items, tax categories on customers and suppliers, and tax rules that pick the template. The configuration is familiar to any ERPNext implementer. The Saudi difference is that the return, the ledger and the e-invoices submitted to ZATCA now all have to agree.

With your tax advisor, I test these points:

• Each template posts to the output or input account and return line your advisor expects
• Exports and other zero-rated supplies stay distinct from exempt supplies
• Imported services are handled under reverse charge, with both sides posted
• Credit and debit notes reference the original invoice and reverse the same lines
• Advances received are taxed in the period your advisor confirms

Then I add a reconciliation that core accounting does not give you on its own: invoices cleared or reported through your e-invoicing app compared with sales invoices and credit notes posted in the ledger for the same period. Rejected or pending submissions must surface to finance before the return is prepared, not after. How the app records status, and which report shows it, depends on the app you choose, which is evaluated on my ERPNext page for Saudi Arabia. VAT and e-invoicing treatment remain your advisor's call.

Withholding tax, card settlements and Saudi bank reconciliation

Payments to non-resident suppliers, for services, royalties or management fees, can attract withholding tax, which the Saudi payer deducts and settles. ERPNext has tax withholding categories that deduct an amount on purchase invoices or payments and post it to a liability account. Whether they fit your cases, or whether a journal routine with clear supporting detail is simpler, is something I test with your advisor. The rates and categories that apply are their decision.

Card receipts are the other daily challenge. Retail and service businesses receive mada and credit card payments that settle to the bank in batches, net of merchant fees and sometimes days later. I route these through a clearing account per acquirer: point of sale or invoice receipts go in, settlements and fees come out, and the balance should empty on each settlement. Any residue points straight to a missing fee or a chargeback.

Saudi bank exports are loaded through statement import, and each line is then cleared against its payment entry or journal on the reconciliation screen. Live bank feeds depend on integrations that should be confirmed with your bank first. For supplier payments, payment terms drive the payables schedule, and payment entries can be grouped into a bulk transfer prepared in the format your bank accepts. The finance automation page describes how these routines fit together.

Branches, regional books and sister entities

Saudi businesses often operate as one legal entity with branches in Riyadh, Jeddah, Dammam and elsewhere, each with its own commercial registration, warehouse and staff. Others are part of a group with separate companies in the Kingdom and the wider Gulf. The accounting structure depends on which of these you are.

• Branches under one VAT registration usually sit inside one ERPNext company, with each branch as a cost center or dimension, its own naming series for invoices and its own warehouses and bank accounts.
• Separate legal entities become separate companies on the same site, each with its own chart, tax templates and bank accounts.
• Sister companies trading with each other are set up as each other's internal customer and supplier; the buyer's purchase invoice is raised from the seller's invoice, while recharges and loans go through inter-company journals.

Related-party balances deserve their own accounts or tags, because they matter to both the auditor and the zakat advisor. A consolidated statement across companies can be produced in ERPNext for management, while formal group financial statements are normally prepared from entity trial balances by your accountant or auditor.

A sister company in the UAE or another Gulf country brings different tax and e-invoicing rules, which I check separately rather than assume. My multi-company ERP page covers the structural decisions.

Opening balances, period locks and the year-end pack

Saudi companies come to ERPNext from many places: Tally, QuickBooks, Arabic accounting packages built for the local market, older ERPs or plain spreadsheets. Whatever the source, the opening approach is the same:

1. Agree a cutover date with finance and your advisor, ideally right after a VAT period has been filed from the old system.
2. Translate old accounts into the new chart, then bring the final trial balance in as one opening journal.
3. Load open customer and supplier invoices individually, so aging and payment matching continue.
4. Bring fixed assets across with cost, accumulated depreciation and remaining life, and record opening stock by warehouse through stock reconciliation.
5. Treat the temporary opening account as the proof: it must be empty before go-live.

Invoices issued before cutover were reported or cleared through your old system, so credit notes against them need a clear procedure in the new one. I agree that procedure with your advisor before go-live.

During the year, each filed VAT period is locked through an accounting period or frozen accounts date. At year end, a period closing voucher closes profit and loss to retained earnings, and a standard pack goes to the auditor and zakat advisor: trial balance, ledger detail, aged balances, fixed asset register, VAT and withholding reconciliations, related-party listings and inter-company confirmations. The data migration service explains the wider cutover method.

When ERPNext Accounting is not enough in Saudi Arabia

ERPNext accounting can carry a Saudi ledger well, but these situations usually push me toward a different answer:

• No e-invoicing app you trust. If no available app covers your invoice types and integration phase with a credible maintenance record, the accounting design cannot compensate.
• Large regulated or listed groups. Formal consolidation, segment disclosures and heavy audit requirements across many entities often suit a finance-led ERP better.
• Government-linked procurement rules. Some buyers set expectations about vendors, hosting or support that a community-supported stack struggles to meet.
• A finance team without system ownership. Updates to ERPNext and the e-invoicing app have to be tested together each time, and somebody must own that.
• Arabic-first statutory reporting with no appetite for custom reports. Bilingual statements and advisor schedules usually need some report work.

None of this is a verdict against open source in the Kingdom; it is a list of risks to price in. A useful exercise is to run the same zakat, VAT and e-invoice reconciliation scenarios on Odoo Accounting for Saudi companies or Zoho Books in Saudi Arabia. The Saudi ERP consultant page shows how I structure that comparison, and the Saudi Arabia hub outlines remote delivery.