Invoice vs Receipt: What Is the Difference?

Most people use the words interchangeably. Most tax authorities do not.

An invoice is a formal payment request issued before payment is made. A receipt is proof that payment occurred. The gap between those two things is where VAT reclaim fails, expense reports get rejected, and audits turn up gaps in a company's financial record.

This guide explains what each document actually contains, why the distinction matters legally, when you need one versus the other, and what to do when a vendor hands you the wrong one.

The one-paragraph answer

An invoice says "you owe us this amount, by this date, for these goods or services." A receipt says "you paid this amount, on this date, for these goods or services." Invoices come before payment; receipts come after. Invoices carry legal weight as a payment demand; receipts carry legal weight as proof of settlement. In B2B transactions in most tax jurisdictions, invoices also carry the structural fields that make VAT reclaim and expense deductions possible. Receipts generally do not.

What an invoice actually contains

A proper invoice is a structured document with specific fields. Not every invoice includes every field, but the core set is consistent across jurisdictions.

Invoice number. A sequential, unique identifier issued by the vendor. This is the field that makes an invoice traceable and auditable. Invoice numbers allow both parties to reference the same document unambiguously, and auditors use them to verify that a company has not duplicated a vendor relationship or fabricated a transaction. If a document does not have an invoice number, it is not functioning as a proper invoice.

Issue date and due date. The issue date establishes when the payment obligation was created. The due date establishes when it must be settled (net-30, net-60, or whatever terms were agreed). These two dates are what accounts payable teams track for cash flow management, and they are what vendors reference when pursuing overdue payments.

Vendor and buyer identification. An invoice includes the vendor's full legal name and business address. In VAT jurisdictions, it also includes the vendor's tax registration number. For B2B transactions, it typically includes the buyer's business name and address, and the buyer's tax ID as well. These fields are what distinguish a tax invoice from a generic payment document.

Itemized line items. What was sold, how many units, at what unit price. Line items are not optional in a proper invoice. They are the basis for verifying that what was charged matches what was ordered, and they are what auditors examine when verifying that an expense was legitimate.

Tax breakdown by rate. In jurisdictions with VAT or GST, the invoice must show tax broken out by rate. If the vendor charges 20% VAT on some line items and 5% on others, each rate appears separately with its taxable base and the tax amount. A single line that says "tax: $48.00" without specifying the rate does not qualify as a VAT invoice in most jurisdictions.

Payment terms and method. Net-30, due on receipt, bank transfer only, late payment interest rate. These terms may be agreed in a contract, but they appear on the invoice so both parties have them in writing for each transaction.

Total and currency. The amount owed, in the transaction currency. For international invoices, some vendors include an exchange rate and a converted amount in a second currency.

What a receipt actually contains

A receipt is a simpler document. Its job is to confirm that a transaction completed, not to establish a payment obligation.

A typical receipt includes the seller's name, the date of the transaction, a list of items purchased or services rendered, the amounts charged, the total paid, and the payment method used (cash, card, bank transfer). Consumer receipts often add the last four digits of the card used.

What a receipt usually does not include: a sequential document number, the seller's tax ID, the buyer's tax ID, an itemized tax breakdown by rate, or payment terms. Some receipts include a total tax line (useful for knowing how much GST was in a restaurant bill), but not a breakdown by rate that qualifies for input tax reclaim.

The structure is simpler because the purpose is simpler. A receipt does not need to define an obligation. It is evidence that an obligation was already met.

The legal distinction by jurisdiction

The practical difference between an invoice and a receipt varies significantly depending on where you operate.

United States (IRS). The IRS does not require a specific "invoice" format for expense deductions. What it requires is adequate documentation of a business expense: the amount, the date, the vendor, and the business purpose. A receipt often satisfies this for ordinary business expenses. However, the IRS may ask for more detail during an audit, and for larger transactions, itemized documentation becomes important. IRS Publication 583 covers the general record-keeping requirements for small businesses in detail.

United Kingdom (HMRC). HMRC makes a sharper distinction. For VAT-registered businesses, only a VAT invoice qualifies for input tax reclaim. A VAT invoice must include the supplier's VAT registration number, the tax point (the date the VAT becomes due), the buyer's name and address for B2B transactions, and the tax amount per rate. A receipt that does not include these fields does not qualify, no matter what the email subject line says. HMRC's guidance on VAT invoices specifies exactly which fields are mandatory for full versus simplified invoices at different transaction amounts.

