Invoice

What does an invoice do in a business transaction?

Payment request, transaction record, and accounting reference

The seller uses the invoice to record the amount requested; the buyer checks the charge against the purchase. Businesses use invoices for goods and services; a freelancer billing a client uses the same basic document function as a company billing another business.

For the seller, money owed by customers is an account receivable. For the buyer, an obligation to pay a supplier is an account payable. Keeping those amounts separate from cash already received or paid matters when planning payments: an unpaid customer invoice cannot tell the seller how much money is available in the bank. The invoice records the charge, while payment records show what has been paid toward it.

Invoices also support bookkeeping and tax records. They identify what a charge relates to, so a business can connect an entry in its books to the underlying transaction. They may need other supporting documents: the IRS recordkeeping guidance explains that a combination of records may be needed to substantiate an expense. Keeping an invoice does not, by itself, establish that an expense is deductible.

Stock and work in progress need separate records too. An invoice documents a billed transaction; invoice amounts alone do not establish what stock remains or the value of unfinished work at the end of an accounting period. For UK self-employed businesses using traditional accounting, GOV.UK lists period-end stock and work-in-progress values separately from amounts owed and unpaid commitments. Keep the records needed to establish those values alongside the purchase and sales invoices, rather than treating the invoice file as a complete picture of the business’s position.

Consider a freelance developer billing after an agreed piece of work has been delivered. The linked records answer different questions:

• The agreement records the scope, price or rate, and payment terms.
• A timesheet, delivered files, or work-review record documents what was supplied or reviewed.
• The invoice identifies the work being billed and the amount requested.
• A bank record showing the incoming payment documents money received; the invoice reference connects it to the charge.

Caption: Illustrative service billed after delivery. Advance billing can precede supply; interim and recurring cycles can repeat. These records answer different questions, rather than replacing one another. IRS recordkeeping guidance · US federal procurement example · UK Small Business Commissioner

If the client questions whether a feature was delivered, the parties need the scope and work records to resolve that question. If they disagree about whether payment arrived, they need the payment record. An invoice alone does not answer either question. This example bills after delivery; an agreed advance can be invoiced before work begins, and staged work can produce several billing cycles.

An invoice alone does not resolve a disagreement over changes to the agreement or determine worker status. Check the agreement and the surrounding facts when a disputed charge introduces a new price or term. For worker classification, the US federal tax example is explicit: the IRS examines control and the parties’ relationship, rather than treating an invoice as a worker-status test.

Invoices, bills, receipts, purchase orders, and statements

An invoice and a bill can refer to the same payment request. Usage varies by business and context; there is no reliable universal rule that reserves invoices for businesses and bills for consumers. Other transaction documents have different jobs.

Document	Usual issuer	Purpose and point in the transaction
Invoice or bill	Supplier	Requests payment for identified goods or services at the relevant billing stage.
Receipt	Seller or payment recipient	Acknowledges payment received.
Purchase order (PO)	Buyer	Communicates what the buyer is ordering, normally before supply, and gives the supplier a purchasing reference.
Account statement	Supplier or account administrator	Summarizes account activity and position, including recorded payments and outstanding charges, across a period.
Quotation or estimate	Prospective supplier	Sets out proposed pricing before the customer proceeds with the purchase; check its scope and terms.

A purchase order number can link the buyer’s order to the supplier’s invoice, but the two documents come from opposite sides of the transaction. If a customer requires a PO reference, ask the customer for it before submitting the invoice. Creating another supplier invoice will not supply the missing buyer reference.

Choose the document that answers the unresolved question. If you need acknowledgement that the supplier received your money, request a receipt or payment confirmation. If a statement shows an unfamiliar charge, request the underlying invoice and transaction details, then compare them with your records. A charge appearing on both an invoice and a statement is not a reason to pay it twice.

For an incorrect charge, tell the issuer which invoice and item need correction—for example, the wrong customer entity, quantity, or price. If you only have a quotation, confirm whether the purchase has proceeded and whether the supplier has issued the payment request. The document’s title alone cannot resolve a mismatch between what was proposed, ordered, billed, and paid.

What information belongs on an invoice?

Parties, invoice numbers, descriptions, and dates

