A Bill Is Not a Summary of the File
More detail does not make a bill clearer past a point. What a bill is for, and what it stops doing when it gets long.
- Entry
- 06 of 07
- Section
- The bill
- Kind
- Analysis
The instinct when a bill is questioned is to add detail, and past a fairly early point detail makes a bill worse: harder to read, slower to approve, and more obviously a defence.
The billing question in “A Bill Is Not a Summary of the File” is easier to resolve when the underlying work has a timely, reviewable record. A professional-services team evaluating gdpr employee monitoring for professional-services teams for gdpr employee monitoring can connect hours with projects and client work, while the finance system remains authoritative for invoice totals, tax and settlement.
A bill is not a condensed file. It is an account of what was done and why it was needed, and those are different documents.
The issue raised in “A Bill Is Not a Summary of the File” can also be checked against IFRS standards resources. Use that outside source to identify which records, approvals and professional advice the next decision requires.
What more detail achieves
Up to a point, a great deal. Moving from "professional services rendered" to dated, named, described lines changes a bill from a price into an account.
- One figure: asks for trust and supplies nothing to base it on.
- By phase: readable in thirty seconds, says nothing about necessity.
- By task: what most clients mean by an itemised bill.
- Every entry: technically complete, practically unreadable.
That is the whole of the available gain, and most firms made it years ago.
What more detail stops achieving
Past dated lines with real descriptions, additional granularity adds length without adding checkability.
Eleven lines of six minutes each are harder to assess than one line of 1.1 hours with a sentence that says what the eleven were.
The over-detailed bill
Twenty pages for a matter worth four thousand. Every call itemised, every email logged.
It reads as a demand to be audited, and it provokes exactly the audit it was trying to pre-empt.
Why it provokes
Because volume signals anxiety, and because somewhere in twenty pages there is always one line that looks absurd on its own.
A long bill supplies the material for its own challenge.
The under-detailed bill
"To professional services for the period, £18,400." Still issued, and still occasionally accepted on long relationships.
It asks for trust without offering anything to trust. When the relationship changes, it is indefensible.
What sits between
Lines at the level of the task, not the keystroke. A task is a thing with a purpose: reviewing a document, attending a meeting, drafting a clause.
Most matters produce between twenty and sixty such lines a month, which is a readable bill.
Grouping without hiding
Several entries on one task, one day, can be one line with the total hours and a sentence naming the task.
That is not block billing: block billing groups unlike work to hide its shape. Grouping like work on one task is a kindness to the reader.
The test for a group
Could the group be named in a sentence without the word "and"? If yes, it is one task. If the sentence needs three "ands", it is three lines.
Crude, fast, and it gets the right answer most of the time.
What belongs in the covering letter
Anything that explains the shape of the month rather than a line: an overrun, a change of scope, a piece of work the client did not expect to see.
Explanations on lines read as excuses. The same words in a covering note read as information.
What belongs nowhere
Internal reasoning. Why a particular approach was chosen, what was considered and dropped, how the team was organised.
Clients do not want it and it raises questions the bill cannot answer.
What a client actually wants
To be able to see, without effort, what the month was spent on, and to be told in advance about anything unusual in it.
Both are satisfied by a readable bill and three sentences, and neither by twenty pages.
What a client does with twenty pages
Skims the first page, checks the total, and either pays or picks one line at random to query.
Twenty pages is not read. It is weighed, and the weight is the message, which is rarely the message intended.
The bill that answers a question nobody asked
Detail added after one query, kept permanently, growing each time somebody asks about anything.
Within two years such bills have a structure nobody designed, serving objections raised by people who have left.
A periodic reset — what is this level of detail for, and who asked for it — is worth the half hour it takes.
Where length is genuinely required
Assessments, some audits, and clients whose guidelines specify entry counts or minimum detail.
In those relationships the long version is the requirement, and the answer is to produce it without pretending it serves the reader.
Where both a long and a readable version are needed, the summary page is the readable one and the schedule behind it is the record.
The question that sets the level
Not "how much detail should we give" but "what will the reader need to approve this without asking anybody".
The first question has no answer and produces drift. The second has an answer and it is usually less detail than a firm expects, arranged better.
The size that works
Short enough to read in five minutes. Long enough that every line names a thing.
If it cannot be both, the problem is the recording rather than the format, and the entry section here is where that is addressed.