Why build for a tax that has not arrived?

Because the cost is asymmetric. Carrying a zero rate through the schema costs a column and a few lines; adding tax to a system whose invoices never had it means touching every historical record, every report and every integration, under a deadline set by somebody else.

What does the data protection law require of an application?

In engineering terms: a lawful reason for what you store, a way to tell someone what you hold, a way to correct or delete it, and reasonable security with breach notification. The same capabilities a GDPR build needs, arrived at through a different statute - which is why building once to the stricter standard is usually the efficient path.

Is local hosting required?

Not as a general rule for private business, and frequently as a condition in government and quasi-government contracts, which is a large share of the market. Because so much work here touches the public sector directly or through a prime contractor, it is worth settling before infrastructure is chosen.

How much of this is an Arabic problem?

Less than people expect on the frontend and more than they expect in the database. Display is well-understood. Sorting, searching and matching Arabic text depend on storage decisions - collation and normalisation - and those are migrations, not settings.

Laravel in Qatar

Laravel development services for Qatari businesses

Qatar has data protection law and, so far, no VAT. The second fact is the trap - an invoicing system built as though tax will never exist is the most expensive thing to change later.

Updated September 22, 2026

Qatar is unusual in the region for two reasons that pull in opposite directions. It legislated on data protection earlier than its neighbours, and it has not introduced the value added tax that most of them now charge.

The second is the one that quietly shapes software, because the correct engineering response to "there is no tax" is not to build as though there never will be.

Build the tax model before there is a tax

A value added tax has been announced, deferred and discussed in Qatar for years. Whether it arrives next year or later, the asymmetry is what matters:

Carrying tax through a system that charges zero costs almost nothing. A rate on the line item, a tax total on the invoice that happens to be zero, a registration number field that is currently empty, and reports that group by a rate nobody is using yet.

Adding tax to a system that never had it is a different project. Every invoice template, every total, every integration that consumes your invoices, every report and every historical record has to be reconciled with a new concept - usually on a timetable set by an authority rather than by you, and usually while the business continues.

So on a Qatari build we model it from the start:

The rate belongs to the line item at the time of issue, not to a configuration value read later.
The invoice carries a tax total, currently zero, and the template has a place for it.
Tax registration is a field on the customer and on your own entity.
Reporting groups by rate from the beginning, so the report does not need rewriting when a second rate exists.

None of that is speculative work. It is a handful of columns and the difference between a configuration change and a quarter.

The data protection law, in engineering terms

Qatar's statute arrived before most of its neighbours' and asks for the things this kind of law asks for: a legitimate basis for processing, consent where consent is the basis, notice to individuals, access and correction rights, security appropriate to the risk, and notification when something goes wrong. Special categories - health, children, criminal records - carry extra obligations.

For an application that means the same four capabilities a European build needs, and they are cheap only if they are designed in:

A consent record with history rather than a flag. A deletion that is an operation the system performs, with an explicit list of what is retained for legal reasons. An export that does not require a developer. And access logging good enough to answer what was touched when something goes wrong.

Where a product serves Qatar and the wider Gulf, building to the strictest regime in the set and applying it everywhere is less work than tracking four statutes separately, and it does not get you into trouble anywhere.

Public sector shapes the market

A large proportion of substantial software work in Qatar is government, state-owned or a supplier to one. That changes the constraints from preferences into contract terms - hosting location, access control, audit trails, documentation delivered in a specific form.

The engineering consequence is that residency and auditability are decisions made at the start of a project rather than questions answered during a security review, because moving them afterwards means moving the infrastructure.

Arabic reaches the database

Right-to-left layout is the visible half and the well-understood one. What lands on the backend is text handling: collation decides sorting, and Arabic has multiple written forms of the same letter, optional diacritics and characters that look identical and are not.

A customer searching for a name typed differently from how it was stored finds nothing, and nobody reports it because it looks like the record does not exist. Normalisation at write time with an index on the normalised form fixes it, and it is a migration once there is data.

Working with us

We work remotely from Ankara, in English, in the same time zone as Doha for part of the year and an hour apart for the rest. The working week here runs Monday to Friday, which overlaps Qatar's Sunday-to-Thursday week by four days

worth planning around rather than discovering.

The engineering is our usual application development and integration work, with the tax model carried from the start because the cheapest time to add a tax is before anyone is charging one.

Modelling a tax before it exists asks for the care that money columns ask for on day one. Those are the decisions you cannot take back cheaply. A nullable rate column added in a hurry two years from now is not the same thing as one designed in.

Invoicing and payment. In US dollars, by bank transfer to an IBAN. Codefacture Yazılım A.Ş. is a Turkish company, so no Turkish VAT appears on the invoice under the export-of-services exemption. There is no Qatari VAT line either, for the reason the rest of this page is about.