Microsoft Dynamics 365 Business Central is now the main ERP platform for many employers that once relied on Dynamics NAV, changing how systems are maintained, extended and integrated.
That shift matters for pay because the role now combines ERP knowledge, AL development, cloud delivery and integration skills. A Microsoft Business Central developer builds and customises solutions in Dynamics 365 Business Central, usually working with finance, operations and project teams to turn business requirements into reliable extensions, integrations and technical changes.
What a Microsoft Business Central developer does
A Business Central developer works inside the Microsoft Dynamics 365 Business Central environment to design, build, test and support technical solutions. The work can include creating AL extensions, modifying existing functionality, integrating Business Central with other systems, investigating performance issues and supporting upgrades from older Dynamics NAV or C/AL-based solutions.
The role is different from a purely functional consultant role, although the two often overlap on projects. Developers are expected to understand the business process they are changing, especially in finance, stock, warehousing, manufacturing or project accounting, but their value is usually judged by how well they can implement maintainable technical solutions. Readers who need product context before comparing salary ranges may find this overview of Microsoft training paths useful as a starting point.
In practice, the highest-value work is rarely simple field changes or screen customisation. Employers tend to pay more for developers who can refactor legacy C/AL customisations into modern AL extensions, build API-led integrations, connect Business Central with Power Platform or other Dynamics 365 applications, and use Azure services or Azure DevOps to support release management. Those skills reduce upgrade risk and make SaaS Business Central easier to maintain over time.
UK salary ranges for Microsoft Business Central developers
For UK permanent roles, the source salary ranges indicate that entry-level Microsoft Business Central developers commonly sit around £25,000 to £35,000 per year, while experienced developers can reach roughly £40,000 to £70,000 per year. These figures should be read as gross annual base salary in GBP, not take-home pay, and they should be checked against current UK sources such as Reed, Glassdoor, LinkedIn Jobs, Hays and specialist Dynamics recruitment reports before publication or salary review.
The lower end of the range usually reflects developers who are still learning Business Central, have limited ERP project exposure, or need support from senior colleagues on architecture and release decisions. The middle of the market is often where developers can independently build AL extensions, debug production issues and work with functional consultants to translate requirements into technical specifications. The higher end is more likely where the developer can lead technical design, own integrations, review other developers’ work, and support migrations from NAV to SaaS Business Central.
Salary benchmarking becomes unreliable when UK figures are mixed with US or European data. A role advertised in dollars or euros may look comparable at first glance, but tax, benefits, pension expectations, healthcare arrangements and employment law are different. UK candidates and hiring managers should compare gross annual base salary, bonus potential, pension contribution, working pattern and training budget before deciding whether an offer is competitive.
Why location still affects pay in remote and hybrid roles
London and the South East often carry higher salary expectations because of cost of living and employer competition, but remote work has made regional benchmarking less straightforward. Some employers still apply London-weighted bands when the role is attached to a London office, even if the developer works mostly from home. Others use national bands and pay the same range regardless of where the employee lives in the UK.
Fully remote roles create another distinction: some companies price the role by the employer’s office location, while others price it by the employee’s location. That difference can change the offer, especially when a London-based partner hires a developer living outside the South East or when a regional end-customer recruits nationally. Candidates should ask which policy is being used rather than assuming that “remote” automatically means London-weighted pay.
Regional variation also depends on the type of employer. A local end-customer may pay less than a specialist Microsoft partner but offer a narrower and more stable environment. A partner may expect travel, multiple customer projects and faster context-switching. An ISV may pay a premium where the developer has productised AL expertise and understands how to build repeatable functionality rather than one-off customer changes.
What raises or lowers a Business Central developer offer
Experience matters, but employers rarely price the role by years alone. A developer who has spent several years on small customisations may be offered less than someone with shorter experience but stronger exposure to SaaS migrations, extension architecture, APIs, automated testing and production troubleshooting. The strongest offers usually reflect evidence that the developer can reduce project risk as well as write code.
Several technical and business skills can influence pay materially:
- Modern AL extension development, including maintainable architecture and extension lifecycle management.
- Performance tuning in Business Central, especially where reports, posting routines or integrations affect users at scale.
- API, Power Platform and Dynamics 365 integration work, where Business Central must operate as part of a wider Microsoft environment.
- CI/CD experience with Azure DevOps, source control discipline, automated testing and release pipelines.
- Vertical knowledge in manufacturing, distribution, finance-heavy environments, warehousing, costing or project accounting.
Certifications can help support a salary case, particularly when they match the work being discussed. The Microsoft Certified: Dynamics 365 Business Central Developer Associate credential, commonly associated with MB-820, is most relevant for developers who want to validate Business Central technical skills. The Business Central developer MB-820 course is one route for professionals preparing to formalise those skills, but employers will still look for practical evidence from projects, code quality and problem-solving.
Functional understanding can also increase a developer’s value. A technically strong developer who understands posting groups, dimensions, costing, purchase flows or warehouse processes can make better design decisions and challenge weak requirements earlier. For professionals who are closer to process design than code, the functional route may be the better fit; broader Microsoft learning options, including Microsoft training access, can support either direction depending on career goals.
Permanent salary versus contractor day-rate work
Permanent and contract roles should not be compared by headline pay alone. A permanent salary includes a package around the base figure, while contract income depends on day rate, billable days, IR35 status, gaps between engagements, tax treatment, insurance, accounting costs and the absence of employee benefits. A high day rate can still produce a less predictable year if the engagement is short or if there are long breaks between contracts.
A useful decision framework starts with stability. Permanent employment usually suits developers who value predictable income, paid leave, pension contributions, sick pay, structured progression and a clearer place inside a team. Contracting may suit developers who are comfortable with commercial risk, have in-demand specialist skills and can manage pipeline, administration and negotiation without relying on one employer.
The second factor is the day-rate-versus-base comparison. Contractors should compare realistic annual billable days against permanent salary plus benefits, rather than multiplying a day rate by every working day in the year. The third factor is IR35 and tax complexity, because inside and outside IR35 engagements can produce different net outcomes even when the advertised day rate looks similar. The fourth factor is skill development: partner work can broaden exposure across many customers, while ISV or end-customer roles can deepen product or domain expertise over a longer period.
Location also affects contract work. Some UK Business Central contracts remain remote, while others require periodic site attendance for discovery, testing, go-live support or workshops. A higher rate may be less attractive if travel costs, unpaid travel time or short extensions reduce the real value of the engagement.
Total compensation: what sits beyond base salary
Base salary is only one part of the offer. In the UK, pension contributions, annual bonus potential, paid leave, private medical insurance, certification support, conference attendance, flexible working and training budgets can change the value of a package. A slightly lower base salary can be competitive if the pension contribution, paid learning time and working pattern are materially better.
For example, one offer may provide a higher base salary but limited training support and a fixed office pattern. Another may offer a lower base salary but include paid certification time, a stronger pension contribution, remote working and exposure to major Business Central migration work. The better offer depends on the developer’s stage of career, financial needs and the kind of experience that will improve future earning power.
Hiring managers should also treat learning and development as part of retention, not simply as a perk. Business Central changes regularly, and developers who are not given time to keep up with AL, APIs, Microsoft release waves and test tooling may become less effective. Candidates should ask whether training is funded, whether study time is available, and whether certifications are tied to project assignments or career progression.
Partner, ISV and end-customer pay dynamics
Microsoft partners, ISVs and end-customers often value Business Central developers differently. Partners usually need developers who can move between customers, interpret varied requirements and work with consultants under delivery pressure. The base salary may sometimes be more conservative than a high-paying end-customer role, but the learning curve can be faster because the developer sees more implementations, upgrades and integrations.
End-customers tend to offer deeper knowledge of one business environment. The work may involve fewer greenfield projects, but developers can gain strong insight into operational processes, reporting needs and long-term system governance. In organisations with complex finance, manufacturing, warehousing or distribution requirements, that domain knowledge can be a meaningful salary lever.
ISVs sit slightly differently again. They may pay more for developers who can build reusable Business Central apps, think in terms of product architecture, handle extension compatibility and understand AppSource-style quality expectations. Productised AL development is different from bespoke customer work because changes must be supportable across multiple customers and Business Central updates.
How to negotiate a Business Central developer salary
A strong negotiation starts with evidence, not a general statement about market demand. Candidates should bring examples of relevant project work: an AL extension that reduced manual processing, a NAV-to-Business Central migration, an integration with Power Platform or an improvement that reduced posting or reporting delays. The aim is to connect technical skills to business outcomes.
It is usually better to discuss salary once the employer understands the candidate’s fit for the role. At that point, the candidate can compare the offer with UK market ranges, explain which skills justify a higher band and ask about the full package. If the base salary cannot move, pension, bonus, remote working, certification support, paid study time or review timing may still be negotiable.
Candidates should avoid three common benchmarking mistakes. First, US salary figures should not be converted into GBP and treated as a UK equivalent. Second, gross salary should not be confused with net take-home pay or contractor income. Third, benefits should not be ignored, especially when comparing permanent roles with contract opportunities.
Reading the market with care
The Business Central developer market in the UK is shaped by cloud migration from NAV, the need for modern AL skills, and the growing importance of integrations across Microsoft’s business applications. Developers who can combine clean technical delivery with finance and operations understanding are better placed than those who focus only on syntax or narrow customisation tasks.
The most practical next step is to benchmark against current UK adverts and salary surveys, then compare that evidence with the responsibilities of the specific role. Anyone assessing whether their skills match the market can also speak with Readynez about training options that support Business Central developer progression, including preparation for recognised Microsoft certification paths.
