Summary invoicing survives the move to Electronic Invoicing, with one constraint that changes how consolidation logic has to be written. A summary invoice consolidates multiple transactions with the same customer over a defined invoicing period onto a single document, under Article 65 of the VAT Decree-Law and Article 59 of the Executive Regulation. Where the consolidated total comes out negative, the document cannot be issued as an invoice at all.
The Negative Total Rule
The Guidelines state that certain fields at document level can be zero or a positive number in order to pass Peppol validation. Where the total payable amount is negative, meaning the period nets to a credit position, the transaction must be documented using an Electronic Credit Note. The Guidelines confirm that this rationale applies to summary invoices in the same way it applies to any other document.
The consequence is that the document type is determined by the arithmetic, and the arithmetic is only known once the period closes. A billing run that consolidates a month of activity for a customer cannot know in advance whether it is producing an invoice or a credit note.
Why This Breaks Common Billing Logic
Most consolidated billing processes assign the document type at the start of the run, based on the billing arrangement or the document type configured against the customer. Credits raised during the period are then netted into the invoice as negative lines, and the run produces an invoice regardless of where the total lands. That design produces a negative-total invoice whenever returns, rebates or milestone reversals in a period exceed new billing.
Under PINT-AE the run has to compute the net first and branch on the result. A period that nets positive produces an electronic Tax Invoice or Commercial Invoice; a period that nets negative produces an Electronic Credit Note carrying the same underlying lines. Both documents then need their own numbering, their own approval path and their own transmission.
Where This Shows Up
The Guidelines use a bank as the example: multiple supplies to a customer over a month, consolidated into a single monthly electronic Tax Invoice summarising all of them. The same pattern runs through telecoms, logistics, facilities management, distribution with volume rebates, and any arrangement where fee income and credits accumulate against one customer account across a period.
These are also the highest-volume billing processes in most businesses, which is what makes the constraint operationally significant. A rule that affects a handful of documents a year can be handled by exception; a rule that can affect any customer in any monthly run has to be built into the run itself.
Scenario 4 Applies to Commercial Invoices
The scenario is available to businesses issuing Commercial Invoices as well as electronic Tax Invoices, so a Person outside the VAT net who consolidates periodic billing is inside the same constraint. Summary invoicing is not restricted to Taxable Persons.
The test worth running before go-live is a simple one: take twelve months of consolidated billing history and count how many customer periods closed at a net negative. That number is the volume of documents that will need to route to the credit note path, and it is usually larger than the billing team expects.