Make the invoice identifiable before asking the recipient to check its total: name the supplier, the customer, the transaction, and the relevant dates. The following is a practical checklist; the legally required fields depend on the issuer’s circumstances and local rules.

Use the supplier’s legal identity and the correct customer entity, with addresses and a contact for billing questions. Ask the customer which entity to bill and where to submit the invoice. A billing address identifies the recipient of the invoice; a delivery address identifies where the supply goes. These may differ, and a service invoice will not necessarily need shipping details. Add the customer’s purchase order number or project reference where relevant so the recipient can find the order or responsible team.

Give each invoice a unique identifier that both parties can use in correspondence and payment records. A consistent numbering scheme makes invoices easier to track; there is no universal required number of digits. For example, an issuer might use a year and sequence, such as “2026-001”, provided its scheme meets the rules that apply to it. Keep the invoice number distinct from the buyer’s PO number: one identifies this payment request, while the other identifies the buyer’s order.

Describe the goods or services precisely enough for someone other than the original contact to understand the charge. “Consulting” gives an approver little to match against the work. An illustrative service description could read “Checkout bug fixes, Project Cedar, 1–7 November 2026; 10 hours at USD 80 per hour.” This identifies the task, project, period, and charging basis. Separate tasks or goods into line items when they need separate quantities, rates, or review.

Keep the dates distinct:

• Invoice date: when this invoice was issued.
• Supply date or service period: when the goods were supplied or the billed work took place.
• Payment due date: when payment is due under the applicable terms.

For monthly work, the service period can end before the invoice is issued. Neither date automatically tells the recipient when payment is due. State the due date clearly and check that it follows the agreed payment trigger, rather than leaving the buyer to infer it from the work period.

Amounts, tax, currency, and payment instructions

Show how the amount requested was calculated and how much remains to be paid. For each item, give the quantity or hours, unit price or rate, and line total. Then show the subtotal and any applicable adjustments, such as an agreed discount, reimbursable expenses, or tax. Label those adjustments so the customer can see what each amount represents. Tax rates and required tax details depend on the transaction and applicable rules.

Keep the value of the work separate from the outstanding balance. In this hypothetical example, the customer has already paid an advance:

Calculation	Amount
10 hours × USD 80 per hour	USD 800
Less advance already received	−USD 200
Remaining balance before tax or further adjustments	USD 600

Caption: Hypothetical amounts, not a rate benchmark: 10 × USD 80 = USD 800; less an already received USD 200 advance = USD 600. Tax and other adjustments are excluded.

These figures illustrate the calculation, not a market rate or tax treatment. The current payment request is USD 600 because the supplier has already received USD 200 toward the USD 800 work value. Identify the earlier payment or credit being applied so both sides can reconcile it. An advance merely requested on another invoice is different from money already received; check which amounts have actually been paid before deducting them as payments.

State the currency explicitly—for example, USD rather than an ambiguous dollar symbol. Include the accepted payment method and the destination details needed for that method, such as the account holder and bank account information for a transfer. Give the payment reference the customer should use, usually the invoice number, plus any customer reference needed to allocate the payment.

Check these instructions before issuing the invoice. A correct total is difficult to collect or reconcile if the account details are wrong or the payment arrives without an identifiable reference. The exact bank fields depend on the payment route; a domestic transfer template may need different information from a cross-border one.

Common fields versus local legal requirements

A useful invoice checklist is a starting point for preparing the document. To establish what is legally required, check the rules for the issuer’s country, legal form, tax status, and transaction. A customer’s processing requirements, such as a project code, are another layer: they can matter to approval even when they are not statutory invoice fields.

The UK illustrates how those requirements can differ within one country. GOV.UK’s invoice-content guidance gives a core field list and adds identity requirements by business form. A sole trader must include their name and any business name used; when using a business name, they must also give an address where legal documents can be delivered. A limited company must use its full name as it appears on its certificate of incorporation. Simply copying a trading name from a logo may therefore miss information the issuer needs to provide.

UK VAT invoices have further requirements. For example, HMRC’s VAT guide specifies a sequential unique invoice number based on one or more series, as well as VAT-specific information. Whether a VAT invoice must be issued, and which form is appropriate, depends on the supply and applicable exceptions. Those UK rules should not be applied as a global template.

