Invoice
An invoice is a document a seller sends to request payment for goods or services already supplied, or for an agreed billing milestone. It identifies the seller and customer, describes what is being charged, shows amounts and taxes, and states when and how payment should be made. Required details vary by jurisdiction and transaction.
Why this matters when you invoice
An invoice gives the customer a clear payment request and creates a shared record of what was supplied, what it costs and when payment is expected.
Where it appears in the workflow
The document title normally identifies it as an invoice. Key details include the invoice number and date, seller and customer, line items, totals, tax information, due date and payment instructions.
Invoice example
A consultant completes a workshop and sends invoice IC-1042 for eight hours of facilitation. It lists the service date, hourly price, VAT where applicable, total due, Net 14 terms and the calendar due date.
Common mistakes
- Sending a quote when payment is actually being requested.
- Leaving the customer, line items or payment deadline unclear.
- Reusing an invoice number without checking applicable numbering rules.
Use the right document
Open the matching document mode, replace the example content and review the details before export.
This page explains common document usage. Your agreement and applicable local rules determine what applies to a transaction.
Frequently asked questions
Is an invoice proof that payment was received?
No. An invoice requests or records an amount due. A receipt normally confirms that payment has been received.
Is every invoice a structured e-invoice?
No. A PDF or paper invoice is not automatically a structured electronic invoice. E-invoices contain machine-readable invoice data in an accepted format.