Business software in Kuwait and Qatar: running books before VAT arrives

Where Kuwait and Qatar stand today

As of September 2026, neither state levies VAT. That is the whole of the immediate answer, and it is worth stating plainly because a good deal of Gulf software marketing implies otherwise.

Both states signed the 2016 GCC VAT framework agreement, which sets a 5% standard rate when a member state adopts it. That is the shape of the eventual change, not a commitment to a date. Timetables in this region move; your accountant confirms what applies to you and when.

Why tax-as-configuration matters at a rate of zero

The usual mistake is to treat “no VAT” as “no tax requirement”, and buy accordingly — a simple invoicing tool with no tax model at all. The bill for that arrives on the day a rate is announced, because the migration is not the rate. It is everything the rate touches: item prices, quotations already issued, open contracts, receipts, the chart of accounts, and every report anyone reads.

The alternative is software where tax is configuration you control rather than a country baked into the product. In practice that means five things you should be able to do without a developer and without a data migration:

• Define a tax — its name, its rate, its components if it has more than one — and start using it from a date.
• Choose inclusive or exclusive pricing per price list, because a shop and a contractor will want opposite answers.
• Have it split automatically on every posting. A sale, a purchase, an expense, a POS settlement: each writes a balanced double-entry voucher with the tax portion in its own ledger.
• Read a tax summary from those postings, not from a separate calculation that can drift.
• Leave history alone. Transactions posted before the rate existed keep their own treatment; nothing is re-stated behind you.

Get that today, at a rate of zero, and switching VAT on later is an afternoon of configuration rather than a project. Buy a product with a “Kuwait — no tax” mode instead, and you will be buying again.

Neighbours make the point. The UAE and Oman charge 5%, Saudi Arabia 15%, and Bahrain 10%, all under the same framework agreement Kuwait and Qatar signed. A Gulf-capable platform is one that runs all of those side by side — see the multi-country GCC guide if you already trade across borders.

Currency, and the three-decimal question

The Kuwaiti dinar has three decimal places. So do the Bahraini dinar and the Omani rial. This sounds trivial and is not: software that assumes two places will round every line, and the error compounds across a long invoice, a price list, and a month of postings until the books argue with the bank.

Treat it as a buyer’s test rather than a claim to be believed. Enter a price with three decimals, invoice a quantity that will not divide neatly, then compare the printed document, the receipt and the posted voucher. Do it with every vendor you shortlist, ours included, and you will learn more in five minutes than from any feature grid.

The same applies to buying. Kuwaiti and Qatari businesses import in dollars, euros and rupees. Exchange rates should be first-class data, carried into the books with the transaction, with reports read in your base currency.

Arabic documents and an Arabic workspace

Bilingual documents are not a VAT feature and are needed now. An invoice in Kuwait City or Doha is commonly read by an Arabic-speaking customer and an English-speaking accountant, and issuing two separate invoices for one sale is how records fall out of step.

What to look for: paired Arabic and English labels on one page, right-to-left layout done properly rather than a mirrored English template, and the same treatment across every printable document type — quotation, invoice, receipt, delivery note, credit note. The workspace itself should run in Arabic for the staff who prefer it. There is a full test in what to look for in bilingual documents.

What to set up now

1. Books that post themselves. Confirm an invoice; open the voucher it wrote. Do the same for a purchase, an expense, and a counter sale.
2. A tax model you can reach. Ask the vendor to add a 5% tax live, apply it to one item, and show the split — then remove it again.
3. Currency set up and tested, with rates carried onto foreign purchases and a three-decimal amount run through a document, a receipt and the ledger.
4. Bilingual document templates, with branding set per branch if you have more than one.
5. A financial year you define, with lock dates, so closed periods stay closed.

Do those five now and the eventual arrival of VAT is a settings change with an effective date. To try the list against Flowyana with the dinar or riyal and your own documents, book a demo.