Subscription billing and revenue testing

What subscription billing testing covers

A billing defect repeats on every renewal of every affected subscriber. We compute expected invoices, credits, retries, and revenue entries independently of the billing engine and compare them with its output.

Plan changes and proration

Worked example on a day basis, for a monthly period from 1 July to 1 August (31 days): a customer on a 31.00 USD plan upgrades to 62.00 USD at 00:00 UTC on 21 July. The 11 unused days give a credit of 11.00 USD and a charge of 22.00 USD, so 11.00 USD is due. A downgrade back to 31.00 USD at 00:00 UTC on 26 July then credits 12.00 USD for the 6 remaining days and charges 6.00 USD, a net credit of 6.00 USD.

The suite also covers seat changes, trial conversion, monthly to annual switches, changes at the exact period boundary, and changes whose customer-local date differs from the UTC date. Rounding modes and divisors are tested with financial calculation testing; the prorated billing testing guide lists the test data.

Article 219 of the VAT Directive treats any document that amends and refers specifically and unambiguously to the initial invoice as an invoice, and Article 90(1) reduces the taxable amount where the price is reduced after the supply, under conditions that Member States determine. We test that each proration credit note references its original invoice and reverses tax at the rate the client's tax specification assigns.

Usage metering

The checks replay a synthetic corpus with a known total per customer and period, for example 10,000 events in one monthly period, of which 200 repeat an idempotency key already sent. The expected billed quantity for that period is 9,800. The corpus also includes events timestamped before period close and delivered after it, events near midnight in non-UTC time zones, aggregation rules (sum, maximum, last value) and meter resets on a mid-period plan change.

Under the practical expedient in paragraph B16 of IFRS 15, an entity whose right to consideration corresponds directly with the value of its performance completed to date may recognise revenue in the amount it has a right to invoice. For such an entity, a metering error moves straight into reported revenue.

Dunning and card retry schedules

Retry branches follow the Visa Category 1 and Category 2 reattempt rules set out on the billing segment page, and a merchant must not reattempt with the same account number after response code 14.

We map every response code the processor returns to a branch and count retries across the 30-day window, including retries customers start in the portal. We also test that an updated payment method stops the old schedule, that the dunning email matches the invoice state, and that the final action (cancel, pause, or mark unpaid) follows the policy. The dunning testing guide gives the schedule cases.

Cancellation and renewal notices

The cancellation and notice rules we test against, including 15 U.S.C. 8403, California Business and Professions Code 17602, and the status of the FTC Negative Option Rule after the Eighth Circuit vacated its October 2024 amendments on 8 July 2025, are listed on the billing segment page.

We test that cancellation stops scheduled renewals and pending dunning retries, and that each notice job selects the right subscribers on the right date.

Revenue recognition handoff

Under IFRS 15 paragraph 106, a contract is presented as a contract liability when the customer pays, or payment is due, before the entity transfers the service. On a 1,200.00 USD annual plan invoiced and paid on 1 January and recognised monthly on a straight-line basis, the export shows 100.00 USD of revenue and a 1,100.00 USD contract liability at 31 January. Paragraph 21 sets how a contract modification that paragraph 20 does not treat as a separate contract is accounted for. The reconciliation ties each invoice line, credit note, and refund to its service period and to the recognised and deferred amounts. Ledger postings are covered by ledger and reconciliation testing.