Legal Invoice Review.
Every line, every guideline, every time.
Leah reviews every outside counsel invoice line against the engagement letter, the billing guidelines, and the matter budget. Violations surfaced. Adjustments drafted. The response to outside counsel ready to send.
The leakage hides in the lines no one reads.
Outside counsel invoices reviewed sample-only
Legal ops sees thousands of line items per cycle. Manual review covers headline totals and a thin sample. The vast majority of lines are paid without anyone reading them, and the leakage hides in the lines no one opens.
Block billing slips through
A single eight-hour entry covering research, drafting, calls, and review is the canonical guideline violation. Reviewers flag it when they see it, but most blocked entries pass through because no one is reading every narrative.
Rate violations missed
Approved rate cards live in engagement letters. Invoices arrive with rate creep, unapproved escalations, and timekeepers who were never on the matter. Without line-level matching against the rate card, the variance gets paid.
Charged non-allowed work paid
Billing guidelines exclude internal training, conflict checks, file management, summer associate time, and admin tasks. These categories show up routinely in narratives and clear approval because no one is checking guideline-by-guideline at the line.
Matter budgets blown without notice
Budgets are agreed at engagement and forgotten in operations. By the time finance reconciles spend to budget, the matter is already over its cap and the conversation with outside counsel happens after the fact, not before.
Firm-by-firm consistency drift
Reviewer A is strict on block billing. Reviewer B lets it pass. Firm 1 gets challenged on travel time. Firm 2 does not. Inconsistent enforcement undermines the guidelines and trains outside counsel on what they can actually get away with.
Every line item, parsed and structured
Leah ingests outside counsel invoices in LEDES, PDF, or e-billing formats. Every line is extracted with timekeeper, rate, hours, narrative, task code, activity code, and matter reference. The result is structured data the review engine can reason over, not a stack of documents a human has to flip through.
“We used to print invoices to review them. Leah turned every invoice into structured data the day it arrives, and the review work shifted from data entry to actual judgment.”
Director of Legal Operations, Global Insurer
Five steps from invoice arrival to response sent
Leah operates on top of your e-billing system. No rip and replace. Value from the first invoice cycle.
Receive Invoice
Outside counsel invoices arrive via LEDES, PDF, e-billing system, or firm portal. Leah ingests the source format and normalizes it into one structured representation.
Parse Line Items
Every line is extracted with timekeeper, rate, hours, task code, activity code, and the full narrative. Each invoice is linked to the governing engagement, guidelines, and budget.
Apply Guidelines
The engagement letter rate card, billing guidelines, staffing constraints, and matter scope are evaluated against every line. Rules run at the line, not the invoice.
Detect Violations
Block billing, rate variances, non-allowed work, vague narratives, and staffing violations are flagged with the offending line, the rule, and the proposed adjustment.
Draft Adjustments
Leah drafts the line-level write-down, the rationale tied to the specific guideline, and the response to outside counsel. Legal ops reviews, edits, and sends.
Got Questions? Get Answers.
E-billing systems collect invoices, route approvals, and store data. They do not read narratives, interpret engagement letters, or apply billing guidelines at the line level. Leah operates on top of your e-billing system. Invoices flow in through the same channel, but every line is read against the full rule set, violations are surfaced with proposed adjustments, and the response to outside counsel is drafted automatically. The e-billing system stays. The review work changes.
No. Leah reads your existing engagement letters and outside counsel guideline documents and turns them into a structured rulebook the review engine applies. If your guidelines change, you update the document and Leah picks up the new rules. The guidelines remain the policy. Leah is the enforcement layer.
Leah ingests LEDES 1998B, LEDES 2000, LEDES XML, e-billing exports, and PDF invoices. Smaller firms that bill in PDF are parsed with the same line-level extraction as LEDES files. There is no requirement that every panel firm move to a single format before the review engine works.
Block billing thresholds, vague-narrative criteria, and partner-on-associate-task rules are inherently judgment heavy. Leah surfaces the line, the rule it appears to violate, and the rationale for the proposed adjustment. Legal ops reviews and decides. Where confidence is below threshold, the line is queued for human review before any adjustment is communicated to outside counsel.
Most legal ops teams move from a multi-week manual review cycle to a same-day cycle in the first month. Invoices are parsed, evaluated, and queued for review the day they arrive. The bottleneck shifts from reading narratives to approving the proposed adjustments, which is the work that benefits from human judgment.
Yes. Leah is deployed by insurers, financial institutions, manufacturers, and healthcare groups with strict data protection requirements. Engagement letter and invoice content does not train Leah's underlying models. Customer data is encrypted in transit and at rest. SOC 2 Type II, GDPR, CCPA, HIPAA-ready, and ISO 27001 aligned. Private instance deployment is available.
