What Is Mirsal 2? A Guide for UAE Clearing Agents and Freight Forwarders

If you work in customs clearance in the UAE, Mirsal 2 is not new to you. You have filed hundreds — perhaps thousands — of declarations through it. You know how the system works. You know where the fields are. You know which documents need to be uploaded.

And yet, rejections still happen. Rework still eats into your day. Your team still spends hours transferring data from commercial invoices, packing lists, and bills of lading into the system — manually, field by field.

The problem is not Mirsal 2. The problem is what happens before you open it.

What Is Mirsal 2?

Mirsal 2 is the customs declaration management system used by Dubai Customs and operated through the Dubai Trade Portal. It is the mandatory channel through which all import, export, and re-export declarations are submitted for goods moving through Dubai.

The system is used by:

• Licensed UAE customs brokers
• Clearing agents operating under freight forwarders
• Broker Representatives filing on behalf of importers and exporters
• Logistics companies with in-house clearance teams

Mirsal 2 handles the full declaration lifecycle — from initial filing and document upload through to duty assessment, inspection assignment, and release. It connects to the broader Dubai Trade ecosystem, including the Port Community System and free zone authority systems.

For goods entering or leaving through Dubai, there is no alternative. Mirsal 2 is the system.

What Mirsal 2 Requires From a Clearing Agent

A standard customs declaration in Mirsal 2 requires structured data extracted from multiple source documents. For each shipment, a clearing agent typically needs to prepare and enter:

• Importer and exporter details
• Consignee and notify party information
• HS code (12-digit harmonised tariff classification)
• Country of origin
• Gross and net weight
• Package count and description
• Commercial value and currency
• Incoterms
• Port of loading and port of discharge
• Document references — invoice number, bill of lading or airway bill number
• Supplementary data where required for restricted or controlled goods

Each of these data points must match across the commercial invoice, packing list, and transport document. Any discrepancy — a different value, a mismatched description, a missing origin declaration — creates grounds for rejection.

Why Mirsal 2 Rejections Happen

Rejection rates of 10–15% are common for clearing agents in active operational environments. Most agents accept this as a normal cost of doing business. It should not be.

The most common rejection causes are not Mirsal 2 errors. They are data preparation errors:

1. Value discrepancies — The declared value in Mirsal 2 does not match the commercial invoice.
2. HS code mismatches — The classification used does not align with the product description or previous shipment history.
3. Document field inconsistencies — A consignee name appears differently across the invoice, packing list, and bill of lading.
4. Missing supplementary data — Required fields for specific commodity types are left incomplete.
5. Origin errors — Country of origin is incorrectly declared or not supported by the certificate of origin.

Each rejection means time lost, a customer query, an internal review, and a corrected resubmission. For high-volume clearance operations, this compounds across every working day.

The Real Problem: Manual Data Transfer Before Submission

Clearing agents know Mirsal 2. What costs them time and accuracy is the step before it — extracting data from documents and preparing it for entry.

The typical pre-filing workflow in most UAE clearing operations looks like this:

1. Documents arrive by email, WhatsApp, or client portal
2. The clearing agent reviews the commercial invoice, packing list, and transport document manually
3. Data is transferred — field by field — into Mirsal 2 or a staging template
4. HS codes are looked up manually, cross-referenced against past shipments or online databases
5. A supervisor reviews the entry before submission

This process relies on attention, experience, and available time. Under pressure — during peak cargo periods, with multiple shipments running in parallel — errors are introduced not because agents lack knowledge, but because the volume of manual data handling creates the conditions for error.

Mirsal 2 is not the problem. Manual data preparation before Mirsal is.

HS Code Accuracy: Why It Matters More Than Ever in UAE Customs

The UAE’s adoption of the 12-digit HS code requirement has added a layer of precision to customs classification that older workflows were not designed to handle reliably. A clearing agent who previously worked from experience and manual lookup now faces a stricter classification environment where an incorrect code carries real consequences — penalty, audit exposure, and shipment hold.

