Method note: this brief proposes a source-led review approach. It does not claim that private client or firm data has been collected.
Question and scope
This protocol asks how often the rate used on an invoice disagrees with the approved rate card and the matter record. The unit is a billed time line, and the measure is whether the rate, the timekeeper, and the effective date match the client's written approval. The study covers invoices issued during the period, not the rate negotiation itself. It does not evaluate whether the approved rate is competitive.
Scope the study to matters with at least one timekeeper whose rate changed during the engagement or during the prior twelve months. Include invoices that were paid, adjusted, and still open so the denominator reflects the full workload. Exclude lines with no timekeeper rate, such as flat-fee or cost-only lines, and record the number excluded. State the billing system, the rate card source, and the owner of the analysis.
Defining the event
Define a rate disagreement as a billed line where the rate, the timekeeper identity, or the effective date does not match the approved rate card and the client's written approval. A line with the right rate but the wrong timekeeper is still a disagreement for this study. A line with a correct rate that was approved orally is a documentation gap, not a rate error. Write two examples and one boundary case before coding.
Define a stale matter record as a matter where the rate field was not updated after an approved change. Keep it separate from a missing client approval and from a keying error. A matter can have more than one cause, so code the primary cause and note the secondary one. The separation shows whether the fix belongs to the rate process, the matter setup, or the invoice review.
Population and denominator
The population is every billed time line on the included invoices. Report the number of invoices, the number of lines, the number excluded, and the number in the final sample. Count lines rather than invoices, because one invoice can contain several timekeepers and rates. If a line is billed at a blended rate, state how it was treated in the coding guide.
Use the billed line as the denominator and report the disagreement rate by line and by billed value. A small number of high-value lines can carry most of the exposure, so the value measure matters. Keep both measures in the report. The value measure should use the billed amount, not a notional rate.
Evidence sources
Use the invoice, the approved rate card, the matter record, and the client's written rate approval as the primary evidence. Compare the rate and the effective date across all four sources and record the date each was observed. If the matter record and the rate card disagree, do not assume that one is correct without the client approval. The evidence log should let a second reviewer repeat the match.
Rank the sources so reviewers know what to trust first. A signed client approval is stronger than an internal rate card, and a current rate card is stronger than a matter record that was never updated. A billing system note is weaker than a dated approval. Record the evidence type for each line so the analysis can separate a documentation gap from a rate error.
Sampling
Sample across clients, practice groups, and timekeeper levels so one rate change does not define the result. Include lines with a recent increase, a client-specific exception, and no change at all. Draw the sample before reading the invoice outcome so the selection is not biased toward the disputed lines. If the population is small, review every line and extend the period.
Stratify the sample by whether the rate change had a written client approval on file. A change with a clear approval tests the matter record and the invoice, while a change without one tests the approval process. Report the disagreement rate for each stratum rather than pooling them. The reader should be able to see where the control breaks.
Coding the record
Use a short code list that points to a specific repair. Code each line as matched, stale matter record, missing client approval, wrong timekeeper, wrong effective date, keying error, or unknown. Add a note for the rate difference and the date it was observed. Keep the code list short enough that two reviewers can apply it consistently.
Have a second reviewer code a sample and compare the results. Resolve disagreements by returning to the rate card and the client approval, not by majority vote. Report the agreement rate and revise any code that is applied inconsistently. If the reviewers cannot agree on which source is authoritative, stop and fix the hierarchy before continuing.
Measuring the variable
Measure the disagreement rate by line, by billed value, and by cause. Report the median and the range for the rate difference so a few large matters are visible. Measure the time between the approved effective date and the first invoice that used the new rate. Keep the raw counts with the analysis file so a reviewer can check the calculation.
Do not convert the rate difference to a revenue figure without the approved fee and collection data. The study measures rate accuracy, not profitability. If the firm wants a revenue view, run it as a separate analysis with the finance owner. A precise dollar figure built on an unapproved rate is less useful than a clear mismatch count.
Analysis and reporting
Report the overall disagreement rate, the rate by cause, and the number of lines behind each figure. Show the share of billed value affected and the most common stale-record pattern. Compare only groups with similar rate structures and approval rules. Include the lines that matched so the report shows the full distribution.
Give the reader one table that answers the main question and put the coding detail in an appendix. Write the finding in plain language before presenting the technical definition. Include the cases that contradict the pattern rather than hiding them in an average. A report that cannot be acted on is just another record of the past.
Limits and sources of error
A missing approval is not proof that no approval existed, and an updated rate card is not proof that the client agreed. Report the completeness of the evidence before drawing a conclusion. Small samples, mid-period changes, and reviewer disagreement can all limit interpretation. A rate approved in a call may be correct but undocumented, which is a different problem from a wrong rate.
Avoid comparing clients with different rate structures or effective-date rules. A client with a fiscal-year rate cycle will produce a different pattern from one with a calendar-year cycle. Describe the context beside the rate and avoid ranking individual billers. The purpose is to improve the rate record, not to judge professional worth.
Privacy and retention
Store the invoices, rate cards, and client approvals in a controlled folder with access limited to the study team. Remove client names, rates, and matter details from the analysis file when they are not needed. If an example is shared, use a role label and redact the client and the specific rate. Keep the unredacted evidence separate from the working analysis.
Do not circulate a client-level or timekeeper-level list about rate disagreements outside the management context. Aggregate the results before sharing them more broadly, and check that a small group cannot be re-identified. The same rule applies to screenshots of the billing system and to quoted client messages. Privacy is part of the method, not an afterthought added at the end.
Applying the result
Choose one change that matches the most common cause. If the matter record is stale, add a rate-change task to the matter setup checklist with a named owner and an effective date. If the client approval is missing, add a required field before the rate can be saved. If keying errors dominate, add a second review at the first invoice after a change. Test one change before adding another.
A lower disagreement rate is not the only useful outcome. Faster invoice review and fewer client questions can improve the process even when the rate stays similar. Report the direct result and the service result separately. Stop the change if it adds a step that the team works around instead of using.
Review cadence
Repeat the study each quarter and after any rate cycle or matter-system change. Keep the definitions and the unit stable so periods can be compared. Report the lines that were excluded or still open beside the main rate. Review the coding guide after the first repetition and keep the changes visible.
Review the result with the billing manager and the rate owner, not only with the preparer. Ask which fix is easiest to sustain and which gap causes the most client questions. Set one change and a follow-up date, then check whether the change held. The next study should test the repair, not just repeat the same count.
Put the guidance to work
Choose one recurring billing workflow, identify its authoritative source records, and name the owner who reviews exceptions. We can help turn that boundary into a focused support role.
Discuss your workflow


