In brief
Map group VAT numbers, member TINs, shared devices and credential changes when members join, leave or replace the group representative.
A Saudi VAT group adds a member, replaces its representative or separates into individual registrations. Those events can change which Fatoora credentials remain active and who must onboard the issuing units.
ZATCA’s E-Invoicing Detailed Technical Guidelines, version 2, sections 3.3.8 and 3.4, describe the credential consequences. Connect the VAT registration decision and effective date to the actual issuing architecture before making the operational change.
Identify the group and member in the correct fields
Section 3.4.1, printed page 40, states that the group representative conducts onboarding. The CSR’s Organization Identifier uses the fifteen-digit group VAT registration number. The Organization Unit Name identifies the relevant member using its ten-digit TIN.
The same scenario requires each individual member to be onboarded as a separate device with a unique CSID, and allows each member to have multiple devices. Sections 3.4.1–3.4.2 also discuss shared devices and member-specific devices. Establish the actual setup and applicable scenario before deciding which credentials are affected.
A member’s TIN and the group VAT number serve different identification functions. Keep both in the unit register and confirm their actual CSR mapping with the solution provider. The VAT group registration guide explains the separate legal grouping framework.
Apply the scenario for the actual change
| Group event | Consequence described in section 3.4.1 |
|---|---|
| Create a group | The representative onboards the group setup. Existing individual credentials of joining taxpayers are automatically revoked where applicable. |
| Add a member | A qualifying group-owned shared device has no CSID change under that scenario, with responsibility for correct group invoicing retained. The representative onboards the new member’s own devices. Existing individual credentials of the joining member are automatically revoked where applicable. |
| Remove an ordinary member | The stated shared-device scenario has no CSID change. The representative revokes the departing member’s own devices. That taxpayer onboards devices it will use individually, where applicable. |
| Disband the entire group | Existing group credentials are automatically revoked, including shared and member-specific devices. Individual taxpayers onboard the devices they will use separately, where applicable. |
| Change the representative | Existing group credentials are automatically revoked, including shared and member-specific devices. The new representative onboards the latest setup. |
The removal scenario expressly excludes removal of the representative. Use the representative-change scenario when that is what actually occurs.
An unchanged shared-device credential still requires correct invoices on behalf of the group. Confirm the issuer and member data, routing and effective date; an unchanged certificate does not validate an obsolete configuration.
Follow a member-specific unit example
Dariba illustration. Assume a correctly mapped member-specific architecture with no shared devices. Group member A has two issuing units and member B has one, giving three active group units. Member C joins with two units that need onboarding for the group.
The representative onboards C’s two units using the correct group and member identification. C’s two former individual credentials are automatically revoked under the joining scenario. After successful completion, the group has five active units: A’s two, B’s one and C’s two.
Later, B leaves while A remains the representative. The representative revokes B’s one group credential. Assume the other units remain appropriate and active. The group has four continuing units. If B will invoice individually using its unit, B needs the applicable individual onboarding. The old group credential does not become an individual credential merely because B owns the equipment.
The numbers illustrate this assumed architecture. They do not prescribe how many credentials a different shared-server or signing arrangement needs.
Assign the portal and device steps correctly
Section 3.4.2, printed page 42, distinguishes the representative’s role from the member’s. The representative initiates onboarding and generates the OTP. The table permits the member to enter the OTP and generate the CSR from its own device, with the required member TIN, and continue the device’s onboarding process.
It assigns revocation to the representative. The table’s limited viewing access for a joining member is described as ninety days and configurable. It should not be treated as authority for that member to initiate group onboarding or revoke group credentials.
Agree who handles the portal, unit configuration, compliance completion and production check. Keep the completion evidence with the registration change.
Prepare for a representative change across the whole setup
A representative change has broader consequences than adding an ordinary member to a qualifying shared device. Sections 3.3.8 and 3.4.1 describe automatic revocation of the group’s existing credentials, followed by onboarding by the new representative.
Prepare the unit inventory and operational sequence with the parties and provider. Confirm the actual registration status and new credentials before relying on production operation. The credential lifecycle guide covers status, renewal and revocation evidence.
Dariba recommends retaining the approved group change, effective dates, old and new unit mapping, revocation and onboarding outcomes, and any unresolved documents. Reconcile the transactions and invoices through the change using the Fatoora-to-VAT return reconciliation. Changing a certificate does not determine the tax point or create a second sale.
Sources
- ZATCA E-Invoicing Detailed Technical Guidelines, version 2, November 2022Sections 3.3.8 and 3.4.1–3.4.2, printed pp.38–42: automatic revocation, five group-change scenarios, CSR identifiers and representative/member roles.
