Business Central Consultant, Jordan

Environments, localizations and where the Jordanian company sits

Each Business Central online environment is created for a specific country localization, and every company inside that environment shares it. This matters for Jordanian entities in regional groups. If the group already runs Business Central in the UAE or Saudi Arabia, it can be tempting to add the Jordanian company to the same environment. Whether that is appropriate depends on what the Jordanian company needs locally and on what Microsoft and the partner support.

Before any design work, I establish:

• Availability. How Business Central is currently offered for Jordan, according to Microsoft's published information and each partner's written statement.
• Localization source. Whether Jordanian features come from Microsoft or from a partner or third-party app, and what they cover.
• Environment choice. Whether the Jordanian company should have its own environment, and what that means for intercompany postings, shared master data and group reporting across environments.
• Licensing. How users who work across several companies or environments are licensed, described as a cost driver.
• Maintenance. Who keeps local apps compatible with Microsoft's update schedule.

These answers decide the shape of everything that follows, so I document them as a short decision note for your finance and IT leads. Broader regional questions sit on my Dynamics 365 consultant Jordan page. Tax content is for your advisor; I do not give tax advice.

Posting groups for sales tax and exported services

Business Central uses VAT posting groups for sales tax as well, so Jordan's general sales tax is modeled through VAT business posting groups on customers and vendors, VAT product posting groups on items, resources and G/L accounts, and a setup that combines them with a rate and accounts. General posting groups do the same for revenue and cost.

The matrix I draft with your accountant typically distinguishes:

• Local customers and vendors under the standard treatment, and any categories your advisor treats differently.
• Foreign clients of services exporters, with the treatment your advisor confirms for exported services and separate revenue accounts so export income is visible.
• Items and services with special treatment, each with its own product posting group rather than a manual override on the document.
• Intercompany counterparties in the Gulf or elsewhere, separated from income and cost earned with outside parties.
• Resources and jobs for services firms billing time, so project revenue posts consistently.

VAT statement lines are then set to reproduce the figures your accountant files, and the setup is tested with a representative month of real documents in the partner's sandbox. Any withholding requirements and how they are handled by the localization are listed separately. Your tax advisor decides every treatment and should confirm the rules currently in force before the matrix is approved.

Dimensions for clients, projects and principals

Jordanian services exporters want margin by client, project and delivery team. Pharmaceutical and medical distributors want it by principal, brand or therapeutic line, and by channel such as hospitals, pharmacies and wholesalers. Business Central dimensions provide these analyzes without inflating the chart of accounts, but the two global dimensions and the shortcut set are best chosen before any entries are posted.

The dimension plan I prepare includes:

• Global dimensions for the analyzes used daily, often business line and client or principal.
• Shortcut dimensions for project, team, channel and region, visible on sales and purchase documents and journals.
• Default values attached to customer, vendor, item and resource cards, so most entries are tagged without user effort.
• Mandatory rules on revenue, direct cost and selected expense accounts.
• Allocation approach for overheads like premises, software subscriptions and leadership time, on a basis finance approves.

For services firms using jobs, I check how job tasks, resources and time entries carry dimensions through to invoices. For distributors, I check that item tracking for lots and expiry, where needed, works alongside the dimension design. Reports are prototyped with sample data so management sees the result early. The IT services and pharmaceutical industry pages give operational context.

Fils precision and an additional reporting currency

The dinar's three decimal places must be reflected in several Business Central settings, not just one. General ledger setup holds decimal places and rounding precision for local currency amounts and unit amounts, plus an invoice rounding precision. Each foreign currency card has its own equivalents. If any of these are left at defaults designed for two-decimal currencies, small differences appear between lines, tax and totals, and then again in what reaches the e-invoicing platform.

I list the relevant settings, agree values with your accountant and test them with invoices containing fractional quantities, line discounts and mixed tax treatments, comparing results with a manual calculation. Partners from two-decimal markets sometimes miss one setting, so this is part of acceptance rather than an assumption.

Currency reporting is the second decision. Many Jordanian entities report to a parent in dollars, or bill foreign clients in dollars and euros. An additional reporting currency stores every ledger entry in both dinars and the chosen currency. Given the dinar's longstanding dollar peg, a dollar reporting currency moves little, while euro or other balances can move more. I review with group finance:

• whether the reporting currency is needed, or consolidation elsewhere is enough;
• how rates are maintained and by whom;
• how adjustment runs are reviewed before posting.

Activating it before posting starts avoids a heavy later exercise. More on currency controls: multi-currency ERP.

Reading the statement of work for a Jordanian rollout

Whether the partner is in Amman, in a Gulf hub or delivering for the parent group, the statement of work is where Jordanian requirements are either protected or quietly dropped. I read it against your requirements and return a written set of comments and questions.

Points I check in particular:

• Jordan-specific scope stated explicitly: localization app, e-invoicing app, sales tax reporting, Arabic layouts and decimal precision, rather than covered by a general phrase about the group template.
• Apps by name, with publisher, licensing basis and who maintains them through updates and rule changes.
• Environment and intercompany design included in scope, not left as a later phase.
• Migration defined by object, history depth and reconciliation responsibility.
• Testing that includes Jordanian scenarios, a failed e-invoice submission and a fils-level rounding test.
• Support in Jordanian working hours after go-live, with a route for urgent submission issues.

I am independent of Microsoft and of every partner. No license or service fee reaches me from the deal, so my comments are about fit and risk only. If a lighter platform would serve the Jordanian business better, the note says so. Related pages: the Business Central overview, ERP proposal review, ERP consulting in Jordan and my Jordan page.