A retailer with Phase 2 integration technically complete still needs someone to check whether its exemptions and credit notes satisfy what ZATCA requires.

Many businesses treat e-invoicing as solved once the technical integration goes live, then discover later that a specific transaction type was never correctly mapped to ZATCA's requirements. This advisory work exists to catch that gap before an inspection does, covering the regulatory interpretation questions that a technology implementation does not answer on its own.

Interpreting requirements for non-standard transactions

Standard sales invoices are the easy case. Consignment arrangements, bundled products with mixed VAT treatment, transactions with related parties and export documentation each raise specific questions about how ZATCA's requirements apply. Those questions need answers from someone who understands both the regulation and your business model, not a generic technical checklist.

Coordinating technical and regulatory perspectives

The people who built your e-invoice integration understand the technical mechanics. We add the regulatory interpretation layer, confirming that what was built meets what ZATCA intends, since an integration that works technically but rests on an incorrect interpretation still produces non-compliant invoices.

Following ZATCA announcements

ZATCA introduces requirements in stages and its focus can change over time. We follow its published announcements and tell you which ones apply to your business, so you are not treating every requirement as equally likely to be tested.

A hypothetical example

A Riyadh business exports services to a GCC customer and applies zero-rating to the invoice, assuming all exports qualify. A compliance review would check whether that specific service meets the place-of-supply conditions, because an incorrect treatment affects both the VAT position and the e-invoice data submitted to ZATCA.

Building this into ongoing operations

Rather than a one-time review, we recommend periodic compliance checks, particularly after any change to products, customer types or markets. This connects to the ongoing work covered in ZATCA compliance outsourcing, for businesses that want this handled continuously rather than periodically.

Reviewing before a business model change

Launching a new product line, entering a new market or restructuring how sales are invoiced each has e-invoicing implications. These are worth reviewing in advance, not discovering as a compliance gap after the change has gone live. The same applies to a VAT configuration review.

Training staff who issue invoices

The people entering transactions daily need practical guidance on the classification decisions that matter for your business, not a general compliance briefing. Most e-invoicing errors originate at data entry rather than in the technical system.

Reviewing the effect on the VAT return

A classification error in e-invoicing rarely stays isolated. It usually affects the VAT return figures built from the same transactions. We review both together, because correcting one without the other leaves a gap that surfaces in a later review.