Before using a template, establish which rules apply to your business and sale, then check that its fields accommodate them. US state sales-tax questions and cross-border VAT treatment need their own checks; the presence of a tax box does not determine whether tax is due. If the template cannot show a required identifier or tax detail, change the template rather than assuming the field is unnecessary.

Which type of invoice fits the transaction?

Standard, advance, interim, recurring, and final invoices

Choose the billing stage that matches the agreement: a single sale, an advance, part of a project, a repeated service period, or the final balance. These names describe practical billing arrangements rather than one exclusive international legal classification. A recurring service can, for example, be invoiced in advance.

A standard or one-off invoice covers a particular sale or piece of work. A supplier delivering a single equipment order or completing a standalone repair might issue one invoice for that transaction. Its timing still follows the agreed arrangement and applicable rules; invoices are not always issued after delivery.

An advance or deposit invoice requests an agreed amount before the relevant work or supply. For a service project, the parties might agree an initial payment before work starts, with the remainder billed later. Distinguish the request from the payment: issuing an advance invoice does not show that the customer has paid it. The label also does not determine the deposit’s tax treatment.

An interim or milestone invoice bills an agreed portion of a larger engagement. For example, a development project might provide for a charge when a specified delivery stage is reached. Identify the stage and the work covered so the customer can check the billing trigger. If extra work changes the price, keep the agreement to that additional scope with the billing records rather than relying on an unexplained extra line.

A recurring invoice is issued for each repeated billing period, such as a monthly support retainer. Show the service period on each invoice so the customer can distinguish November’s charge from October’s. Repeated invoice generation and automatic payment collection are separate arrangements: collecting from a stored payment method needs the appropriate authorization and setup for that method. A monthly invoice alone does not establish that collection has occurred.

A final invoice reconciles the remaining amount at the end of the work. Show the total being settled, earlier invoices or credits relevant to that settlement, payments already received, and the balance now requested. In the earlier USD 800 work example, an already received USD 200 advance leaves USD 600 before tax or further adjustments. If an earlier stage invoice remains unpaid, account for it explicitly so the customer can see whether the final request includes that amount; do not present the same charge as separately payable twice.

Pro forma, commercial, credit, and debit documents

A pro forma invoice presents preliminary transaction information in an invoice-like format. It can set out proposed goods, prices, and payment terms before the transaction proceeds. Check what the supplier is asking you to do with it; it should not be assumed to be the final accounting or tax document. For UK VAT specifically, HMRC states that a pro forma cannot support input-tax recovery. A proper VAT invoice is needed at the relevant supply or payment stage under those rules.

A commercial invoice has a goods-trade function beyond an ordinary payment request. Customs authorities use its information for import or export clearance and assessment of duties and taxes. The US International Trade Administration’s commercial-invoice guidance advises checking destination-country requirements. That is why a goods shipment may need customs information that a domestic service invoice does not. A freelancer serving an overseas client should not assume that a goods-export template, with customs fields, is the appropriate format for their service.

Credit and debit documents adjust an earlier charge. A credit adjustment reduces it—for example, to correct an overcharge or reflect an agreed price reduction. A debit adjustment can increase it, such as when an undercharge is corrected. Names and procedures vary by jurisdiction, so check the applicable process rather than treating “debit invoice” as a universal document category.

Make the original invoice and the reason for the adjustment identifiable. For UK VAT corrections, HMRC’s credit- and debit-note rules include that linkage. It lets the recipient follow the change from the original charge to the revised balance. A credit note also needs to be reconciled with payment records: reducing the charge does not itself show that a cash refund has reached the customer.

Overdue describes a balance that remains unpaid after its due date. It is a status, not a separate kind of sale. A reminder should identify the original invoice and outstanding amount so the customer can check it; it should not make the same original charge appear payable a second time.

How are paper, PDF, and structured e-invoices different?

Choosing a delivery format and submission channel

Choose both the invoice format and the route the customer uses to receive it. A PDF is a file format; email is a delivery channel. A portal can receive a PDF, structured invoice data, or another accepted format. Sending an invoice electronically does not, by itself, establish that it meets a particular legal definition of an e-invoice.

