What Type of Invoices Should a Business Issue?

Depending on the transaction, a business may issue a tax-compliant invoice, commercial or pro forma invoice, receipt, quote or estimate, or credit note.

These documents should not be treated as interchangeable. A quote communicates proposed pricing before a transaction is finalized. A pro forma invoice can provide expected transaction details before the formal invoice is issued. A tax invoice records a formal billing event and may need to meet specific VAT or other tax requirements. A receipt confirms that payment has been made, while a credit note adjusts an invoice that has already been issued.

The distinction matters for payment architecture because different documents are connected to different business events. The invoice is generally connected to the billing obligation, the receipt to the payment event, and the credit note to an adjustment of an existing invoice. The system generating each document therefore needs access to the information required for its particular purpose.

Tax-Compliant Invoices

A tax-compliant invoice is a formal invoice that meets the applicable invoicing and tax requirements. In the EU, VAT rules establish common requirements for VAT invoices, while individual countries can have additional national rules. EU rules cover information such as the invoice date, a unique sequential invoice number, supplier and customer details, the nature of the goods or services, the taxable amount, VAT rate and VAT amount.

This makes a tax invoice different from a document that simply displays an amount and a payment button. The invoice may form part of the company's tax records and, for business customers, can be relevant to the customer's ability to reclaim input VAT.

The requirements can become more complex when a business operates across multiple countries. The applicable tax treatment may depend on the supplier, customer, type of supply and place of supply. The invoice may also need specific wording or tax information, for example where a reverse-charge mechanism applies.

The invoicing system therefore needs to have access to the information required to determine and document the applicable tax treatment. This can include the legal entity issuing the invoice, customer details, VAT identification numbers, description of the supply, tax rate and tax amount.

For businesses operating internationally, it is therefore important not to assume that a generic invoice generated by a payment provider is automatically a tax-compliant invoice for every market. The provider may generate the document, but the business remains responsible for ensuring that the invoicing process meets the applicable requirements.

Commercial and Pro Forma Invoices

A commercial invoice documents the commercial details of a transaction and is particularly important in international trade. It can contain information about the goods, quantities, prices, seller and buyer and may be used as part of customs and import processes.

A pro forma invoice serves a different purpose. It is generally issued before the final transaction or formal invoice and communicates what the expected transaction will look like. It may include the products or services, quantities, prices and other commercial information that the customer needs before proceeding.

A pro forma invoice can therefore be useful when a customer needs a document before payment or before the final invoice can be issued. For example, a customer may use it to obtain internal approval, arrange payment or prepare an import transaction.

The important distinction is that a pro forma invoice should not automatically be treated as a tax invoice. Whether a particular document has legal or tax consequences depends on the applicable rules and the substance of the transaction, not simply the title printed at the top of the document.

In a payment architecture, a pro forma invoice can therefore sit before the formal billing event. The customer receives the expected transaction details, but the final invoice is generated later when the conditions for formal invoicing have been met.

Receipts and Payment Confirmations

A receipt has a different purpose from an invoice: it confirms that the customer has made a payment.

This distinction is particularly relevant for immediate payment flows. A customer completes checkout, the payment succeeds and the business provides a receipt or payment confirmation containing information about the transaction.

A receipt does not necessarily replace an invoice. Whether a formal invoice is required depends on the transaction, customer type and applicable rules. In the EU, for example, VAT invoicing requirements differ between B2B and certain B2C transactions, with individual countries having specific rules and exceptions.

The technical distinction is useful because the receipt is normally driven by the payment event, whereas the invoice is driven by the billing or supply event. The two documents can therefore be generated by different systems.

A PSP may be well suited to generating a payment receipt because it knows whether the payment succeeded, which payment method was used and when the transaction took place. That does not necessarily mean that the PSP should also be responsible for generating the company's legally relevant tax invoice.

This distinction becomes especially important when the ERP or billing platform is the financial system of record. The PSP can provide payment confirmation while the ERP or billing system maintains the formal invoice and accounting record.

Quotes and Estimates

A quote or estimate is normally issued before the business creates an invoice. It communicates the expected price and commercial terms if the customer proceeds with the proposed transaction.

A quote may contain products or services, quantities, prices, discounts, taxes and a validity period. The customer can then accept the quote, after which the business creates the order and eventually issues an invoice.

The important distinction is that a quote is generally not the final billing document. It describes a proposed transaction rather than documenting the completed billing event.

This makes quotes particularly relevant to businesses where sales and billing are separate processes. A CRM or sales system may create the quote, the customer may accept it, an order-management system may create the order and a billing platform or ERP may subsequently generate the invoice.

A typical B2B process might therefore be:

Quote → Customer acceptance → Order → Invoice → Payment

The same principle can apply to subscription businesses. A sales team may agree a particular subscription package and pricing with a customer, create a quote, and then create the actual subscription in the billing system once the customer accepts it.

