# Billabex status glossary

- HTML page: https://www.billabex.com/en/help/customer-accounts-documents/billabex-status-glossary/
- Language: en
- Version française: https://www.billabex.com/fr/aide/comptes-clients-documents/glossaire-statuts.md
- Updated: 2026-07-10
- Site index: https://www.billabex.com/llms.txt

<section class="help-summary" aria-labelledby="in-short"><h2 id="in-short">In short</h2><p>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.</p></section>

## 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

1. Identify whether the object is an account, invoice, credit note, payment, or communication.
2. Find the status in the reference table below.
3. Check dates and amounts determining financial statuses.
4. For a communication, read each recipient event timeline.
5. 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 |
| Email       | 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.