UTBMS Codes, LEDES Billing, and OCG Compliance
The invoice came back short. You billed a carrier for a month of defense work, sent it through their e-billing portal, and a few days later part of it is flagged: two lines reduced for block billing, a paralegal's research kicked out because that timekeeper wasn't on the approved list, one narrative rejected as too vague to review.
The work was real and already done. The money is stuck behind a formatting and compliance problem, and three things drive it: UTBMS codes, LEDES files, and outside counsel guidelines. They get confused constantly. Here's what each one is, why invoices get rejected, and where the manual effort really goes.
What UTBMS, LEDES, and OCGs actually are
Start with UTBMS. The Uniform Task-Based Management System is a standardized set of task and activity codes for classifying legal work. Litigators know the L-code series: L110 for fact investigation, L120 for analysis and strategy, L240 for dispositive motions, and so on, each paired with an activity code like A101 (plan and prepare). The point of a shared code set is comparison. A carrier can see what discovery or strategy costs across every firm it retains, because everyone tags the work the same way.
LEDES is the envelope. The Legal Electronic Data Exchange Standard defines the file your invoice ships in, and the common version is LEDES 1998B. It's a structured text file with one line per time entry, carrying the date, timekeeper, hours, rate, task and activity codes, and narrative. Your billing system generates it; the client's e-billing system reads it. If a required field is missing or the file is malformed, it bounces before a person ever sees it.
Outside counsel guidelines are the rulebook. OCGs are the client's or carrier's written rules for what you may bill and how: which timekeepers are approved and at what rate, the billing increments allowed, what counts as non-billable clerical work, whether block billing is permitted (it usually isn't), and how specific a narrative has to be. Every carrier writes its own, and this is the document a reviewer measures each line against.
The three fit together in order. Guidelines set the rules, UTBMS codes classify the work, and LEDES carries it to the client. Break any one of them and the invoice suffers.
Why e-billing invoices get rejected
Rejections and reductions come in a few predictable shapes.
The first is wrong or missing task codes. An entry tagged L190 when the guidelines wanted L120, or no code at all on a matter that requires one. The reviewer can't map the work to a budget line, so it gets queried and held.
The second is block billing, several tasks compressed into one entry with one number: "reviewed discovery, called client, drafted motion, 3.2." Most guidelines want one task per line so each can be judged on its own, and block-billed entries are among the first things e-billing systems and auditors flag. We went deeper on why in our piece on block billing.
The third is a narrative that trips a guideline. Billing for clerical work the rules exclude, like organizing files or scheduling. Time from a timekeeper who was never approved on the matter. A description too vague to justify the hours, the classic "attention to file." Each of these is a rule written down in a PDF, and each violation is a line the carrier reduces or kicks back.
Every rejection carries the same cost: someone reworks the entry, resubmits, and waits another cycle to get paid. The work itself was fine. The payment is stuck behind process.
The manual tax at month-end
Here's the part that quietly burns hours. Coding entries and checking them against a guideline is exactly the work attorneys avoid, because it's tedious and it isn't lawyering. So it drifts downstream. The attorney writes a plain narrative, leaves the code blank, and moves on.
At month-end it lands on billing staff. A coordinator opens the draft invoice next to the carrier's guideline PDF and the approved-timekeeper list, and works line by line: assign the task code, catch the block-billed entry and split it, rewrite the vague description, pull the paralegal time that isn't approved on this file. On an active matter that's hundreds of lines, against a dozen clients who each have a different rulebook.
Do it carefully and the invoices clear. Do it under deadline and things slip through, which is how you land back at a reduced invoice next month. Either way it's a recurring scramble that grows with your caseload, and it's a big reason panel and insurance defense work feels heavier to run than the rate card suggests. We wrote more about that in AI timekeeping for litigation and insurance defense.
Where Ajax fits
Ajax is the automatic timekeeping tool we build, and this is one of the problems it solves. The aim is to get the entry right as it's created instead of repairing it at month-end.
Task codes are configured per client. When a carrier requires UTBMS L-codes and activity codes, Ajax applies them to entries as it drafts them, based on the captured work and that client's rules. A different client with a different code set, or none at all, is handled its own way.
Outside counsel guidelines can be ingested. Give Ajax the rules and it drafts narratives to fit them from the start: a full task per line rather than block billing, the specificity a reviewer expects, clerical work left off. The narrative arrives written to the standard instead of flagged against it later.
Increments and rules differ client by client. Billing increments default to tenths of an hour, and a client that wants quarter-hour or fifteen-minute increments is a configuration change, not a rebuild. One attorney covering five carriers doesn't have to keep five rulebooks in their head.
What Ajax doesn't do is submit to the carrier for you. Released entries flow into your billing system with the codes already attached, and your billing system produces the LEDES file the e-billing portal ingests. Getting the codes and narratives right upstream is what makes that export clear review the first time. Every draft stays private to the timekeeper until release, so no one's mid-day work is exposed before it's ready. For one firm's experience with this, see our Doyle Seelbach case study.
FAQ
What are UTBMS task codes?
UTBMS task codes are a standardized set of task and activity codes law firms use to classify legal work on a bill. UTBMS stands for the Uniform Task-Based Management System; litigation uses the L-code series (case assessment, motions, discovery, trial) with activity codes, so a client or carrier can compare and budget spend across every firm it retains.
What is a LEDES file?
A LEDES file is the standardized electronic format a law firm's invoice travels in on its way to a client's or carrier's e-billing system. LEDES stands for the Legal Electronic Data Exchange Standard (commonly the 1998B version): a structured text file with one line per time entry, carrying date, timekeeper, hours, rate, task and activity codes, and narrative. The firm's billing system generates it; the client's reads it.
What are outside counsel guidelines?
Outside counsel guidelines are a client's or carrier's written rules for what outside counsel may bill and how. They set approved timekeepers and rates, allowed increments, non-billable clerical work, whether block billing is permitted, and how detailed narratives must be, and they vary from client to client. A reviewer measures each invoice line against them.
Can Ajax apply task codes automatically?
Yes. Task codes are configured per client, and Ajax applies them to entries as it drafts them, based on the captured work and that client's rules. Outside counsel guidelines can also be ingested so narratives comply from the start, and increments can be set per client, so entries reach review already coded rather than raw.
Bring a real client's rulebook to a demo and we'll configure it live, codes, guidelines, increments and all.