Credit Notes for Refunds and Adjustments

A credit note is used to reduce or adjust an amount that has already been invoiced. Common cases include refunds, cancellations, returned goods, pricing corrections and other changes to the original transaction.

The important point is that a credit note is normally connected to the original invoice. It should not simply be treated as an unrelated negative invoice.

For example, if a customer was invoiced €1,000 and the business subsequently determines that €200 needs to be refunded, the billing system can issue a €200 credit note referencing the original invoice. The customer's financial position is then adjusted by that amount.

What happens next depends on whether the original invoice has already been paid. If it is still outstanding, the credit note may reduce the amount the customer needs to pay. If the invoice has already been paid, the credit may result in a refund or create a credit balance that can be applied to a future invoice.

This creates an important relationship between invoice, credit note and payment. A refund is the movement of money back to the customer; the credit note is the billing document that records the adjustment to the original charge.

This distinction matters particularly in subscription billing. A customer may cancel part way through a billing period, receive a prorated adjustment or be entitled to a partial refund. The billing system determines the adjustment, while the payment system may subsequently execute the refund.

How the Different Documents Fit Together

The easiest way to distinguish these documents is to consider the stage of the commercial process they support.

A quote or estimate communicates a proposed transaction. A pro forma invoice can communicate expected transaction details before the final invoicing event. A tax-compliant invoice records the formal billing event where an invoice is required. A receipt confirms that payment has been made. A credit note adjusts a previously issued invoice.

Not every transaction will contain all of these documents. A simple consumer transaction may involve a payment confirmation and, depending on the applicable rules, an invoice. A complex B2B transaction may involve a quote, purchase order, invoice, payment and potentially a credit note.

The important point is that each document represents a different business event. Treating them as interchangeable can create problems in accounting, tax reporting and payment reconciliation.

Which System Should Generate Each Document?

The document type also influences which system should generate it.

A quote may naturally originate in a CRM or sales system. A tax invoice may be generated by a billing platform, ERP or invoicing system that has the customer, transaction and tax information required to produce the document. A receipt is often generated by the PSP because it is closely connected to the successful payment. A credit note should normally be generated by the system that owns the original invoice and the billing logic behind it.

This does not mean that a PSP cannot technically generate several of these documents. The more important question is whether the generated document corresponds to the company's legal, tax and accounting requirements.

For example, a PSP may be able to generate a PDF labelled as an invoice and include the customer, amount and payment information. That does not automatically mean the document contains every piece of information required for a VAT invoice in the relevant jurisdiction. In Germany, for example, the Federal Ministry of Finance sets specific mandatory invoice information under the VAT rules, including supplier and customer information and tax identification details.

The same consideration applies to electronic invoicing. In Germany, the structured part of an electronic invoice must contain the information required under the VAT rules so that it can be processed electronically; a PDF alone does not necessarily satisfy the definition of an electronic invoice.

This is why the business should identify the system of record for invoices rather than simply choosing whichever system can generate the most attractive invoice PDF.

How Invoices, Receipts and Credit Notes Affect Payment Processing

The relationship between these documents and the payment system should also be defined explicitly.

For an invoice, the payment system needs to know which invoice is being paid and how the payment changes its status. For a receipt, the key event is the successful payment itself. For a credit note, the billing system needs to determine the adjustment and the payment system may then need to execute a corresponding refund.

This becomes particularly important when different systems are involved. A billing platform or ERP may generate the invoice, while a PSP processes the payment. If a refund is later issued, the refund event needs to be communicated back to the billing or accounting system so that the financial records remain consistent.

The architecture should therefore avoid treating documents as isolated PDFs. The document should remain connected to the underlying customer, order or subscription, invoice, payment and accounting record.

Choosing the Right Invoice and Document Model

The right document model depends on the commercial process, customer type and applicable legal and tax requirements.

Tax-compliant invoices are required where a formal invoice must meet applicable VAT or other tax rules. Commercial and pro forma invoices are useful for communicating transaction details before or alongside the formal invoicing process, particularly in B2B and international trade. Receipts confirm that payment has been made. Quotes and estimates belong earlier in the sales process and communicate proposed pricing rather than final billing. Credit notes adjust an invoice that has already been issued.

Before selecting a PSP, billing platform or ERP, the business should therefore define which documents it needs, which system generates each document, which document represents the legally relevant invoice, and how each document relates to payments, refunds and accounting records.

This is particularly important for businesses operating across multiple countries. Generating a PDF is relatively straightforward. Ensuring that the document contains the required information, reflects the correct tax treatment, uses appropriate invoice numbering and remains connected to the underlying accounting records is the more important architectural question.

Once these responsibilities are clear, the payment and billing architecture becomes easier to design. The goal is not simply to find a provider that can generate invoices, but to ensure that invoices, receipts, credit notes and other commercial documents are generated by the right system and remain consistent with the underlying billing, payment and accounting processes.