Setting up a Master Agreement with complex, cross-contract discounting in SAP BRIM is a multi-step process involving different components. First, in Subscription Order Management, individual subscription contracts must be created with a direct reference to the overarching Master Agreement. This establishes the necessary hierarchical link. Second, the actual discounting logic is configured within Convergent Invoicing. A discount agreement is created in Convergent Invoicing and assigned to the Master Agreement. During the invoicing run, the system aggregates the billable items from all linked subscription contracts and applies the conditions defined in this discount agreement.

A. Rate consumption with reference to master agreement: Rating in Convergent Charging is executed based on the charge plan of the individual provider contract, not directly against the master agreement.

C. Create discount agreement for master agreement in subscription order management: The execution of complex, cross-contract discount agreements is a core function of Convergent Invoicing, not Subscription Order Management, which is used for order capture and contract creation.

1. SAP S/4HANA Help Portal, Convergent Invoicing -> Master Agreements in Convergent Invoicing: "You can use master agreements to group contracts for invoicing and for applying discounts across multiple contracts... You create master agreements in a CRM system and replicate them to SAP Convergent Invoicing." This document confirms that the master agreement is created in the CRM/SOM system and used in CI for cross-contract functions.

2. SAP S/4HANA Help Portal, Convergent Invoicing -> Discount and Surcharge Agreements: "You can assign discount and surcharge agreements to master agreements. The system then applies the discounts and surcharges to all billable items that belong to contracts that are assigned to the master agreement." This directly supports that the discount agreement is created and assigned in Convergent Invoicing (Option B).

3. SAP S/4HANA Help Portal, Subscription Order Management -> Master Agreement: "A master agreement is a long-term agreement with a business partner that defines the general terms and conditions for all associated contracts... You can assign a master agreement to a subscription order or a solution quotation." This confirms that individual contracts are created with a reference to the master agreement in SOM (Option D).

In SAP BRIM, the partner settlement process is intrinsically linked to the customer process through both master data and transactional data. First, at the master data level, a customer's provider contract must be explicitly connected to a partner agreement. This assignment ensures that any consumption under that contract is flagged for partner settlement. Second, during the transactional process in Convergent Invoicing, when a billable item is generated for the customer's consumption, the system uses the contract's partner link to trigger the creation of a corresponding partner billable item. This new item contains a reference to the original customer billable item, creating a direct, traceable link between the customer revenue and the partner's share.

A. Convergent Charging links customer consumption items with partner consumption items.

Convergent Charging processes source consumption data to create charged items for various parties, but the explicit link for the settlement process is established in Convergent Invoicing through billable item references.

B. Partner settlement rule controls risk assessment to a third party.

Partner settlement rules define the calculation logic for revenue sharing (e.g., percentages, fees). Risk assessment is a separate function typically managed by SAP Credit Management within FI-CA.

---

1. SAP Help Portal, SAP S/4HANA (2020), Convergent Invoicing, Partner Settlement, Process Flow:

This official documentation states, "Based on the billable items of your customers, the system creates billable items for partner settlement." This directly supports the creation of partner billable items with reference to customer billable items (Answer C). The reference is essential for traceability in this "based on" process.

2. SAP Help Portal, SAP S/4HANA (2020), Convergent Invoicing, Partner Settlement, Prerequisites:

The documentation lists as a prerequisite: "You have entered the business partner, with whom you want to settle shares, in the provider contracts of your customers." This confirms that the customer contract must be connected to the partner, establishing the master data link (Answer D).

3. SAP Learning Journey, BR235 - SAP Convergent Invoicing, Unit: Partner Settlement:

Course materials for the CBRU2C2020 certification explicitly detail that the partner is assigned at the provider contract item level. They also illustrate the process flow where customer billable items are the source for generating partner settlement billable items within Convergent Invoicing, establishing the transactional link.

A billable item in SAP Convergent Invoicing is an enriched, business-ready object prepared for the invoicing process. It contains crucial accounting and organizational context that is not present in a standard rated consumption item generated by a rating engine like SAP Convergent Charging. This added information includes the Contract Account (to identify the business partner to be billed), main transactions (to control financial posting), and organizational data (such as the company code for financial reporting). A rated consumption item primarily contains the calculated monetary value (price and currency) for a service usage event but lacks this specific FI-CA business context, which is added during its transfer to the billing system.

B. Currency: A rated consumption item, by definition, has a monetary value calculated by the rating engine, which inherently includes a currency.

