Skip to content
Quickship Technologies logoQuickshipTechnologies

CustomsUAE & KSA7 min read

What to Check Before Buying Clearing Agent Software UAE & KSA

What to check before buying clearing agent software for UAE and Saudi work: a checklist covering Fasah, ZATCA, Dubai Customs, Arabic and audits.

By Quickship Editorial Team · Published 31 October 2026

Looking for the software itself? See our customs clearance software UAE, free to try for 3 days.

What to check before buying clearing agent software for UAE and Saudi work comes down to six things: Fasah and ZATCA fit, UAE customs system connectivity, Arabic and English output, audit-ready document storage, multi-client access, and a live test on a real shipment. If a vendor cannot show all six on your own files, keep looking. The checklist below gives you the questions to ask and the proof to ask for.

What to check before buying clearing agent software for UAE and Saudi work?

Check the six areas in the table below, and ask the vendor to demo each one rather than describe it. Slide decks are easy. Your files are not.

Area What to ask Proof to request
Fasah and ZATCA How does it handle Fasah filing, broker authorizations and deadlines? A KSA file from start to finish
UAE systems Which UAE customs systems does it connect to, and how? A UAE file for Dubai and one other emirate you use
Arabic and English Can it produce both, and store certified translations? A bilingual document sample
Audit storage How long are files kept, and can you export them fast? A retrieval test on an old file
Multi-client access Can staff and clients see only their own data? Two test clients and two roles
Sample shipment Can it run your real workflow? A paid or free trial on anonymised files

Write your own scorecard from this table. Mark each row pass, partial or fail. Do it before you see pricing, so price does not blur the result.

Does it fit Fasah and ZATCA rules for Saudi clearance?

It should, and it should support the steps ZATCA actually publishes. ZATCA says importers must complete Fasah clearing procedures and the customs declaration at least 48 hours before the shipment reaches the port of entry. They can file directly or through a customs broker. That 48-hour window should show up in your software as a visible deadline per shipment, not a note in someone's head.

Ask the vendor these questions:

  • What does "Fasah integration" mean? It might mean a live connection. It might mean the software prepares data that your staff re-key into Fasah. Both can be useful. Only one saves typing. Make the vendor say which.
  • How does it track broker authorizations? Under ZATCA's customs journey, an importer or exporter can delegate a broker at a specific customs port, for import, export or both. Traders can set single or multiple use. The ZATCA user manual says the broker accepts or rejects the authorization in Fasah, and that authorizations have start and end dates and can be cancelled. Your software should store the port, scope and expiry for each client, and warn you before one lapses.
  • Does it prompt for the standard documents? ZATCA lists the commercial invoice, the bill of lading and a certificate of origin (not needed if the origin is clearly established). Other documents depend on the goods, so ZATCA points you to the Customs Tariff or your broker. The software should let you add document rules per tariff line rather than fix one list for everyone.

For a step-by-step view of the process itself, see our guide to Fasah and Saudi customs clearance.

Does it connect to UAE customs systems?

Ask which UAE systems it supports by name, and what "support" means for each. The UAE does not run one single customs front end. Dubai Customs runs Mirsal 2, which it describes as its paperless electronic clearance system. Other emirates use their own systems. A forwarder working Jebel Ali and KEZAD, or Dubai and another emirate, needs the vendor to show each route.

Questions to put to the vendor:

  1. Which UAE customs systems do you work with today? Name each one.
  2. Is data exchanged live, by file upload or by manual re-entry?
  3. How do you handle Dubai Trade tasks, such as payments and delivery orders? Dubai Trade's clearing-agent page lists these, but it looks dated, so confirm the current process with Dubai Customs.
  4. What happens when a system changes its format? Who updates your software, and how fast?

Also ask about paper. In 2023, Dubai Customs Notice 04/2023 extended the window to submit hardcopy documents from 14 to 30 days after online filing, per EY's summary. Rules like this change. Your software should track a hardcopy due date per declaration, and you should confirm the current period with Dubai Customs.

Can it produce Arabic and English documents?

It must, because Saudi tax rules treat Arabic as a requirement. ZATCA's input tax guideline says tax invoices must include the relevant details in Arabic, in addition to any other language. It adds that ZATCA may accept a non-Arabic invoice as alternative evidence for an input tax deduction if the taxpayer provides a certified translation on request. The guideline is dated July 2020, so check for a newer version.

For a clearing agent, that means testing three things:

  • Right-to-left text. Type Arabic consignee names and addresses. Check they display and print correctly, with no broken letters or reversed numbers.
  • Bilingual output. Print a declaration summary and an invoice with Arabic and English together.
  • Translation storage. Can you attach a certified translation to the original document, so both are retrieved together?

A common mistake is checking Arabic only on screen. Print it and export it to PDF too. Many tools fail at that step.

How should it store documents for audits?

