Shipment document consistency checker

How the checker works

Pick a route, read the document list for that route, then type the same facts from each document: consignee, shipper, quantity, weight, packages, Incoterm, and value. India routes add IEC, GSTIN, and HSN, and a column for the bill of entry or the shipping bill. Gulf routes stay on the commercial invoice, the packing list, and the bill of lading or airway bill. That is the set English-speaking Saudi and UAE desks compare before a FASAH or Mirsal filing.

The check is clerical and it runs in your browser. Nothing you type is uploaded. The page does not open ICEGATE, FASAH, Mirsal, or CargoWise. A blank is not treated as a match. If you only fill one document, the report says there is nothing to compare yet.

FASAH documents checklist

Saudi import desks assemble a commercial invoice, a packing list, a bill of lading or airway bill, and a certificate of origin when the lane needs one, then attach that set to the FASAH declaration. ZATCA's English import instructions and fasah.sa are the places to confirm the current list and the pre-arrival step. Product permits such as SABER or an SFDA approval sit on top of that set only when the product needs them. This page will not tell you whether your product needs a permit.

English clearance notes keep returning to a simpler problem: the invoice, the packing list, and the transport document have to tell the same story. A different consignee, package count, weight, or value is a mismatch you can see before the declaration is submitted. The Saudi lane on this page is that pre-check. It is not the FASAH screen and it is not a customs ruling.

Dubai customs document mismatch

Declarations filed through Mirsal 2 rely on the same three commercial documents, plus the arrival notice or delivery order used at the port or airport, and whatever Dubai Customs currently asks you to attach. The Dubai Customs service guide is the document to confirm against. English write-ups of declaration queries keep coming back to the invoice, the packing list, and the bill of lading disagreeing.

Use the UAE lane when the shipment moves through Dubai or another UAE port and the declaration will be made in Mirsal. Type the figures as printed. The report lists the fields that disagree and the fields that agree, so a colleague can check the papers without starting the comparison from scratch. An invoice, packing list, and bill of lading check for the UAE is the same shape as the Saudi one, with Mirsal as the filing context instead of FASAH.

Shipping documents checklist for India

A shipping documents checklist for India import adds the bill of entry. Export documents for India add the shipping bill. The fields that usually have to agree are the parties, the quantity, the gross weight, the package count, the Incoterm, the value, the currency, the IEC, the GSTIN, and the HSN on the line you are checking.

IEC is usually 10 characters. GSTIN is usually 15. The checker compares the characters you type and warns when the shape looks off. It does not look the number up on a government portal. On export, a GSTIN that differs between the invoice and the shipping bill is called out in plain language, including the SB003 code that customs-house IGST refund notes have used for that kind of mismatch. The checker does not read the circular, decide a refund, or file the shipping bill.

An invoice and packing list mismatch is the same class of problem as a bill of lading that carries a different weight. HSN is compared as printed. The tool does not classify the goods and does not calculate duty.

Invoice, packing list, and bill of lading

Names are compared without case or light punctuation, so "L.L.C." and "LLC" can agree. If one name merely contains the other, the report asks for a review instead of calling it a clean match. Numbers have to agree. Kilograms are not converted to pounds. Incoterms are split into the code and the named place, so FOB Jeddah against CIF Jeddah is a mismatch, and FOB Jeddah against FOB Dubai is a review.

Value and currency are expected on the invoice and, for India, on the bill of entry or shipping bill. The packing list and the transport document are included in the value check when you type them. HS codes on Gulf lanes are compared as printed on whichever documents you fill. That is a character check, not a classification.

What you can use on Monday

The report is on the page as soon as you run the check. Download the text or open a printable page and save a PDF. Attach it to the shipment file, or hand it to the person who will correct the invoice before anyone files. The checklist for the route is included in the download.

The report also counts how many values you typed. One shipment is a short form. Every shipment, retyped, is the work. If supplier invoices are the problem rather than shipping documents, the invoice mismatch policy builder drafts owners and a tolerance for accounts payable. An ICEGATE acknowledgement code belongs on the customs error decoder, which stays on published bill-of-entry messages and does not classify goods.

What this page leaves for a discovery call

The tool checks one shipment, and only the fields you type. It does not read PDFs, watch a mailbox, or push a draft into a filing system. It does not tell you the duty, the licence, or the permit.

Neurocell's paid work starts where this page stops: reading a real set of shipment documents, cross-checking them, and putting the result where the team already works. That is workflow automation scoped after a short discovery call. Larger builds start with short paid discovery. There is no price on this page. Clear quote after a short discovery call.