D. Price for event: The primary purpose of rating a consumption item is to calculate its price; therefore, this information is fundamental to a rated item.

1. SAP S/4HANA Documentation, "Convergent Invoicing -> Billable Item Management -> Billable Items -> Structure of a Billable Item": This official documentation outlines the standard fields of a billable item. It explicitly lists "Contract Account", "Company Code" (as part of Organizational Data), and "Main Transaction and Subtransaction" as key components of the structure, which are required for processing in Contract Accounts Receivable and Payable (FI-CA).

2. SAP S/4HANA Documentation, "Convergent Invoicing -> Integration -> Transferring Billable Items": This section details the process where data from external systems is transferred to Convergent Invoicing. It explains that during this process, the system enriches the incoming data (like rated items) with FI-CA specific information, such as the contract account and posting parameters (main/sub-transactions), to create a complete billable item. This confirms that these details are added at the billable item stage, not the rated item stage.

A master agreement in SAP Billing and Revenue Innovation Management (BRIM) serves as an umbrella contract that consolidates multiple individual provider contracts for a single business partner. Its core functionalities, primarily managed within SAP Convergent Invoicing, include creating a single, consolidated invoice that covers all linked contracts. Furthermore, it enables the application of cross-contract conditions, such as granting discounts or applying surcharges based on the aggregated consumption or charges from all underlying contracts. These two functions, consolidated invoicing and cross-contract discounting, are central processes directly related to the master agreement.

C. Partner settlement: This is a distinct business process for managing financial settlements with sales or service partners, which is not a primary function of a customer-facing master agreement.

D. Revenue recognition: This is a subsequent financial accounting process handled in the general ledger, governed by accounting standards. The master agreement provides input but does not execute the process itself.

1. SAP Help Portal, SAP S/4HANA (2020), Convergent Invoicing -> Master Agreement: "You can use master agreements to create a single invoice for a business partner for different contracts... You can also use master agreements to grant discounts and apply charges across contracts." This source directly confirms that invoice creation and discounting are key processes.

2. SAP Help Portal, SAP S/4HANA (2020), Functions in Invoicing -> Invoicing of Master Agreements: "The system can group the invoicing documents of the individual accounts of a master agreement in a new, collective invoicing document for the master agreement." This statement explicitly supports the invoice creation (consolidated invoicing) capability.

3. SAP Help Portal, SAP S/4HANA (2020), Partner Settlement: This section describes partner settlement as a separate component for managing remuneration for partners, distinct from the customer-centric master agreement functionality.

In SAP Contract Accounts Receivable and Payable (FI-CA), which manages receivables for SAP BRIM, clearing rules are configured using clearing control. This control is defined by clearing variants, which specify how incoming payments are matched against open receivables. The main transaction and sub-transaction are fundamental attributes of an FI-CA document that classify the business transaction. By assigning different main/sub-transactions to receivables originating from different products, you can configure a clearing variant to specifically group and sort these items, thereby prioritizing them during the clearing process. This is the standard mechanism for implementing differentiated clearing logic based on the nature of the receivable.

A. Cost center: This is a Controlling (CO) object used for internal cost management and reporting; it does not influence external customer payment clearing rules in FI-CA.

B. Product: The product is the basis for the rule, but the rule itself is not defined within the product master data. The product information is used to derive the main/sub-transaction.

C. General ledger account: This is a Financial Accounting (FI) object for posting and reporting. While FI-CA items post to G/L reconciliation accounts, the account itself does not define clearing logic.

1. SAP S/4HANA - Official Vendor Documentation: In the section on Clearing Control, the system for defining clearing rules is detailed. It states, "You define the rules for clearing in a clearing variant... For each clearing step, you can define rules for grouping and sorting the items." The available fields for sorting and grouping explicitly include Main Transaction (VTREF) and Subtransaction (VTRE2).

Source: SAP Help Portal, SAP S/4HANA, Contract Accounts Receivable and Payable (FI-CA) -> Clearing -> Clearing Control -> Clearing Variant.

2. SAP S/4HANA - Official Vendor Documentation: The documentation on business transactions explains the role of main and sub-transactions. "Every posting in Contract Accounts Receivable and Payable is based on a transaction... The main and sub-transactions are the key for controlling business transactions." This control extends to dunning, interest calculation, and clearing.

Source: SAP Help Portal, SAP S/4HANA, Contract Accounts Receivable and Payable (FI-CA) -> Basic Functions -> Postings and Documents -> Basic Settings -> Main and Subtransactions.

