MTX — Multi Transport Xpress
← Back to InsightsTrade Updates

WeBOC GD Filing: Common Errors That Hold Shipments at Karachi

7 min read

Goods Declaration mistakes cost more time than port congestion. Errors our customs desk sees every week on Pakistan import and export filings.

A shipment can reach Karachi on schedule and still sit for days because the Goods Declaration (GD) on WeBOC does not match the physical cargo or the commercial documents. That is not a carrier problem — it is a filing problem. Terminals do not invent clearance. Customs channels do.

MTX coordinates with licensed customs brokers every working day. We do not file GDs ourselves. We see the same preventable mismatches often enough that the operations desk keeps a living checklist for Karachi Port and Port Qasim traffic. Use it before the broker submits — not after the container starts accruing free-time pressure.

Why GD Errors Feel Like Port Congestion

Shippers often blame “the port” when the box is not moving. Ask two questions first: what is the GD status on WeBOC, and what is the terminal hold reason? If the GD is under query or assessment, trucking and carrier follow-ups will not unlock the gate. If the terminal cites a carrier or unpaid local charge, customs is not the bottleneck.

That split saves a day of phone calls. It also tells you whether to escalate to the broker, the bank (for LC value issues), or the line agent.

HS Code Mismatches Between Invoice and GD

The commercial invoice HS code does not always match what the broker files on WeBOC. Common causes on Pakistan lanes:

  • The shipper copied an old code from a previous order that no longer matches the product build
  • The description is vague — “machine parts,” “textile accessories,” “chemicals” — so the broker picks a nearby chapter that triggers a different duty or exam path
  • The buyer’s PO uses one tariff language and the Pakistani invoice uses another

Customs may hold the GD for assessment. The container stays at the terminal. The demurrage clock does not pause because someone “meant” the correct chapter.

What to prepare before filing: confirmed HS code on the invoice, a one-page product note for first-time SKUs, and broker sign-off that GD text matches the bill of lading description. For repeat programmes, keep a classification note per SKU family so every new PO does not reinvent the story under cut-off pressure.

Value and Currency Declaration

Under-invoicing flags are common on imports where declared value looks low against comparable shipments. WeBOC risk engines compare against historical ranges for that HS code and origin. A suspiciously low invoice invites query even when the commercial deal is genuine — especially on related-party shipments without supporting pricing notes.

Exporters face the opposite trap: invoice value not matching the letter of credit amount, or freight and insurance additions missing from the FOB/CIF calculation on the GD. Assessment basis must tell one story across invoice, contract, and credit.

Worked example — Faisalabad surgical goods (export): A shipper filed GD on an FOB value while the LC was CIF. The freight line was not reflected correctly in the assessment basis. Clearance paused until the broker amended. The vessel still sailed — after a rushed amendment and a late night of document chasing. The fix next time was a ten-minute pre-file check: LC Incoterm vs GD value basis.

Worked example — Karachi machinery import: An importer declared a used line at a value well below recent comps for the same HS and origin. Customs queried. Free days ran to day six before supporting quotes arrived. Demurrage was lawful. The commercial “savings” on invoice value cost more than the duty difference would have.

Quantity and Packaging Unit Errors

Cartons versus pieces versus kilograms — the GD quantity unit must align with the packing list and the B/L. A mismatch of 500 cartons filed as 500 pieces when each carton holds 24 units will stop clearance until amended.

Reefer and bulk shipments have their own unit traps (net vs gross, kilograms vs metric tons). Check the packing list line by line before the broker submits. If you consolidate multiple POs into one container, the GD lines must still reconcile to physical packages — not to the buyer’s internal SKU count alone.

Consignee, NTN, and License References

Wrong NTN, expired import license reference, or consignee name not matching the bank LC beneficiary — these are administrative but block release instantly. For corporate importers with multiple entities, confirm which NTN sits on the GD before the vessel arrives. Changing consignee after arrival is slower and sometimes not possible without reopening the case.

Export side: shipper details on the GD should match how the company is registered for the Export Form (EF) path through the authorised dealer bank. Nickname trading styles on the B/L that do not match corporate registration create avoidable queries.

Export GD Timing vs Booking and Gate-In

Exporters sometimes file GD after the container has gated in. Karachi terminals and customs channels expect alignment between booking, gate-in, and GD status. Late export GD filing can delay loading permission even when the truck made the queue.

We advise exporters to have the broker draft ready before trucking picks up the empty container — not after stuffing is complete. Parallel work (haulage + draft GD + SI) beats sequential work when cut-offs are tight.

Import Timeline: Vessel Arrival to Clean Release

MilestoneTypical target (clean docs)What breaks it
Advance docs to broker3–5 days before ETAWaiting for originals only
Draft GD reviewBefore berthHS / value / unit mismatch
File / assess pathOn or before discharge planIncomplete license / NTN
Exam or query responseSame day if evidence readyMissing specs / comps
Delivery order + truckDay of releaseFinance or unpaid locals

These are planning targets, not statutory guarantees. Examination intensity varies by risk profile. The point is to run bank, broker, and trucking in parallel — not in a relay race that starts after the box is already on free days.

How MTX Coordinates With Brokers

MTX is a freight forwarder, not a customs broker. We do not file GDs. We pass clean shipping documents early, flag B/L description issues before release, and chase milestone updates when GD status blocks terminal movement. If your broker needs a corrected commercial invoice, we push the shipper the same day — not after the free-day warning email.

Practical Checklist Before Filing

  • Invoice, packing list, and B/L descriptions use the same product language
  • HS code confirmed with the broker — not copied blindly from an old shipment
  • Value basis matches LC or contract terms (FOB / CIF / CFR and currency)
  • Quantity units match physical packages (and net/gross where relevant)
  • NTN, entity name, and license references are current for the correct company
  • For exports: broker has draft GD before the container gate-in target
  • For imports: broker has advance pack before ETA, not only after discharge
  • Someone owns query response the same day — not “after lunch tomorrow”

Documents Pack That Prevents Most Queries

Keep a single shared folder (or email thread) with: commercial invoice, packing list, B/L or arrival notice, product specs for first-time items, LC pages covering goods description and Incoterms (if applicable), and any prior customs correspondence for the same SKU. Brokers work faster when they are not hunting attachments across five WhatsApp groups.

Pakistan customs procedures change with SROs and budget announcements. A forwarder who stays current on documentation — and honest about what brokers need — keeps cargo moving faster than one who only books the vessel. If your shipment is stuck, start with GD status and terminal hold reason. Everything else is secondary noise until those two answers are clear.

Need this handled on a live shipment?

Share origin, destination, cargo type, and target dates — our operations team will respond with a practical booking path, not a brochure.