Which Two Processes for Combined Purchase Receipts in Business Central?
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in the case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question. Background - Fabrikam, Inc., is a manufacturer of products for the gift industry. The company plans to implement Business Central as its new enterprise resource planning (ERP) system. The company sells to two types of customers: wholesale and retail. Retail customers order at special events and online. Wholesale customers send in orders by email. Current Environment - Order processing - • The company uses a purchase order (PO) workflow for any PO over $500. • The system has been fully configured for sales order prepayments and will check for a prepayment invoice at posting. • Customers can special order products with a prepayment that is due on receipt. Invoicing - • Wholesale customer payment terms are net 30, with a 2% discount if paid within 10 days. • Retail customer payment terms are payable on receipt or shipment. Reporting - • The company uses headcount (number of employees) and square footage for statistical accounts. Integrations - The company currently uses Outlook, Excel, Word, and Teams to communicate internally and externally with customers and vendors. Requirements - Order processing - • The company must be able to combine multiple purchase receipts into one vendor invoice. • Posted vendor invoices must be reverted when damages are reported or a product is returned to the vendor. • Fully invoiced POs must not appear on the PO list page. • Customer prepayments vary based on customer relationship. Special orders from new customers have a 25% prepayment. Established customers have only a 15% prepayment. • The company must be able to approve POs by email without opening Business Central. • Customers often reorder the same items with similar quantities. The system must be configured to ask the user if recurring lines should be added to sales orders. Invoicing - • Customer revenue must be posted to separate general ledger (G/L) accounts based on customer type. The G/L account must have subcategories for wholesale and retail revenue. • Accounts receivable must be posted to separate G/L accounts based on customer type. The G/L account must have subcategories for wholesale and retail accounts receivable. • Currently, inventory is sold at a cost based on purchase and sales over a period. Reporting - • Financial reports must include statistical accounts. • The financial report structure must map to account categories. Integrations - The company requires the following integration capabilities: • Create sales orders while collaborating with customers by email. • Edit customer information while messaging the sales team in a group chat. • Communicate a brochure to all customers at once about a sales campaign. General ledger posting accounts - The company requires the following G/L posting accounts: • Retail Receivables = 13100 • Wholesale Receivables = 13200 • Payment Discount = 54800 • Retail Sales = 44100 • Wholesale Sales = 44200 • Sales Prepayments = 22160 Issues - • Order entry takes too long for wholesale customers. • Vendors ship partial orders but send one monthly invoice. The company is unable to associate one invoice with multiple POs in the current environment. • Inventory reconciliation was difficult in the company's old system because it allowed users to sell more inventory than was physically available. • Users must log in to the system to provide workflow approvals. You need to train users on order processing requirements and how to process purchase invoices created from combined receipts. Which two related processes should you include? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
Community Votes
67% of anonymous learners picked answer BC. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests your ability to map the case's purchasing requirements onto the exact Business Central processes — combining receipts leaves each PO fully invoiced, and reverting a posted vendor invoice for damages or a return needs a purchase credit memo — while the trap is borrowing the sales-order recurring-lines requirement and turning it into a purchase process.
This MB-800 case-study question asks which two Business Central processes users must be trained on when multiple purchase receipts are combined into one vendor invoice. It establishes that deleting fully invoiced POs (B) and creating a purchase credit memo (C) are the two related processes the scenario requires.
The most common wrong pick is A (Create recurring purchase lines), because the case mentions recurring lines; however, that requirement explicitly applies to sales orders, so training users on recurring purchase lines satisfies no stated requirement.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The case requires that multiple purchase receipts be combined into one vendor invoice and that posted vendor invoices be reverted when damages are reported or goods are returned to the vendor. When several POs are consolidated into a single vendor invoice, every one of those POs ends up fully invoiced, so users must know how the system removes/delete POs that are fully invoiced so they stop appearing on the PO list page — exactly option B. For the reversal requirement, the supported Business Central process is to create a purchase credit memo against the posted vendor invoice, which reverses the purchase cost and the payable and can reference the goods returned to the vendor — option C. Both processes belong to the same combined-receipt-to-one-invoice flow, which is why the question calls them "related" processes to include in the training.Why the Other Options Are Wrong
A (Create recurring purchase lines) is the classic distractor: the case states that recurring lines must be offered on sales orders ("ask the user if recurring lines should be added to sales orders"), so a recurring purchase line process answers a requirement the scenario never makes. D (Correct or cancel unpaid purchase invoices) addresses unpaid posted invoices used to fix a document before settlement, whereas the case is about reverting posted vendor invoices caused by damages or a return to the vendor, which is the purchase credit memo path. In addition, D largely duplicates C instead of covering the second, distinct process the combined-receipt scenario needs, and neither C nor D alone handles the fully invoiced PO list requirement.Community Comment Notes
python123 argued that "A and B are out of box functions, don't need train the user" and leaned toward C and D, but every process named here is a standard Business Central capability, so being "out of the box" does not disqualify B or C from the training list. 73e77dc selected A and B yet justified B with the observation that "in combined shipments PO are left open in the system and must be deleted afterwards", which is precisely the PO list page requirement behind option B. Another learner simply posted "Answer is BC", while f5b341e asked "Why not AC?", illustrating how easily candidates swap the sales-order recurring-lines requirement into the purchasing scenario.Official Reference
Exam Strategy
In MB-800 case studies, re-read the requirement bullets and match each option literally to one bullet before selecting; here only the "fully invoiced POs must not appear on the PO list" rule and the "posted vendor invoices must be reverted" rule map to real processes. Beware of options that swap document types (purchase versus sales) or that fix unpaid documents when the scenario is about posted ones.
Frequently Asked Questions
Why is creating recurring purchase lines (A) not a valid training process here?
The case only requires recurring lines on sales orders for repeat customers, so training users on recurring purchase lines does not satisfy any stated requirement.
Why is correct or cancel unpaid purchase invoices (D) wrong for this scenario?
Correct and Cancel only work on unpaid posted invoices used before settlement, while the case needs posted vendor invoices reverted for damages and vendor returns, done with a purchase credit memo.