The test invoice was submitted successfully, then the developer who implemented the integration left. Months later, connection credentials needed maintenance and nobody knew who had access or where the renewal instructions were kept. This is not an invoice-layout problem. It is an operational ownership gap. One successful connection does not establish that the business can sustain the service after launch.
ZATCA describes the integration phase as adding technical and business requirements and connecting invoicing solutions to its systems. It also publishes relevant security specifications. This article concerns organising work around those requirements, not replacing them with an internal checklist or certifying any product.
Assign decisions before launch
Record actual responsible people rather than department names alone. Operations need an owner for tax data, a technical connection owner, someone monitoring unresolved documents, and backup coverage for sensitive duties. One person may hold several roles in a lean team, but approvals and review should remain clear. A former contractor should not retain permanent access by default.
| Decision | Proposed owner | Evidence before execution |
|---|---|---|
| Change core tax data | Financial data owner | Supporting document and impact review |
| Change connection settings | Integration owner | Approved change request and test plan |
| Resolve an uncertain document status | Invoice monitoring owner | Document reference and attempt outcomes |
| Release a software update | Service owner | Test results and an incident response plan |
These are suggested responsibilities, not job titles prescribed by the Authority. The objective is to avoid someone changing important data and approving the consequences without risk-appropriate review. Define escalation channels and realistic support coverage. Do not promise branches continuous support unless it actually exists.
Credentials are not ticket attachments
Treat keys, tokens and credentials as operational secrets. Limit access to people who need it, separate testing from production, and keep secret values out of error logs, email and explanatory files. An asset register can retain a secure reference, owner, status and review date without displaying the secret itself.
Check the applicable design and specifications before replacing a device, branch configuration or operating identity. Copying settings from one device to another is not necessarily a neutral action. If a secret is exposed, follow an incident process that establishes scope, revokes or replaces affected credentials through the authorised procedure, and verifies service recovery. Deleting the original message does not invalidate copies already received elsewhere.
Small changes can affect the whole document
A rounding rule, classification mapping or buyer-data change can alter a document's contents without greatly changing its visible layout. Match testing to the change: line calculations and totals, required fields, document identity and file integrity, and external processing outcomes where applicable. Preserve the configuration version that produced the test sample so later differences can be explained.
Before release, agree when unexpected results should halt further rollout and how documents already created will be handled. Reverting software does not erase earlier submissions and does not justify deleting production documents or regenerating them in bulk. Remediation must respect each document's status and the relevant official rules.
Monitor the business process, not just server availability. A website can remain online while invoices accumulate without completing their required processing route. Show their count, oldest timestamp and cause distribution, and assign alerts to someone able to act. Test coverage when the primary owner is absent: a dashboard nobody reviews is not effective monitoring.
During an integration interruption, follow the Authority's and provider's approved procedures for the circumstances and invoice type. Do not invent a general permission to bypass or postpone requirements. Preserve the timeline, affected documents and response actions, then investigate the cause after restoration. End the review with a specific improvement to configuration, testing or responsibility assignment.
A useful handover enables an authorised replacement to understand what works, what remains untested and what requires attention without exposing secrets. Neither the handover nor this article establishes that Wali ERP integration is implemented or accredited. That conclusion requires separate operational and verification evidence.
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.
