Follow the standard invoice from sale to clearance
Consider a supplier billing a business customer for equipment. The finance team verifies the buyer and transaction details, then generates the standard invoice and submits it for clearance. After acceptance, the cleared invoice is shared with the buyer. In your demo, ask to see the clearance response and how a rejected submission is corrected before the document is shared.
Follow the simplified invoice from checkout to reporting
Consider a restaurant issuing a simplified tax invoice for a counter sale. The customer receives the invoice at checkout; the system then reports it to FATOORA within the prescribed window. Ask to see how the cashier can continue under the agreed operating procedure and how finance detects pending or failed reporting. Printing a QR code alone does not show that reporting succeeded.
Prepare onboarding by branch and system
Confirm the applicable integration date with your ZATCA notification. List each invoicing solution or unit in scope, its branch, credentials owner and invoice types. Test standard, simplified and credit or debit note scenarios relevant to your business. Include a rejected submission and an interruption, then reconcile the submission log with issued documents.
Keep evidence after go-live
Assign someone to monitor acceptance, rejection and outstanding reporting. Document who investigates a failure and how the original transaction, invoice file and response remain traceable. Review exception records after the first busy shift and at month-end. Apply ZATCA's current specifications to your circumstances; the two examples above are illustrative, not invoice templates or tax advice.
Is a PDF invoice enough for Phase 2?
A readable invoice is only part of the workflow. Confirm the applicable structured invoice format, FATOORA integration, and the clearance or reporting status under ZATCA's specifications.
