MB-800 Decoded: 24 Business Central Scenarios and the Reasoning Behind Each Answer

Most exam prep is a race to memorise letters. That works right up until a client asks why, and you discover you learned a lookup table instead of a system.

So this is not an answer key. It is a walk through 24 scenarios from the Microsoft Certified: Dynamics 365 Business Central Functional Consultant Associate practice material, where the answer is the least interesting part. What matters is the mechanic underneath — which setup table BC reads, which page owns the setting, and why the three wrong options are wrong in three different ways.

I have regrouped the questions by functional area rather than keeping their original order, so this reads as a study path instead of a shuffle. Where the exam answer and real-world practice diverge, there is an In the field note.

A note on sources. These are practice-assessment style items — the format Microsoft publishes freely on Microsoft Learn. If you are studying from questions someone claims to have recalled from a live exam, close that tab. Sharing live exam content breaches the NDA you agreed to, and Microsoft revokes certifications over it.

---

1. Chart of Accounts and Account Categories

Four questions, one underlying theme: in Business Central, the Chart of Accounts is not a list of accounts. It is a configuration surface that drives reporting, protection, and structure. Almost every wrong answer in this section is someone treating it as a list.

1.1 Protecting accounts that have nothing posted to them

A company has issues with users deleting general ledger accounts that were created for future posting group usage but have nothing posted to them. You need to prevent deletion of these accounts. Which two actions should you perform?

Answer: Enable the Check G/L Account Usage field, and assign the general ledger account to a posting group setup table.

Why it works. Business Central has two independent guards against deleting a G/L account, and this scenario deliberately disables the first one.

The default guard is entry-based: BC refuses to delete an account that has G/L entries within the protected window defined by Allow G/L Acc. Deletion Before on the General Ledger Setup page. Empty accounts sail straight past it.

The second guard is the Check G/L Account Usage toggle, also on General Ledger Setup. Switch it on and, before deleting, BC scans the posting setup tables — General Posting Setup, VAT Posting Setup, Customer/Vendor Posting Groups, Bank Account Posting Groups, FA Posting Groups, Inventory Posting Setup — and blocks the deletion if the account is referenced anywhere.

That is why this needs both halves. The toggle is the guard; the posting group assignment is the thing being guarded. Turn on the check with the accounts referenced nowhere, and you have protected nothing.

Why the others fail.

• Post an entry for a negligible amount — this genuinely would block deletion, which is exactly what makes it a tempting trap. But you are corrupting the ledger to enforce a configuration rule. Every reconciliation, every audit trail, every trial balance now carries a phantom 0.01 that someone will eventually ask about. Never solve a setup problem by posting data.
• Run the Where-Used List analysis — read-only diagnostics. It tells you where an account is referenced; it has no authority to stop anything.

In the field: these two toggles solve different problems, and clients regularly ask for the wrong one. Allow G/L Acc. Deletion Before protects accounts with history. Check G/L Account Usage protects accounts with a role. A well-configured company uses both.

1.2 Creating a new cost account

You need to create a new cost account in the Chart of Accounts. Which three actions should you perform?

Answer: Set Account Category to Expense, set Income/Balance to Income Statement, and run Indent Chart of Accounts.

Why it works. A cost account is by definition a profit-and-loss account, so Income/Balance = Income Statement — this is what tells BC to zero the account at year-end close and roll its balance into retained earnings, rather than carrying it forward.

Account Category = Expense is the reporting classification. It is what places the account in the right block of the system-generated financial reports (more on this in the next question).

Indent Chart of Accounts is the one people skip, and it is the one that quietly breaks reports. The Chart of Accounts is a hierarchy built from Begin-Total and End-Total rows, and the Indent Chart of Accounts action recalculates each account’s indentation level and — critically — the Totaling ranges on the End-Total rows. Add an account without re-indenting and it exists, posts correctly, and is silently excluded from its own subtotal.

Why the others fail.

• Set Income/Balance to Balance — that makes it a balance sheet account. It would never close at year-end and would accumulate cost forever.
• Leave the Account Category blank — the account drops out of every category-driven financial report. It still posts; it just becomes invisible in exactly the places management looks.

In the field: in current BC versions, setting Account Category often auto-populates Income/Balance for you. Don’t let that convenience hide the relationship — the exam tests it, and so does the first client whose imported chart has them mismatched.

