Vendor Statement: Definition and AP Meaning

Glossary definition of a vendor statement: what it is, how it differs from an invoice, and why it matters for margin drift audits. Read the full guide.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Vendor Statement: Definition and AP Meaning

A vendor statement is a periodic summary a vendor issues listing the invoices it has billed, the payments it has received, and the balance it believes is still owed. It is an account-level snapshot, not a transaction-level record: it shows totals and aging buckets, not the rate card, contract clause, or line-item detail behind each charge.\n\nAP teams use it to reconcile their own ledger against the vendor's view of the account. Where the two disagree, that gap is where margin drift and simple timing differences both hide, and only closer review of the underlying invoices tells them apart.

1. What information does a vendor statement contain?

A vendor statement lists, for a given period, each invoice number and date the vendor billed, each payment it recorded against your account, and the resulting open balance, usually grouped into aging buckets such as current, 30, 60, and 90 days past due. It does not itemize product or service lines, rates, or contract clauses. It is a balance document, built from the vendor's own receivables ledger.

AP teams read it alongside the invoices themselves, never in place of them.

2. How is a vendor statement different from an invoice?

An invoice is a bill for one delivery: it names the goods or services provided, the quantity, the rate, and the amount due against a purchase order or contract. A vendor statement is a rollup across many invoices and payments over a period, showing only totals and balances. An invoice creates the obligation to pay; a statement reports on obligations already created.

Reconciling one against the other is a standard part of monthly AP close.

3. Why does a vendor statement matter when auditing margin drift?

A vendor statement confirms what the vendor's own records show was billed and paid, which gives an independent check against your internal ledger. A mismatch between the two does not prove an error by itself; it flags an amount worth tracing back to the invoice and the contract terms behind it, which is where drift such as a rebate gap or a volume tier misapplication actually gets confirmed.

The statement points to where to look. It does not itself prove the finding.

4. What should an AP team do when a vendor statement does not match its ledger?

Trace the specific invoice numbers or dates causing the variance, pull the underlying invoice and purchase order for each, and check them against the contract terms that should govern the charge. Timing differences, such as a payment in transit, resolve on their own. Genuine mismatches, like an invoice billed twice or a credit never applied, need to be logged and pursued with the vendor directly.

A regular reconciliation cadence catches these gaps before they age into write-offs.

  1. Isolate the variance: Identify which invoice numbers or dates account for the difference between the statement balance and the internal ledger.
  2. Pull source documents: Retrieve the invoice, purchase order, and relevant contract clause for each flagged item.
  3. Classify the cause: Determine whether the gap is timing, a duplicate charge, a missing credit, or a contract term applied incorrectly.
  4. Escalate to the vendor: Raise confirmed discrepancies with the vendor's AR contact and track resolution to close.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

What is a vendor statement?

A vendor statement is a periodic summary a vendor sends listing invoices billed, payments received, and the resulting balance owed. It is an account-level document, not a transaction-level one: it shows totals and aging, not line items, rate cards, or contract terms.

Is a vendor statement the same as an invoice?

No. An invoice bills for a specific delivery of goods or services against a purchase order or contract. A vendor statement summarizes a set of invoices and payments over a period, usually a month, to show the running balance. AP teams reconcile the two together.

Why does a vendor statement matter for margin drift?

A vendor statement confirms what a vendor believes it billed and what it believes was paid. Comparing that balance against your own AP ledger surfaces timing gaps, disputed amounts, and open credit memos that a single invoice review would not reveal.

Can a vendor statement show a duplicate payment?

It can point to one. If the statement shows a lower balance than your ledger expects, or the same invoice number appears twice in the vendor's activity, that is a signal worth tracing, though the underlying invoices confirm it. See duplicate payment for the mechanism.

Does a vendor statement show contract terms like rate cards or volume tiers?

No. A statement lists dollar amounts and dates, not the rate card, volume tier, or rebate clause behind them. Confirming those terms requires the contract itself and the individual invoices, not the statement.

How often do vendors send statements?

Most commonly monthly, aligned to the vendor's own billing cycle. Some vendors send them only on request or when a balance ages past a set number of days. The cadence is set by the vendor, not a fixed standard.

Who reconciles vendor statements inside a company?

Typically the accounts payable team, as part of routine ledger close. The reconciliation confirms the statement balance matches the company's own payable balance for that vendor and flags any variance for research.

1. What information does a vendor statement contain?

A vendor statement lists, for a given period, each invoice number and date the vendor billed, each payment it recorded against your account, and the resulting open balance, usually grouped into aging buckets such as current, 30, 60, and 90 days past due. It does not itemize product or service lines, rates, or contract clauses. It is a balance document, built from the vendor's own receivables ledger. AP teams read it alongside the invoices themselves, never in place of them.

2. How is a vendor statement different from an invoice?

An invoice is a bill for one delivery: it names the goods or services provided, the quantity, the rate, and the amount due against a purchase order or contract. A vendor statement is a rollup across many invoices and payments over a period, showing only totals and balances. An invoice creates the obligation to pay; a statement reports on obligations already created. Reconciling one against the other is a standard part of monthly AP close.

3. Why does a vendor statement matter when auditing margin drift?

A vendor statement confirms what the vendor's own records show was billed and paid, which gives an independent check against your internal ledger. A mismatch between the two does not prove an error by itself; it flags an amount worth tracing back to the invoice and the contract terms behind it, which is where drift such as a rebate gap or a volume tier misapplication actually gets confirmed. The statement points to where to look. It does not itself prove the finding.

4. What should an AP team do when a vendor statement does not match its ledger?

Trace the specific invoice numbers or dates causing the variance, pull the underlying invoice and purchase order for each, and check them against the contract terms that should govern the charge. Timing differences, such as a payment in transit, resolve on their own. Genuine mismatches, like an invoice billed twice or a credit never applied, need to be logged and pursued with the vendor directly. A regular reconciliation cadence catches these gaps before they age into write-offs. 1. Isolate the variance: Identify which invoice numbers or dates account for the difference between the statement balance and the internal ledger. 2. Pull source documents: Retrieve the invoice, purchase order, and relevant contract clause for each flagged item. 3. Classify the cause: Determine whether the gap is timing, a duplicate charge, a missing credit, or a contract term applied incorrectly. 4. Escalate to the vendor: Raise confirmed discrepancies with the vendor's AR contact and track resolution to close. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

What is a vendor statement?

A vendor statement is a periodic summary a vendor sends listing invoices billed, payments received, and the resulting balance owed. It is an account-level document, not a transaction-level one: it shows totals and aging, not line items, rate cards, or contract terms.

Is a vendor statement the same as an invoice?

No. An invoice bills for a specific delivery of goods or services against a purchase order or contract. A vendor statement summarizes a set of invoices and payments over a period, usually a month, to show the running balance. AP teams reconcile the two together.

Why does a vendor statement matter for margin drift?

A vendor statement confirms what a vendor believes it billed and what it believes was paid. Comparing that balance against your own AP ledger surfaces timing gaps, disputed amounts, and open credit memos that a single invoice review would not reveal.

Can a vendor statement show a duplicate payment?

It can point to one. If the statement shows a lower balance than your ledger expects, or the same invoice number appears twice in the vendor's activity, that is a signal worth tracing, though the underlying invoices confirm it. See duplicate payment for the mechanism.

Does a vendor statement show contract terms like rate cards or volume tiers?

No. A statement lists dollar amounts and dates, not the rate card, volume tier, or rebate clause behind them. Confirming those terms requires the contract itself and the individual invoices, not the statement.

Margin Drift Resources