In SAP Convergent Charging (CC), a Billable Item Mapping is a design-time object used to transform the results of the rating process into a format understandable by a downstream billing system, such as SAP Convergent Invoicing (CI). The rating process within a charge produces Charged Items (runtime data). The structure of these Charged Items is defined by a Charged Item Class, which is a design-time template automatically generated by SAP CC when a charge is configured. The Billable Item Mapping explicitly uses this Charged Item Class as its source to map fields to the target Billable Item Class in the external system.

A. Charged item: This is a runtime transactional data object created during the rating process, not a design-time configuration object.

B. Billable item: This is a runtime data object created in the target billing system (e.g., SAP CI), not an object created within SAP CC's design environment.

D. Chargeable item class: This design-time object defines the structure of the input data for the rating process, not the rated output that is mapped for billing.

1. SAP Help Portal, SAP Convergent Charging 2020, Application Help: In the section on Billable Item Mapping, the documentation states, "A billable item mapping describes the mapping between the fields of a charged item class in SAP Convergent Charging and the fields of a billable item class in the connected SAP system." This directly links the creation of the mapping to the Charged Item Class.

Source: SAP Help Portal, SAP Convergent Charging 2020 FPS 1 > Application Help > Integrating with an External System > Billable Item Management > Billable Item Mapping.

2. SAP Help Portal, SAP Convergent Charging 2020, Application Help: The documentation for Charged Item Classes clarifies their origin: "SAP CC automatically generates a charged item class when you set up the generation of charged items in a charge." This confirms it is a design-time object created within CC as part of the charge configuration process, which precedes or is concurrent with the mapping creation.

Source: SAP Help Portal, SAP Convergent Charging 2020 FPS 1 > Application Help > Chargeable Item Charging > Charged Items > Charged Item Classes.

A bank transfer, specifically a credit transfer where a customer initiates the payment (a "push" transaction), is considered final and settled once the funds are received in the beneficiary's bank account. Unlike other methods, there is no standard, automated process for a "return" due to issues like non-sufficient funds. While reversals are theoretically possible in rare cases like fraud, they are exceptional, manual processes, not a routine part of payment processing. SAP's automated returns handling (e.g., return lots in FI-CA) is designed for payment methods like checks, direct debits, and credit cards, which can be dishonored or charged back after initial processing.

A. Checks: Checks can be dishonored and returned by the bank for various reasons, most commonly for non-sufficient funds (NSF). This is a standard "return" event.

B. Credit card collections: These are subject to chargebacks, where a cardholder disputes a transaction with their issuing bank, resulting in the reversal (return) of the payment.

D. Debit memos: A debit memo is a billing document that increases a customer's debt, not a payment method. Payments made against it (e.g., by direct debit) can be returned.

1. SAP Help Portal for SAP S/4HANA, Contract Accounts Receivable and Payable (FI-CA), Business Transactions -> Payments -> Processing Incoming and Outgoing Payments -> Returns: The official documentation outlines the returns process. It states, "You can process returns for incoming payments by check, direct debit, debit memo, or credit card." This explicitly confirms that returns are a standard process for options A, B, and D (interpreting "debit memo" as a payment made via direct debit against a debit memo document), while notably omitting incoming bank transfers.

2. SAP Learning Hub, Course BR235 - Convergent Invoicing in SAP S/4HANA, Unit 6: Payments, Dunning, and Collections: This courseware explains the different payment scenarios in Contract Accounts Receivable and Payable (FI-CA). It distinguishes between payment methods where the company initiates the collection (e.g., direct debit, credit card) which are subject to returns, and payments initiated by the customer (e.g., bank transfer), which are processed as cleared funds upon receipt via electronic bank statement, with no standard return mechanism.

3. SAP Press (2021), SAP Billing and Revenue Innovation Management: Functionality and Configuration, Section 5.3.4 Returns: This section details the returns management process within SAP BRIM. The examples and configuration steps provided focus exclusively on reversible payment methods such as direct debits, checks, and credit card chargebacks, reinforcing that incoming bank/wire transfers are not subject to this automated process.

A master agreement in SAP Convergent Invoicing serves as a central point of control for a group of subordinate agreements belonging to a business partner. Its primary purpose is to standardize and consolidate billing and invoicing activities. This is achieved by assigning specific functional agreements:

1. Billing Agreement (D): This is assigned to a master agreement to enforce a common set of rules for the creation of billing documents across all included sub-agreements.

2. Invoice Agreement (C): This is assigned to ensure that all billing documents generated for the grouped agreements are consolidated into a single, collective invoice.