1.3 Why account categories matter at all

For which three reasons should you assign account category and subcategory to a general ledger account?

Answer: to ensure system-generated account schedules include the account; to ensure consistency of Financial Statement reports; and to ensure the account is included in Microsoft Excel reports.

Why it works. All three answers are the same fact wearing three hats: account categories are the reporting backbone. When BC generates the standard financial reports — Balance Sheet, Income Statement, Cash Flow Statement, Retained Earnings — it does not read your account numbers. It reads the category and subcategory mapping and builds the report structure from it.

This is why the mapping is a genuine consultancy deliverable, not a data-entry chore. Get it right once and the standard reports simply work, in every company, in every language, without a single custom row definition.

Why the others fail. Both distractors are real BC features that have nothing to do with categories:

• Post a transaction directly to a G/L account — governed by the Direct Posting checkbox on the account card. Unrelated.
• Apply dimensions to a transaction — governed by Default Dimensions and the Dimensions setup. Also unrelated.

Naming note: since BC 2022 release wave 2, Account Schedules are called Financial Reports in the UI. Exam material still uses the older term, and so does most of the internet. They are the same object.

1.4 Which reports actually consume the mapping

A user is mapping general ledger accounts to G/L account categories and wants examples of reports where these configurations are directly used. Which three reports can you provide?

Answer: Balance sheet, Cash flow statement, and Retained earnings.

Why it works. These are three of the four out-of-the-box statements BC generates directly from the account category and subcategory mapping (the fourth, Income Statement, simply isn’t among the options). Change a mapping, refresh, and the statement restructures itself.

Why the others fail.

• Sales analysis — reads sales and item ledger entries, sliced by customer, item, and dimension. It never touches account categories.
• Daily invoicing — an operational document report listing invoices for a date range. Not a financial statement at all.

The pattern to internalise: account categories drive statements, not analytics. If a report answers “what is our financial position,” categories matter. If it answers “what did we sell,” they don’t.

---

2. Analytics, Power BI, and Power Platform

Three questions that test whether you can draw the boundary between what Business Central does and what the surrounding Microsoft stack does. The distractors here are all plausible-sounding capabilities attributed to the wrong product.

2.1 Filtering an embedded Power BI report

A purchase manager uses an embedded Power BI report and must display the previous quarter’s figures. What are two ways to achieve this?

Answer: set a filter for the embedded Power BI report displayed in Business Central, or filter the report from the Power BI report interface.

Why it works. Both answers act on the Power BI report itself — one through the report part hosted inside BC, one by opening the report in the Power BI service. Either way you are manipulating the report’s own filters and slicers, which is where a date dimension like “previous quarter” lives.

Why the others fail. Both distractors are legitimate BC features that operate on the wrong object:

• Analyze Data mode — a genuinely excellent feature (pivot-style ad-hoc analysis directly on a list page), but it works on the Business Central list data, not on the embedded Power BI visual. Filtering the list does nothing to the report.
• Set list page filters in Business Central — the embedded report part responds to the currently selected record, not to an arbitrary date range applied to the list. Narrowing the list of purchase documents does not reslice the report’s time dimension.

The distinction worth carrying: BC filters BC data; Power BI filters Power BI data. They meet at record context, and nowhere else.

2.2 What Power Platform actually provides

The finance department needs information about Microsoft Power Platform capabilities to analyze data, automate processes, and build business solutions. Which three capabilities should you recommend?

Answer: create interactive dashboards and visual reports based on Business Central data (Power BI); build a mobile app for sales representatives to enter orders (Power Apps); automate repetitive or approval-based processes involving Business Central data (Power Automate).

Why it works. The three answers map cleanly onto the three Power Platform pillars the question’s own wording hints at — analyze → Power BI, build business solutions → Power Apps, automate processes → Power Automate.

Why the others fail. This is a well-built question, because both distractors are real capabilities — just not Power Platform ones:

• Manage file storage and document collaboration — SharePoint and OneDrive. Microsoft 365, not Power Platform.
• Create predictive forecasts using AI models built directly into Business Central — read that phrasing again. It describes a Business Central feature (the Sales and Inventory Forecast extension, Cash Flow Forecast). The question asked what Power Platform provides. The answer is disqualified by its own description.

