Configured on sales journals
Devices and Phase settings
Link ZATCA devices to sales journals and control electronic invoicing per journal — the same place invoices are issued.
Gulf / KSA
E-invoicing that lives
inside your ERP.
For businesses selling into Saudi Arabia and the wider Gulf, ZATCA rules matter. TOSS ERP ships ZATCA configuration on sales journals — sandbox first by default — so compliance sits next to the invoices you already post, not in a separate tool.
Sandbox before production
Safe defaults
Environments default to sandbox so nothing reaches the live authority until you deliberately enable production after testing.
Invoices you already use
Not a parallel document set
Customer invoices in accounting are the documents e-invoicing builds on — stock, AR, and tax stay one story.
Built for multi-country SMEs
Gulf-ready, not Gulf-only
The same ERP serves teams elsewhere with local chart packs and tax setup. ZATCA is available when your Gulf sales need it.
Compliance + operations
E-invoicing next to stock and cash
Pair ZATCA with POS, inventory, or full SME modules — one workspace for the Gulf storefront and the back office.
ZATCA
Sales invoices
POS
Accounting
Inventory
How e-invoicing is switched on
ZATCA settings start in sandbox, and the integration ships turned off until someone enables it. Phase 1 can place a QR code on the invoice without calling the authority API. Phase 2 submission uses a device. A sales journal can require that device to be linked to that journal before a submission is sent.
Nothing is sent to the live authority until the integration is enabled, the environment is production rather than sandbox, and the company confirms that sandbox tests were done. The customer remains the taxpayer. The software can be corrected; the filing and any penalty stay with the business that issues the invoice.
Companies that do not sell into Saudi Arabia leave the integration off. Invoices, credit notes, and payments work without it. When a point-of-sale shop has auto-submit turned on, it uses the same company configuration — it does not create a separate tax account.
E-invoicing for ZATCA is optional. Invoices, payments, and the rest of the workspace work without it. Every plan starts with a 30-day free trial, and Starter and Basic have no implementation cost. Questions? Chat with us on WhatsApp.
Common questions
Does TOSS ERP submit invoices to ZATCA by default?
No. The environment defaults to sandbox and the integration ships disabled. Production submission is a switch the company turns on after sandbox testing.
Who is responsible for the tax filing?
The business that issues the invoice. The product generates the document and can submit it when configured. Penalties and the filing itself stay with that business.
Can one sales journal have its own device?
Yes. A device can be linked to one sales journal. When that journal requires e-invoicing, Phase 2 uses the linked device.
Do I need ZATCA to use invoicing?
No. Customer invoices and credit notes post without it. Turn the integration on only if you file with ZATCA.
See ZATCA in a trial workspace
Create a company and open Accounting → ZATCA configuration.