SaaS Invoice Template

Setup takes about 20 minutes. Download the .xlsx file and open it in Excel or Google Sheets. Start with the Customer List sheet — add each of your current customers with their billing contact, address, AP email, payment terms, plan tier, and any PO or cost center numbers they require. Then populate the Subscription Schedule with their billing dates and amounts. Once those two sheets are set up, the Invoice sheet will work with dropdowns instead of manual entry, and the schedule gives you a built-in billing calendar so nothing slips through.

To generate an invoice, go to the Invoice sheet and enter the invoice number, select the customer from the dropdown, and confirm the billing period. Fill in the applicable line items — subscription fee, seat count if seat-based, usage overages pulled from the Usage Log, and any professional services or one-time charges for that period. The totals block calculates subtotal, discount, and tax automatically. Export to PDF and send to the billing contact listed in the Customer List. For monthly recurring customers, most of the line items stay the same — it's usually just the usage overage row that changes.

After sending, log the invoice in the Invoice Log. Set the status to Outstanding, then update to Paid when payment clears or Overdue if it doesn't arrive by the due date. For SaaS companies, the most important monthly discipline is confirming the Invoice Log accounts for every customer on the Subscription Schedule before closing the month — missed invoices at a 20-customer scale are easy to catch; at 100 customers they become a revenue leak. Most finance teams do a 10-minute reconciliation on the last business day of each month to confirm the counts match.

SaaS invoicing looks straightforward until you're managing 50 customers on different plans, billing cycles, and pricing models. Some customers pay monthly; others are on annual contracts invoiced monthly. Some are on flat-rate subscriptions; others have seat-based or usage-based components that change every period. A few enterprise customers have strict AP requirements — PO numbers, cost center codes, specific invoice formats — and will hold payment until the invoice matches exactly what their system expects. Using a generic invoice template for this creates errors: missed line items, wrong amounts, invoices sent to the wrong contact, and delayed payment from formatting issues.

The SaaS billing structure that works is one that separates line item types rather than mixing them into a single undifferentiated table. Subscription fees are fixed and predictable; usage overages require calculation from a separate log each period; professional services may be hourly or milestone-based. Keeping these in distinct sections with their own subtotals makes the invoice readable for the customer and auditable for your own finance team. It also makes disputes easier to resolve — when a customer questions an overage charge, you can reference the Usage Log and show exactly which billing period and usage figure the charge is based on.

The operational discipline that separates SaaS finance teams that close cleanly from those that chase invoices is a monthly billing checklist. Run through the Subscription Schedule at the start of each billing cycle, identify every customer due that month, generate invoices in order, and log each one in the Invoice Log before moving to the next. Review the log at month-end to confirm everyone on the schedule was invoiced and no outstanding balance is more than 30 days old. This sounds basic, but at a 30-60 customer scale without a dedicated billing system, it's the process that prevents the common SaaS revenue leak: recurring customers who weren't invoiced because they fell off someone's mental checklist.