An e-invoicing claim should be supported by a specific scope, a tested invoice lifecycle and clear operational ownership. The logo on a brochure does not establish what your deployment will do.
Use the authority as the source of requirements
Consult the ZATCA e-invoicing portal, the applicable rollout guidance and the published business and technical specifications. Record the versions used in your implementation assessment.
The official specifications include a data dictionary and an XML implementation standard. Your technical review should connect the applicable requirements to actual output and validation evidence. This article does not replace the authority’s requirements or professional advice about your own circumstances.
Ask for a traceable test pack
Choose relevant invoice and note scenarios with your finance team. For each, keep the source ERP record, the generated output, the validation result and the final status. Include an incomplete record so error handling is demonstrated rather than described.
Test amendments through the correct document process. Ask what the operator can edit, what must remain preserved and how corrections are represented. Confirm those behaviours against the applicable specifications.
Inspect operational responsibilities
Document who owns onboarding, secure credential handling, test environments, production activation and monitoring. Ask what happens after a failed request and how duplicate processing is avoided when the operator retries. These are acceptance questions; they should be demonstrated for the proposed solution.
Agree an escalation route and a process for reviewing authority updates. A one-time successful test does not define ongoing service responsibilities.
Keep commercial claims precise
Ask whether the proposed integration is included, separately licensed or delivered by another provider. Identify limitations, exclusions and required configuration. Avoid treating “certified,” “approved” and “supports integration” as interchangeable claims; request evidence for the exact wording used.
Use System Setup and Sales & CRM as starting points for a DNA discussion. Confirm the current Saudi implementation scope with the team and assess it against your documented requirements. References checked on 29 September 2026.
