Mirsal 2 declarations: the fields that cause the most rejections

Key Takeaways

• Most Mirsal 2 rejections trace back to five causes: wrong HS code length or format, an expired digital certificate, an incorrect free-zone facility code, a missing broker or consignee acknowledgment, or the wrong declaration type for the shipment.
• From August 2026, the 12-digit GCC HS code became mandatory for rest-of-world imports into the UAE mainland — a code that still validates at the old 8-digit length will now bounce.
• A re-export declaration filed after the 180-day window from the original import date is rejected regardless of how correct every other field is.
• Checking these five fields before submission is faster than resubmitting after a hold.

Mirsal 2 is Dubai Customs' electronic declaration system: every import, export, re-export and transit movement through Dubai's ports and free zones is filed through it, and a rejected declaration stops the shipment from clearing until it is corrected and resubmitted. A hold at this stage is rarely about the goods themselves — it is almost always a field-level error on the declaration.

Why the HS code is the single most common rejection point

A wrong or mismatched Harmonized System code is the most frequent cause of a Mirsal 2 rejection, and it fails in two distinct ways. The first is length: as of August 2026, the 12-digit GCC HS code is mandatory for imports into the UAE mainland from outside the GCC, replacing the shorter codes that used to validate (SamVertex, retrieved 2026-09-08). A declaration submitted with an 8-digit or 10-digit code, correct as far as it goes, is rejected outright for format.

The second failure is a mismatch: the HS code entered in Mirsal 2 has to agree with the goods description on the commercial invoice, packing list and certificate of origin. Where those documents describe a product one way and the declared code implies another, customs holds the shipment for review rather than accepting the declaration as filed (Topway Shipping, retrieved 2026-09-08). Pull the 12-digit code from the Dubai Customs Tariff portal directly rather than trusting a supplier's own code, which is frequently the exporting country's classification rather than the UAE's.

Digital certificate and facility code errors are procedural, not commercial

Two further causes sit outside the goods entirely. An invalid or expired digital certificate on the filing party's account blocks submission regardless of what the declaration itself contains — a certificate renewal lapse is an administrative failure, not a customs judgment call, and it is worth checking before, not after, a filing deadline.

Facility code errors are specific to free-zone transactions: a declaration filed against the wrong facility code, or with a mainland facility code on a free-zone-bound shipment, is rejected because the system cannot reconcile the declared destination with the licensed facility on record. This matters most for companies operating from more than one facility, where the default code saved from a previous filing quietly carries over to a shipment it does not apply to.

Filing the wrong declaration type wastes a full submission cycle

Mirsal 2 supports roughly a dozen distinct declaration types, and each carries its own required fields and validation rules (Velmontcrest, retrieved 2026-09-08). The two errors that recur most:

• Import to Local filed on a free-zone-bound shipment. If cargo is destined for a free zone rather than the mainland, an Import to Local declaration does not apply and is rejected; the correct type routes the goods differently and carries a different duty treatment.
• Re-export declarations filed outside the 180-day window. A re-export must be declared within 180 days of the original import date. Filed after that window, on an otherwise correct declaration, it is rejected on timing alone, and the goods default to standard import treatment instead.

Missing broker or consignee acknowledgment is the last recurring cause: Mirsal 2 requires the broker (where one is used) and the consignee to acknowledge the filing before it proceeds, and a declaration submitted without that step sits unactioned rather than formally rejected, which can be more disruptive because nothing visibly flags it as a problem until someone checks.

A five-point check before submission

Run these five checks before filing, in this order, since each one is faster to fix before submission than after a hold:

1. HS code length and match — 12 digits, matching the description on invoice, packing list and certificate of origin.
2. Digital certificate validity — confirm it has not lapsed, particularly around a renewal cycle.
3. Facility code — matches the actual licensed facility and destination (mainland vs free zone) for this specific shipment.
4. Declaration type — Import to Local only for mainland-bound cargo; re-export filed inside the 180-day window from the original import date.
5. Broker and consignee acknowledgment — confirmed before submission, not assumed.

Building this check into the logistics and shipping setup for a trading business, as a standing step before every filing, is cheaper than the delay and demurrage a hold at the port creates. Run your own shipment's duty exposure through the UAE customs duty calculator alongside the declaration check, since a wrong HS code affects both compliance and cost.

Frequently asked questions

What happens to a shipment while its Mirsal 2 declaration is on hold?

It does not clear the port or free zone until the declaration is corrected and resubmitted. Demurrage and storage charges continue to accrue at the terminal during the hold, separate from any customs penalty.

Can a customs broker prevent these rejections?

A broker familiar with the current HS code requirements and declaration-type rules reduces the risk, but the underlying documents (invoice, packing list, certificate of origin) still have to agree with each other — a broker cannot reconcile a genuine mismatch between them, only flag it before filing.

Does the 12-digit HS code requirement apply to GCC-origin goods too?

The August 2026 mandate specifically targets rest-of-world imports into the mainland; confirm current treatment for GCC-origin goods with your customs broker or Dubai Customs directly, since intra-GCC rules are handled separately from the rest-of-world classification change.

The bottom line

A Mirsal 2 rejection is almost never about whether the goods are allowed into the country — it is about whether the declaration describes them, and the filing itself, correctly. The five checks above catch the causes that recur most: HS code format and match, certificate validity, facility code, declaration type, and acknowledgment. Running them before submission is the difference between a same-day clearance and a shipment sitting at the port while someone corrects a field that should have been right the first time.

Figures verified 8 September 2026 against SamVertex, Topway Shipping and Velmontcrest reporting on 2026 Mirsal 2 and HS code requirements. Confirm current declaration-type rules and the 12-digit HS code rollout status directly with Dubai Customs or a licensed broker before filing, since customs procedures are revised periodically.