What does the Build Legal E-Billing File (LEDES 1998B) skill do?

Convert law-firm time & expense records into a LEDES 1998B pipe-delimited e-billing file — the 24-field layout, UTBMS task/activity/expense codes, fee vs expense vs adjustment lines, line-total and invoice-total reconciliation, and a worked example for corporate e-billing intake (TyMetrix/Legal Tracker)

How do I run the Build Legal E-Billing File (LEDES 1998B) skill?

Copy the skill and paste it into your own Claude or ChatGPT, then provide your source data. FinchContext skills run inside your own AI assistant, so your financial data never leaves your control.

Which region does the Build Legal E-Billing File (LEDES 1998B) skill cover?

United States. It targets the local tax authority / e-invoicing format described on this page.

Build Legal E-Billing File (LEDES 1998B)

Skill: Convert legal time & expense records into a LEDES 1998B invoice

Region: United States Category: Legal / eDiscovery Does: Takes a law firm's matter time and expense entries and assembles a LEDES 1998B electronic billing file — the pipe-delimited standard corporate legal departments require for e-billing intake (TyMetrix 360, Legal Tracker, BillerXpert, CounselLink, Onit). Spec: LEDES 1998B (Legal Electronic Data Exchange Standard, LEDES Oversight Committee) + UTBMS codes

LEDES 1998B is maintained by the LEDES Oversight Committee (LOC). It is a strict pipe-delimited (|) flat format with a fixed field order; most e-billing systems also enforce client-specific billing guidelines (required UTBMS codes, timekeeper rate caps, block-billing rules) on top of the format. Validate against the LOC spec and the client's billing guidelines before submission.

File structure

Line 1:  LEDES1998B[]                              (format identifier)
Line 2:  <pipe-delimited header row of field names ending in []>
Line 3+: <one pipe-delimited data row per LINE ITEM, ending in []>

Each record line ends with []. One file can carry multiple invoices; rows are grouped by INVOICE_NUMBER. Each line item is either a fee (timekeeper work) or an expense.

Field order (24 fields, 1998B)

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[]

Field	Notes
`EXP/FEE/INV_ADJ_TYPE`	`F` fee, `E` expense, `IF`/`IE` invoice-level adjustment
`LINE_ITEM_TASK_CODE`	UTBMS task code (e.g. `L330` Depositions, `L120` Analysis/Strategy) — fees only
`LINE_ITEM_ACTIVITY_CODE`	UTBMS activity code (e.g. `A101` Plan and prepare for) — fees only
`LINE_ITEM_EXPENSE_CODE`	UTBMS expense code (e.g. `E101` Copying) — expenses only
`LINE_ITEM_NUMBER_OF_UNITS`	hours (fees) or quantity (expenses)
`LINE_ITEM_UNIT_COST`	hourly rate (fees) or per-unit cost (expenses)
`TIMEKEEPER_CLASSIFICATION`	UTBMS timekeeper level (e.g. `PT` partner, `AS` associate, `PL` paralegal)

Calculation rules

LINE_ITEM_TOTAL = (NUMBER_OF_UNITS × UNIT_COST) + LINE_ITEM_ADJUSTMENT_AMOUNT. Adjustments are negative for write-downs.
INVOICE_TOTAL must equal the sum of all LINE_ITEM_TOTAL values for that INVOICE_NUMBER (including expense and adjustment lines). E-billing systems reject on any mismatch.
Dates are typically YYYYMMDD; line-item dates must fall within BILLING_START_DATE…BILLING_END_DATE.
UTBMS codes are conditional by type: fee lines carry task + activity codes (no expense code); expense lines carry an expense code (no task/activity). Many client guidelines require UTBMS coding and reject uncoded lines.
Amounts are decimal; do not include currency symbols or thousands separators. Currency itself is client-dependent (USD typical; the same format serves other currencies).

Worked example

One fee line (3.5 hrs partner @ $500) + one expense (200 copies @ $0.10), one invoice:

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[]
20250131|INV-1001|CLIENT01|MAT-2025-07|1770.00|20250101|20250131|January fees and costs|1|F|3.50|0.00|1750.00|20250115|L120||A104|TK001|Review and analyze discovery responses|FIRM01|500.00|Jane Doe|PT|CM-2025-07[]
20250131|INV-1001|CLIENT01|MAT-2025-07|1770.00|20250101|20250131|January fees and costs|2|E|200|0.00|20.00|20250116||E101||TK001|Photocopying|FIRM01|0.10|Jane Doe|PT|CM-2025-07[]

(Fee line total 3.5 × 500 = 1750.00; expense 200 × 0.10 = 20.00; INVOICE_TOTAL = 1770.00 = Σ line totals.)

Validation checklist

First line is exactly LEDES1998B[]; header row matches the 24-field order; every row ends in []
Pipe-delimited; field count consistent on every line; no stray pipes in descriptions
EXP/FEE/INV_ADJ_TYPE correct per line (F/E/IF/IE)
Fee lines carry UTBMS task + activity codes; expense lines carry an expense code (per client guidelines)
LINE_ITEM_TOTAL = units × unit cost + adjustment; INVOICE_TOTAL = Σ line totals
Line-item dates fall within the billing period; dates in the agreed format (YYYYMMDD)
Timekeeper IDs, names, and UTBMS classifications populated; rates within any client caps
Validated against the LOC spec and the client's e-billing guidelines before upload

Last updated: 2026-05-31 — confirm the field order, UTBMS code requirements, date format, and currency against the current LEDES 1998B specification (LEDES Oversight Committee) and the client's e-billing system guidelines before use.