Default Dimensions in Business Central: What to Configure Before Go-Live

Default dimensions are a control system to ensure financial transactions can be accurately reported in management reports and financial analysis. Rules and setups that control default dimensions in Business Central enforce the reporting and analysis strategy and are more than just master data setup.

Default Dimensions

Dimensions, Default Dimensions, and the Dimension Set ID in Business Central

When a transaction posts in Business Central, BC creates a unique identifier called the Dimension Set ID. This ID represents the exact combination of all dimension values on that entry.

A purchase invoice tagged with Department = Finance and Project = ERP Rollout gets a different Dimension Set ID from one tagged with Department = Finance alone. That ID is what the reporting engine reads, and it is uneditable. That means you cannot add a dimension value to a posted entry by editing a field, only by running a correction routine.

Having worked on more than 60 BC implementations since 2015, I have seen two common problems in this area.

The first is treating dimensions as extra fields to filter on, almost like adding columns to a spreadsheet. That only applies to the two global dimensions. The other dimensions — shortcut or standard — are not additional fields on records or columns in a table. They form a combination of codes and values. For example, a purchase invoice can carry a Project, a Department, and a Cost Centre dimension simultaneously. The combination of all three forms a single Dimension Set ID. Filtering by one of them in a report works because BC resolves the ID, not because the value sits in a standalone field.

The second is assuming that dimension values on orders and journals must come from default dimensions on customers, vendors, or G/L accounts. Default dimensions on a customer are copied to sales documents, but BC supports default dimensions with no value. That is how you make a dimension mandatory without pre-selecting a value, which lets users choose the correct value at the time they prepare the document.

Default dimensions can also be configured with a range of allowed values, so the choice is constrained without being fixed.

Setting Up Default Dimensions in Business Central Before Go-Live

The Default Dimensions page controls four behaviours for each dimension on a given master record, set via the Value Posting field.

Blank means no restriction: the dimension can be used or ignored. With code Mandatory, users must select a value before posting, but any valid dimension value is allowed. Same Code applies to documents that can generate multiple transactions. For example, a sales order that users can ship and invoice in stages or a project. With this setup, users cannot change the value of the specified dimension for the same order because all the transactions must have the same code. No Code means the dimension will have a blank code.

A common misunderstanding about default dimensions is that users do not need to set up default dimensions with mandatory values. Business Central supports default dimensions with a blank value for teams that need to enforce that a dimension is used without a pre-existing value. This setup helps clients who need certain dimensions to be mandatory, but need users to select the correct value before recording the transaction. In this case, BC will stop the user from posting without selecting a value, but leaves the selection open.

Control accounts and default dimensions

Same Code must not be set on any G/L account that receives postings from multiple sources or automated processes. A control account for trade creditors receives postings from purchase invoices across every vendor, every department, and every project. No single dimension value is correct for all of them. The same principle applies to inventory control accounts, cash, and other balance sheet accounts.

Before go-live, users and consultants set up the master data entities that need default dimension configuration, such as customers, vendors, items, and salespeople. G/L accounts need default dimensions only where they are used directly on invoices and journals. G/L accounts that receive postings via posting groups, such as item sales accounts populated through the General Posting Setup, do not need default dimensions on the account itself; the team will set up the correct default dimension on the item instead.

Dimensions on a G/L Account Card

Default Dimension Priorities in Business Central: How Conflicts Are Resolved

When a transaction involves more than one master record, and those records carry default dimensions for the same dimension code, BC needs to decide which value to use. A sales order where both the customer and the salesperson have a default Department dimension will produce a conflict: two sources, one dimension code, one entry.

Default Dimension Priorities resolves this conflict. You set a priority order per combination of transaction type and source. For instance, sales transactions, customer and item source of the dimension. BC applies the value from the highest-priority source.

Defaults Dimensions Priority

Correcting Dimension Errors in Business Central After Posting

BC has a Dimension Correction tool that allows dimension values on posted G/L entries to be corrected after posting. You identify the entries, specify the correction, run a validation, and apply it. The validation step checks dimension restrictions, blocked values, and Value Posting rules against the proposed change before anything is written.

Corrections apply only to G/L entries. The entries in the customer ledger, vendor ledger, and item ledger for the same transaction are not updated. The correction keeps your financial reports accurate, but it does not rewrite the originating transaction across all ledgers. That means reports that use subledgers, such as item ledger entries, value entries, or project ledger entries, will show different dimension values than the general ledger entries they refer to.

Correct Dimensions

How long a correction run takes depends entirely on transaction volume and database size. It can take two minutes. It can take four hours. The case for getting the default dimension setup right before go-live is not that corrections are impossible — it is that corrections on a full month of posted entries are a different exercise from corrections on a handful of test entries. The Dimension Correction tool is not a substitute for a correctly configured go-live.

If you are in the configuration phase and want a second opinion on your dimension design before go-live, get in touch.