Customs Clearance Software: UAE and Saudi Buyer's Guide

Customs clearance software is the system of record for an import before it becomes stock: one file per inbound shipment holding the goods, the documents, the people filing and the state of the entry. For an importer serving both the UAE and Saudi Arabia, the hard part is not the feature list: Dubai, Abu Dhabi and Saudi Arabia file through different platforms, with different registrations, broker rules and deadlines. This guide covers what the record must hold, what differs across the three, and what to test before you buy.

What customs clearance software has to cover

Four jobs sit under the dashboards:

1. Hold the shipment record. One record per inbound shipment, from supplier dispatch to stock received, carrying the port it lands at, because the port decides the rulebook.
2. Hold the documents. Commercial invoice, packing list, bill of lading or airway bill, certificate of origin and product approvals, kept against the shipment rather than in an inbox. Dubai Customs' examination policy has the officer reconcile exactly those documents against each other, then against the declaration (policies booklet).
3. Get the data to whoever files. In Dubai, Mirsal 2, through the Dubai Trade portal or a business-to-government link (Dubai Customs). In Abu Dhabi, Abu Dhabi Customs and ATLP. In Saudi Arabia, Fasah, where ZATCA says the data may be presented directly or through a customs broker (import instructions).
4. Show status per country. Dubai clears an online declaration within seconds unless customs intervene for further verification, with documents still due at the counter afterwards (customer guide).

One company, three customs platforms

A UAE and Saudi importer is not dealing with one authority or one portal.

"Integrated with customs" is not one claim, it is three, so ask which emirate or country each covers. And a Fasah broker authorisation tied to Jeddah Islamic Port means nothing at Jebel Ali.

The record each shipment needs before anyone files

Dubai Customs' examination policy describes how an officer works: the invoice is reconciled with the packing list, the certificate of origin, the bill of lading and the marks and numbers, then with the declaration. That is your specification.

Deadlines the software should be counting

The clocks that cost money when nobody is watching them:

1. Filing before arrival in Saudi Arabia. ZATCA's import instructions say clearing procedures and the customs declaration must be completed at least 48 hours before the shipment arrives at the port of entry. Flag it at estimated arrival minus a working day or two. The rest of that sequence is in our Fasah guide.
2. The customs client code in Dubai. Dubai Customs' policies booklet gives sixty days from licence expiry to renew the code, and suspends it if the client processes no customs transactions for six months. A seasonal importer can lose its code quietly between shipments.
3. The Saber shipment certificate. Saber's shipment certificate service for imported commercial products takes one to two working days to issue, costs SAR 350 before VAT, and the certificate is valid for 90 days. Start it early enough that the certificate is live when the goods arrive, and see our Fasah guide for where it fits.
4. Duty payment in Saudi Arabia. ZATCA's customs duty deferral e-service offers a 30 day postponement, through a bank guarantee or a documentary obligation, with financial statements provided through the Qawaem programme. If you use it, the deferral date belongs on the shipment.
5. The point of no return. The FTA's VAT Import Declaration User Guide says that once the declaration is sent to the FTA, the customs system will not allow any further editing of the form, and the only states it can change to are approved or declined. Put the review before submission.

Giving your clearing agent access without losing control

ZATCA's import instructions allow the importer to present the data directly or through a customs broker. Either way the software holds the record they work from.

Dubai Customs' policies booklet is direct about brokers, and it maps onto how access should be set up. The broker is responsible for the accuracy of the details in the goods declaration, for the accuracy and completeness of all electronic communications sent via the Integration System, and for keeping that data in safe custody and confidence. The licence comes from the Customs office, and its conditions are registration with the Department of Economic Development and that AED 50,000 guarantee (importer of record).

So the agent record should carry what the authorities work from: in Dubai the broker's licence, in Abu Dhabi the delegation in Abu Dhabi Customs systems, in Saudi Arabia the Fasah authorisation, which ZATCA grants for a specific port, a stated duration, import or export or both, single or multiple use. Record which authorisation covers which shipment.

A worked example

Say a Dubai brand imports 400 units of a small kitchen appliance: 250 through Jebel Ali, 150 through Jeddah Islamic Port for a Saudi marketplace. The figures are made up to show the shape of the work.

The UAE half runs on one invoice, packing list and bill of lading, the brand's customs client code and a Dubai agent filing through Dubai Trade. The Saudi half uses the same invoice but needs a Saudi importer with a Commercial Registration, a Fasah account, a broker authorised for Jeddah, Saber coverage, and a declaration completed 48 hours before the vessel arrives.

Corrected once on one record, the unit price reaches both agents and the 48 hour Saudi countdown sits on the shipment, with landed cost following from the same lines (landed cost calculation).

What to test in a demo

Bring last month's hardest shipment, not sample data.

1. Take one invoice covering a shipment landed at Jebel Ali and one at Jeddah Islamic Port. Can one record hold both?
2. Ask where the HS code lives, whether it holds the full 12 digit GCC tariff code, and whether it carries to the next shipment.
3. Open the clearing agent record and look for the fields the authorities use: a Dubai broker's licence number, a Fasah authorisation with its port and period.
4. Ask which of Mirsal 2, ATLP and Fasah the integration claims, by what channel, and what happens when a submission is rejected.
5. Ask how a Mirsal 2 or Fasah hold reason is captured, who is told, and whether it is a field you can report on.

What commonly goes wrong

• Documents are attached but the data is not. A folder of PDFs does not stop an invoice disagreeing with a packing list (more in our guide to customs clearance time in Dubai).
• Classification drifts. The Mirsal 2 and Fasah declarations carry different HS codes for the same product, so duty and restrictions differ by port.
• Corrections arrive too late. Dubai Customs lists declarations amended after registration among the cases for full inspection, so a price fix made after filing is paid for at the port.
• Nobody owns the Saudi side. Settle who the Saudi importer of record is, with a Commercial Registration and a Fasah account, before the goods ship.

Where Quickship fits

Quickship's Customs Clearance Module is built around the record described above: every inbound shipment with its invoice, packing list, airway bill and certificates kept against it, declaration data prepared once and passed to customs systems through the integrations in place, clearing agents receiving jobs and updates through the platform rather than by email, and each shipment showing its clearance stage so a hold is visible the day it happens. Released shipments carry across as expected stock in the Inventory Module.

Whichever product you choose, apply one test: can one person say, in under a minute, whether the Jebel Ali shipment cleared and whether the Jeddah one has its Saber certificate?