Protocol premise

The study would test whether closed disputes stay closed or return because the original resolution did not address the customer's actual claim.

Protocol status and question

This is a proposed research protocol, not a report of completed findings. It asks what share of closed disputes are reopened within a stated window and which closure evidence is associated with a return. The result would help a finance team distinguish a durable resolution from a temporary silence. A later reviewer should be able to see what the study was allowed to conclude. State plainly which decisions the protocol cannot support.

The protocol cannot prove why a customer reopened a dispute. It can describe the pattern and point to the records that need a closer review. The sponsor should define the decision the result might inform, such as a change to the closure checklist. Write the intended use in one sentence so the scope cannot drift. A later reviewer should be able to see what the study was allowed to conclude.

Population and observation unit

Define the population as all disputes closed during a stated window, with the customer, invoice, amount, and closure date recorded. The unit is one dispute, not one customer or one invoice. A dispute that is reopened and closed again remains one case with multiple closure events. A count that cannot be rebuilt is not a population. Keep duplicate and missing records visible in the denominator.

Set the observation window long enough to capture the typical reopening period. If most reopenings happen within thirty days, a seven-day window will miss them. Record the reason for any dispute that leaves the population, such as a write-off or a legal referral. Name the system that produced the frame and the export time. Keep duplicate and missing records visible in the denominator.

Definitions and measures

Define a dispute as a customer claim that changes the amount or timing of payment and requires a finance decision. Define closure as a recorded resolution with an owner, a date, and the evidence used. Define reopening as a new claim on the same invoice after closure, regardless of whether the amount changed. Give one example and one counterexample for every measure. Put the denominator and window beside every rate.

Report the reopening rate overall and by closure type. A closure based on a customer promise may behave differently from one based on a credit memo or a corrected invoice. Include the time to reopening and the reason given by the customer. The reason is descriptive, not proof of cause. Give one example and one counterexample for every measure.

Evidence standard

Link each closure to the resolution record, the approval, and the communication sent to the customer. A closure that exists only as a status change is weakly evidenced. A reopening should link to the new claim and the earlier closure so the reviewer can compare them. A summary without the source is not evidence. Use stable references rather than personal folder names.

Where the customer's reason is ambiguous, record the exact words and the reviewer's interpretation separately. Do not convert a vague complaint into a specific cause. The study should preserve that uncertainty because it affects what the closure checklist can promise. Keep the original record even when a later correction is added. Link each classification to a document a second reviewer can open.

Sampling and collection

Use all closed disputes in the window if the volume allows. If sampling is necessary, stratify by closure type, amount, and owner so the common paths are represented. Select cases before checking whether they were reopened to avoid bias toward interesting failures. Record the first classification before discussion. State the final sample size and how it was reached.

Pilot the classification on ten cases and compare reviewers. Clarify whether a partial payment after closure counts as a reopening or a new payment event. Record the decision rule and apply it consistently. Select the sample before reviewing outcomes. Keep the sampling rule with the data file.

Analysis and reporting

Report the reopening rate with the denominator and the observation window. Break the result down by closure type and by the evidence attached at closure. Show the number of cases that were reopened more than once, because a repeated case may indicate a different problem from a single return. Name the counterexamples as well as the main pattern. Show the distribution, not only the average.

Present the findings as a description of closure durability, not as a judgment about individual analysts. A high reopening rate may reflect a customer behavior, a billing error, or an unclear closure rule. The report should name the possible causes and the records needed to test them. Show the distribution, not only the average. Write the limitation beside the finding it affects.

Limits and sources of error

The study may miss reopenings that arrive through a different channel or a different invoice. It may also count a customer's follow-up question as a reopening when no amount changed. The definition should be narrow enough to be meaningful and broad enough to capture the real work. Say what a second study would need to test. Keep the limitation in the same sentence as the claim it qualifies.

A policy change during the window can alter both closure behavior and reopening rates. Record the change and consider splitting the window. The report should state what it cannot see, including disputes resolved outside the recorded system. Name the records the study could not see. Say what a second study would need to test.

Review cadence

Repeat the review after a closure checklist change and at the same interval each year. Compare the same closure types and the same observation window. A lower reopening rate is useful only if the closures still resolve the customer's claim. Set the next review date before the current one ends. Record the decision the review is expected to inform.

Assign the follow-up to the owner of the dispute process and set a date. The protocol should end with a specific question about which evidence should be required before a dispute can be closed. Set the next review date before the current one ends. Store the data and the protocol together for the next pass. Close the review with one question for the process owner.

Sources

  1. U.S. Government Accountability Office, Standards for Internal Control
  2. Consumer Financial Protection Bureau
  3. Financial Accounting Standards Board
Do dunning replies stop the next collection step?How often do agency referrals lack a dated approval?

Put the protocol into operational context.

Discuss the queue, evidence, ownership, and safeguards that apply to your workflow.

Discuss your workflow