SaaS ERP Consultant, Saudi Arabia

Which system should issue the tax invoice?

This is the first design decision for any SaaS company billing customers in Saudi Arabia, and it is often made by accident. Many subscription billing platforms create invoices automatically every period. ZATCA's e-invoicing rules govern how tax invoices are generated, what they contain, how they are stored and, for taxpayers in the integration phase, how they are shared with the authority. If the billing platform cannot meet those rules for your situation, every automatic invoice becomes a problem.

There are three common patterns, and your advisor and the vendors should confirm which is workable:

• The subscription billing platform issues compliant invoices directly, through its own capability or a connected e-invoicing solution.
• The billing platform calculates charges and sends billing events to the ERP, which issues the compliant invoice.
• The ERP handles both subscriptions and invoicing, accepting fewer billing features in exchange for one compliant source.

Each pattern affects payment links, dunning, customer portals and reporting. I map the consequences of each against your customer mix, so the choice is deliberate. For the broader picture of e-invoicing in Saudi ERP projects, see my ERP consultant in Saudi Arabia page.

Upgrades, proration and credit notes

Subscription businesses change invoices more often than most. A customer adds users halfway through a term, moves to a higher plan, downgrades at renewal or cancels early under a contractual clause. Each change usually creates a prorated charge or a credit, and in Saudi Arabia each of those documents has to follow the same e-invoicing rules as the original invoice.

In requirements workshops I list every amendment scenario your contracts allow and decide for each one:

• Whether it produces a new invoice, a credit note against the original, or both.
• How the credit note references the original invoice so the link survives in both systems.
• How the amounts are shown in Arabic and English and how VAT is recalculated.
• How deferred revenue is adjusted, following the policy your accountants set.

These scenarios then become UAT scripts. I test them with real data before go-live, because a mistake in proration logic repeats on every customer who upgrades, and correcting issued e-invoices is far more work than designing them correctly. The general quote-to-cash flow behind this is on my ERP for SaaS page.

Government contracts, Arabic documents and collections

Software companies with public sector or semi-government clients in the Kingdom often run two very different businesses. Large accounts sign annual or multi-year agreements after a formal procurement, require Arabic documentation, and pay according to their own approval cycles. Smaller customers subscribe monthly or annually with card or bank transfer payments.

For the larger accounts, the system needs to hold contract references, approved purchase documents, acceptance certificates where they apply, and the invoice schedule agreed in the contract. Collection reporting should show not only how old an invoice is, but which approval step it is waiting on, because chasing the wrong person delays payment further.

Arabic is not optional. Invoices, statements and often contracts need Arabic, sometimes alongside English, and some clients reference Hijri dates in their documents. I check that invoice templates, customer portal messages and statements can be produced correctly in both languages before a platform is selected.

On the revenue side, multi-year contracts with annual billing create deferred and unbilled balances that finance must explain to auditors and to zakat or tax advisors. Your accountants set the policy; I make sure the contract data supports it.

Hosting expectations and working remotely

Government entities and regulated sectors in Saudi Arabia, such as banking, often have firm expectations about where data is hosted and who can access it. Those expectations usually start with your product, but they extend to systems that hold client data: CRM records, support tickets, contracts and invoices. Your counsel and your clients' requirements determine what applies.

During selection I gather the questions your clients have already asked and check each candidate platform's hosting options, including whether a local data center region exists, whether self-hosting is possible, and which integrations would move data elsewhere. That evidence goes into the evaluation alongside e-invoicing and Arabic support, through a structured vendor selection process.

I deliver this work remotely, with live sessions scheduled in your working week and recorded walkthroughs for teams who cannot join. Finance, sales operations and engineering usually all need a voice, because billing touches the product as much as the ledger. My ERP integration work covers the connections between product usage, billing and finance. See the Saudi Arabia hub for more on how I work with businesses in the Kingdom.