UTBMS Codes: Validating Task-Based Billing

UTBMS codes are the standard codes law firms use to classify each line of a legal invoice by phase or task, by the type of activity performed, and by expense type. Validated properly, they turn a LEDES invoice into structured data that shows what work was done, at what stage of the matter, and at what cost.

Most legal departments already require the codes. Fewer check them well. Missing codes, codes from the wrong set, and work logged against the wrong phase all pass through review and quietly weaken every spend report built on top. This guide covers what the codes describe, which checks to automate, how phase budgets use them, where human review fits, and how to test and report on task-based billing.

What are UTBMS codes?

UTBMS codes are the classification codes of the Uniform Task-Based Management System, a standard for describing legal services and expenses at the line-item level. The system was developed in the 1990s by US legal industry bodies working with an accounting firm, and the standards are now maintained by the LEDES Oversight Committee.

The codes are grouped into code sets for different kinds of work. The litigation set is the most widely used, and organizes work into phases such as case assessment, pleadings and motions, discovery, trial, and appeal, with numbered codes like L100 through L500. Departments choose which code sets apply to which matter types, and that choice should be written into your billing guidelines.

The value comes from consistency. When every firm codes the same way, you can compare discovery spend across matters, firms, and years using one shared vocabulary.

How do UTBMS codes fit into a LEDES invoice?

UTBMS codes sit on each line of a LEDES invoice alongside the timekeeper, date, hours, rate, and amount. LEDES provides the electronic file format, and UTBMS provides the codes that describe the work on each line.

Together they produce a line-item record of who did the work, what task and activity it was, how long it took, and what it cost. That record is what makes automated review and spend analysis possible. Without codes, an invoice line is a free-text description and a number, and every analysis depends on someone reading descriptions by hand.

The LEDES billing format has several versions, but all of them carry task, activity, and expense codes in defined fields, so validation can target those fields directly. The codes themselves are maintained as a public standard, and the UTBMS site hosted by the LEDES Oversight Committee publishes code sets for litigation, counseling, bankruptcy, intellectual property, and mergers and acquisitions.

What do task, activity, and expense codes describe?

Task, activity, and expense codes describe different parts of the same invoice line: the task or project, the type of work done, and the kind of cost incurred.

• Task codes. Identify the task or project performed, usually within a phase, such as a discovery task under the litigation set. Phase-level grouping is what most budgets and reports use.
• Activity codes. Identify the type of activity on the line, such as planning, research, drafting, review, communication, attendance, or file management. Activity codes show how time was spent within a task.
• Expense codes. Classify expense lines, such as copying, travel, or filing fees, so disbursements can be reported and checked separately from fees.

A fee line normally carries a task code and an activity code. An expense line carries an expense code. Confirm which combinations your configuration requires, since requirements vary by implementation and code set.

Which UTBMS checks should eBilling validate automatically?

eBilling should validate the objective UTBMS checks automatically: whether each required code is present, whether it is a valid code, and whether it is permitted for the matter. These checks have one right answer, so a rule can make the call.

Onit’s invoice rejection reasons include invalid task code, missing task code, missing activity code, and missing expense code, alongside unapproved timekeeper rate and unauthorized. Those reasons map neatly to the core automated checks:

• Missing codes. Any fee line without a task or activity code, or expense line without an expense code, is rejected.
• Invalid codes. A code that does not exist in the configured code set is rejected.
• Wrong code set. A litigation code on an advisory matter, or the reverse, is rejected or flagged depending on policy.
• Restricted codes. Codes your guidelines exclude for a matter type are rejected with a specific reason.

Reject with the exact reason and line number, so the firm can fix the invoice in one pass. Rejections are rising across the market, and billing data from about 400 law firms shows invoice rejection rates climbed from 11 to 18 percent in 2025. LEDES invoice validation applies the same rule to format and data errors.

How do UTBMS phase codes drive matter budgets?

UTBMS phase codes drive matter budgets by giving each budget line a phase to track against. In SimpleLegal, UTBMS phase codes form the basis for certain budgets, so spend coded to a phase counts against that phase’s budget.

Phase budgets make overruns visible early. A matter that has used 80 percent of its discovery budget before depositions start is a conversation to have now. In Onit, eBilling rules can check whether spend on a task code reaches a predefined budget threshold and flag or reject the invoice when configured to do so.

