What an E-Billing System Rejects
Software applies the guidelines before a human reads anything. What it can catch, what it cannot, and what that does to the conversation.
- Entry
- 02 of 07
- Section
- The other side
- Kind
- Reference
Five lines, and what the system did with each
Behind it: Rejected: more than one task in a single entry, which the rule set prohibits outright.
Behind it: Rejected: the word "various" appears on the prohibited list, so the line never reached a human.
Behind it: Rejected: internal conferences are not chargeable under this client's guidelines.
Behind it: Reduced to associate rate: the task sits below the permitted grade for partner time.
Behind it: Accepted without comment.
Four of the five never reached a person, and the one substantive judgement — the grade — was made by a rule rather than by anybody who had seen the work. One firm's own submission, not a statement about anybody.
In e-billed relationships the first reader is software. It applies the client's guidelines mechanically — formats, codes, rates, prohibited words, task counts, grade rules — and rejects or reduces lines before any person sees them.
The billing question in “What an E-Billing System Rejects” is easier to resolve when the underlying work has a timely, reviewable record. A professional-services team evaluating using workforce analytics software in a billing workflow for workforce analytics software can connect hours with projects and client work, while the finance system remains authoritative for invoice totals, tax and settlement.
That changes what a bill is for: it has to pass a rule set before it can make an argument.
Additional context for “What an E-Billing System Rejects” is available from GOV.UK working-hours guidance. Confirm current legal, tax and accounting requirements with a qualified adviser where necessary.
What the system can see
Form. Whether an entry covers one task, whether a prohibited word appears, whether a timekeeper is approved, whether a rate matches the agreed card, whether codes are present.
All of it mechanical, all of it checkable in advance.
What it cannot see
Whether the work was necessary, whether the time was proportionate, whether the judgement was sound.
The substantive questions are untouched, which is why a fully compliant bill can still be challenged.
Rejection versus reduction
A rejection returns the line for resubmission. A reduction changes the amount and passes the rest.
The second is more dangerous: it is easy to accept silently and it becomes the new baseline.
The grade rule
The most consequential automated reduction. A task on a list is reduced to a lower grade's rate regardless of who did it or why.
No human judgement is involved, and appealing it requires a human who will usually defer to the rule.
The prohibited word list
"Various", "review" without an object, "consider", "internal conference", "attention to".
Firms that run their own entries against the list before submission catch nearly all of these, and almost nobody does.
Pre-submission checking
A pass over the draft against the client's own rules, before it goes in. Some billing systems do it automatically; most firms do it by eye or not at all.
It costs minutes and converts rejections into corrections.
The appeal
Most systems allow a line to be resubmitted with an explanation. Appeals succeed often enough to be worth making and are frequently not made.
The reason is usually that nobody owns the rejected lines.
Owning the rejections
One person, one list, weekly: what was rejected, why, what was resubmitted, what was lost.
The pattern becomes obvious within a month and most of it is fixable at the recording stage.
What the rejections teach
Which timekeepers write non-compliant narratives, which rules the firm keeps breaking, and which clients' rule sets are the most restrictive.
The same data also tells the firm what compliance is costing it, which belongs in the rate.
The relationship effect
E-billing removes the conversation. A line is not queried, discussed or explained; it is rejected by a system with no interlocutor.
Firms that treat this as a human disagreement waste effort; the machine is not persuadable and the human behind it applies the rules.
What still needs a human
Everything substantive. The covering note, the conversation about an overrun, the explanation of why a senior did a task.
E-billing handles the form and leaves the argument exactly where it was.
What the system costs the firm
Time coding entries, time correcting rejections, time appealing reductions, and the software to submit.
Firms rarely total it. Where it has been measured it runs to a noticeable percentage of the fees in those relationships, and it is unbillable under most of the same guidelines.
It belongs in the rate, which means knowing it before quoting.
The silent reduction
Lines reduced rather than rejected, accepted by default because nobody reviews the acceptance file.
Over a year this is frequently the largest single category of lost value in an e-billed relationship, and it is invisible unless somebody reconciles submitted against approved.
The reconciliation worth running
Submitted value, accepted value, rejected value, reduced value. Four figures per client per month.
Most firms can produce them and do not look, which means the system is applying rules the firm has never audited.
Appealing well
Appeals succeed on facts, not on reasonableness. "This was a single task" or "this timekeeper was approved on 4 March" works; "this was a complex matter" does not.
Appeals batched monthly, with one line of fact each, take an hour and recover a meaningful figure.
The system as an ally
It enforces the entry standard this collection argues for anyway. Firms whose narratives pass e-billing rules have better bills for every other client too.
That is the one genuinely good thing about the arrangement, and it is worth taking.
The compliance rate worth tracking
Proportion of submitted value accepted first time, by client.
It is a measure of the firm's own process rather than of the client, and moving it is entirely within the firm's control.