What it means
A customer may ask why an invoice includes a fee, or a supplier may ask why a payment is short, and slow answers can delay payment, raise collection costs and damage trust. The team needs the invoice, contract, order and delivery evidence in one place so the right person can answer without repeated handoffs.
A timestamp alone does not show whether the reply helped, so keep the actual message or ticket note and sample replies for a clear answer, evidence and an honest next step. A named owner who cannot see the supporting contract may still need to hand the case to someone else.
Define the clock and service target: start when the query reaches the designated channel, identify business hours or calendar time, and treat a first useful response as one that names an owner, explains what is being checked or answers the question. A final resolution may require a corrected invoice, credit note or evidence that the original bill is right, so measure both stages and open-query age.
Agree on when the clock stops for a genuine first response and when the resolution clock stops. If a customer sends missing documents later, show any paused period separately rather than silently deleting it, and reopened tickets should retain their earlier history so the team cannot manufacture a fast result by closing and recreating cases.
Classify reasons such as wrong price, missing purchase order, tax detail, quantity, duplicate bill or unclear service, and remember that a quick reply saying "we are looking into it" every day should not count as repeated resolution. Escalate high-value disputes and due-date risks, and if only part of an invoice is disputed, clarify how the undisputed amount should be handled under the agreement.
Segment the results by query type, priority and channel before comparing teams, since a simple request for a copy of an invoice is not the same as a contract interpretation dispute. Report the share answered within a promised window as well as the median, with both measures showing how many queries remain open.
Review whether internal process causes delay, as frequent missing delivery evidence or incorrect master data may be fixed upstream. Compare response time with accuracy and customer satisfaction, because a rushed incorrect answer can extend the dispute.
For owners, this metric protects cash conversion without making customers pay unsupported amounts merely to keep an account current.
In practice
Real-world examples.
Example
A buyer asks about a freight surcharge Monday at 10:00; the seller provides the rate schedule Tuesday at 10:00, a 24-hour useful response.
Example
Support sends an automatic receipt instantly, but the query remains unresolved for a week; report those two times separately.
Example
Finance issues a corrected credit note after finding a duplicate line, and marks the query resolved when the customer receives it.
Formula
Calculation
Median first useful response time = Middle elapsed response time after sorting all eligible invoice queries by time to first substantive reply
Worked example. Five fictional queries receive useful replies after 2, 4, 5, 12 and 30 hours.
- Sorted times are 2, 4, 5, 12 and 30.
- The median is 5 hours, while the 30-hour case still needs attention.
- The average is (2 + 4 + 5 + 12 + 30) / 5 = 53 / 5 = 10.6 hours, which the single slow case pulls upwards.
Share answered within a promised 8-hour window = 3 of 5 = 60%. Also track unanswered queries and time to final resolution.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Hillcrest Services, an invented facilities provider. Its dashboard showed a five-minute invoice response time because auto-replies counted as answers. Customers still waited days for explanations of overtime charges and withheld payment. Hillcrest defined a substantive reply and linked billing tickets to signed work records. Billing agents could answer standard queries directly, while contract exceptions moved to an owner with a deadline.
The dashboard now shows first useful response, final resolution and open value. The reported time initially rose, but the number described real service and helped the company address delayed cash. In a fictional monthly review, Hillcrest sees ten unresolved queries awaiting signed work records. The billing lead asks operations for the records before promising a credit or demanding full payment. The oldest ticket stays visible in the ageing report despite its quick first reply.
The team also samples the words in replies. A message naming the disputed line and attaching the signed record is useful; another automatic receipt notice is not. This quality check guards against a target that rewards speed over a correct answer.
Watch out
Common mistakes.
- Counting an automatic acknowledgement as a substantive answer.
- Reporting only closed queries and hiding unanswered ones.
- Optimising speed while sending unsupported or incorrect explanations.
Questions
People also ask.
Should we measure first reply or final resolution?
Both, with clear labels. They answer different management questions. Use the first useful response to assess access and ownership, and the final resolution time to identify work that remains blocked.
Do weekends count?
Set and publish the clock rule that matches the promised service coverage.
What if the invoice is partly disputed?
Clarify the supported amount and process under the actual agreement.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%