How to Write Outside Counsel Guidelines Your E-Billing System Can Enforce
Most billing guidelines are written for lawyers and enforced by nobody. This ten-step playbook rewrites them as rules your e-billing system can check, reject and defend across currencies and borders.
Why Guidelines Written in Prose Fail at the Invoice Screen
If your e-billing platform keeps passing invoices that break your policy, the platform usually isn't the problem. The guidelines are. Most outside counsel guidelines read as advice to lawyers ("firms should staff matters efficiently") when the system needs instructions it can test ("no more than two timekeepers may bill to a single deposition"). A reviewer can apply the first sentence. Software can't.
This playbook turns policy into testable rules. It's written for in-house teams with panels in several countries, where one invoice may arrive in euros with VAT, the next in rupees with GST, and a third in dollars with no tax line at all. The goal: every automated rejection traces to a numbered clause the firm signed, so the firm can't argue it away.
Sort Every Clause Into Rules, Flags and Judgment Calls
Step 1: Pull your current guidelines, engagement letter templates and side agreements into one document, then number every obligation. Step 2: Label each one. A hard rule is something the system rejects automatically. A flag goes to a reviewer. A judgment call stays with the matter owner. Expect to drop or rewrite a large share of your clauses, because many turn out to be untestable.
| Policy intent | Machine-checkable version | Enforcement |
|---|---|---|
| Reasonable rates | Rate per timekeeper ID must not exceed the approved rate table for the matter's currency | Hard rule |
| Efficient staffing | Maximum timekeepers per task code per day | Flag |
| No block billing | One task code per line; lines over 3.0 hours with multiple verbs flagged | Hard rule plus flag |
| No overhead charges | Expense codes for secretarial work, word processing or local phone calls rejected | Hard rule |
| Work must be valuable | None | Judgment call |
A clause with no testable version belongs in the relationship section of the document. Keep it out of the billing rules.
Lock Rate Caps to Timekeepers, Currencies and Dates
Step 3: Approve rates per timekeeper, not per seniority band, and tie each rate to a currency and an effective date. Banded rates invite arguments over whether someone is a senior associate or counsel. A rate attached to a named timekeeper ID gives you a clean comparison.
For cross-border billing, state which currency is authoritative and which exchange-rate date applies. Suggested wording: "Invoices must be issued in the currency stated in the matter's rate approval. Fees billed in any other currency will be rejected. Where conversion is required for reporting, the client's treasury rate on the invoice date applies."
Add a notice period for increases, commonly 60 to 90 days before your fiscal year starts, and state that a new rate applies only once approved in the system. Otherwise increases arrive quietly in the January invoices.
Write Staffing and Block-Billing Rules a Parser Can Read
Step 4: Staffing. Set numeric limits on how many timekeepers may attend internal conferences, depositions, hearings or client calls, and cap transition time when a new timekeeper joins (say, no charge for the first 5 to 10 hours). Make these flags, not hard rejections, because trials and crisis matters will legitimately break them.
Step 5: Block billing and increments. Require 0.1-hour increments, one task per line and a minimum narrative length. Suggested wording: "Each time entry must describe a single task with a single UTBMS task and activity code. Entries combining multiple tasks will be rejected in full and may be resubmitted once, itemized." Reject the whole line rather than reducing it. Firms learn the rule faster.
Set Expense and Tax Rules That Survive Different Tax Regimes
Step 6: Publish an expense whitelist by UTBMS expense code (E-codes), with caps and receipt thresholds. Express travel class, hotel caps and per-diem limits per region, since a single cap won't suit both Singapore and São Paulo.
Tax is where single-country guidelines break. Firms in the EU and UK generally charge VAT, Indian firms charge GST, many Gulf states apply or are introducing VAT regimes of their own, and some jurisdictions charge no tax on legal services at all. Require tax in its own line and field, never folded into fees. That raises the format question. LEDES 1998B handles multiple currencies and separate tax poorly, so international panels should consider LEDES 1998BI or LEDES XML 2.1. Name the required format in the guideline itself. Tax treatment varies by jurisdiction and by where the service is supplied, so have your tax adviser confirm invoice requirements for each country before you hard-code them.
Make UTBMS Codes and Budgets Do Real Work
Step 7: Choose your code sets and require them. Litigation matters normally use the L-series task codes with A-series activity codes. Advisory and transactional work fits less neatly, so decide whether to use the counseling or project code sets or a short custom list, and publish it.
Then link codes to budgets. If the matter budget is held by phase, the system can flag an invoice once a phase reaches, say, 80% of budget and reject anything over 100% until a revised budget is approved. Without that link, UTBMS codes are labels nobody reads.
Require Accruals on a Fixed Calendar
Step 8: Finance needs to know about work not yet invoiced. Require firms to submit accruals through the platform by a fixed working day before each month-end or quarter-end. The date depends on your fiscal calendar: many companies run a calendar year, while Indian and Japanese companies commonly close in March.
Suggested wording: "Firms must submit unbilled fees and expenses per matter by the third working day before period close. Matters without a submitted accrual will be treated as zero for that period." Add a time-to-bill limit too, commonly 60 to 120 days after the work, with late time rejected. That stops surprise invoices for work done eight months earlier.
Build an Appeals Process That Keeps Rejections Final
Step 9: A rejection only holds if the appeal route is narrow and time-limited. Allow one appeal per line item, filed inside the platform within a set window (30 days is common), citing the guideline clause and the reason for an exception. Name who decides, typically the matter owner for staffing flags and legal operations for rate and expense rules, and set a response time.
Suggested wording: "Adjustments not appealed within 30 days of notification are final and may not be rebilled. Approval of an exception applies only to the line appealed and does not amend these guidelines." That last sentence matters. Without it, one approved exception gets cited as precedent in every later dispute.
Pilot, Measure and Decide What to Automate First
Step 10: Before full rollout, run the rules in flag-only mode against two or three months of past invoices. Rules that would have rejected legitimate work point to badly worded clauses. Then go live with a small panel first.
Platform choice limits how much you can automate. Brightflag, Onit, LawVu, Wolters Kluwer ELM Solutions, Thomson Reuters Legal Tracker, SimpleLegal and Mitratech all support LEDES billing and rule-based invoice review, but they differ in multi-currency and tax handling and in how many rules you can configure. Typical 2026 market ranges run from roughly $15,000 to $60,000 a year for mid-sized departments and $75,000 to $250,000 or more for enterprise deployments, and some vendors also charge firms a submission fee. These figures vary widely by contract and region, so get quotes. Red flags: tax handled only as free text, rate tables that can't hold more than one currency per timekeeper, and appeals handled outside the system by email.
Our rule for sequencing: turn on hard rules for rates, expenses and late time in month one, because they're objective and the firm has little to argue with. Add staffing and block-billing flags around month three, once reviewers trust the output.
Quick answers
Should we reject non-compliant invoices automatically or reduce them?
Reject for objective breaches such as unapproved rates, missing task codes or barred expenses, because rejection makes the firm fix its process. Use reductions or reviewer flags for judgment-based items like staffing. Mixing the two without clear criteria creates disputes.
Which LEDES format should international law firms use?
For panels billing in several currencies or charging VAT or GST, LEDES 1998BI or LEDES XML 2.1 are the usual choices because they carry tax and currency fields. LEDES 1998B suits single-currency billing without separate tax. State the required format in your guidelines and confirm your platform accepts it.
Do law firms have to accept our billing guidelines?
Generally, firms are bound only once the guidelines are incorporated into the engagement terms, usually through the engagement letter or panel agreement. Get written acceptance and version-date the document so you know which rules applied to which invoices. Have your own counsel review the incorporation wording for each jurisdiction.
How often should outside counsel guidelines be updated?
An annual review aligned to the rate-approval cycle works for most teams, with mid-year changes only for errors or regulatory needs. Give firms 30 to 60 days' notice before new rules take effect in the e-billing system, and apply changes going forward only, never to work already performed.
Written by the Counsel Core Tech editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.