What Is a Vendor Statement? The Complete AP Guide

A vendor statement is a supplier-issued document that summarizes all transactions between a vendor and buyer over a defined period, listing invoices, payments received, credits applied, and the outstanding balance. AP teams rely on vendor statements to reconcile their own records against the supplier's ledger and catch discrepancies like missing invoices or unapplied payments.

---

Vendor Statement Definition and Purpose

A vendor statement is a periodic summary document issued by a supplier to a buyer that lists every transaction between the two parties over a defined period, typically one calendar month. It captures invoices raised, payments received, credit notes applied, and any adjustments, then presents the outstanding balance the supplier believes the buyer owes. You may also see this document called a supplier statement, an account statement, or a statement of account. These terms are interchangeable and all refer to the same document.

The primary purpose of a vendor statement is straightforward: it gives your AP team a supplier-side record of the account so you can verify that your own books match. When a supplier sends you a statement showing three unpaid invoices totaling $14,200 and your ledger shows the same three invoices at the same amounts, you have confirmation that both sides agree. When the numbers differ, you have a starting point for investigation.

A note on terminology: If you arrived here searching for "vendor statement" and expected information about property transactions, you may be thinking of the Section 32 vendor's statement used in Australian property law. That is a completely different document, a legal disclosure required during property sales in certain Australian states. This guide covers vendor statements exclusively in the accounts payable and accounting context.

What makes this document distinct from other AP paperwork is its role as an external control document. An invoice requests payment for a single transaction. A vendor statement, by contrast, aggregates all transactions over a period and presents the supplier's view of the entire account balance. It is not a payment request. It is a reconciliation tool, a mirror held up to your own records so you can confirm accuracy or catch errors before they compound.

---

What Does a Vendor Statement Contain?

Vendor statements vary in format from one supplier to the next, but most contain a standard set of data fields. If you want a breakdown of open item and balance forward statement formats, those are the two main layouts AP teams usually encounter. Here is a field-by-field breakdown of what a typical vendor statement shows. If you need to convert a vendor statement into Excel before reviewing balances, this same field list becomes the backbone of a usable spreadsheet.

Statement date and statement period. The statement date is the date the supplier generated the document. The statement period defines the date range the statement covers, for example 1 March to 31 March. Together, these two fields establish the time window for every transaction listed below them.

Supplier details. This block identifies the vendor issuing the statement. It typically includes the company name, registered address, phone number or email contact, and tax identification number (such as an EIN or VAT number). These details allow the buyer to confirm the statement came from a legitimate, known supplier.

Customer details. The buyer's information appears near the top as well. Expect to see the buyer's company name, the account number the supplier has assigned to the buyer, and the billing address on file. The account number is particularly important because it ties the statement to the correct ledger on the supplier's side.

Opening balance. This is the amount outstanding at the start of the statement period, carried forward from the previous statement. It represents every unpaid invoice, unapplied credit, and unresolved adjustment that existed before the current period began. If the opening balance does not match what the buyer's records show as owed to that supplier at period start, a discrepancy exists that needs investigation.

Transaction lines. The transaction section is the core of the document. It lists every financial event between the buyer and supplier during the statement period. Each line typically includes one of the following:

• Invoice numbers, invoice dates, and invoice amounts for goods or services billed during the period
• Payment references and payment amounts for remittances the supplier received and applied
• Credit note numbers and credit amounts for returns, pricing corrections, or other reductions
• Debit note or adjustment entries for any other modifications to the account balance

Transaction lines are usually listed in chronological order, giving a running account of activity from the first day of the statement period to the last.

Closing balance. The closing balance is the total amount outstanding at the end of the statement period. It is a calculated figure, not an arbitrary number. The supplier arrives at it using a straightforward formula:

Opening Balance + Invoices Issued - Payments Received - Credits Applied = Closing Balance

This formula makes the document's logic concrete. If the buyer independently calculates the same closing balance using their own records, the two accounts are in agreement. If the figures diverge, the transaction lines provide the audit trail needed to find the source of the difference.

Aging breakdown. Many vendor statements include an aging summary that categorizes the outstanding balance by how long each portion has been unpaid. A typical aging breakdown groups amounts into buckets: current (not yet due), 1 to 30 days overdue, 31 to 60 days overdue, 61 to 90 days overdue, and 90+ days overdue. This breakdown gives both parties immediate visibility into payment health without requiring a separate aging report.

Payment terms and remittance instructions. The final section specifies where and how to send payment. This may include bank account details for wire transfers, a mailing address for checks, accepted payment methods, and the agreed payment terms (such as Net 30 or Net 60). Having remittance instructions on the statement itself reduces back-and-forth when AP teams are ready to pay.

---

How a Vendor Statement Differs from an Invoice, Purchase Order, and Credit Note

Vendor statements are often confused with invoices, but the two documents serve fundamentally different purposes. An invoice requests payment for a single transaction. A vendor statement summarizes an entire account relationship over a defined period, capturing every invoice, payment, credit, and adjustment in one view.

The following table breaks down how vendor statements compare to the other core documents AP teams handle daily.

Document Type	Issued By	Purpose	Frequency	Key Content
Vendor statement	Supplier	Summarizes account activity and outstanding balance over a period	Monthly or on request	All invoices, payments, credits, adjustments, and running balance
Invoice	Supplier	Requests payment for a specific transaction	Per transaction	Line items, amounts, payment terms, and due date for one sale
Purchase order	Buyer	Authorizes a purchase before goods or services are delivered	Per order	Ordered items, quantities, agreed prices, and delivery terms
Credit note	Supplier	Reduces the amount owed due to returns, errors, or pricing adjustments	As needed	Original invoice reference, credit amount, and reason for the credit
Remittance advice	Buyer	Confirms that payment has been sent	Per payment	Payment amount, invoice references covered by the payment, and payment method

