Show TOC

 Self-Billing – Complete Process


The following puts the self-billing procedure in context as part of the process flow between customer and vendor. It provides an overview of the uses of this function and the system settings required.

Note Note

The settings detailed here refer to an SD coupling between 2 clients or 2 SAP systems.

End of the note.


Vendor (SD)

  • You have created a material with the corresponding views (for example, Sales and Distribution).

  • You have created the customer master in your system.

  • You have created an SD scheduling agreement or order for this customer for the appropriate material, and entered the customer material and the partner description in this scheduling agreement or order.

  • You have created an SD delivery and an initial billing document.

  • You have fulfilled the prerequisites for receiving self-billing documents per EDI. See also Self-Billing Procedure With EDI .

  • You have made the Customizing settings for the self-billing procedure. See also Processing Inbound Self-Billing Documents .

Customer (MM)

  • You have created a material with all relevant views.

  • You have created the vendor master in your system. In the vendor master, you have flagged the indicators GR-based inv. verif. and AutoEvalGRSetmt Del.

  • You have created an MM scheduling agreement or a purchase order. Make sure that the indicators GR-based inv. verif. and AutoEvalGRSetmt Del. are flagged in the purchasing document item. Your MM scheduling agreement must contain at least one schedule line, at least one of which is issued.

  • You have fulfilled the prerequisites for sending self-billing documents per EDI.

Process Flow

  1. The vendor creates a delivery with reference to the SD scheduling agreement/order in his system.

  2. The vendor posts goods issue of the delivery.

  3. The vendor creates an initial billing document, which he does not send to the customer.

  4. The customer receives the materials and creates a goods receipt with reference to the delivery note number in the MM module.

  5. The customer creates a self-billing document for the goods received, using the MM ERS functions. Make sure that you use the document selection LI .

  6. The customer transmits the self-billing document to the vendor "per EDI" (in this case: ALE). The document must include a number that the system can use to directly or indirectly determine an SD document number (for example, the SD delivery.)

  7. The vendor system reads and checks the transmission, which can contain several IDocs and therefore several deliveries.

  8. The vendor initiates processing of the transmission, in which the open value from the internal invoice is compared with the value in the self-billing document.

  9. If the values match, an external reference number is updated in the billing (FI) document.

  10. If the values do not match, the system automatically posts all differences, debit or credit, depending on the +/- sign. It assigns a reference number to all documents that are assigned to the delivery. The reference number is used later to post receipt of payment. If you have set a tolerance check, the system creates no open items unless the tolerance levels are exceeded. If the tolerance levels are exceeded, the system creates new open items. However, these are not assigned a reference number. Unless tolerance checking is set, the system creates new open items for every clearing entry. To set the system to create no new open items, you must activate a tolerance group, in which the tolerance check is explicitly switched off (that is, the Check limits field is not flagged.)