Skip to main content

New: the AI Shortlist. Describe your company and get matched products with the review evidence behind each one. Try it free

Procurement VMSProcurement software, honestly rated.

HomeDocument decoderVendor Invoice

Document decoder

Vendor invoice: what it must contain and how accounts payable should handle it

A vendor invoice that arrives incomplete costs more to fix than it did to write.

By Procurement VMS Editorial TeamReviewed by Michael, Procurement Advisor ExpertUpdated 4 minute read

On this page
  1. What a vendor invoice is
  2. Common vendor errors
  3. Frequently asked questions

Key takeaways

  • A vendor invoice is a supplier's request for payment, with the details of what was supplied and what is owed.
  • Required fields vary by country but usually include the vendor, buyer, date, number, description, amounts, tax and payment terms.
  • Accounts payable should reject or query invoices that lack an order reference, a valid tax number or matching quantities.
  • Giving vendors a short guide to your invoice rules cuts rework.

Free PDF and Excel: Vendor invoice rules sheet and rejection log. Get it below

What a vendor invoice is

Definition

A vendor invoice is a document from a supplier to a customer that lists goods or services supplied, the amount due and the payment terms.

The same document is a sales invoice to the vendor and a purchase invoice to you. This page is aimed at the team that receives and sets the rules for vendor invoices.

Made-up example, for illustration only

A company publishes a one-page vendor guide: invoices must carry a PO number, be addressed to the legal entity, show tax registration and be sent to one mailbox. Within six months, the share of invoices rejected for missing PO numbers falls from 22 percent to 6 percent.

Fields to require
FieldWhat goes in itWhy it matters
Vendor name, address and tax numberAs on the vendor master.Identifies the supplier.
Buyer name and addressYour legal entity.Correct entity for tax.
Invoice number and dateUnique, sequential.Duplicate check.
PO numberYour order reference.Three-way match.
Description, quantity, priceLine by line.Matches the order.
TaxRate and amount.Credit claim.
Total and currencyStated clearly.Payment.
Payment terms and bank detailsAs contracted.Scheduling.

Common vendor errors

  • No PO number.
  • Wrong legal entity.
  • Rates differ from the contract.
  • Charges for items not delivered.
  • Bank details changed without a verified request.
  • Duplicate invoice numbers.

The processing flow is in the invoice approval and GRN guide. Disputes may end in a credit note.

Vendor invoice rules to publish
  • Mailbox or portal for invoices.
  • PO number is mandatory.
  • Legal entity names.
  • Tax details required.
  • Format accepted: PDF, e-invoice, portal.
  • Contact for disputes.

Last checked: 19 October 2026. General practice. Tax invoice contents are set by local law.

Free PDF and Excel

Vendor invoice rules sheet and rejection log

A one-page rules sheet to send to vendors and a log for tracking rejected invoices and reasons.

  • Rules sheet
  • Required fields table
  • Rejection reason log
  • Excel rejection tracker

Frequently asked questions

What is a vendor invoice?

A supplier's bill to a customer for goods or services supplied.

What must a vendor invoice include?

Vendor and buyer details, date, number, description, amounts, tax and payment terms. Local law adds more.

How do you verify a vendor invoice?

Match it to the order and receipt, check the tax number and bank details, and test for duplicates.

Why do invoices get rejected?

Common reasons are missing PO numbers, wrong entity, mismatched prices or quantities, and missing tax details.

Where should vendors send invoices?

To a single, published mailbox or portal.

Where to read next

Take the PDF to your next meeting

It is a working document, not a brochure. Fill it in with your own numbers and share it with your team.

Looking at software instead? See our ranked procurement software list.

Disclosure: Zapro AI appears on some comparison pages as an editor's pick, and the people behind this site have a professional connection to Zapro AI.

Written by

Procurement VMS Editorial Team

Our editors research each guide from vendor documentation, public pricing pages and buyer feedback, and name the sources on the page. Learn who the team is.

Reviewed by

Michael, Procurement Advisor Expert

Michael checks our guides for practical accuracy against how procurement teams buy and run software. Read his profile.

Editorial guide

How we write and check pages

Read our editorial policy, how we handle corrections and what we do when a source changes.

Explore this topic with AI

Open this page in your assistant of choice, get the key takeaways and carry on the conversation.