Business Central Consultant, Qatar

Posting groups when no VAT return drives the design

In Business Central, users do not choose accounts on most documents. The system finds them from posting setup: the customer's general business posting group meets the item's general product posting group and returns a revenue or cost account, while customer, vendor and inventory posting groups decide the balance sheet side. A careless matrix produces a ledger that reconciles but tells management nothing.

I am not aware of any general VAT operating in Qatar, so ask your tax advisor to confirm it, since tax rulings are theirs to make. That removes return boxes from the design but not the need for structure. For a Qatar company I usually separate:

• Revenue streams: contract revenue, supply-only sales, service and maintenance, rental of equipment.
• Customer types: government and semi-government, main contractors, private clients and related companies, each with its own receivables account where finance wants it.
• Retention receivable and payable: held apart from trade balances so aging and release are visible.

I also leave VAT posting setup in a clean, minimal state rather than deleting it, so a future indirect tax could be introduced through configuration. Corporate income tax, withholding on some payments abroad and the arrangements for Qatar Financial Centre entities are topics for your advisor; my job is a chart of accounts that gives them the figures without rework. The Dynamics 365 consultant Qatar page covers product choice, payroll and hosting.

Dimensions for contracts, divisions and joint ventures

Dimensions are where Qatar finance teams win or lose their management reporting. Business Central allows a small number of global dimensions that sit on every entry and further shortcut dimensions that are faster to enter but slower to analyze, so choosing which is which is a real decision.

The pattern I start from for a project-led Qatar business:

• Global: contract or job, and division or business line, because nearly every report filters by them.
• Shortcut: department, joint venture or consortium share, and sometimes site or vessel for marine and logistics firms.
• Default dimensions: set on jobs, customers, vendors, fixed assets and employees so users rarely type a value.
• Posting rules: code mandatory on cost accounts, same code where a contract must never be changed, and blocked combinations to stop impossible pairings.

Joint ventures deserve extra care. Where a Qatar contractor shares a project with a foreign partner, finance usually needs the JV's results both inside the company and as a separate statement for the partners. Depending on the JV's legal form, that may mean a separate company in Business Central or a dimension with its own reporting. I write the options down with your auditors' view before setup, because changing a global dimension after go-live is disruptive.

Overloading dimensions is the opposite risk. Every extra value list is a field someone must fill correctly on every document, so I keep only what a named manager will actually read.

Sister companies, intercompany and the group view

Many Qatar owners run a contracting company, a trading company that supplies it, and perhaps a manpower or equipment rental company that charges both. Business Central treats each as its own company, and the value comes from designing how they trade with each other.

What I settle with finance:

1. Intercompany partners and mapped accounts: so a sales invoice from the trading company creates a matching purchase document in the contractor's inbox, with the same amount and reference.
2. Recharge rules: staff on loan, shared premises and equipment hire between companies, with a monthly routine rather than year-end journals.
3. Pricing: whether goods move at cost or with a margin, which affects stock valuation in the group view.
4. Consolidation: a consolidation company that imports each trial balance, eliminates intercompany balances and gives the owners one set of numbers. Exchange rate methods are needed where a sister entity sits in another GCC country and books in its own currency.

Unmatched intercompany balances are the most common group close problem I see. I add a reconciliation report and a named owner to the design, and I test it during UAT with deliberately mismatched entries. Groups weighing a different platform for this can compare approaches on the multi-company ERP page.

Moving from NAV, GP or Tally without importing old habits

Qatar companies arrive at Business Central from very different starting points, and each brings its own risk.

• Dynamics NAV: often heavily customized over the years. I list every modification and ask the business which ones still matter, because rebuilding all of them as extensions is the fastest way to inflate a project. Microsoft offers migration tooling for some on-premises versions; ask the partner whether it applies to yours.
• Dynamics GP: account segments usually split into a main account plus dimensions. Finance, not the developer, should own that mapping.
• Tally or a local package: ledgers often mix customers, suppliers and expenses, and stock groups rarely match how items are sold. Masters need rebuilding, not copying.

The scope I recommend for most Qatar projects: open customer and vendor invoices with original references, retention balances by contract, open purchase orders and subcontract commitments, stock by location, fixed asset registers with accumulated depreciation, and monthly general ledger balances for comparison. Older transaction detail remains searchable in the retired system or an export archive.

Each test load is reconciled against the source trial balance and aging reports before the next one starts. My legacy migration notes describe the checks, and ERP data migration explains how I run them.

Questions I put to a Qatar partner's statement of work

A Business Central proposal for Qatar can look complete and still leave the hard parts to you. I read it with your design in hand and convert each gap into a question the partner must answer in writing, following my vendor proposal review approach.

The points I check most often:

• Is the localization described, and does it come from Microsoft, an app publisher or the partner's own code?
• Are retention, advances and progress billing standard features, a third-party app or custom development?
• Is payroll included, excluded or assumed to be another vendor's problem?
• Which Arabic or bilingual report layouts are in scope, and how many?
• Does migration include open items and balances, or master data only?
• How many UAT rounds are supported, and who writes the test scripts?
• Do support hours cover the Qatar working week, including Ramadan timings?

Business Central is not always the answer. A single trading company without multi-entity needs may be better served by a lighter accounting product, and a business without an internal system owner will end up dependent on the partner for every change. If your requirements point that way, you will hear it from me plainly. For how I support Qatar businesses beyond Business Central, start at the Qatar overview or my Qatar ERP consulting page.