In SAP S/4HANA Cloud, the combination of multiple source documents into a single billing document is contingent on the homogeneity of key header-level data. The system will create separate billing documents (an invoice split) if these criteria differ. The Payer is the most fundamental criterion, as an invoice is a legal document issued to a specific legal entity responsible for payment. The Billing Date is equally critical as it determines the document's date for financial accounting and posting periods. Therefore, both the Payer and the Billing Date must be identical across all source documents to be consolidated into one billing document.

B. Ship-to party: The Ship-to party is an item-level partner function. A single invoice for one Payer can contain items delivered to multiple different Ship-to parties.

C. Incoterms: While different Incoterms are a standard criterion for a billing split, the Payer and Billing Date are more fundamental for partner and financial consolidation, making them the primary answers.

1. SAP S/4HANA Cloud

Public Edition - Help Portal

Sales -> Billing -> Billing Document Split and Combination:

"The system combines items from different documents in one billing document if their header data is identical. For example

the following header data must be identical:

Payer

Billing date

Destination country/region

Incoterms"

This official documentation explicitly lists both Payer and Billing date as mandatory identical fields for billing document combination.

2. SAP S/4HANA Cloud

Public Edition - Best Practices Explorer

Scope Item Convergent Billing (1MC):

The process flows for scope item 1MC rely on the standard billing engine's logic. The test script for creating a combined invoice implicitly requires selecting documents with matching header data

primarily the Payer and desired billing date

to ensure successful consolidation. The core combination logic is not altered by the convergent billing scenario itself.