The Import Box on Your VAT Return Is Filled In by Someone Else

There is one figure on a UAE trading company's VAT return that the company does not calculate. The import box is populated from customs declarations filed against its TRN — by clearing agents, on dates the company did not choose, from values the company did not enter.

Every other line comes out of the accounting system. That one comes out of the customs system.

They are two different records of the same goods, and the interesting question is not whether they agree. It is whether anybody in the business is asked, monthly, to explain why they do not.

Two ledgers, one shipment

Five rows, five ways for two correct records to differ. In practice the recurring ones are:

• Timing. A container cleared on the 30th and received on the 3rd sits in one month for customs and the next for accounts. On a business shipping weekly this never nets to zero, it just rolls.
• Valuation. Duty is assessed on CIF. If your supplier invoiced FOB, customs adds freight and insurance to reach a value your purchase ledger has never held.
• Exchange rate. The declaration uses the customs rate on the clearance date. Your ledger uses the rate on your invoice date.
• Declarations you did not expect. A returned shipment, a sample, a warranty replacement, a consignment moved by a third party using your TRN.

The last one is the one that produces the unpleasant surprises, because it is the only one where the figure in the box relates to goods your system has no record of at all.

The shape of it

One shipment, two records, one box on the return

One container of goods

It is recorded twice, by two organisations, from two documents, and neither copy is wrong. One of them is filed against your TRN before your accounts team has seen the supplier's invoice.

The customs record

Filed by the clearing agent, against your TRN, on a date the company did not choose.

The purchase ledger

Built by your accounts team from the supplier's invoice, keyed to your own purchase order.

Five places the two are assembled differently

1. 1. The document

   The customs record: The declaration.

   The purchase ledger: The supplier's invoice.

   What that does: Two complete records of the same goods, built by people who have never met and have never compared them.

2. 2. The date

   The customs record: Clearance.

   The purchase ledger: The invoice date, or the receipt date.

   What that does: One month for customs and the next for accounts, on any shipment that crossed a month end. In a business shipping weekly the difference rolls forward rather than nets out.

3. 3. The value

   The customs record: CIF, plus whatever customs assesses on top of it.

   The purchase ledger: The invoice value, at your exchange rate.

   What that does: A supplier who invoiced FOB has left customs to add the freight and the insurance, so the declared value is a figure your ledger has never held.

4. 4. The exchange rate

   The customs record: The customs rate on the clearance date.

   The purchase ledger: Your rate on your invoice date.

   What that does: The same goods, in dirhams, twice, at two rates set days apart by two bodies for two purposes.

5. 5. The key

   The customs record: The declaration number.

   The purchase ledger: The purchase order.

   What that does: Nothing joins them — so a declaration you did not expect, a return or a sample or a warranty replacement or goods moved on your TRN by somebody else, has no purchase order to be missing from. It appears in the box attached to goods your system has no record of.

The import box on the VAT return

One figure, populated from the customs record. Every other line on the return comes out of the purchase ledger. The two will not agree by accident, and the monthly report that would explain why — declarations filed against your TRN, set against shipments in your system, with the unmatched ones named — is the control almost nobody builds.

Duty is a cost; VAT should not be

Worth separating, because they are routinely handled by the same person on the same day and behave nothing alike.

Customs duty — 5% on most goods under the GCC common tariff, with higher rates on a short list and exemptions on another — is a real cost. It never comes back. It belongs in the item's landed cost, and if it is posted to a duty expense account instead, every margin figure per item is overstated by it.

Import VAT under the reverse charge is not a cost at all for a registered business making taxable supplies. It is declared and recovered in the same return, net effect nil. Treating it as a cost — which happens whenever a clearing agent's disbursement invoice bundles duty and VAT into one line and it gets coded to one account — both inflates cost and loses the recovery.

That single bundled line on the agent's invoice is, in our experience, the most common source of both errors at once. It needs splitting at the point of entry, not at year end.

What a system has to hold to survive a review

Not much, but all of it, and none of it is standard.

1. The declaration number on the shipment, so a figure in the import box can be traced to goods.
2. The customs value alongside the invoice value, with the difference visible rather than reconciled away.
3. Duty as a landed cost component, allocated onto items.
4. Import VAT as a tax, not a cost, posted through the reverse-charge mechanism.
5. A monthly comparison of declarations filed against your TRN with shipments recorded in the system — including declarations with no matching shipment.

Point 5 is the whole control, and it is the one nobody builds. It answers the only question an auditor genuinely wants answered: does the number the authority already has match the goods you say you bought?

A company that can produce that comparison, month by month, with its exceptions listed and explained, is in a different position from one that starts assembling the answer after the query arrives. That difference is most of what surviving an FTA audit actually consists of, and it costs nothing once the declaration number lives on the shipment.

The short version

The import figure on your return is assembled from customs declarations; your ledger is assembled from supplier invoices; the two use different dates, different values and different exchange rates, so they will never agree by accident and are rarely reconciled on purpose.

Duty is a cost that belongs on the item. Import VAT is not a cost at all, and treating it as one is expensive twice. The clearing agent's single bundled line is where both mistakes are made.

And the control that matters is one monthly report nobody runs: declarations against your TRN, compared with shipments in your system, with the unmatched ones listed by name.

Where this sits alongside the rest of a UAE tax file is in Odoo, VAT and e-invoicing in the UAE and the e-invoicing readiness plan. The trading and warehousing side of it, with the customs entry on the same record as the goods, is Logix.