Subscription Billing manages the complete recurring-revenue lifecycle. It holds a structured product catalogue and one or more price books, so the same offering can carry different prices by market, segment, currency or contract. Pricing is expressed across the full range of commercial models: flat recurring fees, tiered and volume pricing, pure usage-based rates, and hybrid plans that combine a committed platform fee with metered overage. Plans support multiple billing frequencies, minimum commitments, entitlements, discounts, credits and free trials.

Consumption flows in as metered events, which the rating engine converts into charges against the applicable price. The module prorates cleanly whenever a subscription starts, stops or changes mid-cycle, so upgrades, downgrades, quantity changes, plan swaps and cancellations all resolve to the correct charge or credit without manual adjustment. On each billing date it assembles invoices, applies taxes, and collects payment through stored payment methods, retrying intelligently on failure and driving structured dunning sequences when collection lapses. Every charge carries the revenue-recognition treatment that lets finance close the books with confidence.

At the centre of the model sits the subscription: a durable agreement that a given customer will receive a defined set of offerings, at agreed prices, over a period of time. A subscription binds a customer account to one or more plans drawn from the catalogue, and it carries a life of its own, moving through activation, changes, renewals and eventual cancellation while preserving a full history of every version it has held.

A plan describes what is being sold and how it is charged. It resolves, through the active price book, to concrete prices that may be fixed, graduated by quantity, or driven by measured consumption. Where consumption matters, usage arrives as a stream of timestamped events attributed to the subscription; rating turns that raw usage into money by applying the relevant price, honouring included allowances, tiers and caps before any overage is charged.

Billing periodically crystallises these obligations into an invoice, an immutable financial statement of what is owed for a period, against which payments, credits, refunds and adjustments are recorded. Running alongside the invoice is the revenue view: each charge is decomposed into performance obligations and scheduled for recognition independently of when cash is billed or received. The relationships are what give the model its power. A customer holds many subscriptions; a subscription accretes usage and versions over its life; an invoice reflects the state of subscriptions at a point in time; and revenue schedules trace back through every one of these so that any recognised figure can be explained to its source.

The defining workflow is order to cash. A new subscription is created from a catalogue offer, priced through the applicable price book, activated, and from that moment it accrues charges and, where relevant, usage. On each cycle a billing run sweeps every subscription due, computes fixed and metered charges, applies proration for any mid-cycle events, produces invoices, and initiates collection. Successful payments reconcile automatically against open invoices; failures enter retry and dunning.

Change management is continuous rather than exceptional. Upgrades, downgrades, add-ons, quantity changes and cancellations are applied at any point in a cycle, with the module calculating the precise credit or additional charge and adjusting future invoices accordingly. Renewals run automatically at term end, respecting price uplifts and renewal terms, and cancellations settle any final usage and outstanding balance.

Dunning is a first-class workflow: configurable sequences of retries, reminders, grace periods and escalation govern how the organisation pursues failed payments, with the option to suspend or terminate service when collection is exhausted. Throughout, credit notes, refunds and manual adjustments provide controlled routes to correct billing without compromising the integrity of issued invoices.

Subscription Billing implements revenue recognition to the ASC 606 and IFRS 15 five-step model. Each contract is decomposed into distinct performance obligations, and the transaction price is allocated across them on the basis of standalone selling price, with discounts and variable consideration apportioned correctly. Recognition then follows the pattern of each obligation: recurring platform access is recognised rateably over the service period, usage is recognised as it is consumed, and one-off elements are recognised at the point control transfers.

The engine maintains a revenue waterfall that projects and tracks recognised, deferred and unbilled revenue across every future period, so finance can see, for any month, exactly how much revenue will be recognised and from which obligations. Contract modifications are handled to the standard, treated as either a separate contract, a prospective change, or a cumulative catch-up depending on their nature. Deferred revenue and contract asset and liability balances are maintained continuously and reconcile to the invoiced and recognised positions.

Controls run throughout. Invoices are immutable once issued and corrected only through credit notes; every price, rate and recognition decision is captured with its inputs; and a complete audit trail records who or what changed a subscription, when and why. Tax is determined per line and per jurisdiction, and multi-currency contracts are billed and recognised in their transaction currency with disciplined translation for reporting.

Subscription Billing does not operate in isolation; it is wired into the shared spine of Nashua 360. It draws the parties it bills from the customer master data and the things it sells from the product master data, so accounts, contacts, entitlements and catalogue definitions stay consistent with the rest of the suite rather than being re-keyed. Commercial terms agreed in the sales and quoting process flow straight into subscriptions without re-entry.

Its deepest integration is with Accounting and Control. Recognised revenue posts as journal entries to the general ledger on the correct periods, invoiced amounts create and clear accounts receivable, and collected cash reconciles against those balances, so the subledger for recurring revenue is always in agreement with the financial statements. Deferred revenue, contract assets and contract liabilities are carried into the ledger with full traceability. Collections and cash application share the receivables and payments view with the rest of finance, and billing data feeds the suite's analytics and reporting layer for metrics such as recurring revenue, retention, churn and expansion. The result is one continuous chain from a priced offer to a closed set of books, with no seams where reconciliation breaks down.

Nashua 360 treats AI Workers as first-class users, and Subscription Billing is built for them. Finance and revenue teams query the module conversationally, asking for a customer's recognition schedule, the drivers of a month's deferred revenue movement, or the accounts most exposed to churn, and receive answers drawn directly from live billing data with the underlying records cited. Workers also execute action: they draft plan changes, prepare credit notes, assemble a billing run for review, and construct dunning outreach, all within the module's permissions and controls.

AI Workers watch the recurring-revenue estate for anomalies and exceptions: unexpected usage spikes, subscriptions billing outside their expected range, revenue that fails to reconcile, or collection patterns that signal risk, raising these before they reach the ledger. They extract structured terms from incoming order documents and contracts to seed or amend subscriptions, and they provide decision support around pricing, renewal strategy and revenue treatment for complex modifications. Crucially, a Worker can serve as a named approval or review node in a workflow: validating a revenue-allocation judgement, signing off a high-value credit, or gating a billing run against the close calendar, with its reasoning recorded in the same audit trail as any human action.