Accounts payable

What share of vendor statements are reconciled before payment?

A proposed protocol for measuring whether a vendor statement is reconciled before the payment run.

This research is general operational information, not legal, tax, accounting, employment, benefits, privacy, cybersecurity, insurance, or financial advice.

What share of vendor statements are reconciled before payment? evidence review illustration

Question and scope

This is a proposed research protocol, not a report of completed findings. It asks what share of vendor statements are reconciled before payment. The result would describe the reconciliation record. A short note with four fields is easier to use than a long narrative.

The protocol does not measure whether the vendor was paid correctly. It measures whether the statement was checked before the run. Keep the evidence with the record rather than in a separate log. Update the template when the same question appears twice.

Population and unit of analysis

Define the population as vendor statements received during a stated period. The unit is one statement, with the vendor, the statement date, the reconciliation date, and the payment run recorded. If the source is unclear, route the question instead of guessing. A control that depends on memory is not yet a control.

Link the statement to the payment run so the same statement is not counted twice. A statement that arrived after the run should be marked as late. If the source is unclear, route the question instead of guessing. Record the date and the source so the next reviewer can repeat the check.

Definitions and measures

Define a pre-run reconciliation as a completed reconciliation dated before the payment run. Define completeness as the presence of the matched items and the reviewer. Use the same format for every handover so the next reader can scan it. Keep the boundary visible in the place where the work is assigned.

Report the pre-run rate and the completeness rate separately. A reconciliation done after the run may still be useful but does not prevent the error. Keep the boundary visible in the place where the work is assigned. Name the owner in the same line as the action.

Evidence standard

Use the statement, the reconciliation schedule, and the payment run. A statement without the schedule is weak. The reviewer should be able to see the difference and the resolution. A short note with four fields is easier to use than a long narrative.

Record the date and the reviewer. A later review may need to see who checked the statement. Use the same format for every handover so the next reader can scan it. A control that depends on memory is not yet a control.

Sampling and collection

Use a census of the statements. If sampling is necessary, stratify by vendor size. A sample that excludes the large vendors may miss the biggest risk. Name the owner in the same line as the action.

Pilot the classification on a few statements and compare the reviewers. Clarify how a statement with no activity is treated. If the source is unclear, route the question instead of guessing. Ask whether a new reviewer could act on the record without a conversation.

Analysis and reporting

Report the pre-run and completeness rates by vendor size. Show the statements reconciled after payment. Present the results as a description of the process, not a judgment about the team. Separate what was observed from what was assumed.

Limits and sources of error

The statement may not be received every month. State the coverage. The payment run date may change after the reconciliation, which can change the classification. A short note with four fields is easier to use than a long narrative.

Review cadence

Repeat the review after a process change or at the same interval each quarter. Compare the same vendor sizes. Assign the follow-up to the accounts payable lead and set a date. Test the rule on one real transaction before applying it to the run.

Useful internal handoffs

Sources