Billing & Payment Workflows
Last reviewed: 16 November 2026
Invoice generation
| Trigger | New subscription, renewal (lead time or boundary), plan/add-on change, cancellation fee, custom invoice |
| Rules | Each charge lands on exactly one invoice; due date = invoice date + net term days |
| Records changed | Invoice, invoice items, payment request |
| Errors | An invoice for the same order is never created twice, even if a step is retried |
Usage to invoice
| Trigger | The period boundary (renewal date) |
| Input | Events with eventType, subscriptionId, accountId, quantity, eventTimestamp, properties |
| Rules | Duplicate eventId rejected; usage accepted for an ended term during the Late usage window; package rounding applies to the period total |
| Errors | Missing required fields return 422 |
Detail: Usage Billing Lifecycle.
Payment collection
Failed payment recovery (dunning)
| Trigger | A failed debit |
| Rules | Before each retry BillHive checks whether the customer already paid; the subscription is In Dunning and can only be cancelled immediately |
| Records changed | Dunning case, payment attempts, invoice status, subscription status |
| Notifications | Payment Failed, Reminder, Urgent Notice, Account Restricted, Account Suspended, Final Notice, Cancelled (Non-Payment), Win-Back |
Detail: How Dunning Works.
Refund processing
Detail: Offline Refunds.
Subscription to revenue reporting
Formulas and examples: Revenue Metrics.