Business Central Managed Support
Business Central rarely fails loudly. It fails as a posting error at close, an approval sitting in someone's queue, a dimension that stops reconciling, or an extension that breaks after an update wave. Kendra provides a named support pod that resolves those issues, tracks what keeps coming back, and removes the causes rather than the symptoms.
Indicative planning range: $3,500–$8,000 / month for a Business Central environment. Final pricing is confirmed after discovery and scope alignment.
Support across the finance and operations surface of Business Central, including the extensions, integrations, and reporting layers most teams depend on daily.
The problems that actually reach a Business Central support queue.
These are the recurring patterns behind most Business Central tickets. Individually they are small. Collectively they are why finance teams lose days each month to work that should not require a human at all.
Posting and period-close errors
Documents that will not post, dimension combinations blocked by mismatched setup, posting groups pointing at the wrong accounts, and periods that will not close cleanly because something upstream was never reconciled.
Approval workflows that stall
Requests sitting with the wrong approver, workflow conditions that no longer match how the business is organized, notifications that stopped firing, and approval chains that break whenever someone changes role.
Extension and ISV conflicts
AL extensions and third-party add-ons that collide with each other or with a Microsoft update — usually surfacing as an event subscriber failing quietly rather than an obvious error.
Permission and access problems
Users who cannot see what they need, users who can see more than they should, and permission sets that have drifted over years of ad-hoc changes rather than reflecting current roles.
Integration and Power Platform failures
Power Automate flows failing silently, API and connector errors, and data arriving from another system in a shape Business Central will not accept.
Reporting that no longer reconciles
Account schedules and Power BI reports that disagree with the ledger, usually because a dimension, posting group, or filter changed and the report never did.
A named pod, a defined cadence, and a documented scope.
Business Central support is delivered inside the same subscription model as the wider managed support layer: consistent people, defined response targets, and a standing rhythm for reviewing what keeps recurring.
What the pod handles day to day
- Incident intake, triage, and resolution within agreed response targets.
- Configuration changes across finance, purchasing, sales, and inventory setup.
- AL extension fixes and minor development within the subscription scope.
- Permission set review, role design support, and access troubleshooting.
- Workflow and approval reconfiguration as the organization changes.
- Report, account schedule, and dimension corrections.
The operating cadence
- Monthly service review covering volumes, trends, and recurring causes.
- Quarterly business review covering the operating model, not just tickets.
- A visible, prioritized backlog rather than an invisible ticket pile.
- Reserved capacity redirected into backlog and improvement work when reactive demand is light.
- Runbooks written for anything that has now happened more than twice.
- US-led account management with an offshore-enabled delivery pod.
Microsoft ships continuously. Someone has to own what that breaks.
Business Central receives major release waves plus ongoing minor updates. For most mid-market teams nobody formally owns the question of what each update touches — so exposure is discovered by a user at the worst possible moment.
How release exposure is managed
What is inside the subscription — and what is quoted separately.
A support subscription only works when both sides know where it ends. Larger work is scoped and quoted rather than quietly absorbed or refused late.
Inside the subscription
- Break-fix, configuration, and incident resolution.
- Minor AL development and extension maintenance.
- Update wave assessment and regression testing.
- Permission, workflow, and reporting support.
- Backlog work drawn from reserved capacity.
Separate scope
- New Business Central implementations and company rollouts.
- Migration from GP, NAV, or another ERP onto Business Central.
- Large custom extension development programmes.
- New integrations to systems not currently connected.
- Finance transaction execution — see the Finance Operations BPO layer.
What Business Central buyers ask first.
Do we need to leave our current Business Central implementation partner?
How many users or companies does this suit?
Who handles Business Central update waves?
Can you support our ISV add-ons and custom AL extensions?
What if most of our problems turn out to be process rather than system?
Want Business Central support that actually reduces the queue?
Start with an assessment of your current ticket patterns, extension footprint, update exposure, and the finance workflows that cause the most avoidable friction.