Which Posting Groups Post Wholesale and Retail Revenue 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 configure posting groups to post revenue per invoicing requirements. Which two groups should you use? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Community Votes
50% of anonymous learners picked answer BD. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests whether you know the General Posting Setup pair (Gen. Bus. PG x Gen. Prod. PG) resolves the revenue/sales account, while the trap is assuming the customer posting group, which controls receivables, also controls revenue.
In Business Central, the sales revenue account on a posted sales invoice comes from the General Posting Setup, whose key is the combination of a general business posting group and a general product posting group. This page explains why splitting Fabrikam's retail and wholesale revenue into 44100 and 44200 requires both of those groups rather than the customer posting group.
Picking customer posting groups (C) because revenue must differ by customer type; the customer posting group only supplies the receivables account (13100/13200), it does not determine the sales account on the invoice.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Fabrikam needs Retail Sales = 44100 and Wholesale Sales = 44200 to be hit automatically when sales invoices are posted. In Business Central the sales (revenue) account is not stored on the customer or the item; it is read from the General Posting Setup, whose primary key is exactly the pair general business posting group x general product posting group. The business posting group is taken from the customer (RETAIL vs WHOLESALE) and the product posting group from the item line, so you must create/assign the general business posting groups for the two customer types and keep the general product posting groups that complete each setup row. Every relevant Gen. Bus. PG x Gen. Prod. PG row then carries 44100 for retail and 44200 for wholesale, which satisfies the requirement that revenue be split by customer type. That is why both B and D are required parts of the solution.Why the Other Options Are Wrong
Bank account posting groups (A) only control which bank G/L account is used for bank ledger entries and reconciliation, so they never touch a sales invoice revenue line. Customer posting groups (C) hold the Receivables Account and therefore satisfy the separate requirement that AR be split into 13100 (retail) and 13200 (wholesale) - a balance-sheet entry, not revenue; the question explicitly asks about posting revenue. General product posting groups alone (D without B) cannot differentiate customers, because the same item is sold to both wholesale and retail buyers, so a product-only key would collapse the two revenue accounts into one. Inventory posting groups (E) drive inventory valuation and COGS through the Inventory Posting Setup and are never the source of the sales/revenue account. This income-statement versus balance-sheet split is the cleanest way to eliminate the distractors.Community Comment Notes
The recorded votes are deadlocked (BD 50, BC 50), so the thread is a tie-breaker, not a majority signal. python123 landed on the intuitive pairing with "B. general business posting groups C. customer posting groups", and 73e77dc reasoned that "retail/wholesales are related to the customer (not product)", concluding that the general business posting group specifies revenue while the customer posting group covers receivables. That logic correctly identifies where the customer-type split lives, but it stops one step short: the revenue account is only resolvable through a full General Posting Setup row, which needs a product posting group on the other half of the key. 70e8a4b cut straight to the deciding factor with "for income statement BD" - revenue is an income statement account, and the income statement accounts (sales, COGS, inventory adjustment) all live on the General Posting Setup, while the customer posting group feeds a balance-sheet control account.Official Reference
Exam Strategy
In case-study questions about posting groups, first identify which G/L entry the requirement is about: revenue and COGS come from the General Posting Setup (Gen. Bus. PG x Gen. Prod. PG), while receivables/payables come from the customer or vendor posting group. Read the verb in the question - 'post revenue' versus 'post receivables' - and only then pick letters.
Frequently Asked Questions
Why is the customer posting group not enough to split retail and wholesale revenue?
The customer posting group only supplies the receivables account (13100/13200). Revenue comes from the General Posting Setup, which pairs a general business and a general product posting group.
Does Fabrikam need new general product posting groups for wholesale and retail?
No. Retail and wholesale are customer attributes, so they drive the general business posting group; existing general product posting groups pair with them in the General Posting Setup.