How to Choose a Dynamics 365 Finance & Operations Partner in the UAE

Two executives looking concerned while reviewing a Dynamics 365 project on a tablet, after problems surfaced late in the implementation
Write your requirements, test F&O expertise and review the design before costly rework.
Two executives looking concerned while reviewing a Dynamics 365 project on a tablet, after problems surfaced late in the implementation

Table of contents

Authors

Picture of Hichem Chekebkeb

Hichem Chekebkeb

Subscribe to our newsletter

Short answer: To choose a Dynamics 365 partner in the UAE, start with your own requirements, not with partner websites. Write down your processes, volumes and compliance needs. Then test each partner’s expertise on your hardest scenarios. Finally, have an independent F&O expert review their design before anyone builds it. A design fix costs days; a live-system fix can cost a re-implementation.

The UAE has dozens of Microsoft partners. Most promise the same things: certified experts, end-to-end implementation and GCC compliance. That makes the choice hard. A wrong choice is also expensive, and it usually shows up late. By the time users test the system, the design is already built. From then on, every change means rework, reconfiguration or, in the worst case, a new implementation.

In 2027 the stakes go up. UAE e-invoicing becomes mandatory on 1 January 2027 for companies with revenue of AED 50 million or more. Everyone else follows on 1 July 2027. Your partner must connect Dynamics 365 to an Accredited Service Provider (ASP) before your date.

This guide is for finance directors and IT managers in the UAE. It helps you choose a Dynamics 365 partner for Finance & Operations (F&O), or check the one you already have. It covers what to prepare, how to test expertise, the red flags and when to bring in an independent reviewer.

Why Dynamics 365 projects go wrong before they start

Most troubled projects we review did not fail on technology. Instead, they failed on two things that happened before the first line of code. First, the company never wrote down its real requirements, so the partner quoted and designed for a simpler business. Second, nobody on the customer side could judge whether the partner’s design was good. As a result, problems surfaced in user testing or after go-live, when they cost the most to fix.

When the problem is found What fixing it usually means
During requirements Rewrite a document
During solution design Change the design before anyone builds it
During build or testing Rework code and configuration; the timeline slips
After go-live Data fixes, retraining and sometimes a re-implementation

Step 1: Write down your requirements first

Partners can only design for what you tell them. So before you choose a Dynamics 365 partner, prepare a short requirements pack:

  • Processes: your end-to-end flows, such as tender to invoice, procure to pay and hire to pay.
  • Volumes: legal entities, users, sites, projects and invoices per month.
  • What makes you different: how you price, approve, cost projects and bill customers.
  • Integrations: banks, your e-invoicing ASP, payroll and WPS, and any other systems.
  • UAE compliance: VAT, corporate tax and your e-invoicing phase.
  • Reports: the reports management actually uses each month.

Mark each item as must-have or nice-to-have. Then give the same pack to every partner, so you compare like with like.

Step 2: Test expertise, not marketing

Badges, logos and company size are a starting point. However, they describe the company, not the people who will design your system. So test expertise directly.

Before you choose a Dynamics 365 partner, pick your two hardest scenarios. For example, how a site material request becomes a project cost, or how payroll splits across projects. Ask each partner to walk through how they would handle them in standard F&O. Good partners show you the standard feature first and explain where it falls short. Weak partners jump straight to “we’ll customize it”.

Also ask who will design and build your solution, and meet them before you sign. Their experience on F&O projects like yours matters more than anything on a website.

Step 3: Check that they start with standard F&O

Consultant and client reviewing a Dynamics 365 Finance and Operations solution design on a laptop

Ask for a fit-gap analysis. It should show which requirements standard F&O covers, which need configuration and which need customization, and why. In a healthy fit-gap, standard features and configuration cover most requirements.

If a partner proposes many customizations early, ask which standard option they rejected and why. Every customization you add today must be tested with every Microsoft update for years.

Step 4: Ask how they customize

In current versions of F&O, partners can’t change Microsoft’s code directly; extensions are the only supported way to customize. That rule helps. Still, an extension can fight the standard process just as badly as old-style code did.

So ask to see a sample technical design document. Also ask whether someone reviews the code before release, and whether all code sits in your own Azure DevOps project. Finally, confirm in the contract that you own the code they write for you.

Step 5: Check UAE compliance know-how

Your partner should speak confidently about three topics:

  • VAT and corporate tax. VAT is 5%. Corporate tax is 9% on taxable income above AED 375,000. Your tax setup in F&O must support both.
  • E-invoicing. Invoices must leave F&O in the PINT AE format through an ASP. Microsoft has announced built-in UAE e-invoicing for F&O, with general availability planned for December 2026. Even so, you still need an ASP and a working connection to it. Late adoption costs AED 5,000 per month.
  • Payroll. Dynamics 365 has no built-in UAE payroll. Therefore, ask which add-on they use for WPS files and end-of-service gratuity, and how it posts to the general ledger.

