Business Central Consultant, Kuwait

Keeping fils intact from price list to bank file

The dinar's three decimals are configured once in Business Central, but money passes through many places that can each drop the last digit. In Kuwaiti projects I have learned to test the journey, not the setting.

The checkpoints I include in UAT:

• Price lists and discounts: agency price lists sometimes quote finer unit prices than the invoice total shows, and line discounts on agency price lists should not round differently from the invoice.
• Documents: quotations, invoices, credit notes and statements must print three decimals in both Arabic and English layouts.
• Payments: supplier payment files and salary transfer files must carry fils exactly as the bank expects.
• Apps: every third-party extension in the proposal, such as a point-of-sale or rental app, needs the same test.
• Reporting: Excel exports, Power BI models and any custom report should agree with the ledger to the last fils.

I write these as short scripts with expected results so the partner can run them and finance can sign them. Problems found here are cheap to fix; problems found after the first month-end are not.

As I understand it, no general VAT is currently levied in Kuwait, which keeps tax setup light, though your advisor should confirm that and any income tax or levies that affect your entities. Tax advice is outside my role. The Dynamics 365 consultant Kuwait page covers group design, hosting and local integrations.

Posting groups and dimensions for brands, agencies and channels

A Kuwaiti distributor may represent many international principals. The owners ask a simple question: which brands make money once rebates, marketing support, showroom costs and slow stock are counted? Business Central can answer it if the design separates what should post differently from what should only be analyzed differently.

My rule of thumb:

• Posting groups for differences that need separate accounts: goods versus services, cooperative and retail customers versus government buyers, related companies, and inventory classes such as trading stock, demo units and spare parts.
• Dimensions for analysis that shares accounts: brand or principal, product line, channel, showroom or branch, and salesperson.

Default dimensions on items carry the brand automatically, and defaults on customers carry the channel, so a salesperson rarely chooses a value. Value posting rules make brand mandatory on revenue, cost of sales and marketing accounts. Principal rebates and marketing support received are recorded against the same brand, so the brand report shows the full picture.

One caution: Business Central limits how many dimensions can be global, and changing them later is disruptive. I choose global dimensions by asking which filters appear on nearly every management report. For many Kuwaiti distributors that is brand and channel, with branch and salesperson as shortcut dimensions. My ERP solution design work documents this before configuration.

Consolidating a Kuwaiti parent with subsidiaries abroad

Kuwaiti groups often own companies in Saudi Arabia, the UAE or further afield, each keeping books in its own currency and under its own tax rules. Business Central handles each as a separate company and brings them together in a consolidation company, but the method needs to be agreed with your auditors rather than left to defaults.

The decisions I document:

1. Business units: each subsidiary is set up as a business unit with its currency, the share consolidated and the accounts that map into the group chart.
2. Exchange rate methods: average rates for income statement accounts, closing rates for most balance sheet accounts and historical rates for equity, with the translation difference posted to a named account.
3. Eliminations: intercompany receivables, payables, sales and dividends removed, with a reconciliation of mismatches before each consolidation run.
4. Minority interests and goodwill: often calculated in a consolidation workbook outside the ERP, with the result posted back. I say plainly where standard features stop.

Subsidiaries in VAT countries need their own tax setup and possibly their own localization, which affects the partner's scope and the subscription list. I run a consolidation dry run on migrated balances before go-live so the first real group close is not the first test. Related options appear on the multi-currency ERP page.

Leaving bespoke systems and older NAV behind

Many established Kuwaiti companies run accounting software built for them years ago, or an older Dynamics NAV installation extended by several developers. Both carry knowledge the business depends on, and both hide surprises.

For bespoke systems I start by documenting what the software actually does each month: reports finance relies on, approval rules, special calculations for commissions or rebates. Some of that will be standard in Business Central, some will need an app or extension, and some can simply stop. For NAV, I build a list of modifications with their purpose and owner, then ask the business to classify each as keep, replace with standard or retire. Whether your NAV release can use Microsoft's migration tooling is a question for the partner to answer in writing.

The data scope I usually recommend:

• Customers, vendors and items mapped to the new posting groups and dimensions.
• Open receivables and payables with original references and currencies.
• Open orders, including principals' outstanding purchase orders.
• Inventory per warehouse counted on the cutover date and tied back to the ledger.
• The fixed asset register, including depreciation charged so far.
• Monthly ledger balances for prior-year comparison.

Older transactions stay readable in an archive. My legacy migration page sets out the reconciliation checks.

What I check in a Kuwaiti statement of work

Nothing I earn depends on Microsoft licenses or partner referrals, so my only interest in a proposal is whether it delivers what you need. Using the vendor proposal review method, I separate the Microsoft subscription, any third-party apps and the partner's own code, then check:

• Whether the localization in scope is named, with its publisher, or described only in general terms.
• How many Arabic or bilingual layouts are included and which documents they cover.
• Whether consolidation and intercompany are configured and tested, or left for later.
• Which integrations are included, such as point-of-sale, ecommerce or payment providers, and which are excluded.
• Whether migration covers balances and open documents or masters only.
• Who writes UAT scripts, how many test rounds are supported and what happens when a round fails.
• Support hours across the Sunday to Thursday week and through Ramadan.

I also tell you when Business Central is not needed. A single company with simple trading and no consolidation can often run on a lighter system. More on how I support Kuwaiti businesses is on the Kuwait hub and my ERP consultant Kuwait page.