Business Central Consultant, Lebanon

Start with Microsoft's availability list

Microsoft sells Business Central online only in the countries and regions it lists, and it publishes that list alongside the localizations it maintains itself. Before anyone prices a project, check the current list for Lebanon and ask each partner to state in writing which country version they would deploy for your Lebanese company, how it would be licensed and where its data would be stored. If the answer relies on an affiliate abroad or on a partner-built localization, that belongs in the written reply as well.

This is not a formality. The country version decides which local features exist out of the box, what the partner must build, and what happens to that work when Business Central receives its regular updates. Answers from different partners often differ, and the differences carry cost and risk.

I put the answers side by side with the questions that follow from them: who maintains any localization extension, how your accountant will verify VAT outputs, which document layouts must be built for Arabic, French or English use, and how a later change of partner would affect the extension. The Dynamics 365 in Lebanon page discusses the broader product family; this page stays with Business Central's setup.

Posting groups and dimensions your accountant can read

Business Central does not ask users which account to post to. It derives accounts from posting groups assigned to customers, vendors, items and resources, combined in setup tables. When those tables are designed carelessly, the system posts confidently to the wrong accounts, and month-end becomes a series of reclassifications.

I prepare a posting group matrix with your accountant:

• General business and product posting groups for local customers, clients abroad, affiliates, goods and services.
• VAT business and product posting groups whose combinations hold the treatment your accountant confirms.
• Customer, vendor and inventory posting groups that decide the receivable, payable and stock accounts.

Dimensions carry the management view. Business Central offers global dimensions stored on every entry and further shortcut dimensions on entry screens, so the choice of which become global matters for filtering and reporting. For a Lebanese group I usually consider business line, branch or outlet, project and affiliate, then set default dimension values on customers, items and accounts, with posting rules that block entries missing a mandatory value.

The partner configures the tables; I check each combination by posting test documents and reading the resulting entries with your accountant. The ERP solution design page shows how I record these choices.

Designing the additional reporting currency

Each Business Central company keeps its ledger in a local currency, and you can switch on an additional reporting currency so that general ledger entries also store an amount in a second currency. For Lebanese groups that read results in more than one currency, this is often the deciding feature, but its behavior depends on choices made at setup.

The questions I settle with your accountant before the partner configures it:

• Which currency is local and which is additional, given how each company is registered and reports.
• Which exchange rates feed the additional amounts, who maintains them and on what schedule.
• When the exchange rate adjustment routine runs and how its results are reviewed.
• How residual differences between the currencies are posted and checked.
• Whether a management rate that should not affect the ledger is kept outside it as reporting data.

Switching the feature on after transactions exist is possible but disruptive, so I prefer to decide early and test with a full month of sample documents: sales and purchases in each currency, payments on different dates and a month-end adjustment. Reports in both currencies are then compared with figures your team calculates independently. The multi-currency ERP page discusses the general principles.

Reading a partner's statement of work

You license and implement Business Central through a partner, and the statement of work becomes the document that defines what you receive. Lebanese groups sometimes sign one written for a generic project, then discover that localization, migration or reporting were assumptions rather than commitments. I review it on your behalf, without any commercial interest in the outcome.

The sections I read most closely:

• Deliverables and exclusions. Each process in your requirements should map to something delivered or something explicitly excluded.
• Assumptions. Phrases such as standard functionality only or client provides clean data shift work and cost to you.
• Data migration. Who extracts, cleans, loads and reconciles each data set.
• Extensions. Who owns the code, how it is updated and what happens if you change partner.
• Acceptance and change control. How a deliverable is accepted and how new requests are priced and approved.
• Support after go-live. Coverage hours, response expectations and the language support is given in.

I return a marked-up copy with questions for the partner, then help you compare revised versions. The vendor proposal review page explains the method, and the Lebanon ERP consultant page and Lebanon hub describe my wider work.