Trust & billing · Guide

LEDES 1998B format: a practical guide

LEDES 1998B is a pipe-delimited electronic invoice format used by insurers and corporate clients. Rejections usually come from four things: missing UTBMS task codes, malformed dates, unbalanced totals, and a header that does not match the line items.

Muhammad DanishIndependent consultant · Updated 15 November 2026
On this page
  1. What LEDES 1998B is
  2. Why insurers require it
  3. The fields that cause rejections
  4. A practical conversion workflow
  5. Validation checklist
  6. What to do when an invoice is rejected
  7. Where the time actually goes
  8. Build or buy

An insurer rejects an invoice for a formatting reason, not a billing reason. The time was real, the rates were right, the work was done — but the file had a missing task code, a date in the wrong format, or a total that did not match the line items. The invoice comes back, the payment cycle restarts, and the firm spends an afternoon on data entry instead of law.

LEDES 1998B exists to make electronic billing consistent. Understanding its structure is the fastest way to stop the rejections.

What LEDES 1998B is

LEDES stands for Legal Electronic Data Exchange Standard. The standards are published by the LEDES Oversight Committee, a voluntary industry body, and are widely required by insurers and corporate legal departments in the United States.

The 1998B variant is a pipe-delimited text format. It has three functional parts:

  • A header identifying the format version, the invoice, the client and the matter
  • Invoice-level totals for fees, expenses and taxes
  • Line items for each time entry and expense, with task and activity codes

The format is plain text. That makes it portable and easy to validate, and it makes a single misplaced delimiter a file-wide error.

Why insurers require it

Insurers use LEDES files to compare invoices across firms and matters. The Uniform Task-Based Management System (UTBMS) codes are the shared vocabulary: a task code describes the kind of work, an activity code describes how it was done, and an expense code describes the cost.

That comparison only works if every firm uses the same codes and the same field order. A file that is structurally valid but semantically inconsistent — the wrong task code, a vague narrative — still gets rejected or reduced.

The format gets the invoice read. The codes and narratives decide whether it is paid.

The fields that cause rejections

Missing or invalid UTBMS codes. Every line item needs the codes the client requires. A blank task code is the most common single cause of rejection.

Dates in the wrong format. LEDES expects a specific date representation. A spreadsheet exported with a local date format will fail validation even if the date is correct.

Totals that do not match. The invoice-level fee total must equal the sum of the line-item fees. Rounding differences and excluded lines break this.

Delimiter problems. The pipe character separates fields. A pipe inside a narrative field — or a missing pipe at the end of a line — shifts every subsequent field.

Character encoding and line endings. Non-ASCII characters and mixed line endings can corrupt the file when it is imported.

Tax treatment. Tax lines must be consistent with the invoice and with the client's requirements. A tax total without corresponding line items is a common error.

A practical conversion workflow

  1. Export time entries from the billing system as CSV, with matter, timekeeper, date, hours, rate, narrative, task code and activity code.
  2. Validate the data before conversion. Check for missing codes, zero or negative hours, duplicate entries and dates outside the invoice period.
  3. Map the fields. Each CSV column maps to a LEDES field; the mapping should be fixed for each client, not rebuilt for every invoice.
  4. Calculate totals from the line items, not from a separate summary.
  5. Generate the file with the required header and the exact delimiter.
  6. Re-import or re-parse the output to confirm it reads back correctly.
  7. Submit and keep a copy of the exact file sent, with the submission date.

Step 6 is the one firms skip. A file that opens correctly in a spreadsheet can still be malformed when parsed by the client's system; a round-trip check catches structural problems before submission.

Validation checklist

Before sending a LEDES file:

  • Format version and client identifiers present
  • Invoice number unique and in the required format
  • Matter and client references match the client's records
  • Every line has a date, timekeeper, hours, rate and narrative
  • Every line has the required task and activity codes
  • Expense lines have the required expense codes
  • Fee total equals the sum of line-item fees
  • Expense total equals the sum of expense lines
  • Tax total equals the sum of tax lines
  • No pipe characters inside narrative fields
  • Dates in the required format
  • No blank required fields
  • File encoding and line endings consistent
  • A copy of the submitted file retained

What to do when an invoice is rejected

Ask for the exact error, not just the rejection. Most e-billing systems return a reason code or a line reference. Then:

  1. Fix the specific error.
  2. Re-validate the whole file, because a fix can create a new mismatch.
  3. Resubmit with a note explaining the correction if the client requires it.
  4. Record the rejection and its cause, so the same error does not recur next month.

A rejection log is worth keeping. Firms that track rejection reasons usually find that two or three causes account for most of them — and those causes are fixable in the export template.

Where the time actually goes

Most firms do not lose time on the LEDES format itself. They lose it on the data cleanup before conversion: entries without codes, narratives that need rewriting, timekeepers missing from the rate table, and expenses that were never categorised.

That work has to happen somewhere. Doing it before the invoice is generated is cheaper than doing it after a rejection, because the second version also has a deadline attached.

Build or buy

A billing suite with LEDES export handles the format, but it also carries a per-user fee and a migration cost. For a small firm that bills a handful of insurance clients, a standalone converter — CSV in, validated LEDES out — is often the cheaper route, provided it validates before export.

The deciding question is volume. If the firm sends one LEDES invoice a month, a converter and a checklist are enough. If it sends dozens, the export should be automated inside the billing system, with the validation still in place.

Frequently asked questions

What is LEDES 1998B?

A legal electronic data exchange standard published by the LEDES Oversight Committee. The 1998B variant is a pipe-delimited invoice format widely required by insurers and corporate legal departments in the United States.

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

The 1998BI variant adds international fields and is used for cross-border matters. Domestic US insurance work usually asks for 1998B.

What are UTBMS codes?

Uniform Task-Based Management System codes — a shared vocabulary for task, activity and expense types. Insurers use them to compare invoices across firms, so a missing or wrong code is a common rejection reason.

Why was my LEDES file rejected?

Check four things first: the header totals must equal the sum of the line items, dates must follow the required format, every line needs the required task and activity codes, and the file must use the expected delimiter and line endings.

Can I create a LEDES file in Excel?

You can, but the format is unforgiving: one misplaced delimiter shifts every field on the line. A converter validates the structure before export and is less error-prone than hand-editing a spreadsheet.

LawFirmTools provides software tools only. Nothing here is legal advice, and LawFirmTools is not a lawyer or a law firm. This article is general information for legal professionals; it is not a substitute for professional judgment or for your state bar's rules.