LEDES 1998B Explained: What Corporate Clients Actually Expect From Your Invoices

I want to start with something that happened to a firm I was talking to a few months back, right, because it explains the whole reason this post needs to exist. They had done about six weeks of work for a mid sized manufacturer, real work, discovery review, a couple of depositions, the kind of matter that generates a genuinely large bill, and they sent over an invoice that looked completely professional, a clean PDF, itemized by date and by biller, the sort of invoice that would satisfy basically any individual client on earth. And the general counsel's office bounced it without even reading it closely. Not because the number was wrong, not because the work wasn't done, but because the e-billing platform their legal department runs its payables through, the CounselLink and Legal Tracker and Brightflag type of system that most corporate law departments and insurance companies use now, only accepts invoices in a specific machine readable format called LEDES 1998B, and a PDF simply is not that file, no matter how clean it looks. So the firm had to go back and reconstruct six weeks of billing by hand into a pipe delimited text file with a fixed set of fields in a fixed order, and that reconstruction alone pushed payment out by close to three weeks. That is basically the whole reason this post exists, and I want to walk through what LEDES 1998B actually is, why corporate clients insist on it, and what your billing system actually needs to do so this never happens to your firm.

What LEDES 1998B actually is, in plain terms

LEDES stands for Legal Electronic Data Exchange Standard, and 1998B is the version most corporate legal departments and insurers are still running on today, even though newer XML versions exist, mostly because 1998B is simple enough that every e-billing platform on the market still accepts it and most firms' systems can still produce it. At its core it is a flat text file, pipe delimited, meaning every field on every line is separated by the "|" character instead of commas or tabs, and every line item on your invoice, meaning every single time entry and every single expense, has to show up as its own row with around 26 required fields filled in correctly. Things like the invoice number, the client and matter ID exactly as the corporate client has it recorded on their side, the billing date range, the timekeeper's name and ID and classification such as partner or associate or paralegal, the task code and activity code under something called UTBMS, and the line item total. For instance a single hour of litigation research by an associate does not just show up as "1.0 hrs, legal research, $450." It shows up with a task code like L120 for fact investigation, an activity code like A103 for drafting, the associate's timekeeper ID matching what is on file with the client, and a line item description, all sitting in the exact field position the format expects. Get one field out of order or leave one blank and the whole invoice can bounce.

Why corporate clients require this instead of just asking nicely for it

Let me be very honest about the actual reason here, because it is not bureaucracy for its own sake. A general counsel's office or an insurance company's claims department is often managing outside counsel spend across dozens or hundreds of law firms at once, and the only way to compare what firm A charged for deposition prep against what firm B charged for the same kind of work, or to catch a paralegal being billed at an associate rate, or to enforce a billing guideline like "no more than two timekeepers on a single call," is to have every invoice arrive in the same structured format so their software can actually parse it. A PDF is readable by a person but it is basically useless to a machine trying to sum up litigation spend by task code across a portfolio of matters. So the requirement is not about making your life harder, it is about the client's ability to run their legal spend the way a finance department runs anything else, with structured data they can audit and benchmark, and if your firm cannot produce that structured data on demand, you are functionally harder to work with than a competing firm that can, even if your hourly rate is lower.

What corporate e-billing systems are actually checking for

It helps to know what the receiving end is actually validating, because this is where most rejections come from and it is rarely the invoice total. Here is roughly what a corporate e-billing platform checks the moment your file lands.

How Casely actually gets a firm to that file without the manual work

This is the part I actually built, so let me walk through the mechanics rather than describe it in the abstract. Inside Casely, every hour an attorney logs against a matter sits as unbilled time until someone clicks "Bill Unbilled Time," and that one click turns every unbilled hour on that matter into a numbered, itemized draft invoice in a single pass, no retyping, no spreadsheet in between. Once an hour has been billed it is marked automatically so it can never be pulled into a second invoice by accident, which matters a lot here because a duplicated line item is exactly the kind of thing a corporate audit catches and flags your firm for. Invoice numbering is automatic and sequential with no gaps, which sounds small until you remember that a gap in invoice numbering is one of the first things an e-billing platform's validation layer checks for. And when the client on the other end needs the file in LEDES 1998B rather than a normal invoice, the export sits right there as an option, pulling the client and matter ID, the timekeeper classifications, and the task codes straight out of the data that was already attached to the time entries when they were logged, instead of asking a paralegal to reconstruct all of it after the fact.

Why this only works if your billing system handles more than one billing model

Here is the catch here, and it is one a lot of billing software gets wrong. Not every matter at your firm is a corporate hourly matter running through an e-billing platform. You might have a personal injury matter on contingency, a trademark filing on flat fee, and a corporate litigation matter that absolutely needs a LEDES 1998B export, all open at the same firm on the same day, sometimes handled by the same associate. Casely puts the billing type, hourly or flat fee or contingency, on the matter itself rather than forcing the whole firm onto one billing model, so the flat fee trademark matter gets a manual invoice built the way that client actually wants to see it, and the corporate litigation matter runs through the same Bill Unbilled Time flow into a LEDES export, and neither one has to fight the system to get there. The invoice template itself is also fully customizable in settings, your logo, your bank details, the tax label if you are running a GST ready practice, your terms, so the individual clients still get an invoice that looks like your firm rather than a generic export.

What actually changes once the export is a button instead of a project

The difference this makes is not really about the invoice itself, and so yeah, that is basically the whole case for it, but I do want to land on why it matters at the level a managing partner actually feels it. A five attorney firm doing a mix of plaintiff work and corporate defense work does not have a billing coordinator whose entire job is reformatting invoices into LEDES files, and every week that a corporate client's invoice sits bounced in an e-billing queue because a field was missing is a week that firm is floating that receivable itself, on its own cash flow, for work it already finished. Does that make sense, right, the work was done weeks ago, the only thing standing between the firm and getting paid is whether the file lands in the format the client's system will actually accept. Get the billing mechanics right at the source, meaning time entries that already carry the right timekeeper and task data the moment they are logged, and the LEDES export stops being a special project someone dreads at the end of the month and just becomes the last click in a process that was already going to happen anyway.