LEDES Billing Format Explained

LEDES stands for Legal Electronic Data Exchange Standard, a set of file formats that allow law firms to send invoices to corporate clients as structured, machine-readable data. Where a PDF has to be read by a person, a LEDES file presents every line item as coded fields an eBilling platform can validate automatically against billing guidelines, approved rates, and matter budgets. Understanding the LEDES billing format matters to anyone configuring or supporting an eBilling deployment, because most invoice rejections trace back to how the file was built.

Who maintains the LEDES standard?

The LEDES standard is maintained by the LEDES Oversight Committee, an independent body that has governed it since the 1990s. For context, billing data from about 400 law firms shows invoice rejection rates climbed from 11 to 18 percent in 2025. The initiative began as an industry-wide project led by PricewaterhouseCoopers and was later incorporated as a nonprofit, now directed by a board.

That independence is the reason the format works. Because no single vendor controls it, corporate legal departments running different eBilling platforms can require the same file structure from the same law firms, and firms can generate one format that satisfies many clients.

The committee also maintains the code sets that give the data meaning, including activity codes, expense codes, and timekeeper classification codes, alongside the UTBMS task code sets used to categorize legal work.

Which LEDES formats exist?

Four LEDES formats matter in practice, and the differences affect what an implementation can support.

• LEDES 1998B. An ASCII, pipe-delimited file containing 24 fields per line item. LEDES.org describes it as the most widely used ebilling standard in the US legal industry, and the committee has stated it does not intend to modify the format further.
• LEDES 1998BI. The international variant, ratified in 2006 after being proposed by the Legal IT Innovators Group. It extends 1998B with additional fields covering tax handling and address information, which makes it the practical choice outside the United States.
• LEDES XML 2000. An older XML format that permitted client-specific extensions. It is no longer supported by the committee.
• LEDES XML 2.x. The more recent XML family, supporting richer data structures than the pipe-delimited formats allow.

Version selection is a scoping decision on any eBilling implementation. A single-jurisdiction US deployment can usually standardize on 1998B. A program spanning multiple countries with tax obligations needs 1998BI or an XML format, and that decision affects vendor onboarding instructions for every firm on the panel.

What does a LEDES 1998B file actually contain?

A LEDES 1998B file contains twenty-four fields per line item, covering invoice-level information, matter identifiers, timekeeper details, and the line item itself. Reading it is closer to reading a spreadsheet saved as plain text than reading an invoice.

The fields group into four sets.

• Invoice level. Invoice date in YYYYMMDD form, a unique invoice number, billing period start and end dates, and invoice totals.
• Identifiers. Client ID, law firm matter ID, and the client’s own matter identifier, which is how the invoice attaches to the right matter in the client’s system.
• Timekeeper. Timekeeper ID, name, classification, and rate. The committee’s classification codes cover partner, associate, of counsel, legal assistant, and other.
• Line item. Date, task code, expense code, activity code, units, unit cost, adjustment amount, and line total, plus whether the entry is a fee or an expense.

Most eBilling platforms publish file specifications for the LEDES formats they accept, and those specifications are the reference to work from when mapping fields during an implementation.

Why do LEDES files fail validation?

LEDES files fail validation because the format is strict and several fields are mandatory. A file that looks correct in a text editor will bounce if a required field is empty or wrongly structured.

The recurring causes are consistent across deployments.

• Missing mandatory fields. Invoice date, invoice number, client and matter identifiers, line item date, and line total all reject when null.
• Arithmetic mismatch. Each line item total must equal unit cost multiplied by units, plus any adjustment. Rounding differences fail.
• Missing task codes on fee lines. Fee entries require a task code and timekeeper ID. Expense entries require an expense code.
• Unauthorized codes. A task code the client has not approved for that matter type rejects even when the code is valid UTBMS.
• Date format errors. Dates must be YYYYMMDD, and regional date formats are a frequent cause of failure in multinational deployments.
• Duplicate invoice numbers. Invoice numbers must be unique per firm.

Most of these originate on the firm side during invoice generation, which is why vendor onboarding matters as much as platform setup on an eBilling rollout. That balance is covered in what an Onit eBilling implementation involves.

How do UTBMS codes relate to LEDES?

UTBMS codes are the vocabulary. The file is the container. The Uniform Task-Based Management System provides standardized codes for tasks, activities, and expenses, and the file carries those codes in specific fields.

