ZATCA Phase 2 invoices with QR code, clearance and an online payment link, without running a full accounting department.

Saudi services firms, clinics and contractors reach their ZATCA Phase 2 wave while still invoicing from Word or Excel, with customers refusing documents that carry no QR code and receivables chased over WhatsApp. Odoo Invoicing issues standard and simplified tax invoices under the Saudi localization and tracks each one until it is paid, and Naqlah, Odoo partner in Saudi Arabia, onboards your journal on Fatoora and connects your payment gateway.
The invoice layout is Arabic by default with English alongside for foreign clients, and every document carries your VAT number, commercial registration and the 15% tax breakdown in SAR, with branch CRNs where a company bills from several locations. Naqlah sets up the fiscal positions, the Arabic template and the journal connection to Fatoora, then links PayTabs or Paymob so a customer can settle by mada from the PDF. For a store on Salla, the Naqlah Salla app turns online orders into simplified invoices in bulk, and for everything else the integrations list shows what connects.
Fatoora onboarding, sandbox to production
Each invoicing journal is tested in sandbox and simulation with the OTP from the Fatoora portal before production is switched on. Naqlah runs the first live invoices with your team because production cannot be reverted.
Rejection handling built in
A rejected invoice is corrected and resubmitted inside Odoo and is never shared with the customer while rejected. The rejection reason from ZATCA is stored on the document for the audit trail.
Branch invoicing under one VAT number
Branches bill under the parent VAT number with their own CRN printed on the invoice. Receivables stay in one place while each branch sees its own collections.
1. Invoice confirmed and XML signed
The invoice, whether created from a quotation, a Salla order or by hand, is confirmed and Odoo produces the signed XML with the Phase 2 QR fields.
2. Sent to clearance or reporting
If the customer record carries a VAT number it goes to the clearance API as a standard invoice; otherwise it is reported as a simplified invoice.
3. PDF with payment link delivered
The cleared PDF/A-3 with the embedded XML and QR code is emailed to the customer with a PayTabs or Paymob link for mada or card payment.
4. Payment registered, receivable closed
The gateway payment or bank transfer is registered against the invoice, reminders stop, and your external accountant sees the settled receivable in the ledger.
Timelines depend on scope and on the state of your customer data, and Naqlah gives you a clear roadmap in the first consultation.
| Area | Before | With Odoo via Naqlah |
|---|---|---|
| Invoice creation | Typed in Word or Excel, numbering by hand | Generated from the order or contract in one click |
| ZATCA | Manual portal entry, add on, or no compliance at all | Cleared and reported automatically on confirmation |
| Payment | Bank transfer chased over WhatsApp | mada and card link on the invoice itself |
| Reminders | Manual messages when someone remembers | Scheduled by days overdue with statements attached |
| Reporting | None until the accountant closes the year | Aged receivables and revenue live for the owner |
| Growth | New system and re-entry when bookkeeping moves in house | Activate Accounting on the same data with no re-entry |
Everything else, we cover in a free 30-minute consultation.
Free consultation. Meet the team and get a clear roadmap in one call.