For a deeper look at invoice anatomy, see what invoices contain and how they work, or explore the different types of invoices in accounting. The buyer's side of the transaction starts with a purchase order, while remittance advice confirms what was paid. All of these documents appear as line items on the vendor statement, which is why it functions as the master reconciliation document for the account.

---

When and Why Suppliers Send Vendor Statements

Suppliers typically send vendor statements on a regular monthly cycle as standard AR housekeeping, when an account carries overdue balances (30, 60, or 90+ days past due), during quarter-end or year-end account reviews, to support a payment dispute with documentary evidence, or on request from the buyer's AP team during reconciliation or audit preparation.

Note that a vendor statement is distinct from an internally generated accounts payable aging report. The aging report is buyer-generated from your own ledger; the vendor statement is supplier-generated from their receivables records. Comparing the two is a core part of reconciliation.

---

How AP Teams Use Vendor Statements for Reconciliation

Reconciling a vendor statement means comparing the supplier's record of account activity against the buyer's own accounts payable records for the same period. The goal is to confirm that both parties agree on what has been invoiced, paid, and credited, and to surface any differences before they affect financial reporting or cash flow.

The standard reconciliation workflow follows a consistent sequence that AP teams repeat for each supplier on a regular cycle.

1. Obtain the vendor statement. Some suppliers send statements automatically at the end of each month or quarter. For suppliers that do not, request one directly. The statement should cover the same period you plan to reconcile.

2. Pull the corresponding AP records. From your accounting system, generate a supplier ledger report for the same vendor and the same date range. This report should list all recorded invoices, credit notes, and payments.

3. Compare the closing balance. Check the ending balance on the vendor statement against the AP ledger balance for that supplier. If the two figures match, the reconciliation is complete for that period, and no further investigation is needed.

4. If balances differ, perform a line-by-line comparison. Match each transaction on the vendor statement against the corresponding entry in your AP ledger. For every invoice, payment, and credit note, verify that the invoice number, date, and amount align between both records.

5. Identify discrepancies. Flag any transaction that appears on one record but not the other, or where the recorded amount differs. Common examples include invoices the supplier has issued but your team has not yet received, payments you have made that the supplier has not yet applied, or credits that only appear on one side of the ledger.

6. Investigate and resolve each discrepancy. Determine whether the difference stems from a timing issue, a data entry error, a missing document, or a genuine dispute. The next section covers the most frequent discrepancy types along with specific resolution steps for each.

7. Document the reconciliation outcome. Record what was compared, what discrepancies were found, and how each was resolved. This documentation creates an audit trail that supports both internal controls and external audit requirements.

This process matters because errors in AP records tend to compound when left undetected. A Gartner survey of nearly 500 accounting professionals found that 59% make several financial errors per month, with capacity constraints from manual processes and growing workloads cited as the primary cause. Regular vendor statement reconciliation is one of the key controls that catches these errors early, before they distort financial statements, trigger duplicate payments, or damage supplier relationships.

Beyond error detection, the aging breakdown on a vendor statement also supports payment prioritization. When cash flow is constrained, AP teams use the aging buckets to identify which supplier balances are most overdue and allocate payments accordingly, addressing 90+ day balances before current ones to avoid late fees and preserve supplier terms.

For a step-by-step walkthrough of this process with a worked example and automation tiers, a dedicated guide on reconciling vendor statements covers the full workflow in detail. Teams looking for broader context on three-way matching and automation strategies will also find a dedicated guide on the invoice reconciliation process useful.

---

Common Vendor Statement Discrepancies

The most frequent mismatches AP teams encounter during vendor statement reconciliation are missing invoices (supplier billed but AP has no record), unapplied payments (payment sent but not credited on the statement), duplicate charges, pricing or amount differences between the invoice and the purchase order, credit notes not applied to the account, and timing differences where payments cross in transit near the statement cut-off date.

Each discrepancy type follows a standard resolution path. For step-by-step resolution procedures, a worked numerical example, and automation tiers, see the dedicated guide on vendor statement reconciliation. When repeated mismatches point to something more serious than clerical error, an overview of accounts payable fraud red flags and controls helps separate suspicious activity from routine statement noise.

Pricing discrepancies often trace back to the goods received note, which records what was actually delivered versus what was invoiced. Checking the GRN against the supplier's delivery note pinpoints whether a quantity or pricing mismatch originated at the point of delivery. Understanding how credit notes relate to invoices is also essential when reconciling unapplied credits.

---

Putting Vendor Statements to Work

• Set a recurring reconciliation schedule. Request statements from high-volume and high-balance suppliers at least monthly. For lower-volume suppliers, quarterly reconciliation is a reasonable starting point.
• Prioritize by risk and volume. Focus reconciliation effort on suppliers carrying the largest outstanding balances or generating the most transaction activity, where undetected errors carry the greatest financial exposure.
• Document every resolution. When discrepancies surface, record the investigation steps, communications, and outcome. This audit trail protects your team during internal or external audits and prevents the same issue from being re-investigated later.
• Reduce manual matching effort at scale. For AP teams processing high volumes of vendor-referenced documents such as invoices, credit notes, and purchase orders, AI-powered invoice data extraction tools can cut the manual work involved in matching document data against vendor statement records, freeing your team to focus on exception handling and supplier communication rather than data entry.