Customer Order Summary Invoice

A summary invoice is an invoice for more than one customer order delivery. There are several conditions that must be met for a summary invoice to be created:
  • 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/E), but normally it defaults to the settings on 'Customer. Open' (CRS610/H) and 'CO Type. Open' (OIS010/K).

There are also several settings for summary invoicing in 'Settings – Customer Order Invoicing' (CRS722) to define whether summary invoicing should break 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 it is set to '0' in (CRS722), the 'Sep invoices' setting on the customer (CRS610/H) controls the behavior.

Regardless of these settings, deliveries can only be invoiced together if the fields listed below 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 master 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).

There are also settings that must be the same, depending on some other settings, as follows:

  • 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 'Advance invoice code' on (OIS010/K) is 2-'Prepayment req allowed' and 'Prepmt posting' is set to 2-'No posting prepayment invoice' in (CRS722).

Independent of all the settings and validations described above, any delivery that gets a Tax calculation code applied on the invoice is prevented from being included in a summary invoice.

Note: If the invoice is used for tax reporting, the sender’s tax details must be the same for the whole invoice. The only way to guarantee that is to select to break by warehouse and delivery terms in (CRS722). You can achieve this without these settings if all the warehouses involved are in the same country, using the same VAT registration number, and all the delivery terms have the same settings for 'Tax point' and 'Fisc rep rule' in 'Delivery Term. Open' (CRS065).
Related topics