The billing mistakes that quietly cost SaaS companies revenue

01.1. No automated retry for failed cards

A card payment can fail for reasons that have nothing to do with the customer's intent: a temporary hold, a limit reached, a network blip at the bank. A single attempt gives up too soon.

Without automated retries, someone must notice the failure and chase it. Usually no one does. The account lapses, and the customer is counted as churn.

What to do: classify failures into soft (try again) and hard (needs a new card). Retry soft failures on a schedule spaced over several days. Stay within your gateway's retry rules.

02.2. Expired cards that never get updated

Cards expire on a date everyone knows in advance. Yet many companies wait for the payment to fail before they say anything.

What to do: use your gateway's card updater service if it is offered, and send a prompt before the expiry month with a one-click way to update. An in-app banner works better than email alone, because customers are already in your product.

03.3. Discounts that never expire

A discount offered to close a deal or save an account has a way of becoming permanent. Two years later, a customer pays an introductory rate on a product that has doubled in value.

What to do: give every discount an end date and an owner. Review the list each quarter. If a discount should continue, renew it on purpose.

04.4. Usage that is not billed, or billed late

If you charge for usage, anything that slips through the metering is free. Events get dropped, services forget to report and a backlog delays the invoice by a cycle. Late billing also surprises customers, who then dispute it.

What to do: reconcile event counts against invoiced quantities each period. Alert on large gaps. Decide how to handle late events and tell customers.

05.5. Wrong tax handling

Charging the wrong tax rate, or none, is a compliance and revenue problem. If you under-collect, you may owe the difference yourself. If you over-collect, you face refunds and unhappy customers. Rules vary by place and product type, and they change.

What to do: use a tax engine rather than a spreadsheet. Store tax details for each customer. Have your finance or tax advisor confirm the setup. We do not give tax advice, but we can make sure the system applies whatever rules you adopt.

06.6. Manual invoices that get missed

Custom contracts often live outside the billing system. Someone creates an invoice by hand each quarter. A busy week, a holiday or a staff change, and the invoice never goes out.

What to do: move recurring custom deals into the billing system as scheduled invoices. For anything that must stay manual, create a tracked task with a due date and a second person who checks it.

07.Why these leaks persist

None of these mistakes is hard to understand. They persist because each one sits between teams. Failed payments belong to billing, but the customer relationship belongs to support or sales. Discounts are agreed by sales and tracked by finance. Usage is produced by engineering and billed by finance. Tax belongs to finance, yet depends on product data engineering holds.

When a problem sits between teams, each team assumes another is watching. Nothing alerts anyone, because the loss is a payment that did not happen, not an error that was thrown. There is no ticket, no outage and no angry customer. The cost shows up only if someone compares expected revenue to actual revenue.

That comparison is the single most useful habit. Each month, take the list of active subscriptions and what they should have paid, and compare it to what arrived. The gap is your leakage. Break it down by cause and the six items above will appear.

08.What recovery looks like in practice

Recovery is attractive because the customer has not chosen to leave. A good recovery flow is calm and specific.

• A failure arrives and is classified: temporary, or needs a new card.
• Temporary failures are retried on a spaced schedule, without any message at first.
• If retries fail, the customer sees a clear banner in the product and gets a short email with a secure link to update their card.
• A second reminder follows a few days later. It states the date access will change.
• After a grace period, the account is paused, not deleted, and the customer can restore it in a click.
• Every step is logged, so you can see which messages actually recover payments.

Two details matter more than they seem. First, the update link should not need a login or a support ticket. Second, the tone should assume an honest mistake. Most failures are not a customer refusing to pay.

Keep a record of the recovery rate by failure reason. If one reason recovers poorly, change that flow only. Test one change at a time against a small group, so you know what worked.

09.A simple audit you can run this month

• Pull last quarter's failed payments. Count how many were never recovered.
• List the active discounts and sort by age.
• Compare usage events to invoiced usage for one full period.
• Check a sample of invoices for correct tax.
• List every customer billed by hand and confirm each invoice was sent.
• Find cards expiring in the next sixty days.

10.Common mistakes when fixing this

• Starting with pricing changes. Fix leakage first. It costs customers nothing.
• Fixing everything at once. Start with failed payments, then discounts, then the rest.
• Not measuring. Record the recovery rate before and after each change.
• Treating billing as finance's problem alone. Engineering, support and finance each hold part of the answer.

11.How to keep it fixed

An audit finds leaks once. To keep them closed, give each one an owner and a number. Finance owns the monthly expected-versus-actual comparison. Billing owns the failed-payment recovery rate. Sales owns discount end dates. Engineering owns the usage reconciliation. Put the four numbers on one page and review them monthly for fifteen minutes. When a number moves the wrong way, you will see it within a cycle instead of a year.

Do not wait for a perfect dashboard. A spreadsheet that compares expected and actual payments for one month will show you where to look, and that is enough to begin.

Pick the first fix by size and ease. If failed payments are the largest gap, start there. If one old discount covers a big account, start with a conversation instead of code.

Share the first month of results with the whole team. Showing that a recovered payment or an expired discount brought back real money is the best way to keep the audit alive.

12.Where to start

Start with failed payments. They are measurable, the fix is well understood and the revenue is already yours. Then work down the list.

Brandsmashers builds the retry logic, reminders, reconciliation jobs and reporting that close these gaps, and we can run the audit above with you before any build begins. If you want a second pair of eyes on your billing, book a call and we will go through it together.