Accounting software for Saudi businesses — VAT, Zakat and ZATCA
Double-entry accounting built for Saudi rules: VAT returns and VAT ledger accounts computed on the same basis, Zakat working papers, ZATCA e-invoicing, foreign-currency invoicing and Arabic-English accounts.
- Auto-post sales · purchases · payroll
- Bank reconciliation + cheque registry
- P&L · Balance Sheet · Cashflow
100% double-entry · auto-post
One ledger, posted as you work
Once auto-posting is switched on, sales, purchases, payroll, expenses, depreciation and payments post to the general ledger as they happen, not in a month-end batch. The consequence is practical: the VAT return, the trial balance and the management accounts read the same numbers, and a built-in Data Verification report, not a spreadsheet, checks the trial balance against the ledger and the source transactions.
The chart of accounts is yours to shape, with cost centres, projects and branches as dimensions rather than as more accounts — which keeps the chart readable after three years of growth.
Tax that survives an audit
VAT is computed per line, and a credit note reuses the tax of the invoice line it reverses, so a return against a two-year-old invoice carries that invoice's rate and your comparatives stay true. Zero-rated and exempt supplies get their own tax rates with a ZATCA exemption code, because the split governs input-tax recovery.
Posted journals are corrected, not overwritten: a posted entry is reversed with its own audit trail, and editing a source document re-posts through a reversal. Nothing quietly changes history, which is what an auditor tests for.
Closing a period
Fiscal periods with soft close and lock, journal approval, bank reconciliation and automatic year-end closing entries are built in, and a closed period stays closed — the ledger refuses any posting dated in it, so last month's figures cannot drift.
Statements come out in Arabic and English from the same data, which matters when the same figures go to a Saudi bank, a foreign parent company and an auditor in the same week.
Common questions
When do transactions post to the general ledger?
As they happen. Once auto-posting is switched on, sales, purchases, payroll, expenses, depreciation and payments post as they occur rather than in a month-end batch. The VAT return, the trial balance and the management accounts read the same numbers, and a Data Verification report, not a spreadsheet, checks the trial balance against the ledger and the source transactions.
How are branches, projects and cost centres handled?
As dimensions on the posting rather than as additional accounts. That keeps the chart of accounts readable after three years of growth, while still allowing profitability to be read per branch, project or cost centre.
What happens to a credit note raised against a two-year-old invoice?
The credit note reuses the tax of the original invoice line, so it carries the rate the invoice was issued at rather than today's, and your comparatives stay true. VAT is computed per line, and zero-rated and exempt supplies get their own tax rates with a ZATCA exemption code, because that split governs input-tax recovery.
Can a posted entry be edited?
Not in place. A posted journal is corrected by reversal with its own audit trail, an edited source document re-posts through a reversal, and a ZATCA-filed invoice is corrected by credit note. Nothing quietly changes history.
What happens after a period is closed?
A closed period stays closed. The ledger refuses any posting dated in it, so you date a late invoice in the open period with a reference to the one it relates to; a soft-closed period can be reopened by an authorised user, a locked one never. Statements come out in Arabic and English from the same data.