Non-LEDES Invoices vs LEDES Files: How eBilling Handles Both

A LEDES invoice is a legal bill submitted as a structured, machine-readable file in the Legal Electronic Data Exchange Standard, and non-LEDES invoices are bills keyed into the eBilling portal by hand or converted from a PDF. What separates them is how much structured data arrives at ingestion and how much of the checking a person has to do. If your program accepts both channels, your job is to give both the same downstream controls, so a PDF bill gets the same scrutiny as a clean file.

What is the difference between non-LEDES invoices and LEDES files?

Non-LEDES invoices and LEDES files differ in how the billing data enters the system: one arrives as a structured file the platform can read line by line, and the other has to be entered or extracted and then checked by a person. Everything after ingestion can work the same way for both.

• Input. An electronic submission is a file, most often LEDES 1998B, uploaded through the vendor portal. A manual submission is either typed line by line into a web form or produced by converting a PDF bill into invoice data.
• Validation. The structured file is checked by the system for columns, delimiters, and required fields before it is submitted. Manual data is checked by people, first the vendor and then your reviewer.
• Effort. A clean file is processed in seconds. A 40-line PDF bill can take a reviewer 15 to 30 minutes to verify properly.

LEDES 1998B is a pipe-delimited text standard for legal invoices, and that fixed structure lets the platform do the first round of checking for you. The standard defines LEDES 1998B as an ASCII, pipe-delimited format containing 24 fields, so every file can be read the same way.

How does an eBilling platform validate an electronic LEDES file?

An eBilling platform validates an electronic LEDES file by checking its structure and content against the format before the bill is ever submitted to the client. In Counsel Exchange, Onit’s outside counsel portal, a LEDES upload is checked before submission, and a file with a critical error cannot go forward. The most common failures are structural: missing or extra columns and the wrong delimiter. A LEDES 1998B file carries 24 columns and a LEDES98BI file carries 52, so a single dropped field breaks every row after it.

• Structure. Column count, delimiters, and header rows are checked first. A file that fails here goes back to the firm and never reaches your reviewers.
• Content. Invoice number, invoice date, billing period, matter identifier, and timekeeper fields must be present and in the expected format.
• Guideline rules. Checks for rates, task codes, and expenses run once the structure passes, and the full rule set is covered in LEDES invoice validation rules that catch bad invoices.

Treat a 100 percent structural pass rate on accepted files as the baseline.

How are non-LEDES invoices created in an eBilling system?

Non-LEDES invoices are created in an eBilling system either by direct entry into a web form or by converting a PDF bill into invoice data that the vendor then reviews. Counsel Exchange supports LEDES upload, PDF upload, and manual entry, so a single vendor portal can carry both channels.

With direct entry, the vendor types the invoice details and each fee and expense line by hand. With PDF conversion, the system processes the PDF into line items, and the vendor reviews the extracted lines, confirms the general invoice fields, selects the matter, and submits. Either way, the data was built by a person or by extraction, so it carries more room for error than a parsed file.

Keep the original PDF attached to every manual record. Auditors will ask for it when an extracted figure is questioned 18 months later.

Which law firms should submit LEDES files, and which can bill manually?

Law firms with recurring, high-value work should submit LEDES files, and manual billing should be reserved for low-volume vendors where the setup cost outweighs the benefit. Handling cost is the reason, since a 2026 benchmark survey of nearly 200 AP and finance leaders put the average cost to process one invoice at $9.90, against $2.67 for the best-performing teams. Most departments find that a small group of firms produces most of their outside counsel spend. Those firms usually export LEDES already.

• Volume and value. A vendor sending more than two or three invoices a month belongs on LEDES. Add a spend threshold, for example $50,000 a year, above which a structured file is mandatory whatever the invoice count.
• Capability. Local counsel in some jurisdictions, expert witnesses, and small specialist vendors often cannot produce a LEDES file. Allow manual billing for them and record that decision on the vendor record.
• Access. Decide which submission routes each vendor may use, and record its authorized method and portal status during onboarding.

Why do manual invoices need more review than LEDES files?

Manual invoices need more review than LEDES files because every field was typed or extracted, and each one is a place where a date, rate, quantity, or total can be wrong. Extraction tools struggle with scanned bills, tables that run across pages, and expenses grouped under a single line.

