collective billing

[Former Member]

HI

Please explain what are the requirements to do the collective billing

My client done collective billing customer once in month but instead of one invoice no four invoices are created .

[Former Member]

Hi Konda,

Collective billing is possible for documents of the same type. In VF04 you can specify the billing document type for which you want to run billing for.

Let's say for instance you want to run billing for sales document types BV (cash sales) and OR (standard order). Sales doc BV is assigned to billing type BV. Sales doc OR is assigned to billing type F2. Therefore you can't run collective billing for two sales documents, one being OR and the other BV. The system will generate two billing documents, one BV and the other F2

Another point you need to pay attention to is the header details. It is not enough to have the same PY (payer) partner function for two sales documents to be billed via a single billing document.

Let's say for instance you have two SP (sold to parties) with two different partner procedures

10001:

SP 10001

BP 10001

PY 10003

and

10002

SP 10002

BP 10002

PY 10003

The system will automatically create two seperate billing documents because the header information is not the same. This may sound strange, since the payer partner is the same 10003, but that's how the system works as per default.

If you want to have collective billing from multiple SP's you need to have a look at OSS note 43067

This is what it says:

Solution

1. In the partner determination procedure for the billing document header, the partner function for the sold-to party must be removed .

2. In the partner determination procedure for the billing document item, the partner function for the sold-to party mast be added.

3. A new data transport routine must be created in the customer area.Within this routine, the billing header field VBRK-KUNAG must be set to the payer for instance (VBRK-KUNRG).

FORM DATEN_KOPIEREN_601.

VBRK-KUNAG = VBRK-KUNRG.

ENDFORM.

All statistics which refer to the sold-to party are influenced by point 3.. The statistics must be checked for this.

4. Background billing or the processing of the billing due list (Transaction VF04) must be converted in such a way that the system no longer selects according to the sold-to party but according to the payer (see Note 25147).

[Former Member]

Hi,

T code.VF04.But the header data needs to be same while doing collective billing.

This combination criteria you can maintain in field ZUKARI(VBRK) field.This combination criteria has to be written in routine in copy control.

Regards,

Amrish Purohit

[Former Member]

hai,

can u be a bit clear, if u want collective billing to be done, these are the folowing pre-requesities

1. same payer

2.same billing date.

3.same currency.

then u can create a combined invoice.

if ur requirment is if u want to give a combined invoice for a week,month

then we use invoice list. VF21 is the t:code.

thank you.

regards

reward points

sriram

[Former Member]

Hello Konda,

<b>// Reward if this helps //</b>

Collective Billing Configuration steps:-

• transaction VD02 - Change Customers - tick Billing and filled in the Customer Code, Sales org., Distr.channel and Division then hit enter.

• Look for field name Inv.list sched. - you must filled in the Factory Calendar that you are currently using.

• You can simulate the collective billing in transaction VF04 - Process Billing Due List.

During simulation, if the billings cannot be combine, the system will give you this message,

Different header fields $000000001 $00000000 Combination criteria in the billing xxxxxxxxxxxx123 xxxxxxxxxxxx125

Criteria to satisfy for collective billings:-

• Billing document type is the same.

• Reference document type is the same.

• Item category in the reference document is the same.

The system combines into one billing document all transactions for the same customer and same billing data. If the header data and the header partners for the specified deliveries or sales orders are identical and if the requirements for splitting do not apply, one billing document is created for all the deliveries or sales orders.

The following illustrates an example. The system determines that deliveries 1 and 2 had the same bill-to party, and therefore combines the deliveries in one billing document.

Delivery Order 1 - |

-

---

> Invoice

Delivery Order 2 - |

Regards

AK

[Former Member]

Processing Billing Due List (T.Code: VF04)

&#61550; To make billing faster and easier, the R/3 System provides the billing due list as a means to process more than one billing document at a time. The system combines as many items for billing as possible in as few billing documents as possible.

&#61550; This function can be executed by:

&#61599; manual processing of the billing due list (online processing)

&#61599; creating a background job to be executed during off-peak hours

Regards,

Rajesh Banka

Reward points if helpful.

[Former Member]

<b>Processing Billing Due List (T.Code: VF04)</b>

&#61550; You will not usually bill transactions individually. You are far more likely to carry out periodic collective billing runs (collectively by goods issue posting, for example).

&#61550; If you are working with the billing due list, enter the selection criteria, for example, sold-to party, billing date, destination country. The system uses the selection criteria as a basis for combining the transactions to be billed.

&#61550; When selecting, you can also decide whether the billing due list should only contain documents that are order-related, delivery-related, or both.

&#61550; The graphic above displays a case in which creation of billing documents is restricted to those documents that were delivered before May 15 for sold-to party C1. Based on this selection, the system creates the billing due list and creates billing documents on the basis of this list.

&#61550; After saving, you can display the log to determine which billing documents were created from a billing due list and whether any errors occurred.

&#61550; You can process the billing due list in simulation mode. The system displays the billing documents without saving the documents. Transactions containing errors are indicated with the corresponding processing status.

&#61550; As of Release 4.5, further selection data (sales document number, distribution channel, division, and shipping point) and new ways of processing are available when processing the billing due list. The information provided in the error log has also been extended.

Regards,

Rajesh Banka