Your dimensions aren’t the problem. Your design is.

By Michelle Serna · Microsoft MVP, Business Central

If your monthly close involves Excel exports, hand-reconciliation between two reports, or a conversation that starts with “why doesn’t this number tie,” I want to suggest something uncomfortable.

It’s not the system.

In ten years of Business Central implementations, the single most expensive feature I’ve watched companies misuse is dimensions. Not because dimensions are hard. Because dimensions look simple. You can create them in thirty seconds. Tag a transaction in two clicks. And by the time anyone notices the damage, you have three years of posted entries tagged inconsistently, six dimensions that nobody owns, and a CFO who doesn’t trust the dashboard.

The good news is that this is fixable. Better news: most of the fix is design, not technology. Here is the approach we run on every cleanup engagement, distilled.

Start with the question, not the dimension

The single biggest mindset shift is this. Don’t ask “what dimensions should we create.” Ask “what do we need to report on.”

The wrong instinct sounds reasonable: let’s add a dimension for everything so we have flexibility later. Twelve months later, you have twelve dimensions, three are actually used, and your reports are a mess.

The right instinct sounds boring: our CFO needs revenue by department, expenses by cost center, and margin by project. That is three reporting questions. So you build three dimensions. They get fully adopted because everyone knows why they exist. And the reports actually tie.

Every dimension should answer a specific reporting question. If it doesn’t, don’t create it. That is the rule.

The four questions that kill bad dimensions before they exist

Before you create a new dimension, run it through these four questions. If you can’t answer all four with confidence, don’t create it.

What specific report does this dimension enable? If nobody on the leadership team can name a real report this dimension powers, you don’t need it. “It would be nice to have for flexibility” is the red flag.

Who will tag this consistently? If the answer is “everyone,” that usually means nobody. You need a real owner accountable for data quality on that dimension.

Can this data live somewhere else? If the dimension maps one-to-one to a master data field like customer, item, or project, just use that field. Don’t duplicate it.

Is it worth the overhead? Every dimension adds work for your users. The reporting value has to exceed the tagging cost. If you are asking your AP clerk to tag four dimensions on every invoice but you only filter on two, you are paying for data you don’t use.

Run every dimension through these four questions before you create it. Run them again every year for the ones you already have.

Download the Dimension Design Checklist

Defaults are your governance, not a suggestion

Once you have the right dimensions, the second-biggest source of mess is governance. Business Central gives you four rules for how a default behaves on a master record. Picking the right one is the difference between clean data and constant cleanup.

Code Mandatory blocks posting if the dimension is missing. Use this for your most critical dimensions. Department on expense accounts is a great example. If somebody tries to post an expense without a department, the system stops them at the door.

Same Code locks the dimension to a specific default that cannot be overridden. Great for fixed assignments. If your IT department always codes to cost center IT, set Same Code and the value is permanent.

No Code requires the dimension to be blank. Use this where the dimension genuinely doesn’t apply. Intercompany clearing accounts are a classic case.

Code Optional suggests a default but lets users change it. Use sparingly. Optional becomes blank, fast.

A note on Code Mandatory from the CFO side: be intentional. If you turn this on for every dimension without testing in a sandbox first, you will block posts your team did not expect. Phase it in.

Download the Default Dimension Quick Reference

When something goes wrong (and it will), use the right tool

Even with perfect governance, somebody is going to post something wrong. The Dimension Correction tool has been in Business Central since the 2021 wave 1 release, and it is one of the most underused features in the product.

It lets you fix dimensions on posted ledger entries without reversing and reposting. Three-step workflow: Draft, Validate, Run. Every change is logged. Fully auditable. Reversible.

Before this tool existed, finding a wrong dimension after the fact meant reversing the entry, reposting it correctly, and explaining to your auditors what just happened. That era is over.

One caveat. Correction is a safety net. It is not a strategy. If you are running corrections every month for the same kinds of mistakes, the answer is not better corrections. The answer is going back and fixing the process, the defaults, or the training that caused the error in the first place.

The cleanup playbook

If you have inherited a messy setup, here is the order of operations. Following it matters. Do these out of sequence and you will end up cleaning the same data twice.

Step 1: Audit what exists. List every dimension and every value. Identify what is being used, what is unused, and what is being used inconsistently. The audit alone usually surfaces a third of your dimension values as unused.

Step 2: Map to reports. For each dimension still on the list, name the specific report or dashboard that consumes it. If you can’t name a report, flag it for retirement.

Step 3: Set defaults and rules. Apply Code Mandatory, Same Code, and combination blocking. This is where you stop the bleeding. Going forward, no more bad data gets in.

Step 4: Correct historical data. Now use the Dimension Correction tool to fix what is already posted. Not before. If you try to clean historical data before you fix the process that caused it, you will be cleaning the same data again next quarter.

Download the Dimension Cleanup Template

The payoff

When dimensions are designed for the questions you actually need to answer, governed with defaults that match how your business operates, and cleaned up on a regular cadence, three things change.

Your financial reports tie without manual reconciliation. Your Power BI dashboards reflect reality, not last month’s reality. And your finance team stops being the detectives who chase down bad data and starts being the analysts who answer real questions.

Clean dimensions aren’t about perfection. They’re about making every report trustworthy and every decision data-driven.

Have a dimension setup you suspect is broken? Tell us where it hurts. We’ve seen it before.