European Union (VAT Directive). The EU VAT Directive (2006/112/EC) sets the baseline requirements across all member states, with individual countries adding local requirements on top. The Directive requires that a VAT invoice include the supplier's VAT identification number, a sequential invoice number from a unique series, the date of issue, the date of supply if different, the buyer's VAT ID for cross-border B2B, and the taxable amount and VAT amount per rate. Simplified invoices (similar to receipts) are permitted for lower-value transactions, typically below 100 EUR, but they do not always qualify for input tax credit depending on the member state. The full requirements are set out in Articles 219 to 240 of the VAT Directive.

Practical takeaway. If you operate in a VAT or GST jurisdiction, a receipt does not substitute for an invoice when you want to reclaim input tax. If you operate in the US, a receipt usually works for expense deductions but may not hold up under audit scrutiny for large or complex transactions. Know your jurisdiction's rules before filing.

When you need an invoice versus a receipt

The right document depends on the context. Here is where each one matters.

B2B purchases, VAT reclaim. You need an invoice. Specifically, a tax invoice with your business's name and VAT ID, the supplier's VAT ID, and a breakdown of tax by rate. A payment confirmation email from Stripe or a cash register receipt does not qualify. This applies to every B2B purchase in an EU or UK context and to GST-registered purchases in Australia, Canada, and similar systems.

Business expense reimbursement. Many companies accept receipts for small amounts (under a company-defined threshold) and require invoices for anything larger. Check your company's expense policy. If you are the person setting the policy, note that requiring invoices for everything above $50 gives you a cleaner audit trail and prevents the gap where employees submit receipts that do not include itemized tax.

Accounts payable and cash flow management. You need invoices. A receipt tells you what was already paid. An invoice tells you what is coming due. AP teams track invoices to manage when payments are released, capture early payment discounts, and avoid late fees. Receipts do not contain due dates or payment terms because those are irrelevant once payment has been made.

Proof of payment in a dispute. You need a receipt. If a vendor claims you did not pay and you need to prove you did, a receipt with the payment method and date is the right document. An invoice shows an obligation existed, not that it was settled.

Audit trail for B2C businesses. For businesses selling to consumers, issuing receipts is standard. Invoices are typical in B2B contexts. If you run a consumer-facing business, your records of sales should include receipts for every transaction, not just the ones above a threshold.

Individual expense tracking, personal taxes. Receipts usually suffice. The IRS and HMRC both accept receipts for personal expense documentation, provided the receipt shows the amount, vendor, and date. The exception is if you are a sole trader or freelancer claiming VAT input credit, in which case the rules above apply.

Where the terms get conflated

Several common business situations blur the line between invoice and receipt in ways that cause real problems.

SaaS subscriptions. When Stripe charges your card on the first of the month, the email that arrives in your inbox is almost always labeled "receipt" or "invoice" interchangeably depending on the vendor's email template. In practice, what you receive is often a payment confirmation, not a proper tax invoice. To get a real invoice with a sequential number, your VAT ID on the document, and a tax breakdown, you usually need to first enter your business details in the vendor's billing settings. Platforms connected through Stripe or Amazon Business handle this in specific ways that are worth understanding before you assume you have the compliant document.

App stores (Apple, Google). App Store and Google Play purchases generate receipts, not tax invoices. This matters if you are buying paid apps or subscriptions for your business and want to reclaim VAT. Both Apple and Google have a separate process for business billing that issues proper invoices, but it requires setting up a business account rather than making personal purchases. Many businesses discover this gap during an annual VAT return when their accountant flags that the app store charges in their records are backed only by purchase receipts.

Cash sales. A cash sale completed with a handwritten receipt or a simple cash register slip is technically a receipt, not an invoice. No invoice number, no tax ID, no terms. For the buyer, this is usually fine for small incidental expenses. For the seller, cash transactions with only a receipt create a record-keeping gap that tax authorities look at closely. If you receive significant income from cash sales, issuing proper numbered invoices even for completed cash transactions is better practice.

Utilities and telcos. Monthly utility and telecom bills often say "invoice" on them, but they are issued after the service period and after payment has often been automatically collected. Technically they function as both: a billing statement (invoice) for the period and a receipt if payment was already taken. Most tax authorities treat these as invoices for VAT purposes, but the document should still have the required fields (supplier VAT ID, your account details, tax breakdown) to qualify.

