ERP Business Analyst, Oman

Turning Omani VAT and e-invoicing into a requirement set

Oman applies VAT through the Oman Tax Authority, and the authority has been preparing an electronic invoicing framework. I keep the regulatory detail high level here because scope and timing are set by the authority and can change; confirm both with your tax advisor and the official guidance before you rely on them.

For the BRD, the useful work is to break tax into concrete, testable statements. I build a scenario register with finance and your advisor, and each row becomes one or more requirements:

• Standard, zero-rated and exempt sales, with the customer and item data that decide the treatment.
• Imports, including how VAT paid or deferred at the border is recorded against the shipment.
• Services purchased from outside Oman and any reverse charge your advisor confirms.
• Tax invoices and credit notes in Arabic and English, with the fields and numbering they must carry.
• Rounding of rial amounts to baisa per line and per document, checked on printouts and exports as well as in the ledger.

For e-invoicing, I add data quality requirements: registration numbers validated on entry, no free-text customers, consistent units and descriptions. I do not interpret the law; I record what your advisor tells me. My ERP requirements gathering page describes the wider method.

Energy-sector suppliers: call-offs, job tickets and In-Country Value

A large part of Oman's private sector supplies oil, gas and other energy operators, along with government-linked infrastructure projects. These customers work through framework agreements, call-off orders, service entry sheets and vendor portals, and many expect suppliers to report on In-Country Value commitments such as local purchasing, Omani employment and training. In many supplier businesses those reports are still assembled by hand from several spreadsheets.

When I map this kind of business, the requirement set usually covers:

• Framework contracts with rate schedules, and call-offs that draw down against them.
• Field job tickets or timesheets approved by the customer's representative before billing.
• Invoices that quote the customer's purchase order and service entry references exactly, so they are not returned.
• Supplier and subcontractor records tagged as local or foreign, and staff records showing nationality, so ICV figures can be produced from transactions.
• Equipment and crew costs tracked per contract and per well site or location.

The exact ICV methodology belongs to each operator, so I document what your customers ask for rather than assuming a standard. These flows are drawn using my ERP process mapping approach.

Trading and logistics requirements around Omani ports

With ports at Sohar, Salalah and Duqm and land routes into neighboring countries, many Omani companies import, store and re-distribute goods. Their requirements are dominated by movement and cost, and they are easy to underestimate in a module checklist.

I document how a shipment moves from purchase order to forwarder booking, arrival, customs clearance, warehouse receipt and onward delivery, and which documents travel with it at each step. From that map come requirements for landed cost allocation (freight, insurance, duty, clearing and handling) by value, weight or volume; goods in transit visible as stock; batch or expiry tracking for food and pharmaceutical lines; and delivery notes in both languages for government and project customers.

Payroll and HR requirements often appear here too, because logistics firms run drivers and warehouse crews. I record whether salary files for the Wage Protection System, social insurance data and Omanization reporting will come from the ERP or a separate HR product, and what has to pass between them. The resulting gap analysis then shows which platforms handle these flows without heavy customization. Background on distribution systems is in my ERP for trading article.

How I run requirement sessions with Omani teams

I begin with the owner or general manager to understand which customers, contracts and reports matter most, then hold separate sessions with finance, procurement, operations and HR. Many Omani firms are family businesses or groups where a few senior people hold the commercial rules in their heads, so those early conversations save a lot of rework later.

Workshops are scheduled on your Sunday to Thursday week in Gulf Standard Time, kept short and focused on one process at a time. I ask for real documents in advance, such as a customs declaration, a call-off order or a bilingual invoice, because walking through a document gets more accurate answers than abstract questions. Staff who cannot join live can answer a short questionnaire in Arabic or English.

All of this happens online; I have no base in Oman and visits are possible only by arrangement. Drafts are shared for comment and approved area by area, and the agreed BRD becomes the scope reference for whichever implementer you choose. See ERP BRD consulting for the document structure, my ERP consultant page for Oman for selection and implementation support, or the Oman overview.