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 billing questions arrive after the invoice due date. The unit is a question event, defined as a client communication that requires a billing response before the invoice can be considered resolved. The purpose is to understand whether the firm is inviting questions early enough or learning about problems only when payment is late. The result describes timing, not the merits of any question.
Scope the study to invoices issued in a defined period and to questions received through the agreed client channels. Include email, portal messages, calls logged by the billing team, and formal dispute notices. Exclude internal questions from partners and routine payment confirmations. State the period, the clients, and the channels included so the result is comparable.
Defining a billing question
A billing question is a client request for explanation, correction, or supporting detail about an invoice or a charge. A payment confirmation is not a question, and a simple acknowledgement is not a question. A dispute is a question with a stated disagreement, and it should be coded separately. The definition should require a response from the billing team, not just a read receipt.
Distinguish a question about the invoice from a question about the matter or the legal work. A client may ask why a case took a certain course, which belongs to the relationship owner rather than the billing queue. Record the subject so the analysis does not mix billing process issues with legal service issues. The billing team can still coordinate the response without owning the substance.
Population and denominator
The population is every invoice issued in the period that reached the client through an active channel. Exclude invoices that were never sent, were cancelled before delivery, or were replaced by a credit memo before the client saw them. Report the number of invoices and the number of questions so the reader can see the base. A question rate without a denominator is not interpretable.
Use the invoice due date as the reference point and calculate the days between delivery, question, and due date. A question that arrives on the due date should be coded consistently, either as on-time or post-due, according to a written rule. Record the time zone used for the timestamps. Small timing choices can change the result when many questions arrive near the deadline.
Data sources
Use the billing system for invoice delivery and due dates, the shared inbox for question timestamps, and the portal for client messages. Reconcile the sources so the same question is not counted twice. If a question arrives by phone, record the call time and the person who took it. A missing timestamp should be marked, not guessed.
Link each question to the invoice and the client account. That link allows the analysis to separate questions about a specific charge from questions about the account or the payment process. Record the question type and the final resolution where available. The evidence should let a second analyst reproduce the count.
Sampling
If the invoice volume is large, sample by client, invoice amount, and delivery month. Include invoices with no questions so the denominator reflects the full population. Draw the sample before reviewing the question timing to avoid selecting only late disputes. Report the sampling method and the number of invoices drawn from each stratum.
For a smaller firm, review every invoice in the period and every logged question. Extend the period rather than lowering the evidence standard if the volume is too small. Track questions that arrive after the study window and report them separately. Dropping late-arriving questions would bias the result toward the early side.
Timing analysis
Report the share of questions arriving before the due date, on the due date, and after the due date. Add the median number of days after delivery and the median days before or after the due date. A single share hides whether late questions arrive one day late or several weeks late. The distribution is more useful than the average.
Break the timing down by question type. A rate question may arrive early because the client reviews the invoice immediately, while a narrative dispute may arrive late after an internal audit. Compare the pattern across clients only when the delivery method and payment terms are similar. Note any client-specific review cycle that explains the difference.
Coding question types
Use codes such as rate, narrative, staffing, expense, duplicate charge, budget, payment terms, and other. Define each code with an example and require a short note for the other category. A question can have more than one code, so name the primary code and list secondary codes. The coding should point to the invoice field or process that needs attention.
Have a second reviewer code a sample and compare the results. Resolve disagreements by returning to the client message and the invoice. If a code is used inconsistently, revise the definition before continuing. The code list should be short enough to remember and specific enough to guide a fix.
Reporting
Report the overall share, the distribution by timing, and the breakdown by question type and client. Include the number of invoices and questions behind each rate. Show the share of questions that required a credit or write-down, because a late question with no financial effect is different from one that changes the invoice. The report should separate frequency from consequence.
Present the results to the billing manager and the relationship owners with a short note on what the timing suggests. If most questions arrive after the due date, the issue may be invoice clarity, delivery timing, or the client's review process. The report should propose one test, not a general conclusion. Keep the raw data available for a follow-up review.
Limits and sources of error
Clients may ask questions through channels the firm does not capture, such as a direct call to a partner. Those questions can be missing from the study and make the late share look lower. Ask the relationship owners whether they received billing questions outside the tracked channels. Report the estimated gap rather than assuming the record is complete.
Payment terms and invoice delivery dates vary by client, so a raw comparison can be misleading. Report the terms beside the timing result and avoid ranking clients on late questions alone. The study measures when questions arrive, not whether the client is difficult. Keep the limitations beside the conclusion.
Privacy and retention
Store the question log and the invoice links in a controlled billing folder. Remove client names and matter details from the analysis file when they are not needed. If an example is shared for training, redact the client and the amounts. Follow the firm's records policy for the retention period.
Limit access to the study team and the billing manager. Do not circulate a client-level list outside the group that needs it for service improvement. Aggregate the results before sharing them more broadly. The same privacy rule applies to any screenshots of portal messages.
Applying the result
If many questions concern narratives, test a clearer invoice summary or a short pre-submission note that explains the narrative standard. If rate questions dominate, review the rate display and the client's rate history. If questions arrive late because the client reviews internally, ask whether an earlier draft or a summary call would help. The fix should match the question type and the timing.
Test one change on a defined client group and compare the timing distribution with the baseline. A shift from post-due to pre-due questions is a service improvement even if the total number stays the same. Record the result and the next review date. The study should improve the conversation around invoices, not just measure it.
Review cadence
Repeat the study quarterly for the first year after an invoice format or delivery change, then twice a year. Keep the question definition and the due-date rule stable so the timing comparison is valid. If a client changes payment terms, report that client separately rather than blending it into the total. A stable method is what makes a trend trustworthy.
Review the results with the billing manager and the relationship owners for the clients in the sample. Ask which questions could have been prevented by a clearer invoice or an earlier conversation. Choose one client group for a test and set a follow-up date. The review should connect the timing data to a specific service change.
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


