16.3 Combined Shipments/Receipts & Prepayment Workflows

Key Takeaways

  • Combined invoicing consolidates multiple posted receipts or shipments for the same vendor or customer into a single purchase or sales invoice using the 'Get Receipt Lines' / 'Get Shipment Lines' functions or batch jobs.
  • For the 'Combine Shipments' batch job to group multiple shipments onto a single sales invoice, shipments must share identical Bill-to Customer, Currency, Payment Terms, and Tax/VAT configurations, and the customer must have 'Combine Shipments' enabled.
  • Invoices created from combined receipts or shipments maintain full audit traceability, recording original document numbers and line references while updating outstanding invoiced quantities on originating orders.
  • Prepayment processing allows organizations to invoice and collect advance deposits before order fulfillment, locking document shipment until required prepayment percentages are invoiced and paid.
  • Final invoice posting automatically deducts previously invoiced prepayments by reversing the Balance Sheet Prepayments account (Customer/Vendor Advances) and billing only the remaining net balance.
Last updated: September 2026

16.3 Combined Shipments/Receipts & Prepayment Workflows

Quick Summary: In high-volume distribution and procurement environments, generating an individual invoice for every delivery creates excessive administrative overhead. Microsoft Dynamics 365 Business Central addresses this through Combined Invoicing, allowing organizations to consolidate multiple uninvoiced Posted Purchase Receipts (via Get Receipt Lines) or Posted Sales Shipments (via Get Shipment Lines or the Combine Shipments batch job) into a single commercial invoice. For transactions requiring advance cash collection or upfront supplier deposits, Business Central provides an end-to-end Prepayment Workflow. By configuring Prepayment % rules across customers, vendors, or items, organizations can issue Prepayment Invoices to balance sheet advance accounts, hold order fulfillment until payment clears, and automatically deduct advance deposits when generating final billing statements.


Combined Purchase Invoicing: Get Receipt Lines

When a vendor delivers multiple partial orders or scheduled deliveries across a billing cycle (e.g., daily deliveries from an industrial supplier), accounts payable can aggregate all uninvoiced deliveries onto a single vendor invoice.

Combined Purchase Invoicing Process:

[PO 1001: 50 Units Received] ──► Posted Purchase Receipt 107001 (Table 121)
[PO 1002: 30 Units Received] ──► Posted Purchase Receipt 107002 (Table 121)
[PO 1003: 20 Units Received] ──► Posted Purchase Receipt 107003 (Table 121)
                                        │
                                        ▼ Create Empty Purchase Invoice (Page 51)
[Purchase Invoice: Vendor 20000] ◄──────┘ Select Lines -> Functions -> "Get Receipt Lines"
  ├── Line 1: 50 Units (Rcpt. 107001 / PO 1001)
  ├── Line 2: 30 Units (Rcpt. 107002 / PO 1002)
  └── Line 3: 20 Units (Rcpt. 107003 / PO 1003)
         │
         ▼ Post Invoice (F9)
[Financial Settlement & Order Update]
  - Single Vendor Ledger Entry created for $ Total
  - Updates Quantity Invoiced on all 3 original Purchase Orders
  - Fully invoiced orders automatically archive or delete

Execution Mechanics for Get Receipt Lines

  1. Create a new Purchase Invoice (Alt+Q -> type Purchase Invoices, Page 51), and specify the Buy-from Vendor No.
  2. In the Lines FastTab, select Functions -> Get Receipt Lines... (Page 5703).
  3. Business Central displays a filtered list of all posted purchase receipt lines for this vendor where Quantity Invoiced < Quantity Received.
  4. The user multi-selects the relevant lines and clicks OK.
  5. Business Central copies the lines onto the invoice. Each line retains a reference to the originating Receipt No. and Receipt Line No..
  6. Upon posting (F9), the system debits inventory/expense accounts, credits Accounts Payable, and updates Quantity Invoiced on each originating Purchase Order line.

[!NOTE] Organizations can automate consolidated vendor billing using the Combine Purchase Receipts batch report (Report 497), which scans all open receipt lines across vendors and compiles batch draft purchase invoices.


Combined Sales Invoicing: Combine Shipments Batch Job

To satisfy enterprise customers who demand weekly or monthly consolidated billing rather than individual invoices per parcel delivery, Business Central provides the Combine Shipments feature.

Combine Shipments Prerequisites & Execution:

[Customer Card: Page 21] ──► Shipping FastTab: "Combine Shipments = YES"
                                        │
  ┌─────────────────────────────────────┼─────────────────────────────────────┐
  ▼ Sales Order 1                       ▼ Sales Order 2                       ▼ Sales Order 3
