Using vendor statements to find unrecorded liabilities

A vendor statement is one of the few outside records that can show a bill the ledger never received. The accounts payable aging report answers what the company thinks it owes. The statement answers what the vendor thinks is outstanding, and the gap between those two views is where unrecorded liabilities and cutoff errors tend to sit. This report asks how a bookkeeping team can use vendor statements to test the completeness of accounts payable for a defined period. The unit is one vendor statement matched to one vendor's ledger activity. The output is a difference list, a disposition for each difference, and a short conclusion about whether the ledger is complete enough for the close.

The scope is the accounts payable subledger and the related expense or inventory accounts for one entity. The method assumes the team can obtain statements for the vendors that matter, and that it can read the ledger detail behind each balance. It does not assume that every vendor sends a statement or that every statement is accurate. The protocol is a bookkeeping control, not an audit. It borrows the completeness principle from audit guidance but does not provide audit assurance. Its purpose is to make a bounded, repeatable test that a reviewer can inspect before the close is signed off.

The ledger can only prove that recorded bills were processed. It cannot prove that every bill the company owes was received, entered, and approved. A missing invoice leaves no row to review, so a reconciliation that starts and ends inside the ledger has no way to detect it. This is why completeness is a different question from accuracy. An accurate ledger can still be incomplete, and a complete ledger can still contain wrong amounts.

The vendor statement provides an external population that may include activity the company has not recorded, which makes it useful for the completeness side of the close. GAO's internal-control standards emphasize documented transactions, assigned responsibility, and records that a reviewer can reconstruct. A completeness test fits that frame because it asks whether the record set is whole, not merely whether each recorded item is correct. The test also creates evidence of the review itself.

COSO's framework treats monitoring as a distinct activity with its own evidence. A monthly statement review is monitoring. It does not fix the payable, and it does not prove that the ledger is complete. It produces a signal that a reviewer can use to decide where to look before the close. The vendor statement reconciliation method is the practical starting point.

Start by defining which vendors need a statement review. Include vendors with a balance, vendors with activity in the period, vendors with recurring services, and vendors that are difficult to reconcile. A useful rule is to cover the vendors that make up most of the payable balance plus any vendor with a known history of late invoices. Set a cutoff frame before reading the statements. Record the period start, the period end, the statement date, and the ledger extraction time.

A statement dated after the ledger extraction can include activity the ledger could not yet have, so the comparison needs to account for that timing. Confirm the statement is complete. Check that it has an opening balance, period activity, and a closing balance, and that the page numbers or file pages are all present. A statement that begins mid-period or omits the closing balance is not a reliable completeness test until the missing part is obtained.

Record the source and date for each statement. If the vendor sends a portal export, save the export and note the report parameters. If the client forwards a PDF, keep the email or message with it. The evidence should show what was reviewed, not only that a review happened.

Build a reconciliation with three parts: opening balance, period activity, and closing balance. Match the statement opening balance to the ledger balance at the prior cutoff, then match each statement line to a ledger bill, payment, credit, or adjustment. End by comparing the statement closing balance to the ledger balance at the current cutoff. Do not reconcile only the closing balance. A closing balance can agree while individual lines are missing and offsetting.

The line-level match is what reveals a missing bill, a duplicate payment, or a credit that was recorded in the wrong period. Use a stable matching key. Invoice number plus amount is usually stronger than date plus amount, because vendors often issue several invoices on the same day. When the invoice number is missing, use the purchase order, the service period, or a combination of amount and description, and mark the match as inferred.

Keep unmatched statement lines and unmatched ledger lines in separate lists. A statement line with no ledger match may be an unrecorded liability. A ledger line with no statement match may be a payment the vendor has not applied, a duplicate, or a timing difference. The two lists need different follow-up.

A difference list becomes useful when every line has a disposition. Use a small set of codes such as unrecorded bill, duplicate ledger entry, duplicate vendor credit, payment not applied, timing difference, disputed amount, and unable to determine. The codes should be defined in the workpaper so two reviewers classify the same fact the same way. For an unrecorded bill, attach the vendor invoice, the receiving or service evidence, and the proposed account. The bookkeeper can prepare the accrual or the bill entry, but the client's accounting owner should approve the amount and the period. A statement line alone is not enough support for a liability.

For a payment not applied, compare the payment date, amount, and reference with the vendor's remittance advice. A payment that left the bank but has not reached the vendor's account is a timing item only if the evidence supports it. Otherwise it may be a lost payment or a misapplied receipt. For a credit, confirm whether it is a true vendor credit, a refund, or a correction of a prior invoice. Do not net a credit against an unrelated bill just to make the statement agree. The credit needs its own ledger entry and its own link to the statement line.

The statement review is also a cutoff test. Look for goods or services received before the period end whose invoice arrived after the cutoff. These are the classic unrecorded liabilities, and they are easy to miss when the team only reviews invoices in the inbox. Compare the receiving log, service completion evidence, or project milestone record with the ledger and the statement. A receipt dated before the cutoff with no bill in the ledger is a candidate accrual. A bill dated after the cutoff for a service performed before it is also a candidate, even if the vendor statement has not yet been issued.

Decide the period treatment with the accounting owner. The bookkeeper can propose an accrual and document the evidence, but the decision to record a liability in a closed or open period belongs to the owner. Record the reasoning so the next close does not reopen the same question. Check the reverse of the same issue as well. An invoice recorded before the service was received may need to be deferred or reversed. The statement can show the vendor's view of the charge, but the company's period treatment depends on when the obligation and the benefit actually arose.

End each statement review with a one-page summary: vendor, statement date, opening balance, period activity, closing balance, ledger balance, total unmatched, and the disposition of every material difference. Add the reviewer, the review date, and the location of the supporting files. State the limitations plainly. The review covers only the vendors selected, and a vendor that sends no statement may still have an unrecorded liability. The statement itself may be incomplete or may include charges the company disputes. The test reduces the chance of a missing liability, but it does not eliminate it.

PCAOB AS 2301 discusses the nature and extent of evidence in response to assessed risks. This protocol borrows the general idea that evidence should be matched to the risk, but it is not an audit and does not provide audit assurance. The bookkeeping team should describe it as a completeness control, not as proof. The GAO's internal-control standards and the month-end close support workflow both depend on the same discipline: a named reviewer, a bounded test, and a record that can be reconstructed. The decision this method supports is a close-readiness decision. If the material differences are explained and the remaining items are owned, the reviewer can proceed with a documented limitation. If they are not, the close should wait for the evidence rather than rely on a statement total that only appears to agree.