Compliance guide

How to onboard to the Fatoora platform

What happens between opening the Fatoora portal and issuing your first cleared invoice.

What does onboarding to Fatoora mean?

Onboarding is how each invoice-issuing unit you have, whether a system, branch or point of sale, gets a digital certificate from ZATCA that lets it stamp invoices and send them to the platform. It has two stages: a temporary compliance certificate used to pass test checks, then a production certificate used in live operation. It's done once per issuing unit, not once per business, and the certificate stays valid until it needs renewal.

First: list your issuing units

What surprises businesses most is that this isn't one process for the whole company. Every unit that issues invoices needs its own certificate. An accounting system at head office, three points of sale in branches, and a separate system for subscription invoices make five units, not one.

  • The accounting or ERP system issuing tax invoices.
  • Each point of sale issuing simplified invoices to individuals.
  • Any side system issuing invoices, such as bookings, subscriptions or an online store.
  • Branches issuing their own invoices from a separate system.
Start with this list. The number of units sets how many OTPs you'll request and how many certificates you'll manage. Miss one unit, and its invoices stay outside the system after you think onboarding is done.

What must be ready first

  • Active VAT registration: portal access requires a registration status of Active or Reactive.
  • Access to the Fatoora portal: through ZATCA's single sign-on, with an account that can manage e-invoicing.
  • A system that really supports Phase 2: it must generate a key pair and certificate request, sign invoices and connect to ZATCA's APIs.
  • Correct business details: legal name, VAT number, the branch's national address and sector all go into the certificate request.

The steps from start to go-live

  1. Log in to the Fatoora portalFrom ZATCA's portal through single sign-on, then go to the onboarding and management portal.
  2. Request OTP codesFrom the option to onboard a new unit or device, request one code per issuing unit. You can request 1 to 100 per request, and each code has six digits.
  3. Enter the code in the issuing unit within an hourThe code is valid for one hour from when it's generated. Manual entry works for several units, while automatic entry from the system covers one.
  4. The system creates and sends the certificate request (CSR)The issuing unit generates a private and public key pair, builds the request with business and unit details, and sends it to ZATCA.
  5. Receive the compliance certificate (CCSID)A restricted certificate that isn't for live use. It's only for passing the checks in the next step.
  6. Run the compliance checksSend the required test documents for your registered invoice type, covered in the next section, and confirm all are accepted.
  7. Request the production certificate (PCSID)Issued after you pass the checks. This is the certificate used to clear your real invoices and report simplified ones.
  8. Move live invoicing onto the systemAfter confirming a real invoice of each type passes, including credit and debit notes.

This sequence matches ZATCA's documentation in the Fatoora Developer Community and Microsoft's onboarding guide for Dynamics 365. See the e-invoicing portal for current technical specifications.

Certificate request fields that cause rejections

FieldWhat it holdsSpecification
Unit common nameA unique name or tracking number for the issuing unitSet by the business, and not repeated between units
Unit serial numberProvider name, model or version, and serial numberUsually generated by the system, not the user
Organisation identifierThe business's VAT number15 digits, starting and ending with 3
Organisational unit nameBranch nameFor VAT groups: the 10-digit unique number
Organisation nameTaxpayer nameFree text
CountryCountry codeTwo letters under ISO 3166
Invoice typeWhat this unit issuesFour digits: the first for tax invoices, the second for simplified, the last two reserved
LocationBranch or unit locationThe short national address is preferred
IndustryBusiness activityFree text
The invoice type field deserves care. "1000" means tax invoices only, "0100" simplified only, and "1100" both. Your choice sets which documents the compliance check asks for, and getting it wrong means restarting onboarding.

Field specifications come from ZATCA's developer documentation and Microsoft's onboarding guide, which agree on them.

Compliance checks: exactly what you send

Registered invoice typeDocumentsWhat's required
1000: tax only3Tax invoice, debit note, credit note
0100: simplified only3Simplified invoice, simplified debit note, simplified credit note
1100: both6All of the above
If a check fails or doesn't finish, you don't just repeat the check. You start again from a new OTP and a new certificate request. So prepare and review the documents before requesting the code, not after.

Simulation before production

ZATCA has a simulation environment separate from production, each with its own portal and endpoints. Use it to try the full cycle before touching real invoices.

A frequent mistake: generating an OTP in one environment's portal and using it in the other. The code must come from the portal matching the environment you're connecting to, or the request is refused with no obvious reason.

Common mistakes that stop onboarding

  • An expired OTP: an hour passes quickly if the technical team starts after requesting it.
  • The wrong invoice type: a unit issuing both types but registered for one fails later, not immediately.
  • A forgotten issuing unit: a branch or side system stays outside, and its invoices aren't compliant.
  • Mismatched business details: a wrongly formatted VAT number, or a branch name that doesn't match the record.
  • Testing only sales invoices: credit and debit notes are part of the check, and are often neglected until the platform rejects them.
  • Regenerating an invoice instead of re-sending it: this creates a new identifier, counter and hash, so ZATCA sees two invoices.

If you see a rule code in a rejection, look it up in our ZATCA error codes reference.

Renewal and tracking certificates

The production certificate isn't permanent. Renew it from the onboarding and management portal, in a process like first onboarding: the old certificate is revoked and a new one issued. Act before it expires, because expiry stops invoices being sent.

We've left out a validity period in months or years. Available sources say to renew "before it expires" without a figure we could verify. The period is on the certificate itself and in ZATCA's portal.

Where emerge fits

Onboarding is done with ZATCA once per issuing unit. After that, the emerge accounting system handles each invoice from inside the system: building the file in the required format, stamping it, clearing tax invoices, reporting simplified ones, and issuing credit and debit notes, with entries in the same books.

See the accounting system

Common questions

How long is a Fatoora OTP valid?

One hour from when it's generated, and it has six digits. If it expires before you enter it in the issuing unit, generate a new one from the portal.

Do I need a certificate for each branch or point of sale?

Yes. Onboarding is per issuing unit: the accounting system, each point of sale, and any side system that issues invoices each need their own OTP, request and certificate.

What is the difference between a CCSID and a PCSID?

The compliance certificate (CCSID) is issued after the request is accepted, and is only for passing compliance checks. The production certificate (PCSID) is issued after those checks, and is used in live operation to clear and report invoices.

What happens if a compliance check fails?

Repeating the check isn't enough. You start again from a new OTP and a new certificate request, then redo all the checks.

How many documents does the compliance check need?

It depends on the registered invoice type: three for tax invoices only, three for simplified only, and six if the unit issues both.

Want to put this into practice in your business? Try it yourself, or ask us on WhatsApp.

Note

This guide is general information, not tax or legal advice. Regulations and deadlines change, and the final reference is what the Zakat, Tax and Customs Authority publishes. Check with your tax adviser before acting on it.