Budget Billing Procedure

In the statistical procedure, the budget billing amounts are not posted as debits until they are paid by the customer.

In the partial bill procedure, the individual amounts are posted directly as debits.

In the budget billing plan, an average amount is determined either by simulation or manually. The customer pays this average amount for a period of 12 months. At the end of this period, a new simulation is run for the next period. In addition, actual consumption is calculated monthly, and the results are printed on the bill. In addition, the difference between the customer's actual consumption and the average amount is calculated, updated monthly, and printed on the bill. In the last month of the billing period, the actual amount and the accumulated difference are billed.

In average monthly billing/equalized billing, the customer is charged an average amount based on billings over the last 12 months (or less in the case of new customers). In addition, actual consumption is calculated monthly, and the results are printed on the bill. The amounts due for later months are calculated using the average of the previous (maximum 11) months plus the current bill and the accumulated difference. This difference is updated monthly and is also printed on the bill. In final billing, the amount due is derived from the actual consumption and the accumulated difference.

In the payment scheme, the bill amount from the latest billing is copied to the next budget billing plan. This means that the bill amount need not be cleared through a direct payment. The budget billing amount is made up of a portion of the bill and a portion of the extrapolation for the subsequent budget billing periods.

Budget billing amount due dates are administered in a budget billing plan.

The budget billings can be displayed as statistical postings (that is, they are not posted to the general ledger) in the account balance display immediately (for example, after the budget billing plan has been created).

The budget billing amounts can be printed, by due date, for example. To do this, first start the budget billing request report. This report generates the print documents that form the basis for the print report. After that, start the print report, which generated the actual bills for budget billing.

When payment occurs, the budget billing amount is first posted. This includes value-added tax.

During invoicing, the budget billing plan is deactivated and the paid budget billing amounts are transferred.

Budget billing amount due dates are administered in a budget billing plan.

The budget billing amounts cannot be displayed immediately (for example after you have created the budget billing plan) in the account balance display. In the partial bill procedure, the budget billing plan is administered in a shadow table, which is not used by FI-CA.

The item is not transferred in FI-CA until the Enter partial bill report is started (debit entry procedure). This is the first posting with value-added tax. This report must be scheduled periodically, even if you do not want to print any partial bills. In addition, this report generates the print documents that form the basis for the partial bill printout, should it be required.

The budget billing amounts can be printed, by due date, for example. To do this, start the print report after the Enter partial bill report has run. This generates the physical partial bill.

During payment, only open items are cleared. No changes are made to the value-added tax posting. It was already posted.

During invoicing, the budget billing plan is deactivated and the posted partial bills are transferred.

The Average Monthly Billing (AMB) and Budget Billing Plan (BBP) payment plan procedures are used mainly in the North American market for monthly meter readings/billing.

Customers use these payment plans to even out the monthly payments to their utility companies.

In the AMB procedure, the amount to be paid monthly is a calculated average amount. A customer using a BBP procedure pays the same monthly amount for the entire12 months.

The difference between the billing amount and the AMB/BBP amount is updated in a separate item (balance forward).

In an AMB procedure, the customer pays an average amount every month. The amount is calculated from the last n months (generally 12 months).

The AMB amount can differ from month to month.

The balance forward becomes smaller and smaller as the end of the period approaches. In the AMB procedure, the remaining amount to be paid at the end of the period is less than the amount in the BBP procedure.

Depending on the Customizing settings, the customer only has to pay the AMB amount or the AMB and balance forward amount at the end of the period.

In a BBP procedure, the customer pays the same amount every month. The amount is calculated from the last n months (generally 11 months).

The remaining amount the customer has to pay at the end of the period (balance forward) is generally higher in BBP procedures than in AMB procedures.

At the end of the period, the customer has to pay the BBP amount and the balance forward. The settings are specified in the contract.

In a BBP procedure, the BBP amounts are managed technically in a budget billing plan. However, these amounts cannot be viewed in the account balance display, but in a shadow table. This table is also used for the partial bill procedure in budget billing.

The payment plan procedures (AMB/BBP) are controlled in the contract using the Payment plan category, Start month and Alternative start month fields.

These fields can be entered manually in the contract. You can also enter this data using the transaction for creating a payment plan.

The main function of the payment plan category is to determine which payment plan procedure is being used. You define the payment plan category in Customizing.

When the start month has been reached, the payment plan is created in invoicing.

The system processes any changes you make in the contract fields during the next invoicing. For example, you must delete the start month in the contract if the customer wants to terminate his/her payment plan immediately. The balance forward is then settled in the next invoicing, and the customer must pay the remaining amount.

One payment plan is always maintained for each contract. However, there is now also a maintenance transaction that can be used for the maintenance of multiple payment plans for multiple contracts. For example, across different divisions.