Outside-Counsel Guidelines and E-Billing Rejections
For firms doing corporate or insurance-defence work, the invoice is not the end of the billing process — it is the start of a second review. The client's outside-counsel guidelines (OCGs), enforced by an e-billing portal, check every line before a penny is approved. Lines that break a rule are reduced or rejected, the invoice bounces back, and the fee earner who did the work weeks ago has to revisit it.
Each rejection is slow, and each one delays payment. This article walks through why entries get rejected, why the timing of the check is the real problem, and how catching violations at the desk — before submission — changes the economics.
What outside-counsel guidelines actually govern
OCGs are the client's rules for how their legal work may be billed. They vary by client, but most cover a familiar set of controls:
- Approved and prohibited task codes — often UTBMS codes — with certain activities (internal conferences, administrative time, some research) disallowed or capped.
- Time increments — usually tenths of an hour, with rounding rules and sometimes a cap on the units a single activity may claim.
- Block billing — combining several tasks under one time entry and a single duration, which most guidelines forbid; each task must be a separate line.
- Staffing and rate rules — who may work the matter, at what rate, and whether partner time on a task juniors could do is chargeable.
- Narrative requirements — descriptions specific enough to justify the time, with vague entries ("attention to file", "review documents") frequently reduced.
None of this is obscure. The difficulty is that the rules differ from client to client, and the person writing the time entry is rarely thinking about a specific client's guideline at the moment they record it.
The most common reasons entries get rejected
Across e-billing portals, a handful of patterns account for most reductions and rejections:
- Block billing. Several tasks bundled into one line. The portal cannot attribute time to an approved code, so it reduces or bounces the entry.
- Prohibited or mismatched task codes. The activity maps to a code the client disallows, or to no valid code at all.
- Increment and rounding breaches. Entries that violate the client's rounding policy, or a single task claiming more units than the guideline permits.
- Vague narratives. Descriptions that do not say what was done or why it was necessary.
- Staffing or rate violations. A timekeeper or rate the guideline does not approve for that matter.
- Duplicate or administrative time. Two people billing the same internal meeting, or non-chargeable admin recorded as billable.
The common thread is that every one of these is knowable at the moment the entry is written. Nothing about a block-billed line or a prohibited code requires the invoice to be assembled first — the violation exists the instant the entry is recorded.
Why the timing is the real problem
Most firms discover these violations at the worst possible moment: after the invoice has been compiled, submitted, and rejected. By then the cost is compounded.
- The fee earner has moved on and must reconstruct what a weeks-old entry meant.
- A billing clerk or partner spends time reworking and resubmitting.
- Payment is delayed by a full billing cycle or more.
- Some genuinely billable time is written off simply because fixing it costs more than it is worth.
The information needed to prevent all of this existed at the desk when the work was recorded. The check just happened in the wrong place, run by the client instead of the firm, and too late to be cheap.
Moving the check to the desk, before submission
The fix is structural: enforce the guideline where and when the entry is created, not after it leaves the building.
This is what Timentry is built to do. Timentry enforces compliance rules before submission — outside-counsel guidelines, prohibited task codes, and billing rules are configured per client and checked at the point the entry is prepared. An entry that would be rejected by an e-billing portal is flagged at the desk, so it can be corrected before the invoice goes out rather than after it comes back.
Two other parts of the product make that check more effective:
- AI-drafted narratives. Timentry's AI activity-clustering layer drafts a specific, review-ready narrative from the day's captured activity on a matter, which reduces the vague-description rejections that thin, from-memory entries produce. You review and edit every draft before anything is submitted.
- Deterministic matter attribution. Because activity is matched to the right matter automatically — using matter numbers, sender domains, and names, with AI only as a fallback — the client whose guideline applies is known, so the correct ruleset is the one being checked.
The effect is not that rejections become impossible; a portal can still reduce a line for reasons outside any tool's view. The effect is that the predictable, rule-based rejections — the block-billed line, the prohibited code, the increment breach — are caught before they ever reach the client.
The bottom line
E-billing rejections are mostly not billing accidents; they are timing failures. The rule was checkable at the desk and got checked at the portal instead. Every rejection that a firm catches before submission is a billing cycle saved and a write-off avoided — and, over a year of OCG-governed work, that difference shows up directly in the realisation rate. For how realisation is calculated and why uncaptured time undermines it, see How to Calculate Billable Hours and Realization Rate.
This article describes common e-billing and OCG practices for educational purposes and is not legal or compliance advice. Specific guideline requirements vary by client and jurisdiction; always follow the applicable engagement terms.
To see compliance enforcement work against your own clients' guidelines, see how Timentry works or talk to the team.