2.3 What data connectors are for

A retail company plans to build a Power Apps mobile app so store managers can check stock and submit purchase requests. Which two capabilities can data connectors provide?

Answer: configure custom apps to securely read and update Business Central records, and enable workflow automation that triggers actions in Business Central processes.

Why it works. A connector is a governed data pathway. It gives external applications authenticated, permission-respecting read and write access to BC data, and it exposes triggers and actions that Power Automate flows can hang off. Both halves of the scenario — checking stock (read) and submitting purchase requests (write plus workflow) — run through it.

Why the others fail.

• Generate new general ledger accounts automatically when the connector is enabled — connectors move data; they do not create master records on their own initiative. This would be alarming behaviour if it were true.
• Bypass licensing requirements — the exact opposite of what happens. Connector access is authenticated as a Business Central user and inherits that user’s licence and permission sets. Data reached through a connector is licensed data. Any exam answer offering to bypass licensing is wrong on principle.

---

3. Fixed Assets

Four questions, and one distinction that decides three of them: does this journal integrate with the general ledger, or not?

3.1 Disposal that must appear on the Balance Sheet

An accountant plans to process a fixed asset disposal transaction. The result must be included on the Balance Sheet. Which two components should you recommend?

Answer: the Fixed Asset G/L journal and the Sales invoice.

Why it works. Selling a fixed asset is a two-stage transaction, and the question’s phrase “each correct answer presents part of the solution” is the clue that both stages are required.

Stage one — Fixed Asset G/L Journal. Before you can dispose of an asset you must depreciate it up to the disposal date, otherwise your gain or loss is calculated against a stale book value. You post this in the FA G/L Journal with FA Posting Type = Depreciation and the Depr. Until FA Posting Date checkbox ticked.

Stage two — Sales invoice. The sale itself goes on a sales invoice line with Type = Fixed Asset and the asset number in the No. field. Posting it records the receivable, the disposal, and the resulting gain or loss.

The Balance Sheet requirement is the real test here. Only G/L-integrated postings reach a financial statement.

Why the others fail.

• Fixed Asset journal — the trap, and a good one. The plain FA Journal posts to the fixed asset ledger only. No G/L entries, nothing on the Balance Sheet. It exists for depreciation books kept for tax or reporting purposes that must not touch the financial books.
• Sales journal — a general journal template for sales-side entries. It is not the vehicle for a fixed asset disposal.
• Physical Inventory journal — inventory item counts. Unrelated to fixed assets entirely.

In the field: the FA Journal versus FA G/L Journal distinction is the single most common source of “the asset depreciated but nothing hit the P&L” support tickets. Check the depreciation book’s G/L Integration FastTab before you check anything else.

3.2 Verifying entries before you commit

All entries are created in the Fixed Assets G/L journal and are ready to post. The company must verify and analyze future fixed asset entries. Which feature should you recommend?

Answer: Preview Posting.

Why it works. Preview Posting runs the actual posting routine inside a transaction that is rolled back at the end. You get the complete set of entries that would be created — G/L, FA ledger, VAT, customer or vendor — and you can drill into each one. That is literally “verify and analyze future entries.”

Why the others fail.

• Post and Post and Print — both commit. Verification after the fact is not verification.
• Test Report — closer, and worth knowing. It prints a validation report flagging posting errors: missing accounts, blocked assets, date restrictions. But it reports on the journal lines and their errors, not on the resulting ledger entries. It answers “will this post?”; Preview Posting answers “what will this post?”
• Journal Check — not a Business Central feature. Invented distractor.

3.3 Retiring an asset with no proceeds

The accountant must create an entry that retires a fixed asset without providing proceeds, using the Fixed Asset G/L journal. Which fixed asset posting type should you recommend?

Answer: Disposal.

Why it works. Disposal is the posting type that ends an asset’s life. It closes out the remaining net book value and calculates gain or loss. With no proceeds — scrapping a machine, writing off a stolen laptop — you post a Disposal line with an amount of zero, and BC writes the entire remaining book value off as a loss.

Note also the rule BC enforces: a disposal entry must be the last entry posted for a fixed asset. You cannot depreciate an asset after disposing of it.

Why the others fail.

