Identifying Invoicing Core Features

Recommended chapters are:

• Unit 5 - Invoicing Process
• Unit 6 - Invoice Functions
• Unit 9 - Invoice Printing

The invoicing function describes a task that is supported in invoicing:

• Automatic Account Maintenance
• Manual Account Maintenance (Dialog Call)
• Activation of Open Items
• Integration in BW Sales Statistics
• Charges and Discounts
• Debit Entry of Statistical Documents
• Dunning Proposal
• Calculation of Interest on Open Items
• Invoicing of Billing Documents
• Creation of Collective Invoicing Printout
• Invoicing of SD Documents

Invoicing consists of several processing steps. These processing steps may be complete business transactions and are known as invoicing functions.

In the definition of an invoicing process, you define which invoicing functions are to be performed.

This offers several advantages:

• The invoicing functions selected show which invoicing processing steps are performed in an invoicing process.
• Without any negative effect on the runtime, the invoicing program recognizes invoicing functions that are not required and does not perform them.
• You can use a multilevel control to activate or deactivate invoicing functions that are not required in all cases.

The invoicing program defines the order in which the invoicing functions are performed.

The invoicing process flow depends on the following parameters:

• Invoicing process
• Invoicing type
• Invoicing category

This multi-level control enables you to run invoicing according to your requirements.

The criteria specified above are determined as follows during the processing of each contract account: The user specifies the invoicing process explicitly when starting invoicing. The main task of the process is to define which categories of source documents are to be processed. It also defines the process flow for the invoicing functions. There is a differentiation between mandatory and optional invoicing functions.

Each invoicing process proposes an invoicing type. You can override the invoicing type in event 2603. The invoicing type enables you to react individually to the composition and the properties of the invoicing unit. It also defines, for each invoicing unit, which optional invoicing functions are performed.

At the master data level, you can influence the invoicing process flow using the invoicing category; this is transferred from the contract account.

In the realms of billing and invoicing, various documents are updated as follows:

Documents and line items from PSCD that are either posted or processed during invoicing are associated with the invoicing document through a unique reference table named DFKKINVDOC_P. This linkage also incorporates a reference document type that conveys the business and internal invoicing implications of these posting documents and line items.

The reference document types in use are consolidated in the value table TFK2605.

During the invoicing process, various source documents (such as billing documents, SD documents, and so on) are associated with the invoicing document using a unique reference table named DFKKINVDOC_S. Additionally, this reference is tagged with a reference document type, SRCDOCTYPE, which characterizes the specific type of source document. This system allows for easy identification of the invoices generated based on a particular billing document.

Every source document has an associated invoicing and reversal history. Notably, each source document can have at most one invoicing document that hasn't been reversed.

This multi-level control enables you to run Invoicing according to your requirements. The criteria specified above are determined as follows during the processing of each contract account:

• The user specifies the invoicing process explicitly when starting Invoicing. The main task of the process is to define which categories of source documents are to be processed. It also defines the process flow for the invoicing functions. There is a differentiation between mandatory and optional invoicing functions.
• Each invoicing process proposes an invoicing type. You can override the invoicing type in event 2603. The invoicing type enables you to react individually to the composition and the properties of the invoicing unit. It also defines, for each invoicing unit, which optional invoicing functions are performed.
• At the master data level, you can influence the invoicing process flow using the invoicing category; this is transferred from the contract account.

As standard, to determine the due date, invoicing runs event 1330 of Contract Accounts Receivable and Payable (PSCD). The due date determined in event 1330 and, if applicable, the due date for cash discount and the related cash discount percentage specification are transferred to all new posting items created for the invoicing document and to the invoicing document header as the invoice due date. At event 1330, the final invoice amount is not yet known.

In addition, event 2640 is available in invoicing. With this event, after the determination of the final invoice amount, you can check the due date originally determined (and change it if necessary) after integrated account maintenance and the creation of subitems.

By default, to determine the due date, invoicing triggers event 1330. The due date determined in event 1330, and, if relevant, the cash discount's due date along with the corresponding cash discount percentage, are relayed to all the freshly generated posting items for the invoicing document as well as the invoicing document header under the invoice due date. Notably, during event 1330, the final invoice sum remains undetermined.

Furthermore, invoicing offers event 2640. Utilizing this event, once the definitive invoice amount is discerned, you can examine (and modify if needed) the originally established due date following integrated account upkeep and the inception of subitems.