Skip to content

Microsoft Dynamics 365 · F&O · Business Central · Power Platform

Most Dynamics projects fail at the licence decision, years before go-live.

Business Central sold to an organisation that needed Finance & Operations becomes a rebuild in year three. F&O sold to a company of ninety people becomes a budget nobody can defend. Answer five questions below and we will tell you which one you need — including when it is the cheaper one.

AL and X++ extensions · ZATCA Phase 2 · UAE FTA · Peppol · Dataverse · Fabric

Platform fit

Business Central or Finance & Operations?

Five questions. The answer appears on this page — no email, no gate, and we will happily tell you that you do not need the larger product.

01How many people will touch the system?
02How many legal entities consolidate?
03What does production look like?
04How many statutory regimes do you file under?
05How complex is warehousing?
Recommendation0/5

Answer all five and we will tell you which platform fits — including when the answer is the cheaper one.

No email, no gate. The result appears here.

Indicative. Licensing and statutory scope can move the answer.

Comparison

The differences that actually decide it

Licensing pages compare feature lists. These are the five dimensions that determine whether a deployment holds up in year three.

DimensionBusiness CentralFinance & Operations
Typical headcount10 – 300300 – 10,000+
Legal entities1 – 5Unlimited, with eliminations
Extension languageALX++
WarehouseBins, basic directed pickingWave, load, yard, RF
ManufacturingAssembly, light MRPMulti-site, multi-level BOM
Typical timeline6 – 12 weeks16 – 24 weeks

Migration

Off NAV, AX, GP or SAP without a variance

Configuration packages and Azure Data Factory get the data across. The gate is what stops a rounding difference reaching production.

Extract then Sanitise then Reconcile then Cutover01ExtractNAV · AX · GP · SAP02SanitiseConfig packages, ADF03Reconcile$0.00 variance gate04CutoverDual-write, then switch
Phase 03 is a gate, not a milestone — it either reads $0.00 or the cutover does not proceed.

Statutory

E-invoicing mandates are where GCC projects bite

A clearance rejection is not a reporting problem, it is a stopped invoice. We build these as native extensions against the official schemas instead of bolting on a middleware subscription.

ZATCA Phase 2

Saudi Arabia

UBL 2.1 XML, ECDSA signatures, TLV Base64 QR, direct Fatoora clearance.

FTA VAT 201

United Arab Emirates

AED dual-currency ledgers, 5% and 0% rules, audit-ready FAF output.

InvoiceNow / Peppol

Singapore

Peppol Access Point, automated B2G and B2B transmission.

EU e-invoicing

European Union

Country chart templates, OSS/IOSS, Intrastat.

The practice

Fourteen surfaces, written up in full

Each of these is a page with real deliverables, not a capability tile.

Questions

Dynamics 365, answered straight

  • We deploy native AL and C# extensions that generate UBL 2.1 compliant XML files, compute ECDSA cryptographic digital signatures, generate ZATCA-approved TLV Base64 QR codes, and communicate directly with the Saudi ZATCA Fatoora clearance/reporting portal APIs.

Next

Bring the implementation that is already slipping.

We are often brought in mid-project. Send us the scope, the current partner's plan and the date you are supposed to go live. You leave with a written assessment whether or not we work together.