A Business Central audit is an independent review of an installation that is already live, or of a project that has stalled before go-live. It answers three plain questions: what state is the system really in, what is it costing you to leave it as it is, and what is the most economical way to put it right. For many UK businesses the answer is not a fresh start. It is a structured project rescue that keeps what works and replaces what does not.
This page is for finance directors, managing directors and IT leads who suspect that their Business Central project has gone off course, and who are weighing up whether to change Business Central integrator. If you are still at the selection stage, read the guidance on choosing a Business Central partner first.
Signs that a Business Central audit is needed
Problems rarely arrive as one dramatic failure. They accumulate, and the people closest to the system often stop noticing them. These are the signals we hear most often from UK finance and operations teams:
- The go-live date keeps moving, and each new date comes with a new explanation.
- Month-end and VAT returns need manual rescue. The accountant exports figures to spreadsheets to reconcile what the ledger should already show.
- Users have built shadow processes. Orders are tracked on the side, stock is counted outside the system, and nobody trusts the reports.
- Every change is a dispute. What was in the original scope, and what is a chargeable extra, has become a standing argument.
- Your partner is slow to answer or has changed its team. The consultant who knew your business has left and nobody has taken over properly.
- Updates frighten everyone. The business avoids the regular Microsoft updates because something custom broke last time.
- Nobody can explain how it was configured. There is no document that says why a setting is the way it is.
One or two of these is normal in a busy business. Several at once, over several months, is a reason to look underneath. The common ERP project mistakes are a useful checklist to compare against.
What an audit examines
A sound audit is not a generic health check. It follows the way your business actually uses the system. The main areas are below.
| Area | What the reviewer looks at | Typical finding |
|---|---|---|
| Set-up and configuration | Company set-up, posting groups, number series, dimensions, approval flows | Settings copied from another company that do not suit your structure |
| Data | Customers, suppliers, items, opening balances, duplicates, historic migration | Duplicate records and balances that do not agree with the old system |
| Custom development | Extensions, code quality, dependencies, whether changes sit in extensions or in the base | Heavy modification that blocks updates |
| Performance | Slow pages, long-running reports, job queues, integrations that lock tables | Reports built on unindexed data, or integrations that run at peak hours |
| Security and access | Roles, permission sets, segregation of duties, leavers still active | Users with access they should not have, and shared logins |
| Version and updates | Which version you run, how far behind you are, update windows | An environment that has fallen behind the supported release path |
| Integrations | Links to banking, e-commerce, payroll, CRM, EDI | Brittle connections with no monitoring or error handling |
| Licences and users | Licence types against actual use | Full licences held by people who only need limited access |
Configuration and data
Configuration faults are the cheapest to fix and the most expensive to ignore. A badly designed chart of accounts, wrong posting groups or poorly chosen dimensions will distort every report for years. The reviewer compares the set-up with how you really trade: your VAT treatment, your cost centres, your customer terms and your stock locations.
Data quality comes next. A migration that looked finished at go-live often hides duplicated accounts, unreconciled opening balances and items with inconsistent units. Auditors trace a sample of transactions from source document to ledger to report. If the figures do not agree, the cause is usually in migration or in set-up, not in the product. For more on how a data move should be handled, see the page on migrating to Business Central.
Custom development
Custom code is where rescue projects most often become expensive. The reviewer asks whether the development is packaged as extensions, whether it follows Microsoft's recommended approach, who holds the source, and whether it has been tested against a newer release. Our guide to customising Business Central explains what good practice looks like. A development that cannot survive an update is a liability, and the audit should say so plainly and indicate what it would cost, in effort, to remedy.
Version, updates and cloud environments
Business Central online receives two major updates a year, in April and in October, and minor updates in between. These contain critical fixes and regulatory changes. The update period for a major version runs for five months from its general availability, with a month of grace afterwards, and each environment has a configurable update window. An installation that has been held back, or whose extensions fail when the update arrives, is a classic symptom of the problems above. The reviewer checks your environments, the update settings and whether a sandbox is used to test ahead of each release. Our page on versions and editions sets out the options.
Security and permissions
In a rescue it is common to find permission sets granted far too widely because it was quicker during the project. Reviewers check roles against the real jobs people do, look for leavers who still have access, and test segregation between those who raise and those who approve payments. For a business under the scrutiny of an accountant or auditor, this part of the report often matters as much as the technical findings.
UK tax and compliance fit
An audit must also test the system against your UK obligations. Check that VAT set-up, Making Tax Digital submissions and your payroll arrangements work as intended; our guide to Making Tax Digital and your ERP lists the points to confirm. Microsoft notes that VAT functions not covered as standard, for example for Northern Ireland, VAT groups by consolidation or construction-type sectors, must be met through partner solutions or sector-specific software. If your business trades in any of those situations, the reviewer should confirm exactly how the gap is covered. More context is on the page about Business Central in the UK.
Changing integrator without starting again
Moving to a new partner is less drastic than it sounds, provided you separate three things: what you own, what is documented, and what is custom.
What you own. Your data, your tenant and your licences belong to your business. Microsoft states that online licences are bought through a partner under its Cloud Solution Provider programme, so a change of partner also means arranging the transfer of your licences and your delegated administration. Settle this early, because it affects who can act on your environments from the first day.
What is documented. If the original partner left clear configuration notes, process maps and test records, the new team can take over quickly. If it did not, the audit becomes the documentation, and its cost is worth paying.
What is custom. Extensions are the real unknown. Where they are well built and you hold the source, they can usually be kept. Where they are not, you decide extension by extension whether to repair, replace with standard functions or drop.
Documents and access to recover before you leave
Request the following, in writing, before the relationship ends:
- Global or delegated administrator access to every environment, production and sandbox.
- Source code and packaged extensions for all custom development, with a statement of who owns them.
- Configuration documents, the data-migration mapping and any reconciliation evidence.
- Integration details: endpoints, service accounts and the names of connected systems.
- The list of open issues, change requests and agreed but undelivered work.
- Training material and user guides produced during the project.
- The contract, statement of work and any signed change notes.
Do not rely on goodwill alone. Read your contract for the clauses on code ownership, notice and handover, and take legal advice where they are unclear. A good new partner will help you plan the handover but cannot force a former supplier to release what it is not obliged to.
What Microsoft will and will not do
It helps to be realistic about escalation. Every Business Central customer has a partner acting as first-line technical support, which raises cases with Microsoft where needed as delegated administrator of the customer's tenant. Microsoft's own support deals with incidents, not usage questions, and does not help repair corrupted data. A project in trouble is therefore resolved by choosing the right partner, not by escalating to the vendor. The page on support and maintenance explains how that relationship should work.
A recovery plan that works
A rescue goes best when it is staged and when each stage has an exit. A typical plan looks like this:
- Stabilise. Freeze non-essential changes, secure administrator access, take a verified backup, and fix the faults that stop people trading or filing returns. Online environments can be restored to a point within the recent past, which gives a safety net before any corrective work.
- Diagnose. Run the audit across the areas above and produce a ranked list of findings, each with its business impact and the effort to fix it.
- Decide. For each major finding, choose between repair, rebuild and leave alone. Involve the finance team and the people who use the system daily, not only IT.
- Correct. Fix configuration and data first, then custom code, then integrations. Test in a sandbox before anything reaches production.
- Retrain. Poor adoption is often as damaging as poor configuration. Refresh training for your users once the system behaves as the process says it should.
- Hand over to support. Agree who does what, how issues are logged and how updates are tested in future.
Where the findings reveal that the original scope was wrong, a short restart of the implementation for one area, such as stock or manufacturing, is often cheaper than patching it.
Budget and expectations
Cost depends on the extent of the problems, so be wary of anyone who quotes a rescue price before examining the system. Licence costs are a separate matter: Microsoft's published prices differ by country and currency, and your final price is confirmed at purchase. Our page on Business Central pricing covers the cost structure. In the audit itself, ask for a fixed scope, a named reviewer and a written report that you can show to your board or lender.
Choosing who carries out the audit
Independence matters. A partner auditing its own work has an obvious conflict, and a competitor auditing a rival has another. Look for a reviewer who has no stake in selling you a fix, or at least who sets out transparently where the recommendations lead to paid work.
Ask for evidence of Business Central experience rather than general ERP claims. Microsoft's partner designation scheme includes certifications such as the functional consultant and developer credentials for Business Central, which can be a reasonable indicator of skills, though they do not replace references from comparable UK businesses. Ask whether the people doing your audit hold them, and whether they have rescued projects like yours.
If you would like help finding such a reviewer or a replacement partner, our free matching service puts you in touch with certified integrators that fit your size, sector and region. We do not carry out audits or implementations ourselves, and we are not affiliated with Microsoft; the integrator does the work and agrees its terms with you directly.
Frequently asked questions
When should we commission a Business Central audit?
Commission one when go-live keeps slipping, when users work around the system in spreadsheets, when month-end close takes longer than it did before, or when every change request becomes a dispute. An audit is also sensible before you sign a support contract with a new partner or before a major version update, because it tells you what you are really inheriting.
Can we change Business Central integrator without starting the project again?
Usually yes. Your data, your tenant and your licences belong to your business, and most of the configuration can be documented and reused. What decides the outcome is the state of the custom code, the quality of the documentation and whether you hold administrator access. An audit separates what can be kept from what must be rebuilt.
What do we need from our current partner before we leave?
Ask for administrator access to your own environments, the source code and extension packages of any custom development, the configuration and data-migration documentation, the integration settings and credentials for connected systems, and the list of open issues. Your contract should say who owns the code, so read it before you give notice.
Does Microsoft rescue a failing Business Central project?
No. Microsoft's technical support covers incidents, not project recovery or training, and it does not help to repair corrupted data. Your partner is the first line of support and escalates to Microsoft where needed, so a project in difficulty is rescued by a competent partner, with an independent audit as the starting point.
Will an audit cost us more than it saves?
An audit is far smaller than the cost of continuing a project on a faulty foundation, because it stops you paying for further development on top of errors. Its price depends on the size of the installation and the depth of review, so ask for a fixed scope in writing and agree what the report will contain before work begins.
Sources
- Microsoft Learn — Business Central technical support
- Microsoft Learn — Business Central update rollout timeline
- Microsoft Learn — Business Central environment backup and restore
- Microsoft Learn — Business Central licensing
- Microsoft Learn — Business Central VAT after the UK left the EU
Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.