• Line-level check. Verify dates, timekeepers, hours, rates, expenses, taxes, and the invoice total against the PDF. A documented review of 100 percent of manual bills is the right standard.
• Matter check. Confirm the vendor selected the right matter. A bill booked to the wrong matter can pass every rate rule and still distort your spend reporting.
• Correction tracking. Record how often extracted fields are corrected, broken down by vendor. A firm whose PDFs need fixes on more than one invoice in five is a strong candidate to move onto LEDES.

Which eBilling controls should apply to both invoice channels?

The same downstream eBilling controls should apply to both invoice channels, so a bill entered by hand is held to the same standard as a file the system parsed.

• Duplicate detection. Run it after ingestion on both channels. Onit’s duplicate checks can compare matter, vendor, amount, currency, worked date, timekeeper, rate, line type, and task, activity, and expense codes.
• Rate validation. Check every fee line against the approved rate for that timekeeper and matter, whatever its source.
• Audit trail. Retain the original LEDES file or PDF, the validation results, any rejection reason, the correction, and the final disposition.

The same guideline logic applies too. Route approvals by matter, amount, and exception type, and keep the submission channel out of the routing logic entirely. The target is zero confirmed duplicate payments, whichever route the bill took.

How should rejected manual and electronic invoices be corrected?

Rejected manual and electronic invoices should be corrected through a resubmission that links back to the original, so the full history of the bill stays in one place. In Counsel Exchange, a rejected invoice is resubmitted linked to the original, and every correction comes back as a new submission.

For an electronic bill, the firm fixes the file and resubmits it against the rejected invoice. For a manual bill, the vendor copies the rejected invoice, updates the invoice number and the fields that were wrong, and submits again. When a firm wants to contest an adjustment, the case follows a 10-day vendor appeals SLA for adjusted invoices.

Use a short, fixed list of rejection reasons, such as wrong matter, rate variance, missing receipt, and suspected duplicate. Free-text rejections cannot be reported on. Aim to have corrected bills back within five business days, and track the median correction time separately for each channel.

What should an eBilling team measure for each invoice channel?

An eBilling team should measure first-pass acceptance, reviewer touch time, and correction cycle time separately for each invoice channel, because a blended number hides where the effort goes.

• First-pass acceptance. The share of invoices approved without a rejection. Report it as two figures, one for LEDES files and one for manual bills.
• Touch time. Minutes of reviewer effort per invoice. Manual bills usually take several times longer, and this number makes the business case for moving a firm onto LEDES.
• Correction cycle time. The median days from rejection to corrected resubmission, reported for each channel.

Add the share of spend arriving as structured files, reviewed quarterly.

Conclusion

A LEDES file and non-LEDES invoices can carry the same matter, the same rates, and the same obligation to pay, and your program only stays accurate when both are held to the same controls. Decide which firms bill by file and which bill by hand, and record it at onboarding. Give manual bills a documented line-level review, run duplicate and rate checks on both channels, and correct rejections through linked resubmissions. Then measure each channel on its own.

Frequently asked questions

What are non-LEDES invoices?

Non-LEDES invoices are legal bills submitted without a structured LEDES file, either typed into the eBilling portal by hand or converted from a PDF. They need a documented line-level review, because every field was entered or extracted.

What is a LEDES invoice?

A LEDES invoice is a legal bill submitted as a structured text file in the Legal Electronic Data Exchange Standard, which lets an eBilling system read and validate every line automatically. The most widely used version, LEDES 1998B, is a pipe-delimited file with 24 fields per line.

Does PDF conversion remove the need for manual invoice review?

PDF conversion speeds up data capture, and the extracted line items still need review before submission. The vendor checks the lines and invoice fields first, and the client’s reviewer should verify them against the original PDF.

Should manual invoices follow the same approval workflow as LEDES files?

Manual invoices should follow the same approval workflow as LEDES files, with routing decided by matter, amount, and exception type. The submission channel affects how the data is captured and should have no effect on who approves the bill.

How are duplicate invoices caught across manual and electronic channels?

Duplicate invoices are caught across manual and electronic channels by running the same duplicate checks after every invoice is ingested. The checks compare attributes such as matter, vendor, amount, currency, worked date, timekeeper, rate, and billing codes.

How does a law firm correct a rejected invoice?

A law firm corrects a rejected invoice by resubmitting it linked to the original rejected invoice, whether the bill was a LEDES file or a manual entry. In Counsel Exchange, that link keeps the full history of the bill in one place.

---

*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.*