Describing Concepts of Billing in Contract Accounts Receivable and Payable

Objectives

After completing this lesson, you will be able to:
  • Understand the billing process and billing subprocess
  • Identify the key elements of billable items, such as the source transaction code and billable item type

Billing in Contract Accounts Receivable and Payable

Lesson Overview

At the conclusion of this lesson, you will be able to understand the basic concept of billing in contract accounts receivable and payable.

Business Example

There are two different groups of billable items, from a business perspective, in two different divisions. These are Print Services and Internet Sales. These two groups require different billing frequencies, selected based on different criteria, grouped into billing units, and processed into separate billing documents. You achieve this by assigning each group to its own separate billing subprocess.

Then you can process both billing subprocesses together in one billing process or in separate billing processes.

Billing in Contract Accounts Receivable and Payable

Relation between Billing Process and Billing Subprocess.

Defining the billing process and billing subprocess

To execute billing, you must have defined at least one billing process with an assigned subprocess. A subprocess is a self-contained processing operation within a billing process. It is used to select and group billable items and form a billing document.

If possible the rating system determines the subprocess. Otherwise the subprocess needs to be derived out of rating fields in SAP Convergent Invoicing with loading into the BIT Class.

In case of test data billable items are assigned to a subprocess, if they are created.

The system cannot process them together with billable items of another subprocess in a common billing document.

A subprocess in billing controls the selection of the billing worklist, the grouping of billable items into billing units, and the specification of the billing type.

Therefore, the focus of the billing process lesson is to analyze the billing subprocess.

Example Telecommunication Overview for Billing Subprocess Data and Telecommunication Overview

The billing subprocess steps are listed below:

Data selection

During data selection, the system selects the billable items for the billing process.

You define the selection criteria for the data selection in selection variants for the billing process.

Grouping into billing units

The system groups the selected billable items together into billing units for each contract account. Multiple billing units can be created for each contract account.

Billing in contract accounts receivable and payable creates one billing document for each billing unit.

You define the criteria that are used to create the billing units in grouping variants for the billing process.

Aggregation of billable items

The system includes the selected billable items of a billing unit in the billing document. More so, the billable items are summarized in billing document items. The individual items that belong to this summarization are linked with the billing document item.

Update

The system writes the billing document created for the billing unit and the individual billed items to the database, and at the same time deletes the processed billable items.

Relation between Billable Item Classes and Billable Item types.

Business Example

In the company Print Service Corporation, data load & telecommunication services should be billed together with the same frequency.

Billable item types DATA1 and TEL1 are used for monthly charges and are summarized into one billing document. Billable item types DAT2 and TEL2 are used for usage charges, and are summarized in another billing document.

The subprocess in the example is called BSDA Billing Subprocess Printing.

The billing subprocess, together with the billable item type, specifies the business significance of an individual billable item. Each billing subprocess is assigned to one or more activated billable item classes at client level.

You can create new subprocesses in customizing for contract accounts receivable and payable under Financial AccountingContract Accounts Receivable and PayableConvergent InvoicingBasic FunctionsBillable ItemsBillable Item ManagementDefine Subprocesses of Billing.

Key Elements of Billing Items

Explanation of the Source transaction, which is a combination of source transaction ID and the source transaction type.

Business Example

One print represents one source transaction ID. If the legacy rating and charging system cuts the call in two parts for rating purposes, because it starts on one day and ends the next day, you can summarize it by combining the same source transaction ID together to form one billing document item.

A source transaction is defined by the combination of a source transaction type and a source transaction ID.

A source transaction represents a group of billable items that belong together from a business viewpoint. In the standard system, further processing of billable items is always controlled by the source transaction, that is, by each combination of a source transaction ID and source transaction type. A source transaction can include billable items belonging to different record types.

The source transaction ID represents an external document number, and is used to group billable items that belong together in a source transaction. The individual billable items represent the external document items.

The source transaction type specifies the business meaning of the source transaction ID, both from the perspective of billing and from the perspective of the external system. It also defines rules for how the source transaction ID and the source transaction are interpreted in follow-on processes.

You can make the necessary settings in customizing for contract accounts receivable and payable under Financial AccountingContract Accounts Receivable and PayableConvergent InvoicingBasic FunctionsBillable ItemsBillable Item ManagementMake Settings for Source Transaction Types.

Explanation of key elements of a billable item.

Keys

  • VKONT – Contract Account
  • Source Trans Type – Source Transaction Type
  • Source Trans ID – Source Transaction ID
  • Subprocess – Billing Subprocess
  • BIT Class – Billable Item Class
  • BIT Type – Billable Item Type

If billable items are assigned to a billable item class for which the interface component Assignment of External/Internal Account Assignment or Receivable/Payables (Reduced interface) is active organizational data and main- and subtransactions are derived with subprocess, billable Item type and optional external keys in Convergent Invoicing posting areas 8120 and 8121.

Billable Items are enriched in Posting Area 8120 with organizational data as there is Company Code, Division, Business area, segment and Profit center.

When billable items are transferred to the SAP system from an external system, there is no guarantee that they have the values for main- and subtransactions that are recognized in the SAP system, therefor they can derived in posting area 8121.

Visualization of how the account assignment derivation takes place.

Summarization of Billable Items

  • The aim of the billing process is to summarize billable items with same key elements into billing document items, to reduce the amount of billable items and sort them according to the invoicing process criteria.
  • You can summarize billable items with different company codes, different billable item classes, or different billable item types into one billing unit.
  • One criterion for the aggregation of billable item types is the same source transaction type.
  • If the source transaction concept is not enough, aggregation criteria can also defined in customer-specific fields that can be added to the billable item class in Z-fields.

Log in to track your progress & complete quizzes