ERP Consultant for Jordan

Sales tax, e-invoicing and the invoice record

In Jordan the invoice is where most compliance risk sits. General sales tax has to be calculated correctly on each line, items with different tax treatments need their own codes, and the national electronic invoicing system run by the tax department expects structured data rather than a printed document. If those rules live in a spreadsheet or in one accountant's head, every new product or customer type becomes a risk.

During requirements work I list every invoice scenario the business actually produces: local sales, exports of services, credit notes, advance payments and invoices issued by more than one entity. Each scenario becomes a test case. When vendors demonstrate their systems, they run those cases, and I check how the tax is calculated, how the electronic invoice is generated and submitted, and what the user sees when a submission fails.

I do not give tax advice. Your accountant or tax advisor confirms the treatment of each scenario and the current e-invoicing obligations, and the system design is built to follow their guidance. My ERP requirements gathering service describes how these scenarios are captured, and the Jordan hub summarizes the wider market context.

Pharmaceuticals, IT services and regional offices

Jordanian companies looking at ERP often fall into one of a few patterns, and each needs a different emphasis in the design.

• Pharmaceutical manufacturers and distributors need batch and expiry control, quarantine and release steps, and the ability to trace a batch from purchase to customer. My notes on pharmaceutical ERP cover the wider process.
• IT and services exporters sell projects, retainers and support contracts to clients abroad. They need timesheets, project budgets, recurring billing and margin by contract, often invoiced in US dollars. The IT services page covers the core workflow.
• Regional offices serving the Levant and the Gulf keep local books for Jordanian purposes while reporting to a parent company in another currency and chart of accounts.

Trying to serve every pattern with one generic setup usually disappoints everyone. I start by agreeing which processes are critical for your business and which can stay simple, and the design follows from that decision. A distributor that also runs a small services arm, for example, may need full warehouse control but only light project tracking, and the platform shortlist should reflect that balance.

Choosing a platform for a Jordanian business

No platform is the right answer for every company in Jordan. I compare options against your written requirements and the support you can realistically get, whether from an implementer in Jordan, elsewhere in the region or working remotely.

• Zoho can suit services firms and smaller distributors that want CRM, accounting and inventory in one subscription with a modest rollout.
• Odoo covers manufacturing, quality and warehouse needs alongside accounting, which interests pharmaceutical and trading companies.
• ERPNext appeals to firms with in-house developers who want open-source code and control over hosting.
• Microsoft Dynamics 365 fits regional offices whose parent already standardizes on Microsoft.

For each shortlisted option I check how sales tax and the e-invoicing connection are handled, whether Arabic print templates can be produced, how dinar and dollar balances revalue, and who will maintain any local customization. The answers go into a scoring sheet you can share with your board. My ERP evaluation service explains the method in more detail.

Data migration, integration and data protection

Before go-live, data usually has to come from several places: a desktop accounting package, inventory spreadsheets, a CRM or contact list and sometimes a separate payroll file prepared by a local provider. I define what moves, at what level of detail and in which order, then plan reconciliation so opening balances, stock quantities and open invoices agree with the old records before anyone signs off.

Integration needs are usually modest but important: bank statement imports, the e-invoicing connection, an ordering portal for distributors and the payroll provider's output for journal posting. Each one gets an owner, a defined data format and a test. The ERP data migration page describes the checks I use.

Jordan has introduced legislation on personal data protection. Customer and employee records should be stored and accessed with that in mind, so I include role-based access, hosting location and retention questions in the requirements, and leave the legal interpretation to your counsel.

Working remotely with teams in Jordan

All my work for Jordanian clients is delivered remotely. Discovery runs as a series of short video workshops with each department, followed by written process maps and a requirements document for review. Vendor demonstrations, design walkthroughs and acceptance testing follow the same pattern, with a shared tracker that records open questions and decisions so nothing depends on memory.

Jordan's clock runs a few hours behind India's, leaving a shared working window wide enough for live workshops in your morning and review time on both sides afterward. Workshops and documents are in English. Where users work mainly in Arabic, a bilingual member of your team checks Arabic templates and leads end-user training, which also builds internal ownership of the system.

If your business operates beyond Jordan, the global page explains how I work with groups spread across several countries, and my ERP implementation support covers the build phase in more depth.