• Depreciation — spreads cost across the useful life. It reduces book value but the asset stays active and keeps depreciating.
• Write-down — reduces book value to reflect impairment. The asset remains in service. This is the closest distractor and the reason to read the verb: “retires” means the asset is gone, not merely worth less.
• Acquisition Cost — the opposite direction entirely. This is how value enters an asset.

3.4 Two ways to post the disposal

You need to create and post a fixed asset disposal transaction. What are two ways you can achieve this goal?

Answer: post a disposal entry in the G/L journal with the balance account on the same line, or with the balance account on a separate line.

Why it works. Both are valid, and they produce identical results.

Same line: fill Bal. Account Type and Bal. Account No. directly on the disposal line. One self-balancing line.

Separate line: use the Insert FA Bal. Account action, which reads the Disposal Account and Disposal Bal. Account fields from the asset’s FA Posting Group and generates the balancing line for you. This is the safer habit — it uses your configured posting groups instead of relying on the person entering the journal to remember the right account.

Why the others fail.

• Set the depreciation book to Disposed — there is no such setting. Disposed status is a consequence of posting a disposal entry, reflected afterwards in the Disposed and Disposal Date fields. You cannot flip a switch to retire an asset, and it is worth understanding why: the switch would leave the book value stranded in the general ledger.
• Run the Fixed Asset – Book Value 01 / 02 reports — these verify after the fact. Useful, but the question asks how to create and post, and reports do neither.

---

4. Journals and Reversals

4.1 Where reversal actually lives

A company recently posted several transactions that must be reversed. Where does the system allow you to reverse posted transactions?

Answer: General Ledger entries.

Why it works. The Reverse Transaction action lives on the G/L Entries page (and on the Customer, Vendor, and Bank Account Ledger Entries pages). It operates on the Transaction No. that groups all entries created by a single posting, so reversing one line reverses the whole balanced transaction — never half of it.

BC then posts a mirrored correcting entry and marks both sides as reversed, leaving a complete audit trail. This is a deliberate design choice over deletion: in accounting, you never erase, you offset.

Reversal is refused when the entry has been applied (unapply first), when the posting date falls outside your allowed posting range, or when the entry was already reversed.

Why the others fail.

• General journal — where transactions are entered, not where posted ones are reversed. You could of course key a manual opposite entry, but you would lose the linkage, the reversal marking, and the audit trail that make the built-in function worth having.
• Posted Sales Invoices — the sharpest distractor, because this page really does offer Correct and Cancel. But those actions create a credit memo — a new corrective document, which is a different accounting concept from a transaction reversal, and only applies to sales invoices.
• Customer statements — a report.
• Posted Payment Reconciliations — you can undo a posted bank reconciliation, but that is a targeted feature, not the general reversal mechanism.

4.2 The monthly payroll journal

An accountant posts the same payroll expense entries every month and needs a solution that stores the journal setup with all accounts, dimensions, and descriptions for the next period, while still allowing amounts to be adjusted before posting. What should you recommend?

Answer: save the general journal as a standard general journal and retrieve it as needed.

Why it works. A standard journal is a saved template of journal lines. Use Save as Standard Journal once, and thereafter Get Standard Journals pulls the whole structure — accounts, dimensions, descriptions, and optionally amounts — into a clean batch. Adjust the figures, post, done. Nothing happens automatically, which is precisely what the accountant wants.

Why the others fail.

• Copy Document — works on sales and purchase documents. There is no journal equivalent.
• Copy posted entries from the General Ledger Entries page — not a function. You would be re-keying from a list.
• Create a recurring general journal with a fixed reversal method — this is the distractor built from two half-truths. Recurring journals do persist their lines, so the first half sounds right. But Fixed means the amount stays unchanged after posting, and a Reversing method auto-posts an offsetting entry the next day. That combination is designed for month-end accruals, not payroll expense — and it fights the requirement that amounts be adjustable.

In the field: a recurring journal with Variable recurring method (which clears the amount after each posting, forcing fresh entry) is a perfectly good real-world answer to this problem, and arguably better than a standard journal because the recurring frequency drives the posting date forward automatically. The exam wants the standard journal. Know both.

---

5. Deferrals

Six questions — a quarter of the whole set. That weighting is not an accident: deferrals are where revenue recognition, period accounting, and setup design meet, and they are the topic where consultants most often configure something that almost works.

