ZATCA & E-Invoicing Compliance — Shared Reference

When both tracks are active, keep ownership separated:

• ZATCA owners (Saudi track)
• E-Invoicing (EU) owners (European track)
• Finance reviewers who validate invoice correctness across both tracks

Do not merge settings ownership unless governance explicitly requires it.

1. Decide which compliance track applies per market and entity.
2. Keep ZATCA settings isolated from EU e-invoicing settings.
3. Assign separate owners for seller settings and customer data quality.
4. Maintain separate pilot evidence packs per compliance track.
5. Publish separate go-live criteria per market.

1. Classify invoice stream by market/regulatory track.
2. Route invoices to the applicable compliance workflow.
3. Validate output according to track-specific requirements.
4. Store evidence in market-specific folders.

Use separate audit/evidence bundles for each compliance track:

• ZATCA evidence bundle
• E-Invoicing (EU) XML and validation bundle

• Can we use one runbook for both ZATCA and EU e-invoicing?
• No. Keep dedicated runbooks and ownership models.
• Where is the EU runbook?
• `docs/user-guide/170-e-invoicing-eu.md`.
• Why separate guides?
• To avoid mixing regulatory assumptions and to keep operational accountability clear.