Business Central Consultant Staffing for a Calendar Microsoft Sets
Functional consultants, AL developers and upgrade leads who own your extensions, your release waves and the relationship with your partner. Contract, contract-to-hire and direct hire.
KORE1 places Dynamics 365 Business Central functional consultants, AL developers and upgrade leads on contract or direct hire, typically producing a vetted candidate in 17 days, for companies that need Business Central expertise on their own payroll.
Last updated: August 29, 2026
The email comes from Microsoft. Not from your team. An update is available for your environment, it says, and here is the date it is going to run.
Somebody forwards it to the partner who built your customizations four years ago. Then everyone waits. Business Central keeps its published rhythm either way, two major releases a year in April and October, minor releases in most of the months between, and an administrator somewhere has already picked the window inside which the service is allowed in.
You can move the date. You cannot move the year. Code that will not compile against the new version eventually gets uninstalled so the update can finish.
For most companies that is a good trade. Nobody misses the eight-year upgrade projects NAV customers used to budget for, and an ERP that patches itself is genuinely better than one that doesn’t. What changes is who has to be paying attention, because an evergreen system only stays evergreen if somebody on your side is reading the notifications and can say out loud whether your extensions are ready.
Here is the part that catches people. Business Central is sold and delivered through Microsoft partners, so there is no direct implementation team to call. The people who know why your dimensions are set up the way they are sit on somebody else’s payroll, carry somebody else’s utilization target, and answer to a queue you can’t see. That arrangement works. Right up until the quarter it doesn’t.
KORE1 has recruited enterprise systems talent since 2005. Business Central is worked by the same ERP recruiters team that covers broader ERP consultant staffing, and it draws on the wider Dynamics 365 consultant practice for anything that spans the stack. Gap on the code side rather than the configuration side? That is Dynamics 365 developer staffing. If the question is how a Microsoft search gets run rather than who gets hired, that is the recruiters who work this market.
Your Partner’s Bench Is Not Your Bench
Ask a Business Central customer who owns their system. You get a pause. Then a company name that isn’t theirs.
None of which is a shot at partners. The channel is how Microsoft chose to sell this thing, and a good VAR earns every dollar of it. The problem is narrower. Partners are staffed to deliver projects, so the strongest consultants sit on implementations, and your Tuesday question about an intercompany posting group joins a queue behind somebody else’s go-live.
The shape of the call varies less than you would think. An upgrade has failed twice. On the partner side three consultants have cycled through the account inside a year, so nobody over there can tell you why the posting setup looks like that, and meanwhile finance has built a reporting spreadsheet around the outside of the system, because change requests kept coming back priced three weeks later and at some point they stopped bothering. There is no villain in this. That account is worth less to the partner than the implementation running down the hall, and everybody involved can do the arithmetic.
Acquisitions produce the other version. You wake up owning two tenants, two partners and two opinions about which chart of accounts survives. Which one do you keep? Neither VAR is neutral on that question, and neither of them is going to volunteer that they aren’t.
Firing the partner is rarely the fix. Hiring one person who can hold the other side of that conversation usually is. They read the release plan before the partner does. They know which of your seventeen customizations still earn their keep, and they can tell a half-day change request from a three-week one long before anybody has quoted it.
That person is hard to find, and the reason is structural. Almost the whole labour market for this skill sits inside partners. So we go there.
Five Months, Then One Month, Then It Isn’t Your Decision
Every Business Central major release runs the same three phases, and control only ever moves one way. The lit band on each rail is the part of the calendar that still belongs to you. Watch it drain. By the third row there is none of it left, which is why the colour has gone out of the row as well.
Update period
April or October, first workday, and it lands on existing environments roughly a week after that. From there your administrator picks any date across five months. An attempt that fails quietly reschedules itself for seven days out. Nobody outside IT notices.
Your dateGrace period
September, or March. The date can only be pulled earlier now, never pushed. Failures still notify whoever sits on the recipient list, and Microsoft may start showing ordinary end users warnings about the incompatibility in the browser and on their phones, which is often how a CFO finds out there was a problem at all.
Earlier onlyEnforced update period
Extensions blocking the update may now be uninstalled from the environment automatically so it can complete. Your data survives. It stays put and comes back when a compatible version is installed. Microsoft will not install that version for you, though, and says so plainly.
Microsoft’s
Two smaller clocks run alongside that one. Neither is hypothetical. A Marketplace app that isn’t compatible with the current version can be pulled from Marketplace thirty days after that version ships, and anything blocking a critical security update can be uninstalled within fourteen days of the fix becoming available. Breaking changes themselves are announced at least a year ahead, which is generous, and is exactly the sort of notice that only helps if somebody is reading it. Microsoft documents the whole sequence in its Business Central update cycles and app and per-tenant extension maintenance guidance.
Four Seats, and Only One of Them Writes Code
All four get posted under one title constantly. Not one labour market. They don’t price alike either.
Owns configuration, dimensions, posting setup and the conversation with finance. Turns “we need margin by branch” into something the system can genuinely report on, and knows when the honest answer is a rethink rather than another field.
Writes and maintains the per-tenant extensions, and owns whether they still compile against the next release. Closest to our Dynamics 365 developer bench.
Owns the admin center. Environments, sandboxes, update scheduling, permission sets, and the notification recipient list that decides who finds out first when an update fails.
For NAV estates and multi-entity rollouts. Rules on each customization one at a time. Adjacent to ERP project manager staffing.
Two Trackers, Sixty-Six Thousand Dollars Apart
ZipRecruiter had the national average for a Dynamics 365 Business Central consultant at $99,275 as of July 25, 2026, with most of the range sitting between $61,500 and $141,500. Glassdoor, the same month, said $165,333. Same title. Same country.
Read the footnote on the second one. That Glassdoor average rests on three submitted salaries. Three. It’s a rumour with a dollar sign in front of it, and it is still the number a candidate will quote you on the first call, so it pays to know where it came from.
Our own read is narrower and a lot less exciting. A functional consultant with three to five years of genuine Business Central delivery, rather than NAV nostalgia with a new logo on it, sits in the low six figures. AL developers price above that. The premium isn’t the language. AL is learnable in a quarter by anybody who has written C# for a living, so what you are actually paying for is whether this person has shipped an extension that survived two release waves without an incident.
Three things move the band, and seniority is only one of them. Modules first. Manufacturing and jobs costing are a different job from distribution, and the pool that has run either one in production is thin. Upgrade history second, meaning somebody who has taken a customer from NAV to Business Central online and can describe what they deliberately threw away on the way. The third is the boring one and it is usually the tiebreaker. Can they talk to finance? A consultant who sits through a month-end close and understands what people are complaining about beats one who knows more of the object model, every time.
Bands by seniority sit in our 2026 Dynamics 365 consultant salary guide, and for contract pricing against neighbouring platform work there’s the 2026 ERP consultant hourly rates breakdown.
What We Ask Before Anybody Gets Submitted
Half an hour with whoever owns the admin center saves us a fortnight of guessing. The long-form version, comp bands and an interview method included, sits in the 2026 Dynamics 365 consultant hiring guide.
- 01
Name the version
Online or on-premises, which major version you’re on, and how many waves back that puts you. A company two releases behind is hiring for a different problem than one that updates on schedule.
- 02
Count the extensions
How many per-tenant extensions are installed, who wrote each one, and whether anybody has tested them against the preview. Most people can’t answer the third part. That is itself the answer.
- 03
Say what the partner keeps
Are you supplementing your VAR or replacing them? Say which. Candidates ask inside the first ten minutes and they can hear a non-answer from across a table.
- 04
Name the modules
Manufacturing, jobs, warehouse, service. Microsoft lists Essentials at $80 per user per month and Premium at $110, and Premium is where manufacturing and service management live, so the licence tier alone tells us which pool to work.
- 05
Decide who owns the admin center
Whoever sits on the notification recipient list finds out first when an update fails. If that’s only your partner today, say so. For a lot of our clients, moving that responsibility in-house is the whole reason for the hire.
Everybody Lists the Modules. Ask About an Update That Failed.
Put six Business Central resumes side by side and the middle third is interchangeable. Finance, sales, purchasing, inventory, jobs. A line about AL. Then somewhere near the bottom, NAV 2016 or NAV 2018.
None of it separates anybody. So we ask about a bad one instead.
Walk me through an update that failed. Skip the fix. Not the interesting part. What we want is who found out, how they found out, and how long the environment sat on the old version before anybody did anything about it.
People who have genuinely lived in this tell it with a calendar running underneath. A per-tenant extension had added a field to a base table, Microsoft later shipped a field with the same name, the schema wouldn’t merge, and nobody caught it until the third failed attempt because the notification recipient list still held a consultant who had left the partner back in March. What they changed about that list afterwards usually comes out unprompted, and that part is the tell.
Then a cold scenario, handed over without warning. You’re four weeks from the end of the grace period, one extension will not compile against the new version, and the developer who wrote it works for a partner that has stopped returning calls. What do you do this week?
The answer we’re listening for reaches the fork quickly. Either you strip the failing objects out and reinstall a reduced version, or you accept that the enforced period is going to take it and you plan how the business runs without that functionality for a fortnight. “Escalate to Microsoft” is not a wrong answer. It is the answer of somebody who has never sat through the last two weeks of a grace period, and you can hear that inside a minute. There are more in that shape in our Dynamics 365 consultant interview questions bank. The platform-agnostic version lives in ERP consultant interview questions.
Three Ways to Buy the Same Skill
Pick by what’s actually on the calendar this quarter, not by what the org chart says you’re allowed to have.
Contract & Contract-to-Hire
A defined stretch, roughly one release cycle, aimed at a single thing. An upgrade. An extension cleanup. Or the months after go-live when hypercare has ended and the questions have not. Conversions happen often enough, and the trigger is nearly always the same, which is the first wave the client gets through without phoning anybody.
Contract Staffing →Direct Hire
Business Central is where your revenue gets recognised, so a permanent seat is usually the honest answer. Then brace for the market. Nearly everybody good is currently billing somebody at a VAR, and they will decide quickly whether this job has been thought through or whether thinking it through is the job.
How direct hire works here →A Crew Against a Deadline
A team against a written statement of work, priced to a deliverable rather than to hours, which moves the date off your risk register and onto ours. Three shapes come up most. A NAV to Business Central online move. Two tenants after an acquisition that have to become one. Extension remediation with a grace period already circled. Frequently paired with ERP hypercare support.
Project Staffing →Common Questions
What does a Business Central consultant actually do all day?
A Business Central consultant configures the system to match how the business runs, then keeps it running through Microsoft’s twice-yearly releases. Configuration, reporting, integrations, user support and update readiness, roughly in that order of time spent.
The morning is usually somebody else’s problem. A posting group that routes to the wrong account, a report that stopped reconciling after a dimension was renamed, a warehouse user who can’t post a receipt. Project work fills the afternoons when there is any. This quarter that might be a Shopify or Power BI connection. Next quarter, a sandbox refresh to test the October release. Then close week arrives. It eats the calendar whole.
Do we need a functional consultant or an AL developer?
Functional, in most cases. If the ask is reporting, dimensions, posting setup, workflow or user adoption, a functional consultant covers it. Bring in an AL developer once you own per-tenant extensions that somebody has to keep compiling.
Posting one requisition for both is the mistake we see most. It reads as a senior hybrid role, pays like a mid-level one, and is still open at week twelve while everybody wonders why. So post two.
What does a Business Central consultant cost in 2026?
ZipRecruiter put the national average at $99,275 in July 2026, with most salaries between $61,500 and $141,500. Glassdoor reported $165,333 the same month, from three submissions. Contract rates for senior profiles clear both.
Modules move the number further than geography does. Geography matters less. Manufacturing and jobs costing carry a real premium because the pool that has run either in production is small, and it thins again if you also want somebody who writes AL. Bands by tier sit in our Dynamics 365 consultant pay benchmarks.
We already have a Microsoft partner. Why would we hire our own?
Because a partner is staffed to deliver projects and you’re running a system. An internal owner changes what actually gets sent to the partner, and how much of it, which is usually where the money is.
It also changes what happens when something breaks in August. The partner versus staffing agency comparison goes through the trade properly, including the cases where keeping everything with the VAR really is correct. Small tenant, no customizations, no integrations. Hire nobody and enjoy it.
How often does Business Central update, and can we skip one?
Two major releases a year, April and October, plus minor releases in most other months. Skipping a major release isn’t an option. You can schedule it anywhere inside a five-month window, and then a one-month grace period starts.
After the grace period comes the enforced update period, when anything blocking the update can be uninstalled automatically so it completes. It isn’t common. It is written down, though, and every Business Central customer carrying per-tenant extensions is somewhere on that clock right now whether anybody has looked or not.
We’re still on Dynamics NAV. Who do we need first?
An upgrade lead, before a developer. Every NAV customization needs a decision, standard functionality or a rebuilt AL extension or an AppSource app or retirement, and that decision list is what sets both the budget and the timeline.
C/AL code doesn’t carry across. It gets rewritten as an AL extension against event publishers that may not sit where the original custom function did, which is why the honest version of this project starts with an inventory and an argument rather than with a developer. The data side of the same programme is ERP data migration staffing, and how long an ERP implementation really takes covers the schedule.
How long does a Business Central search take?
Seventeen days is our ERP desk average from open req to a vetted candidate. A tightly written Business Central search tends to close inside another three to six weeks. Wanting manufacturing and AL in one person stretches that.
Budget isn’t the lever. The posting is. “Business Central experience required” is a phrase that qualifies nobody, so somebody on your side burns a fortnight separating the people who meant it from the people who once sat through a demo. Put your version, your live modules and two of your extension names in the advert instead. That moves the date further than another ten thousand on the base would. How ERP implementation teams are structured is a useful sanity check if you’re not sure how many seats you’re actually short.
Tell us your version, your extension count, and who’s on the notification list. We’ll size the seat.
A half-hour call is enough for us to come back with a rate band, a date that is not fiction, and a straight answer on whether you are short one person or two.
Start the Conversation →