The challenge is compounded by the nature of classification work itself. HS code accuracy depends on product description quality from the shipper, familiarity with commodity-specific classification rules, and knowledge of recent updates to the UAE tariff schedule. This is judgment-based work, not a lookup task.

What experienced clearing agents consistently report: they do not want full automation on HS codes. They want assistance — a suggestion based on the product description and shipment history — with the final decision remaining with the agent. That distinction matters for how preparation tools should be designed and how clearing operations should think about where intelligence helps and where human judgment remains essential.

What UAE Clearing Agents Are Doing to Reduce Pre-Filing Errors

The clearing operations managing highest shipment volumes in Dubai are addressing the preparation problem directly, rather than accepting rejection rates as fixed overhead.

The approaches showing consistent results:

• Document-to-field extraction — Using document intelligence tools to extract structured data directly from commercial invoices and packing lists, reducing manual retyping and the transcription errors it creates.
• Cross-document validation before filing — Running automated checks across multiple documents to identify mismatches before the declaration reaches Mirsal 2.
• HS code assistance — Using classification tools that suggest the appropriate HS code based on product description, with the clearing agent retaining final approval. The decision remains with the experienced operator.
• Workflow standardisation at intake — Structuring the document intake and pre-filing process so each stage has a defined checkpoint, reducing variability across team members and shifts.

Where Nunar Fits Into This

Nunar is not a replacement for Mirsal 2. It does not file on your behalf or remove the clearing agent from the submission process. Nunar is the preparation layer that sits before your team opens the Dubai Trade Portal.

Nunar extracts structured data from incoming documents — commercial invoices, packing lists, certificates of origin — validates that data across documents before entry, and presents your team with a checked, ready dataset for Mirsal 2 input. Where HS classification assistance is needed, Nunar suggests based on description and context. Your agent confirms. The filing remains yours.

For a clearing operation processing 50–200 declarations per month, removing manual extraction time and pre-filing discrepancies from the daily workflow has a compounding effect. Fewer rejections. Less rework. Less time spent on queries from customers waiting for their shipments.

The real problem is not submission. It is preparation.

Summary: What UAE Clearing Agents Need to Know About Mirsal 2

• Mirsal 2 is mandatory for all Dubai customs declarations. There is no alternative channel.
• The system is reliable. The challenge is the data preparation that precedes it.
• Rejection rates of 10–15% are common but not inevitable. Most rejections trace back to pre-filing errors, not Mirsal 2 itself.
• The 12-digit HS code requirement raises the cost of classification errors — accuracy at the preparation stage matters more than before.
• Document intelligence tools can reduce manual data transfer time and pre-filing error rates without removing human control from the declaration process.
• Free Zone to Mainland Customs Clearance in UAE: The Full Process
• UAE 12-Digit HS Code Requirement: What Clearing Agents Need to Know Before the Deadline

Frequently Asked Questions

What is Mirsal 2 used for?

Mirsal 2 is the Dubai Customs declaration system used to submit all import, export, and re-export declarations through the Dubai Trade Portal. It is mandatory for all goods movements through Dubai for licensed UAE customs brokers, clearing agents, and Broker Representatives.

Who uses Mirsal 2?

Licensed UAE customs brokers, clearing agents working under freight forwarders, in-house clearance teams at logistics companies, and Broker Representatives filing declarations on behalf of importers and exporters.

Why do Mirsal 2 declarations get rejected?

Most rejections are caused by data preparation errors — value discrepancies, HS code mismatches, or inconsistencies between the commercial invoice, packing list, and transport document. These errors occur during manual data extraction and entry, before the declaration reaches Mirsal 2.

What is the difference between Mirsal 2 and the Dubai Trade Portal?

The Dubai Trade Portal is the broader digital platform for UAE trade facilitation services. Mirsal 2 is the customs declaration module within that platform, used specifically for filing and managing customs declarations with Dubai Customs.

Can the Mirsal 2 preparation process be automated?

The data preparation stage — extracting structured information from incoming documents and validating it before entry — can be significantly automated without removing agent oversight from the submission process. Document intelligence tools handle the extraction and cross-document checks. The filing decision, HS classification approval, and final submission remain with the clearing agent.