Why Legal Invoice Deductions Happen and How to Prevent Them Before Prebill

A lawyer can perform necessary work, record the right amount of time, and still have the resulting invoice reduced. The work may be legitimate while the entry fails a client’s billing agreement. Or the entry may be perfectly written while the client disputes the staffing, scope, rate, or necessity of the work.

Those are different problems, and they require different remedies.

The most useful way to reduce legal invoice deductions is not to treat every adjustment as a writing problem. It is to identify where the defect entered the revenue cycle, then move the appropriate control as close to that point as possible. For entry-level problems (such as block billing, vague narratives, incorrect codes, and prohibited activities), that often means checking the work before the timekeeper approves it, not waiting for prebill.

Start by naming each kind of reduction

Firms do not always use billing terms consistently. Before analyzing deductions, establish definitions that match the firm’s accounting and billing systems.

This separation prevents a misleading conclusion. If client deductions decline only because partners write down more value before submission, the firm has moved the reduction rather than necessarily improving the result.

It also avoids describing every internal write-down as “lost revenue.” Some work was not authorized, reasonable, or contractually billable in the first place.

Five reasons legal invoices get reduced

1. The entry does not describe the work clearly

Common entry defects include:

• combining distinct tasks in one block-billed line;
• using a vague narrative that does not explain what was done or why;
• selecting a task or activity code the narrative does not support;
• assigning the entry to the wrong client or matter;
• using an increment or rounding practice the agreement prohibits; and
• disclosing information that does not belong on an invoice.

These problems are often addressable while the work is fresh. For an insurance-defense example, The Hartford’s published billing guidelines call for separate tasks, sufficient detail, and actual time recorded in tenths. A timekeeper who can still remember the purpose and boundaries of the work is in a much better position to correct an entry than a billing professional reviewing it weeks later.

2. The work conflicts with a client rule or authorization

Outside counsel guidelines can govern staffing, billable activities, narrative content, codes, increments, prior approvals, budgets, rates, and expenses. The Association of Corporate Counsel’s OCG practices illustrate how broad those agreements can be.

A reduction may follow when an unapproved timekeeper performs the work, several people attend without authorization, a restricted activity is billed, or work exceeds an agreed scope or budget. No universal checklist can replace the client’s actual engagement terms and current guidelines.

Some of these issues can be detected from an individual entry. Others require facts that are not present there: a prior-approval record, a matter budget, a staffing plan, a negotiated rate, or a documented exception. The latter need separate operational controls and human judgment.

3. The invoice fails technical validation

An otherwise sound entry can be returned because of an invalid matter ID, missing field, incorrect date range, duplicate invoice number, unsupported code, malformed LEDES file, or late submission. The FDIC’s legal-invoice validation criteria show how structural checks can delay or reject an invoice before anyone evaluates the legal work. The LEDES 1998B specification likewise defines a structured e-billing format with required fields.

These are invoice-generation and submission controls. Improving a narrative will not repair a malformed file or meet a missed deadline.

4. The client disputes reasonableness or necessity

Clients may question whether work was necessary, whether its duration was reasonable, whether effort was duplicated, or whether the staffing choice was efficient. They may also make an incorrect adjustment that the firm should appeal.

The ABA’s Model Rule 1.5 addresses reasonable fees and expenses and communication of the basis or rate. Software can preserve a better record and flag a documented rule. It cannot make unauthorized, unnecessary, or unreasonable work payable, and it cannot guarantee that a reviewer agrees with the firm.

5. The billing workflow corrects problems too late

Repeated deductions often expose a process problem:

• lawyers reconstruct time after task boundaries and context have faded;
• guidelines sit in PDFs or inboxes apart from the entry workflow;
• prebill reviewers fix the same defects without returning the reason to the timekeeper;
• rule ownership is unclear; or
• adjustments are recorded as undifferentiated dollar reductions.

Prebill remains an important control. But it is a costly first checkpoint for facts that were easier to verify when the entry was created.

Decide whether to prevent, review, or appeal

Billing leaders can assign each recurring reason to the stage where it can actually be controlled.

This matrix also sets realistic expectations for technology. A point-of-entry system should not claim responsibility for controls that depend on a complete invoice, a matter budget, or events after export.

What prevention before prebill looks like

Hourglass is designed around the portion of this problem that begins with the time entry.

First, it builds a record of supported work as it happens so the timekeeper is not reconstructing the day from memory alone. It can use evidence across applications to draft a duration, client, matter, narrative, and task and activity codes. When evidence is insufficient, a field can remain blank for the user rather than receiving a fabricated answer.

Second, Hourglass can evaluate the proposed entry against configured guidelines. A firm can upload an OCG and turn it into candidate rules, but a person must verify and approve those rules before activation. Rules can apply at the firm, client, or matter scope. For supported entry-level checks, Hourglass can explain the issue and suggest a correction; administrators decide whether a rule warns or blocks release.

Third, the timekeeper remains responsible. The user can edit, split, merge, reject, or add to the draft. No entry reaches the billing system without human approval.

The boundary matters just as much as the capability. Hourglass does not currently check expenses, negotiated rates, or budgets. It does not perform controls that require comparison across multiple entries, the full matter, or the assembled invoice. Nor does it decide whether the underlying legal work was strategically necessary or reasonably staffed.

After approval, Hourglass sends the entry to the firm’s billing system. Billing systems generally do not send Hourglass structured client deductions, appeals, or collection outcomes in return; those processes are usually manual. Hourglass therefore should not be treated as a native end-to-end source for downstream deduction or realization reporting.

Measure the whole path, not one percentage

To learn whether prevention is working, establish a baseline before changing the process. Keep these values separate:

1. worked or recorded value;
2. internal prebill write-downs;
3. submitted value;
4. gross client deductions;
5. successful appeal recoveries;
6. final billed value; and
7. collected value.

Normalize reasons into categories such as entry quality, coding, staffing, rate, expense, budget, authorization, invoice format, timeliness, reasonableness, duplicated effort, and reviewer error. Compare similar clients, matters, fee arrangements, timekeepers, and periods. Track correction time for billing staff and partners separately from financial outcomes.

Most importantly, watch for displacement. Lower post-submission deductions paired with higher prebill write-downs are not automatically an improvement. Neither is a projection of captured activity equivalent to collected revenue.

Firms exploring the economics can use the Hourglass impact calculator to model their own timekeeper counts, rates, hours, and deductions after appeals. Its output is directional; a real business case should add the firm’s software, integration, service, and internal implementation costs.

A practical deduction audit

Start with the last three to six billing cycles and ask:

• At what stage did each reduction occur?
• What normalized reason caused it?
• Was the issue visible from one proposed time entry?
• Which client rule or engagement term governed it?
• Could the timekeeper have corrected it before approval?
• Did the fix require rate, expense, budget, matter, invoice, or submission data?
• Was the reduction appealed, and what was recovered?
• Did the same defect appear again?

The goal is not to eliminate every adjustment. It is to stop making prebill the first place the firm discovers preventable entry defects and to preserve partner judgment for the questions only people can answer.