Business Central best practices that keep a system healthy

Business Central best practices for financial structure

Keep the chart of accounts to natural accounts only. These show what was earned, spent, owned or owed. Put the who and where into dimensions, such as Department, Region or Project. Two global dimensions and up to six shortcut dimensions are set on the General Ledger Setup page. They appear as columns on journals and documents.

Then make dimensions reliable. Use Default Dimensions on customers, vendors, items and G/L accounts. Set Value Posting to Code Mandatory where analysis must be complete. Add dimension combinations to block pairings that make no sense. Reports built on clean dimensions need far fewer manual corrections at month end.

Master data and posting groups in Business Central best practices

Most posting errors trace back to a record created in a hurry. Use customer, vendor and item templates, so new records arrive with the right posting groups, payment terms and dimensions. Limit who can create or change master data. Also consider an approval workflow for new vendors and bank account changes.

Treat posting groups as finance-owned setup. The General Posting Setup and Inventory Posting Setup pages decide which accounts every transaction reaches. So changes there should be rare and documented. Keep number series tidy and avoid manual numbering on documents. Block records that are no longer used, instead of deleting them.

Permissions and user setup

Avoid giving everyone the SUPER permission set. Build security groups by role, assign permission sets to the groups and add users to the groups. The Effective Permissions page shows what a person can really do. The recording feature in permission sets also helps. It captures the steps of a task and builds a precise set from them.

Use the User Setup page to restrict posting dates for each user. That way, only finance can post into a prior period. Switch on the Change Log for sensitive setup tables and bank details. Keep its scope narrow, so it stays readable. Then go through user access whenever someone changes role or leaves.

Month-end and daily routines

A steady close depends on small daily tasks. Reconcile bank accounts often with the Bank Account Reconciliation page. Keep the job queue running for cost adjustment and posting routines. Clear unposted documents that will never be used. The Adjust Cost - Item Entries batch job should run regularly, so inventory value agrees with the ledger.

At month end, follow a written order. First, post recurring journals and run fixed asset depreciation. Next, reconcile receivables and payables subledgers to their control accounts, and check inventory valuation. Last, set Allow Posting From on General Ledger Setup to the new period. A checklist that names the person for each step prevents gaps.

Business Central best practices for updates and extensions

Business Central online gets two release waves a year, plus smaller updates along the way. Set an update window in the admin center that avoids your busy hours. Keep a sandbox that is a recent copy of production. Before each major update, run your key processes there with your extensions installed.

Be strict about customization. Look for a standard feature first. Then try an AppSource app. Write a custom AL extension only when neither fits. Keep source code in version control, and document what each extension does and why. Remove extensions nobody uses. If a second opinion would help, our consultants can assess your setup.

Business Central best practices: frequent questions

How many dimensions should a company use?

As few as answer the questions management really asks. Many companies do well with three or four, such as department, location and project. Every extra dimension adds data entry and room for mistakes. So add one only when a recurring report needs it. Business Central best practices favor a small, steady set over a long list.

Should we delete old customers, vendors and items?

Usually not. Records with history cannot be deleted without extra steps, and removing them can make old documents harder to read. Set the Blocked field instead. That stops new transactions while keeping the record and its ledger entries available for lookups and reports. So Business Central best practices keep your history intact, and nobody posts to an old record.

How often should the cost adjustment run?

For most companies, a nightly job queue entry is sensible. Switch on automatic cost posting if finance wants inventory value in the ledger all the time. Running it only at month end can make the job slow. It also hides costing problems until the close. So a steady rhythm beats a big monthly run.

What is the most common setup mistake you see?

A chart of accounts that tries to carry departments and locations in the account number. It produces a very long account list, awkward reports and frequent miscoding. Moving that detail into dimensions is nearly always worth the effort, even in a live system. We can plan that move with your finance team, one step at a time.

Do we need a sandbox if we have no custom code?

Yes. A sandbox is where you try new features, train new staff and rehearse data imports. You can also test AppSource apps there before they touch live data. It is included with the online service. Copying production into it takes only a few clicks in the admin center. So the cost of having one is small.

Guides that go deeper on Business Central best practices

Each habit in these Business Central best practices has its own detailed guide. Start with the one closest to your current problem. Our pages cover dimensions, permissions, the month-end close and sandbox environments. Or ask our consultants to go through your system with you. We can rank what to fix first, and then help your team make each change safely. For the product detail, see Business Central documentation on Microsoft Learn.