Short-Pay Resolution Event Lag: A Reproducible Billing Study

Published: September 14, 2026.

This study defines an administrative measure for the recorded time between a short-pay trigger and a carrier-defined resolution event. It does not decide whether an invoice was correct, whether a deduction was allowed, whether collection action was appropriate, or why a case took a certain amount of time.

Research question and scope

The question is: for eligible invoice-payment differences, how long elapses from the first qualifying short-pay observation to the registered resolution event? The unit is one invoice-payment pair. Split and combined payments require a predeclared linking rule.

Specify the period, carrier entity, customers, currencies, systems, minimum difference if any, and cutoff before reviewing results. Select invoices and payments independently of whether cases later resolved.

Event and evidence definitions

The trigger should be a documented payment or remittance event with a calculable difference from the linked invoice. Keep the amount, currency, source, and timestamp. Store a stated reason separately and identify who supplied it.

The stop event must be objective and chosen in advance. Examples could include recorded payment receipt, approved adjustment, written finance closure, or another carrier-defined event. Different outcomes can remain separate categories while sharing one interval rule.

Methodology

Freeze the cohort and link invoices to payments under the registered rule. Flag ambiguous, duplicate, split, and combined matches. Do not choose a convenient match merely to make the interval calculable.

Calculate elapsed time only when trigger and stop timestamps pass their evidence tests. Open cases remain open at the cutoff and contribute to aging bands. Missing triggers or uncertain links are reported as not calculable.

Publish eligible, resolved, open, excluded, ambiguous-link, missing-trigger, and missing-stop counts. For calculable resolved cases, report the median and selected distribution bands. For open records, publish current age at cutoff separately. A completed-only average would exclude the cases most likely to be old.

Reproducibility procedure

A second reviewer should reproduce linking, eligibility, event type, and interval for short, middle, long, open, corrected, and ambiguous records. Store disagreements and dated corrections. Keep raw financial records in restricted systems and expose only the minimum needed in the analysis file.

Interpretation boundaries

Recorded lag can reflect missing evidence, customer response, approval sequence, system posting, correction cycles, staffing, or the chosen definition. The study does not establish cause. It should not rank employees or customers without a separate, justified design.

Limitations

Payment posting dates may differ from receipt dates. Remittance details can arrive later or through another channel. Credits and combined payments complicate linking. Results apply only to the registered cohort, systems, rules, and cutoff.

Source treatment

The cited government materials provide broker, records, and retention context. They do not define a resolution clock or endorse the metric. Local event rules and calculations remain clearly labeled.

Conclusion

Short-pay resolution lag can reveal where administrative records remain open when the denominator is complete and the clock is explicit. It is a workflow measure, not a financial, contractual, or performance judgment.

References

1. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-371, retrieved 2026-09-14
2. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-379, retrieved 2026-09-14
3. https://www.archives.gov/records-mgmt/policy, retrieved 2026-09-14