An invoice is a commercial document sent by a seller to a buyer requesting payment for goods or services delivered. It specifies what was provided, amounts owed, payment terms, and due dates, serving as a transaction record for both parties and as supporting documentation for tax and accounting purposes.
That is the standard definition, but the full meaning of an invoice goes deeper when you look at it from both sides of the transaction. This guide covers invoices from the sender's and the receiver's perspective: what each field means, how invoices compare to related documents, their legal standing, how requirements differ across countries, and what the processing workflow looks like after an invoice lands on your desk.
What Is an Invoice and Why Does It Exist?
At its core, an invoice is a seller's formal request for payment. When a business delivers goods or provides a service, it issues an invoice to the buyer documenting what was provided, how much is owed, and when payment is due. The seller (also called the vendor or supplier) sends the invoice; the buyer (the customer or client) receives it. This exchange creates a financial record that both parties rely on.
Invoices serve a dual role depending on which side of the transaction you sit on:
- For the sender, an invoice triggers accounts receivable. It is the mechanism through which a business formally requests and tracks the money it is owed. Until the invoice is issued, the sale may be complete in practice but not yet recorded as a collectible obligation.
- For the receiver, an invoice triggers accounts payable. It is the document that tells your finance team or accounting software exactly what you owe, to whom, and by when. Every payment you authorize against an invoice reduces your outstanding liabilities.
This is why invoices matter in business far beyond the moment of payment. They are the primary source documents in double-entry bookkeeping, creating the audit trail that connects a transaction to your general ledger. Tax authorities expect invoices to substantiate revenue claims and expense deductions. Auditors use them to verify that reported figures match actual commercial activity.
The scale of invoicing reflects its importance. The EU alone processes enough invoices each year that the European Commission's VAT in the Digital Age initiative estimates e-invoicing mandates will reduce VAT fraud by up to EUR 11 billion annually and cut business compliance costs by EUR 4.1 billion, underscoring the invoice's role as one of the most fundamental documents in global commerce.
Invoices appear in virtually every commercial context, in many different types depending on purpose and jurisdiction. A manufacturing supplier invoices a retailer for a bulk shipment of components. A freelance designer invoices a marketing agency for a completed logo project. A law firm invoices a corporate client for billable hours. A SaaS company invoices subscribers on a monthly billing cycle. Regardless of industry, business size, or geography, the purpose of an invoice remains the same: to formally document what was sold, confirm what is owed, and provide a reliable record for both parties.
The next question is what information actually belongs on an invoice, and what each field means depending on which side of the transaction you sit on.
What Every Invoice Should Include
Whether you are sending an invoice or receiving one, every invoice follows a common structure. The fields below represent the standard components that appear on a properly formatted invoice. Knowing what to include helps senders get paid faster and helps receivers verify charges before authorizing payment.
| Field | What It Is | Sender's Purpose | Receiver's Checklist |
|---|---|---|---|
| Invoice number | A unique identifier assigned to each invoice | Tracks the transaction in your accounting system and prevents duplicate entries | Confirm the number is unique and has not appeared on a previous invoice. Use it as the reference when corresponding about payment. |
| Invoice date | The date the invoice was created and issued | Establishes the official start point for payment terms | Verify the date aligns with when goods or services were actually delivered. |
| Due date | The date by which payment is expected | Sets a clear collection timeline based on agreed payment terms | Flag immediately if the due date conflicts with your internal payment cycle or the agreed terms. |
| Vendor/seller details | Name, address, contact information, and tax identification number of the entity issuing the invoice | Identifies you as the payee and provides the tax ID required for compliance | Confirm the vendor name and tax ID match your approved vendor records. |
| Buyer/customer details | Name, billing address, and any required reference numbers such as a purchase order number | Ensures the invoice reaches the correct department and gets matched to the right account | Check that the purchase order number matches your internal records. An incorrect or missing PO number is one of the most common reasons invoices get held up in accounts payable. |
| Line items | An itemized list of each good or service provided, including description, quantity, unit price, and line total | Documents exactly what was delivered and at what price | Compare each line item against the delivery receipt or service agreement. Confirm quantities, descriptions, and unit prices match what was actually received. |
| Subtotal, tax, and total | The pre-tax sum of all line items, applicable tax amounts (sales tax, VAT, or GST depending on jurisdiction), and the final amount due | Breaks down the charges transparently for the buyer | Recalculate the math independently. Verify the tax rate is correct for your jurisdiction and that the total equals the subtotal plus tax. |
| Payment terms | The agreed conditions governing when and how payment is due | Defines expectations for cash flow planning | Confirm the terms match your contract or purchase order. |
| Payment instructions | Bank account details, accepted payment methods, or online payment links | Removes friction from the payment process so funds arrive without delays | Verify that payment details match previous invoices from the same vendor. A sudden change in bank details can be a red flag for fraud. |
Common payment terms formats: "Net 30" = due within 30 days of invoice date; "2/10 Net 30" = 2% discount if paid within 10 days, otherwise due in 30; "Due on receipt" = payment expected immediately.
In practice, most invoices place the seller's logo and contact details at the top, the buyer's details below or to the right, a prominent invoice number and date in the header, line items in a tabular grid in the body, and the subtotal, tax, and total at the bottom right. The exact arrangement varies by industry and software — some invoices add project codes, department references, or shipping details — but the top-to-bottom flow stays consistent.
With so many fields in common, invoices are frequently confused with related financial documents like bills, receipts, and statements.
Invoice vs. Bill vs. Receipt vs. Statement
People use "invoice" and "bill" interchangeably in casual conversation, and while that is understandable, the distinction matters when you are managing money on either side of a transaction.
An invoice and a bill are actually the same document viewed from opposite sides of the table. When you send a request for payment to your customer, you call it an invoice. When your customer receives that same document, they call it a bill. The paper has not changed. The terminology shifts based on your role in the transaction.
A receipt and a statement, however, are fundamentally different documents. Here is how all four compare:
| Document | Issued By | When Issued | Purpose | Payment Status |
|---|---|---|---|---|
| Invoice | Seller | Before payment | Request payment for goods or services delivered | Unpaid |
| Bill | Seller (from buyer's perspective) | Before payment | Same as invoice, viewed by the party who owes money | Unpaid |
| Receipt | Seller | After payment | Confirm that payment was received; serves as proof of purchase | Paid |
| Statement | Seller | Periodically (monthly, quarterly) | Summarize all transactions, payments, and credits over a time period | Mixed (shows overall account balance) |
The key distinction is timing and purpose. An invoice (or bill) exists before money changes hands. A receipt exists after. For a deeper comparison of how these two documents differ across use cases, see our invoice vs. receipt guide. A statement is neither a single request nor a single confirmation. It is a running summary of the entire relationship between two parties over a defined period, showing every invoice issued, every payment received, and every credit applied, along with the outstanding balance.
One additional document worth understanding is the credit note. A credit note is issued by the seller to reduce or cancel part (or all) of an outstanding invoice amount. Common reasons include returned goods, billing errors, or previously agreed discounts that were not reflected on the original invoice. A credit note always references the specific invoice it adjusts, creating a clear paper trail for both parties' records. Its counterpart is the debit note, which works in the opposite direction — issued when an amount owed needs to increase, such as after an undercharge or additional charges not covered by the original invoice.
Is an Invoice a Legal Document?
An invoice is not a contract. Sending one does not, by itself, create a legal obligation for the recipient to pay. The obligation to pay originates from the underlying agreement between the parties, whether that is a signed contract, a purchase order, or even a verbal agreement to purchase goods or services.
So what is an invoice in legal terms? It is evidence of a transaction and a formal record of a claim for payment. In a dispute, an invoice serves as supporting documentation alongside contracts, delivery receipts, and purchase orders. It demonstrates that a seller expected payment for specific goods or services at a stated price and date.
While an invoice alone does not bind anyone to payment, it becomes legally significant in several important ways:
- Tax compliance. Most jurisdictions require invoices for tax purposes. VAT invoices are mandatory across the European Union, and tax invoices are required in countries like Australia. Without properly issued invoices, businesses cannot meet their reporting obligations.
- Tax deductions and credits. Invoices form the basis for claiming input tax credits (such as VAT reclaims) and for substantiating business expense deductions. A missing or incomplete invoice can mean a denied deduction.
- Court evidence. Courts routinely accept invoices as evidence in payment disputes. A well-documented invoice, combined with proof of delivery or service completion, strengthens a creditor's case considerably.
Beyond legal proceedings, the purpose of an invoice in accounting is foundational. Invoices are the primary source documents for recording revenue on the seller's side and expenses on the buyer's side. They form the backbone of accurate financial reporting, create audit trails, and ensure compliance with accounting standards. Without invoices, there is no reliable way to verify that financial statements reflect actual business activity. The IRS requires businesses to retain records that support reported income, deductions, and credits. Invoices are a key part of this documentation. General guidance is to keep these records for at least 3 years from the date you file your return, though certain situations extend the requirement to 6 or 7 years. Retention periods vary significantly by country — see our guide to invoice retention requirements by country for a global comparison. Given these obligations, the common challenges that arise during invoice processing can create real compliance risks when left unaddressed.
Invoice requirements also vary significantly by country, which adds another layer of complexity for businesses that operate across borders.
How Invoice Requirements Vary by Country
There is no single global standard for invoices. Requirements vary by country, and what qualifies as a valid invoice in one jurisdiction may be incomplete or non-compliant in another. If your business operates across borders or works with international suppliers, understanding these differences is essential, especially when applying country-specific rules such as Oman's VAT invoice field and timing requirements.
United States
The US has no federal invoice format requirement. Businesses have broad flexibility in how they design and structure their invoices. That said, invoices must contain enough detail to support IRS record-keeping requirements, including the parties involved, the date, amounts, and a description of the goods or services. State sales tax rules can add another layer of complexity, as some states impose specific documentation requirements depending on the type of transaction and whether sales tax applies.
European Union
The EU VAT Directive mandates specific fields on VAT invoices. These include VAT identification numbers for both seller and buyer in B2B transactions, sequential invoice numbering, the date of supply, itemized VAT amounts broken down by rate, and the applicable VAT rate or rates. E-invoicing mandates are expanding rapidly across the EU, with several member countries now requiring structured electronic invoices for B2B transactions rather than PDFs or paper documents.
United Kingdom
HMRC requires VAT-registered businesses to issue VAT invoices containing specific fields: the seller's VAT registration number, the tax point (date of supply), and a clear breakdown of amounts at each VAT rate. Post-Brexit, UK VAT invoices follow UK-specific rules that are distinct from EU requirements, so businesses trading with both the UK and EU need to be aware of the differences between the two regimes.
Australia
The Australian Taxation Office distinguishes between "tax invoices" and regular invoices. GST-registered businesses must issue tax invoices for sales of AUD 82.50 or more (including GST). A tax invoice must include the seller's ABN (Australian Business Number), the GST amount, and be clearly labeled as a "tax invoice." Without a valid tax invoice, the buyer cannot claim GST credits.
The trend toward mandatory e-invoicing is accelerating globally, driven by governments seeking greater tax compliance and faster processing. Teams handling cross-border AP should verify country-specific rules before treating older practices as valid — requirements are changing rapidly in jurisdictions from the Philippines to the EU's ViDA initiative.
Regardless of which country your invoices originate from, the process of handling an invoice after you receive it follows a broadly consistent pattern.
What Happens After You Receive an Invoice
Most invoice guides focus on the sender's perspective: how to create, format, and send an invoice. But every invoice has a receiver, and the processing workflow on that side is just as critical. For anyone who processes invoices or oversees a team that does, understanding each step from receipt to reconciliation keeps payments accurate, on time, and audit-ready.
Here is how an invoice works its way through a typical accounts payable workflow.
Receive the invoice. Invoices arrive through multiple channels: email attachments, postal mail, e-invoicing systems, or supplier portals. They come in equally varied formats, from PDF files and scanned paper documents to structured electronic data interchange (EDI) transmissions. The first task is simply capturing the invoice and routing it into your processing system rather than letting it sit in an inbox or on a desk.
Capture and record the data. Once received, the invoice details need to be entered into your accounting or ERP system. This includes the vendor name, invoice number, line items, amounts, tax, and payment terms. Manual data entry is still common, particularly in smaller organizations, though many businesses now use invoice scanning and data extraction tools to automate this step and reduce keying errors.
Verify against source documents. Before approving any payment, verify that the invoice matches what was actually ordered and received. This process is called invoice matching. Two-way matching compares the invoice against the original purchase order to confirm quantities and prices align. Three-way matching adds a third document, the goods receipt or delivery record, to confirm the items were actually delivered. You can read more about how invoice matching works across two-way, three-way, and four-way methods. Any discrepancies between these documents are flagged and investigated before the invoice moves forward.
Route for approval. Verified invoices enter an approval chain that varies by organization. Approval routing is typically based on the invoice amount, the department being charged, or the budget owner responsible. A $200 office supply invoice might need only a department manager's sign-off, while a $50,000 equipment purchase could require director-level or executive approval. Clear approval thresholds prevent bottlenecks while maintaining financial controls.
Execute payment. With approval secured, the invoice is scheduled for payment according to the agreed terms. If the terms are Net 30, the payment is queued for the due date. Some suppliers offer early payment discounts, such as 2/10 Net 30, meaning a 2% discount for paying within 10 days. Taking advantage of these discounts can generate meaningful savings at scale, but only if your workflow moves fast enough to meet the discount window.
Reconcile and close. After payment is sent, the final step is recording the payment in your accounting system, matching it to the corresponding invoice, and closing the transaction. The reconciled invoice, along with its supporting documents, becomes part of your permanent financial record for auditing and tax purposes.
Each of these steps adds time and cost — understanding the real cost of processing an invoice helps quantify where manual handling is the biggest driver of expense.
Related Articles
Explore adjacent guides and reference articles on this topic.
German Invoice Types: Abschlagsrechnung to Schlussrechnung
All German invoice types explained: Abschlagsrechnung, Teilrechnung, Schlussrechnung, and more. Covers legal basis, VAT timing, and XRechnung type codes.
SKR03 vs SKR04: German Chart of Accounts Explained
English guide to SKR03 vs SKR04, with chart structure, invoice coding, DATEV handoff, ERP mapping, and when each setup fits best.
Incoterms on Commercial Invoices: Requirements Explained
Practical guide to showing Incoterms on commercial invoices, formatting the term correctly, and matching invoice wording to freight and shipping documents.
Invoice Data Extraction
Extract data from invoices and financial documents to structured spreadsheets. 50 free pages every month — no credit card required.