Inclusive or exclusive: the 5% you eat without noticing

There is a five-word question that decides whether you keep an extra AED 4,762 on a hundred-thousand-dirham deal: is that inclusive of VAT?

Every service business in the UAE answers that question on every quote it issues. Most answer it accidentally, by template inheritance, by habit, by whoever happens to build the quote that day, and the businesses answering it accidentally are, in aggregate, donating serious money to nobody in particular. Not to the government, which collects the same tax either way. Not to the client, who agreed to a number. The money simply evaporates from the margin, invisibly, which is the worst way to lose anything, because invisible losses never get fixed.

This article walks through the mechanics, why the error is structural rather than careless, what it compounds to across a year, the second failure hiding behind the first, and the three-line fix.

The mechanics, in one worked example

Take a deal quoted at AED 100,000, with VAT at 5%.

Quoted "plus VAT" (exclusive): you invoice AED 105,000. The client pays 105,000, you remit 5,000 to the FTA, and you keep AED 100,000. Your quote meant what it said.

Quoted "inclusive of VAT": the tax lives inside your number. You invoice AED 100,000, of which the taxable amount is 100,000 ÷ 1.05 = AED 95,238, and the VAT is AED 4,762. You remit the 4,762 and keep AED 95,238.

Same headline number on the quote. A difference of AED 4,762 in what your business actually earns, which on a typical service margin is not a rounding error, it can be a fifth of the profit on the job.

Neither treatment is wrong. Inclusive pricing is a legitimate commercial choice, often the kind one in consumer-facing work. The failure is not choosing inclusive. The failure is not choosing at all, and letting the word be decided by whichever old proposal got copied at 6pm on a Thursday.

Why it happens structurally

Nobody prices a deal and then deliberately throws five percent of it away. The error enters through the sides, and it enters structurally.

It enters through templates. The proposal for the new deal starts life as the proposal from an old deal, and it inherits that deal's VAT language along with its fonts. If your template library contains both inclusive and exclusive ancestors, and after a few years it always does, then your pricing policy is effectively random, determined by document genealogy rather than by anyone's decision.

It enters through deadline pressure. Quotes get built at the last responsible moment, by whoever is free, and the VAT line is the least interesting line on the page. Under pressure, the least interesting line is the one that gets inherited rather than examined.

It enters through ambiguity in conversation. "It'll be around a hundred thousand" gets said on a call. The client hears a total. The salesperson meant a fee. Neither is lying; the word "inclusive" simply never occurred, and by the time the invoice makes the difference concrete, someone is having an awkward conversation, and awkward conversations with clients get resolved in the client's favour more often than not.

And critically, the error hides. AED 100,000 inclusive is a perfectly plausible number. Nothing about it looks wrong on the invoice, in the ledger, or in the month-end totals. The discovery mechanism, for most firms, is the accountant at filing time, months after the money mattered, when it is a historical curiosity rather than a recoverable margin.

What it compounds to

Run the arithmetic across a year rather than a deal, because that is where it stops being a detail.

A firm doing thirty projects a year at an average of AED 100,000, with treatment decided by template inheritance, might plausibly get the intended word wrong on a fifth of them, six deals. Six times AED 4,762 is roughly AED 28,500 gone. If the same sloppiness ever touches larger deals or bigger portions of the book, and it does, because the mechanism is random, the number climbs quickly into six figures.

Here is what makes it worse than a normal loss: it gets misdiagnosed. The leak never presents as "we are inconsistent about VAT language". It presents as "margins seem thinner than they used to be", and the natural response to thin margins is to raise prices, which answers the wrong question with the bluntest instrument available, and occasionally costs deals that the correct fix would have kept.

The second failure hiding behind the first

There is a subtler problem underneath the wording problem, and it concerns time.

Suppose the VAT rate ever changes. Any system that computes tax at display time, which is what a spreadsheet formula does, and what many simple tools do, will silently rewrite history: reopen last year's invoice and it recalculates at this year's rate. Your documents stop agreeing with your filed returns. Your audit trail now contains paper that contradicts itself, and reconstructing what was actually charged becomes forensic work.

The correct behaviour is unglamorous and absolute: the rate is frozen onto each invoice at the moment it is issued. An invoice from the 5% era says 5% forever, no matter what the rate becomes. This is one of those requirements that seems theoretical until the day it isn't, and on that day it is the difference between a clean audit and a very long week. It is also about to matter more: as the UAE moves toward structured e-invoicing, invoice data becomes something machines read and cross-check, and self-inconsistent history stops being merely embarrassing.

The three-line fix

The fix requires no software, though software makes it automatic. Three rules:

1. Decide the treatment once, per deal, at deal level. Not per document, not per template, not per person. The deal record says inclusive or exclusive, and every document generated from that deal obeys it. Write it into your quoting checklist today: "VAT treatment: decided and written on the deal."

2. Compute the tax in exactly one place. One formula, one engine, one source of truth. The moment two documents can compute VAT independently, they will eventually disagree, and the disagreement will land on a tax document.

3. Freeze the rate on issue. Every invoice carries the rate that applied the day it was raised, permanently.

In Trazer these three rules are not policies but construction: the treatment is a field on the deal, one engine computes every tax line, and the rate freezes onto the invoice at issue, then posts straight into Zoho Books so the FTA-facing books and the operational system agree by design. Ten currencies get the same discipline, with the FX rate frozen per deal at agreement, because "what did we actually earn" should never depend on what the dirham did last Tuesday.

But start with the checklist line. It costs nothing, it takes effect on the next quote you send, and the first time it catches an inherited "inclusive" on a deal you meant to price "plus VAT", it will have paid for this article's reading time roughly five thousand times over.

Answering the client-side question, before it becomes an argument

One more scenario deserves its own paragraphs, because it is where the wording problem most often turns into a relationship problem: the client who believed the number was inclusive when you meant it exclusive.

It happens most readily with first-time clients and with businesses used to consumer pricing, where every number they ever see includes tax. Your proposal says AED 100,000, they budget AED 100,000, and the invoice for AED 105,000 lands as an unpleasant surprise. You are contractually correct and commercially damaged, because no client enjoys discovering that the number in their head was wrong, whoever's fault the discovery is.

The prevention is cheap and worth systematising. Say the treatment out loud in the pricing conversation, not just in the document: "that's one hundred thousand plus VAT, so a hundred and five all-in" costs four seconds and eliminates the entire category of surprise. Put both figures on the proposal, fee and total payable, so there is no arithmetic left for the client to do wrong. And when a deal genuinely must land on a round all-in number, and in this market sometimes it must, then choose inclusive deliberately, work backwards to the real fee of AED 95,238, and check your margin against that figure, not against the headline. An inclusive deal is only a mistake when you priced it as if it were exclusive.

Handled this way, the VAT line stops being a trap and becomes a small professionalism signal: the firm that is precise about tax wording, a client reasonably assumes, is precise about scope and delivery too.

If you want to see the structural version, where the question is asked once and then becomes impossible to get wrong, bring a recent quote to a thirty-minute walkthrough and we will run it through live.