Choose the cadence from the statement cycle

A supplier statement reconciliation should follow the supplier's statement cycle. A monthly statement needs a monthly check, while a weekly statement may need a weekly review. Record the cycle and the statement date for each supplier. A single company-wide cadence will miss the suppliers that matter most.

Set the cadence from the risk and the volume, not only from the calendar. A high-value supplier with frequent credits may need a mid-month check. A low-volume supplier may be fine at month end. Write the reason beside each schedule.

Schedule the check before the payment run, not after it. A reconciliation that happens after payment can only record a loss. Put the deadline on the accounts calendar. The payment owner should see the result before releasing funds.

Review the cadence when a supplier changes terms or a new account is opened. Record the effective date and the new statement channel. Tell the desk which supplier moved. An unreviewed cadence drifts away from the actual risk.

Match the statement to the ledger, not the inbox

Reconcile the supplier's statement to the accounting ledger, not to the email that carried it. The ledger is the record the business will pay from. The statement is the supplier's claim about that record. Comparing two emails proves nothing.

Start with the closing balance on both sides and work back through the open items. Match invoices, credits, and payments by reference and amount. Do not match on amount alone when two invoices share a value. A false match hides a real difference.

Record the statement date, the ledger date, and the cut-off used. A supplier may include an invoice the ledger has not yet received. That is a timing difference, not an error. Label it clearly so the next cycle does not re-investigate it.

Keep the statement file with the reconciliation, not in a personal folder. Name the file with the supplier and the period. A reviewer should find the evidence from the ledger entry. A reconciliation without the source statement cannot be checked.

Record every difference with a reason code

Every unmatched line needs a reason code and an owner. Common codes include missing invoice, duplicate payment, price difference, credit not applied, and timing. A line marked query without a code cannot be grouped or fixed. The code turns a list into a pattern.

Record the amount of each difference and the age in days. A small difference that has been open for months is a bigger risk than a large one found yesterday. Sort the report by age as well as value. The oldest items should get attention first.

Separate a supplier error from an internal error. A missing credit note is usually a supplier issue, while an unposted invoice is usually internal. The owner and the fix differ. Reporting both as reconciliation differences hides where the work belongs.

Do not adjust the ledger to make the statement match without evidence. An adjustment without a source document creates a false record. Route the correction through the normal journal process. The reconciliation should prove the fix, not invent it.

Route a disputed line to one owner

A disputed line should have one owner at a time, not a shared queue. The owner may be the buyer, the accounts specialist, or the supplier contact. Record the name and the date the dispute was raised. Shared ownership is how a dispute ages without action.

Send the supplier a specific question with the supporting documents. A vague request for clarification produces a vague answer. Name the invoice, the amount, and the difference. Ask for the document that would resolve it.

Set a follow-up date that matches the payment terms. A dispute that sits past the due date may become a late payment even when the supplier is wrong. Record the next action and the deadline. The payment owner should know the line is disputed before the run.

Close the dispute only when the ledger and the statement agree or the difference is written off with approval. Record the approval reference and the reason. A write-off without approval is an unexplained loss. The audit trail should show who decided and why.

Review open differences before the next cycle

Review open differences before the next statement arrives. Group them by supplier, reason code, and age. A supplier with repeated price differences may need a contract review. A cluster of missing invoices may need a receiving process fix.

Measure how many differences were cleared within one cycle. A high clearance rate shows the process works, while a low rate shows the desk is accumulating work. Report the count and the value. Both numbers matter to the client.

Check that the same difference is not reopened every month. A recurring line may need a standing correction or a contract change. Record the decision and the owner. Repeated investigation is a hidden cost.

Give the client a short summary with the open value, the aged items, and one process change. Name the supplier and the action. Record the effective date and compare the next cycle. The reconciliation should reduce future differences, not only report them.

For the next step, compare this workflow with Design a supplier onboarding packet for a Philippines operations desk and Run a weekly backlog aging review for a delegated queue. For access and oversight, use the authoritative planning reference alongside your own policy.