Customer Order Summary Invoice

A summary invoice is an invoice for more than one customer order delivery. Several conditions must be met to create a summary invoice:
  • The 'Summary invoice' code on the deliveries must not be 0.
  • The 'Summary invoice' code can be set manually on the customer order header on 'Customer Order. Open' (OIS100/F) or the delivery header on 'CO Delivery. Open' (OIS150/F). As a rule, the code defaults from the settings on 'Customer. Open' (CRS610/H) and 'CO Type. Open' (OIS010/K).

Several settings for summary invoicing are available in 'Settings - Customer Order Invoicing' (CRS722). These settings define whether summary invoicing breaks by delivery address, delivery number, order type, warehouse, delivery terms, customer, and shipment.

Break by delivery address or delivery number is controlled by the 'Sep invoices' parameter. If 'Sep invoices' is set to 0 in (CRS722), the 'Sep invoices' setting on the customer (CRS610/H) controls the behavior.

Regardless of these settings, deliveries can be invoiced together only if these fields are the same:

  • 'Division' (ODHEAD.DIVI)
  • 'Summary invoice code' (ODHEAD.AICD)
  • 'Payer' (ODHEAD.PYNO)
  • 'Invoice recipient' (ODHEAD.INRC)
  • 'The VAT registration number' (from the delivery address, or the customer primary record if no delivery address is specified)
  • 'FAM function'
  • 'Currency code' (ODHEAD.CUCD)
  • 'Payment terms' (ODHEAD.TEPY)
  • 'Payment method' (OOHEAD.PYCD)
  • 'Future rate agreement' (ODHEAD.FECN)
  • 'Exchange rate type' (OHEAD.CRTP)
  • 'VAT included code' (OHEAD.TINC)
  • 'Invoice series' (OTYPE.OT34)
  • 'Corrective invoice series' (OTYPE.OT79)
  • 'EU triangle code' (OHEAD.ECTT)
  • 'Discount model' (OHEAD.DISY)
  • 'Cash discount term' (OHEAD.TECD)
  • 'Manual due date' (OHEAD.DMDT)
  • 'Value date' (OHEAD.CURD)
  • 'Tax applicable' (OHEAD.TXAP)
  • 'Trade agreement model' (OHEAD.TAGY)
  • 'Reference number (credit card)' (ODHEAD.NREF)
  • 'Third party provider (credit card)' (ODHEAD.3RDP)
  • 'Reference number of payment request' (OHEAD.PYRE)
  • 'Finance reason code' (OOHEAD.FRSC).

These settings must be the same under specific conditions:

  • Delivery date (ODHEAD.DLDT), if the delivery date is the due date base
  • The facility of the delivering warehouse (MITWHL.FACI whs from ODHEAD), if 'No corr invoice' is not selected in (CRS722)
  • Order number (DHEAD.ORNO), if total price is used on the order
  • Customer number (OHEAD.CUNO), if 'Adv invoicing' on (OIS010/K) is 2-'Prepayment requests are allowed' and 'Prepmt posting' is set to 2-'No posting prepayment invoice' in (CRS722)

Independent of these settings and validations, a delivery cannot be included in a summary invoice if a tax calculation code is applied to the invoice.

Note: If the invoice is used for tax reporting, the sender’s tax details must be the same for the whole invoice. To ensure consistent tax details, select break by warehouse and break by delivery terms in (CRS722). You can achieve the same result without these settings if all warehouses are in the same country, use the same VAT registration number, and use delivery terms with the same 'Tax point' and 'Fisc rep rule' settings in 'Delivery Term. Open' (CRS065).
Related topics