Explanation:

Comprehensive Detailed Explanation
The Suggest Vendor Payments batch job in Microsoft Dynamics 365 Business Central proposes vendor payments based on due dates, available discounts, and applied report filters. The key logic applied to each requirement is:
* Invoice PI001 (Amount -500.00, Due 02/15/21, Payment Discount Date 02/15/21)
* Requirement is to suggest payment on 02/28/21.
* Even though the discount date has passed, to include PI001 the Last Payment Date must be 02/28
/21 with the Posting Date = 02/28/21.
* This ensures the invoice appears in the suggested payments run at month end.
* Credit Memo PC001 (+125.00, Posting 01/08/21, Due 02/08/21)
* Credit memos are suggested as refunds if their due date is within the last payment date window.
* Since it's required on 02/28/21, set Last Payment Date = 02/10/21; Posting Date = 02/28/21 to ensure it is picked.
* Invoices PI002 and PI003 with discounts
* PI002 (Amount -1000.00, Discount -20.00, Discount date 02/28/21).
* PI003 (Amount -75.00, Discount -1.50, Discount date 02/27/21).
* Both discounts fall before 02/28/21. To ensure the discount is deducted, Find Payment Discounts must be set to Yes.
* The Last Payment Date = 04/01/21 with Posting Date = 02/25/21 ensures they are included while respecting discount dates.
Microsoft Learn References
* Suggest Vendor Payments - Business Central
* Payment Discounts
* Vendor Payments in Business Central

Requirement: Invoices must be automatically emailed to customers using a fixed template.
Solution:
A). Set Email to Yes (Use Default Settings) # ensures invoices are sent automatically without prompting.
E). Apply Office Server Settings to the SMTP Mail Setup # configures the company's mail server (SMTP
/Office 365) so that emails are sent.
F). Assign a Document Sending Profile to the Customer where Email is set to Yes # links customers to the correct sending method (Email with fixed template).
Other options:
B). Allow Sender Substitution is optional, not required.
C). Prompt for Settings requires manual action (not automatic).
D). Assigning "Email = No" contradicts the requirement.
Reference:Set Up Document Sending ProfilesSMTP Mail Setup in Business Central

Explanation:

Comprehensive Detailed Explanation
In Dynamics 365 Business Central, the Value Posting field on dimensions defines how dimensions behave during posting:
* No Code
* The dimension is optional.
* Users can change or skip the default dimension value when entering a transaction.
* Used when you want flexibility.
* Code Mandatory
* A dimension value must be entered before posting is allowed.
* Ensures the transaction always contains a dimension value, but users can pick any valid one.
* Used when dimension entry is required for reporting.
* Same Code
* The system enforces that only the default dimension value assigned to the account type can be used.
* Users cannot change the default value, ensuring strict consistency.
Microsoft Learn References
* Default Dimensions and Value Posting Types
* Set Up Dimensions

Explanation:

In Dynamics 365 Business Central, posting groups automatically direct entries to the appropriate general ledger accounts based on transaction type.
* Customer Posting Groups
* Define how customer transactions are posted to the general ledger.
* They handle accounts such as receivables and also manage payment differences (e.g., rounding or short payments).
* Correct for: Automatic posting of received payment differences.
* Vendor Posting Groups
* Define how vendor transactions are posted.
* They specify the payables account in the G/L where vendor balances are tracked.
* Correct for: Automatic posting to the payables account.
* Inventory Posting Groups and Inventory Posting Setup
* Define how inventory transactions post to G/L accounts.
* They also control postings to work in progress (WIP) accounts, including location-specific accounts.
* Correct for: Automatic posting to different work in progress balance accounts, depending on the location.
Why not the others:
* Bank Account Posting Groups # Define which G/L accounts are linked to bank accounts, not payment differences, payables, or WIP.
* General Posting Setup # Determines revenue, COGS, and VAT accounts based on business/product posting groups, not the specific actions in this scenario.
:
Microsoft Learn: Set up General Posting Groups
Microsoft Learn: Customer and Vendor Posting Groups
Microsoft Learn: Inventory Posting Setup

Buying groups require all invoices in a month to be due on the 20th of the following month (from the case study).
In BC, this is achieved by setting up Payment Terms = CM+20D (Current Month + 20 Days). Example:
Invoice on Sept 5 # due Oct 20.
Payment terms are assigned directly to the customer card, not to the posting group or price group.
Option E (D20) would set due date 20 days after invoice date, which is incorrect.
Assigning to Customer Posting Group or Price Group does not control due dates.
Correct: A and C