Billabex status glossary
Find the operational meaning of customer, invoice, payment, credit-note, and communication statuses.
Updated
In short
Billabex statuses describe either a financial fact or processing state. An **Overdue** invoice is not the same as a **Bounced** email, and a **Paused** account does not mean its balance is zero. Use the table below to identify the object, then open detail: status summarizes state while its cause remains in dates, amounts, and events.
Expected result
You interpret each badge in its object context without inferring the wrong action.
Before you start
- Identify the screen and object carrying the status.
- Open detail when several causes can produce the same badge.
Procedure
- Identify whether the object is an account, invoice, credit note, payment, or communication.
- Find the status in the reference table below.
- Check dates and amounts determining financial statuses.
- For a communication, read each recipient event timeline.
- For a pause, find every reason and task still active.
What Billabex does
| Object | Main statuses | Meaning |
|---|---|---|
| Invoice | Issued, Overdue, Paid | Due date and total coverage |
| Payment | Unpaid, Partially paid, Paid, Overpaid | Share of total covered |
| Credit note | Issued, Partially settled, Settled | Amount still available |
| Collections | Active, Paused | Whether another action may be scheduled |
| Sent, Delivered, Opened, Bounced, Complained | Technical feedback per recipient |
If the result is not what you expected
- A state can change after asynchronous processing; compare times before and after refresh.
- An opened email does not prove payment, and a paid invoice does not prove last-email delivery.
- For a label absent here, preserve its exact text and use the guide for that object.