Qatar does not levy VAT today, so the correct way to configure “Qatar VAT” in Zoho Books is to build the tax structure and deliberately leave it inactive: domestic Qatari sales invoices must carry no VAT line, no VAT registration number and no 5% charge, because no VAT law is in force and the General Tax Authority (GTA) does not register businesses for VAT. The 5% rate belongs in a test organisation, not in your live books, until Qatar publishes its VAT law and registration rules. Getting this right is less about tax arithmetic and more about preventing VAT from being charged, accrued or reported by accident — and keeping the ledger clean enough that switching the regime on later is a settings change rather than a rebuild.
That answer surprises a lot of finance teams in Doha, because almost every “Qatar VAT” article online describes a 5% rate, a registration threshold and a filing calendar. Those numbers come from the GCC Common VAT Agreement, which Qatar signed in 2016 and has not yet implemented. The agreement is a framework, not a statute: it obliges signatories to adopt a national VAT law, and it is that national law — published in the Official Gazette, with executive regulations and GTA guidance — that would create an obligation to register, charge and file. Until then, a Qatari company has nothing to charge and nothing to return.
The practical position is easy to state. There is no VAT law in force in Qatar, the GTA has not opened VAT registration, there is no VAT return to file, and no Qatari tax authority issues a VAT registration number. A domestic invoice issued by a Doha business should therefore show the value of the supply, any applicable customs duty or excise already embedded in the price, and no VAT line at all. If an invoice in your file shows “VAT 5%”, one of three things has happened: a foreign VAT charge has been passed on by a GCC-registered supplier, a template has copied a UAE or Saudi format, or someone configured a rate in the accounting system that has no legal basis in Qatar.
What exists in the meantime is a real and separate tax base. Qatar levies corporate income tax at 10% on the foreign-owned share of taxable profits, withholding tax on certain payments abroad, and excise tax at the point of import or production on specific goods such as tobacco, energy drinks and carbonated drinks. Excise is not VAT and is not configured the same way — it is usually embedded in the landed cost of the goods rather than raised as a line-item tax on the customer invoice.
Alongside the tax question there is an invoicing question. Qatar’s Cabinet has approved a draft e-invoicing law and its executive regulations, developed by the Ministry of Finance with the GTA, but the detailed technical specification and rollout timeline are still to be published. That matters for configuration because e-invoicing regimes typically require structured invoice data — a supplier tax identifier, item-level classification, tax category codes and an audit trail — and those are precisely the fields that are usually left empty or filled inconsistently in a system that was never designed for them.
Zoho Books does not ship a Qatar-specific VAT edition. Qatari organisations run on the global edition, where every tax is defined manually rather than inherited from a country module. That is an advantage — you are not forced into another jurisdiction’s rules — but it also means nothing in the product stops you creating a 5% rate and applying it to a live customer tomorrow. The control has to come from your configuration discipline, not from the software.
Under Settings → Taxes → Tax Rates you define each rate by name and percentage; under Tax Groups you combine rates that must be applied together. For a Qatar organisation the useful pattern is to create the future structure now with an unambiguous naming convention — for example QA-VAT-5-STD and a group QA-VAT-5-GROUP — so that when the law lands, every item, template and report refers to one clearly identified object rather than three people inventing three different rates. Create it, document it, and do not attach it to any live item or contact.
Tax Settings controls whether tax is tracked in a single account or split between output and input tax accounts. For a business with any GCC cross-border activity, separate accounts are worth the small extra effort: foreign VAT collected on behalf of another jurisdiction should never sit in the same ledger line as a Qatari liability, because the two are reported to different authorities on different forms. Keeping them apart also makes the monthly control trivial — your Qatari output tax account should reconcile to zero every month.
A default tax rate on an item or a contact is a promise the system keeps on every future transaction, silently, including transactions created by API, by recurring invoice profile or by a colleague in a hurry. If any item carries a 5% default because it was copied from a UAE template, that error will propagate without anyone choosing it. Audit the item list and the customer list, set defaults to no tax, and check recurring invoice profiles separately — they hold their own tax settings and are frequently overlooked.
This is the sequence we use when preparing a Qatari client’s Zoho Books organisation for a tax regime that has been announced but not enacted. It takes an afternoon for a clean organisation and considerably longer where historical data is messy.
The table below is the mapping we apply in practice. It assumes a Qatari company with no VAT registration anywhere in the GCC; the cross-border rows change if the company holds a registration in another member state.
| Transaction | Qatar VAT position today | Zoho Books configuration |
|---|---|---|
| Domestic sale in Qatar | No VAT. No VAT line, no VAT number, no registration reference. | Item and contact defaults set to no tax; template stripped of VAT fields. |
| Export of goods outside the GCC | No Qatar VAT because no VAT exists; customs and export documentation still apply. | No tax applied; retain shipping and customs evidence with the invoice for audit. |
| Sale into a GCC state where you are registered | Foreign VAT applies at that state’s rate, reported to that authority — not to the GTA. | Separate tax rate, separate tax agency, separate tracking account, correct currency. |
| Purchase from an overseas vendor | No Qatari import VAT; customs duty may be payable at clearance. Foreign VAT, if charged, is the vendor’s jurisdiction. | Record duty in the landed cost of the item; keep foreign VAT on its own account if it is recoverable elsewhere. |
| Excise goods | Excise is a separate tax on specific goods, not VAT, and is not shown as a VAT line. | Embed in item cost or price; track the excise obligation outside the VAT accounts. |
| Reimbursements and disbursements | No VAT; characterisation depends on whether you acted as principal or agent. | Use a distinct item so the treatment is visible in reports rather than buried in a service line. |
VAT becomes real for a Qatari group the moment it trades into a GCC state that has implemented it, or holds a registration there. Four of the six member states now operate VAT: Saudi Arabia at 15%, the UAE at 5%, Bahrain at 10% and Oman at 5%. A Doha-headquartered distributor with a Saudi branch, or a consultancy billing UAE clients through a UAE registration, is inside those regimes and outside Qatar’s non-existent one.
The configuration lesson is simple and frequently ignored: one tax rate object must never serve two jurisdictions. Build a distinct rate, agency and tracking account per country, name them with the country code, and report them separately. Zoho Books handles this cleanly in a multi-currency organisation, but only if the structure was designed rather than accumulated.
Most of the damage we see in Doha is not caused by misunderstanding VAT. It is caused by configuration drift that nobody owned.
The value of a dormant structure is that activation becomes a short, ordered project instead of an emergency. The sequence that works is roughly this:
| Phase | What changes in Zoho Books | Evidence to keep |
|---|---|---|
| Registration | Add the GTA tax identifier to the organisation profile and to the invoice template. | Registration certificate and effective date. |
| Rate activation | Attach the prepared 5% group to taxable items and customers; leave exempt categories empty. | Signed tax matrix mapping every product line to a category. |
| Opening position | Record opening stock and accrued liabilities; lock transactions before the effective date. | Opening balance working papers agreed to the trial balance. |
| First return | Reconcile the Tax Summary to the general ledger before filing; investigate every difference. | Signed reconciliation and filed return. |
| E-invoicing | Add structured fields and audit trail once the GTA specification is published. | Mapping document against the published technical standard. |
Qatar’s corporate income tax, withholding tax and excise obligations are administered by the GTA, and an assessment is only as good as the ledger behind it. A company that has been quietly charging a non-existent VAT has an unexplained liability on its balance sheet and invoices that do not match its returns. A company that has kept its tax accounts clean, its templates accurate and its supporting documents attached has a much shorter conversation with an auditor — and, when VAT arrives, a defensible opening position instead of a reconstruction exercise.
The same discipline pays off in the e-invoicing transition. Regimes generally build on structured data: identifiers, tax categories, item codes, timestamps and an unalterable audit trail. Zoho Books already holds most of that, but only if customer records are complete, items are classified rather than described in free text, and transaction locking is used to protect closed periods.
BNF Consulting is an Authorised Zoho Partner and an Official Odoo Partner based in West Bay, Doha. We configure Zoho Books and Odoo for Qatari companies as a tax-ready structure rather than a set of defaults — chart of accounts, tax rates, tracking accounts, templates and reporting controls — and we document what must change when the GTA publishes VAT and e-invoicing rules. If you are unsure whether your current organisation is charging something it should not, the review starts with your tax settings and one month of invoices. Call +974 7703 0026, email sales@bnf-consulting.com, or see the Zoho and Odoo pages for capability detail; our services page covers the wider finance and audit-readiness work, and you can book a consultation from Doha.
One caution belongs at the end of any article on this subject. Tax positions depend on facts, registrations and the law in force on the date of the transaction, and Qatar’s position can change when a law is issued. Treat this as configuration guidance, confirm the current legal status with the GTA or your tax adviser before you change a live system, and keep a dated record of the advice you relied on.
No. No VAT law is in force in Qatar and the General Tax Authority does not register businesses for VAT, so domestic Qatari invoices should carry no VAT charge and no VAT registration number. Qatar signed the GCC Common VAT Agreement in 2016, but the agreement only obliges member states to introduce national VAT law; it does not itself impose one.
Zoho Books will let you create any tax rate and apply it, because Qatari organisations run on the global edition where taxes are defined manually. That is exactly why configuration discipline matters: a 5% rate can be created in minutes and applied to live invoices with no legal basis. Build the rate, document it, and leave it unassigned until a Qatari VAT law takes effect.
The GCC Common VAT Agreement contemplates a mandatory registration threshold of QAR 375,000 of annual turnover and a voluntary threshold of QAR 187,500. Those are framework figures and become binding in Qatar only through national legislation, so treat them as planning assumptions rather than current obligations.
Keep it completely separate from the Qatari ledger: a distinct tax rate for that jurisdiction, a distinct tax agency, a distinct tracking account and the correct transaction currency. Saudi Arabia applies 15% and the UAE 5%, and each is reported to its own authority, so a shared rate or shared tax account makes reconciliation and filing unreliable.
Almost certainly, once the GTA publishes its technical specification. Qatar's Cabinet has approved a draft e-invoicing law and executive regulations, but the data format, clearance model and timeline are still pending. In the meantime, the useful preparation is complete customer and item records, consistent tax categories, transaction locking for closed periods and a full audit trail.
