In one recent production run, our billing engine turned 31,389 transactions into 4 invoices. Not 31,389 invoices. Not 31,389 unreadable line items. Four clean documents — each one summarizing thousands of underlying transactions into figures a customer can actually understand.
That number points at a tension every billing system faces. Show a customer everything they were charged for, line by line, and the invoice becomes an unreadable wall. Show them a clean summary, and someone usually had to assemble it by hand — exporting data, consolidating it in a spreadsheet, pasting totals back. Most teams pick the lesser evil and live with it.
Too granular
Hundreds of tiny line items — one per event, usage record, or transaction. Technically complete. Practically unreadable. The customer can't tell what they're paying for, so they call you.
Hand-assembled
Someone exports the data, consolidates it in a spreadsheet, and pastes the totals back. Clean for the customer — but slow, repetitive, and one copy-paste away from a wrong number on a real invoice.
The real job isn't listing. It's summarizing — without losing anything.
Good billing isn't about printing every transaction. It's about presenting the right summary on the invoice while keeping every underlying transaction intact behind it. One invoice line should be able to stand for one transaction — or for thousands.
In our platform, Digent.Billing, a single invoice line can summarize as many transactions as you like — and you decide how they group. By period, by service, by whatever dimension fits your business. Not a developer, not a hardcoded rule: the grouping is configuration you control. The quantities and values roll up automatically into one clean line, and the customer sees a number they understand.
The invoice stays readable. The detail doesn't disappear — it's one click away whenever anyone needs it.
Nothing is lost
This is the part that matters most. Summarizing on the invoice doesn't mean discarding the detail. Every transaction that fed into a line stays individually recorded and individually traceable. When a customer questions a charge, when finance reconciles, when an auditor asks “what is this €1,240 made of?” — the full breakdown is right there.
It's part of a larger idea behind how we build billing: what you charge for is configurable, and how it's grouped onto the invoice is configurable too. The business decides what a clean invoice looks like — not the limits of the software.