Business Central Consultant, Bahrain

NBR VAT cases for traders and exporters

The National Bureau for Revenue runs VAT in Bahrain, and your tax advisor decides how each of your transactions should be treated. I translate that advice into Business Central setup and tests; I do not give the advice itself.

Services firms tend to worry about foreign clients. Traders and exporters based in Bahrain have a different list, and it is longer than most first proposals assume:

• Shipments cleared at a Bahraini port or the causeway, with VAT taken from the customs declaration instead of the overseas seller's invoice.
• Goods sold to customers in Saudi Arabia or other GCC countries and shipped out of Bahrain.
• Local sales at the standard rate, plus any zero-rated or exempt categories your advisor identifies.
• Services bought from suppliers abroad under reverse charge.
• Purchases where input tax is blocked, such as some entertainment or vehicle costs, if your advisor says so.
• Credit notes and returns that must reverse the original treatment exactly.

For each case I record the VAT business and product posting groups, the calculation type, the accounts and the statement line. Then the partner posts a set of test documents and produces the VAT statement, and your accountant compares it with what the return should show. Mismatches usually trace to a wrong default on a customer, vendor or item, which is easy to fix before go-live and painful afterward. The Dynamics 365 consultant Bahrain page covers product choice and hosting.

Dinar precision and the currencies around it

The Bahraini dinar carries three decimals and is pegged to the US dollar. A Bahrain-based regional business, though, rarely lives in dinars alone. Customers may pay in Saudi riyals, suppliers invoice in dollars or euros, and some staff costs are recharged from other entities in their own currencies.

What I design and test:

• Currency rounding: three decimals for the dinar, with unit-price precision chosen for bulk goods and invoice rounding switched on only if finance wants it.
• Exchange rate source: who updates rates, how often, and whether an automatic rate service is used.
• Revaluation: month-end adjustment of open foreign currency receivables, payables and bank accounts, with separate accounts for realized and unrealized differences.
• Receipts in another currency: a riyal payment applied to a dinar invoice, with the residue cleared by application rounding instead of lingering on the account.
• Bank files: payment files that carry three decimals exactly as your bank's portal expects.

Because the peg keeps dollar movements small, finance teams sometimes skip revaluation setup. That leaves euro and other balances misstated at month-end. I include a revaluation run in UAT with expected results prepared in advance, and I check that every app in the proposal, including any banking or expense add-on, respects the third decimal. Related considerations are on the multi-currency ERP page.

Dimensions for markets served and lines of business

A company in Bahrain that sells into Saudi Arabia, Kuwait and the rest of the Gulf usually wants to know which market earns its keep. Often there is no separate legal entity per market, so the answer has to come from analysis inside one company's ledger.

The dimension plan I start from:

• Market served: Bahrain, Saudi Arabia, other GCC and rest of world, defaulted from the customer so salespeople do not choose it.
• Business line: distribution, service, rental or projects, defaulted from the item or resource.
• Cost center: sales, operations, warehouse and administration, defaulted from employees, vendors and fixed assets.

Market and business line are usually the strongest candidates for global dimensions, since almost every report filters by them. Cost center may be a shortcut dimension. Value posting rules then make market mandatory on revenue and cost of sales, so the margin by market report never has an unassigned line.

Shared costs need a rule too. Warehouse, regional management and marketing costs can be allocated by revenue, volume or headcount, either through allocation accounts or a monthly journal. I agree the method with finance and leave it documented, because nobody remembers the logic a year later. If the market view later justifies separate legal entities, the same dimension values carry into intercompany and consolidation design. My ERP solution design work covers this.

Migrating from QuickBooks, Xero, Sage or older NAV

Bahrain companies reaching Business Central usually come from a cloud accounting product that has been stretched too far, from a Sage installation, or from an older Dynamics NAV system that has become hard to support.

Each starting point shapes the work:

• QuickBooks or Xero: finance data is usually clean, but stock, units and locations often need to be built properly for the first time, and class or tracking categories map to dimensions.
• Sage: account structures and departments often need simplifying, and multi-currency history may be inconsistent.
• NAV: data structures are familiar, so the effort shifts to reviewing customizations and deciding which survive. Ask the partner whether Microsoft's migration tooling covers your version.

For Bahrain I usually propose moving the trading parties already mapped to the new posting design with their VAT numbers, every unsettled invoice or credit note in its own currency with its tax amount, outstanding orders, inventory per location valued at cutover, fixed assets and their depreciation, and monthly ledger balances for comparison. Detailed transaction history remains available in the old system or an archive. No trial load is accepted until the legacy trial balance, receivable and payable aging and VAT control accounts agree with it. Method notes are on moving off QuickBooks and under ERP data migration.

Partner proposals, and when a lighter system is enough

I hold no partnership with Microsoft and sell no subscriptions or services from any partner. That lets me review a Bahrain proposal purely on whether it fits your business, using the vendor proposal review approach.

Local VAT reports and bilingual layouts in Bahrain have commonly been delivered through partner or publisher apps rather than the base product. That may change, so I check it each time. My other questions:

• Is VAT testing, including a return dry run, in scope, or left to the client?
• Are imports, GCC sales and reverse charge configured, or only standard local VAT?
• Which layouts are bilingual and which documents are covered?
• Does migration include open documents and balances?
• Are bank files and exchange rate services included?
• Who prepares test scripts, and is more than a single test cycle priced?
• Do support hours match your working week?

Sometimes the honest conclusion is that Business Central is too much. A single company with modest stock and no consolidation can often stay on a cloud accounting tool that already supports Bahrain VAT. I say so when the requirements point that way. Platform-neutral advice for the kingdom sits on my Bahrain ERP consulting page, with a summary of remote engagements on the Bahrain overview.