There is no universal legal count of invoice types because names overlap across countries and industries. This guide covers 20 common types of invoices used in business, from standard and proforma invoices to credit notes and e-invoices. Choosing among these different types of invoices depends on transaction stage, billing basis, issuer relationship, trade and tax rules, and delivery format.
Flat lists hide how one document can fit several categories at once. The table gives a direct overview of the types of invoices in business; the six-lens framework that follows explains how to choose and process each type.
20 Common Types of Invoices at a Glance
These 20 invoice types form a practical business taxonomy, not a universal legal classification. Labels overlap: a single document might be a recurring VAT e-invoice, for example. Synonyms such as standard invoice and ordinary sales invoice, credit note and credit memo, or interim and progress invoice are counted once.
| Type | Category or lens | When used | Example |
|---|---|---|---|
| Standard invoice (sales invoice) | Purpose | After goods or services are delivered | A designer bills a client for a completed website |
| Proforma invoice | Purpose | Before delivery, as a detailed estimate | An exporter gives a buyer the expected cost before shipment |
| Recurring invoice | Billing basis | On a fixed schedule for ongoing services | A software provider bills the same monthly subscription |
| Interim/progress invoice | Billing basis | For a completed portion or percentage of a long project | A contractor bills when 40% of the work is complete |
| Milestone invoice | Billing basis | When a specific contractual event is completed | A consultant bills after the approved design phase |
| Timesheet invoice | Billing basis | For hours recorded during a billing period | An agency bills 42 approved consulting hours |
| Retainer invoice | Purpose | To collect an advance that secures future capacity | A law firm requests a deposit before starting work |
| Final invoice | Purpose | At project close, after prior payments are reconciled | A builder bills the remaining balance after handover |
| Overdue or past-due invoice | Payment status | When an issued invoice remains unpaid after its due date | A supplier resends a Net 30 invoice marked past due |
| Consolidated invoice | Billing basis | To combine several transactions into one billing document | A wholesaler groups a month's deliveries into one invoice |
| Credit note (credit memo) | Adjustment | To reduce or cancel a prior charge | A seller credits two returned items |
| Debit note | Adjustment | To document a buyer's adjustment claim or, where applicable, an upward correction | A buyer reports damaged goods and requests a credit |
| Self-billing invoice | Issuer perspective | When an agreed buyer issues the seller's invoice | A dairy calculates payment from the measured delivery |
| Purchase invoice | Record perspective | When the buyer records a supplier's sales invoice in AP | An AP team posts a vendor's equipment invoice |
| Commercial invoice | Trade | For customs valuation of an international shipment | An exporter lists HS codes and origin for shipped machinery |
| Consular invoice | Trade | When the destination requires consular certification | An exporter has shipment details certified before dispatch |
| VAT invoice | Regulatory | For a taxable sale in a VAT jurisdiction | An EU supplier itemizes net value, VAT rate, and VAT amount |
| Tax invoice | Regulatory | For GST or another indirect-tax system | An Australian supplier issues a GST-compliant tax invoice |
| Simplified or retail invoice | Regulatory | Where local rules allow fewer fields for eligible sales | A retailer issues an abbreviated receipt for a low-value sale |
| E-invoice | Format and regulatory | When structured electronic data is required or chosen | An Italian supplier transmits invoice data through SdI |
How Invoice Types Are Categorized: A Six-Lens Framework
The categories are best treated as overlapping lenses rather than mutually exclusive boxes:
- Purpose explains the transactional reason for billing, such as requesting payment, collecting an advance, or closing a project.
- Billing basis and status explains whether billing follows a schedule, hours, progress, milestones, grouped transactions, or an unpaid due date.
- Adjustment covers documents that reduce, dispute, or otherwise correct a previous charge.
- Issuer and record perspective distinguishes who creates the document and how the same sales invoice appears in the buyer's purchase ledger.
- Trade and regulatory context covers customs documents and invoice rules imposed by tax authorities.
- Delivery format covers how the invoice is transmitted and processed, from paper and PDF to structured electronic data.
A domestic service company might only need standard, recurring, and occasional credit invoices. An import-export firm may also handle commercial invoices, VAT invoices, and structured e-invoices. The sections below explain what each type means, when to use it, and what the recipient should do.
Invoice Types by Purpose: Standard, Proforma, Recurring, and More
The most common way to categorize types of invoices in accounting is by billing purpose, basis, and status. These ten types cover most day-to-day invoicing scenarios, whether you issue them or receive them in an accounts payable workflow.
1. Standard Invoice
A standard invoice is the baseline document in any billing relationship. It is issued after goods have been delivered or services have been performed, and it represents a formal demand for payment.
A standard invoice typically contains:
- Invoice number (unique identifier for tracking)
- Invoice date and due date
- Seller and buyer details (names, addresses, tax IDs)
- Line items with descriptions, quantities, and unit prices
- Total amount due
- Payment terms (e.g., Net 30, Net 60)
When most people say "invoice" without any qualifier, they mean a standard invoice.
When to issue one: After you have fulfilled your side of a transaction and need to collect payment.
When you receive one: This is a binding request for payment. Verify the line items against your purchase order or agreement, confirm the amounts, and schedule payment according to the stated terms.
2. Proforma Invoice
A proforma invoice is issued before delivery as an estimate or preliminary bill. It outlines the expected goods, services, quantities, and prices so the buyer can review and approve the terms.
A proforma invoice is not a demand for payment. It functions more like a detailed quote or a good-faith projection of what the final bill will look like.
The difference between a proforma and a standard invoice comes down to timing and obligation. A proforma is a preliminary document sent before the transaction is confirmed. Once the buyer agrees to the terms and the seller fulfills the order, the proforma is replaced by a standard invoice, which is the actual payment request. The proforma itself carries no accounting obligation for either party.
When to issue one: When a prospective buyer requests a formal cost breakdown before committing, or when you need to provide pricing documentation for import/export planning or internal purchase approvals.
When you receive one: Treat it as a quote. Review the terms, quantities, and pricing carefully. If everything looks correct, confirm the order. The seller will then issue a binding standard invoice once delivery occurs. For a deeper AP-focused walkthrough, see this guide to handling proforma invoices before final billing.
3. Recurring Invoice
A recurring invoice is issued at regular intervals for ongoing services such as subscriptions, retainer-based work, maintenance contracts, or SaaS licenses. The amounts, line items, and payment terms are typically consistent from one billing cycle to the next.
When to issue one: When you provide a service on a fixed schedule (monthly, quarterly, annually) and the terms remain stable across periods.
When you receive one: Set up an expected payment schedule in your AP system. Because recurring invoices are predictable, any deviation in the billed amount should be flagged immediately and verified against your service agreement.
4. Consolidated Invoice
A consolidated invoice combines multiple deliveries, orders, or charges from the same supplier and period into one billing document. For example, a wholesaler might replace 20 separate delivery invoices with one month-end invoice that itemizes every shipment.
When to issue one: When the customer agreement permits periodic combined billing and every underlying transaction can be identified clearly.
When you receive one: Match each listed transaction to its purchase order and receipt, then confirm that no delivery was omitted or billed twice. Do not approve only the grand total.
5. Timesheet Invoice
A timesheet invoice bills for recorded hours, usually by employee, role, date, or activity. For example, an IT consultancy might invoice 42 approved hours at the contract's hourly rates after a two-week sprint.
When to issue one: When the contract is time-and-materials based and the relevant timesheet has been approved.
When you receive one: Compare names, hours, rates, and approval records with the contract and timesheet before payment.
6. Interim Invoice (Progress Invoice)
An interim invoice, also called a progress invoice, is issued for partial completion of a project. This type is common in construction, consulting, engineering, and any engagement where work spans weeks or months across defined milestones.
Interim invoices allow the seller to maintain cash flow during multi-phase work rather than waiting until the entire project is finished. Each interim invoice corresponds to a specific milestone, deliverable, or completion percentage agreed upon in the contract.
When to issue one: When your contract specifies milestone-based or percentage-of-completion billing, and you have reached a defined checkpoint.
When you receive one: Match the interim invoice against the project milestone or completion percentage stated in your contract. Confirm that the work described has actually been performed before approving payment. Keep a running tally of all interim payments made, because you will need this total when the final invoice arrives.
7. Milestone Invoice
A milestone invoice is triggered by a specific contractual event rather than a general percentage of completion. A software agency, for example, might bill when the client approves the design phase, even if that milestone does not equal a fixed share of total project effort.
When to issue one: When the contract names a completed deliverable, approval, or event as the billing trigger.
When you receive one: Confirm that the exact milestone and any required acceptance criteria have been met. Keep it in the same project payment schedule as interim invoices so the final reconciliation includes both.
8. Retainer Invoice
A retainer invoice is issued in advance to secure future services or reserve capacity. The client pays upfront, and the provider draws against that balance as work is performed.
The distinction between a retainer invoice and a recurring invoice matters: a retainer is prepayment for work not yet performed, while a recurring invoice bills for work that has already been completed in a given period. AP teams that handle retainers frequently also deal with prepayment invoices and their settlement against final invoices, which follow a similar advance-payment logic but with distinct journal entries at each stage. Retainers are common with law firms, creative agencies, and consultants who reserve dedicated hours or availability for a client.
When to issue one: When your engagement model requires the client to fund an account or pay a deposit before work begins.
When you receive one: Track the retainer balance carefully. As the provider delivers work, reconcile the hours or deliverables consumed against the prepaid amount. Request detailed statements showing how the retainer is being drawn down so you can verify that billings align with actual work delivered. These statements function similarly to vendor statements in accounts payable, providing a periodic summary of all transactions between the two parties.
9. Final Invoice
A final invoice is issued at the completion of a project, after all work has been delivered. It accounts for every interim payment and retainer drawdown already received, and states the remaining balance due.
In some cases, the final balance may be zero if all progress payments and retainer charges fully covered the project cost. The final invoice still serves an important purpose: it closes out the billing relationship for that engagement and provides a complete reconciliation record.
When to issue one: When the project is complete and you need to settle the remaining balance (or confirm that all payments have been received).
When you receive one: Reconcile the final invoice against every interim invoice and retainer payment you have made throughout the project. The total of all payments, including the final invoice amount, should equal the agreed project cost. Any discrepancy needs to be resolved before payment.
10. Overdue or Past-Due Invoice
An overdue invoice is an existing invoice that remains unpaid after its due date, not a replacement document with a new invoice number. For example, a supplier may resend a Net 30 invoice marked "past due" and show the original amount plus any contractually valid late charge.
When to use one: After the due date has passed, as a payment reminder that preserves the original invoice number, date, and audit trail.
When you receive one: Check whether the invoice is genuinely unpaid or stuck in approval, verify any late fee against the contract, and resolve disputes before scheduling payment.
These ten purpose, billing-basis, and status types cover most routine invoicing needs, from one-time sales to complex projects. The next category addresses documents used when a charge needs to be corrected or disputed after issue.
Adjustment Documents: Credit Notes and Debit Notes
When a charge needs to be corrected or disputed after issue, credit notes and debit notes create a documented trail of what changed and why. Each should reference the relevant original invoice, but the direction and issuer differ.
These two adjustment documents cover most post-issue reductions and claims.
Credit Note (Credit Memo)
A credit note is issued by the seller to reduce the amount the buyer owes on a previously issued invoice. It effectively reverses part or all of the original charge. The term "credit invoice" is often used interchangeably with credit note or credit memo, though the precise meaning depends on regional terminology. Terminology and legal requirements vary by jurisdiction — in Germany, for example, the term Gutschrift was redefined to mean self-billing invoice, and businesses must now use a Stornorechnung for invoice corrections under German tax law to avoid VAT complications.
When to issue a credit note:
- Goods were returned by the buyer
- A pricing error was discovered after invoicing
- A discount was agreed upon after the original invoice was sent
- Part of an order was cancelled
Key fields on a credit note:
- Reference to the original invoice number, tying the adjustment back to the specific transaction
- Amount being credited, stating the exact reduction applied
- Reason for the credit, providing a clear explanation of why the adjustment is being made
If you receive a credit note: Apply it against the referenced invoice in your AP ledger. If payment has already been made, the credit note creates a balance you can offset against future invoices from that supplier or use as the basis for requesting a refund. Understanding how invoice matching works across document types becomes particularly important here, since credit notes must be reconciled against the correct original invoice to keep your records accurate.
Debit Note
A debit note is issued by the buyer to formally notify the seller of a discrepancy or to request a credit. It is less common than a credit note but serves an important function when the buyer identifies a problem first.
When to issue a debit note:
- You were overcharged on an invoice
- Goods arrived damaged or defective
- Items listed on the invoice were missing from the delivery
In some jurisdictions, a debit note from the buyer is the formal trigger for the seller to issue a corresponding credit note. The debit note documents the buyer's claim; the credit note is the seller's acceptance of that claim. For a deeper look at how debit notes work in practice, including debit note definitions, worked examples, and journal entries, it helps to see the full accounting cycle from issuance through ledger posting.
If you receive a debit note (as the seller): Treat it as a formal dispute or adjustment request. Verify the claim against your own records, including delivery confirmations and contract terms. If the debit is valid, respond by issuing a credit note for the agreed amount.
Store every credit note and debit note alongside the invoice it references so the original charge, claim, and accepted correction remain traceable.
Invoice Types by Issuer and Record Perspective
Two labels describe who creates or records the invoice rather than why the transaction occurred. Neither is an adjustment category by default.
Self-Billing Invoice
A self-billing invoice reverses the usual issuer relationship: under a prior agreement, the buyer calculates the amount owed and issues the seller's invoice on the seller's behalf. For example, a dairy may measure a delivery at its facility, apply the agreed price, and create the supplier's invoice.
When to use one: In relationships where the buyer has the authoritative quantity or valuation data, such as agriculture, waste management, or consignment sales, and the applicable tax rules permit self-billing. The parties need a formal agreement covering responsibilities and the pricing method.
When you receive one as the seller: Verify quantities and amounts against delivery records and the agreement, then raise discrepancies promptly. Store the accepted document as your sales invoice; it does not need to modify a previous invoice.
Purchase Invoice
A purchase invoice is the buyer or AP team's name for a supplier's sales invoice after it enters the purchase ledger. It is not a separate invoice created by the buyer. For example, the same equipment invoice is a sales invoice in the vendor's records and a purchase invoice in the customer's records.
When to use the term: When recording or discussing supplier invoices from the buyer's accounting perspective.
When you receive one: Validate the supplier, line items, tax, and payment terms; match it to the purchase order and receipt where applicable; then post it to accounts payable.
International Trade Invoices: Commercial and Consular
Cross-border shipments introduce documentation requirements that domestic transactions never encounter. Customs authorities need to assess duties, verify origin, and enforce trade agreements before goods clear the border. Two invoice types exist specifically for this purpose: the commercial invoice and the consular invoice.
Commercial Invoice
The commercial invoice is the primary document for international shipments. Issued by the exporter to the importer, it functions as both a billing document and a customs declaration. Virtually every country requires one before goods can clear customs.
A commercial invoice includes several fields not found on a standard domestic invoice:
- Harmonized System (HS) codes that classify the goods for tariff purposes
- Country of origin identifying where the goods were manufactured or produced
- Incoterms (International Commercial Terms) specifying who bears responsibility for shipping, insurance, and duties at each stage of transit
- Currency of transaction and total declared value used by customs to calculate import duties and taxes
The declared value on a commercial invoice directly determines the duties and taxes the importer will pay. Incorrect HS codes can result in overpayment, underpayment, or shipment delays at the border. Mismatched Incoterms create disputes over who covers freight, insurance, and customs fees.
If you receive a commercial invoice as an importer: verify the declared value against your purchase agreement, confirm the HS codes match the actual goods, and check that the Incoterms align with what was negotiated. Errors caught before the shipment arrives are far cheaper to resolve than corrections made after customs processing has begun. Given that commercial invoices frequently involve multiple languages and varying currency formats, processing international invoices across languages and currencies adds another layer of complexity to verification.
Consular Invoice
A consular invoice is a commercial invoice that has been certified or stamped by the consulate of the importing country, located in the exporting country. This certification confirms that the invoice details are accurate and that the transaction complies with the importing country's trade regulations.
Historically, consular invoices were common in international trade. Today, only a limited number of countries still require them, and the practice continues to decline as electronic customs systems replace manual verification. Where still required, obtaining consular certification adds both cost and processing time to the export workflow, since the exporter must submit the invoice to the relevant consulate and wait for approval before shipping.
If you receive goods where a consular invoice is required: confirm the consular stamp or certification is present and valid before submitting the documentation for customs clearance. Shipments without the required consular certification will be held or rejected at the border.
Note that the commercial invoice is distinct from the customs declaration — both are typically required for international shipments, and discrepancies between them trigger inspections and delays.
Beyond these trade-specific types, many countries impose distinct requirements on invoice format and content for domestic tax compliance.
Regulatory Invoice Types: VAT Invoices, Tax Invoices, and E-Invoices
Some invoice types exist not because a business chooses them, but because the law demands them. Regulatory invoice types are defined by tax authorities and governments that dictate the format, content, or delivery method an invoice must follow. Getting these wrong carries real consequences: rejected tax deductions, audit penalties, and fines. Three regulatory categories matter most for finance professionals operating across jurisdictions.
VAT Invoices
A VAT invoice is the standard tax-compliant document required in countries that operate a value-added tax system. The EU, UK, Norway, Switzerland, and dozens of other jurisdictions mandate VAT invoices for business-to-business transactions.
In the EU, the EU VAT Directive sets minimum content requirements that all member states must enforce. A compliant VAT invoice must include:
- Seller and buyer VAT registration numbers
- The VAT rate applied to each line item
- The VAT amount broken out separately
- Net totals (before tax) and gross totals (after tax)
- Sequential invoice number, date of issue, and date of supply
Individual countries layer their own invoice types and field requirements onto the broader tax framework. Austria's Kleinunternehmerregelung, for example, imposes specific invoice rules for small businesses operating under the VAT exemption. Always apply the rules for the place and date of supply rather than assuming one VAT template works everywhere.
If you receive a VAT invoice: You need a valid, correctly formatted VAT invoice to reclaim input VAT on your tax return. Missing or incorrect VAT fields, such as an invalid registration number or an omitted VAT breakdown, mean you cannot deduct that VAT. This makes VAT invoice validation a compliance-critical step in accounts payable.
Simplified or Retail Invoice
A simplified or retail invoice contains fewer buyer or line-level fields than a full tax invoice where local law permits it, often for eligible low-value or point-of-sale transactions. A shop receipt that states the transaction date, supplier, tax treatment, and total can be one example, but the permitted fields and thresholds are jurisdiction-specific.
When to issue one: Only when the transaction and local rules qualify; use a full VAT or tax invoice when the customer needs it or the threshold and transaction rules require one.
When you receive one: Confirm that the document qualifies for simplified treatment and still supports any input-tax claim. Ask the supplier for a full tax invoice if required information is missing.
Tax Invoices
Tax invoices serve the same function as VAT invoices but in countries that use a goods and services tax (GST) or other indirect tax systems rather than VAT. Key jurisdictions include:
- Australia: A buyer generally needs a tax invoice to claim GST credits for purchases over AUD 82.50 including GST
- India: GST tax invoices with GSTIN numbers, HSN/SAC codes, and state-level tax breakdowns (CGST, SGST, IGST)
- Singapore: GST tax invoices for registered businesses
Required fields vary by country but typically include tax identification numbers for both parties, the tax rate applied, and the tax amount stated separately from the net price. India's GST system is notably complex, requiring place-of-supply rules that determine whether central, state, or integrated GST applies. In the United States, a similar state-level patchwork exists for sales tax invoice requirements across different states, where each jurisdiction sets its own rules for what must appear on a tax-compliant invoice. Thailand adds another variation, distinguishing between full and abbreviated tax invoices with different mandatory fields depending on transaction type and VAT registration status.
If you receive a tax invoice: A valid tax invoice is your documentation for claiming input tax credits. Without one, you absorb the full tax cost. In audit situations, tax authorities will request these invoices as proof that claimed credits are legitimate.
E-Invoices (Structured Electronic Invoices)
In the regulatory sense, an e-invoice is issued, transmitted, or reported through the structured format and channel prescribed by the relevant authority. A PDF sent by email generally is not a compliant structured e-invoice. The exact platform, timing, document scope, and taxpayer coverage depend on the mandate.
E-invoicing mandates are expanding rapidly across the globe:
- Italy: Mandatory domestic B2B e-invoicing since 2019 via the Sistema di Interscambio (SdI)
- India: Mandatory for in-scope taxpayers whose aggregate annual turnover reached INR 5 crore in any applicable year, via an Invoice Registration Portal
- Brazil and Mexico: Long-standing mandatory e-invoicing (Nota Fiscal Eletronica and CFDI, respectively)
- Saudi Arabia: ZATCA's generation phase has applied since December 2021, with system-integration requirements rolling out in waves since 2023
- EU-wide: The adopted ViDA (VAT in the Digital Age) package introduces digital reporting based on e-invoicing for cross-border B2B transactions from July 2030
The Peppol network is widely used for exchanging standardized electronic documents between businesses and governments, including in Europe, Australia, New Zealand, and parts of Asia-Pacific.
The regulatory push is partly about tax revenue protection. The European Commission says the ViDA package was adopted in March 2025, with cross-border B2B digital reporting taking effect on 1 July 2030; it estimates that the e-invoicing-based system can reduce VAT fraud by up to EUR 11 billion per year.
If you receive or are required to send e-invoices: Your accounting and ERP systems must be capable of generating, transmitting, receiving, and processing structured electronic invoice data. PDF attachments will not satisfy compliance requirements in mandated jurisdictions. Many businesses operating across borders are transitioning to structured e-invoicing formats specifically because regulatory mandates leave no alternative.
A perfectly accurate invoice with all the right fields can still fail regulatory requirements if it arrives in the wrong format. As e-invoicing mandates continue spreading, delivery format is becoming as consequential as invoice content for compliance.
Invoice Delivery Formats: Paper, PDF, and Structured Electronic
The final lens in the invoice taxonomy is delivery format: how an invoice is transmitted, received, processed, and stored. This lens is independent of the others. A standard invoice, a VAT invoice, or a credit note can each be delivered in any of the three formats below. The choice of format has direct consequences for processing speed, error rates, storage costs, and regulatory compliance.
Paper Invoices
Paper invoices are printed documents delivered by postal mail or by hand. Despite the digital shift across most industries, paper remains common in construction, government contracting, and regions where digital infrastructure is limited. Processing a paper invoice requires manual data entry or scanning followed by optical character recognition (OCR), both of which introduce delay and error risk.
Regulatory mandates and efficiency pressures are steadily reducing paper use. Even where paper is still permitted, printing, postage, filing, physical storage, and retrieval add handling cost that digital formats avoid.
PDF Invoices
PDF invoices are digital documents sent by email or downloaded from supplier portals. They represent the most common format for businesses that have moved away from paper, and many organizations treat PDFs as "electronic invoices." This label is misleading.
A PDF is an unstructured document. The data (supplier name, line items, amounts, tax rates) is locked inside a visual layout designed for human reading. To get that data into an accounting or ERP system, someone must either type it in manually or run the PDF through automated extraction software. The process of digitizing paper and PDF invoices into structured data adds a processing step that structured formats eliminate entirely.
As covered in the regulatory section above, a PDF sent by email does not qualify as an e-invoice under most regulatory definitions. Jurisdictions that mandate e-invoicing require machine-readable structured data, not a visually rendered document. One emerging bridge between the two formats is the hybrid invoice (such as ZUGFeRD in Germany and Factur-X in France), which embeds structured XML data inside a PDF file. Germany's expanding B2B e-invoicing mandate is accelerating adoption of these hybrid formats, and understanding Germany's e-invoicing requirements and supported formats is increasingly relevant for businesses that receive invoices from German suppliers. The human-readable PDF and the machine-readable data travel together as a single file, satisfying both regulatory requirements and the recipient's need for a visual document.
Structured Electronic Invoices (E-Invoices)
Structured electronic invoices are machine-readable data files transmitted in standardized formats such as XML, UBL (Universal Business Language), or Peppol BIS. The receiving system ingests the data automatically, without human intervention and without any extraction step. Every field (invoice number, line items, tax calculations, payment terms) arrives as discrete, labeled data that flows directly into accounting or ERP software.
The trade-off is readability. A human cannot open an XML file and scan it the way they would a PDF. Viewing software or an ERP interface is needed to render the data in a human-friendly layout. For compliance and processing purposes, though, the structured format is unambiguous. There is no interpretation of layout, no misread characters, and no extraction error.
Why the Distinction Matters
| Characteristic | Paper | Structured Electronic | |
|---|---|---|---|
| Transmission | Mail / hand delivery | Email / portal download | Network / API / platform |
| Data accessibility | Locked in print | Locked in visual layout | Directly machine-readable |
| Processing method | Manual entry or scan + OCR | Manual entry or automated extraction | Automatic system ingestion |
| Regulatory e-invoice status | No | No | Yes |
| Typical error rate | Highest | Moderate | Lowest |
The bolded "No" for PDF is deliberate. When a government mandates e-invoicing, submitting a PDF will not satisfy the requirement. Businesses planning for compliance in jurisdictions rolling out e-invoicing mandates need to adopt structured electronic formats, not switch from paper to PDF alone.
Understanding how delivery format intersects with the other lenses—purpose, billing basis and status, adjustment, issuer and record perspective, and trade and regulatory context—gives a complete picture of which invoice to use. The next section translates that understanding into a practical decision framework.
Which Invoice Type Should You Use? A Decision Framework
The previous sections explained what each invoice type is, how it works, and where it fits within the six-lens framework. This section puts that knowledge to work with a scenario-based guide.
You are billing for completed goods or services. Issue a standard invoice. This is the default document for requesting payment after you have delivered a product or finished a service. It includes line items, payment terms, and the total amount due.
You need to provide a price estimate before delivery. Issue a proforma invoice. This gives your client a detailed cost breakdown before any goods ship or work begins. Once delivery is complete, convert the proforma into a standard invoice with the final amounts.
You bill the same client regularly for the same service. Use a recurring invoice. Set up a fixed template with agreed-upon amounts and a billing cycle (weekly, monthly, quarterly). Each billing period generates a new invoice from the same baseline, reducing manual data entry and ensuring consistency.
You are working on a long-term project with milestones. Issue interim or progress invoices at each milestone, billing for the portion of work completed. When the project wraps up, issue a final invoice that accounts for the total contract value minus all interim payments already received.
You need to correct or dispute a previously issued charge. The seller issues a credit note when the amount owed should be reduced. A buyer may use a debit note to document an overcharge, damaged goods, or another claim and request the corresponding credit. Reference the original invoice number to maintain a clear audit trail.
You are shipping goods internationally. Issue a commercial invoice. This document is required by customs authorities to assess duties and clear the shipment. Before shipping, check whether the destination country requires a consular invoice certified by its local consulate, as some jurisdictions still mandate this additional step.
You operate in a VAT or GST jurisdiction. Issue a VAT invoice or tax invoice that includes all tax fields required by your jurisdiction: tax identification numbers, applicable tax rates, tax amounts broken out per line item, and any reverse charge notations. The specific field requirements vary by country, so verify your local rules.
Your jurisdiction mandates e-invoicing. Issue a structured electronic invoice through the required clearance platform or reporting network. Countries with e-invoicing mandates (such as Italy's SDI, India's IRP, or Saudi Arabia's ZATCA) specify both the data format and the transmission channel. A PDF sent by email does not satisfy these requirements.
Real scenarios layer multiple lenses. Consider a UK-based consultancy billing a German client for milestone work on a six-month project. Each completed milestone may trigger a milestone invoice (billing-basis lens) formatted as a VAT invoice with reverse-charge notation (regulatory lens) and delivered as a structured electronic invoice if the applicable rules or client's AP system require it (delivery-format lens). Or consider a Brazilian manufacturer exporting goods to the US: the shipment requires a commercial invoice with HS codes and Incoterms, while the domestic tax record may require a Nota Fiscal Eletronica. These compound scenarios are where the six-lens framework proves its value over flat lists.
If you are unsure which type applies, start with a standard invoice. The standard invoice is the foundation that every other type builds on or modifies. From there, layer on regulatory requirements as your jurisdiction demands: add VAT fields if you are in a tax jurisdiction, switch to a structured electronic format if e-invoicing is mandatory, or attach customs documentation if goods cross borders.
Common Invoice Type Mistakes and How to Avoid Them
Even experienced finance teams make errors when selecting or processing invoice types. These five mistakes appear repeatedly across businesses of all sizes.
1. Treating a proforma invoice as a final invoice. A proforma is an estimate, not a payment request. Paying against one can cause overpayment or accounting discrepancies. Wait for the standard invoice before scheduling payment; on the sending side, always convert the proforma to a standard invoice with its own number once the transaction is confirmed.
2. Issuing a new invoice instead of a credit note to correct an error. Replacing an invoice with a "corrected" version creates duplicate records and reconciliation problems. Issue a credit note referencing the original invoice number, then issue a new invoice for the corrected amount if needed.
3. Sending a standard invoice where a VAT or tax invoice is required. In VAT/GST jurisdictions, a standard invoice missing required tax fields (registration numbers, rate breakdowns) prevents the receiver from reclaiming input tax. Confirm each jurisdiction's mandatory fields and build them into your templates by default.
4. Confusing a PDF with an e-invoice. E-invoicing mandates require structured data (XML, UBL, Peppol BIS) transmitted through a government-designated system. A PDF sent by email does not qualify, regardless of how it was generated. Submit invoices through the required platform in the specified format.
5. Missing required fields on commercial invoices. Omitting HS codes, country of origin, or Incoterms causes customs holds, incorrect duty rates, and trade-agreement disqualification. Use a template covering all destination-country requirements and verify before shipping.
Frequently Asked Questions About Invoice Types
How many types of invoices are there?
There is no universal legal count because invoice labels overlap and jurisdictions define their own categories. This guide groups 20 common business invoice types into a practical taxonomy.
What are the most common invoice types?
The most common are standard or sales invoices, proforma invoices, recurring invoices, interim or progress invoices, final invoices, and credit notes. The mix depends on how a business bills, trades, and complies with local tax rules.
Which invoice type should a small business use?
Use a standard invoice by default after delivering goods or services. Then add the billing, trade, tax, and format requirements that apply—for example, recurring billing, VAT fields, customs data, or a mandated structured e-invoice.
Invoice Data Extraction
Extract data from invoices and financial documents to structured spreadsheets. 50 free pages every month — no credit card required.
Related Articles
Explore adjacent guides and reference articles on this topic.
Proforma Invoice, Credit Note, and Invoice Copy Terms
Understand proforma invoices, credit notes, invoice copies, and proforma credit notes so mixed document batches are classified and posted correctly.
What Is a Credit Invoice? Meaning, Uses, and Common Pitfalls
A credit invoice typically means a credit note or credit memo that reduces an earlier invoice. Learn what it covers, when to use it, and what to watch for.
What Is a Proforma Invoice? Guide for AP Teams
What a proforma invoice is and how it differs from a final invoice. Learn what AP teams should do when one arrives and how to reconcile it later.