ERPNext CRM Consultant, Saudi Arabia

From quotation to compliant invoice: what sales must capture

Under ZATCA rules, invoices to business customers and to consumers are treated differently, and invoices to VAT-registered buyers generally need more buyer information. That information has to come from somewhere, and in most companies the somewhere is the salesperson who opened the account.

So I design the ERPNext sales chain backwards from the invoice:

1. Lead records the company or individual, source and owner, with a flag for whether the buyer is a business.
2. Conversion to customer is the control point: business customers need their VAT number, commercial registration and address elements completed before conversion is approved.
3. Quotation uses the customer's tax category, so VAT shows correctly and the buyer sees the amount they will be invoiced.
4. Sales order and delivery note carry everything forward.
5. Sales invoice is generated and passed to whichever e-invoicing app or connector your ERPNext stack uses.

The exact fields required, and how the e-invoicing layer reads them from ERPNext, should be confirmed against current ZATCA specifications and with your tax advisor. The evaluation of those e-invoicing apps is covered on my ERPNext consultant in Saudi Arabia page. My concern here is upstream: a sales process that delivers complete data, so finance is not chasing customers after the goods have shipped.

Commercial registration, VAT numbers and the national address

Saudi customer records have more structure than salespeople expect. A business buyer has a legal name, often in Arabic and English, a commercial registration number, a VAT registration number if registered, and a national address made up of separate elements such as building number, street, district, city and postal code.

In ERPNext I usually set up:

• Tax ID for the VAT number, with a format check and a mandatory rule for business customers.
• Custom fields for commercial registration number and, where useful, its expiry.
• Address fields extended to hold the national address elements separately rather than as one free-text line.
• Legal names in both languages, so Arabic documents print the registered name correctly.

For data already in the system, I run a gap report before go-live: which active customers lack a VAT number, which have addresses in one line, which appear more than once. Sales owners then fix their own accounts, which is faster and more accurate than finance guessing. Keeping the address structured also helps reporting by region, useful for companies selling across Riyadh, Jeddah, Dammam and beyond. For regional context see the Riyadh ERP consultant page.

Tenders, distributors and long project pipelines

Many Saudi suppliers sell into projects: government work published through official procurement channels, private developers, and main contractors buying for large sites. These deals move through stages that a simple lead and opportunity flow does not capture well.

For project-led selling I extend ERPNext opportunities with:

• Bid stages such as invitation received, clarification, technical submission, commercial submission, award and contract.
• Key dates for submission deadlines and validity, with reminders to the responsible person.
• Related parties including the owner, consultant and contractor, because the buyer and the decision-maker are often different.
• Attached documents such as prequalification files and technical offers, so they are not lost in personal folders.

Distributors and dealers selling across regions need a different shape: repeat orders, credit limits and price lists by customer group, where the CRM side is mostly visit planning and follow-up. ERPNext handles that adequately once territories and sales persons are configured. Lead sources are worth recording carefully in both models; referrals, exhibitions, tender alerts and existing accounts behave very differently. Industry detail is on the Saudi construction ERP and contracting pages.

Riyal pricing, GCC buyers and foreign currency quotes

Most Saudi sales are quoted in riyals, but suppliers that sell into other GCC markets or buy and resell imported equipment often need dollar or euro quotations too. ERPNext supports quotations and invoices in a foreign currency while keeping the company's books in riyals.

What I agree with sales and finance before configuring:

• Which customers trade in which currency, fixed on the customer so accounts do not mix currencies.
• How foreign currency prices are set: separate price lists with validity dates, or riyal prices converted at a defined rate.
• Who approves discounts above agreed thresholds, especially on large project quotes where small percentages carry real money.
• VAT treatment for exports and GCC sales, confirmed with your tax advisor and built into templates linked to tax categories.

Payment terms deserve attention too. Project customers may pay on milestones or certificates, and some buyers expect long credit periods. Recording the agreed terms on the quotation means they carry into the order and invoice, and collections can follow them. The approval workflows and ERPNext accounting in Saudi Arabia pages cover the control side.

Frappe CRM, a dedicated CRM, and when ERPNext CRM is too basic

ERPNext CRM fits Saudi businesses where selling is relationship and product led, and where salespeople benefit from seeing stock, prices and customer balances. It is weaker in a few areas I always flag:

• Marketing automation: nurture flows, scoring and landing pages are basic, which matters for consumer brands and education or healthcare providers running campaigns.
• Ads attribution: tying Snapchat, Google or Meta campaigns to revenue requires custom capture or another tool.
• Arabic user experience: the interface supports Arabic, but test each screen your sales team uses, especially on mobile, before committing.
• Messaging and telephony: connectors exist through third parties; verify them individually.

Frappe CRM is a separate app some teams find lighter to use. I would evaluate it against your Arabic, approval and handover needs rather than assume it fits. If another CRM serves your sellers better, I specify the link so ERPNext owns customers, items, prices and invoices, and the CRM never creates a tax-relevant record on its own. See ERPNext CRM, CRM consulting, the Saudi ERP consultant page and the Saudi Arabia hub.