Explanation:

When configuring bank accounts in Dynamics 365 Business Central, there are two key aspects:
* Bank Account Nos.
* Controlled in the General Ledger Setup.
* This setup determines the default number series used when you create new bank accounts.
* Correct assignment: General Ledger Setup.
* G/L Account for the bank account
* Each bank account in Business Central must be linked to a unique G/L account to ensure proper postings of deposits, payments, and reconciliations.
* This is controlled by the Bank Account Posting Group, where you specify the G/L account that represents that bank account in the chart of accounts.
* Correct assignment: Bank Account Posting Group.
Why not the others:
* Cash Flow Setup and Source Code Setup are unrelated to defining number series for bank accounts.
* General Business Posting Group and General Posting Setup handle VAT and revenue/cost account mapping, not bank account posting.
* Bank Account Currency Code defines the currency of the bank account, but not its link to a G/L account.
:
Microsoft Learn: Set Up Bank Accounts in Business Central
Microsoft Learn: Bank Account Posting Groups

Comprehensive Detailed Explanation
The requirement in the case study is that the company warehouses products as Case quantities but wants to expand capabilities by setting up all inventory in a quantity of Each. This means they need to configure Units of Measure (UoM) so that one item can be managed both by Case and by Each.
In Business Central:
* Units of Measure Table - defines the available unit codes (e.g., EACH, CASE, BOX) with descriptions.
* To use Case as a unit, you must first define it in the Units of Measure table.
* Correct: D. Add a Code and Description to the Units of Measure table.
* Item Units of Measure (Qty. per UoM) - links the item to multiple units of measure and specifies conversion (e.g., 1 Case = 10 Each).
* For example, if a Case = 10 Each, you set Qty. per Unit of Measure = 10 for Case.
* Correct: A. Set a Unit of Measure for case to a Qty. of 10.
* Why the other options are incorrect:
* B. Qty. per UoM = 1 is redundant (default Each already equals 1). It does not meet the requirement for Case-to-Each conversion.
* C. Case with Qty. = 1 would make Case = Each, which is incorrect because Case must represent multiple units (10 Each).
Microsoft Learn References
* Work with Units of Measure
* Set Up Item Units of Measure

Explanation:

The requirement is: "You need to configure retail store customer cards to track revenue by market." In Business Central, to track revenue by customer market (Retail, Veterinarian, Breeder), you configure default dimensions on the Customer Card.
* Assign the dimension code # Market
* The business wants to analyze revenue by Market (Retail, Veterinarian, Breeder).
* Therefore, the dimension code must be Market.
* Assign the dimension value code # Retail
* For this specific setup, the customer is a retail store, so the dimension value must be Retail.
* Select a value posting # Same code
* To ensure that every posting for this customer always carries the same dimension value, use Same Code.
* Other options:
* Blank = no default dimension.
* No code = optional dimension.
* Code mandatory = requires entry but allows flexibility in values.
* Since we want strict tracking by a fixed market (Retail), Same code is correct.
This ensures that every transaction posted for the customer will always have Market = Retail, enabling accurate revenue tracking.
Microsoft Learn references:
* Work with Dimensions
* Set Up Default Dimensions
* Dimension Value Posting Options

Explanation:

Comprehensive Detailed Explanation
To record customer payments in Business Central and apply them against invoices while updating the bank account, you use the Cash Receipt Journal. The preparation follows a clear sequence:
* Open a cash receipt journal
* Navigate to Cash Receipt Journal via search. This opens the batch where payments are entered.
* Add lines for each customer payment
* Enter the Account Type = Customer, the Customer No., the Payment Amount, and the posting date.
* Each line represents one customer payment.
* Select G/L Account as the Balance account type
* Set the Bal. Account Type = G/L Account (or Bank Account depending on how the company manages postings).
* Enter the Bal. Account No. to represent the bank G/L account where the payment will be deposited.
* Apply entries
* Use Process # Apply Entries to match the payment against one or more open customer invoices.
* This ensures the payment clears the correct outstanding balances.
* Post the cash receipt journal
* Once all lines are entered and applied, select Post to create the customer ledger entries and bank G
/L entry.
This workflow ensures:
* Customer balances are reduced.
* The payment is reflected in the bank account.
* The invoices are applied correctly.
Microsoft Learn References
* Apply Customer Payments Manually
* Cash Receipt Journals
* Work with General Journals

Explanation:

In Dynamics 365 Business Central, you can configure discount posting to determine how the system calculates and posts discounts:
* Calculate discounts given on items sold # Select Line Discounts
* Line Discounts are calculated on individual item lines (e.g., 10% off a specific product).
* This matches the requirement because the company wants discounts applied to each sold item, not on the total invoice.
* Invoice Discounts would apply to the total invoice amount, not per item.
* Post discounts to general ledger account # Sales Line Disc. Account
* Once discounts are calculated, they must be posted to a specific account in the G/L.
* You configure this by specifying a Sales Line Discount Account in the General Posting Setup.
* This ensures discount postings are separated and tracked properly.
Other options not correct:
* Select Invoice Discounts # Totals-level discounts, not per item.
* Select No Discounts # Disables discount posting.
* Purchase Line Disc. Account # For purchase-side discounts, not sales.
Microsoft Learn References
* Set Up Discount Posting
* Sales Line Discounts