Kontakt

Ansicht
Dokumentation

Sales: Billing Plan (payment plan) ( RELNSD_SLS_30ZAHLUNGSPLN )

Sales: Billing Plan (payment plan) ( RELNSD_SLS_30ZAHLUNGSPLN )

General Data in Customer Master   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Sales: Billing Plan (payment plan)

Description

During order processing, a detailed billing plan can be stored in the sales document on item level instead of a single billing date.

The billing plan specifies which amount or percentage rate is to be billed, and when this is to be done. This form of invoice creation plays an important role, for example in rent settlement where invoices are created periodically and in the billing of projects where billing dates are linked to the completion dates of the various stages of the project.

Each billing plan is identified by a billing plan number which is internally assigned by the system.

In order processing you reach the billing plan by choosing Item -> Contract -> Billing plan. There are different overview screens for the application examples of rent and milestone billing of projects.

Functionality

  • Automatic creation of billing dates in the billing plan
In Customizing, you can control the way that the system calculates the various dates (for example start date and final date, horizon, settlement period) and enters them automatically in the billing plan. The dates are either transferred from the contract data or proposed on the basis of the billing plan type.
A setting can also be made in Customizing which allows you to enter the dates manually.
  • Pricing and billing
Order items which belong to the billing plan are billed on the due date. The values to be billed are determined from the conditions for theorder items or from the specifications (amounts or percentage specifications made for the dates in the billing plan date).
When creating a billing document from the document, you must choose the documents with due dates using a selection date.
The following functions are also defined for billing:
  • Billing block

You can set a billing block for each date in the billing plan. This billing block prevents the billing of this date. Other dates in the billing plan are not affected.
For project milestones, a billing block exists until the milestone is confirmed as finished by the network. After confirmation of the completion of the milestone is received, the billing block is automatically cancelled.
  • Billing index

A billing index is set up and updated for each date in the billing plan. If the date is blocked for billing, this information is transferred to the index.
  • Billing status

A billing status is managed for each date. It displays how far an item was processed during billing. After billing, the billing status on the overview screen of the billing plan is automatically set to "C". In this way, a billing date in the billing plan can only be billed once.
The order item has an overall status which displays the status of all dates (for example, "partially billed" if at least one date has already been billed). You can display the overall status from the overview screen by choosing Item -> Status.
  • Closing invoice for milestone billing

Dates not yet billed are taken into account for the closing invoice. Price changes, for example, which were only made after the billing of individual dates can be passed on to the customer.
The closing invoice is not automatically defaulted in the billing plan and must be entered manually.
  • Fixed date in milestone billing

You can control for each date in the billing plan, whether it is a fixed date or whether the planned date or the actual date is adopted from the milestone.
  • Document flow
After billing a date, the document flow of the order items in question also includes the billed dates. In the document flow (Environment -> Document flow), the billing plan number, the date of creation, the date and the billed value are stored. By double-clicking, you can go to the detail display on which the billed date is shown.
  • Creating with reference
In Customizing, the number of a billing plan can be stored as a reference for each billing plan type. During order processing with this billing plan type, dates are determined on the basis of this reference, then re-determined on the basis of the current rules, and entered into the billing schedule.

Forms of billing plan (billing plan types)

A billing plan type can be assigend to an item category in Customizing. This cannot be changed during order processing.

Depending on the billing plan type, a billing plan can either be used for milestone billing and for periodic billing. You can distinguish between the two forms of the billing plan, in that the total value to be billed is either divided up between the individual dates in the billing plan or is billed periodically as a total value for each date until the predefined final date.

One billing rule is stored for each billing plan date. This controls how the value of a date to be billed is to be determined. There are six billing rules in the standard system. Billing rule 2 (value-based milestone billing) specifies, for example, that the entire billing value is distributed among the dates and on each date a certain part of the total value is billed.

  • Milestone billing
A typical example for a milestone billing is the billing of projects (for example plant engineering and construction). This is carried out in steps as certain activities or project sections - so-called milestones which are stored in a network with actual data - are completed. The milestones are also assigned to the dates in the billing plan and contain a billing block until the milestone is reported as completed by the network.
Corresponding order items are linked to the project network by the schedule lines. You reach the network by choosing the menu sequence Item -> Schedule line -> Quantities/dates -> Procurement details -> Transactions.
For each date, you can control whether the billing date
  • is a fixed date,

  • is always updated with the actual date of the milestone,

  • is updated with the actual date of the milestone, if this is completed after the 'planned' billing date in the billing plan, or

  • is updated with the actual date of the milestone, if this is completed before the 'planned' billing date in the billing plan.

  • Periodic billing
An example of a typical application of periodic billing is rental contract processing.
The dates for creating the billing plan are either transferred from the contract data, determined from the billing plan type, or explicitly entered. The following dates are important in this case:
  • Start and end dates define the validity period of the billing plan and are transferred - where possible - from the contract data. The dates can also be determined using date determination rules. Further information on contract data and date determination can be found in the release note on contract processing.

  • The periodicity of the billing date determines the recurring billing dates (for example, monthly) and whether billing is to take place on the 1st or the last of the month.

  • Based on these dates, the billing dates are determined and entered in the billing plan. If no end date is entered, or if the end date is so far in the future that not all the billing dates can be set, then a rule must be specified to determine the horizon.

The horizon specifies the last date up to which dates for periodic billing documents are to be set. The horizon is always determined from a rule which contains the current date (= CPU date) as a baseline date. As the CPU-date moves forward, so the horizon is constantly extended and the billing dates are dynamically moved into the future.
Date determination according to the current horizon can either be started automatically or manually: If a date is invoiced without a final date, the billing document starts a process which extends the billing plan according by the horizon. You can add subsequent dates to the billing plan manually on the basis of the horizon by choosing Outline agreement -> Contract -> Periodic billing.

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

In Customizing, the following options exist for the billing schedule:

  • Billing plan type
The billing plan type contains the basic control data for the billing plan and specifies the type of billing plan. By means of certain rules for date determination, the period of a billing plan, for example, is defaulted including the horizon, from which the respective dates in the billing plan are determined.
The billing plan type is determined from the document item category and the relevance for billing. It is displayed in the billing plan, but cannot be changed there. The standard system contains a billing plan type for milestone billing (01) and for periodic billing (02).
In the field Dialog sales order you can control, whether the billing dates are automatically determined and set in the billing plan or whether this is done manually.
In the field In advance you can control, whether billing is backdated or carried out in advance, whether rent which is invoiced on the 15th of every month, should for example, be invoiced backdated or not.
  • The date descriptions described the respective billing dates in the billing plan. The descriptions are only used for differentiating between the billing dates and have no controlling character.
  • Date category
Date categories control certain billing data on the level of billing dates, such as, fixed dates or billing blocks.
  • Default date category
A date category is assigned to each billing plan type and defaulted in the document. The date category 'Closing invoice' is not defaulted in the standard system and must be entered manually.
  • Date proposal
The date proposal is only relevant to the billing plan type 'Milestone billing', and can contain a sequence of dates which are used as a reference during order processing.
  • Assignment of sales document items
Item categories for which a billing plan can be created, must be classified in Customizing as relevant for billing with 'I' (relevant for order- related billing document - billing plan) and assigned a billing plan type.

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

Further information about settings in the billing plan can be found in the Implementation Guide under "Billing plan".






RFUMSV00 - Advance Return for Tax on Sales/Purchases   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 12927 Date: 20240523 Time: 084015     sap01-206 ( 207 ms )