Paper and ordinary PDFs present information for a person to read. A structured invoice carries data in defined fields that a receiving system can process electronically. Some formats combine structured data with a readable presentation. If a customer asks for a structured e-invoice, ask which format its system accepts rather than assuming an emailed PDF will suffice.

The submission channel is a separate practical requirement. The customer may process invoices through an accounts-payable email address, a supplier portal, or an agreed system interface. Ask where to send the invoice, which attachments or references to include, and how to check that it was received. Sending it only to the person who commissioned the work may leave it outside the finance team’s processing route.

A payment link gives the customer a way to access a payment page or make a payment. Check that the invoice itself is available in the required form; the presence of a working link does not establish that the invoice’s contents or format satisfy applicable rules. Likewise, a template can keep the layout consistent, but a polished design does not validate the fields or authenticate the payment destination.

Before submitting, confirm that the recipient can open or process the document and that the channel is the one it requested. Keep the invoice and any submission acknowledgement linked. An upload confirmation or email receipt documents a delivery step; approval and payment still need to be tracked separately.

Germany’s structured e-invoice example

Germany makes the format distinction consequential for domestic business transactions within its VAT regime. As of 14 November 2026, the Federal Ministry of Finance’s e-invoice FAQ distinguishes an E-Rechnung, whose structured data permits electronic processing, from an “other invoice” such as paper or a simple unstructured PDF. Emailing that PDF does not turn it into an E-Rechnung under these rules.

Qualifying formats include XRechnung and qualifying ZUGFeRD formats. XRechnung needs a viewer for human-readable presentation; a hybrid format can combine a readable document with structured data. The structured part is decisive in a hybrid invoice. Check the actual format and data rather than assuming that every XML file, every ZUGFeRD profile, or every file with a PDF presentation qualifies.

Receiving and issuing have different timelines:

• Receiving: domestic businesses have needed the capability to receive E-Rechnungen since 1 January 2025. An email inbox is sufficient as a receiving channel. An exemption from issuing—for example, under the small-business supplier regime—does not remove the need for receipt capability.
• Issuing: transition provisions permit other invoice formats through 31 December 2026. An extended transition runs through the end of 2027 for issuers with prior-year turnover up to EUR 800,000. A separate transition through the end of 2027 also covers EDI transmission that does not yet meet the new structured-format requirements.

During those transitions, other electronic formats, such as a simple PDF, require the recipient’s consent; paper remains possible under the transition provisions. A business can therefore need to receive structured invoices while still being permitted to issue another format for an eligible transaction.

Caption: Germany, domestic VAT B2B; 14 Nov 2026. Check scope/exceptions; B2G is separate. End-2027 covers prior-year turnover ≤ EUR 800,000 or transitional EDI. Other electronic formats during transition need recipient consent. German Federal Ministry of Finance

Check scope and exceptions before applying that timeline. The domestic VAT B2B rules include exceptions for, among other cases, small-amount invoices up to EUR 250 gross, small-business suppliers, and many exempt transactions. Business-to-government invoicing has separate provisions. A foreign customer or a public-sector order therefore needs its own scope check rather than an automatic application of this B2B example.

For a particular invoice, establish which transaction rules apply, whether an exception or transition is available, and which qualifying format and channel the recipient accepts. Receipt readiness alone does not answer whether the supplier must issue a structured invoice for that transaction today.

How does an invoice move from issue to payment?

Agree terms, create the invoice, and submit it correctly

Agree the billing trigger and payment terms before preparing the invoice. Establish whether the charge falls due in advance, at a milestone, or after a service period, then confirm the payment method and the event from which the payment period runs. Record those terms with the agreement so the invoice can apply them consistently.

“Net 30” needs a clear starting point. For example, parties might agree payment within 30 days of receipt of a correct invoice. That is a specified arrangement, not a global default; counting from issue, delivery, or approval could produce a different due date. Put the resulting due date on the invoice and resolve any uncertainty about the trigger before sending it.

