E-Invoicing

Fatoora CSID Renewal and Revocation: Keep Production Credentials Current

Updated 20 November 20263 min read

In brief

Track e-invoicing certificate status, renewal, voluntary revocation and registration changes with an issuing-unit evidence checklist.

A finance team can have a working connection and an invoice archive while a particular issuing unit’s production credential has expired or been revoked. Keep the actual certificate status beside the list of units used to generate and send invoices.

ZATCA’s E-Invoicing Detailed Technical Guidelines, version 2, sections 3.3.4–3.3.8, distinguish compliance checks, production credentials, renewal and revocation. A Cryptographic Stamp Identifier, or CSID, needs to match the actual taxpayer and e-invoice generation solution unit.

Distinguish the compliance stage from production

Section 3.3.4, printed pages 30–31, describes compliance checks after the unit obtains its compliance CSID. The production CSID then enables authentication and use of the core e-invoicing APIs.

The checks follow the functionality declared for the unit. The guideline lists the standard invoice, debit note and credit note for the standard-only case, and the corresponding three simplified documents for the simplified-only case. Keep the results for the functionality actually used. An unfinished or failed check requires the stated onboarding or renewal process to be reinitiated, including a new OTP and CSR.

The solution requirements guide explains how generating, signing and sending roles affect the unit map. Use that map when assigning a credential to a server or device.

Plan renewal around the actual expiry record

Sections 3.3.5–3.3.6, printed pages 32–33, describe renewal as revocation of the existing CSID and issuance of a new one. The portal’s unit list includes status, onboarding date, certificate expiry and any revocation date.

RecordPractical check
Taxpayer and unit identityMatch the registration, asset or unit name, serial number and location.
Supported documentsCompare the declared functionality with the invoice flows in use.
Current certificateRecord its actual status and expiry from the portal and solution.
Renewal outcomeRetain the new credential reference, updated status and successful completion evidence.
Continuing invoice flowCheck that the intended production unit completes its applicable document process.

Assign an owner and enough preparation time to resolve failed checks. An internal reminder thirty days before expiry can be useful; that chosen reminder is Dariba’s operating suggestion and does not establish a statutory renewal period or extend a certificate’s validity.

Because renewal replaces the old credential, agree the cutover with the solution provider. Record which credential the production unit is using after completion.

Identify the affected unit before voluntary revocation

Section 3.2.3, printed page 18, lists reasons for taxpayer-initiated revocation, including suspected compromise of the key or unit, sale or transfer, discontinued use, inaccurate credential information, loss, theft, damage, unauthorized onboarding and a major upgrade.

The process in section 3.3.7 involves selecting the relevant active unit, confirming revocation and checking that its status is reflected as revoked. Keep the supporting event and confirmation. Assess the replacement or re-onboarding needed for continuing operations.

Dariba illustration. A business has three correctly mapped production units. Unit A is renewed, Unit B is sold and its credential is revoked, and Unit C continues unchanged. Assume no replacement is installed for B and A’s renewal is completed correctly. The business then has two continuing active units. A’s old credential belongs in the renewal history; it does not represent a fourth operating unit.

Record automatic revocation on a registration change

Section 3.3.8 explains automatic revocation when VAT registration status changes to deregistered or suspended. VAT group formation, membership and representative changes have additional scenarios.

The same section describes a ninety-day period of restricted portal access after the stated registration-status change: viewing previously onboarded units, without other onboarding functions such as generating an OTP. That viewing period does not keep a revoked CSID usable for production.

Use the VAT group credential guide for group-specific consequences. Preserve the unit history and retrievable invoices when recording a change. For an interruption affecting generation or integration, apply the actual incident procedure described in the clearance and reporting guide.

Close the change with completion evidence

Dariba recommends a file linking the initiating event, affected unit, old and new credential references where relevant, portal status, completion result and outstanding invoice work. Keep credentials and private keys within the authorized solution and access arrangements; the review file should identify the change without circulating secret material.

Check completion against the live setup and current ZATCA requirements. A saved renewal request alone does not show that the replacement production credential is installed and being used successfully.

Sources