Business Central Health Check: Complete Guide

By Lee Nash · 2026-08-02 · 10 min read

The Problem: When Business Central Quietly Drifts Out of Shape

Microsoft Dynamics 365 Business Central is rarely the thing that fails loudly. It fails quietly. A posting group points at the wrong general ledger account, a dimension isn't marked as mandatory, a permission set is far broader than anyone intended, and for months nobody notices. Then month-end arrives, the numbers don't reconcile, and a finance team spends three days unpicking transactions that were misconfigured from the start.

This is the core problem a Business Central health check addresses: the slow, invisible drift between how your system was originally implemented and how it actually behaves today. Very few Business Central environments stay exactly as they were signed off at go-live. People leave, partners change, new legal entities are added, workflows are bolted on, and small "temporary" fixes become permanent. Each individual change seems harmless. Collectively, they erode data quality, reporting accuracy and security.

Who tends to have this problem? In our experience it's almost everyone running Business Central for more than a year, but a few situations make it acute:

• Organisations that inherited their setup. You went live with a partner who is no longer involved, or a colleague configured everything and has since left. Nobody currently in the business fully understands why things are set the way they are.
• Fast-growing companies. Volumes have doubled, you've added warehouses, sales channels or a second company, and the configuration that suited a smaller operation is now creaking.
• Finance teams chasing reconciliation issues. The trial balance is fine, but sub-ledgers don't agree with the GL, inventory valuation looks wrong, or VAT returns need manual adjustment every quarter.
• Businesses preparing for something big. An audit, a system upgrade, a migration to a new reporting tool, or a private-equity due-diligence process. Suddenly the state of your data is under scrutiny.

The underlying reason this happens is structural. Business Central is enormously flexible, and that flexibility is a double-edged sword. There is no built-in alarm that tells you a customer posting group is misrouting revenue, or that Adjust Cost - Item Entries hasn't run in weeks, or that ten users share an admin-level permission set. The system does exactly what it's configured to do — even when that configuration is wrong. The cost surfaces later as misstated margins, painful audits, security exposure and hours of avoidable manual work.

The frustrating part is that most of these issues are cheap to find and cheap to fix if you look. They only become expensive when they're allowed to compound. That's the case for reviewing your configuration deliberately rather than waiting for a crisis to force the question.

The Solution: A Structured Configuration Review

The answer isn't a vague "tidy-up" or a gut-feel opinion from whoever is nearest the system. It's a structured Business Central health check: a systematic review of your configuration, master data, posting setup, security and performance against known good practice, resulting in a prioritised list of findings you can actually act on.

A good health check is diagnostic, not disruptive. It reads your setup; it doesn't change it. Nobody should be re-posting entries or flipping switches during the review itself. The output is a clear picture of where you stand and what to do about it, ranked by risk and effort — so you can fix the account-misrouting issue this week and schedule the nice-to-haves for later.

A thorough review covers several distinct areas:

• Financial configuration. General posting setup, VAT posting setup, customer and vendor posting groups, inventory posting setup, and the chain of default accounts that determine where transactions land. This is where the most costly errors hide.
• Master data quality. Duplicate customers and vendors, incomplete item cards, missing dimension defaults, inconsistent number series, and no-longer-used records that clutter reporting.
• Dimensions and reporting readiness. Whether dimensions are consistently applied, mandatory where they should be, and structured so that your management reports and Power BI dashboards actually reconcile to the GL.
• Security and permissions. Over-privileged users, unused accounts, segregation-of-duties gaps, and permission sets that grant more than the role requires.
• Batch jobs and housekeeping. Whether cost adjustment, inventory posting to the GL, and job queue entries are running reliably and on schedule.
• Performance and extensions. Environment sizing, telemetry signals, and any installed apps or per-tenant extensions that could be causing slow-downs or conflicts.

Business Central actually gives you a lot of the raw material for this yourself. The Setup Checklist, Assisted Setup, the Chart of Accounts and G/L Account Categories, and the various posting-setup pages all expose the current state. Microsoft also ships tooling — such as the Field Monitoring feature for sensitive fields, telemetry through Azure Application Insights, and standard reports like the Inventory Valuation and G/L Register — that a reviewer can lean on rather than reinventing.

What turns those raw tools into a genuine solution is method and judgement: knowing which combinations of settings cause real-world problems, knowing what "good" looks like for a business of your type, and being able to separate the urgent from the cosmetic. That's the difference between staring at hundreds of setup fields and walking away with a two-page action plan.

This is exactly the gap a free Business Central configuration review is designed to close. It gives you an independent, structured read of your environment without the commitment of a full project — a starting point, not a sales pitch.

How to Run a Business Central Health Check

You can carry out a meaningful review yourself with system access and a methodical approach. Below is a practical sequence using real Business Central features. Treat everything here as read-only investigation — do not change posting setup on a live system without testing and a clear rollback plan.

