Accounts receivable for SaaS: Invoices, aging, and collections

Updated 2026-09-24

Accounts receivable is money a customer owes when your right to payment is unconditional apart from the passage of time. In a SaaS business, the daily work usually starts with an invoice and ends with a payment, credit, or write-off.

A clean receivables process connects the contract, invoice, usage records, and cash receipt. It also shows who will resolve an unpaid balance. Keep the supporting documents with each transaction; the IRS recordkeeping guide explains their role in your books and tax returns.

Accounts receivable vs. revenue and deferred revenue

These balances answer different questions.

Balance	Question
Accounts receivable	What does the customer owe us?
Revenue	What service have we earned revenue for?
Deferred revenue	What billed or paid service do we still owe?
Cash	What money have we received?

A valid invoice for an annual subscription can create a receivable before you deliver the full year of service. Revenue then follows the service obligations, not the collection date.

An unbilled amount is not automatically a receivable. If your right to payment still depends on another condition, it may be a contract asset. Our revenue recognition guide explains that distinction.

How recurring billing changes collections

A customer can owe several invoices while holding a credit or making a partial payment. Keep one customer balance with links to each invoice, receipt, credit, and dispute.

Billing model	What the receivables process needs
Monthly card subscription	Failed-payment follow-up and a way to match refunds and processor payouts
Annual invoice	Purchase order and vendor approval checks before renewal, plus an agreed payment date
Subscription plus usage	A usage statement, service period, and owner for charge disputes
Wire, ACH, check, or reseller payment	A way to match receipts outside the billing tool to the right customer and invoices

Annual renewals can cause a large receivables balance even when customers pay on time. Plan collections around renewal dates and customer payment runs, and distinguish a timing change from a rise in overdue debt.

Apply cash and credits to the right balance

Use the customer's remittance instructions to match a payment to invoices. If no instructions arrive, request them or follow a documented policy that fits the contract. Keep an unmatched receipt visible as unapplied cash until you resolve it.

For an illustrative example, a customer owes two invoices of $1,000 and $800. A $1,200 wire does not close both invoices. If the customer says it covers the first invoice and part of the second, apply $1,000 and $200 respectively. The remaining balance is $600.

A credit memo can reduce that balance, but it is not a cash receipt. Define who can approve credits and refunds, which invoice each adjustment affects, and when unused credits carry forward. Preserve the link between the original charge and the adjustment.

From invoice to payment: An example

Assume a customer owes $600 for API usage already delivered. This is an illustrative example without tax or fees.

Record the $600 receivable and earned revenue, if neither has already been recorded.
Send the invoice with the usage period, rate calculation, due date, and payment details.
Record a $600 payment against that invoice when it arrives.
Reconcile the receipt with the bank or payment processor settlement.

Do not record revenue again when the customer pays. If you accrued the revenue before issuing the invoice, move the balance to the right billed account without recording it twice.

For an invoice layout, use our B2B SaaS invoicing guide.

Build an aging report you can act on

Age open invoices from their due date, and keep not-yet-due balances separate. Choose aging bands that suit your terms.

Illustrative status	What to check	Next action
Not due	Invoice reached the right contact	Fix delivery or purchase order issues
1–30 days overdue	Payment status and any dispute	Send a clear reminder and confirm a payment date
31–60 days overdue	Reason for delay	Assign an owner and resolve the issue
More than 60 days overdue	Collection outlook and contract rights	Review escalation and expected credit losses

The bands are an internal policy choice, not a legal collection schedule. An unpaid invoice is not always a refusal to pay: a missing purchase order or usage dispute may block the customer's approval.

Keep disputed balances visible. Moving an invoice out of the report does not resolve it.

Set a collection schedule

Choose a cadence that fits the contract and customer. One sample policy sends a reminder before the due date, follows up when payment falls due, then assigns a personal follow-up after seven days and an escalation after fourteen. Any service hold needs its own contract check and approval.

For each overdue invoice, record the AP contact, reason for delay, promised payment date, next action, and owner. A missing purchase order needs a different response from a disputed usage charge. Confirm that vendor onboarding is complete before sending repeated payment reminders.

A practical monthly reconciliation

Start with the prior closing receivables balance. Add invoices and other receivable entries. Subtract payments, credits, and write-offs. The result should match both the customer ledger and the general ledger. Use separate receivable, allowance, and clearing accounts in your SaaS chart of accounts.

Investigate differences such as:

A payment applied to the wrong customer or invoice.
An unapplied receipt.
A refund or dispute recorded only in the payment processor.
A credit memo that did not reach the ledger.
Currency differences.
Revenue recorded twice when unbilled usage became an invoice.

Reconcile processor settlements separately. The bank payout may be net of fees and refunds, so it may not equal the sum of customer payments.

Handle credits, disputes, and bad debts separately

A billing error may require a credit and a corrected invoice. A valid invoice that a customer cannot pay raises a credit-loss question. Those are different events.

Record who approved each credit or write-off and why. Preserve the original invoice and its link to the adjustment. Apply your accounting policy for expected credit losses; do not wait for every old invoice to become certain to fail before reviewing the allowance.

Tax deductions for bad debts follow their own rules. A book write-off does not, by itself, establish a tax deduction. Check the IRS bad-debt guidance before treating the book entry as a deduction.

What should the team track?

Track the overdue balance, the age of that balance, open disputes, and the next action by owner. If you use days sales outstanding, keep the calculation consistent and explain large advance billings or seasonal changes.

A collection target should not encourage the team to hide disputes with credits or change due dates after the fact.

When to formalize the process

Set up a shared customer ledger and a weekly collection review once net terms, recurring credits, or payments outside one processor make balances hard to track. Assign one owner for payment matching and one for each open dispute.

A small team can start with consistent invoices, an aging report, and a clear action list. Add systems as the work grows; a new billing tool will not fix unclear payment or credit rules.

Common questions

Do paid monthly subscriptions create accounts receivable?

They can create a short-lived receivable between billing and payment. The exact entries depend on the billing and accounting setup. Failed payments can leave an open balance that needs review.

Should we stop service for late payment?

Follow the contract and your stated policy. Confirm the facts and the right contact before taking action. Finance, support, and the account owner should use the same status.

Does an invoice prove that revenue is earned?

No. Billing, service delivery, and payment can occur on different dates. Review the contract and recognition policy before treating the full invoice as current revenue.