The mental model to hold throughout: a deferral template is reusable configuration. A deferral schedule is one document’s plan. Ledger entries are what actually happened. Three layers, and most wrong answers come from confusing two of them.

5.1 Where you build a user-defined schedule

A project invoice’s revenue must be split across months as: 200 / 1,000 / — / — / 500 / 400. You need to set up a schedule for user-defined deferrals. What are two locations you can use?

Answer: the Sales Order and the Sales Invoice.

Why it works. Look at the numbers: two of the six months get nothing. No automatic calculation method can produce that pattern — not Straight-Line, not Equal per Period, not Days per Period. Skipping periods and setting arbitrary amounts is exactly what Calc. Method = User-Defined exists for.

And a User-Defined template deliberately contains no amounts. You enter them on the Deferral Schedule page, opened from a document line — which means the sales order line or the sales invoice line.

Why the others fail.

• Deferral template — this is where you choose User-Defined, but it holds no amounts. That is the definition of the method, not an oversight.
• G/L account — carries a Default Deferral Template field, which decides which template appears by default. It never holds a schedule.
• Project — no deferral schedule entry point exists on the project card. Deferrals attach to document lines.

5.2 Schedule versus ledger entries

You select a deferral code on a sales invoice line that has a sales rent account. You need to record the deferrals according to a schedule in ledger entries. Which function should you use?

Answer: Post.

Why it works. This question tests one idea: a schedule is a plan; only posting creates entries.

The moment you select a deferral code on the line, BC calculates the schedule automatically — you can open it, inspect it, adjust it. None of that touches the general ledger. It is attached to an unposted document.

Posting is what writes the full amount to the deferral account (a balance sheet account such as Unearned Income) and then creates the dated G/L entries that release it to the income account period by period.

Why the others fail.

• Deferral schedule, Calculate Schedule — the trap, and a well-designed one. This action recalculates the plan on the document after you have changed the start date, number of periods, or amounts. It produces a revised schedule and zero ledger entries.
• Preview posting — shows exactly what would be created, then rolls it back. Extremely useful for validating a deferral before committing; produces nothing permanent.
• Redistribute account allocations and Generate lines from allocation account — both belong to the Allocation Accounts feature introduced in BC 2023 release wave 2, which splits a single line across multiple accounts or dimensions by fixed or variable share. A different feature solving a different problem: allocation splits by account, deferral splits by time.

5.3 Making a deferral apply automatically

The company sells one-year support subscriptions and must recognise income monthly rather than all at once. You need to set up the deferral template so it is added automatically when a subscription is invoiced. Where should you set up the deferral template?

Answer: the Item card.

Why it works. The Default Deferral Template field sits on the Costs & Posting FastTab of the Item card. The identical field exists on the Resource card and the G/L Account card — the three things you can sell on a document line. Put a template there, and the Deferral Code on the sales line fills in automatically whenever that item is sold.

The design principle: deferral is a property of what you sell, not who you sell it to. A one-year support subscription is recognised over twelve months regardless of which customer buys it.

Why the others fail.

• Customer card — no such field, for the reason just given.
• Sales & Receivables Setup — holds no deferral default. A company-wide default would be meaningless anyway, since most lines should not be deferred.
• Recurring Sales Journal — not how subscription invoices are raised here, and journals carry no default template.

5.4 Choosing a calculation method

A movie subscription service’s start date must be based on the number of days the service was used since the sales date. Which calculation method should you select for a six-month period?

Answer: Days per Period.

Why it works. The four methods differ in how they slice the amount:

Method	How the amount is split
Straight-Line	By number of periods, distributed according to period length
Equal per Period	By number of periods, distributed evenly — every period identical
Days per Period	By the actual number of days in each period
User-Defined	Not calculated at all — you type every amount

The question’s phrase — “based on the number of days the service was used” — maps directly onto Days per Period. A subscription starting on the 20th gets eleven days of revenue in the first month, a full month in months two through six, and the remaining days trailing into a seventh partial period.

Why the others fail.

• Equal per Period — every period gets the same amount regardless of how many days it contains. February and March would recognise identical revenue. It ignores the day count entirely, which is the one thing the question asks for.
• Straight-Line — the genuinely close cousin, and worth understanding. It also produces a prorated first period, but it distributes by period length rather than computing strictly from day counts. In many calendars the two produce similar numbers; the exam distinguishes them by the wording “number of days.”
• User-Defined — manual entry, no calculation. Wrong whenever a rule exists.