A practical setup sets two thresholds per phase. A warning threshold at around 80 percent of the phase budget triggers a flag to the matter lead. A hard threshold sends spend above 100 percent for approval, or rejects it where the engagement terms allow.

Phase budgets only work if the coding is accurate, which is why code validation comes first.

Which task-based billing problems need a human reviewer?

Task-based billing problems need a human reviewer when deciding whether the code is correct depends on what actually happened on the matter. A valid code can still be the wrong code, and no rule can see that from the invoice alone. These calls belong to the human layer of automated legal invoice review, which keeps judgment with people.

• Wrong phase. Trial preparation work coded to discovery, for example, which shifts spend between budgets.
• Activity mismatch. A description that reads as drafting coded as communication.
• Catch-all codes. Heavy use of general or “other” codes that hide what the work was.

Reviewers in Onit can see budget, matter, task codes, activity codes, and timekeepers together during invoice review, which makes these patterns easier to spot. Where one firm repeatedly miscodes, raise it with the firm and add guidance to your outside counsel billing guidelines.

How should law firms be told about UTBMS requirements?

Law firms should be told about UTBMS requirements in writing before their first invoice, with the code sets, required fields, and rejection rules for each matter type. Most coding errors in the first few months come from firms that never received the rules.

A one-page coding guide usually covers four things:

• Code sets. Which UTBMS code set applies to each matter type, such as litigation or counseling.
• Required fields. Which codes every fee line and expense line must carry.
• Restricted codes. Any codes your guidelines exclude, with the reason.
• Worked examples. Two or three correctly coded invoice lines firms can copy.

Send it with onboarding materials and again whenever the rules change. Onboarding law firms to eBilling goes smoothly when the rules arrive before the first rejection.

How do you test UTBMS validation rules before go-live?

UTBMS validation rules are tested by submitting invoices built to break each rule and confirming every one is rejected or flagged with the right reason. Twenty to thirty test invoices cover most configurations.

Build lines with a missing task code, a missing activity code, an expense with no expense code, a code that does not exist, a code from the wrong set, a restricted code, and spend that crosses each budget threshold. Add clean invoices that should pass untouched. Run them under at least two firm accounts and check the rejection message text.

How does UTBMS data improve legal spend reporting?

UTBMS data improves legal spend reporting by letting you break spend down by phase, task, activity, and timekeeper across every matter and firm. Accurate codes are what make these comparisons trustworthy.

• Spend by phase. Compare discovery or trial spend across litigation matters and firms.
• Activity mix by firm. See how much time each firm spends on research, drafting, and review.
• Expense spend by type. Track copying, travel, and filing costs separately from fees.
• Phase spend against budget. Spot overruns early, and use two or three years of data to budget new matters. Legal analytics dashboards are only as reliable as the data underneath them, and for spend, that data is largely UTBMS codes.

Conclusion

UTBMS codes are only as useful as the validation behind them. Choose the code sets for each matter type, automate the checks for missing, invalid, and restricted codes, and use phase codes to track budgets with clear thresholds. Keep miscoding judgments with reviewers, give firms a written coding guide, and test every rule before go-live. With that in place, every invoice adds reliable data to your spend reporting.

Frequently asked questions

What are UTBMS codes?

UTBMS codes are standard codes from the Uniform Task-Based Management System that classify each legal invoice line by task or phase, activity, and expense type. They are carried in LEDES invoices so legal spend can be validated and reported consistently.

Who maintains the UTBMS standard?

The UTBMS standard was developed in the 1990s by US legal industry bodies, and it is now maintained by the LEDES Oversight Committee.

What is the difference between task and activity codes?

Task codes identify the task or project performed, usually within a phase of the matter. Activity codes identify the type of work done on the line, such as research, drafting, or review.

Which UTBMS errors can Onit reject automatically?

Onit’s invoice rejection reasons include invalid task code, missing task code, missing activity code, and missing expense code. Rules can be configured to reject invoices with these errors.

How do UTBMS phase codes relate to budgets?

UTBMS phase codes can form the basis for matter budgets, so spend coded to a phase is tracked against that phase’s budget. Rules can flag or reject spend that crosses a set threshold.

Can automated rules catch miscoded UTBMS lines?

Automated rules catch missing, invalid, and restricted codes. Lines with a valid but wrong code, such as work logged to the wrong phase, usually need a human reviewer.

---

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