LEDES File Validator
Open or paste a LEDES 1998B invoice and find the problems e-billing systems reject before you upload it: the header and all 24 fields, line and invoice arithmetic, dates, UTBMS task, activity and expense codes, and timekeeper classifications. The check runs in your browser, and the file never leaves your computer.
24 fields
checked on every line
4 code lists
ABA, DRI, eDiscovery, LOC 2013
In browser
nothing uploaded or stored
Check a LEDES 1998B file
Open the .txt, .ledes, .dat or .edi file your billing software exported, or paste its contents. The check runs in this browser tab. Nothing is uploaded or stored.
1
Invoices
9
Line items
1
Errors
5
Warnings
Fix the errors before you upload. Each one breaks the LEDES 1998B specification.
Warning line 4, invoice 2611-0418, item 2
0.25 hours is not in tenths of an hour. Many carrier guidelines require actual time in 0.1 hour increments.
Warning line 5, invoice 2611-0418, item 3
The description strings several tasks together with semicolons under one time entry. Carrier guidelines commonly reject this as block billing, so give each task its own entry and time.
Warning line 6, invoice 2611-0418, item 4
The description reads as clerical work (Bates numbering). Carrier guidelines, and courts awarding attorney's fees, treat clerical tasks as overhead whoever performs them.
Warning line 8, invoice 2611-0418, item 6
L360 (Discovery On-Site Inspections) comes from the DRI revised litigation codes (2007), not the ABA 1997 codes. Confirm this client accepts it, or switch the code set if the client uses that list.
Error line 9, invoice 2611-0418, item 7
LINE_ITEM_TOTAL is 280.00, but unit cost times units plus adjustment (180.00 × 1.5) is 270.00.
Warning line 9, invoice 2611-0418, item 7
LINE_ITEM_DATE Nov 2, 2026 falls outside the billing period, Oct 1, 2026 to Oct 31, 2026. The specification expects line dates between the billing start and end dates, so move the line to the invoice for its period or correct the dates.
Invoices in the file
| Invoice | Date | Firm matter | Client matter | Billing period | Stated total | Line items add to | Fees | Expenses | Hours |
|---|---|---|---|---|---|---|---|---|---|
| 2611-0418 | Nov 5, 2026 | 2026-0193 | CLM-0055120 | Oct 1, 2026 to Oct 31, 2026 | 2,400.40 | 2,400.40 | 1,773.00 | 627.40 | 9.35 |
Timekeepers on fee lines
| ID | Name | Classification | Hours | Fees | Rates billed |
|---|---|---|---|---|---|
| JD | Doe, Jane | PARTNR | 1.55 | 403.00 | 260.00 |
| RR | Roe, Richard | ASSOC | 7.0 | 1,270.00 | 180.00 |
| KP | Poe, Kim | PARALG | 0.8 | 100.00 | 125.00 |
UTBMS codes used
Hours and amounts by code, the same breakdown a claims professional or e-billing reviewer sees.
| Code | Type | Name | List | Lines | Hours | Amount |
|---|---|---|---|---|---|---|
| L110 | Task | Fact Investigation/Development | ABA litigation codes (1997) | 1 | 1.3 | 338.00 |
| L120 | Task | Analysis/Strategy | ABA litigation codes (1997) | 1 | 0.25 | 65.00 |
| L140 | Task | Document/File Management | ABA litigation codes (1997) | 1 | 0.8 | 100.00 |
| L210 | Task | Pleadings | ABA litigation codes (1997) | 1 | 1.1 | 198.00 |
| L240 | Task | Dispositive Motions | ABA litigation codes (1997) | 1 | 1.5 | 280.00 |
| L330 | Task | Depositions | ABA litigation codes (1997) | 1 | 2.4 | 432.00 |
| L360 | Task | Discovery On-Site Inspections | DRI revised litigation codes (2007) | 1 | 2.0 | 360.00 |
| A101 | Activity | Plan and prepare for | ABA activity codes (1997) | 1 | 2.4 | 432.00 |
| A103 | Activity | Draft/revise | ABA activity codes (1997) | 2 | 2.6 | 478.00 |
| A104 | Activity | Review/analyze | ABA activity codes (1997) | 1 | 1.3 | 338.00 |
| A106 | Activity | Communicate (with client) | ABA activity codes (1997) | 1 | 0.25 | 65.00 |
| A109 | Activity | Appear for/attend | ABA activity codes (1997) | 1 | 2.0 | 360.00 |
| A110 | Activity | Manage data/files | ABA activity codes (1997) | 1 | 0.8 | 100.00 |
| E101 | Expense | Copying | ABA expense codes (1997) | 1 | 15.00 | |
| E115 | Expense | Deposition transcripts | ABA expense codes (1997) | 1 | 612.40 |
Checks follow the LEDES 1998B Field Specification (LEDES Oversight Committee, rev. 7/2014), the published UTBMS code sets and the LEDES timekeeper classification list. Each client’s e-billing system and billing guidelines add their own rules, such as approved timekeepers, rates and matter numbers, which no file check can see.
What the validator checks
The rules come from the LEDES 1998B field specification published by the LEDES Oversight Committee, the body that maintains the format, and from the e-billing vendors’ own documentation. Every finding carries the file line number, the invoice and the line item, so the billing team can go straight to the entry in the billing system.
The first two lines
Format headerLine 1 must read LEDES1998B[] exactly. Line 2 lists the 24 field names in order, from INVOICE_DATE to CLIENT_MATTER_ID, and every line in the file ends with []. Brightflag, for one, has a dedicated error code for an incorrect LEDES header, BF120.
Exactly 24 fields on every line
Brightflag error BF109Fields are separated by the pipe character, so a pipe typed inside a description splits it in two and pushes every later field one place to the right. The validator counts the fields on each line and names the line that is off.
Required fields by line type
Field specificationEvery line needs the invoice date, number and total, the client and matter IDs, the billing period, a line number and type, a line total, a line date and the law firm ID. Fee lines (F) also need a timekeeper ID, name, classification and description. Expense lines (E) need an expense code. Only invoice-level adjustments (IF and IE) may leave units and unit cost blank.
Line item arithmetic
LINE_ITEM_TOTALEach line total must equal unit cost times units plus the adjustment amount, where a negative adjustment is a discount and a positive one a premium. The specification calls a line more than 0.1% away from that formula clearly an error. The validator flags any gap over half a cent: as an error beyond 0.1%, as a warning below it.
Invoice totals
INVOICE_TOTALINVOICE_TOTAL must be the sum of the invoice's line totals. The specification gives 1% as an example of a reasonable rounding variance for the receiving system, but some systems, Brightflag among them, require an exact match. Only the first line's invoice date, total and billing period count, so a later line that disagrees is flagged too.
Dates, numbers and lengths
Field typesDates are YYYYMMDD and must exist on the calendar, so 20261131 fails. Amounts are plain numbers with up to 4 decimal places and no commas or currency signs. Text fields have limits: 20 characters for invoice numbers, matter IDs, timekeeper IDs and codes, 30 for timekeeper names and 10 for classifications.
Line item numbers
LINE_ITEM_NUMBERLine numbers must be unique within an invoice but need not run in order. The specification says the time entry's primary key in the firm's billing system is usually used. The same number may appear again on another invoice in the same file.
Plain ASCII text
Character setLEDES 1998B is an ASCII format. Curly quotes, long dashes and accented letters pasted from a word processor arrive as unreadable characters, so the validator names each one with its Unicode value. It also catches a byte order mark at the start of the file, an invisible character some editors add.
What a LEDES 1998B file looks like
A LEDES 1998B file is plain text. The first line names the format, the second names the fields, and every line after that is one fee, expense or adjustment, with the invoice fields repeated on each line. These are the first three lines of the fictional sample invoice loaded in the validator above.
LEDES1998B[] INVOICE_DATE|INVOICE_NUMBER|CLIENT_ID|LAW_FIRM_MATTER_ID|INVOICE_TOTAL|BILLING_START_DATE|BILLING_END_DATE|INVOICE_DESCRIPTION|LINE_ITEM_NUMBER|EXP/FEE/INV_ADJ_TYPE|LINE_ITEM_NUMBER_OF_UNITS|LINE_ITEM_ADJUSTMENT_AMOUNT|LINE_ITEM_TOTAL|LINE_ITEM_DATE|LINE_ITEM_TASK_CODE|LINE_ITEM_EXPENSE_CODE|LINE_ITEM_ACTIVITY_CODE|TIMEKEEPER_ID|LINE_ITEM_DESCRIPTION|LAW_FIRM_ID|LINE_ITEM_UNIT_COST|TIMEKEEPER_NAME|TIMEKEEPER_CLASSIFICATION|CLIENT_MATTER_ID[] 20261105|2611-0418|CARRIER01|2026-0193|2400.40|20261001|20261031|Professional services and costs through October 31, 2026|1|F|1.30|0|338.00|20261005|L110||A104|JD|Review incident report, scene photographs and claimant's recorded statement to assess liability|12-3456789|260|Doe, Jane|PARTNR|CLM-0055120[]
Because the invoice fields repeat, the specification settles conflicts in advance: for each invoice number, only the first line’s invoice date, total, billing period and description count, and the rest are disregarded. A file may hold several invoices.
The 24 fields
Types and lengths are from the specification. Currency 10.4 means up to 4 decimal places. “Fee lines” are lines typed F.
| # | Field | Type | Required on | Rule |
|---|---|---|---|---|
| 1 | INVOICE_DATE | Date, YYYYMMDD | Every line | Only the first line's value counts for each invoice. |
| 2 | INVOICE_NUMBER | Text, 20 | Every line | One file may carry several invoices. |
| 3 | CLIENT_ID | Text, 20 | Every line | The firm's client code. |
| 4 | LAW_FIRM_MATTER_ID | Text, 20 | Every line | The firm's matter number. |
| 5 | INVOICE_TOTAL | Currency, 12.4 | Every line | The sum of the invoice's line totals. |
| 6 | BILLING_START_DATE | Date, YYYYMMDD | Every line | First day of the billing period. |
| 7 | BILLING_END_DATE | Date, YYYYMMDD | Every line | Last day of the billing period. |
| 8 | INVOICE_DESCRIPTION | Text, 15 KB | Optional | A summary of the work billed. |
| 9 | LINE_ITEM_NUMBER | Text, 20 | Every line | Unique within the invoice, not necessarily consecutive. |
| 10 | EXP/FEE/INV_ADJ_TYPE | Text, 2 | Every line | F fee, E expense, IF or IE invoice-level adjustment. |
| 11 | LINE_ITEM_NUMBER_OF_UNITS | Numeric, 10.4 | All but IF and IE | Hours on a fee, items on an expense. Zero is an error. |
| 12 | LINE_ITEM_ADJUSTMENT_AMOUNT | Currency, 10.4 | Optional | Negative for a discount, positive for a premium. |
| 13 | LINE_ITEM_TOTAL | Currency, 10.4 | Every line | Unit cost times units, plus the adjustment. |
| 14 | LINE_ITEM_DATE | Date, YYYYMMDD | Every line | Normally inside the billing period. |
| 15 | LINE_ITEM_TASK_CODE | Text, 20 | Fee lines, if the client uses codes | A UTBMS task code such as L330. |
| 16 | LINE_ITEM_EXPENSE_CODE | Text, 20 | Expense lines | A UTBMS expense code such as E101. |
| 17 | LINE_ITEM_ACTIVITY_CODE | Text, 20 | Fee lines, if the client uses codes | Never without a task code. |
| 18 | TIMEKEEPER_ID | Text, 20 | Fee lines | The firm's own key for the timekeeper. |
| 19 | LINE_ITEM_DESCRIPTION | Text, 15 KB | Fee lines | May be blank on an expense that has a code. |
| 20 | LAW_FIRM_ID | Text, 20 | Every line | The firm's federal taxpayer ID. |
| 21 | LINE_ITEM_UNIT_COST | Currency, 10.4 | All but IF and IE | The standard, undiscounted rate or cost per unit. |
| 22 | TIMEKEEPER_NAME | Text, 30 | Fee lines | Last name, a comma, then first name. |
| 23 | TIMEKEEPER_CLASSIFICATION | Text, 10 | Fee lines | A code from the LEDES classification list. |
| 24 | CLIENT_MATTER_ID | Text, 20 | Unless the client has no matter numbers | The client's claim or matter number. |
Errors and warnings
An error means the file breaks the LEDES 1998B specification itself: a missing header, a line with 23 fields, a date that does not exist, a line total that does not match its units and rate, or an invoice total that misses the sum of its lines by more than 1%. A system that enforces the specification will not accept them.
A warning is something the specification allows but clients commonly reject or reduce: a task code from a different UTBMS list, a line dated outside the billing period, a pre-2014 timekeeper code, 0.25 hours where the client wants tenths, or a description that reads as block billing. Read each one against the client’s billing guidelines.
Fix both in the billing system and export the file again rather than editing the text by hand. A corrected line total typed into the file leaves INVOICE_TOTAL wrong on every line of that invoice, and the next export overwrites the change anyway.
Which UTBMS code set the client uses
UTBMS, the Uniform Task-Based Management System, gives each fee line a task code for what the work was for and, if the client wants it, an activity code for what the timekeeper did. Each expense gets an expense code. Thomson Reuters’ Legal Tracker help puts client demand plainly: almost all clients require expense codes, many require task codes for at least some types of work, and few require activity codes.
The original ABA lists from 1997 have 29 litigation tasks grouped under 5 phases, L100 to L500, plus 11 activity codes and 24 expense codes. The phase codes are headings. A line takes a task such as L330 Depositions, and the validator warns when it carries L300 instead.
In 2007 a committee of insurers and insurance defense firms revised the litigation list, and DRI published it as the UTBMS Litigation Code Set Revised 2007. Its introduction calls insurance defense the dominant user of task-based billing and says users had been modifying the codes unilaterally to fit their own litigation management guidelines. The revision keeps the ABA expense codes, adds A112 Travel to the activity codes, adds L360 for on-site inspections and drops the two catch-all tasks, L190 and L390. An invoice coded L190 can fail at a carrier that uses the 2007 list even though the ABA list allows it.
| Code | Name | ABA 1997 | DRI 2007, for insurers |
|---|---|---|---|
| L190 | Other Case Assessment, Development and Administration | Yes | No |
| L390 | Other Discovery | Yes | No |
| L360 | Discovery On-Site Inspections | No | Yes |
| A112 | Travel | No | Yes |
| L310 | Written Discovery | Yes | Renamed Written Discovery/Interrogatories |
| L440 | Other Trial Preparation and Support | Yes | Renamed Trial Preparation and Support |
| L510 | Appellate Motions and Submissions | Yes | Renamed Appellate Proceedings/Motions Practice |
In 2013 the LEDES Oversight Committee revised the activity and expense codes. The revised expense codes begin with X instead of E, such as X101 for in-house black and white copies and X127 for deposition transcripts, and X900 to X998 are reserved for client-specific codes. The committee suggested a phase-in of at least four months before clients reject the original E codes. The revised activity list runs from A101 to A128 and adds billable travel time (A112), communication with witnesses (A113) and experts (A114), and medical record and medical bill management (A115).
The committee’s eDiscovery codes, ratified July 13, 2011, run from L600 to L693: nine catch-all codes marked NOS, for not otherwise specified, such as L650 Review, and 25 tasks such as L653 first pass document review and L655 privilege review. Unlike the litigation phase headings, the NOS codes are meant to be billed. The validator accepts eDiscovery codes alongside either litigation list.
Pick the list the client’s billing guidelines name. If they do not say, ask the client or check the code list in its e-billing system before the first invoice goes out.
Fee entries carrier guidelines reject
Insurance carriers publish billing guidelines for the firms on their panels, and invoices are reviewed against them line by line. The Hartford’s guidelines for claims panel counsel are public and show the kind of rule the optional guideline checks look for. Turn the checks off for a client whose guidelines are different.
Time in tenths of an hour
Actual time should be entered in tenths of an hour.
The validator flags fee lines whose hours are not a multiple of 0.1, such as 0.25 or 1.33.
One task per entry
Grouping different activities under a single task code (block billing) is not acceptable.
The validator flags descriptions that string several tasks together with semicolons.
Clerical work is overhead
Secretarial/clerical functions including scheduling (regardless of who performs them)
The same overhead list names file organization and maintenance, indexing, Bates numbering, proofreading, conflicts checks, typing and word processing, and data entry. The validator flags fee descriptions built around those words. The Supreme Court made the point for fee awards in Missouri v. Jenkins, 491 U.S. 274, 288 n.10 (1989): "purely clerical or secretarial tasks should not be billed at a paralegal rate, regardless of who performs them."
Specific descriptions
Vague and non-descriptive task entries cannot be honored.
The guidelines give file review, legal research and deposition preparation as examples. The validator flags those and other one or two word entries.
Approved rates only
Unilateral rate changes and rate changes negotiated with Hartford Claim Handlers will not be honored.
The validator lists each rate a timekeeper is billed at and flags a timekeeper billed at two rates on one invoice.
The checks match words, so read each warning against the entry. “Attend scheduling conference” is attorney work and is not flagged, while “schedule deposition of treating physician” is flagged as scheduling.
The work on that list still has to be done. Under guidelines like these it simply cannot be billed, which makes it a cost question: the less an hour of scheduling, indexing and e-billing submission costs the firm, the less unbillable overhead each matter carries.
Timekeeper classification codes
TIMEKEEPER_CLASSIFICATION takes a code from the LEDES Oversight Committee’s revised list, ratified in August 2014 and last updated June 25, 2023. The list has 51 codes, nearly all six letters long, and replaced the two-letter codes LEDES 1998B used before. These are the ones law firm invoices use most.
| Code | Timekeeper | Former 1998B code |
|---|---|---|
| PARTNR | Partner | PT |
| ASSOC | Associate | AS |
| OFCOUN | Of Counsel | OC |
| STFATT | Staff Attorney | |
| TEMPAT | Contract Attorney, not a regular employee of the firm | |
| PARALG | Paralegal certified or licensed where that is required | |
| LGLAST | Legal Assistant | LA |
| CLKSEC | Clerk or Secretary | OT |
| TEMPOS | Contract Other Staff, not a regular employee of the firm | |
| LGLINT | Legal Intern | |
| LGPRMG | Legal Project Manager | |
| DOCRNA | Document Reviewer, Non-Attorney |
The paralegal code turns on credentials, not job title. The committee reserves PARALG for a timekeeper who holds a certification or license from a jurisdictional authority where one is required, and gives California as the example. Anyone else doing that work is LGLAST. Timekeepers who are not regular employees of the firm have their own codes: TEMPAT for contract attorneys and TEMPOS for all other contract staff.
Two codes exist for 98B workarounds: ADJSMT for an invoice adjustment and FLTFEE for a flat fee. The committee says to use them only if the e-billing vendor specifies them, because many systems do not recognize them. NBOTHR marks a system user whose services are not billed to the client, so it never belongs on a billed fee line. The validator accepts all 51 codes, warns on the old two-letter codes and names the code that replaced each one.
What a file check cannot see
A clean result means the file is well formed and adds up. It does not mean the client will pay every line.
Approved timekeepers and rates
The e-billing system compares each line with the timekeepers and rates the client approved. Collaborati, for example, requires every TIMEKEEPER_ID to match a timekeeper the client authorized and caps the ID at 8 characters, where the specification allows 20.
Each portal's own rules
Brightflag asks for a .txt file, never accepts a blank CLIENT_MATTER_ID, rejects negative units, wants the same invoice description on every line and keeps line descriptions under 1,024 characters. Legal Tracker accepts several invoices in one file but not one invoice billed to several matters, and takes None as the law firm ID for a firm without a federal ID. The validator warns on the Brightflag rules, because a file that meets them still meets the specification.
Caps in the client's guidelines
Copy rates, mileage, travel time, the number of attendees at a deposition, research limits, budgets and invoice deadlines are set client by client. The validator does not know them.
Other LEDES formats
LEDES 98BI, the international version with tax and address fields, LEDES 2000 and LEDES XML use different layouts. The validator recognizes their headers and stops rather than guessing.
Reviewers also judge whether each task was necessary and the time reasonable. No file check can make that call, but a description that says what was done, for whom and why is what lets the reviewer make it.
Someone has to own the export, the check, the upload and the rejection queue for every portal client. DocketHire places remote legal billing assistants who handle that work in the firm’s own billing system and client portals, supervised by the firm. Our e-billing portal support guide covers the client rules sheet and rejection tracking that go with it.
Questions billing teams ask
What is a LEDES 1998B file?
A plain text invoice file with one line per fee, expense or invoice-level adjustment and 24 fields per line, separated by pipe characters. The LEDES Oversight Committee, which maintains the format, calls 1998B the most widely used e-billing standard in the US legal industry and does not intend to change it. The first line reads LEDES1998B[] and the second lists the field names.
Why was my LEDES file rejected?
The mechanical causes are a wrong first line, a line without exactly 24 fields (often a pipe typed into a description), a line total that does not equal unit cost times units plus adjustment, an invoice total that does not equal the sum of its lines, dates not written YYYYMMDD, and codes the client does not use. The rest come from the client's rules: unapproved timekeepers or rates, lines outside the billing period, block billing, clerical tasks and vague descriptions. The validator finds the mechanical causes by line number.
How do I open a LEDES file?
It is plain text, so any text editor opens it, including Notepad and TextEdit. Billing systems save it as .txt, .ledes, .dat or .edi. Brightflag asks for a .txt file and tells firms to rename .edi and .dat files before uploading.
Are UTBMS codes required in a LEDES 1998B file?
The specification leaves task and activity codes to the receiving client and requires an expense code on expense lines. Thomson Reuters' Legal Tracker help says almost all clients require expense codes, many require task codes for at least some types of work, and few require activity codes. A line that carries an activity code must carry a task code too.
Which timekeeper classification code should a paralegal have?
Under the LEDES Oversight Committee's revised list, PARALG is for a paralegal who holds a certification or license from a jurisdictional authority where one is required, as in California. Anyone else doing paralegal work is coded LGLAST, Legal Assistant. The pre-2014 1998B list had no paralegal code, and its LA code maps to LGLAST.
What is the difference between LEDES 1998B and LEDES 98BI?
LEDES 98BI is the international version. It adds fields for tax and for law firm and client details, so each line is much longer: Brightflag counts 52 columns in 98BI V2 against 24 in 1998B. The validator reads 1998B files and says so when it sees a 98BI header.
Is my file uploaded anywhere?
No. Your browser reads the file and the check runs on your computer. Nothing is sent to DocketHire or anyone else and nothing is stored, so closing the tab clears it.
Can the validator fix my LEDES file?
It tells you what to fix and where, but it does not rewrite the file. Make corrections in the billing system and export again, because a hand edit to one line total leaves the invoice total wrong and is lost at the next export.
Sources
The specification, code lists, timekeeper classifications and vendor rules were checked in November 2026. The code lists in the validator follow the spreadsheets and PDFs linked from these pages.
- LEDES Oversight Committee, LEDES 98B format and 1998B field specification (rev. 7/2014)
- LEDES Oversight Committee, revised timekeeper classification codes (ratified August 2014, updated June 2023)
- UTBMS.com, ABA litigation codes (1997)
- UTBMS.com, ABA activity codes (1997)
- UTBMS.com, ABA expense codes (1997)
- UTBMS.com, DRI revised litigation codes (2007)
- UTBMS.com, LOC eDiscovery codes (ratified July 13, 2011)
- UTBMS.com, LOC revised activity codes (2013)
- UTBMS.com, LOC revised expense codes (2013)
- Thomson Reuters Legal Tracker, LEDES 1998B file specifications for law firms
- Thomson Reuters Legal Tracker, about task and activity codes
- Mitratech Collaborati, LEDES 1998B format specifications
- Brightflag, how to correctly format your LEDES file
- Brightflag, LEDES error BF109, incorrect number of columns
- The Hartford, billing guidelines for claims panel counsel
- Missouri v. Jenkins, 491 U.S. 274 (1989)
More for law firm billing teams
E-Billing Portal Support Guide
Client rules sheets, rejection tracking and who owns the portal queue.
Legal Billing Assistant
Time entries, LEDES invoice files and e-billing queues, handled under firm supervision.
Trust Account Reconciliation Checker
Reconcile the bank statement, the trust ledger and the client ledgers in one pass.
Insurance Defense Support Staff
Remote staff for firms that work under carrier billing guidelines and reporting rules.
Give the e-billing queue an owner
DocketHire places remote legal billing assistants with US law firms. They prepare LEDES files, check them before upload and work client rejections inside your billing system, under your firm's supervision. Book a meeting and we will scope the role to your clients and portals.