What Is LEDES, and Why Does Your E-Billing Vendor Keep Asking About It?
Most e-billing rollouts stall on one question: which LEDES billing format and UTBMS codes to require. Here's how to choose, when 1998B won't cover a cross-border panel, and which invoice errors cause rejections.
The question behind your vendor's questions
Roll out an e-billing platform, or join a client's panel as a law firm, and the same question arrives within the first week: which LEDES billing format will you accept or send, and which UTBMS code sets go with it? It sounds like an IT detail. It isn't. The answer decides whether invoices load automatically or bounce, whether tax shows up correctly for finance, and whether your spend reports still mean something a year from now.
LEDES (Legal Electronic Data Exchange Standard) is a set of file formats for legal invoices, maintained by the LEDES Oversight Committee. A LEDES file turns an invoice into structured data. Each line carries a timekeeper, date, hours, rate, amount, task code and activity code, so a billing system can check it against rules without anyone retyping it. Your vendor keeps asking because its validation rules, rate checks and reports all run on those fields. Pick the wrong format, or let each firm pick its own, and the platform can't do its job.
The formats you will actually choose between
There are several LEDES specifications. Buyers realistically choose among three families.
| Format | Structure | Tax handling | Currency | Best fit |
|---|---|---|---|---|
| LEDES 1998B | Pipe-delimited text, one line per fee or expense | Minimal; no proper line-level tax fields | Single, implied | Domestic panels with no VAT/GST to report on the invoice |
| LEDES 1998BI (international) | Pipe-delimited, extra fields | Tax type, rate and amount per line | Currency code included | Panels that need tax data but include firms with basic billing systems |
| LEDES XML 2.x | XML, nested structure | Detailed; supports multiple tax types | Multi-currency supported | Cross-border panels, large firms, complex tax regimes |
Other specifications exist, including timekeeper and rate formats, budget formats and older XML versions. Most corporate legal departments never mandate them. The real choice is whether 1998B is good enough or you need something that handles tax and currency.
Why LEDES 1998B still dominates
LEDES 1998B is decades old and still the default on most e-billing platforms. That's not inertia. Nearly every law firm time-and-billing system can export it, from enterprise suites such as Elite 3E and Aderant to cloud practice management tools such as Clio. Small firms without a native export can often produce the file with converter tools. Require 1998B and you exclude almost nobody.
It's also easy to troubleshoot. The file is plain text with pipes between fields, so a billing coordinator can open it and spot a missing matter ID by eye. When an invoice is rejected, you can see why without calling a developer.
Its weakness is everything beyond a simple domestic fee invoice. 1998B has no proper place for line-level VAT or GST, no explicit currency field, and little room for addresses and tax registration numbers. Firms work around that by adding tax as a separate expense line or an invoice-level lump. The invoice loads, but your tax and spend data come out wrong.
Our position: if your outside counsel mostly bill in one currency with no invoice-level tax to report, require 1998B and stop. XML adds friction for firms and gives you nothing you'd use.
Where LEDES XML earns its complexity
Things change once your panel crosses borders. Say a hypothetical 60-lawyer in-house team uses firms in London, Frankfurt, Singapore, Mumbai, Dubai and São Paulo. Those invoices carry VAT, GST and local service taxes, in five or six currencies. Under 1998B, each firm squeezes tax into its own workaround, and your reports mix pounds, euros and rupees in one column.
LEDES XML was built for this case. It carries tax type, rate and amount at line level, supports more than one tax per invoice, records currency explicitly and has fields for both parties' tax identifiers. Your platform can then validate tax math, convert currencies consistently and give finance something it can reconcile.
The cost is adoption. Many mid-sized and smaller firms can't generate valid XML natively, especially outside North America and the UK. That's why many international panels take a middle route: 1998BI as the baseline, XML from firms that can produce it. Before you mandate anything, ask your vendor which formats it actually parses and validates, not just which it lists on a spec sheet.
One caveat matters. A LEDES file is a data feed, not a statutory tax invoice. Where e-invoicing or invoice-content mandates apply, such as India's GST e-invoicing, Saudi Arabia's ZATCA regime, Mexico's CFDI and the e-invoicing rules being phased in across the EU, firms may still have to issue a separate compliant invoice. Ask a tax advisor in each relevant country how the two documents fit together.
Choosing UTBMS code sets without overreaching
UTBMS (Uniform Task-Based Management System) codes tell you what the work was. Task codes cover the phase or type of work, activity codes cover what the timekeeper did, and expense codes classify disbursements. The litigation set is the most widely used. Separate sets cover counseling, projects, bankruptcy and intellectual property.
The usual mistake is requiring too many sets, or requiring task codes where they don't fit. Force litigation codes onto an M&A matter and everything lands in a catch-all code, which makes the data useless.
- Activity and expense codes: require them on every matter. They're universal and cheap for firms to apply.
- Litigation task codes: require them on disputes matters.
- Counseling or project codes: require them only if someone will actually run reports on them.
- Custom codes: avoid them without a clear reporting need. Every custom code is something each firm configures by hand.
Rule of thumb: if nobody on your team can name the report a code set feeds, don't require it.
The invoice errors behind most e-billing rejections
Most rejections come from a short, predictable list. Firms that know it fix problems before submitting. Departments that know it can write billing guidelines that prevent them.
- Totals that don't reconcile. The invoice total differs from the sum of the lines, usually from rounding, a discount applied at the wrong level, or tax added outside the line structure.
- Timekeeper or rate mismatches. A timekeeper isn't on the approved list, or bills above the approved rate. Often it's a rate increase the client never approved.
- Invalid or missing UTBMS codes. A code from the wrong set, a retired code, or a blank field.
- Dates outside the billing period. Lines dated before the matter opened or after the invoice period ended.
- Wrong matter or client identifiers. The firm uses its own matter number instead of the client's.
- Duplicate invoice numbers. Usually a resubmission without a revised number.
- File format faults. A missing header, the wrong number of fields, stray pipe characters in narratives, or encoding problems with non-English characters.
- Guideline violations. Block billing, vague descriptions, disallowed expenses. The file is technically valid but breaks the client's rules.
Format faults and identifier errors are the cheapest to eliminate. A firm that validates files before submitting, using its billing system's checks or the platform's test upload, avoids most first-pass rejections.
What LEDES compliance actually costs
The standard itself is free. You pay for the systems around it. The figures below are typical 2026 market ranges; they vary widely by contract, region and volume, so confirm with vendors.
- Corporate e-billing and matter management platforms such as Brightflag, Thomson Reuters Legal Tracker, Wolters Kluwer ELM Solutions, Onit, Mitratech and LawVu: roughly USD 15,000–60,000 a year for smaller departments, and well above USD 100,000 for large global deployments. Implementation fees come on top.
- Firm-side submission fees: some platforms charge law firms per invoice or a small percentage of billed value. Firms should ask before signing panel terms.
- LEDES converter tools for small firms: often USD 20–100 per user per month, or a per-file fee.
- Internal effort: mapping UTBMS codes in the billing system, training timekeepers and handling rejections. For firms, this is usually the largest cost.
XML requirements raise costs mainly on the firm side. Weigh that if you rely on smaller local counsel in many jurisdictions.
Red flags when vendors answer the LEDES question
Whether you're a department evaluating a platform or a firm evaluating a client's requirements, these answers should slow you down.
- The vendor says it supports XML but can't show line-level tax validation on a sample invoice.
- Rejection messages are generic ("invalid file") instead of naming the field and line.
- There's no test or sandbox upload for firms to validate files before going live.
- Multi-currency is handled by converting at receipt, with no record of the original currency.
- The platform requires custom code sets in its default configuration.
- Nobody can say how it handles invoices from countries with statutory e-invoicing rules.
A decision rule you can take into the next vendor call
Start with where your firms are and how they tax their invoices. If the large majority of your spend is single-currency with no invoice-level VAT or GST, require LEDES 1998B with activity, expense and litigation task codes, and revisit in two years. If you have material spend across tax regimes or currencies, require 1998BI as the floor, accept XML where firms can produce it, and ask your vendor to show tax validation on real sample files from three of your firms before you sign.
Either way, publish the format, the code sets and the top rejection rules in your billing guidelines before the first invoice is due. Most rejection cycles happen because firms learned the rules after their first invoice bounced.
Questions buyers ask
Is LEDES a legal requirement?
No. LEDES is a voluntary industry standard. Clients impose it through billing guidelines and engagement terms, not regulators. It also doesn't replace a statutory tax invoice where local law requires one, so check with a tax advisor in each country where you bill or are billed.
What is the difference between LEDES 1998B and 1998BI?
Both are pipe-delimited text formats. 1998BI adds fields for currency, tax type, tax rate and tax amount, along with party details that international invoices need. If your panel bills VAT or GST, 1998BI gives cleaner data than forcing tax into 1998B workarounds.
Should we require LEDES XML from all our firms?
Usually not. XML is worth requiring when you have significant cross-border spend with multiple currencies and taxes, and your firms can produce it reliably. Many departments accept 1998BI as the baseline and XML as an option, so smaller local counsel aren't shut out.
Do UTBMS codes work for non-litigation matters?
Yes. There are separate code sets for counseling, projects, bankruptcy and IP. Activity and expense codes apply to nearly any matter. Require only the task code sets you'll report on, because mismatched codes produce data you can't use.
Why do invoices get rejected when the LEDES file looks correct?
A file can be structurally valid and still break the client's rules. Common causes are unapproved rates or timekeepers, dates outside the billing period, or block-billed entries. The rejection message should name the rule. If it doesn't, ask the vendor for field-level error reporting.
Who pays for e-billing: the client or the law firm?
It depends on the platform and contract. The legal department usually pays the license fee. Some platforms also charge firms submission fees per invoice or a percentage of billed value. Firms should confirm any fees before accepting panel terms, and departments should know whether their vendor charges firms.
Written by the Counsel Ops HQ editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.