Business Central Health Check: Complete Guide
Microsoft Dynamics 365 Business Central rarely fails loudly. It drifts. A posting group points at the wrong account, a dimension is not set as mandatory, or a permission set grants more than anyone intended, and nobody notices until month-end will not reconcile. A Business Central health check is how you find that drift before it costs you.
This guide explains what a health check covers and gives you a step-by-step review you can run yourself, read-only, using standard Business Central pages.
Why Business Central drifts
Very few environments stay as they were signed off at go-live. People leave, partners change, new companies are added, and small temporary fixes become permanent. Each change looks harmless; together they erode data quality, reporting and security.
The risk is highest when you inherited the setup from someone who has left, when the business has grown quickly, when sub-ledgers stop agreeing with the general ledger, or when an audit or upgrade is coming. If the problems go deeper than setup, our guide to the signs you have outgrown your ERP helps you tell the difference.
Key PointBusiness Central does exactly what it is configured to do, even when the configuration is wrong. A review is the only reliable way to find those settings.
What a health check covers
- Financial configuration. General posting setup, VAT posting setup, customer, vendor and inventory posting groups, and the default accounts that decide where transactions land. VAT setup matters more than ever, because all VAT-registered businesses should now be signed up for Making Tax Digital for VAT.
- Master data. Duplicate customers and vendors, incomplete item cards, missing default dimensions and number series that are close to running out.
- Dimensions and reporting. Whether dimensions are applied consistently, so management reports reconcile to the general ledger.
- Security and permissions. Over-privileged users, unused accounts and gaps in segregation of duties.
- Batch jobs. Whether scheduled processes such as cost adjustment are running and succeeding.
How to run a health check yourself
Treat everything below as read-only investigation. Test any change in a sandbox environment first, never straight in production.
- Review the chart of accounts. Check account types and totalling, then confirm that G/L account categories map to the right statement lines.
- Audit the posting setup. Look through General Posting Setup, VAT Posting Setup and the posting groups for blank accounts and combinations that should not exist.
- Check dimensions. Review default dimensions on accounts, customers, vendors and items, and which are set to Code Mandatory.
- Inspect number series. Look for gaps, manual overrides and series about to run out.
- Verify batch jobs. Open Job Queue Entries and confirm critical jobs are scheduled and succeeding. Microsoft's guide to scheduling job queue entries explains the statuses.
Pro TipGive every finding a severity and a named owner. A finding without an owner and a date rarely gets fixed.
Users, permissions and performance
Review users and permission sets, and flag anyone with broad administrator rights who does not need them, and leavers whose logins are still active. Microsoft's guide to assigning permissions explains how permission sets combine.
For performance, Business Central can send telemetry to Azure Application Insights. If that is set up, review long-running operations and errors, and note any installed extensions that might add overhead.
Watch OutA health check should change nothing. Fixes come afterwards, tested in a sandbox first, with a way to roll back.
How often to check, and where to get help
Most businesses benefit from a full review once a year, with a lighter check after any big change such as a new company, a major integration or a new finance lead. Align the timing with how much your setup changes, not just the calendar.
If you want an independent view first, our free ERP Health Check asks where your system is letting you down and sends back a short report on where to focus first, with no obligation. Our guides to what an ERP health check involves and why month-end should not take a week cover the next steps. For independent guidance on finance systems, see the ICAEW technology resources.
