A polished invoice printout is not enough to establish e-invoicing readiness. The more useful question is whether the business produces a correct document from reliable data, preserves it as issued, retrieves it, and handles corrections appropriately. Test that complete cycle with someone who will actually operate the system rather than relying on a prepared sales demonstration.
ZATCA explains that the generation and storage phase requires invoices and notes to be generated and stored through a solution meeting the applicable requirements. The integration phase adds further obligations. Passing a generation test does not demonstrate integration readiness. Use the relevant official requirements and notifications—not a general article—to determine the phase and deadline applicable to the business.
Begin before the issue button
Prepare representative business, customer and item data in a test environment without sending trial documents to real customers. Start with a straightforward invoice, then introduce a discount, fractional quantities and a note connected to an original invoice. The purpose is not to accumulate test cases indiscriminately, but to reveal where incomplete master data forces staff into manual workarounds.
Identify the appropriate document type and its required fields. Examples highlighted by ZATCA include a QR code for simplified tax invoices and the buyer's VAT registration number where applicable to a tax invoice. These are examples, not a complete compliance checklist. Consult the specifications for each document type rather than copying one invoice's fields into every transaction.
Ask where the business name, tax identifier, customer information and item classification originate. If every salesperson can freely change them during a sale, the demonstration may work while subsequent invoices diverge. Control master-data editing and review changes before use, with a correction process that does not encourage staff to invent values merely to complete required fields.
Arithmetic matters more than logo placement
For a calculation test assuming a supply taxed at 15%, two units priced at SAR 100 each before tax, less a SAR 20 discount against that line total, produce a taxable base of SAR 180, tax of SAR 27 and a total of SAR 207. The example assumes a tax classification for testing; it does not determine the classification of any actual product.
Check agreement between line details, totals and the amount payable. Changing quantity should recalculate them consistently. Repeat with decimal amounts to examine rounding under the applicable rules, and with a multi-line invoice requiring an appropriate discount allocation. Do not allow a manually overridden total to conceal an unexplained discrepancy.
After generation, read the QR code where required and inspect its data using an appropriate validation method. A scannable square does not establish correct contents or compliance with all other requirements. Check the readability of the customer copy and its agreement with the stored document. Two individually attractive but inconsistent versions are still a problem.
Tomorrow's test: can you find it again?
Close the user session and retrieve the document by its reference using an authorised account. Confirm the correct contents and associated notes are available, without retrieval becoming reissuance or creating a new number. Verify that a read-only user cannot silently delete a document or replace its information.
Test backup restoration in a separate environment and examine selected documents and their relationships rather than trusting a “backup complete” message. Assign responsibility for failed backups, retention and retrieval in accordance with applicable requirements. When changing service providers, establish how documents and the information needed to read them remain accessible after the subscription ends. A scattered collection of images may not meet the intended requirement.
Finish with a short test record distinguishing passed, failed and untested matters. Connect each finding to an example, expected result and corrective owner. Retest a defect after repair, then train branch staff on the real error-handling procedure rather than only the print button.
This is a practical readiness review, not a compliance certificate. The conclusion depends on the full set of ZATCA requirements, the applicable phase and actual operation. This article does not establish Wali ERP accreditation or implementation of phase-two integration.
Sources & further reading
Visit the original source to explore the concept and its wider context.
General educational content. Appropriate treatment depends on your business and accounting policies; consult your accounting professional when applying it to business records.