These two agreements directly implement the core centralizing functions of a master agreement.

A. Discount Agreement: "Discount Agreement" is not a standard, assignable object type within the SAP Convergent Invoicing master agreement framework. Discounts are typically managed in other components like Convergent Charging or provider contracts.

B. Business Agreement: While a master agreement (which is a special type of business agreement) can have other business agreements assigned to it to form a hierarchy, the billing and invoice agreements are the specific functional objects that control the core processes, making them the more precise answers.

1. SAP S/4HANA Help Portal, Convergent Invoicing, "Master Agreements": The documentation explicitly states, "You can use master agreements to group agreements (such as billing agreements or invoice agreements) of a business partner." It further details that you can assign billing agreements to apply central specifications for billing and assign invoice agreements for collective invoicing.

2. SAP Training Course BR235 (SAP Billing and Revenue Innovation Management - Convergent Invoicing): The unit titled "Invoicing" and the lesson "Using Master Agreements" describe the process of assigning both billing agreements and invoice agreements to a master agreement to control the billing and invoicing processes for a group of contracts or subordinate business agreements.

A charged item class in SAP Convergent Charging defines the data structure for the output generated by the charging process. It specifies the set of properties (fields, data types, and descriptions) that will be included in a charged item. This structure serves as a template for the data records that are sent to downstream systems, such as SAP Convergent Invoicing (CI), for billing purposes. Essentially, it dictates the format and content of the output data resulting from a rating and charging operation.

A. The validity period of a charge: The validity period is defined within the pricing components of a charge plan (e.g., price tables, mapping tables), not by the charged item class.

C. The frequency with which items are transferred downstream: Transfer frequency is managed by technical settings and scheduled jobs for data replication, not by the data structure definition of a charged item class.

D. The scope of a charge: The scope of a charge, including which services or events it applies to, is determined by the logic and parameters configured within the charge plan itself.

---

1. SAP Help Portal, SAP Convergent Charging 2020 FPS 02, "Charged Item Classes": "A charged item class describes the structure of charged items that are generated by the charging process and that are to be transferred to a third-party system (SAP Convergent Invoicing, for example). A charged item class is a list of properties (or fields) that define the information available in a charged item."

2. SAP Help Portal, SAP Convergent Charging 2020 FPS 02, "Core Tool > Creating Charged Item Classes": This section details the process of defining the properties (fields) that constitute the structure of the charged item. It states, "You create and configure a charged item class in the Core Tool user interface. You define the properties of the charged items that belong to this class." This confirms the class defines the output structure.

Consumption items are the representation of rated usage data within SAP Convergent Invoicing (CI), created from charged items sent by SAP Convergent Charging (CC).

The rerating process, triggered in CI, is used to recalculate charges for past usage due to events like price corrections. This process explicitly requires reversing the original consumption items and creating new ones based on the re-evaluated charges.

Preaggregation is a performance optimization function within CI that groups multiple consumption items into a single aggregated item before the final billing document is created. This process, by its very definition, operates on a set of existing consumption items.

A. The rating process in Convergent Charging creates charged items from raw usage data. These charged items are then sent to Convergent Invoicing to become consumption items; the rating process itself does not use them.

D. Billing plans are used for recurring or periodic charges (e.g., subscriptions). They typically generate billable items directly in Convergent Invoicing, not consumption items, which are specifically for usage-based charges.

1. SAP Help Portal, SAP S/4HANA, Rerating and Reversal in Convergent Invoicing: "The system reverses the consumption items that are affected by the rerating and creates new consumption items based on the charged items that are transferred again from SAP Convergent Charging." This confirms that the rerating process fundamentally operates on consumption items. (Accessed under the Convergent Invoicing section for SAP S/4HANA 2020).

2. SAP Help Portal, SAP S/4HANA, Aggregation of Consumption Items: "In invoicing, you can group consumption items before billing... The system summarizes the consumption items based on grouping variants that you define in Customizing." This document explicitly states that the preaggregation process groups consumption items. (Accessed under the Convergent Invoicing -> Billing -> Aggregation of Billable Items section for SAP S/4HANA 2020).

3. SAP Learning Hub, Course BR235 - SAP Convergent Invoicing: Unit 3, Lesson: "Explain the Structure and Source of Billable Items". This course material distinguishes between different sources of billable items. It clarifies that consumption items originate from an external rating system (like CC), while recurring charges from billing plans are another source, generating standard billable items directly.