Using the Contract Account

Objectives

After completing this lesson, you will be able to:
  • Describe the Contract Account
  • Describe Master Data in BRIM

Contract Account

Diagram explaining a Contract Account, highlighting its role in storing financial data for long-term business relationships and influencing various processes, with examples including payment terms, credit card payments, SEPA mandates, and additional field assignments.

The Contract account is used to store controlling data for long-term business relationships with a business partner. The data contained in a contract account influences the processes in invoicing, contract account and receivable and payable, taxation, and corresponding processes. In the case of business transactions to a contract account, invoicing documents for the subscription contract, as an example, are submitted to the active Contract Accounts Receivable and Payable (FI-CA). When processing a business transaction, such as a subscription order or subscription contract, you can make sure the system determines a suitable contract account.

Diagram showing the distribution of contract account data from SAP S/4HANA to SAP Convergent Charging, including general data, invoices, refunds, payments, correspondence, dunning, and tax settings.

In SAP S/4HANA, only the contract account is used both in FI-CA and in Subscription Order Management (SOM). Business agreements are no longer required and, therefore, no longer available.

Diagram showing the relationship between a Business Partner, multiple Contract Accounts, and their associated Contracts and Items. Highlights include multiple contract accounts per business partner, single contract account usage in multiple provider contracts, and item-level usage of n-contract accounts.

A business partner can be assigned to more than one contract account to store different payment information for different use cases. For each item in a subscription order or contract, a different contract account related to the business partner can be assigned.

Master Data in SAP Billing and Revenue Innovation Management

Flowchart illustrating the creation and replication of master data in SAP S/4HANA, showing interactions between SD, SOM, MM, FI-CA, and Convergent Charging modules via web services. Key elements include price conditions, bundle products, subscription products, business partners, material types, contract accounts, and provider contracts.

Several master data objects are replicated between SAP S/4HANA and SAP Convergent Charging. Similarly, invoice products for rate plans or fees, for example, Cloud Selection Service can be exchanged between these systems.

In addition to that, the following Subscription Order Management (SOM) objects can be replicated to Contract Accounts Payable and Receivable (FI-CA) of SAP S/4HANA and SAP CC:

  • Business Partner, called subscriber accounts in SAP CC
  • Contract Account in FI-CA called external accounts in SAP CC

The subscription contract created for the IT department is replicated uni-directional from SAP SOM to FI-CA of SAP S/4HANA and to SAP CC. The contract is sent to the common object layer in FI-CA, from where the contract generation in SAP FI-CA itself, as well as in SAP CC, is triggered. Only in the case where the contract can be stored in both systems, will the contract be created.

On the SAP CC site, each provider contract is linked to the corresponding charge plans defined in the Cross Catalog Mapping.

Change Business Partner and Contract Account Master Data

Log in to track your progress & complete quizzes