Freelance and consulting relationships. A freelancer might issue an invoice before payment and then send a separate "paid" confirmation after receiving bank transfer. In longer relationships, some clients treat the bank transfer confirmation as the receipt and discard the original invoice. Keep both. The invoice establishes the business purpose and the terms. The payment confirmation establishes settlement. You need both for a complete audit trail.

How to request an invoice when a vendor gave you only a receipt

This situation is more common than it should be. Many vendors, especially in B2C contexts, default to issuing only receipts. Getting a proper invoice usually requires one of a few approaches.

Check the vendor's billing settings first. For SaaS platforms, the fastest path is the account's billing or payments section. AWS, Google Workspace, Stripe billing, GitHub, and most subscription platforms allow you to enter a business name, address, and VAT number. Once you save those details, the platform retroactively generates proper invoices for recent billing periods and switches to invoices for all future charges. This takes five minutes and solves the problem permanently without contacting support.

Contact the vendor directly. For vendors that do not have a self-service billing portal, email or chat support with the request: "I need a VAT invoice / tax invoice for transaction [reference number] dated [date], issued to [your business name] with our VAT ID [number]." Have your business details ready in a copy-paste format. Most accounting-aware vendors can generate the document within a day or two. Some charge a small administrative fee for retroactive invoice issuance.

Use a business account instead of a personal one. Amazon, Apple, Google Ads, and similar platforms have separate business or organizational account types that issue invoices by default instead of receipts. If you have been making business purchases through a personal account, the cleanest fix is to migrate to a business account going forward. Past purchases made through the personal account may or may not be retroactively issuable as invoices depending on the platform.

Escalate if the vendor refuses. In VAT jurisdictions, a VAT-registered supplier is legally required to issue a VAT invoice to another VAT-registered business upon request. This is not optional. If a supplier refuses, you can report the issue to the relevant tax authority. In practice, most vendors comply once they understand the legal requirement, but it occasionally takes a formal written request citing the relevant directive or regulation.

Keep the request in writing. If you have to chase a vendor for an invoice, do it by email. You want a paper trail showing you requested the compliant document and when. If the vendor fails to provide it and you face questions during an audit, a documented request shifts responsibility appropriately.

For teams handling large volumes of receipts and invoices across many vendors, the classification and chasing problem compounds quickly. Inbox Ledger's AI-powered document processing flags documents that are likely receipts rather than invoices, so you know which vendor relationships need a billing settings update before year-end. The how to organize invoices effectively guide covers the broader archiving side of this problem.

Start for free and extract your first 10 invoices without a credit card.

The document that does not exist (but should)

One blind spot in the invoice-receipt distinction: the proforma invoice. A proforma is not a real invoice. It is a draft or estimate sent before goods are delivered or services are rendered, used to establish terms or support customs clearance for cross-border shipments. It does not create a legal payment obligation, and it does not qualify as a VAT invoice. Do not file a proforma as an invoice in your accounting system. Replace it with a real invoice once the transaction completes.

Similarly, a credit note is not a receipt. A credit note is issued by the vendor to reduce a previously issued invoice (for returned goods, billing errors, or agreed discounts). It carries an invoice number reference and its own sequential number. It is the offsetting document to the original invoice, and it should live in your records alongside it. If a vendor issued you a credit note and you have no record of the corresponding original invoice, your accounting record has a gap.

Organizing both documents without creating two separate archives

The practical problem with the invoice-versus-receipt distinction is that sorting documents into "invoice" and "receipt" buckets manually is tedious and error-prone, especially when vendors use the terms interchangeably in email subject lines.

A better approach: maintain a single archive organized by vendor and time period, and tag each document with its type after capture. The tagging can be automated if your extraction tool classifies documents by their fields. A document with a sequential invoice number, a supplier VAT ID, and a tax-by-rate breakdown gets tagged as an invoice. A document without those fields gets tagged as a receipt, which triggers a review to determine whether you need the proper invoice.

This is exactly the kind of classification and routing that matters at scale. For businesses managing receipts across multiple vendors, the how to organize business receipts guide covers the system design in more detail. For the vendor-specific picture on platforms that often send the wrong document type, the scanning receipts for taxes guide covers what qualifies for deduction and what does not.

For businesses on an older alternative AP system that lumps both document types together without flagging the difference, that gap shows up at audit time. The /alternativeto comparison page covers what to look for in tools that handle the distinction correctly from the start.

The short version: invoices and receipts are not the same document. They serve different purposes, carry different legal weight, and meet different requirements depending on your jurisdiction. Knowing which one you have, and which one you need, is the first step to an archive that actually holds up.