Engineering ERP Consultant, KSA

Local content, vendor qualification and what buyers now measure

Saudi procurement increasingly rewards suppliers that add value inside the Kingdom. Government entities apply local content requirements in their tenders, and large energy and industrial buyers run their own supplier programs that look at local spending, Saudi employment, training and in-Kingdom manufacturing. Requirements vary between buyers and are revised periodically, so the specifics belong to your commercial team and advisors.

Whatever the program, the evidence comes from operational data. An engineering firm typically needs to show, per project or per year:

• Spend with Saudi suppliers versus imports, by category.
• Fabrication and assembly performed in your Saudi facilities.
• Engineering and labor hours by nationality.
• Training and development of Saudi staff.
• Capital invested in local capacity.

If suppliers are not classified at setup, and imported equipment is mixed with local fabrication in one cost account, this evidence is rebuilt by hand every time. I design supplier masters, cost categories and project structures so these figures come from the ledger. Vendor qualification adds another layer: buyers want quality procedures, capacity and past performance, much of which an ERP can report if projects are recorded consistently. This structure is defined during requirements gathering, before any platform is chosen.

Advance payments, milestones and ZATCA e-invoicing

Engineering contracts in the Kingdom often start with an advance payment, move through milestones linked to drawing approval, material arrival, inspection release and delivery, and keep a retention until final acceptance. Change orders add or reduce contract value along the way. Every one of those commercial events produces a tax invoice or a credit note, and under the FATOORAH program those documents must be produced in the required electronic format and, depending on your integration phase, shared with ZATCA.

That makes billing design more than a finance preference. I work through, with your finance lead and tax advisor:

• How advance invoices are issued and later offset against milestone invoices.
• How retention is invoiced and released.
• How a reduction in scope becomes a compliant credit note.
• Which ERP fields carry the buyer's purchase order, project and milestone references onto each invoice.

VAT treatment for each event comes from your tax advisor. I then verify that the ERP and its e-invoicing connection can produce what they confirm, and I question each vendor directly about how their solution is kept current as ZATCA requirements develop. The wider ZATCA discussion sits on my ERP consulting page for Saudi businesses.

Drawings, revisions and bilingual engineering data

Saudi engineering firms often run design teams that mix Arabic-speaking and English-speaking engineers, with drawings and specifications in English and many customer-facing documents in Arabic. The ERP has to support both without creating two versions of the truth.

I set clear rules for master data and design release:

1. Item descriptions: one technical description in English for engineering and purchasing, with an Arabic description maintained for documents that need it.
2. Release point: designs stay in CAD or PLM while in progress; an item and BOM reach the ERP only when a drawing is issued for construction or fabrication.
3. Revisions: a revised issue updates the ERP and lists every open purchase order, work order and reserved item raised against the earlier revision.
4. Change decision: the project manager decides whether the customer pays through a change order or the cost stays internal, and the ERP records that decision.

Long-lead equipment needs extra care. Pumps, compressors, transformers and instruments are often ordered abroad before the design is final, so I tie them to the project with a need date and the drawing revision they were ordered against. These rules form part of the solution design handed to your implementer.

Inspection, certificates and controlled shipments

Quality evidence carries real weight in Saudi energy and utility supply. A typical order is governed by an approved inspection and test plan, with the customer's inspector or a third-party agency attending at agreed points, and the order closes with a full quality dossier.

Some engineered items also carry export control obligations, for example instrumentation or control equipment re-exported to another country. Those obligations can come from Saudi rules and from the rules of the country where components were made. Classification is for your trade compliance advisor; the ERP should hold control flags, end-user details and a shipment block until compliance clears it. All of this is tested in UAT using records from a completed order.

Saudization, migration and remote delivery

Engineering roles are part of most firms' Saudization plans, and buyers also look at the Saudi share of engineering work on their projects. Timesheets that record discipline, project and employee nationality give management a view of where Saudi engineers are deployed and give job cost the hours it needs. Whether payroll lives inside the ERP or alongside it in an HR application, the link has to carry hours and cost without re-keying. Rules on Saudization quotas are for your HR advisors, not for me.

Most Saudi engineering firms I speak with are moving from a local accounting package or an older on-premises system, plus Excel cost trackers per project. The migration priority is open orders: contract value, approved change orders, advances received and recovered, milestones invoiced, retention, committed purchases and cost to date. Closed orders can be archived.

For businesses with mostly repeat production, my Saudi manufacturing ERP page is the closer match, and the engineering ERP guide covers the underlying engineer-to-order model. I work remotely with teams in the Kingdom, scheduling sessions around the Saudi working week; the Saudi Arabia hub describes how engagements are set up.