Saudi sellers: your agent can handle ZATCA Fatoora e-invoicing on every paid order

The KSA version of the 11pm problem

Egyptian operators have ETA. Saudi sellers have ZATCA Fatoora, and Phase 2 made it heavier. It is not a portal you log into at month-end to type in invoices. Phase 2 (the Integration phase, rolling out in waves by taxpayer size) requires e-invoices generated in a compliant structured format and exchanged with ZATCA's platform, with simplified tax invoices for B2C reported within a defined window. Done by hand at any real order volume, this is a daily backlog with penalties attached to falling behind.

The honest framing: this is a regulated, evolving integration with specifics that depend on your taxpayer wave and accounting setup. The point of automation is not to pretend it's simple. It's to take the repetitive per-order work off a human while the structured submission happens correctly every time.

What the agent does

Connect your store and your ZATCA-integrated accounting tool to the Wassel MCP endpoint and give the agent the standing instruction:

On every paid order, generate the ZATCA-compliant invoice through the connected accounting system with the correct VAT lines and seller and buyer details, submit it to ZATCA for the required B2C reporting, store the returned reference and QR against the order, and send the customer their invoice on WhatsApp.

What runs:

• The store signals the paid order. The agent reads the line items, totals, and VAT.
• The connected accounting system (the one carrying your ZATCA integration and credentials) assembles the invoice in the compliant structured format with your seller details and the buyer's.
• The submission to ZATCA happens through that system, and the returned reference and QR come back and are stored against the order.
• WhatsApp Cloud delivers the invoice and QR to the customer while the purchase is still fresh.

The cryptographic and clearance specifics of Phase 2 are handled inside your ZATCA-onboarded accounting provider, the same way the signing device sits outside the ETA receipt flow in Egypt. Wassel orchestrates the flow across your store, that provider, and the customer. It does not replace ZATCA onboarding or claim to be your e-invoicing solution of record.

Why it matters

1. No daily portal backlog. B2C invoices are produced and reported as orders are paid, not reconstructed from exports near the reporting deadline.
2. Fewer structural errors. VAT lines and totals come straight from the order, not retyped. Mismatched figures are a common rejection cause when this is done by hand.
3. The customer gets a compliant invoice immediately. That cuts "send me the tax invoice" follow-ups and the manual reissuing they trigger.
4. An auditable trail. Every order's invoice reference, QR, and submission timestamp is stored against the order, so an auditor's question has an answer in the data, not in someone's memory.

What this does not do

It does not onboard you to ZATCA, choose your taxpayer wave, or replace your compliant e-invoicing provider. Those are your setup, done once with your accountant or solution provider. After that, the per-order generate-submit-deliver loop is what the agent runs so it isn't a person's evening.

Point your agent at the endpoint

Open the Wassel dashboard, copy the MCP endpoint into your Claude, ChatGPT, or Cursor config, and connect your store and your ZATCA-integrated accounting system. Run it on one paid order, confirm the invoice clears and the reference and QR come back, then let it run on the live queue.

If your accounting or e-invoicing provider isn't connected yet, tell us which one. We prioritise integrations off what Saudi sellers actually run, not a roadmap.