Explanation:
Scenario: The item may be transferred between locations.
Item type: Inventory
Scenario: The item can be used in assembly consumption, but the quantity is not tracked.
Item type: Non-Inventory
Scenario: Item will be used in sales transactions.
Item type: Service
In Dynamics 365 Business Central, the Item Type determines how an item behaves in inventory, assembly, and sales:
* Inventory
* Tracks stock quantities and values.
* Inventory items can be purchased, sold, consumed in production, and transferred between locations.
* Correct for: "The item may be transferred between locations."
* Non-Inventory
* Does not track quantities in stock, but can still be used in assembly or job consumption and purchasing/sales documents.
* Correct for: "The item can be used in assembly consumption, but the quantity is not tracked."
* Service
* Represents services offered to customers.
* Used in sales transactions but cannot be transferred or stocked.
* Correct for: "Item will be used in sales transactions."
* All
* Not an item type, but a filter option when viewing item records.
References
* Microsoft Learn: Work with Item Types
Final Mapping
* Transfer between locations # Inventory
* Assembly consumption without tracking # Non-Inventory
* Sales transactions # Service

Explanation:

Comprehensive Detailed Explanation
The scenario: The company receives deliveries during the week and then a consolidated vendor invoice at week's end. In Dynamics 365 Business Central, the correct procedure is:
Step 1. From the purchase order, post receipts for the items
Each delivery is recorded as a purchase receipt against the purchase order. This ensures inventory is updated as soon as items are received.
Reference: Receive Items - Business Central
Step 2. Create a new purchase invoice and use the Get Receipt Lines action When the weekly invoice arrives, create a standalone purchase invoice.
Use Get Receipt Lines to pull in all outstanding receipts for that vendor. This consolidates multiple receipts into one invoice.
Reference: Work with Purchase Invoices - Business Central
Step 3. Adjust purchase invoice lines if needed
Users can update quantities, unit costs, or discounts to reflect the actual vendor invoice.
Step 4. Post the purchase invoice
This records the vendor liability in Accounts Payable and finalizes the invoice posting.
Step 5. Delete fully invoiced purchase orders
Once purchase orders are fully received and invoiced, they can be deleted (or automatically closed) to keep the system tidy.

The requirement is:
"You need to configure the system to post to the receivables account for wholesale customers." From the case study, the G/L posting accounts required are:
* Retail Receivables = 13100
* Wholesale Receivables = 13200
In Business Central:
* Customer Posting Groups (B)
* Customer Posting Groups are used to map customers to specific Receivables G/L accounts.
* You typically create separate posting groups, e.g., "RETAIL" and "WHOLESALE," and assign them to customers based on type.
* This ensures postings go to the correct control account.
* Receivables account 13200 (D)
* For wholesale customers, the posting group must be configured to point to 13200 (Wholesale Receivables).
Why not the others?
* A. Receivables account 13100 - This is for retail customers, not wholesale.
* C. General Posting Setup - This setup manages how transactions post based on combinations of General Business Posting Groups and General Product Posting Groups, but it does not control receivables accounts.
* E. General Business Posting Groups - These are used for revenue, COGS, and VAT postings, not receivables control accounts.
Microsoft Learn references
* Posting Groups in Business Central
* Set Up Customer Posting Groups

To ensure timely payments:
* You can assign a Priority value to vendors (lower value = higher priority).
* When running Suggest Vendor Payments, the system considers vendor priority to decide which payments to suggest first.
* Setting the vendor's priority to 1 (highest priority) ensures this vendor's payments are included early, helping avoid late payments.
Why not the others:
* A & E (Priority 0): 0 is not valid; priority starts at 1.
* B (Enable Late Payment Predictions): Useful for forecasting, but it doesn't enforce actual payment scheduling.
* D (Apply to Oldest): Relates to how payments are applied to invoices, not ensuring timely payments.
Reference:Pay Vendors

Explanation:
Create a shipment document for every item sale # Sales & Receivables Setup Store PDF files of sales invoices and credit memos automatically at the end of each day # Document Sending Profiles Comprehensive Detailed Explanation
* Create a shipment document for every item sale # Sales & Receivables Setup
* In Sales & Receivables Setup, you can configure whether the system automatically creates shipment documents when posting sales orders.
* The field Shipment on Invoice and related posting behaviors are controlled here.
* No. Series only controls numbering, not whether shipment documents are created.
* Store PDF files of sales invoices and credit memos automatically at the end of each day # Document Sending Profiles
* Document Sending Profiles allow you to define how documents such as invoices and credit memos are sent, archived, or stored.
* You can configure the system to automatically generate and store PDF copies of posted sales documents for each customer.
Other options not correct:
* General Ledger Setup # Controls accounting periods, posting settings.
* Inventory Setup # Defines inventory posting and costing, not document sending or shipments.
Microsoft Learn References
* Set Up Sales & Receivables
* Set Up Document Sending Profiles