5.5 Automating an annual expense

The company pays an annual insurance fee providing 12 months of coverage. You need to recognise the expense evenly across the year when the vendor invoice is posted. What should you configure to automate this?

Answer: a deferral template.

Why it works. Build a template with 12 periods and Equal per Period, then assign it as the Default Deferral Template on the insurance expense G/L account. When the vendor invoice is posted, BC debits a deferred-expense balance sheet account for the full amount and schedules twelve monthly releases into the expense account. No monthly intervention.

Why the others fail. The emphasis in the question is on the two words automate and when posted:

• Recurring general journal — would produce the right numbers, but manually: someone posts it every month, forever, and it is not triggered by the invoice. It solves the accounting and fails the requirement.
• Posting groups — route amounts to the correct accounts. They carry no concept of time.
• Vendor posting setup — maps payables and discount accounts. Same limitation.
• Purchase price list — sets what you pay, not when you recognise it.

5.6 Getting the start date into the right tax period

You receive a vendor invoice for the previous period. You need to defer and record the invoice for the real tax period. Which period should you use to configure the start date for the deferral?

Answer: Beginning of Period.

Why it works. The Start Date field on the deferral template offers five options, and each anchors the schedule differently relative to the invoice’s posting date:

Option	Schedule starts
Posting Date	On the posting date itself — first period is partial
Beginning of Period	Day one of the accounting period containing the posting date
End of Period	Last day of that period
Beginning of Next Period	Day one of the following period
Beginning of Next Calendar Year	1 January of the following year

The cost belongs to the previous period, so you post with a posting date in that period, and Beginning of Period anchors the schedule to its first day. The expense lands where it was incurred, which is what “the real tax period” means.

Why the others fail.

• Posting Date — starts mid-period, splitting the first period into a stub. Defensible for genuine mid-month service starts, wrong when you are aligning to a tax period.
• End of Period and Beginning of Next Period — both push recognition forward, out of the period the cost belongs to. Given the scenario mentions the department already exceeded its budget, deferring the cost out of the period is the one thing that would look worst in an audit.
• Beginning of Next Calendar Year — deliberately shifts everything into the next fiscal year. It has a legitimate use (an annual licence bought in December and consumed the following year), but it is not this one.

---

6. Sales and Purchase Document Flow

6.1 Quote to invoice, or quote to order?

A cleaning company charges by the hour and requires payment in full before services are rendered. You create a sales quote for six hours; the customer accepts and needs the bill. What should you do?

Answer: convert the quote to an invoice.

Why it works. The Sales Quote page carries both a Make Invoice and a Make Order action. Which one you choose depends on whether there is anything to manage between agreement and billing.

Here there is not. It is a service — no shipment, no partial delivery, no warehouse. And payment is due before the work happens, so you need the receivable on the books immediately. Make Invoice converts the quote straight into a sales invoice you can post and send.

Why the others fail.

• Convert the quote to a sales order and Create a sales order from the quote — read these two carefully: they describe the same action. When two options are functionally identical, neither can be the single correct answer, because the exam cannot mark one right and the other wrong. That is a free elimination, and it is worth training yourself to spot. On the merits, both are also wrong: an order adds a shipping step this business does not have, and leaves an open document that must still be invoiced before anyone gets billed.
• Send an approval request for the quote — routes the document internally for sign-off. The customer has already accepted; nobody is waiting on approval, and approval bills no one.

6.2 One invoice for a month of shipments

The company ships to the same customer several times a month, and at month-end the customer wants one invoice combining all posted shipments. Which two actions should you perform?

Answer: post each sales order as shipped but not invoiced, and run the Combine Shipments report.

Why it works. The Combine Shipments batch job scans posted sales shipments that have not yet been invoiced and generates one sales invoice per customer, grouping by bill-to customer, currency, and dimension values.

That “not yet invoiced” condition is the whole design. Posting with Ship only leaves the shipment available to be picked up later; posting with Ship and Invoice consumes it immediately. The two actions in the answer are cause and effect.

Why the others fail.

