Research question and scope
This protocol measures how often a supplier statement clears without a recorded reconciliation. The unit is one supplier statement for one period. A cleared statement has no recorded match, difference list, or owner sign-off. The measure describes the accounts control, not the supplier's accuracy.
Set the scope to one accounts desk, one ledger, and a fixed period. Record the statement cycle and the reconciliation rule in force. If the rule changes during the period, split the sample at the effective date. A different rule creates a different denominator.
Keep the measure separate from a duplicate-payment count. A statement can be reconciled correctly and a duplicate can still slip through the payment run. The purpose is to test the statement control. Report payment exceptions separately.
Population and unit of analysis
Define the population as every supplier statement received during the period. Include statements with a zero balance and statements with only credits. The unit is the statement, not each invoice line. A supplier that sends one statement per site is several units when the sites are separate accounts.
Include statements received by email, portal, and post, and mark the channel. Exclude a duplicate statement for the same supplier and period. Report the excluded count. A rate built only from statements that were reconciled will overstate control.
Exclude an internal ledger report that was never compared with a supplier document. The measure is about the supplier's claim. State the exclusion rule before sampling so the boundary is visible. Record the rule in the report so a second reviewer can apply it.
Definitions that make the measure reproducible
Define a recorded reconciliation as a statement date, a ledger date, a matched closing balance or an itemized difference list with reason codes, and a reviewer name. Define a partial reconciliation as one missing element. Define a missing reconciliation as no record at all. Publish one example of each.
Define the payment run date as the date the payment file is released, not the date the invoice is due. A reconciliation completed after the run does not protect that payment. Record the run date with the review date. The gap between them is part of the result.
Decide how to treat a statement that arrives after the payment run. Count it as late and report it separately from a missing reconciliation. A late statement is a timing problem, while a missing record is a control problem. The two need different fixes.
Sampling and data collection
Draw the sample from the statement inbox, the supplier portal, and the ledger for the full period. Record the export date, the filters, and the row count. Do not build the sample from disputed suppliers alone. A disputed-only sample cannot show the routine statements.
Capture the supplier, the statement period, the statement date, the ledger date, the closing balance, the matched amount, the difference count, the reason codes, the reviewer, and the payment run date. Store the statement file with the report. The matched balance and the reviewer field are the core evidence. A missing field makes the statement count as partial.
Check a small overlap sample with a second reviewer. If the reviewers disagree about whether a difference list is complete, the definition is too vague. Rewrite the rule and retest before the full sample. Agreement matters more than sample size.
Record the time spent matching statements to ledger accounts. A report that requires opening every statement will not be repeated. Note the suppliers that send a different format each month. The collection cost belongs beside the result.
Measuring unreconciled statements
Report the share of statements reconciled before the payment run, after the run, and not at all. Show the counts behind each share. The three groups describe different levels of control and should not be collapsed. A single reconciliation rate hides the statement that was checked too late.
Break the result down by supplier value, statement cycle, and desk shift. A high-value supplier may receive more attention than a small one, which is expected. A weekly statement may be more likely to be missed than a monthly one. Compare only groups with similar volume and cycle.
Report the share of statements with open differences and the age of the oldest item. A statement can be reconciled and still carry an unresolved line. Include the reason code and the owner. The open value belongs beside the clearance count.
Report the share of payment runs that included a supplier with an unreconciled statement. This links the control to the money. A high share shows the payment gate is not using the reconciliation result. Include the run date and the amount released.
Limitations and next action
The measure cannot show whether a supplier statement was accurate or whether a payment was correct. It also cannot show a reconciliation performed in a spreadsheet that was never saved. Treat the result as a measure of the recorded control. Note the suppliers and formats that were not included.
Give the result to the accounts owner and the payment owner with one change to test. The change might be a required statement field, a payment-run gate, or a weekly cadence for high-value suppliers. Record the effective date and repeat the measure with the same definitions. A controlled change is easier to judge.
Review the boundary cases before changing the whole cadence. A few suppliers with a quarterly statement may explain a large share of late checks. Fix the schedule first if that is the pattern. The goal is a reconciled statement before payment, not a lower number by definition.