Task codes describe what the work was, such as case assessment or discovery. Activity codes describe how it was performed, such as drafting or reviewing. Expense codes categorize disbursements. Coding is what allows a legal department to compare spend across firms and matters, because it converts free-text narratives into categories a system can group.

This is also where a common configuration decision arises. Clients specify which UTBMS code sets apply to which matter types, and a firm submitting a code outside that authorized set produces a rejection. Communicating that authorized list to firms during onboarding prevents a predictable early rejection cycle.

Why does the format matter for spend analytics?

The LEDES billing format matters for spend analytics because structured data is what makes reporting possible. Invoices arriving as PDFs give a legal department a payment record. Invoices arriving as structured files give it a dataset.

Standardized LEDES data supports reporting on total legal spend, spend by matter type, timekeeper utilization, average hourly rates by firm and practice area, budget variance, and invoice processing time.

None of that reporting works if the underlying data is inconsistent. Historical invoice data migrated without cleansing produces analytics nobody trusts, a pattern covered in why messy legacy data can ruin a perfect platform build.

What are the limitations of the LEDES billing format?

Two LEDES limitations are worth knowing before scoping a deployment. LEDES 1998B repeats invoice-level data on every line item even though it does not vary, which makes files larger than necessary. And the format does not natively handle tax or alternative fee arrangements, which is why international deployments move to 1998BI or an XML format.

A third issue is behavioral. Clients sometimes impose non-standard customizations on the format, which defeats the purpose of having a standard and creates work for every firm that has to accommodate the variation. Resisting that during an implementation is worth the effort, since each customization becomes a permanent onboarding cost for every new firm.

How does LEDES fit into an eBilling implementation?

The LEDES billing format sits as the interface between two configuration exercises. On the client side, billing guidelines become rules the platform evaluates against LEDES fields. On the firm side, the billing system has to generate files that satisfy both the format and the client’s authorized codes.

Firms submit through a vendor portal, and how that portal is configured governs how clean the first billing cycle looks. The portal side is covered in how firms use Counsel Exchange, Onit’s vendor portal, and the rules side in turning outside counsel billing guidelines into enforceable rules.

Testing deserves emphasis here. A real LEDES file from an actual firm exposes formatting behavior that a synthetic test file will not, which is why test cycles should use genuine submissions from the firms that will be billing.

Conclusion

The LEDES billing format is unglamorous infrastructure, and it is the reason legal spend management works at all. It converts an invoice from a document someone reads into data a system can check, which is what makes automated guideline enforcement, rate validation, and spend analytics possible.

For anyone implementing or supporting eBilling, three things follow. Choose the version deliberately at scoping, since tax handling and international requirements rule out 1998B for many programs. Communicate the authorized UTBMS code sets to firms during onboarding, because unauthorized codes cause a predictable early rejection cycle that damages confidence on both sides. And resist non-standard customizations, since each one becomes a permanent cost carried by every firm on the panel.

Frequently asked questions

What does LEDES stand for?

LEDES stands for Legal Electronic Data Exchange Standard. It is a set of file format specifications that allow law firms to submit invoices to corporate clients as structured, machine-readable data, maintained by the LEDES Oversight Committee.

What is LEDES 1998B?

LEDES 1998B is an ASCII, pipe-delimited file format containing 24 fields per line item. LEDES.org describes it as the most widely used ebilling standard in the US legal industry, and the committee has stated it does not intend to modify the format further.

What is the difference between LEDES 1998B and 1998BI?

LEDES 1998BI is the international variant, ratified in 2006. It builds on 1998B with additional fields covering tax handling and address information, which makes it the practical choice for deployments outside the United States where tax treatment must be carried on the invoice.

Why do LEDES invoices get rejected?

Most rejections trace to mandatory fields left empty, line item arithmetic that does not reconcile, missing task codes on fee lines, task codes the client has not authorized for that matter type, dates not in YYYYMMDD format, or duplicate invoice numbers.

What are UTBMS codes?

UTBMS stands for Uniform Task-Based Management System. It provides standardized codes for tasks, activities, and expenses that are carried within specific LEDES fields. The codes convert free-text narratives into categories a system can group, which is what enables spend comparison across firms and matters.

Do all corporate clients require LEDES invoices?

Not all, though most large corporate legal departments and many government entities require outside counsel to submit in a LEDES format. Which version they require varies, and firms working across several clients often need to generate more than one.

---

*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*