• Post each shipment as shipped and invoiced on the same day — the direct contradiction. Every shipment is already invoiced; Combine Shipments finds nothing.
• Create a recurring sales invoice with all shipped items — recurring sales lines and standard sales codes exist in BC, but they generate documents from a saved template. They do not gather posted shipments, and they have no idea what was actually delivered.

In the field: there is a third prerequisite the question omits and clients always hit — the Combine Shipments checkbox on the Shipping FastTab of the Customer card. Without it, orders for that customer default to Ship and Invoice and the whole flow collapses on the first posting. Set it on the customer, not just in the process.

6.3 Invoicing goods you already received

You have a vendor invoice for delivered items on a purchase order. You need to create a purchase invoice for the items. What should you do?

Answer: create a new invoice and use the Get Receipt Lines function.

Why it works. Get Receipt Lines pulls lines from posted purchase receipts into a purchase invoice while preserving the link back to the receipt. That link is what makes the numbers reconcile: the receipt’s invoiced quantity updates, the purchase order’s Qty. Invoiced advances, and the accrued-purchases account clears correctly.

It also handles the messy reality of purchasing — one vendor invoice covering three receipts, or one large receipt invoiced in two instalments — because you select lines and quantities rather than whole documents.

Why the others fail.

• Copy the purchase order into the invoice and copy the posted purchase receipt into the invoice — Copy Document brings the lines across as new lines with no receipt linkage. The quantities are treated as fresh, so you would receive the goods a second time and inflate inventory. This is the trap that looks most reasonable and does the most damage.
• Add invoice details to the purchase order and post the invoice — legitimate BC behaviour and a fine approach when you are invoicing one order in full. But the scenario describes a separate vendor invoice for already-delivered goods and explicitly asks you to create a purchase invoice. It also breaks down the moment the vendor’s invoice does not align neatly with a single order.
• Calculate the invoice and prepayment discount in the purchase order — prepayment functionality. Unrelated.

---

7. Profiles, Personalisation, and Customisation

Two questions, one distinction, and it is the distinction that separates consultants who administer BC from users who tinker with it.

Personalisation is what a user does to their own workspace. It affects them alone, it is reached from the Settings gear, and it is cleared with Clear Personalization.

Customisation is what an administrator does to a profile, affecting every user assigned to that role. It is reached from the Profiles (Roles) page, and it is cleared with Clear Customization.

Same-looking UI. Completely different scope. The exam knows this and tests it directly.

7.1 Removing a profile customisation

You need to remove customizations applied to the Customer list page in the Order Processing profile. Which three actions should you perform?

Answer:

1. Open the profile in customization mode from the Profiles (Roles) list page.
2. Open the Customer list page in customization mode and select Clear Customization.
3. Open Manage Customized pages from the Profiles (Roles) list page and delete the Customer List page entry.

Why it works. Profile customisations are administered from one place: the Profiles (Roles) page. From there you have two routes to the same outcome.

The interactive route is steps 1 and 2 in sequence: select the profile, choose Customize Pages to enter customisation mode for that profile, navigate to the Customer list, and clear it.

The administrative route is step 3 standalone: each customised page is stored as a record, and the Customized Pages view lets you delete that record directly — faster when you know exactly which page to reset and do not want to navigate there in customisation mode.

Why the others fail.

• From the Order Processing role center, open the profile in customization mode — you cannot. From inside a role center, the Settings gear offers Personalize, which changes only the current user’s view. Entering customisation mode for a profile is an administrative action that starts from the Profiles (Roles) page. This distractor is testing whether you know where authority lives.
• Open the Customer list page in personalization mode and select Clear Personalization — the central trap. This clears one user’s personal tweaks and leaves the profile customisation completely intact. The user’s page might even look temporarily fixed, which makes it a genuinely dangerous wrong answer in practice: you would close the ticket and it would reopen for everyone else.

7.2 Changing the Role Center for a whole role

A Sales Order Processor user wants a different Role Center, and the change must apply to all other Sales Order Processor users. Where should you configure this?

Answer: the Profile (role) page.

Why it works. The Role Center field lives on the profile card. Change it there and every user assigned to that profile sees the new Role Center at their next sign-in — which is exactly the “must exist for all other users” requirement.

Why the others fail.

