ZATCA Phase 2 for Field Sales: What Van Sales Teams Need to Get Right

Most conversations about ZATCA e-invoicing focus on the office: the ERP, the accounting system, the POS at the counter. But for distributors, a large share of invoices are not issued in the office at all. They are printed in the back of a van, outside a grocery, sometimes with no signal.

ZATCA's rules apply there too. Here is what that means in practice.

This article is a practical overview, not legal or tax advice. ZATCA updates its technical guidance and integration waves regularly. Always confirm your obligations against the latest official ZATCA publications.

A quick recap of Phase 1 and Phase 2

Phase 1 (Generation) started on 4 December 2021. Businesses had to issue invoices electronically from a compliant system, with required fields and, for simplified invoices, a QR code. Handwritten and editable-document invoices were no longer acceptable.

Phase 2 (Integration) started on 1 January 2023 and is being rolled out in waves based on revenue. In Phase 2, your invoicing system connects to ZATCA's Fatoora platform. Invoices are generated in a structured XML format, stamped cryptographically, and either cleared or reported to ZATCA.

If your business has been notified for a Phase 2 wave, every system that issues invoices on your behalf must be integrated. That includes the app your reps use.

Standard vs. simplified invoices in the field

Phase 2 treats two invoice types differently, and van sales teams usually issue both.

	Standard tax invoice (B2B)	Simplified tax invoice (B2C)
Typical customer	VAT-registered business, supermarket chains	Consumers, some small shops
ZATCA model	Clearance: cleared by ZATCA before it is shared with the buyer	Reporting: reported to ZATCA within 24 hours of issue
QR code	Required	Required
Buyer VAT number	Required	Not required

For a van rep, the type of customer decides which flow applies. Your SFA app has to know which is which and handle each correctly, ideally without the rep needing to think about it.

What every field invoice needs

Under Phase 2, each invoice your rep issues should carry, among other things:

• A unique invoice identifier (UUID) and a sequential invoice number
• An invoice counter and the hash of the previous invoice, which chain invoices together so gaps or edits can be detected
• A cryptographic stamp generated with the device's certificate (CSID) issued during onboarding with ZATCA
• A QR code printed on the invoice
• All required seller, buyer, line, VAT and total fields
• XML in the UBL 2.1 format submitted to ZATCA

Credit notes and debit notes follow the same rules and must reference the original invoice. That matters for van sales, where on-site returns are common.

The offline problem

Here is where field sales differs from the office. A cashier's POS is usually online. A van rep often is not.

A well-built SFA app handles this in three ways:

1. Generate and stamp locally. The invoice, hash, stamp and QR code are created on the device, so the rep can print a compliant invoice with no signal.
2. Queue and sync. The invoice is stored securely and submitted to ZATCA the moment connectivity returns. For simplified invoices, the 24-hour reporting window gives room for this.
3. Track status. The back office sees which invoices are cleared, reported, pending or rejected, and can act on any problem quickly.

For B2B customers who need cleared invoices, discuss your workflow with your provider so that clearance happens before the invoice is shared, as the rules require.

Invoice numbering: the detail that bites

Phase 2 chains invoices with counters and hashes. That makes invoice sequence integrity much more important than it was on paper.

Common causes of trouble in field sales:

• A phone is reset or replaced and the app restarts numbering, creating duplicates.
• The app takes the "last invoice number" from the server, and the server sorts codes as text instead of numbers, so it returns the wrong value.
• Two devices are used by the same rep and issue overlapping numbers.

Duplicates get rejected, and fixing them after the fact is painful. Ask any SFA vendor exactly how they guarantee unique, gap-free numbering per device and per rep, including after a reinstall.

A compliance checklist for your SFA app

• ☐ Certified or integrated with ZATCA Fatoora for Phase 2
• ☐ Generates XML, hash chain, cryptographic stamp and QR code on the device
• ☐ Works fully offline with automatic submission on reconnect
• ☐ Handles standard and simplified invoices correctly
• ☐ Issues compliant credit and debit notes that reference the original invoice
• ☐ Guarantees unique invoice numbering across reinstalls and device changes
• ☐ Shows ZATCA submission status per invoice in the back office
• ☐ Supports Arabic and English invoice printing
• ☐ Keeps an audit trail of every invoice and change

How NobleSFA supports ZATCA Phase 2

NobleSFA is certified for ZATCA Fatoora Phase 2 e-invoicing in Saudi Arabia. Reps issue compliant invoices, credit notes and payment receipts from the van, online or offline, and print them over Bluetooth in Arabic and English. Submission status is visible in the back office, and the data flows to NobleERP or your existing ERP.

Like all TechQode invoicing products, it comes with a one-time implementation and no per-invoice charges.

Not sure your field invoices are compliant? Get a free consultation and we will review your current setup.

Frequently asked questions

Does ZATCA Phase 2 apply to invoices printed in a van?

Yes. If your business is in a Phase 2 wave, every invoice you issue must be compliant, regardless of where or on what device it is printed.

Can a rep issue a ZATCA-compliant invoice offline?

A compliant app can generate and stamp the invoice on the device and submit it when the connection returns. Simplified invoices must be reported within 24 hours. Standard B2B invoices follow the clearance model, so check your workflow with your provider.

Do returns need a credit note under ZATCA?

Yes. A return should be documented with a compliant credit note that references the original invoice.

What happens if an invoice is rejected?

The back office should flag it immediately so the issue can be corrected and the document resubmitted.