Checking 50 LEDES invoices by hand vs. in one batch
If you're checking LEDES invoices one at a time, here's what a batch of 50 actually looks like today: upload file one, wait for the report, note whatever's wrong, upload file two, repeat 49 more times. Nothing about that process is hard, it's just fifty times the single-file process, and the tedium is exactly where real mistakes creep in: a fixed file two that never got re-uploaded, a report you meant to come back to and didn't.
What batch checking actually changes
POST /api/check/bulk takes up to 25 files in one request (LEDES_MAX_BULK_FILES, a starting number, not a hard architectural limit) and runs the same check against every one of them, Tier 1 or Tier 2, your choice, applied uniformly across the batch. You get back a task id, poll it, and when it's done you have two things: a per-file report for each invoice in the batch (identical in shape to what a single-file check returns, so nothing about reading one report changes) and a roll-up summary across the whole batch, counts of how many passed and how many didn't.
The part that matters most for a real workflow: one bad file never blocks the other 24. A single-file process fails hard on the file you're looking at, full stop. A batch check isolates failures per file, so a batch of 25 with one malformed export still gives you complete reports on the other 24 immediately, and tells you which one needs attention, rather than making you find it by process of elimination.
Who this actually matters for
Not someone checking one invoice before submitting it, that's what the free tier already does well. This is for anyone who receives or generates LEDES files in volume: a firm's billing team clearing a batch before a monthly submission deadline, or a legal-tech team validating exports from their own billing system before those exports ever reach a client's e-billing portal. If the LEDES files you deal with usually arrive or get generated in a group rather than one at a time, that's the actual signal this is worth it, not invoice count in the abstract.
Anonymize and normalize batch too
The same shape (POST /api/anonymize/bulk, POST /api/normalize/bulk) applies past just checking: producing anonymized share copies or normalized downloads across a whole batch at once, not one file at a time through the same UI twenty-five times.
Try it
Bulk upload is part of Ledger ($49/mo or $490/yr, flat per firm, no seats) — it's not included on the Day Pass, which is scoped to single-file Tier 2 checking for 24 hours. If the actual shape of your work is "a stack of files, not one file," that's specifically the gap Ledger closes over checking single files repeatedly.