Offshore BookkeepersPowered by StealthAgentsPlan my role
Offshore Bookkeepers guide

A vendor statement match queue that survives month end

A practical queue and review routine for vendor statement mismatches, so a bookkeeping team can clear differences without losing the audit trail.

A practical queue and review routine for vendor statement mismatches, so a bookkeeping team can clear differences without losing the audit trail.
Table of contents

The short answer

  • Record the statement, the ledger balance, and the difference on the day the statement arrives.
  • Separate timing differences, missing invoices, duplicate payments, and credits.
  • Give every difference an owner and a resolution date before the close.
  • Close the item with the evidence and the adjustment, not with a note that says 'checked'.

A vendor statement arrives with a balance that does not match the ledger. The difference may be a timing issue, a missing invoice, a duplicate payment, or a credit that was never applied. The bookkeeper opens the statement, finds the gap, and moves on to the next task.

A statement match queue gives the difference a place to live until it is resolved. It records the statement, the ledger balance, the difference, the cause, and the owner. The queue is not a reconciliation workpaper. It is the list of items that need a decision before the books can be trusted.

Record the statement and the ledger

For each statement, record the vendor, the statement date, the statement balance, the ledger balance, and the difference. Add the person who received the statement and the date it arrived.

A difference without the two balances is only a number. The record should let a reviewer see the same gap without reopening the statement.

Classify the difference

Use a short set of causes: timing, missing invoice, duplicate payment, credit not applied, disputed charge, and unknown. The cause tells the owner what to look for and keeps the queue sortable.

Do not leave an item as "unknown" without a note. The note should say what was checked and what is still missing. An unknown item is a question, not a conclusion.

Check the timing first

Many differences are timing. An invoice may be in transit, a payment may not have cleared, or a credit may be posted in the next period. Check the dates before assuming an error.

Record the expected clearing date and the next check. A timing item that does not clear by the expected date becomes an exception.

Assign an owner and a date

Every item needs an owner and a date. The owner may be the bookkeeper, the purchasing team, or the vendor. The date should reflect the close calendar.

An item without an owner is a note. An item with an owner is a task. The queue should make that distinction visible.

Resolve with evidence

Close an item only when the evidence is attached: the invoice, the payment record, the credit memo, or the vendor confirmation. The adjustment should be recorded with the date and the person who approved it.

Do not close an item by changing the number to match. That hides the difference and removes the chance to learn from it.

Review the queue before the close

Before the close, review the open items and the ones that could affect the financial statements. Escalate the material items and document the decision. The review should be short and specific.

Record who reviewed the queue and when. That record shows the control was operated, not only designed.

Review the pattern monthly

Look at the causes by vendor and by month. A vendor with repeated duplicate payments may need a process change. A vendor with repeated credits may need a statement conversation.

The review should produce one or two changes. A new matching rule or a vendor call is enough. Record the change and the date.

Protect the data

Statements contain vendor names, amounts, and bank details. Keep the queue in the approved system and limit access. Do not forward a statement to a broad channel.

Set a retention period with the client's records policy.

Decide whether the vendor or the ledger is wrong

A difference is not automatically a ledger error. The vendor may have missed a credit, applied a payment to the wrong invoice, or billed an item twice. Check both sides before adjusting.

Record the evidence and the conclusion. A vendor error should be raised with the vendor; a ledger error should be corrected with approval.

Keep the queue short

A queue with a hundred items will not be reviewed. Focus on the material differences and the items that affect the close. The rest can wait for the next cycle with a note.

Share the queue with the client

A short monthly summary of the differences and the fixes helps the client see the value of the bookkeeping work. Keep it aggregate and factual. Do not send vendor bank details.

Make the queue easy to audit

Store the statement, the ledger extract, and the resolution note in one folder per vendor. A reviewer should be able to follow the trail without asking the bookkeeper. A short index at the front of the folder is enough, and it should name the reviewer who closed the item.

Key takeaways

  • Record the statement and ledger balances on the day the statement arrives.
  • Classify the difference and check timing before assuming an error.
  • Assign an owner and a date, and close only with evidence.
  • Review the queue before the close and the patterns monthly.

A vendor statement queue is a small control that protects the close. It keeps the differences visible, owned, and resolved, so the ledger and the vendor record can agree with confidence.

For related workflows, see the bank feed exception queue and the accounts payable services overview.

Questions owners ask

What is a statement match queue?

A list of vendor statements whose balance does not match the ledger, with the difference, the cause, the owner, and the resolution.

Should a small difference be written off?

Only under a written policy and with approval. A pattern of small write-offs can hide a recurring error.

How often should the queue be reviewed?

At each statement cycle and before the close. The review should check the age and the cause, not only the count.

Keep planning

Sources

  1. U.S. GAO, Standards for Internal Control in the Federal Government
  2. NIST, SP 800-53 Rev. 5 Update 1
  3. IRS, Recordkeeping