LEDES invoice validation is the set of automated checks an eBilling system runs on a law firm’s LEDES invoice before it reaches a reviewer or accounts payable, covering file format, matter and timekeeper data, rates, billing codes, duplicates, and payment details. The LEDES file standardizes how invoice data is exchanged. Validation decides whether that data is acceptable to pay. A department receiving 300 to 1,000 invoices a month cannot review every line by hand, so the rules carry most of the load. This guide walks through each validation layer, how rejections should work, and the targets that show the rules are doing their job. If you need a refresher on the file itself, LEDES billing uses standard formats for exchanging invoice data between firms and clients.
What is LEDES invoice validation?
LEDES invoice validation is a control process that checks every submitted invoice against format rules, your matter and rate data, and your billing guidelines before it moves into approval. Validation is getting stricter across the market, and billing data from about 400 law firms shows invoice rejection rates climbed from 11 to 18 percent in 2025. It treats the LEDES file as the start of a review, with every field tested before anyone spends time reading it.
- Technical validation. Confirms the file follows the required LEDES version and structure, and that the math adds up.
- Business rule validation. Checks matters, timekeepers, rates, task and activity codes, and narratives against your guidelines.
- Payment readiness. Confirms approved invoices carry the vendor, cost allocation, and ERP data accounts payable needs.
Most of these rules come straight from your outside counsel guidelines. The work of turning outside counsel billing guidelines from a document into system rules is where validation design starts.
What does format validation check on a LEDES file?
Format validation on a LEDES file checks that the invoice matches the LEDES version your department requires, with the right structure, fields, and totals. It is the first gate, and an invoice that fails it should never reach a human reviewer.
- Version and structure. LEDES 1998B is a pipe-delimited ASCII format with 24 fields, and it remains the most common format for US legal eBilling. For international billing, the current LEDES 98BI format, ratified in January 2020, has 52 fields, adding tax and party details.
- Required fields. Invoice number, dates, law firm ID, client matter ID, and line totals are present and in the expected format.
- Arithmetic. Units multiplied by rate, discounts, taxes, and invoice totals reconcile, with no unexplained difference between the lines and the invoice total.
Tell firms which version you accept during onboarding. Accepting two formats doubles the testing and the ways a file can fail.
How should matter and timekeeper data be validated on LEDES invoices?
Matter and timekeeper data on LEDES invoices should be validated against your own records, so every invoice ties to a real open matter and every timekeeper to an approved rate. These are the checks that stop the most money.
- Matter matching. Every invoice references a valid, open matter number before processing. Invoices against closed or unknown matters are rejected at the gate.
- Timekeeper validation. Every billed timekeeper has an approved ID, a classification such as partner or associate, and a rate card entry.
- Rate compliance. Every hourly rate matches the approved rate card or has a documented exception approval attached.
Rate cards go stale fast. Plan a rate refresh with each firm at least once a year, usually in the first quarter when most firms announce increases.
How are UTBMS codes and narratives validated on legal invoices?
UTBMS codes and narratives on legal invoices are validated by requiring the task, activity, and expense codes your billing rules call for, and by checking that each line describes the work specifically enough to review. Codes make spend reportable; narratives make it reviewable.
Required task, activity, and expense codes must be present and valid for the matter type, since a litigation matter and an advisory matter may need different code sets. Each time and expense line also needs a specific description, and rules can flag block billing, entries under a minimum length, and vague phrases such as “attention to file”.
Narrative rules are the ones firms push back on most. Start them as warnings for 60 to 90 days, then switch to rejections once firms have adjusted.
How do you catch duplicate LEDES invoices?
Duplicate LEDES invoices are caught by matching new submissions against past invoices on invoice number, vendor, matter, and amount. A match on all four is almost always a duplicate, and a match on three deserves a look.
Duplicates rarely come from bad intent. They come from a firm resubmitting after a rejection, a billing system sending twice, or an invoice being split and rebilled. The target is simple: no invoice is ever paid twice. In practice, a well-tuned rule keeps the duplicate rate below 0.1 percent of submissions. Run the check at submission, and again just before payment export, since a corrected invoice can arrive while the original is still in approval.
What should a LEDES invoice rejection tell the law firm?
A LEDES invoice rejection should tell the law firm exactly which rule failed, on which line, and what to fix, in a form their billing team can act on without calling you. Vague rejections turn a five-minute fix into a two-week email thread.
- Specific reason codes. Each rejection carries a clear, actionable error code or message. The LEDES Oversight Committee maintains standardized LEDES error codes, which give firms and clients a shared vocabulary for common failures.
- Line and fix. The message names the failing line and the correction expected, such as the approved rate or the missing task code.
- Tracked to resolution. Every rejected invoice is logged with its reason and followed until a corrected invoice is accepted or the matter is closed out.
Review rejection reasons every month. If one rule accounts for more than a quarter of all rejections, either firms need clearer guidance or the rule needs adjusting.
How should approved invoices be checked before ERP export?
Approved invoices should be checked for payment readiness before they are exported to your ERP, so accounts payable receives nothing it has to send back. An invoice can pass every legal review and still fail at payment.
- Vendor data. The law firm is an approved vendor with valid remit-to and tax details in the ERP.
- Cost allocation. Cost center, general ledger account, and business unit are present and valid for the matter.
- Purchase order and routing. Any required purchase order is attached, and the invoice was approved by someone with the right delegated signing authority for its amount.
These checks depend on clean data flowing between systems.
What targets should an eBilling validation program aim for?
An eBilling validation program should aim for measurable targets on first-pass acceptance, matter and rate matching, coding quality, duplicates, and payment readiness. These are internal control targets from delivery practice, so adjust them to your firms, jurisdictions, and invoice complexity.
- First-pass acceptance. 95 percent or more of invoices pass technical validation on first submission.
- Rate and matter accuracy. 100 percent of invoices reference a valid matter and approved vendor, and less than 2 percent of billed time arrives at an unauthorized rate.
- Coding and AP readiness. Fewer than 1 percent of invoices need correction for missing UTBMS codes or weak narratives, and 100 percent of approved invoices pass AP checks before export.
Track rejection rate by rule, invoice cycle time, and time from approval to ERP export alongside these. Those measures show whether eBilling is actually reducing manual review, and they fit naturally into a broader set of legal eBilling software capabilities your department relies on.
How should new validation rules be rolled out to law firms?
New validation rules should be rolled out to law firms with advance notice, a warning period, and a clear effective date, so firms can adjust their billing systems before invoices start failing. Firms that are surprised by rejections tend to escalate to the business, and the rules lose support.
Give firms 30 to 60 days’ notice of any new rule, with an example of a line that passes and one that fails. Run new rules in warning mode first, then switch them to hard rejections once the warning rate falls. Start with your top 10 to 20 firms by spend, since they usually submit most of your invoice volume. The practices for onboarding law firms to eBilling without a revolt apply equally to every rule change after go-live.
Conclusion
LEDES invoice validation turns a standardized file into a controlled payment process, catching wrong rates, missing codes, duplicates, and bad payment data before anyone signs off. Build it in layers: format first, then matters and timekeepers, then codes and narratives, then payment readiness. Make every rejection specific and tracked, set measurable targets, and review rejection reasons monthly. Roll out new rules with notice and a warning period, and your firms will fix invoices at the source.
How Basla can help
Basla provides delivery teams for enterprise legal management and eBilling software implementation, covering legal technology consulting, business analysis, billing rule configuration, rate card and matter data setup, testing, law firm onboarding support, documentation, and post-go-live support. For LEDES invoice validation, that means translating your billing guidelines into system rules, testing each rule with passing and failing LEDES files, and tuning rejection messages so firms can act on them.
Basla has delivered matter management and eBilling across 10+ global jurisdictions and created and executed more than 1,000 test records for a contract lifecycle management rollout. That testing discipline carries into every eBilling rule set Basla configures.
Frequently asked questions
What is LEDES invoice validation?
LEDES invoice validation is the set of automated checks an eBilling system runs on a law firm’s LEDES invoice before approval and payment. It covers file format, matters, timekeepers, rates, UTBMS codes, narratives, duplicates, and payment data.
How many fields are in a LEDES 1998B file?
A LEDES 1998B file is a pipe-delimited ASCII format with 24 fields. The international LEDES 98BI format has 52 fields in its current version and adds tax and party details.
Why do LEDES invoices get rejected?
LEDES invoices are usually rejected for format errors, invalid or closed matter numbers, rates that do not match the rate card, missing UTBMS codes, or vague narratives. Duplicate submissions are another common cause.
What are LEDES error codes?
LEDES error codes are standardized codes maintained by the LEDES Oversight Committee that identify why an invoice failed validation. They give law firms and clients a shared way to describe and correct common failures.
What first-pass acceptance rate should eBilling target?
An eBilling program should target 95 percent or more of invoices passing technical validation on first submission. Adjust the target to your firm population and invoice complexity.
How do you stop duplicate legal invoices from being paid?
Duplicate legal invoices are stopped by matching each submission on invoice number, vendor, matter, and amount, both at submission and before payment export. A well-tuned rule keeps duplicates below 0.1 percent.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*