Billing operations and reporting

The operations workspace separates active subscriptions, usage exceptions, billing candidates, issued invoices and collection cases. An active subscription may have a draft next invoice and an older unpaid invoice at the same time. A single status badge cannot stand in for all of those facts.

Billing Operator can find the next action and its responsible person without treating an unfinished calculation as a failed payment. Billing Manager reviews financial exceptions and submitted runs. Support receives the customer context needed to explain dates and documents, with payment tokens, integration secrets and restricted financial controls masked.

Recurring revenue indicators need a documented basis. Normalise the accepted recurring commitment to the reporting interval and identify whether usage, one-time charges, discounts and suspended subscriptions are included. Preserve the as-of date and price version used. An operational monthly-recurring indicator does not establish recognised accounting revenue.

Customer additions, cancellations and plan changes can then explain movement between periods on the same basis. Report currencies separately unless an approved reporting conversion is configured. A total that combines unlike currencies or changed inclusion rules can look precise while answering the wrong question.

Invoice reports use issued net and tax amounts with approved issued credits. Collections use verified settled payments and confirmed refunds. The difference between the two is explainable through open balances and unresolved payment outcomes. Draft invoices and payment authorisations stay outside completed financial totals.

Age a collectible balance from the agreed due date using the report’s as-of date. A later credit or payment belongs to its observed effective history; a historical snapshot should not quietly adopt today’s state. Reconcile the original invoice number and provider instruction when a customer disputes the reported balance.

Usage reports connect the billed quantity to accepted source events, aggregation and the plan’s included allowance and tiers. A late event can appear as an adjustment in a later financial review without rewriting the quantity on an earlier issued invoice. Preserve that relationship in the reporting drill-down.

A new price plan affects customers through the accepted change process. Compare the old and new plan versions and effective dates when explaining increased billing. Separate price movement from greater consumption or a different contracted quantity. The explanation should identify the source of the change instead of attributing every increase to usage.

A Customer sees only their account’s documents and permitted usage detail. Finance Viewer can inspect authorised aggregate financial reports without gaining invoice-edit or provider-token access. Exported data and API responses follow the same customer and seller-entity scope.

Before rollout, reconcile a complete subscription interval and a correction across plans, events, invoices, credits and payments. Test a missing tax response, duplicate provider event and cancelled subscription with unpaid history. These checks show whether the configured product can explain its own financial state; a generated dashboard alone cannot establish that result.

• Subscription Status Board — Review the work and supporting records for this module.