Billing Operations Overview
Billing operations are the recurring tasks that turn product configuration and customer contracts into invoices, collections, credits, and reporting.
Floatless separates setup from operations:
- Setup defines what can be billed: products, prices, customers, tax rules, invoice design, and payment settings.
- Operations decide what actually happens: bill runs, invoice review, payment collection, dunning, credits, and reconciliation.
Daily and weekly workflows
| Workflow | Purpose | Primary docs |
|---|---|---|
| Bill run preview | See what invoices would be generated before committing changes | Bill runs |
| Invoice review | Check generated invoices before customer delivery | Invoice operations |
| Payment collection | Track payment status and transaction history | Payments |
| Failed payment recovery | Retry payment and notify customers | Failed payments and retries |
| Credits and adjustments | Correct posted billing without deleting history | Credits and adjustments |
| Reporting review | Monitor revenue, invoices, and risk | Reporting overview |
Operating principles
- Preview before executing a bill run.
- Prefer corrections through credits and adjustments over editing posted financial history.
- Keep invoice design and payment instructions consistent across customer segments.
- Treat API keys and webhook secrets as production credentials.
- Document exceptions, especially manual credits, refunds, and off-cycle invoices.