Home / Research / Invoice follow-up

What share of invoice inquiries close without a fee adjustment?

An outcome study that follows each client invoice inquiry to closure and separates explanation-only resolutions from credits, write-downs, and rework.

Legal Billing Assistant Editorial Team · Published

Editorial illustration representing What share of invoice inquiries close without a fee adjustment?
Table of contents

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 what share of client invoice inquiries close without a fee adjustment. The unit is an inquiry about an issued invoice, and the measure is the closure outcome: explanation only, credit, write-down, rework, or still open. The study follows the inquiry from receipt to closure, not just the first response. It does not evaluate whether the client's question was reasonable or whether the invoice was correct.

Scope the study to invoices issued during the period that received at least one inquiry. Include inquiries that arrived before the due date, after the due date, and after payment. Exclude routine reminder messages that did not ask a question, and record the number excluded. State the billing system, the client communication channel, and the owner of the analysis.

Defining the event

Define an inquiry as a client message that questions an amount, a time entry, a cost, a rate, or the invoice format and expects a response. A request for a copy of the invoice is an administrative request, not an inquiry for this study. A message that combines an inquiry with a payment instruction counts as an inquiry. Write two examples and one boundary case before coding.

Define closure as the point when the client confirms the resolution or the firm records a final adjustment and no further response is pending. An explanation that the client never acknowledges is not closed for this study. Keep still-open inquiries in a separate category so the denominator reflects the full workload. A reopened inquiry after closure should be coded as a new event with a link to the original.

Population and denominator

The population is every inquiry received on an included invoice during the period. Report the number of invoices, the number of inquiries, the number excluded, and the number in the final sample. If one invoice received several inquiries, count each one separately or state the rule used. Keep the unit stable across periods so the closure rate is comparable.

Report the share closed without an adjustment, the share closed with an adjustment, and the share still open. Also report the share that required rework even when the fee did not change, such as a corrected narrative or a resubmitted cost receipt. A pure explanation and a silent correction are different outcomes, so keep them apart. Report the adjustment value beside the count so a small number of large credits cannot hide behind a high explanation rate.

Evidence sources

Use the client message, the invoice, the time and cost records, and the final response as the primary evidence. Compare the question with the invoice line and record the date each was observed. If the client's confirmation is missing, mark the inquiry as unconfirmed rather than assuming closure. The evidence log should let a second reviewer repeat the match.

Rank the sources so reviewers know what to trust first. A written client message is stronger than an internal summary of a call, and the invoice record is stronger than a later recollection. A credit memo or adjustment is stronger than a verbal promise. Record the evidence type for each inquiry so the analysis can separate a documentation gap from a real outcome.

Sampling

Sample across clients, invoice sizes, and inquiry types so one large dispute does not define the result. Include inquiries about time, costs, rates, and format, because the resolution path differs. Draw the sample before reading the outcome so the selection is not biased toward the easy closures. If the population is small, review every inquiry and extend the period.

Stratify the sample by whether the inquiry arrived before or after the due date. A late inquiry may receive a different response because the payment clock is already running. Report the closure rate and the adjustment share for each stratum rather than pooling them. The reader should be able to see whether timing changes the outcome.

Coding the record

Use a short code list that points to a specific repair. Code the outcome as explanation only, credit, write-down, rework, escalation, or still open, and record the inquiry type. Add an unknown category for cases the evidence cannot resolve. Code the number of touches and the owner of each response so the effort is visible.

Have a second reviewer code a sample and compare the results. Resolve disagreements by returning to the client message and the invoice record, not by majority vote. Report the agreement rate and revise any code that is applied inconsistently. If the reviewers cannot agree on what counts as a fee adjustment, stop and fix the definition before continuing.

Measuring the variable

Measure the time from inquiry to first response and from inquiry to closure, using a short log completed during the work. Report the median and the range rather than a single average, because one complex dispute can dominate a mean. Measure the number of touches and the amount of any adjustment separately. Keep the raw entries with the analysis file so a reviewer can check the calculation.

Do not convert the response time to a dollar figure without an approved labor rate and a clear statement that it is an internal estimate. The study measures effort and outcome, not price. If the firm wants a cost view, run it separately with the finance owner. A precise number built on rounded guesses is less useful than a range with a clear source.

Analysis and reporting

Report the overall closure rate, the adjustment share, and the median response time. Show the results by inquiry type and by timing, with the number of inquiries behind each figure. Compare only groups with similar clients and invoice sizes. Include the inquiries that closed without any change 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 client may accept an explanation without saying so, and a missing confirmation is not proof that the inquiry stayed open. Report the completeness of the closure evidence before drawing a conclusion. Small samples, mixed communication channels, and reviewer disagreement can all limit interpretation. An adjustment made outside the billing system may not appear in the record.

Avoid comparing inquiries that differ in complexity or relationship history. A long-standing client may receive a faster explanation than a new client with the same question. Describe the context beside the rate and avoid ranking individual reviewers. The purpose is to improve the response process, not to judge professional worth.

Privacy and retention

Store the client messages, invoices, and adjustment records in a controlled folder with access limited to the study team. Remove client names, amounts, 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 amount. Keep the unredacted evidence separate from the working analysis.

Do not circulate a client-level or reviewer-level list about inquiry outcomes 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 inquiry type. If time narratives dominate, improve the entry standard and the prebill sample. If costs dominate, add a receipt check before the invoice is released. If format questions dominate, fix the invoice template. Test one change on the next invoice cycle before expanding it.

A higher explanation-only share is not the only useful outcome. Faster closure, fewer repeated questions, and a clearer record can improve the relationship even when the adjustment share stays similar. Report the direct result and the service result separately. Stop the change if it shifts the conversation into an informal channel where it cannot be reviewed.

Review cadence

Repeat the study each invoice cycle and after any change to the invoice template, the client contact, or the billing system. Keep the definitions and the unit stable so periods can be compared. Report the inquiries 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 client-facing owner, not only with the responder. Ask which fix is easiest to sustain and which inquiry type creates the most rework. 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.

Authoritative sources

These public references inform the operating questions in this article. They do not replace legal, ethics, privacy, financial, or client-specific advice.

  1. American Bar Association Model Rules of Professional Conduct
  2. Legal Electronic Data Exchange Standard
  3. U.S. Government Accountability Office Green Book
  4. Internal Revenue Service recordkeeping guidance
  5. Federal Trade Commission data security guidance
  6. U.S. Bureau of Labor Statistics

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