legal e-billing: LEDES 1998B invoice validation errors

TL;DR

LEDES 1998B validation errors are almost always format violations: wrong line count in the header, bad date formats, invalid task/activity/expense codes, or arithmetic where line totals do not match the invoice total. Validate against the 1998B spec before submitting: check the field count per line type, code validity against UTBMS sets, and the totals. Most e-billing platforms reject with a line number and a code; fix the generator, not the file by hand. Track rejections per firm to spot vendors whose billing systems chronically emit bad LEDES.

The query

legal e-billing: LEDES 1998B invoice validation errors

Use this when

• Law firm invoices failing e-billing validation
• LEDES 1998B format errors
• UTBMS code validation failures

Not for

• LEDES XML or 1998BI formats (different specs)
• Legal invoice review and rate compliance (separate process)

Steps

1. Capture the platform's rejection: line number and error code.

Expected output: The failure is precisely located.

1. Check the 1998B spec for that line type: field count, formats, code sets.

Expected output: The rule violated is identified.

1. Fix the firm's billing system output or mapping, not the single file.

Expected output: The source stops emitting bad LEDES.

1. Re-validate the regenerated file against the spec.

Expected output: The file passes before resubmission.

1. Track rejections per firm for vendor management.

Expected output: Chronic offenders get attention.

Variant phrasings

LEDES 1998B validation error

legal e-billing invoice rejected

UTBMS task code invalid LEDES

Root cause

1998B is a positional pipe-delimited format from the 90s: every line type has an exact field count and the codes come from fixed UTBMS sets, so even small generator bugs produce structurally invalid files. The fix belongs in the generator because hand-editing one file leaves the bug producing the next hundred.

Edge cases

• Timekeeper classifications and rate checks are separate validations that run after format passes
• Some clients add custom rules on top of 1998B; validate against the client's ruleset too

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_cPavWantZtLEoaOhl7zEKg