[Shipment 102011]                     [Shipment 102012]                     [Shipment 102013]
  - Bill-to: 10000                      - Bill-to: 10000                      - Bill-to: 10000
  - Currency: USD                       - Currency: USD                       - Currency: USD
  - Payment Terms: NET30                - Payment Terms: NET30                - Payment Terms: NET30
  └─────────────────────────────────────┬─────────────────────────────────────┘
                                        │ Run Batch Job: "Combine Shipments" (Report 295)
                                        ▼
                     [Single Consolidated Sales Invoice]
                       - Bill-to Customer: 10000
                       - Contains Lines from Shipments 102011, 102012, 102013

Strict Header Matching Criteria for Combined Shipments

For the Combine Shipments batch job (Report 295) to successfully merge shipment lines into a single sales invoice, the source shipments must share identical commercial attributes:

  • Combine Shipments Toggle: The customer must have the Combine Shipments checkbox checked on the Customer Card (Shipping FastTab).
  • Bill-to Customer No.: Invoicing entity must be identical.
  • Currency Code: Shipments in different currencies cannot be merged.
  • Payment Terms Code & Payment Method Code: Settlement terms must match.
  • Tax Area Code / VAT Bus. Posting Group: Tax jurisdictions must align.
  • Dimension Combinations: Header-level dimensions must not conflict.

If any of these header attributes differ, Business Central automatically splits the lines and creates separate sales invoices.


Prepayment Processing Architecture

In custom manufacturing, high-value capital equipment, or risky customer accounts, companies often require an advance deposit before committing resources or shipping inventory. Business Central provides a dedicated Prepayment sub-system.

End-to-End Prepayment Lifecycle:

1. Configure Setup & Prepayment % (Customer, Vendor, Item, or Document Line)
                           │
                           ▼
2. Create Sales Order ($100,000 Total, Prepayment % = 40% -> $40,000 Prepayment)
                           │
                           ▼ Release Order -> Status = "Pending Prepayment"
3. Action: Post Prepayment Invoice (Codeunit 442)
     Debit: Accounts Receivable .............. $40,000
     Credit: Sales Prepayments (Liability) ... $40,000 (plus VAT/Tax)
                           │
                           ▼ Customer Pays Prepayment Deposit (Cash Receipt Journal)
4. Prepayment Paid = Yes -> Order Status = "Released"
                           │
                           ▼ Warehouse ships physical items to customer
5. Action: Post Final Sales Invoice (F9)
     Debit: Accounts Receivable (Net) ........ $60,000
     Debit: Sales Prepayments (Liability) ... $40,000  [Liquidated]
     Credit: Sales Revenue .................. $100,000 [Full Revenue Recognized]

General Ledger Configuration for Prepayments

Before processing prepayments, posting groups must be mapped to Balance Sheet advance accounts in General Posting Setup (Page 314):

  • Sales Prepayments Account: A Balance Sheet Liability account representing customer unearned revenue or advance deposits.
  • Purch. Prepayments Account: A Balance Sheet Asset account representing vendor prepaid inventory or supplier advance deposits.

Defining Prepayment Percentages

Prepayment percentages resolve through a hierarchical structure:

  1. Document Line Override: Manually entering a percentage in the Prepayment % field on an individual sales or purchase line.
  2. Item-Specific Terms: Configured on the Prepayment Percentages page (linked to Customer or Vendor Cards), defining specific percentages for high-cost items.
  3. Customer / Vendor Default: Entered in the Prepayment % field on the Customer Card (Payment Details FastTab) or Vendor Card.

Operational Prepayment Flow

  1. Order Staging: A Sales Order is created with items totaling $10,000 and a 30% prepayment requirement. The system calculates Prepmt. Line Amount = $3,000.
  2. Posting Prepayment Invoice: In the action bar, the user selects Posting -> Prepayment -> Post Prepayment Invoice... (Codeunit 442). Business Central posts a prepayment invoice, creating a customer ledger entry for $3,000 and crediting the Sales Prepayments Account.
  3. Fulfillment Enforcement: If Check Prepmt. when Posting is active in Sales & Receivables Setup, warehouse staff cannot post a shipment until the prepayment invoice is posted and paid.
  4. Final Invoice Posting: Once goods are shipped, posting the regular invoice (F9) recognizes full revenue ($10,000), automatically deducts the prepayment by inserting a negative line debiting the Sales Prepayments Account (-$3,000), and bills the customer for the remaining $7,000 balance.

Combined Documents vs. Prepayment Processing Comparison

