Phase 1 (generation) required an electronic invoice in a defined format with a QR code. Phase 2 (integration) requires your system to connect to the Fatoora platform, so every tax invoice is cleared before you share it with the customer, and every simplified invoice is reported within 24 hours.
What breaks in practice is rarely the technical connection. It is the data: a customer with a missing VAT number, an incomplete address, a product without a correct tax category, or a credit note that does not reference the original invoice. A sound integration therefore starts with cleaning records, not with installing certificates.
In order: (1) review company, customer and product data; (2) issue the onboarding certificate from the Fatoora portal with an OTP; (3) connect the system to the simulation environment and issue test invoices of every type; (4) work validation errors down to zero; (5) move to production and set up monitoring for rejected invoices.
If you run Odoo, the Fatoora integration is part of the standard Saudi localisation and needs no external middleware. What you need is correct configuration, structured testing and someone watching rejections after go-live. If you run another system, the first question is whether it supports Phase 2 at all, or whether you need an integration layer.
Bottom line: book two weeks for data cleaning before any integration date, and ask your provider for a simulation test report, not a verbal promise.
Does this apply to your organisation?
A fixed-scope diagnostic of your system and data, with a gap list and action plan.
Request the diagnostic