At the agreed billing stage, prepare the invoice using the correct customer entity and reference. Compare it with the agreement and work records, recalculate the charges, and check any previous payments or credits. Attach the supporting material the buyer needs, such as the relevant timesheet or delivery record, rather than expecting an approver to reconstruct the transaction from a vague description.

Submit the checked version through the buyer’s designated channel. The UK Small Business Commissioner’s invoicing guide recommends establishing the right customer details and submission arrangements. Ask who handles missing references or rejected submissions, and retain the sent copy and any acknowledgement.

Track what that acknowledgement actually confirms. Generating an invoice creates the document; successful submission gets it into the buyer’s receiving process; approval follows the buyer’s review. If a portal rejects the file or an email goes to the wrong contact, resolve that delivery problem before treating the invoice as awaiting payment. None of these steps alone confirms that money has been received.

Review and approve a received invoice

Before approving an invoice, match the request to an authorized purchase and the goods or services received. Start with the supplier and customer entity, then compare the scope, quantity, rates, and payment terms with the agreement or purchase order. Ask the person responsible for the delivery to confirm the work where the invoice alone cannot establish what was supplied.

Check your existing invoice and payment records for the same supplier, invoice number, amount, and date. A PDF arriving by email after the same invoice was uploaded to a portal may be another copy of one request. Resolve a possible duplicate before scheduling a second payment, and account for credits or partial payments already recorded.

If the charge is unexpected, the scope is disputed, or the billed entity is wrong, stop and clarify it with the responsible purchaser and supplier. Identify the specific mismatch and obtain the missing support or correction. Receiving an invoice starts that review; it does not, by itself, justify approval. Route the checked invoice to the person authorized to approve that purchase under your organization’s process.

Separately, authenticate any change to the payment destination. A familiar supplier name, plausible total, and ordinary-looking email can accompany a request to send money to a different account. Those details do not establish who controls the new destination. The FBI’s Internet Crime Complaint Center recommends verifying account-information changes through a secondary channel.

In practice, contact the supplier through a previously established number or other independently known channel before paying into the changed account. A new telephone number supplied in the change email does not provide that independent check. If the supplier cannot confirm the change through the known channel, hold the payment and investigate rather than relying on the invoice’s appearance.

Caption: Practical review, not a guarantee: check the transaction and verify changed account details through an independently established channel. A familiar sender or correct total does not authenticate the destination. US federal procurement example · FBI IC3 guidance

These checks address different questions: matching the charge establishes what you are being asked to pay for, while verifying an account change checks where the money would go. Resolve a failure in either check before completing the normal payment authorization.

Pay, reconcile, and retain the linked record

Pay an approved invoice through the agreed method and include the requested invoice or customer reference. Retain the payment confirmation and identify which invoice it relates to. If the reference is missing or one transfer covers several invoices, give the supplier the allocation details so it can match the money to the correct charges.

The seller then reconciles the receipt against the invoice: check the amount received, apply it to the relevant balance, and account for any credits or earlier payments. A partial payment leaves a remaining balance; record that balance explicitly rather than treating the invoice as either wholly unpaid or fully settled. If the receipt does not match the expected amount, investigate the difference before closing the record or chasing the customer.

Keep payment initiation separate from confirmed receipt. A payer’s transfer instruction shows a payment action, while the supplier needs evidence of the incoming funds. Software labels also need interpretation. “Sent”, “viewed”, or “approved” describes document handling, and a “paid” label may have been entered manually or reflect a credit applied to the balance. Check the underlying payment and adjustment records when deciding whether more money remains to be received.

Retain the invoice with its agreement or order reference, relevant work evidence, approval, payment records, and any corrections. That linked set lets a later reviewer follow the charge through to its settlement without mistaking the invoice for proof of payment. Apply the retention rules relevant to your jurisdiction and record type; there is no single retention period for every invoice worldwide.

Resolve corrections, disputes, and overdue balances

Raise an error with the issuer promptly and identify the invoice number, disputed line, and reason. “The invoice is wrong” leaves the supplier guessing; specifying the wrong rate, customer entity, service period, or quantity gives it something to check. Compare the charge with the agreement and work evidence, and distinguish a missing reference from a disagreement about what was supplied.

