Last week a Shenzhen seller told me his 500-piece shipment to Riyadh was all held at customs. Reason: ZATCA showed "invoice not linked to VAT number." This isn't an isolated case. Since June, Saudi e-invoices must be tied to the importer's tax ID. If the invoice data doesn't match the customs declaration, the system blocks it automatically.
Frankly, many sellers used to get away with under-declaring or filling fake invoice numbers. Not anymore. ZATCA's e-invoice system is now fully connected with the Fasah customs platform. Any mismatch in amount, tax number, or HS code triggers a hold. My estimate is that at least 30% of cross-border sellers will hit this wall in the first three months.
What to do? Three actionable tips. First, use ZATCA's official API to pre-validate your invoice before shipping. Second, make sure CIF value, invoice amount, and VAT calculation are consistent — don't run two sets of numbers just to save a few points of tax. Third, if your item unit price is below SAR 1,000 (roughly USD 266), pay extra attention: these low-value goods now require an electronic certificate of origin, or they'll be held at clearance too.
Here's a hidden trap: e-invoices must follow ZATCA's XML schema. PDF scans are no longer accepted. Many logistics providers didn't warn sellers, so cargo arrives and they scramble to re-issue — that's a 5-day delay. Best practice: generate the XML in your system before the goods leave the warehouse and send it with the shipment.
At the end of the day, Saudi is making cross-border sellers' tax trail fully transparent. Is your invoice system ready for that?