E-invoicing requirements proven inside the engagement scope
We turn official obligations into a data, responsibility, and test map—then separate what can be delivered in Egypt from Saudi and UAE work that requires independent project evidence.
GizaLink does not claim ZATCA approval, UAE ASP status, or generally available Saudi or UAE integration.
What do we review?
- The authority, date, and phase applicable to the company
- The source of every tax and commercial field
- Responsibility across the client, GizaLink, and provider
- Acceptance, rejection, retry, and archive behaviour
- Acceptance tests and recovery plan before go-live
Egypt: a workflow delivered after scope verification
There is verified operating experience for the Egyptian e-invoicing workflow. It can be included after reviewing entity, data, codes, environment, and current specifications. This is not government accreditation and does not replace client-specific acceptance testing.
Saudi Arabia: the obligation is official; integration is a separate project
ZATCA introduces Fatoora Phase 2 in waves. Official announcements and specifications determine what applies to the entity, but a GizaLink connection is not marketed as generally available, approved, or compliant before independent delivery and acceptance evidence.
UAE: the service provider is an explicit design party
The UAE model relies on a client-selected accredited service provider. Data ownership, transformation, and failure responsibility are mapped across the parties before delivery. GizaLink is not an ASP and claims no accredited UAE integration.
Regulatory content expires
Waves, decisions, and dates change. Every regulatory page carries an official source and review date, and is checked again when an engagement starts and before contractual scope is fixed.
Official sources
Editorial review: 19 August 2026. Sources are checked again when an engagement begins.
Start with the obligation that applies to your company.
We review the authority, date, data, and parties before turning any requirement into technical scope.