Direct answer

What this role should do

Record the statement date and entity, rebuild the open-item population from the subledger at the same cutoff, match line by line, classify every difference, and close only when each item has an owner and the finance reviewer has accepted the result.

Define the statement and the cutoff

A vendor statement is the supplier's view of what it believes is open, not a ledger of record. Start by recording the statement date, supplier account number, company entity, currency, and the cutoff time used to pull your own open items. If the statement covers a different entity or period, stop and request the correct version instead of forcing a comparison that cannot hold.

Write the purpose in the case: confirm a balance, find missing invoices, recover a credit, or resolve a dispute. The purpose decides which differences matter. A balance confirmation can tolerate small timing items; a dispute review cannot. Keep the supplier file unchanged and store the extracted totals beside it so another person can see exactly what was read.

Rebuild the open-item population

Pull open invoices from the AP subledger as of the same cutoff. Include invoice number, supplier reference, invoice date, posting date, due date, gross amount, tax, currency, payment status, and any credit or prepayment. Record the report name, run time, filters, and row count. A total without its population is not evidence.

Deduplicate the extract before matching. Reversed invoices, cancelled payments, and documents moved to another entity can appear twice under different numbers. Reconcile the row count to the report control total. If those counts disagree, resolve the gap first, because every later match depends on a clean starting list.

Match at the item level, not the total

A matching total can hide two offsetting errors. Match each statement line to one or more open documents using the supplier invoice number first, then amount and date, then purchase order or service period. Record the match basis and a short confidence note. Lines that agree only on amount deserve a second look, because round numbers repeat across suppliers and months.

Keep unmatched items on both sides in the workpaper. The supplier may list an invoice you never received, and you may hold an invoice the supplier omitted. Both are findings. Do not clear a line by writing that it is per statement unless the statement is the agreed source and the owner has accepted that basis in writing.

Explain timing differences with dated evidence

Most differences are timing, but timing still needs proof. For an invoice paid after the statement date, attach the payment date, method, and remittance reference. For goods received but not invoiced, attach the receipt. For an invoice in approval, attach the queue status and the current approver. The explanation should name a date and a document rather than a general impression.

Separate cutoff differences from errors. A payment released on the last day of the month may clear the bank later, which is a settlement timing item. A duplicate invoice is not timing. Classify each line once and let the class drive the follow-up, instead of using one vague note that mixes several causes together.

Handle credits, prepayments, and unapplied cash

Credits are the most common reason a statement will not tie. List every open credit memo, debit memo, rebate, and prepayment with its date, amount, and current application. Check whether the supplier has already applied the credit on its side. A credit applied twice produces a payable that looks smaller than the supplier's records and can hide a real liability.

When a credit is unapplied, do not net it against a disputed invoice without the owner's decision. Record the proposed application and the reason. If the credit belongs to another entity or period, route it to the owner rather than moving it just to make the reconciliation balance.

Route supplier disputes with one question

Some differences are disagreements, not errors. Convert each one into a single answerable question with the document references attached: which invoice is disputed, what amount is accepted, and what evidence the supplier should provide. Send it through the established supplier channel and log the recipient, time, and response due date.

Do not negotiate payment terms or promise a settlement date from the AP support seat. The finance owner sets the position. Your contribution is a precise question and a complete evidence set, so the owner can answer without reopening the whole file.

Keep the reconciliation reproducible

A reviewer should be able to rerun the comparison from the retained files. Keep the statement, subledger extract, match table, exception list, and sign-off in one folder with a version label. Name the preparer and the preparation date. If a later statement supersedes this one, retain the earlier version and mark it replaced.

Record formulas and filters as text, not only as a hidden spreadsheet tab. Software changes and tabs get lost. A short method note that names the source report, cutoff, match order, and tolerance makes the work portable to a backup reviewer or an internal auditor.

Review cadence and sample checks

Reconcile high-value and high-activity suppliers monthly, and the remainder on a schedule the controller approves. Each quarter, sample completed reconciliations: recheck the cutoff, re-perform one match, and confirm that every unmatched line has an owner. Record the sample size and the exceptions found, including clean results.

Track the age of unresolved supplier differences, not only the count. A few old items can carry more risk than many new timing items. Report opening and closing balances of the exception list so a reviewer can see whether work is accumulating or being cleared.

Close with an acceptance record

Close when the agreed balance is supported, every difference has a disposition, and the owner has accepted the result. The record should show statement balance, reconciled balance, total differences by class, and items carried forward with owners and dates.

Acceptance is not the same as supplier agreement. It means the company reviewer has seen the evidence and decided how to treat each item. Keep the supplier response separate from that internal decision so a later reader can tell who concluded what and on which date.

Continue with vendor statement reconciliation support and the AP aging report preparation.

Check the statement reconciliation packet

  • Statement date, entity, account, currency, and cutoff are recorded
  • Subledger extract reconciles to its own row count and control total
  • Every statement line has a match or a documented exception
  • Differences are classified as timing, error, credit, or dispute
  • Open credits and prepayments show their current application
  • Each carried item has one owner and a next review date
  • The reviewer can rerun the match from retained files

Common questions

Accounts payable virtual assistant FAQs

Can an AP specialist settle a disputed statement item?

No. The specialist can assemble documents, calculate the difference, and draft one precise question. The finance owner decides whether to pay, dispute, or write off the item.

How often should supplier statements be reconciled?

High-value and high-activity suppliers usually warrant a monthly cycle; the controller should set the schedule for the rest and record the reason for any exception.

What proves a timing difference?

A dated document that shows the other side of the transaction, such as a bank payment reference, a goods receipt, or an approval queue entry with its timestamp.

Should the supplier statement be edited?

No. Keep the received file unchanged and put extracted totals, notes, and match results in a separate workpaper linked to it.

Factual checks

Sources

These sources support the tax-form, access-control, and phishing guidance in this article. The planning numbers above are labeled examples and do not come from these sources.

  1. SBA: Manage your businessSmall-business finance guidance that supports a documented reconciliation routine; it does not prescribe a matching method.
  2. NARA: Records management policyRecords-management policy used to justify retaining versions and dispositions instead of overwriting the first reconciliation.
  3. NIST SP 800-53 Rev. 5Control catalog context for audit logging, segregation of duties, and evidence retention in the reconciliation workflow.
  4. Nacha: Operating RulesPayment rules context for using a bank payment reference as settlement evidence; company policy still defines the tolerance.

International Labour Organization guidance on remote work arrangements reinforces why remote role briefs should document expectations, communication rhythms, and accountable handoffs.

Contact Us to turn this article into a scoped Philippines-based staffing brief.