LEDES Billing: Formats, UTBMS Codes, and Rejections

What Is LEDES Billing?

LEDES billing is the practice of submitting a law firm invoice in the Legal Electronic Data Exchange Standard (LEDES) format instead of a PDF or a paper bill. Before LEDES, every law firm's billing system produced invoices in whatever format that system happened to generate, and every client that wanted electronic data had to build a separate import routine for every firm it worked with.

The standard is maintained by the LEDES Oversight Committee (LOC), a non-profit standards body that publishes the file specifications every major e-billing platform and corporate legal department builds against. When a client, an insurance carrier, or a corporate legal department requires LEDES billing, the firm has to export its invoice as a structured file the receiving system can parse and validate automatically, line by line, rather than a document a person reads and re-keys by hand.

A LEDES file is a data file with a fixed field structure: timekeeper, task code, activity code, expense code, hours, rate, and a narrative, each in its own place. A carrier's or corporate legal department's bill review software reads those fields directly and applies rules against them before a person ever opens the bill. A firm that submits a PDF where a LEDES file is required has produced a file the receiving system cannot read at all.

Why the LEDES Standard Exists

Before LEDES, every law firm's billing system produced invoices in whatever format that system happened to generate, and every client that wanted electronic data had to build a separate import routine for every firm it worked with.

Two projects ran in parallel to fix that. In the mid-1990s, a joint group from the American Bar Association, the Association of Corporate Counsel, and PwC built Uniform Task-Based Management System (UTBMS), the coding system that describes what a legal invoice line actually covers. A second effort, a cross-industry consortium led by PwC, worked on a standard file format for exchanging that billing data. The coding project disbanded once UTBMS was complete. The format group became the LEDES Oversight Committee, which still governs the standard today.

The LEDES File Formats, Explained

LEDES billing format is not one file type. The LOC maintains several, and which one a firm needs depends entirely on what the client's e-billing platform or outside counsel guidelines specify.

For most firms the working question is not which format is best. It is which format the specific client already requires, since a carrier's bill review system or a corporate legal department's e-billing platform is built to accept one or two of these and reject the rest outright.

How a LEDES Billing File Moves From Time Entry to a Paid Invoice

A LEDES file is the last step in a chain that starts the moment an attorney logs time. Each entry gets attributed to a matter and coded with a task, an activity, and, where relevant, an expense code. The firm's billing system compiles a matter's coded entries into an invoice, then exports that invoice in whichever LEDES format the client's guidelines specify. The client's carrier or corporate legal department feeds the file into its own bill review software, which validates every line against both the LEDES specification itself and the client's own billing rules before a reviewer sees it. Lines that pass post for payment. Lines that fail get flagged, reduced, or rejected outright, and sent back to the firm for correction or appeal.

That last step is where LEDES stops being a formality: a rejection notice that names a line item and a reason code, with no context beyond that. Every flagged line delays payment on finished work, and every reduced line is a write-down that lowers realization on revenue the firm already earned.

Where UTBMS Codes Fit Inside a LEDES File

LEDES and UTBMS solve two different problems, and confusing them is where a lot of the friction starts. LEDES is the container: the file structure, field order, and delimiters that let a receiving system parse a bill automatically. UTBMS, the Uniform Task Based Management System, is the vocabulary that fills specific fields inside that container.

A LEDES file without correct UTBMS codes in its coded fields can be technically well formed and still get rejected, because the codes are what let a bill review system judge whether the work matches the guideline on file.

What Carrier Bill Review Rejects

Most LEDES rejections trace back to a small set of causes, and the LOC's own standardized error codes group them the same way carrier and corporate bill review systems already do: fatal errors that reject the whole file, validation errors that check a value against the client's own rules, and procedural errors that flag a billing practice the guideline prohibits outright.

How to Prevent a LEDES Rejection Before You Submit

For most of the table above, the effective fix is catching the problem at the point an entry is written, rather than at pre-bill or after a rejection notice arrives.

• Confirm the LEDES format and UTBMS code set a client requires before work starts on the matter, not when the first invoice is due.

• Write narratives that name the specific work at the time of entry. A narrative rebuilt from memory days later tends to default to the same vague language bill review flags.

• Select the phase, task, and activity code at the point of capture rather than during invoice review.

• Reconcile timekeeper rates against the client's approved schedule before export, not after a rejection names the mismatch.

• Treat pre-bill and proforma review as the last catch, not the only one.

• Read the client's outside counsel guidelines for task-based billing and narrative-detail requirements before the first entry is written, and hold each narrative to what a defensible narrative needs to include.

A firm that fixes coding and narrative quality at the point of entry sees fewer of these five reasons show up in a rejection notice at all, and more of each month's fees paid in the cycle they were billed.

Can AI Time Capture Reduce LEDES Rejections?

Automated time capture applies the outside counsel guidelines a firm's clients impose, including the task and activity codes and narrative detail a client's LEDES submission depends on, at the point a time entry is created rather than after it.

PointOne Time captures billable work across email, documents, calls, and web activity, and drafts a complete entry before an attorney has to write one from scratch. PointOne Rules ingests the client guidelines a firm operates under and applies them automatically to every entry as it is generated and every pre-bill as it is reviewed, enforcing the correct code set and narrative detail and flagging block billing before it reaches a bill. PointOne Review acts as an AI billing copilot during pre-bill, catching what makes it through.

FAQs about LEDES Billing