What is an Invoice?

An invoice is a formal document a seller sends to a buyer requesting payment for goods delivered or services performed. It records what was sold, at what price, on what terms, and creates the legal basis for the payment obligation. Without one, a transaction exists commercially but not in the books as there's nothing to recognise as revenue and nothing to collect against.

In B2B billing, invoices are the output of the entire revenue process: contract terms translated into a document the customer's accounts payable team can process and pay. The accuracy of that translation is where most billing problems start. A contract might specify a minimum commit of $50,000 with usage billed above that threshold, but if the invoice doesn't reflect the actual consumption data, the customer disputes it and payment delays. 16% of finance professionals rate invoice management as one of their most time-consuming tasks and that's before accounting for the disputes, corrections, and chasing that come with getting invoices wrong.

What an Invoice Must Contain

The legal requirements for invoices vary by jurisdiction, but most B2B invoices share a common structure. Missing any of these fields creates either a compliance problem or a practical one, as the buyer's AP team can and should reject or delay an invoice that doesn't match their purchase order.

See more about what a VAT invoice should contain, according to the EU.

For usage-based and hybrid pricing models, the line item section becomes significantly more complex. A single invoice might contain a flat subscription fee, a metered usage charge calculated from consumption data, a volume discount applied to the total, and a credit from the previous period. Each of these needs its own line, clearly described, or the customer's finance team will spend time reconciling rather than approving.

Invoice Types

Not all invoices work the same way, and the billing infrastructure required to generate them differs substantially.

Standard invoice. A one-time charge for goods or services delivered. Straightforward to generate; the complexity is in getting the line items right.

Recurring invoice. Generated automatically on a schedule for subscription services. The billing system needs to know which customers bill on which cycle, handle proration for mid-cycle changes, and apply any pricing changes that took effect since the last billing period. See subscription management and recurring payments for how this works operationally.

Usage-based invoice. Generated from metering data rather than a fixed schedule. The invoice amount isn't known until consumption is measured, which means the billing system must ingest metering events, aggregate them according to the pricing model, and produce an invoice that accurately reflects what was consumed. See usage metering and usage-based pricing.

Credit note. A negative invoice, meaning issued when a customer was overcharged, when a refund is owed, or when a contract is cancelled mid-period and a credit applies. Credit notes reduce the amount outstanding rather than adding to it. Without a clean credit note process, billing systems accumulate errors that compound over time.

Pro forma invoice. Sent before delivery to confirm pricing and terms. Common in enterprise sales where the buyer needs internal approval before committing.

Self-billing invoice. The buyer generates the invoice on the seller's behalf, typically in marketplace or procurement contexts. See self billing.

The Invoice-to-Cash Process

Issuing an invoice is the start of a process, not the end of one. The invoice-to-cash cycle covers everything from invoice generation to payment received and revenue recognised, and failures at any stage create cash flow delays.

Generation. The billing system calculates what is owed based on contract terms, usage data, and applicable discounts. For companies with complex pricing — hybrid models, volume tiers, multiple entities — this calculation is where errors originate. See billing engine for how this is handled at the infrastructure level.

Delivery. The invoice reaches the buyer via email, customer portal, or e-invoicing network. In many jurisdictions, e-invoicing is now legally required for B2B transactions. See e-invoicing.

Approval. The buyer's AP team matches the invoice against their purchase order. Discrepancies at this stage — wrong PO number, prices that don't match the contract, missing tax details — trigger disputes and delay payment.

Payment. The buyer pays via bank transfer, card, or ACH. Payment terms determine when this is due: Net 30 means 30 days from invoice date, Net 60 means 60 days. The gap between invoice date and payment receipt is Days Sales Outstanding (DSO) — a key metric for finance teams managing cash flow.

Reconciliation. Finance matches the payment received against the open invoice in the accounts receivable ledger. For companies using a payment gateway or payment processor, this means matching bank settlement records against billing system records. Manual reconciliation is where month-end close cycles stretch to two weeks.

Revenue recognition. The invoice triggers a revenue recognition event — or more accurately, the delivery of the goods or services does, and the invoice documents it. Under ASC 606 and IFRS 15, revenue is recognised when performance obligations are satisfied, not when the invoice is sent. See ASC 606 and IFRS 15.

Common invoice accuracy issues

A single invoice for a straightforward SaaS subscription is not a hard problem. The difficulty arrives when the same billing system needs to handle enterprise contracts with custom rate cards, usage-based components, multi-currency charges, mid-cycle amendments, and consolidated statements for customers with multiple subsidiaries.

The companies that get this wrong typically have pricing logic scattered across their product code, CRM, and billing system, with a spreadsheet in the middle reconciling the gaps. The invoice that gets sent to the customer reflects the spreadsheet, not a single authoritative source of truth. When the contract changes, someone has to update the spreadsheet manually. When they miss an update, the invoice is wrong, and the dispute takes longer to resolve than it would have taken to fix the process.

Companies processing serious invoice volume (multiple products, enterprise customers, different geographies) need a billing engine that treats every contract term as a structured input, not a freeform note in a deal record. The invoice is only as accurate as the data model behind it.