How Do You Align Business Central Account Categories With Historical Reports?
Short answer
BD Create or delete account subcategories, and add a subcategory to the G/L account and update the equivalent account schedule.
Question
Key Takeaways
The question tests whether you know Business Central ships fixed top-level G/L account categories (Assets, Liabilities, Equity, Income, Cost of Goods Sold, Expenses) that cannot be created or renamed, while subcategories plus their account schedule rows are fully customisable — the trap is selecting A or C.
In Dynamics 365 Business Central the top-level G/L account categories are fixed, so matching a legacy financial system means managing subcategories and updating the account schedules that drive the reports. This page confirms the correct options are B and D, not the tempting 'create or rename top-level categories' distractors.
Common mistake: The most common wrong pick is A (rename top-level account categories), which drew 33 votes as the AD combination: renaming sounds harmless and useful, but the top-level category nodes are fixed system nodes, so only subcategories can be created, deleted, renamed or moved.
Expert Analysis
Why the Answer Is Correct
Options B and D are the only two actions the G/L Account Categories page actually permits for this scenario. You can create or delete account subcategories to mirror the structure of the manufacturer's historical statements, and you can assign a G/L account to the new subcategory and then update the equivalent account schedule (row definition) so the report totals the new line. Together they reproduce the legacy report layout: B shapes the category tree, D wires the affected G/L accounts and the reporting rows into that tree. Neither action conflicts with the fixed top-level nodes, which is why they present part of the solution each. A manufacturer migrating to Business Central gets historical continuity only when both the category structure and the report definitions are aligned.
Why the Other Options Are Wrong
Option A assumes the top-level nodes are editable, but Business Central's top-level account categories are standard, fixed nodes that cannot be renamed to match a legacy chart. Option C makes the same mistake in the other direction: new top-level categories cannot be created, so any plan that begins with 'create top-level account categories' cannot be implemented. Both A and C therefore describe something the product does not allow, regardless of how desirable the outcome would be for the manufacturer. Note also that the question asks for ways to create account categories and subcategories — options A and C do not produce the subcategory granularity that historical reports require.
Community Comment Notes
As 3e11d6a points out, "The top-level account categories, such as the Liabilities node, are fixed and you can't add your own", and they add that categories at lower levels can be deleted and added, which is exactly options B and D. ivanrlg argued for A and D on the grounds that renaming top-level categories keeps familiar names for stakeholders, but that argument fails because those fixed nodes cannot be renamed. Sridhar.hm and 710e0aa both recorded BD and simply marked it "Correct", and the vote count (67 for BD versus 33 for AD) reflects that consensus. The only genuinely contested point in the thread is whether the top-level nodes are mutable — the documentation quoted for the fixed-node behaviour settles it.
Official Reference
https://learn.microsoft.com/en-us/dynamics365/business-central/bi-row-definitions
This link opens the official vendor documentation in a new tab.
Exam Strategy
Memorise the split: top-level account categories are fixed and cannot be created, renamed or deleted, while subcategories and their report rows are fully editable. Any answer option that talks about creating or renaming a top-level category is a distractor in MB-800.
Frequently Asked Questions
Can you create top-level G/L account categories in Business Central?
Why must the equivalent account schedule be updated when a subcategory is added?
Community Votes
67% of anonymous learners picked answer BD. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
ivanrlg 👍 1To align Dynamics 365 Business Central with historical financial reports, two effective strategies are: A. Rename top-level account categories to match historical conventions, ensuring consistency and familiarity for stakeholders. D. Add a subcategory to the general ledger account and update the account schedule, creating granularity that mirrors historical report structures for accurate reflection in new reports.
-
3e11d6a 👍 1'The top-level account categories, such as the Liabilities node, are fixed and you can't add your own. However, you can delete and add account categories at lower levels and define how the related financial report appears in reports.'. So both A & C are wrong. Ref: https://learn.microsoft.com/en-ca/dynamics365/business-central/bi-row-definitions#use-gl-account-categories-to-change-the-layout-of-your-financial-statements
-
Sridhar.hm 👍 1Correct
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.