cluster_name
, then Orb can automatically re-organize your invoice to be grouped by the cluster’s name at the top level. Orb would then automatically split the costs of storage, network traffic, and compute for each cluster.
SUM
or COUNT
).issued
, it can:
paid
state. This may happen as the result of an Orb-initiated auto-collection action, a user paying the invoice through the invoice portal, or the invoice being manually marked as paid. Note that $0 invoices are automatically marked as paid
upon issuance and do not send email notifications.synced
state. Orb supports syncing to enterprise invoicing providers, such as Bill.com and Stripe Invoicing — this is a one-way sync, and Orb will not pick up changes to the invoice once it’s synced.void
state by being manually marked as void. When an invoice is voided, any balance it consumes is reversed.Payment failed
state (representing either invoice that failed to issue due to a misconfiguration, or a failed payment), a Processing
state (representing invoices whose payment is in progress), and an Action needed
state (representing invoices that require manual issuance). The dashboard is optimized for actionability, allowing you to quickly triage invoices that require your attention and to provide an easy way to summarize the month’s invoices.
Once an invoice’s grace period has elapsed and it is eligible for auto-issue, it will be in a pending issue
state in the Orb dashboard, to signify that Orb will shortly issue the invoice. No manual action is required in this state.
payment_provider
attribute on the customer to the corresponding provider.DocNumber
field)