When correcting the invoice, preserve the connection between the original record and the change. Identify what was corrected and which version or adjustment the recipient should use. For an amount already invoiced or paid, follow the applicable correction process rather than silently overwriting the earlier charge. UK VAT credit- and debit-note requirements, for example, are set out in HMRC’s VAT guide. Keep any adjustment linked to the original invoice and reconcile its effect on the remaining balance or refund.

Before following up on an overdue amount, check the due date, recent receipts, partial payments, credits, and any unresolved dispute. Ask whether the customer has already initiated payment and request the reference if needed. Send a reminder quoting the original invoice and the outstanding balance; avoid creating a new, separately payable copy of the same charge.

If the balance remains unresolved, use the agreed escalation process and check the local rules before adding interest, fees, or taking recovery action. UK business late-payment guidance, for instance, describes remedies within a particular legal regime. It does not establish an automatic fee or collection entitlement for invoices in every country.

What changes when an invoice crosses borders?

Currency, fees, tax, and the amount the supplier receives

For a cross-border invoice, agree both the currency of the charge and the currency in which the supplier expects to receive payment. If they differ, establish who handles conversion and how the settlement amount will be determined. Confirm the accepted payment route, required account details and references, and responsibility for transfer or intermediary charges before the payment is sent.

The amount instructed by the payer can differ from the amount credited to the supplier. Intermediaries or the receiving bank may deduct charges; conversion can also affect the result. The supplier therefore needs to reconcile the actual receipt with the invoice rather than rely solely on the payer’s transfer confirmation.

For a hypothetical same-currency example, suppose the invoice requests USD 600 and the payer sends USD 600, but an illustrative USD 10 deduction leaves USD 590 credited. There is no currency conversion in this example, and USD 10 is not a typical-fee estimate. The figures simply show why “sent in full” and “received in full” can describe different amounts.

Caption: Hypothetical same-currency transfer: USD 600 sent − USD 10 deductions = USD 590 credited. This is not a typical fee. Whether the USD 10 remains owed depends on the agreement and applicable law. US Consumer Financial Protection Bureau

To resolve that difference, compare the transfer confirmation, the supplier’s receipt, and the agreed fee allocation. Ask the payment provider about an unexplained deduction. Whether the customer still owes the USD 10 depends on the agreement and applicable law; do not automatically mark the difference as either settled or overdue.

Tax and invoice-format checks are separate from the payment calculation. Establish which tax rules apply to the transaction, whether tax identifiers or particular invoice wording are needed, and whether the recipient requires a qualifying structured format. A foreign customer’s address alone does not settle the tax question. For example, HMRC’s UK VAT guidance for services requires analysis of the place of supply and tax liability rather than providing a general exemption for services sold abroad.

Invoice currency can also differ from the currency required for a tax disclosure. Under UK VAT invoicing rules, invoice amounts may be expressed in another currency, but the total VAT payable must be shown in sterling. Treat that as a UK-specific check, not a worldwide rule for foreign-currency invoices.

When an invoicing tool helps

An invoicing tool becomes useful when keeping documents, reminders, and payment records aligned is taking repeated manual work. Choose capabilities around the task you need to perform rather than assuming every product covers the whole transaction.

For a seller, look for consistent invoice creation and calculations, repeated billing, reminders, and a clear view of payments and remaining balances. A recurring billing feature can prepare each period’s invoice, but someone still needs to check the current scope, rate, customer details, and any adjustments. Reminder settings should reflect reconciled balances so the customer is not chased for an amount already paid or credited.

A buyer has different needs. Receiving an invoice into a system is only the start: look for ways to capture its details, connect it to the order and work evidence, route it for approval, and retain the resulting record. Structured data can reduce the need to re-enter invoice information, but it cannot establish whether the service was actually delivered or an account change was authentic.

For cross-border use, check whether the tool supports the currencies, invoice fields, and structured formats your transactions require. Test how it records a payment that differs from the invoice amount, including any deduction or conversion. If you need accounting integration, check what information is transferred and how invoice references, credits, and partial payments remain connected.

Set permissions for who can create or change invoices, approve charges, and update payment details. Keep review and payment authorization in the process: validation can flag missing or inconsistent fields, while correct inputs, supporting records, and independent verification still determine whether the request is ready to pay.