Invoices
An invoice is the financial record that tells a customer what they owe for a billing period, order, subscription, usage window, or manual charge.
Invoices in Floatless are usually generated from an upstream workflow:
- A subscription bill run.
- A one-time order.
- A manual billing action.
- A correction or adjustment workflow.
Invoice anatomy
Every invoice can include:
| Area | Description |
|---|---|
| Header | Invoice number, customer, status, issue date, due date, and currency. |
| Service period | The billing period covered by the invoice. |
| Line items | Products, descriptions, quantities, unit prices, usage amounts, discounts, and taxes. |
| Totals | Subtotal, tax, total, paid amount, refunded amount, and balance. |
| Documents | Customer-facing HTML and PDF renderings. |
| Transactions | Payments, refunds, and credit memos associated with the invoice. |
Status lifecycle
| Status | Meaning |
|---|---|
DRAFT |
Invoice is being prepared and should be reviewed. |
POSTED |
Invoice has been issued and should be collected. |
PARTIALLY_PAID |
Some payment has been recorded, but a balance remains. |
PAID |
Invoice balance has been fully paid. |
PARTIALLY_REFUNDED |
Some amount has been refunded or credited. |
REFUNDED |
The invoice has been fully refunded or reversed. |
WITHDRAWN |
The invoice should no longer be collected. |
Invoice balance
Floatless tracks invoice balance from the invoice total and related transactions.
balance = total - amount_paid + amount_refunded
Use the invoice transaction history to explain how the current balance was reached.
Correcting posted invoices
Do not delete or silently overwrite a posted invoice. Use auditable correction flows instead:
- Issue a credit memo to reduce the amount owed.
- Record a refund when money is returned.
- Add notes for internal review.
- Keep transaction history visible for finance and support.