Business Central Consultant, Egypt

Availability, local apps and who owns them

The online Business Central service is sold only in countries Microsoft lists, with some localizations built by Microsoft and others delivered by partners through apps. Egypt's position on that list, and what the local functionality includes, should be checked against Microsoft's current information and confirmed in writing by each bidding partner rather than assumed from a sales conversation.

For an Egyptian rollout there are usually at least two layers of local software: an app for local accounting and reporting features, and an app or service that submits electronic invoices and receipts to the Tax Authority. Sometimes one vendor supplies both, sometimes different firms do. For each I record:

• Publisher and licensing. The publisher, the licensing basis and whether the cost scales with users, documents or companies.
• Separation from the partner. Whether you can keep using the app if you change implementation partner later.
• Update commitment. How the publisher keeps the app compatible with Microsoft's regular updates and with rule changes.
• Support route. Who users call when a submission fails at month end, and in which hours.

This inventory becomes part of the contract file. Your tax advisor determines which obligations your company carries; I do not give tax advice. The broader rollout questions for Egyptian entities are covered on my Dynamics 365 consultant Egypt page.

VAT posting groups and the general posting setup

Posting groups, in combination, determine the accounts Business Central uses for each entry. VAT business posting groups describe the customer or vendor, VAT product posting groups describe what is sold or bought, and the setup table links each pairing to a rate, a calculation type and accounts. General business and product posting groups do the same for revenue, cost of sales and purchases.

With your accountant I draft a matrix covering Egyptian cases such as:

• Domestic sales and purchases under the treatments your advisor defines, including exempt items where they apply.
• Exports, posted to separate revenue accounts and the VAT treatment your advisor confirms.
• Imports, where VAT paid at customs and clearing charges need their own handling, often through purchase documents from the clearing agent.
• Deductions on supplier payments, which may need the local app or a defined journal process if not covered natively.
• Intercompany sales and purchases kept apart from third-party revenue and cost.

VAT statement lines are then configured so the statement reproduces the figures your accountant files, and each combination is tested in the partner's sandbox with real documents. A clear matrix also makes the partner's configuration easier to review, because every posting can be traced back to an agreed line. Treatments and current rules are confirmed by your tax advisor.

Item codes, units and customer data for electronic documents

Electronic invoices in Egypt carry structured item and party data, and most rejections trace back to master data rather than to the connector. In Business Central, that data lives in item cards, units of measure, customer cards and company information, sometimes extended by fields the connector app adds. Deciding early where each value lives, and who maintains it, avoids a stream of rejected documents in the first weeks of live use.

The mapping I prepare with your finance and sales operations teams covers:

• Item codes. Where the registered code for each item is stored, whether one item can map to more than one code, and what happens when a new item is created without one.
• Units of measure. How Business Central units translate to the units the electronic system expects, set once in a mapping table.
• Customer details. Registration numbers, addresses and customer type captured on the customer card, with validation before the first invoice.
• Branches and activities. How issuing locations are represented if documents come from more than one site.
• Arabic descriptions. Which fields carry Arabic text, written and checked by your bilingual staff.

I then include master data defects in acceptance testing: an item without a code, a wrong unit, a customer missing a registration number. The system should block or flag each one before submission. The ERP data migration service covers the clean-up of existing records.

Dimensions and a reporting currency in a volatile pound

Egyptian manufacturers want cost and margin by plant, production line and product family; contractors want them by project and contract; exporters by destination market. Business Central dimensions provide these views without multiplying accounts. I propose global dimensions for the most frequent analyzes, shortcut dimensions for the rest, default values on items, customers and locations, and mandatory rules on revenue and cost accounts so nothing posts untagged.

Currency needs equal care. Many Egyptian entities report to a parent or to lenders in dollars or euros. An additional reporting currency in Business Central records each ledger entry in both pounds and the chosen currency. When the pound moves sharply, that dual record shows management what happened in both currencies, but only if the setup is deliberate:

• Decide on the reporting currency before posting begins, since adding it later is a heavy exercise.
• Agree the rate source and update routine with your accountant, and restrict who maintains rates.
• Review exchange rate adjustment runs before posting, since they affect both currencies and receivables, payables and bank balances.
• Check how inventory values appear in the reporting currency, so margins on stock bought before a move are understood.

I prototype the main management reports with sample data, so finance sees both views before the partner commits. Wider currency controls appear under multi-currency ERP.

Scope checks for an Egyptian Business Central contract

A partner's statement of work for an Egyptian rollout should state clearly what is included in areas that often turn into change requests. Each clause is read against your requirements, and you receive the questions to send back. The points I check most closely:

• Connector and local apps named, with licensing, publisher and support arrangements, and whether their setup is in the fixed scope.
• Signing arrangements for electronic documents: who installs and maintains the signing method, and who is responsible when credentials expire.
• Arabic and bilingual layouts listed by document, with the number of revision rounds and who approves wording.
• Data migration by object and history depth, with the master data clean-up responsibility made explicit.
• Testing, including a rehearsal of rejected and corrected electronic documents.
• Support after go-live in Egyptian working hours, with response expectations and a route for urgent submission failures.

I do not sell licenses or implementation, and no partner pays me, so the review is not shaped by deal size. Where a smaller platform would serve the company better, my note says that plainly. Related reading: Business Central explained, vendor proposal review, my Egypt ERP consultant page and the Egypt hub.