In this guide 6 sections
Test six things before you commit. Check plan changes with proration, trial and renewal rules, retries after failed card payments, tax on each invoice, several currencies and matching of every payment to its invoice. Trial each with a real customer’s history, because the vendor’s demo data hides awkward cases that your own billing history will expose.
Plan changes and proration are where demos hide the truth
Every tool can sell a plan. Few handle a customer who upgrades on the 19th, adds a seat on the 24th and drops one on the 27th, so make the vendor run it live. Test the trial cancelled on day thirteen of fourteen: it should leave no invoice, no card charge and no half created subscription behind.
Check the credit line on the next invoice, which should show the unused part of the old plan and the new charge in words a customer can follow. A downgrade mid-cycle should produce a credit note that names the original invoice, so your accountant can match the two without opening either file.
Ask: now or at renewal? Both exist. Pick one. Whichever you pick, the tool should apply it to every plan the same way and show the rule on the invoice so support staff can quote it.
- Upgrade, downgrade and seat change in the middle of a cycle
- Credit shown as a separate line, not buried in the total
- Annual to monthly switches and the reverse
- Pause, resume, cancel at period end and cancel now
Trials and renewals follow rules you must be able to edit
A trial needs an end date, a card-on-file rule and a reminder before the first charge, and the tool should support both card-up-front and no-card trials.
Renewals need notice, so ask whether the tool reminds the customer before an annual renewal and lets you set the lead time. Look at price changes as well, because an existing customer may need to stay on an old rate while new ones pay the new rate.
Silence is a case too. A customer who never replies still needs a defined outcome, either auto-renew or lapse, set per plan and shown in the reminder email so nobody is surprised.
Failed payments need a retry plan, not a panic
Cards expire. Banks decline. Mandates lapse. A good tool retries on a schedule you set, emails the customer a link to update the card, and moves the account through active, past due and suspended.
Ask what the customer sees. A sudden lockout loses accounts. Gentle warnings keep them.
Check that every retry and its result is logged against the invoice, because your finance lead will want that trail at month end when the reconciliation is due. The suspended stage should keep the customer’s data readable for a set period, so a late payer can export their records and a returning payer loses nothing.
- Retry schedule you can change by plan or region
- Email and in-app reminders in your own wording
- Grace period before access is limited
- A manual way to mark a bank transfer as paid
Tax and currency must be right on every invoice
Tax rules depend on where the customer sits, so ask which jurisdictions the tool covers, whether it validates registration numbers, and whether credit notes carry the same details. Let your accountant judge the format. Watch rounding on invoices with many per seat lines, where a tiny drift on each line can leave a total that disagrees with the ledger.
For several currencies, check which exchange rate applies, on which date it is fixed, how rounding works and how gains or losses on settlement reach your ledger.
Ask for a sample invoice per country. Read each one.
Every payment must find its invoice
Matching is dull. It also saves the most hours. A card payment should close its invoice unaided, a bank transfer carrying a reference should match too, and a part payment should leave a visible balance.
Ask for a reconciliation report that lists unmatched payments and open invoices and exports to your accounting package in the format your accountant already uses. Finance should also be able to filter by payment method, so card settlements and bank transfers can be checked against the bank statement on separate days.
Before signing, import ten real customers. Bill them through one full cycle in a trial, then count the invoices someone had to fix by hand and the payments someone matched manually.
Subscription billing vendor scorecard
One page, eight rows. Rows run from proration and trials to tax, currencies, matching and export, and the columns hold the test scenario, the vendor’s answer, pass or fail, and hand fixes. A header lists plans and currencies.
Open a blank worksheet to printQuestions owners ask
Do we need a billing tool or can the payment gateway do it?
A gateway collects money and may offer recurring charges, but once you have proration, several plans, tax invoices or multiple currencies, you will need billing logic on top. Test the gateway’s limits first.
How should we handle customers who pay by bank transfer?
Issue an invoice with a payment reference, match the transfer on arrival, and check that the tool lets you record a manual payment that clears past due.
Can we change plans and prices after launch?
Yes. Decide first whether existing customers keep the old rate or move at renewal, then store the agreed price against each customer record so later changes cannot rewrite history.
What should we ask about moving our data later?
Ask whether you can export customers, plans, invoices, credit notes and payment history in a standard file such as CSV, with original currency amounts intact. Being unable to leave is a risk.