Attorneys

What is the Legal Electronic Data Exchange Standard (LEDES)?

You finished the work. The client is a bank, a technology company, an insurer, or maybe another law firm. Billing builds the invoice the way your firm always has: your template, your layout, your way of describing the hours. It goes out.

Here is the catch many people miss: that client usually does not pay from a Portable Document Format (PDF) file in someone's inbox. Large organizations require outside counsel to submit bills through an electronic billing (e-billing) system. That is a vendor portal or internal tool that checks whether the invoice is structured the way the client expects before accounts payable releases a dollar.

Two weeks later, that system rejects your bill. The message cites a code or field rule nobody at your firm recognizes. Payment stops. Now you're trading emails with billing, your tech team, and the client's accounts payable contact. What does this mean? Did we use the wrong task code? It looked fine to us.

Next month a different client, with a different vendor, rejects a different bill for a different reason. Or someone on their side retypes your hours by hand while your cash waits. Every round trip is time you should have spent practicing law.

There had to be a better way.

There was. Those e-billing systems were never built to read your firm's template. They were built to read a shared invoice language. The Legal Electronic Data Exchange Standard (LEDES) is a standard for structuring, sending, and receiving electronic legal invoices, so firms and corporate clients can exchange billable work in a form that e-billing systems can check for proper industry codes and structure (validation), send to the right place the first time (routing), and pay with limited friction, without reinventing the invoice for every relationship. Paired with the American Bar Association's Uniform Task-Based Management System (UTBMS), a shared vocabulary of line-item codes, you can understand and align with industry standards for every invoice you submit, restructure, and get paid on.

With LEDES and UTBMS on your side, a rejection stops being a mystery. The code points to a rule you can look up. The fix is specific. The resubmitted bill matches what the client's system expects, and it gets paid.

What is lybra.dev?

Here is the next catch: the standard exists, but it lives in committee documents, spreadsheets, and PDFs. That is what billing ends up digging through at 4 p.m. while a payment sits frozen. lybra.dev is the readable, maintained home for LEDES codes and format rules. Your team starts from a clear answer instead of a downloaded file.

Why do you need it?

When a portal kicks a bill back, you get one place that explains what the rejection means, and one link to send your tech team or e-billing vendor so everyone works from the same reference. That is easier. Shared LEDES and UTBMS language means fewer wrong or missing codes on the next submission. That is better work. Fewer rejection loops mean faster payment, more hours on the matter, and fewer on portal archaeology. That is efficiency your clients feel too.

No lookup can force a particular bank's or insurer's system to accept a particular bill. Clients add house rules, upstream data can be wrong, and your professional judgment remains yours. See our Terms of Service.

What can you do with it?

Look up code families and format rules. See exactly why a rejection points at a standard code. Send your tech team or e-billing vendor a link so everyone is reading the same page.

Next on the roadmap is convert and send. You will be able to upload a messy invoice and get back a LEDES-formatted bill ready to deliver.

How do you get started?

Read Getting started for the plain-language overview. Forward Pricing to whoever runs systems at your firm and ask for a sandbox key. Or schedule a free 15-minute consultation — Consulting and Add It to Leads are scoped on that call. The next time a rejection lands, start here.