Nafeza ACID 48 hour playbook Egypt export

Every Egyptian export shipment requires an ACID number (Advance Cargo Information Declaration) issued through Nafeza, Egypt's customs single-window platform. The ACID must appear on the Bill of Lading or Air Waybill at least 48 hours before vessel arrival at the Egyptian port of loading. Without a valid ACID, the shipping line will not release the BL — the vessel does not load. For Uzbek procurement teams running weekly programmes from Egypt, the practical playbook is a set of five role-shared steps that keeps the ACID flow on schedule and the documentation pack matched to the declaration.

This is the operational playbook. The full regulatory page is at the Nafeza/ACID compliance guide↗; the logistics view is at the Nafeza/ACID logistics page↗.

The 48-hour rule explained

The 48-hour clock runs backward from vessel arrival at the Egyptian port of loading. Inside that window, the ACID number must be issued by Nafeza and printed on the BL or AWB. The clock does not adjust for weekends or Egyptian holidays — programme planners build in a 72-hour buffer minimum to absorb a typo, a missing piece of consignee data, or any other small delay.

The hard rule: inside 48 hours, options collapse. A late ACID filing means the vessel sails without that consignment.

The five most common failure modes

Five specific failures cause rejection at the Egyptian port of loading:

1. Missing ACID number on the BL or AWB — usually a printing error at the shipping line, but the line will not release the BL regardless
2. Wrong HS code on the ACID declaration vs the phyto certificate — the two documents must match
3. Mismatched port of discharge between ACID and BL — even a small clerical error fails
4. Importer data mismatch — TIN typo, legal-name mismatch, wrong address line
5. ACID filed late — under the 48-hour window before vessel arrival

For each, the fix is process discipline upstream, not crisis management at the dock.

What Uzbek buyers should check on every shipment

Uzbek procurement teams have a small but critical role in preventing failure modes 3 and 4. The five-point pre-shipment check:

The first check (consignee data) is the most common source of silent error — a single character typo in a TIN can cascade through the whole declaration.

Role-sharing — who does what

The Uzbek buyer's role is upstream supply of accurate data and downstream verification of the printed BL. No direct Nafeza filing is required from the Uzbek end.

What to do if there's a problem

If a discrepancy is caught before T-48 h:

• Egyptian exporter re-files the ACID
• Documents reissue under the corrected declaration
• No transit impact

If caught inside T-48 h but before loading:

• Emergency ACID amendment is sometimes possible at Egyptian Customs Authority discretion
• Programmatic exporters maintain a 72-hour buffer to absorb this
• Transit impact 24–48 hours typical

If caught after vessel sailing:

• The shipment travels with the wrong declaration
• Uzbek customs at the port of entry may flag for re-inspection, delay, or rejection
• Resolution is always more expensive than prevention

The discipline that keeps the programme on schedule

Three rules that sustain a clean weekly Egypt → Uzbekistan programme:

1. Submit consignee data 7 days before vessel arrival — minimum
2. Maintain a 72-hour buffer inside the 48-hour window — absorbs typos and weekend pauses
3. Visual cross-check on every BL — Uzbek buyer-side review catches printing errors before the cargo sails

This is the playbook. Followed strictly, ACID rejections drop to near-zero. See the supporting pages for the full regulatory and operational detail.