• My Settings page — changes the role for one user only. This is precisely what the question rules out, and it is the answer most people pick because it is the page they have actually used.
• Customized pages — lists page-level customisations for a profile. The Role Center assignment is a property of the profile itself, not a customised page.
• Role Center page — this is the object being displayed, not the place you configure which profile displays it.
• Profile extensions page — a developer-facing view of AL extensions that modify profiles. Not an administrative setting, and not where you reassign a Role Center.

---

The Five Traps Worth Memorising

Strip away the scenarios and nearly every wrong answer above falls into one of five patterns. Learn these and you will out-perform your actual knowledge of BC.

1. Setup versus workaround. Business Central enforces business rules through configuration — Check G/L Account Usage, the Combine Shipments checkbox, Default Deferral Template. Any option that solves a configuration problem by posting data, keying manual entries, or re-typing something monthly is almost always the trap. It usually works, which is what makes it tempting.

2. Customisation versus personalisation. Profile-wide versus per-user. Different starting page, different action, different verb. If a scenario says “for all users,” you are in Profiles (Roles). If it says “for this user,” you are in My Settings or Personalize.

3. G/L integration. The FA Journal versus the FA G/L Journal is the archetype, but the principle is general: if it must appear on a financial statement, it must reach the general ledger. Whenever a question mentions the Balance Sheet or an income statement, check whether the proposed vehicle is G/L-integrated.

4. Information versus entries. Preview Posting, Test Report, Calculate Schedule, Where-Used List, and the Book Value reports all produce information. Only Post produces ledger entries. Questions that say “record,” “create,” or “post” want Post; questions that say “verify,” “analyze,” or “check” want one of the others.

5. Product boundaries. Power BI analyses, Power Apps builds, Power Automate automates, SharePoint stores files, and Business Central does its own forecasting. When a Power Platform question offers a capability that belongs to a different product — or to BC itself — that is the eliminated answer, however true the statement is.

And one piece of pure exam technique from §6.1: when two options say the same thing in different words, both are wrong. A single-answer question cannot mark one right and its paraphrase wrong.

---

Answers at a Glance

#	Topic	Answer
1	Prevent G/L account deletion	Check G/L Account Usage + assign to posting group setup
2	New cost account	Account Category = Expense; Income/Balance = Income Statement; Indent COA
3	Why assign categories	Account schedules; financial statement consistency; Excel reports
4	Reports using categories	Balance sheet; Cash flow statement; Retained earnings
5	Filter embedded Power BI	Filter the embedded report part; filter in the Power BI interface
6	Power Platform capabilities	Power BI dashboards; Power Apps mobile app; Power Automate workflows
7	Data connectors	Secure read/update from custom apps; workflow automation triggers
8	FA disposal on Balance Sheet	Fixed Asset G/L journal + Sales invoice
9	Reverse posted transactions	General Ledger entries
10	Repeating payroll journal	Save as standard general journal
11	Verify future FA entries	Preview Posting
12	Retire asset, no proceeds	Disposal
13	Two ways to post disposal	Balance account on same line; on separate line
14	User-defined deferral schedule	Sales Order; Sales Invoice
15	Quote, paid in advance	Convert the quote to an invoice
16	Record deferrals in ledger	Post
17	Automatic deferral template	Item card
18	Deferral by days used	Days per Period
19	Combine month’s shipments	Post as shipped not invoiced; run Combine Shipments
20	Invoice delivered PO items	New invoice + Get Receipt Lines
21	Annual insurance expense	Deferral template
22	Deferral start, prior period	Beginning of Period
23	Remove page customisation	Customization mode from Profiles; Clear Customization; delete Customized Pages entry
24	Role Center for all users	Profile (role) page

Questions 19 and 20 in the original set were identical, so they are merged here; the numbering above is this article’s, not the source’s.

---

Further Reading

Everything above is grounded in official documentation. If a section left you unsure, these are the pages to read:

• The General Ledger and the Chart of Accounts
• Defer revenues and expenses
• Dispose of or retire fixed assets
• Manage fixed assets
• Customize pages for profiles
• Free Business Central e-learning on Microsoft Learn

The exam rewards people who have configured these things, not people who have read about them. If any section above felt abstract, open a sandbox and build it — the deferral templates especially. Twenty minutes with a real invoice teaches more than an hour of revision notes.