Attribute / FeatureGet Receipt Lines (Purch)Combine Shipments (Sales)Prepayment Invoice Workflow
Primary Business GoalConsolidate AP supplier billsConsolidate AR customer billingSecure upfront financial deposits
Document GenerationPull lines into empty invoiceBatch report creates invoicesTriggered from order action bar
Balance Sheet ImpactNormal AP trade liabilityNormal AR trade receivableCustomer Advance (Liability) / Prepaid (Asset)
Revenue / COGS TimingRecognized upon invoice postRecognized upon invoice postDeferred until final invoice posting
Order Line TraceabilityPreserves Receipt No. on linePreserves Shipment No. on lineReferences originating Order No.

Step-by-Step UI Execution Workflows

Workflow A: Combining Multiple Sales Shipments via Batch Job

  1. Open Customer Card 10000 (Alt+Q -> Customers). On the Shipping FastTab, ensure Combine Shipments is set to Yes.
  2. Create and ship two separate Sales Orders for Customer 10000 on Location BLUE without invoicing (Post -> Ship). Note Posted Sales Shipment numbers 102040 and 102041.
  3. Press Alt+Q, type Combine Shipments, and select the batch job (Report 295).
  4. In the request page, set Posting Date to today's date, and enter 10000 in the Customer No. filter.
  5. Click OK. Business Central runs the batch job and creates a single consolidated draft Sales Invoice.
  6. Navigate to Sales Invoices (Alt+Q -> Sales Invoices), open the newly created invoice, and verify that lines from both shipments are present with traceable shipment references.
  7. Post the invoice (F9).

Workflow B: End-to-End Sales Order Prepayment Processing

  1. Create a new Sales Order for Customer 20000 (Alt+Q -> Sales Orders -> New).
  2. Add Item 1900-S, Quantity = 10, Unit Price = $100.00 (Total = $1,000.00).
  3. On the Prepayment FastTab, enter 40 in the Prepayment % field. Verify that Prepmt. Line Amount reflects $400.00.
  4. In the action bar, click Posting -> Prepayment -> Post Prepayment Invoice... (Codeunit 442). Click Yes to confirm.
  5. Notice the order status updates to Pending Prepayment. Business Central creates a Posted Sales Prepayment Invoice for $400.00.
  6. Register the customer's $400.00 payment in a Cash Receipt Journal and apply it to the prepayment invoice.
  7. On the Sales Order, post the physical shipment: Posting -> Post -> Ship.
  8. In the action bar, click Posting -> Post -> Invoice. Business Central posts the final invoice, recognizes $1,000.00 in revenue, reverses the $400.00 prepayment liability, and leaves an open receivable balance of $600.00.

Common Configuration Pitfalls & Exam Traps

  • Pitfall 1: Combine Shipments Splitting Invoices Unexpectedly. A frequent exam question asks why running Combine Shipments generated multiple invoices for a customer. The root cause is almost always mismatched header fields: differing Payment Terms Codes, Currencies, or Tax Area Codes.
  • Pitfall 2: Order Fulfillment Blocked by Prepayments. If Check Prepmt. when Posting is enabled in Sales & Receivables Setup, warehouse users attempting to ship an order will receive an error if the prepayment invoice has not been posted and paid.
  • Pitfall 3: Missing Prepayment Account in General Posting Setup. Attempting to post a prepayment invoice without defining the Sales Prepayments Account or Purch. Prepayments Account for the relevant Gen. Bus. / Gen. Prod. posting group combination triggers an immediate posting block.
  • Pitfall 4: Attempting Undo Shipment After Combined Invoicing. Once a posted shipment line has been pulled into a combined invoice and posted, the Undo Shipment function on the Posted Sales Shipment is permanently disabled because Quantity Invoiced is greater than zero.
Loading diagram...
Combined Invoicing Consolidation & Prepayment Financial Posting Cycle
Test Your Knowledge

A warehouse ships three separate sales orders to customer 10000 across Monday, Tuesday, and Wednesday. On Friday, the billing clerk runs the 'Combine Shipments' batch job (Report 295) to generate a single consolidated sales invoice. However, the batch job produces two separate sales invoices instead of one. Which customer or order attribute mismatch caused Business Central to split the shipments into multiple invoices?

A
B
C
D
Test Your Knowledge

An industrial manufacturer requires a 40% advance deposit before beginning production of custom machinery on Sales Order SO-5001 (total value $100,000). The sales administrator sets Prepayment % to 40% and chooses 'Post Prepayment Invoice'. Which General Ledger entries and balance sheet impacts occur upon posting this prepayment invoice?

A
B
C
D
Test Your Knowledge

A sales order for $50,000 had a 20% prepayment ($10,000) successfully invoiced and paid by the customer. The goods are subsequently shipped to the customer. When the accounting clerk posts the final Sales Invoice (Post -> Invoice) for the entire order, how does Business Central handle the previous prepayment on the final invoice document and in the General Ledger?

A
B
C
D