When a cash receipt is applied incorrectly, you cannot simply delete or reverse it - instead, you must unapply the entries.
Steps:
* From the relevant Customer Ledger Entry, select Unapply Entries.
* Unapply the second payment first (because payments are applied in sequence).
* Unapply the first payment (the erroneous one).
* Reapply the second payment correctly to the customer ledger entry.
This way, the first erroneous cash receipt is removed, and the correct receipt remains applied.
Why not B or C?
* Reverse Transaction is for reversing journal entries or posted G/L transactions, not for applied customer ledger entries.Why not D?
* Posting a reversing cash receipt is unnecessary; the built-in Unapply Entries function is the proper approach.
Reference:
Unapply Customer Ledger Entries in Business Central

The requirement is: "Customer pricing is determined by the customer market type (Retail, Veterinarian, Breeder). Each customer is associated with only one market type." A). Assign the Customer Price Group code on the customer card # Correct, because each customer must be tied to its market type via a Customer Price Group.
C). Create a Sales Price List by using the assign-to type of Customer Price Group # Correct, because pricing and discounts should be managed at the group level, not per individual customer, ensuring easier maintenance.
E). Create Customer Price Groups that allow line discounts # Correct, because discounts are offered by item, brand, or product category, and must flow to sales lines automatically.
Incorrect options:
B). Exclude line discounts # Opposite of requirements.
D). Create a Sales Price List for the customer # Not scalable; must be done by group, not individual customer.
Correct answers: A, C, E
References:
Set Up Customer Price Groups
Create Sales Price Lists
The requirement is: "Customer pricing is determined by the customer market type (Retail, Veterinarian, Breeder). Each customer is associated with only one market type." A). Assign the Customer Price Group code on the customer card # Correct, because each customer must be tied to its market type via a Customer Price Group.
C). Create a Sales Price List by using the assign-to type of Customer Price Group # Correct, because pricing and discounts should be managed at the group level, not per individual customer, ensuring easier maintenance.
E). Create Customer Price Groups that allow line discounts # Correct, because discounts are offered by item, brand, or product category, and must flow to sales lines automatically.
Incorrect options:
B). Exclude line discounts # Opposite of requirements.
D). Create a Sales Price List for the customer # Not scalable; must be done by group, not individual customer.
Correct answers: A, C, E
References:
Set Up Customer Price Groups
Create Sales Price Lists
Topic 4, Fabrilcam. Inc.
Background
Fabrilcam. 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 1500
* 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 invokes 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 = S4800
* Retail Sales = 44100
* Wholesale Sales = 44200 Sales Prepayments = 22160
Issues
* Order entry lakes 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 m 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.

Explanation:

Comprehensive Detailed Explanation
In Dynamics 365 Business Central, when configuring approval workflows, the Approver Limit Type determines how the system decides which user should receive an approval request:
* Direct Approver
* Uses the Approval User Setup table.
* Always routes the request to the direct approver defined for the user, ignoring the document amount.
* Correct for: "Route approval requests to the approver defined in Approval User Setup, regardless of the amount."
* Specific Approver
* Routes requests to a hard-coded approver specified in the workflow response itself.
* Amounts are not considered.
* Correct for: "Route approval requests to the approver defined in the Workflow Response, regardless of the amount."
* First Qualified Approver
* Checks the approval chain and finds the first approver with sufficient approval limit to approve the amount.
* Correct for: "Route approval requests to a user who can approve requests for the required amount."
* Approver Chain
* Routes approval up the chain, potentially to multiple approvers, until it reaches the top of the approval hierarchy.
* Not directly required in this scenario.
:
Microsoft Learn - Set up approval users and workflows
Microsoft Learn - Workflow Responses and Approver Types

In Dynamics 365 Business Central, the General Journal Reconciliation feature allows reconciliation of ledger entries against G/L accounts (often bank, clearing, or control accounts).
To include a G/L account in the general journal reconciliation window:
* You must enable the Reconciliation Account field on the G/L Account Card.
* This setting flags the account as reconcilable, so it appears in the reconciliation process.
Why not the others?
* B. Direct Posting field # Controls whether you can post directly to the account, not related to reconciliation.
* C. Bank Account Posting Group # Links bank accounts to G/L accounts, but the reconciliation flag still must be set.
* D. Create a new payment reconciliation journal # Used for bank statement reconciliation, not general ledger account reconciliation.
Microsoft Learn Reference
* Reconcile General Ledger Accounts in Business Central

With Check G/L Account Usage = Yes enabled in General Ledger Setup, deletion of a G/L account is only possible if:
* The account has no ledger entries.
* The account has no balance.
* The account is not used in setup fields (posting groups, posting setup, etc.).
The most direct requirement is no balance amount.
Reference:Delete G/L Accounts