Invoice

An invoice is both a payment request and a legal record. In most jurisdictions it must carry specific content to be valid for tax purposes — the issuing entity’s details and tax registration, a sequential number, the date, the customer’s details, a line-item breakdown, the tax applied, and the total due.

Because it is a legal document, an issued invoice generally cannot be edited. Corrections happen through a credit note and a reissue.

What makes B2B SaaS invoicing harder than it looks

• Sequential numbering per entity. Each legal entity needs its own unbroken sequence — see multi-entity.
• Mixed charge types on one document. A hybrid contract puts an annual platform fee, monthly usage, and prorated mid-term changes on invoices that must still be legible.
• Tax by jurisdiction. Rates and rules vary by where the customer is, what is being sold, and whether reverse charge applies.
• Purchase order references. Many enterprise customers will not pay an invoice that does not quote a valid PO number, and the PO may have a value ceiling that a usage overage breaches.
• Consolidated versus per-subscription. A customer with six subscriptions usually wants one invoice, which requires the billing system to group across subscriptions and still show what each line relates to.

The invoice is where every upstream error surfaces

Nothing exposes a broken quote-to-cash process faster than the invoice. A discount that never made it from the quote to the subscription, a proration calculated on stale data, a timed discount that should have expired and did not — the customer sees all of it, in writing, and asks about it.

Disputed invoices delay payment, consume finance and account-management time, and damage trust disproportionately to the amounts involved. Invoice accuracy is, in practice, a measure of how well the systems upstream of it agree with each other.