ERPNext Accounting Consultant, UAE

A chart of accounts that serves VAT, corporate tax and the auditor

Many UAE ledgers were built when VAT was the only tax that mattered. The arrival of corporate tax changed what the chart has to answer. The auditor still needs statements in an accepted framework, and the tax computation now starts from accounting profit, with adjustments for items such as entertainment, fines, certain interest and related-party transactions.

In ERPNext I handle this with structure rather than spreadsheets:

• Accounts separate expenses that commonly need a tax adjustment, so they do not disappear inside general overheads. Your tax agent decides which items those are.
• Cost centers represent divisions, branches or projects that management reviews.
• Accounting dimensions carry the extra tags: the emirate of supply on sales, a related-party flag, or a qualifying and non-qualifying activity marker where a free zone entity needs one.

A dimension can be made mandatory on chosen account types, which stops untagged entries reaching the ledger. That matters at year end, when someone has to justify each adjustment line.

I document the design in a short specification your tax agent and auditor can review. The ERPNext accounting overview covers the general mechanics, and my solution design service is where this sits in a wider project.

Tax templates, emirate tagging and checking the VAT return

ERPNext applies UAE VAT through sales and purchase tax templates, item tax templates for zero-rated or exempt lines, tax categories on customers and suppliers, and tax rules that select a template automatically. The work is in deciding which combinations you need and checking that each one lands where the return expects.

With your tax agent, I build a list of every transaction type and test it:

• Standard-rated sales, split by the emirate where the supply is made
• Zero-rated exports and exempt supplies, kept apart in the ledger
• Imports of goods and services under reverse charge, posting output and input tax together
• Supplies involving designated zones, where your advisor confirms the treatment
• Credit notes and advances, which must adjust the right period and line
• Purchases with non-recoverable VAT, posted to cost rather than to the input account

Earlier ERPNext releases included a UAE VAT return report. Whether your version, or a regional app you install, provides one today should be confirmed on a test site; if not, a custom report built from the same mapping does the job. Either way, a trial return from test transactions is agreed with your tax agent before go-live. Master data matters too: tax registration numbers on customers and suppliers will also feed e-invoicing later, as discussed on my ERPNext page for the UAE. VAT treatment decisions stay with your advisor.

Post-dated checks, dirham accounts and bank reconciliation

Post-dated checks remain part of commercial life in the Emirates, particularly in trading, contracting and property. A ledger that treats a dated check as cash on receipt overstates the bank and understates receivables, and the finance team ends up keeping a separate register.

In ERPNext, a payment entry carries both a posting date and a reference date for the check. My usual design records checks received into a holding account for undeposited or post-dated checks, then transfers them to the bank on deposit or clearance. Issued checks follow the mirror pattern. A report on that holding account becomes the PDC register, so the separate spreadsheet can go. Check printing is handled through a print format matched to your bank's check layout. I confirm the exact flow with your auditor, because some prefer post-dated items to stay off the ledger until the date arrives.

For bank accounts, statements are usually imported from your bank's export into ERPNext, after which ERPNext's reconciliation screen pairs each statement line with the matching receipt, payment or journal. Live feeds depend on integrations that may or may not exist for your bank, so I do not assume them. Dollar and euro accounts carry their own currency, and month-end exchange revaluation keeps open balances at the closing rate. Because the dirham is pegged to the dollar, dollar differences are usually small, but rate rules for invoices and payments in other currencies still need agreeing with finance. The multi-currency ERP page covers that design.

Mainland, free zone and GCC sister companies in one ledger

A common UAE group has a mainland trading company, a free zone entity for re-export or holding, and sometimes a sister company in Saudi Arabia or Oman. Each needs its own books, and the auditor will look closely at the transactions between them.

ERPNext supports this with separate companies on one site. Each has its own chart, cost centers, tax templates and bank accounts, while items, customers and suppliers can be shared where that helps. Group trading is handled by flagging each sister entity as an internal customer and supplier, which lets the purchase side be generated from the selling entity's invoice. Recharges, loans and shared costs move through inter-company journal entries that post both sides together.

For corporate tax, related-party and connected-person transactions often need to be identified and documented. Tagging them with a dimension, alongside the inter-company link, gives your tax agent a clean extract rather than a manual search through the ledger. Whether entities form a tax group, and how free zone income is treated, are questions for your advisor; my job is to make the data support whatever they decide.

A consolidated statement across companies is available in ERPNext for management. Formal group accounts with eliminations are usually prepared by the auditor or accountant from entity trial balances. A sister entity in another GCC country also brings its own tax and e-invoicing rules, which I check separately. The multi-company ERP page sets out the decisions in more detail.

Tally opening balances, period locks and the auditor's pack

Tally is the most common starting point for UAE companies moving their books into ERPNext, followed by QuickBooks and spreadsheets. Tally's groups and ledgers map reasonably well to an ERPNext account tree, but the detail needs care.

• Groups are reworked into the new chart, often consolidating ledgers that existed only for analysis now handled by dimensions.
• Sundry debtors and creditors become customers and suppliers, with tax registration numbers and payment terms checked.
• Bill-wise outstanding balances from Tally are loaded as individual opening invoices, so aging and matching continue without a break.
• Uncleared post-dated checks are carried over into the holding account with their reference dates.
• Tally's closing trial balance becomes a single opening entry, and the temporary opening account is the control: if it does not clear, something was missed.

I usually aim for a cutover at the end of a VAT period, so the final return comes from Tally. Once each return is filed, an accounting period or frozen accounts date blocks back-dated changes, and corrections go into the current period where the tax agent can see them.

At year end, a period closing voucher moves the result to retained earnings. The pack I set up for the auditor typically holds the trial balance, ledger detail, aged balances, the PDC register, the fixed asset register, VAT reconciliations, related-party listings and inter-company confirmations. The legacy software migration page explains the wider approach.

When ERPNext Accounting is not enough in the UAE

ERPNext accounting covers most of what a UAE trading or services group needs, but I flag these situations early:

• Your board wants a vendor commitment on e-invoicing now. The national program is still taking shape, and an open-source stack means planning a route rather than buying a promise.
• Group reporting spans many GCC countries. Several jurisdictions, each with different tax and e-invoicing rules, can be easier on a commercial platform with maintained localizations for each.
• Heavy IFRS-specific accounting. Complex lease accounting, revenue contracts with many elements or formal consolidation usually need specialist tools or significant extra work.
• The tax agent cannot get the data they need without custom reports, and nobody will maintain them. Every custom report needs an owner through upgrades.
• No in-house finance discipline. Open journal entry rights, without roles and approvals, quickly undermine an audit-ready ledger.

Spotting these early is cheaper than discovering them after the first audit. Where they apply, an Emirati group can test the same VAT, corporate tax and PDC scenarios on Odoo Accounting in the UAE or Zoho Books for Emirati firms and see which ledger copes. My ERP consultant page for the UAE explains that evaluation, and the UAE hub summarizes how I work with teams there.