Collective Invoice
A collective invoice combines several individual deliveries or services provided to the same customer within a period into a single invoice. Instead of billing each delivery note separately, the seller bundles all open items – for example every delivery of a month – into one document with a single invoice number and a single payment amount.
A collective invoice combines several individual deliveries or services provided to the same customer over a defined period into a single invoice. Instead of billing each delivery note separately and immediately, the seller collects the open items – for instance all deliveries of a calendar month – and, at the end of the period, invoices them as a bundle in one document with a single invoice number, a single invoice date and a single total amount payable. Each underlying delivery remains traceable as its own line item, referencing its delivery note.
From a business perspective, the collective invoice is an instrument for reducing document volume and administrative effort. A company that delivers to a customer several times a week would generate dozens of documents a month with individual invoices – each with its own payment term, its own monitoring and its own incoming payment. The collective invoice replaces this multitude with one consolidated document. It is therefore especially common in B2B business with recurring delivery relationships, in wholesale and in supplying branches or construction sites. In an ERP system, the collective invoice is not a special case but a billing strategy closely interlinked with the delivery note, order processing and accounts receivable.
At a glance
- Bundles several deliveries/services of a period to the same customer into one invoice
- One document, one invoice number, one payment term – instead of many individual invoices
- Each delivery stays traceable as a line item referencing its delivery note
- Reduces document volume, postage costs and effort in accounts receivable and payment processing
- Typical in B2B wholesale and with recurring delivery relationships (branches, construction sites)
How does a collective invoice work?
The basis of a collective invoice is several completed deliveries that have not yet been invoiced. For each delivery a delivery note is created, documenting the delivered articles and quantities but not yet constituting a demand for payment. At the end of the agreed billing period – for example monthly, weekly or after a certain number of documents is reached – all open delivery notes for the same customer are consolidated and condensed into one document in an invoicing run.
The collective invoice lists the line items of the individual deliveries and, per line item or per delivery note, shows the quantity, the unit price and the total. It is often grouped by delivery note, so the customer can assign each partial delivery to a date and a delivery note number. At the document footer are the subtotal across all deliveries, the disclosed VAT and the total amount. A single payment term applies to this total amount, and it forms a single open item in accounts receivable.
Structure and mandatory components
A collective invoice must contain the same mandatory details as any invoice: the full names and addresses of the seller and the customer, the tax number or VAT identification number, the invoice number, the invoice date, the quantity and type of goods delivered, the delivery date per line item, as well as the consideration broken down by tax rate and the tax amount. The delivery date is critical: because a collective invoice bundles deliveries from different days, the respective time of supply must be identifiable per line item or per delivery note – a blanket reference such as "date of supply equals invoice date" is not sufficient.
Billing cycle and triggers
When a collective invoice is generated is determined by the billing cycle. Common approaches are calendar-based intervals (monthly at month-end, weekly) or event-based triggers such as reaching a certain number of open delivery notes or an amount limit. The cycle is usually stored in the customer master record, so the system knows which customers receive individual invoices and which receive collective invoices. A company can thus bill small customers individually while billing high-revenue regular customers as a bundle.
Why a collective invoice makes sense
The main benefit of the collective invoice lies in efficiency. For companies with a high delivery frequency, the number of invoices to be created, sent and monitored drops drastically. This saves paper and postage on postal dispatch, reduces the postings in accounts receivable and simplifies dunning: one open item is monitored instead of many small ones. The customer benefits too – they receive a clear statement and make a single consolidated payment instead of transferring and reconciling numerous small amounts individually.
A further advantage concerns payment processing and liquidity planning. A single payment term for the entire period makes incoming payments more predictable and the reconciliation of open items easier. At the same time, a collective invoice can effectively extend the payment period, because goods delivered early in the month only become due with the monthly invoice – an aspect sellers should consider when structuring terms. Against this stand possible drawbacks: invoicing is delayed, which pushes the incoming payment back, and a single disputed line item can block payment of the entire invoice.
Collective invoice in the ERP system
In the ERP system, the collective invoice is an automated function of invoicing. After delivery, the system initially only generates the delivery note and marks the line items as "deliverable, but not yet invoiced". An invoicing run then collects all open delivery notes per customer and condenses them – controlled by the invoicing strategy stored in the customer master record – into a collective invoice. Prices, discount scales and tax rates are taken from the article master and price list, so no line item has to be entered manually.
The value of this integration lies in the seamless data flow within the order-to-cash process. Because the collective invoice arises directly from the delivery notes, quantities and prices remain consistent with the actual shipment, and each line item carries its document reference. The generated open item flows automatically into accounts receivable, into dunning and into the advance VAT return. Via the e-invoicing functions of the system, the collective invoice can also be output as a structured data record (such as ZUGFeRD or XRechnung), as is increasingly required in the B2B sphere.
Distinction: collective invoice, individual invoice and partial invoice
The individual invoice bills exactly one delivery or service and typically arises immediately with or after the shipment. The collective invoice is its counterpart: it bundles several completed deliveries retrospectively. To be distinguished from this is the partial invoice (or progress invoice), which represents the reverse case – here a single order that has not yet been fully rendered is billed in several installments. So collective invoice means: many deliveries, one document; partial invoice means: one order, several documents.
DACH specifics: VAT and e-invoicing
For VAT purposes, the time of supply is decisive with a collective invoice. Under German VAT law, an invoice must state the time of the delivery or service (Section 14 (4) UStG). Because a collective invoice bundles deliveries from several days, the respective delivery date must be shown per line item or per delivery note. This is relevant for the customer's input tax deduction: if the time of supply is missing, the invoice is formally defective. The reference is often established via the delivery note numbers and their dates.
The period boundary must also be observed: if deliveries from two advance-return periods are combined in one invoice, the revenues must nonetheless be assigned to the correct period – the tax arises based on the supply, not on the invoice date. In Austria and Switzerland, comparable requirements apply to the invoice details. For all DACH countries, the importance of the electronic invoice is also growing: collective invoices too must meet the formal requirements and, where mandated in the B2B sphere, be issued as a structured e-invoice under the EN 16931 standard.
Example
Example: Beverage wholesaler supplies hospitality customers
A beverage wholesaler supplies a restaurant with replenishment several times a week. Over a month, fifteen to twenty deliveries easily accumulate. With individual invoices, accounting would have to create and send dozens of documents per customer and monitor their incoming payments individually – a considerable effort that also leads to confusing payment processes on the customer side.
Instead, the monthly collective invoice is stored in the customer master record. Each delivery generates only a delivery note, which the driver has signed off. At month-end, accounting starts an invoicing run in the ERP: the system bundles all open delivery notes per customer, groups the line items by delivery date and creates a collective invoice with one total amount and one payment term. Twenty potential individual invoices become one document, the customer transfers one amount, and accounts receivable monitors one open item instead of twenty.
Frequently asked questions
Related services
Sources
Questions about Collective Invoice in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.