A good test question: “Which ASP have you connected to F&O, and did you use an API or SFTP?” A partner with real experience answers in one sentence.

Step 6: Check references, support and pricing

Ask for two references from companies in your industry. Then call them, and ask three questions: What went wrong? How did the partner handle it? Would you hire them again?

Next, ask for support response times by priority, in writing, and check that support runs in Gulf working hours. Microsoft ships regular service updates to F&O, so also ask who tests your customizations before each one. Finally, ask how they price change requests, and request a sample estimate.

Questions to ask in the first call

  1. How would you handle our hardest scenario in standard F&O?
  2. Which of our requirements need customization, and what standard option did you consider first?
  3. Who will design and build our solution, and can we meet them?
  4. Can we see a sample solution design and technical design document?
  5. Where will our code live, and who owns it?
  6. Which ASP have you connected to F&O for UAE e-invoicing?
  7. Can we speak to two clients in our industry?
  8. How do you price change requests, and who tests our customizations before Microsoft updates?

Red flags

  • They say yes to every requirement without asking why.
  • The fit-gap lists many customizations and no standard alternatives.
  • The people in the sales meeting won’t design your system.
  • Code stays in their environment, or the contract is silent on who owns it.
  • They show Business Central or CRM references when you asked about F&O.
  • Their answer on e-invoicing is “Microsoft will handle it”.

A scorecard you can reuse

Use this scorecard when you choose a Dynamics 365 partner. Score each one from 1 to 5 on each line. Then multiply by the weight and add up the results.

Check Weight What a 5 looks like
Requirements understanding 20% Played your requirements back accurately and asked about your edge cases
F&O expertise 20% Walked through your hardest scenarios in standard F&O, on screen
Standard-first approach 15% Fit-gap favors standard features; every customization is justified
Customization practice 15% Extensions, design documents, code reviews, your DevOps, you own the code
UAE compliance 10% Has connected F&O to an ASP; clear on VAT, corporate tax and payroll
References 10% Two reachable clients in your industry
Support and pricing 10% Written response times, update testing and a sample change request

Get an independent expert on your side

Even with a good partner, you are buying something you can’t fully judge yourself. That is where SysBrilliance helps. We are Dynamics 365 Finance & Operations specialists, and in this role we work on your side of the table:

  • Before you choose: we help you write your requirements pack and run the scenario walk-throughs, so you choose a Dynamics 365 partner on evidence.
  • Before the build starts: we review the fit-gap and solution design against Microsoft best practice. We also challenge customizations that standard F&O can already handle.
  • During build and testing: we review customizations and code, so problems surface while they are still cheap to fix.

When we advise on your partner selection, we don’t bid for the implementation ourselves unless you ask us to. In that role, our only job is to protect your interests.

We have seen what happens when nobody does this. At Sewan, earlier customizations had altered core F&O behavior. We analyzed them, replaced what the standard system already did and rewrote the rest as clean extensions. As a result, we cleaned up 97% of the core-harmful customizations (read the Sewan case study). That work was worth doing, but prevention costs far less.

Frequently asked questions

Can I hire an independent expert alongside my implementation partner?
Yes. Independent quality assurance is common on large ERP projects. The reviewer works for you, checks designs and code against best practice and helps you ask the right questions. A good partner welcomes it, because clear requirements and early feedback make their work easier too.

When should I bring in an independent reviewer?
Ideally before you choose a Dynamics 365 partner, and at the latest before the build starts. A review during testing still helps, but by then every change costs more.

Do I need a partner based in the UAE?
Not strictly, because most F&O work happens remotely. Even so, a partner in your time zone answers faster. It also knows UAE VAT, corporate tax and e-invoicing, and can be on site for workshops and go-live.

Can I change my Dynamics 365 partner after go-live?
Yes. You own your licenses and your data. Before you switch, make sure your code sits in your own Azure DevOps project. Also collect the latest documentation. Then plan a short handover in which the new partner reviews the system.

Is Microsoft’s built-in e-invoicing enough for the UAE?
No. Microsoft’s feature generates compliant e-invoices inside F&O. However, the law requires an Accredited Service Provider to exchange them and report to the FTA. Your partner must connect F&O to that ASP and test the full flow.

Next step

About to choose a Dynamics 365 partner, or already in a project and unsure about the design? Book a 30-minute call, and we will tell you honestly where your project stands.