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 long a client's invoice follow-up promise stays open before it is resolved, renewed, or escalated. The promise may be a commitment to pay, to review a charge, or to route the invoice to another approver. The measure is not the invoice age, because an old invoice can have a recent commitment. The question is about the promise cycle and the action that follows it.
Name the client group, the invoice population, the period, and the channels included in the review. A promise made in a phone call and a promise made in a portal comment may be recorded differently. State whether the measurement includes all open promises or only those past a threshold. The scope should also define what counts as a resolution for the purpose of the study.
Unit of analysis
Use one promise event as the unit, from the date the client makes the commitment to the date it is resolved, renewed, or escalated. If the client makes several promises on the same invoice, keep each event separate and link them to the invoice. A renewed promise starts a new cycle but should not erase the earlier cycle from the record. This structure shows whether the relationship is moving or repeating.
Record the invoice, the client contact, the channel, the promised action, and the promised date. If the promise has no date, record that absence explicitly rather than inventing one. An undated promise is a finding in itself because it cannot be aged or escalated. The unit should be observable from the log without asking the original owner to reconstruct it.
Defining a promise and a resolution
A promise is a statement by an authorized client contact about a future action on the invoice. A request for information is not a promise, and neither is a courtesy acknowledgment with no commitment. A resolution is the event that closes the promise, such as payment received, a credit approved, a dispute routed to a formal process, or a new promise with a defined date. Write these definitions into the protocol before counting.
Distinguish a resolved promise from a closed invoice. The invoice may remain open because of a partial payment or a separate dispute, even when the promise was fulfilled. Conversely, an invoice can be closed administratively while the underlying question remains unresolved. The measure should follow the promise, not the invoice status alone. This prevents a clean invoice report from hiding an open commitment.
Evidence standard
Every promise should have a dated record of what the client said and who said it. A summary written weeks later is weaker evidence than a contemporaneous note. If the promise was made by phone, record the call date and the person reached. If it was made in a portal, keep the message reference. The evidence should let a reviewer confirm the commitment without contacting the client again.
Record missing or unclear evidence as its own state. A note that says the client will pay soon is not a dated promise and should not be treated as one. If the contact is not authorized to make the commitment, mark the promise as unverified and route it to the relationship owner. Collapsing these states would make the follow-up process look more controlled than it is.
Sampling and collection
Collect promises from consecutive invoices and include both resolved and unresolved events. A sample of only closed promises will understate the time open and hide the items that never resolved. If the population is large, stratify by client, aging bucket, and channel. Include promises with no date and promises with multiple renewals so the tail of the distribution is visible.
Record the collection window and the criteria used to identify a promise in the log. If the team changed its logging practice during the window, split the data at the change date. A new field or a new reminder process can change both the number of promises recorded and their apparent age. The report should make that change visible rather than blending the periods.
Measuring time open
Calculate the time from the promise date to the resolution date for closed events and from the promise date to the observation date for open events. Report the median, the range, and the number of events that exceeded the promised date. A median that ignores open events can make the process look faster than it is. Show the open count beside the closed count so the reader sees both.
Separate a missed promise date from a renewed promise. A renewed promise may be a legitimate extension or a sign that the original commitment was not serious. Record the reason for the renewal when it is known. The distinction helps the owner decide whether the issue is client communication, internal follow-up, or the original due date.
Analysis and reporting
Report the promise count, the resolved count, the open count, the median days open, and the share past the promised date. Break the result down by channel and client group where the numbers allow. Avoid a single average that mixes a one-week promise with a one-quarter promise. A small table with counts and medians is more useful than a precise-looking ratio.
State the action implied by the result. A cluster of promises past their date may call for a reminder rule or a different contact route. A cluster of undated promises may call for a logging standard. A cluster of renewals may call for a conversation about the client's approval process. Give the owner a specific decision rather than a general warning about aging.
Limits and sources of error
The log may omit promises made outside the recorded channels, and the client contact may not be authorized to commit. A promise can also be recorded differently by different team members, especially when the client is vague. Small samples produce unstable medians, and a single large account can dominate the result. The report should state these limits.
The cited public sources frame recordkeeping, privacy, and internal control practice; they do not provide a promise age for the firm. The protocol measures the observed log, not the client's intent or the firm's collection performance. Use the result to improve the follow-up process and the record, not to judge a client relationship. A cautious reading protects both the analysis and the relationship.
Coordinating with the billing team
Share the promise aging summary with the billing manager and the relationship owner at the same weekly review. A promise that is old may need a relationship conversation rather than another reminder. A promise that is repeatedly renewed may need a different contact or a formal dispute path. The follow-up owner should not have to decide those questions alone.
Separate delays caused by the client from delays caused by the firm. A client waiting for a corrected invoice is not the same as a client ignoring a valid one. Record the responsible party in the log so the aging report does not blame the wrong side. This distinction also helps the team choose the right next action.
Testing a reminder rule
Pilot a reminder at the promised date for one client group and compare the missed-date share with a similar group. Keep the reminder professional and specific to the commitment the client made. If the reminder produces more renewals without more resolutions, the issue may be the client's approval process rather than the firm's follow-up. Adjust the rule based on the result.
Review the pilot with the billing manager before expanding it. Ask whether the reminder improved communication or damaged the relationship. A rule that works for one client may be inappropriate for another, especially where the balance is sensitive. Document the test, the result, and the decision to continue or stop. Keep the client's preferred channel in the rule so the reminder does not create a new complaint.
Review cadence
Review the result monthly while the follow-up process is being changed, then quarterly once the measure is stable. Re-run the protocol after a logging change or a new client portal, because the recorded promise population may shift. Set a review date and name the billing manager who will act on it. A measure that is not reviewed will not change the queue.
Choose one improvement, such as requiring a date for every promise or adding a reminder at the promised date. Test whether the open count and the missed-date share move in the next period. Keep the definitions, the sample, and the open questions together so the next reviewer can repeat the method. The goal is a follow-up process that keeps its commitments visible.
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


