The Receipt and Invoice System Most SaaS Companies Underbuild

What you actually need to know

• Stripe's default receipt is not a tax invoice. They are different documents.
• B2B customers at any meaningful scale will ask for compliant invoices with VAT IDs and sequential numbers.
• Store invoice records in your own database. Do not rely solely on Stripe's API.
• Credit notes are the legal pair to refunds. If you skip them, your customer's accountant will ask.
• Build the invoicing system before the first enterprise deal. Not during it.

The core argument

The invoicing system is not a product feature. It is a financial document system. The distinction matters because teams treat it as a product feature and scope it accordingly. They ship the Stripe integration, generate receipts on payment, and move on. The system works until a customer opens a support ticket asking for a tax invoice with their company VAT ID on it.

Most B2B SaaS companies hit this moment between their tenth and thirtieth customer. The founder writes the invoice manually in Google Docs, sends it, and adds a ticket to the backlog. The ticket stays in the backlog for three months. The next customer asks for the same thing. The workaround scales until it breaks, usually at the first enterprise procurement process when someone asks for retroactive invoices for the past twelve months.

The fix is not complex. Stripe Billing handles the core of it. Sequential invoice numbers, VAT ID storage, PDF generation, credit notes on refund. The gap is in the details that Stripe does not handle for you: collecting tax IDs at signup, storing a copy of every invoice in your own records, generating the matching credit note when you issue a refund outside of Stripe Billing, and customizing the invoice template when an enterprise customer has format requirements.

Two weeks of engineering time, done once, solves the problem for the next three years of customer growth. The founders who do this early never think about invoicing again. The ones who defer it spend disproportionate support hours on a problem that was already solved.

What a compliant B2B invoice must contain

Required fields in most jurisdictions

A tax invoice needs: a unique sequential invoice number, the issue date, the seller's legal name and address, the seller's tax identification number, the buyer's legal name and address, the buyer's tax identification number if applicable, a description of the goods or services, the unit price and quantity, the subtotal, the tax rate applied and the tax amount, and the total amount due with the currency.

Stripe's default receipt covers some of these. It does not cover all of them. The gaps are the seller's tax ID, the buyer's tax ID, and the sequential invoice number in a format your jurisdiction recognizes.

Credit notes

When a customer is refunded in full or in part, the matching credit note is required to close the invoice in their accounts payable system. Stripe Billing generates this automatically for invoices. For charges that are not attached to a Stripe invoice, you need to generate the credit note yourself and deliver it alongside the refund confirmation.

Storage and retrieval

Every invoice your company issues should be accessible by invoice number, by customer, by date range, and by payment status. This is a basic accounting requirement and it is also what your accountant will need at tax time. Build the query interface before your accountant asks for it.

How much does it cost

What the invoicing system must handle

• Sequential invoice numbers that do not have gaps.
• Seller and buyer VAT or tax ID fields on every invoice.
• Custom billing address that may differ from the account address.
• PDF generation and delivery by email on payment and on demand.
• Credit note generation and delivery on refund.
• A local database copy of every invoice independent of Stripe.
• Retroactive invoice regeneration when a customer updates their billing details.
• Annual invoice with monthly line item breakdown for enterprise annual plans.

Expert opinion

The teams that build proper invoicing early are the teams that close enterprise deals cleanly. The teams that skip it lose deals in procurement or spend two weeks scrambling to produce retroactive invoices. The invoicing system is not glamorous work. It is also not optional work. It is the financial document layer that every paying customer relies on. Build it before you need it.

>

Yashveer Singh, founder of Yashveer Labs

How this played out on a real project

A B2B SaaS client was three months into their first enterprise pilot when the procurement team at the enterprise customer asked for VAT-compliant invoices for all charges to date, in the buyer's required format, with the buyer's purchase order number included on each document. The client was using Stripe's default receipts. They had twelve charges to account for.

We spent five days building a minimal compliant invoice system: Stripe Billing activation, VAT ID fields on the customer model, a PDF generation layer using a simple HTML template, and a backfill script that regenerated the past twelve invoices with the correct fields. Total engineering time was about thirty hours. The enterprise pilot closed.

The client then spent another three days building the self-service billing portal so that future customers could download their invoices without opening a support ticket. The full system, from zero to production, was about forty hours of engineer time. The alternative was losing a deal worth a significant amount of annual contract value.

For more on the adjacent billing work, see the subscription billing stack in 2026 and building an operations stack without an operations team.

Common mistakes

1. Treating Stripe receipts as tax invoices. They are not the same document.
2. Not collecting buyer VAT IDs at signup. You will need them and there is no good time to ask retroactively.
3. No local copy of invoice records. Your accountant and your auditors need records you can query without Stripe's API.
4. Skipping credit notes on refunds. The customer's accountant will ask and it will surface as a support ticket.
5. Sequential invoice numbers managed by Stripe only. If you ever migrate off Stripe, you lose the series.
6. One invoice template for all customers. Enterprise customers often have format requirements. Build template variation early.
7. No self-service invoice download. Every customer who cannot download their own invoice opens a support ticket.
8. Not testing the invoice system with an international customer scenario before launch.

A 30 day plan

1. Week one. Audit what Stripe currently produces. Identify the gaps against your jurisdiction's tax invoice requirements.
2. Week two. Enable Stripe Billing if not already active. Add VAT ID fields to customer records. Add seller tax ID to account settings.
3. Week three. Build or customize the PDF template. Add credit note generation to the refund flow.
4. Week four. Build the self-service invoice portal. Build the ops query interface for your accountant.

For more on the billing infrastructure that supports this, read the subscription billing stack in 2026 and workflow automation for saas a founders guide.