Separate the software, portal and platform

To understand what you need, distinguish these components:

  • Your business’s invoicing software: creates invoices and notes with the required data and format, and submits them through integration after onboarding.

  • The Fatoora portal: starts solution-unit onboarding, generates the verification code, displays onboarded units, and initiates stamp-identifier renewal or revocation.

  • The platform behind the portal: receives documents from the solution through integration interfaces, validates them, and returns clearance or reporting results to the system.

Logging into the portal successfully is therefore not the same as successfully submitting invoices. After onboarding, documents move between the solution and platform through APIs; users do not need to log into the portal to submit each invoice.

What you do in the Fatoora portal

ZATCA’s guidance describes logging into Fatoora with taxpayer-portal credentials, selecting onboarding for a new solution unit or device, generating a verification code, and entering it into the invoicing solution. The solution then requests a stamp identifier and completes the required compliance checks.

Reach the correct route through ZATCA’s website or the route in its guidance. Do not start with a commercial software advertisement simply because its product name contains “Fatoora.”

Before generating the code, we recommend asking the system owner to confirm that the intended unit is ready for onboarding and that they know where the code belongs in the software. Do not send passwords, verification codes or private keys through a public enquiry form.

How to check what has been completed

The portal displays onboarded solutions and devices and each unit’s stamp-identifier status. This is different from checking an invoice-submission result: the platform returns document-validation results to the solution, which may be acceptance, acceptance with warnings or rejection.

When reviewing delivery with your provider, ask to see the unit’s portal status and a document result in the software, identifying whether it came from a test or production environment. Keep an open-issues list rather than accepting “connected” as the whole handover. This is an operational recommendation, not a certificate from ZATCA.

Where your business should start

For applicability and timing, use our current-wave guide. For the implementation sequence inside your system, read how to integrate electronic invoicing with Fatoora.

Aleem’s E-invoicing readiness (Fatoora) service assesses your invoicing system’s readiness, prepares it for integration, tests invoices before go-live, and trains your team to issue invoices after integration. Contact us with your system name and invoice sources to define the scope, without sending login credentials.

Aleem Consultations

Sources

https://zatca.gov.sa/en/E-Invoicing/Introduction/Guidelines/Documents/E-invoicing-Detailed-Technical-Guideline.pdf https://zatca.gov.sa/en/E-Invoicing/Introduction/Guidelines/Documents/E-Invoicing_Detailed__Guideline.pdf