1. Confirm the environment and version. Open the Help & Support page (search via Alt+Q for "Help and Support") to record your application and platform version, and check the Admin Center for update rings and environment type (Production vs Sandbox). Always test changes in a Sandbox copy first.
2. Review the Chart of Accounts and categories. Open Chart of Accounts and check the Indentation, account types and totalling. Then open G/L Account Categories to confirm accounts map correctly to the financial statement lines that drive your reports. Misaligned categories are a common cause of dashboards that don't match the GL.
3. Audit the posting setup. This is the heart of the review. Check General Posting Setup (the matrix of business and product posting groups), VAT Posting Setup, Customer/Vendor Posting Groups and Inventory Posting Setup. Look for blank account fields, accounts pointing at the wrong place, and combinations that exist but shouldn't. A single wrong account here can misroute every transaction of a given type.
4. Check dimensions. Open Dimensions and review Default Dimensions at account, customer, vendor and item level. Confirm which dimensions are set to Code Mandatory or Same Code via the Dimension Combinations and value posting rules. Inconsistent dimension usage is the number-one reason management reporting won't reconcile.
5. Inspect number series. Review No. Series for gaps, manual overrides and series that are close to running out. Gaps and manual numbering undermine audit trails.
6. Verify batch jobs. Open the Job Queue Entries and confirm critical processes are scheduled and succeeding. Check that Adjust Cost - Item Entries and Post Inventory Cost to G/L are running — if they aren't, your inventory valuation and margins will be wrong.
7. Review users and permissions. Open Users, User Groups (or Security Groups in newer versions) and Permission Sets. Flag anyone with SUPER who doesn't need it, disabled staff who still have active logins, and roles granting broader access than the job requires.
8. Look at data quality. Use filters and the Data Administration and Table Information pages to spot bloated tables, and scan customer/vendor/item lists for duplicates and incomplete records. Consider Field Monitoring to watch sensitive fields going forward.
9. Check telemetry and performance. If Azure Application Insights is connected, review long-running operations and errors. Note any installed extensions via Extension Management that could be adding overhead or conflicting.
10. Document and prioritise. Capture every finding with a severity (critical / important / cosmetic) and an owner. A finding without an owner and a date rarely gets fixed.

How often should I run a Business Central health check?

For most organisations, a full review once a year is sensible, with a lighter check after any significant change — a new company, a major integration, an upgrade ring change, or the arrival of a new finance lead. High-transaction or fast-changing businesses benefit from a six-monthly cadence. The goal is to catch drift before it compounds, so align the frequency with how much your setup changes rather than the calendar alone.

Can I do a health check myself, or do I need a partner?

You can absolutely start yourself using the steps above, and a competent finance systems owner will surface plenty of value. The limitation is usually benchmarking and blind spots: it's hard to know what "good" looks like for your sector, and it's easy to overlook issues in areas you configured yourself. An independent reviewer brings pattern recognition from many environments and isn't invested in defending the original setup. A pragmatic middle ground is to run the self-check, then have an external review validate your findings and catch what you missed.

Will a health check disrupt our live system?

A properly run health check is read-only and causes no disruption — it inspects configuration and data without changing anything. Disruption only enters the picture at the remediation stage, when you act on the findings. Even then, best practice is to test every change in a Sandbox environment first, apply changes during a quiet window, and keep a documented rollback path. The review itself is safe to run against production.

Where to Go From Here

A Business Central health check isn't about finding fault with how your system was built. It's about acknowledging that any live ERP drifts over time, and that a periodic, structured look under the bonnet is far cheaper than the reconciliation marathons, failed audits and security surprises that come from leaving problems to compound.

If you've read this far, you probably already have a suspicion that something in your configuration isn't quite right — a report that won't tie out, a month-end that's harder than it should be, or simply the uneasy feeling that nobody in the business fully understands the current setup. That instinct is usually correct, and it's worth acting on while the fixes are still small.

The steps above will get you a long way on your own. If you'd rather have an independent, experienced pair of eyes confirm what you've found — or you'd simply like a clear, prioritised picture of where your environment stands — we offer a free Business Central configuration review. It's a no-obligation, read-only assessment that leaves you with an actionable summary, whether or not you choose to do anything further with us.

• Want to understand your system's current state without a big project? Start with a free review.
• Chasing a specific issue like reconciliation or slow performance? We can focus the review there.
• Preparing for an audit, upgrade or reporting migration? A health check is the ideal first step.

Get in touch to arrange your review, or to talk through any of the checks described above. There's no pressure — just a clearer view of your Business Central setup and a plan for keeping it healthy.

© 2026 Amplio Solutions Ltd · Written by Lee Nash · Built by Amplio SolutionsFollow us on LinkedIn