Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For Qatar
No VAT. No e-invoicing mandate. Which means, for once, you get to buy on the merits.
Every neighbour on this list is being sold a deadline. Saudi Arabia has clearance, the UAE has a phased programme, Oman started its rollout this year. Qatar has neither a value added tax nor an electronic invoicing mandate in force — a draft law was approved in 2026 and no timetable has been published with it. That is unusual and it is worth saying plainly, because a market with no deadline is a market where vendors have to find something else to be urgent about. We would rather tell you what the absence actually costs you, what it saves you, and what the cheap preparation is.
- Sales tax
- None in force. We carry Qatar at nil rather than at an anticipated rate, and we are not printing a number Qatar has not printed.
- E-invoicing
- A draft law approved, no published specification or timetable. Nothing to integrate with yet, and no readiness badge from us.
- Language
- English only, no right-to-left layout. Usually survivable in Doha; test it in a site store before you decide.
- Support
- Nairobi, in English, on the same clock — Doha and Nairobi are both UTC+3.
The question every vendor answers vaguely
What is actually in force, what is drafted, and what is merely expected
Three columns, because vendors in this market habitually collapse them into one. When somebody tells you they are "ready for Qatar VAT", ask which column they mean. Nothing below is tax advice and all of it is the General Tax Authority's to change — confirm the current position with them or with your adviser.
-
In force today
Corporate income tax, withholding, excise
A corporate income tax applies to the foreign-owned share of profits, with withholding on certain payments to non-residents and excise on a narrow list of goods. Returns are filed through the General Tax Authority's Dhareeba portal. This is real, it applies now, and it is the only part of the fiscal picture a system can be judged against today.
-
Approved in draft
An electronic invoicing law
The Council of Ministers approved a draft electronic invoicing law and its implementing regulations in 2026. What has not been published is a timetable, a technical specification, a format, or a model — clearance, reporting or network. Until those exist, nobody can build to it, and any vendor claiming they already have is describing an ambition.
-
Expected, undated
Value added tax
Qatar signed the GCC framework agreement in 2016 and has not enacted it. The Dhareeba portal reportedly carries fields that anticipate it. Widely expected is not the same as legislated, and we are deliberately not printing a rate on this page, because Qatar has not printed one either.
The honest consequence of that table is a sentence most vendor pages will not write: there is currently nothing here for us to integrate with, and that is fine. When the General Tax Authority publishes a specification, it becomes an ordinary build against a real document, the same way every other integration in this product was built. What we will not do is sell you readiness for a specification that does not exist yet, or let a "VAT-ready" badge do work that a published honesty ledger should be doing.
Five questions worth putting to every vendor on your list — including us
- When a vendor says "VAT-ready", which column are they in — and can they name the specification they built against?
- If a mandate lands in eighteen months, what would actually have to change in the system we are about to buy? Ask for the list, not the reassurance.
- Do our invoices already carry an unbroken sequential number? Retrofitting that after the fact is one of the most tedious jobs in this business.
- Do we hold customer and supplier registration identifiers as structured fields, or typed into the middle of an address?
- If we are a joint venture, can we already attribute profit by owner — because the tax that exists today already asks that question.
What this actually costs today
Four things no mandate is going to fix for you
With no deadline in the picture, these are the whole case. If none of them is true of your operation, you do not need to buy anything yet and we will say so.
A pipeline that outgrew the spreadsheet two projects ago
Qatar runs an unusual amount of project work per head of population, and the failure is consistent: materials in one place, subcontractors in another, plant on an email. The loss-making job is identifiable, just not until the final account.
Plant that is on a site, or possibly on another site
Generators, compactors, survey kit and tools move between jobs on a phone call. The second time you hire in something you already own is the moment the asset register stopped being a document and became a cost.
Landed cost that disappears into overhead
Almost everything is imported. Freight, clearance, port handling and inland haulage arrive as separate invoices weeks after the goods, get absorbed into an overhead line, and leave you pricing against a unit cost that is confidently wrong.
A joint venture whose profit cannot be attributed
Corporate income tax reaches the foreign-owned share, which means somebody has to say which profits belong to whom. If costs were never attributed to a project or an entity as they were incurred, that answer is assembled annually from memory and defended annually with difficulty.
The actionable half
Six things worth doing now, none of which require knowing what the mandate says
This is the part we would give you on a call whether or not you bought anything. Every electronic invoicing regime we have worked with — Kenya's, and the published models across this region — depends on the same handful of data conditions. They are cheap to establish while nothing is urgent and genuinely painful to retrofit under a deadline. None of them is a compliance feature. All of them are just good records.
One unbroken invoice sequence 01
Cheap now
Cheap now: set the series, let the system own it, never issue outside it.
Expensive later
Expensive later: every regime we have seen requires sequential numbering without gaps, and a history full of manual overrides and parallel books is a reconciliation exercise before you can even begin the integration.
Tax codes on every line, even at zero 02
Cheap now
Cheap now: a tax field on every sales and purchase line, populated, even when the rate is nil.
Expensive later
Expensive later: if the field does not exist, introducing one means revisiting the item master, the price lists and the open orders at the same time as building the integration — under a deadline, with the same three people.
Counterparty identifiers as fields 03
Cheap now
Cheap now: commercial registration and tax identifiers held as their own structured fields on the customer and supplier record.
Expensive later
Expensive later: every mandate validates the counterparty. Identifiers typed into the second line of an address cannot be validated, and extracting them from free text across several thousand records is exactly as tedious as it sounds.
Net, tax and gross split at capture 04
Cheap now
Cheap now: three values stored, not one value and a calculation performed at report time.
Expensive later
Expensive later: derived tax is fine until a rate changes mid-period, a credit note is raised against an old rate, or somebody needs the number that was actually charged rather than the number the current settings would produce.
A document trail attached to transactions 05
Cheap now
Cheap now: the delivery note, the customs entry and the supplier's registration attached to the record they belong to.
Expensive later
Expensive later: this one is not about e-invoicing at all. It is what makes a tax review a retrieval exercise instead of an archaeology one, and it is the thing operators most consistently wish they had started earlier.
Profit attributable by owner 06
Cheap now
Cheap now: cost and revenue attributed to the entity, project and cost centre they belong to as they are captured.
Expensive later
Expensive later: this is not future-proofing, it is a tax that applies today. Corporate income tax reaches the foreign-owned share of profits, so a joint venture needs an attributable position — and reconstructing one from a year of unallocated costs is a genuinely bad month.
What none of that is
Worth being equally clear about the other direction, because "get ready" is the oldest sales line in enterprise software and we do not want to be running it in a slightly better accent.
- It is not a compliance product. There is nothing to comply with yet.
- It is not a reason to buy sooner than your operation needs you to.
- It is not specific to us — a competent local system will do all six, and you should ask them to show you.
- It is not expensive. Five of the six are configuration decisions made once, at setup.
- It is not urgent, which is the whole point and the only genuine advantage this market has over its neighbours.
- It is not a substitute for asking the General Tax Authority what actually applies to you.
If you take one thing from this page: the businesses that will find a Qatari mandate cheap are not the ones who bought early. They are the ones whose records were already in order for reasons that had nothing to do with tax.
Operations in Qatar
If nobody can sell you a deadline, what you are buying is job cost.
The argument above is that this is the one Gulf market where a system gets chosen on whether it runs the business rather than on whether it clears a document. This is what that leaves you buying. An unusual amount of project work per head of population means many jobs running at once, overlapping, sharing the same plant and the same stores — and the failure is consistent: materials in one place, subcontractors in another, plant hire on an email, and a true cost that only exists once the job is finished and it is too late to act on.
Projects
A pipeline where every job carries its own position
Budget and hours per project, cost and bill rates, milestones, and cost attribution pulled from purchases, stock issues, expenses and labour as they happen. A job's position becomes a query rather than a month-end assembly — which is the only version of it that can still change the outcome.
Assets
Plant shared between jobs, with a holder at every point
Generators, compactors, survey kit and tools move between sites on a phone call. Named custody, check-out and check-in, condition at each hand-off and movement history — so a machine charged to one job is not quietly working on another.
Cost attribution
Which venture the cost belonged to, decided at entry
Project, cost centre and department coded as the transaction is captured rather than reconstructed later. Where profit has to be attributed between partners in a venture, a cost that was never coded is a cost somebody has to argue about.
Inventory
Yards, stores and sites that each hold their own stock
Governed transfers between them, in-transit as a state rather than a gap, blind counts and valued variance — because material issued to the wrong job is a costing error that survives to the final account.
Landed cost
Almost everything is imported, so almost every cost lands late
Freight, clearance, port handling and inland haulage arrive on separate invoices weeks after the goods. They attach to the consignment as they arrive and the unit cost moves, rather than disappearing into an overhead line no job can see.
Procurement
Commitments checked while the job can still absorb them
Requisition against a budget line, a threshold that refuses rather than warns, quotation comparison with the award reason recorded, and matching before money moves.
One caution that belongs with the third card. We attribute what you code; we do not decide what belongs to whom. How profit is shared in a venture, and what any share is assessed on, is a question for your adviser — what we guarantee is that the cost was captured against something specific at the moment it was true, rather than allocated by argument afterwards.
Scope, stated plainly
What runs today in Qatar, what we would build, and where we stop on purpose
The first item in the middle column is the one we are asked about most, and the answer there is a straight one rather than a hedge.
Running in the product today
- The riyal as a base currency preset, pegged, with foreign-currency purchases held in their own currency at the rate actually applied rather than a standing monthly one.
- Tax fields on every sales and purchase line, split net, tax and gross at the point of capture — which is worth having at a nil rate precisely because it is cheap now.
- Project, cost-centre and department attribution carried across purchases, stock issues, expenses and payroll cost, so a joint venture has an attributable position rather than an annual reconstruction.
- An asset register with named custody — check-out and check-in, condition at each hand-off, and movement history — across plant, equipment, tools and vehicles. It carries no depreciation and no service history: the value schedule stays with your accountant, and time out of service is not recoverable from it.
- Procurement that refuses above a threshold, with RFQ comparison, three-way matching, and supplier documents whose expiry dates the system watches.
- Landed cost on the consignment, so freight, duty, clearance and handling reach the unit cost instead of an overhead line.
On the roadmap — and commissionable now
- A Qatari e-invoicing integration, the day there is a specification to build against. Until the General Tax Authority publishes one, this is an integration project waiting on its counterparty rather than on us; when it lands, it becomes ordinary work against a real document. We would rather write that sentence than put a readiness badge on a page.
- An Arabic interface and a right-to-left layout. English only, documents included. Doha's commercial floor is heavily English-speaking and this is usually survivable, but a site store or a receiving yard is a different test. Run it with the people who would key transactions.
- A Wage Protection System file and Qatarisation tracking. Our maintained statutory payroll engine covers Kenya only, so no wage file is produced in the layout the Ministry of Labour and the central bank expect, and no nationalisation position is tracked.
- An end-of-service gratuity accrual. Worth separating from the payroll line because it is a real balance-sheet liability under Qatari labour law rather than a filing chore, and accruing it month by month on live employee records is what this adds. Today that lives in your accountant's workbook.
- Interim payment applications, retention and BOQ remeasurement. Our project module is budget, time and cost. A contractor's valuation cycle is a measurement package and we are not one — which matters in this market more than in most, because so much of the economy is main contracting.
Where we point you to a specialist — and the second one is the argument of this page
- Corporate income tax computation and statutory accounts are your adviser's. We do not calculate the foreign-owned share, apportion profit for a return, or file anything with Dhareeba. We hold the attributed records a computation is built from, and your adviser does the rest — which is the same answer we give in every market including our own.
- We will not describe ourselves as "VAT-ready" or "e-invoicing ready" here. The specification has not been published and the implementing law has not been enacted, so readiness is not a thing that can be true yet. A badge claiming it would be the clearest possible signal about how a vendor will handle the rest of your project, and we would rather forgo the badge.
Every item in the middle column is buildable. Wage Protection output, Qatarisation visibility, gratuity accrued month by month on live records, an Arabic interface and a contractor's valuation cycle are all scoped, priceable builds — and gratuity in particular is a balance-sheet liability rather than a filing chore, which makes it the one we would most want to build here. Kenya's eTIMS and payroll engine exist because clients commissioned them. Ask and we will return a specification, a timeline and a price. Electronic invoicing joins that list the day the General Tax Authority publishes a specification, and not one day earlier.
A market with no mandate cuts both ways and we should say so. It means nothing here forces you to buy, which is genuinely to your advantage. It also means you cannot use compliance to justify a decision internally, so the case has to be made on operations — materials, plant, cost and evidence — or not at all. If that case is thin for you right now, the correct answer is to wait, and we will say so on the first call.
How this starts
Three moves, in this order
01
Establish what actually applies to you today
Corporate income tax reaches the foreign-owned share of profits and the treatment differs inside the Qatar Financial Centre. Get that answered by your tax adviser or the General Tax Authority before anybody demonstrates software, because the answer changes what "attributable" has to mean in your accounts.
02
Do the six cheap things while nothing is urgent
One invoice sequence, tax fields populated at whatever rate applies, counterparty identifiers as structured fields, net and tax split at capture, documents attached, costs attributed. None of it requires knowing what a future mandate says, all of it is configuration rather than construction, and it is the entire reason a market without a deadline is an advantage.
03
Then buy for the operation, not the announcement
Take one live project or one real month of purchasing and run it end to end. If the position it produces does not tell you something you did not already know, stop — you do not have a system problem yet, and there is no deadline pretending otherwise.
Read before you shortlist
Guides for this market
Implementation & Rollout
Qatar Has No Deadline. That Is the Whole Argument.
Every neighbouring market is being sold a mandate. Qatar has no VAT and no e-invoicing regime in force — which removes the easiest reason to buy software and leaves only the good one.
Read
Integrations & Data
How to Prepare for an E-Invoicing Mandate Nobody Has Published
Fiscal regimes differ enormously in architecture and almost not at all in what they assume about your records. Six data conditions, five of which are configuration decisions made once.
Read
Implementation & Rollout
Buying Operations Software in Qatar: A Straight Guide
No mandate means the decision has to stand on operational evidence alone. Three honest positions including buying nothing, seven things worth scoring, and what a joint venture's attribution really costs.
Read
Point of Sale
Three Tenders, and the One That Was Never Real
This till takes cash, one mobile-money rail and a card. It briefly took a fourth on refunds — store credit — which reversed the sale, returned the stock, and recorded the debt to the customer nowhere at all.
Read
Reports & BI
One Place That Knows What Time It Is
A report schedule in this product carries its own timezone and computes its next run in it. The deadline engine three modules away has no timezone at all. The capability exists, once, in the place where getting it wrong matters least.
Read
Projects & Job Costing
What a Project Clone Carries, and What It Resets by Design
Copying a project rebuilds the whole structure — tasks, subtasks, dependencies, milestones, checklists — and deliberately resets every date, assignment and trace of progress. The list of what it resets is the most opinionated thing in the module, and we can tune it to your templates.
Read
Questions we are asked here
Straight answers, and what we would build the day there is a specification
Does Qatar have VAT?
No. Qatar signed the GCC unified VAT framework agreement in 2016 and has not enacted implementing legislation, so there is no value added tax in force, no registration and no VAT charged on supplies. It has been widely expected for several years and the General Tax Authority's portal reportedly carries fields anticipating it, but expected is not legislated and we are deliberately not printing a rate here — Qatar has not printed one either. Our tax configuration carries Qatar at nil for exactly that reason, which is a change we made rather than a default we inherited. Confirm the current position with the General Tax Authority or your adviser.
Are you "VAT-ready" for when it arrives?
We are going to give you the unhelpful honest answer instead of the helpful dishonest one. Nobody is ready, because there is no specification to be ready for — no rate, no return format, no filing mechanism, no e-invoicing model. Any vendor telling you otherwise is either describing a generic tax-rate field, which every accounting system has had for thirty years, or hoping you will not ask the follow-up question. What we can tell you is what we do when a specification is published, because we have done it before: Kenya's eTIMS is a real, maintained integration in this product, built against a real document. That is the shape of what would happen here, and it would happen after publication, not before.
What about the electronic invoicing law that was approved?
A draft electronic invoicing law and its implementing regulations were approved at Council of Ministers level in 2026. What has not accompanied it publicly is a timetable, a technical specification, a document format or a model — whether Qatar goes for clearance like Saudi Arabia, a network like Oman, or something of its own. Those details are the entire content of an integration project, so until they exist there is nothing to build. Watch the General Tax Authority rather than vendor newsletters, and treat any specific date you are quoted as a sales device until you can find it published.
We are a joint venture. Does the tax position affect what we should buy?
Yes, and it is the most under-discussed thing on this page. Corporate income tax reaches the foreign-owned share of profits, so somebody has to be able to say which profits are attributable to whom. That is straightforward if cost and revenue carried an entity, project and cost-centre attribution as they were captured, and genuinely difficult if they did not — reconstructing a year of unallocated cost is a bad month and an argument. We do the attribution side properly: purchases, stock issues, expenses and payroll cost all carry project, cost centre and department. We do not do the computation, the apportionment or the filing, and would not want to.
Do you handle Wage Protection System files, gratuity or Qatarisation?
No to all three. Our maintained statutory payroll engine covers Kenya only, so no wage file is produced in the layout the Ministry of Labour and the central bank expect, no nationalisation position is tracked, and — the one worth naming separately — end-of-service gratuity is not accrued month by month on live employee records. That last one is a genuine balance-sheet liability under Qatari labour law rather than a filing chore, and in most operations it lives in an accountant's workbook and is discovered at settlement. Keep the statutory half with a Qatari payroll provider. What travels is employee records, contracts, leave with balances, and payroll cost allocated to projects and cost centres. That is on the roadmap rather than a boundary, and it is commissionable now. A Qatari engine producing wage files in the expected layout, accruing end-of-service gratuity month by month on live records, and showing the Qatarisation position before a deadline rather than after one, is scoped, priceable work. Kenya's eTIMS transmission and its maintained statutory payroll engine both exist because Kenyan clients needed them and commissioned them — neither arrived on a roadmap by itself. Gratuity in particular is worth separating out, because it is a balance-sheet liability rather than a filing chore and it is the item on this roadmap we would most want to build. The advice we would give before you ask: a local bureau already filing every month is cheaper than commissioning us and correct by default. We will take the build if you want it; we would rather you did not need it.
We are a main contractor. Do you handle payment applications and retention?
No, and it matters more here than in most markets because so much of Qatar's economy is contracting. There is no interim payment application, no bill-of-quantities remeasurement, no retention held and released against a certificate, no variation register and no subcontractor back-charge workflow. Our project module is budget, hours, milestones, cost rates and cost attribution — the cost side, not the valuation side. What we cover properly is the half that usually leaks: materials procured and received against a job, site stores as real stock locations, plant and tools under named custody, consumption attributed to the project, and offline capture that works where there is no signal. Most contractors we work with keep a measurement package for valuation and use us underneath it. That is on the roadmap rather than a boundary, and it is commissionable now. A valuation cycle — interim applications, certified amounts, retention held and released, remeasurement against a bill of quantities — is a real module with a real price. Given how much of this economy is main contracting, it is also the roadmap item most likely to be commissioned here. If this is the thing standing between you and a decision, say so and we will come back with a written specification, a timeline and a price before you commit to anything. What we will not do is print a date nobody has paid for.
Where does support come from, and does the working week work?
Nairobi, with remote onboarding and live training in English. Doha is UTC+3 and so is Nairobi, so there is no time difference at all — your working hours and ours are the same hours. The working week differs and is configured rather than assumed: set Friday and Saturday as non-working once and the organization's leave arithmetic, workflow due dates and escalation timers, and helpdesk response clocks all read that setting, along with the public holidays you enter.
No deadline, so bring a real problem instead
Come with one live project or one real month of purchasing. We will run it through and show you the position at the end. If it tells you nothing you did not already know, we will say so — there is no mandate here for either of us to hide behind, which makes this an unusually honest conversation to have.