A legal invoice can look correct on screen and still fail when its electronic file reaches a client portal.
LEDES validation checks whether that file follows the required billing format. A useful pre-submission workflow also checks its identifiers, amounts and client-specific requirements. Passing a format check alone does not establish that every charge is approved or that the client will pay it.
For billing teams, the practical goal is to identify the failure, correct its source and retain evidence of what was checked.
Start with the exact format and destination
Confirm the LEDES version the receiving client accepts before opening the file. A check written for one version should not be applied to another without verification.
The LEDES Oversight Committee describes LEDES 1998B as an ASCII, pipe-delimited format containing 24 fields. Those characteristics do not describe every LEDES format.
Tool compatibility also matters. Mitratech's documentation says Collaborati's LEDES Format Validator supports XML 2.0 and 2.1 and cannot be used with LEDES2000. A familiar tool name is not enough to establish compatibility with your file.
Record the client, receiving portal, expected format and exporter configuration together. This becomes the context for every finding.
Check the file in five passes
Use deterministic checks for file structure and arithmetic. Reserve interpretation and approval for the rules that require them.
| Pass | What to check | Evidence to retain |
|---|---|---|
| File structure | Correct version identifier, header order, delimiters, record endings and field count for the chosen format | File version and precise row or field errors |
| Identifiers | Client, matter and timekeeper values match the receiving system and the applicable master records | Mapping source and any mismatched values |
| Amounts | Line calculations, adjustments and invoice total reconcile under the relevant specification | Expected and actual amounts with the calculation |
| Billing requirements | Approved rates, staffing permissions, codes, required documents and relevant client rules | Rule source, effective date and affected entries |
| Release | Corrections were reviewed and the exact final export was revalidated | Approver, final file identity and validation result |
For 1998B, Legal Tracker's posting-error documentation identifies short records with missing separators, inconsistent invoice totals and invalid classifications as distinct problems. This is why a single “invalid file” label is insufficient for correction.
Check the actual exported file. A prebill preview does not prove that the exporter preserved every value correctly.
Diagnose the source before changing the file
Begin with the portal's error message, then distinguish structural failures from business-data failures.
| Symptom | First check | Likely correction route |
|---|---|---|
| Wrong number of fields | Count separators and compare the header with the correct specification | Fix the exporter mapping or the source text that disrupts the structure |
| Matter cannot be matched | Compare the exported client and firm matter references with the receiving system | Ask the matter-data owner to resolve the mapping |
| Invoice totals disagree across rows | Group records by invoice and compare repeated totals | Correct the source or export logic, then regenerate |
| Rate is rejected | Compare the billed rate with the applicable approved rate and effective dates | Route to rate management or the billing reviewer |
| Narrative violates a client rule | Read the entry alongside the actual guideline | Ask the timekeeper to clarify the work and obtain review |
Client and platform rules vary. For example, CounselLink's troubleshooting guidance calls out client and firm matter-ID mismatches, including potentially case-sensitive values. Do not assume that matching a visible matter name proves that the exported identifier is correct.
Prefer correcting the source record or export configuration. A manual edit to one output file can leave the next invoice with the same problem. When an urgent file correction is necessary, record it and reconcile it with the source system.
Keep format validation separate from AI interpretation
A parser can establish whether the file contains the expected fields. Arithmetic checks can establish whether its numbers reconcile. Neither requires a language model to guess.
A legal agent can assist with a different task: explaining a narrative flag, locating a relevant billing clause or preparing an exception for review. Require the underlying entry and rule to remain visible. An AI suggestion should not silently rewrite the description of work or change an amount.
Maintain separate statuses for “format passed,” “client-rule review complete” and “approved for submission.” This gives reviewers a clear view of what remains unresolved.
Worked example of a misleading green check
Illustrative example, not a LuMay customer result: A firm's 1998B export passes its structural checks. The receiving portal still cannot match one client matter reference.
The billing specialist compares the exported reference with the portal's matter record, confirms the mapping error with the matter-data owner and corrects the source configuration. The team regenerates the invoice and reruns all checks against that new file.
The exception record contains the original value, approved replacement, evidence source, reviewer and final validation result. The initial format pass remains in the history; it does not become evidence that the original matter reference was correct.
Make the release record useful
For each blocking issue, record the invoice and line, failed check, actual value, expected value, rule source, owner and resolution. Keep the original export and distinguish it from each corrected version.
When measuring improvement, separate file rejections from client-rule reductions and later commercial disputes. Track first-pass acceptance, repeat causes and correction time using consistent definitions.
LuMay's Legal Agents include BillingGuard, which LuMay describes as checking invoices, rates, approvals and billing requirements before submission. When evaluating that workflow, ask to see your required LEDES versions, exception evidence and approval process demonstrated against representative files.
Start with one rejected invoice. Trace each failure to its source and assign its owner before extending the checklist across the billing cycle.