It should keep every declaration and its supporting documents together, searchable by shipment, client and date, for at least the period the authority requires. The Dubai Customs Customer Guide says documents related to a declaration must be kept for 5 years from the date of clearance, and that customs may ask for contracts, correspondence and other related documents. The EY summary of Notice 04/2023 says five years from the date of filing. Because the two differ, count from the earlier date or confirm with Dubai Customs.

The Customer Guide also says Dubai Customs keeps declarations in its own e-Archive and that clients can request an audit of their records. Your copy still matters. Do not rely on the authority's archive as your only record.

Run this retrieval test with the vendor:

  1. Pick a file from a past shipment.
  2. Ask them to find it by client name, then by bill of lading number, then by date.
  3. Ask for a full export of the file, with invoice, packing list, bill of lading and correspondence.
  4. Ask who can delete or edit it, and whether changes are logged.
  5. Ask what happens to your data if you leave the service, and in what format you get it back.

Also ask where the data is hosted. Your files hold IDs, trade licences and company data, so UAE and Saudi PDPL obligations apply to how you handle them.

Does it handle many clients and many staff safely?

It should give each client and each staff role its own view, and keep the data apart. A clearing agent acts for many importers at once. One wrong click should not show Client A's invoices to Client B.

Test these points:

  • Roles. Can you give a junior clerk data entry rights but no right to delete or approve?
  • Client views. Can an importer log in to see only its own shipments and documents?
  • Authorization tracking. Is there a list of each client's Fasah authorization, its port and its end date?
  • No shared passwords. Under ZATCA's process, the importer creates the authorization in its own Fasah account. Software should not need your client's login. If a vendor asks for client passwords, walk away.
  • Activity log. Can you see who opened, changed or exported a file?

How do you test a vendor with a sample shipment?

Run one UAE and one Saudi file through the software, using anonymised data from jobs you have already done. Here is a worked example. Say a Dubai broker picks a past sea import into Jebel Ali and a past road import into Saudi Arabia via Dammam. The broker asks the vendor to run both.

Use this sequence:

  1. Create the client. Add a test importer with a trade licence or Commercial Registration number, and set up a user for it.
  2. Enter the shipment. Add the invoice, packing list and bill of lading. Time how long it takes.
  3. Prepare the declaration. Check tariff lines, values and parties. Look for warnings on missing documents.
  4. Check the Saudi deadline. Confirm the software shows the 48-hour Fasah window for the Saudi file.
  5. Print in Arabic and English. Check layout, text direction and names.
  6. Store and retrieve. Close the job, then find it again by three different searches.
  7. Break something on purpose. Leave out a document, enter a wrong value, expire an authorization. See whether the software warns you.
  8. Ask for the bill. Get the price for your volume in writing, including what is extra.

Score each step against your table. Ask your clearing team, not the vendor, to do the clicking. If they find it slower than your current method after a week, that is useful information.

Quickship's Customs Clearance module is built for UAE and KSA clearing work. Apply this same checklist to us as you would to any other vendor, and ask for the sample shipment test before you commit.

Frequently asked questions

Can one clearing agent software cover both UAE and Saudi declarations?

It can, if the vendor supports both sets of rules in one system. Ask to see a UAE file and a KSA file side by side, with the right documents, tariff handling and filing steps for each. Do not accept a single generic declaration form renamed for two countries.

Do I need Arabic on every customs document?

Not on every one, but ZATCA's input tax guideline says KSA tax invoices must carry the relevant details in Arabic, in addition to any other language. Your software should output Arabic and English fields cleanly, and keep certified translations on file in case ZATCA asks for one. Check requirements for each document type with the authority.

How long should a clearing agent keep customs files?

Dubai Customs says documents related to a declaration must be kept for 5 years. Its Customer Guide counts from the date of clearance, while a 2023 notice summarised by EY counts from the date of filing. Count from the earlier date or confirm with Dubai Customs, and ask what rules apply to your Saudi files.

Should the vendor access my clients' Fasah accounts?

No. Under ZATCA's process the importer creates a Customs Broker Authorization in its own Fasah account, and the broker accepts it. Software should track those authorizations, not ask for client passwords. If a vendor asks for client logins, treat it as a red flag.

Sources

  1. ZATCA: Import instructions (Fasah, 48 hours, documents)
  2. ZATCA: Customs journey (Fasah registration and Customs Broker Authorization)
  3. ZATCA: User manual for authorizing a customs broker
  4. ZATCA: Input tax deduction guideline (Arabic invoice requirement)
  5. Dubai Customs: Customer Guide (record retention, e-Archive)
  6. EY: Dubai Customs amends the grace period for declaration supporting documents (Notice 04/2023)

Rules and fees in the UAE and Saudi Arabia change. This guide reflects the sources above on 31 October 2026. Check the official source before acting on it.

Customs Clearance Module

Clearance software for the UAE and KSA, integrated with customs and clearing agents.

Book a demo

More on customs

Instant quote