> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nectarclimate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Funding overview

> Track the bill payment lifecycle from review through delivery or payment.

<Tip>Need help in this area? See [Bill Pay FAQ](/platform/bill-pay/faq).</Tip>

The funding overview gives you visibility into where every bill sits in the payment lifecycle. A visual pipeline shows aggregate counts and totals at each stage, and a detailed table lets you drill into individual bills.

## Pipeline stages

The pipeline summary at the top of the page shows four stages with bill counts and total dollar amounts:

| Stage                 | What it means                                                                                                 |
| --------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Awaiting approval** | Bills have been validated and are waiting for Nectar's operations team to review and approve them for routing |
| **Funds requested**   | Bills on the centralized payment path where funding has been requested                                        |
| **Funds in transit**  | Funding has been received and payment is being processed                                                      |
| **Paid / Delivered**  | Bills that have been successfully paid (centralized path) or delivered to their destinations (AP-coded path)  |

## Bill pay statuses

Each bill in the system has a [bill pay status](/platform/glossary#bill-pay-status) that indicates its current position in the lifecycle:

| Status                 | Description                                                                    |
| ---------------------- | ------------------------------------------------------------------------------ |
| **Waiting validation** | Bill entered the pipeline and is being checked for data quality issues         |
| **Validated**          | Bill passed validation and is awaiting review                                  |
| **Pending routing**    | No routing rules matched — waiting for manual assignment or catch-all          |
| **Delivered**          | Bill was forwarded to a destination (email or ERP). Terminal state.            |
| **Funding requested**  | Centralized path: waiting for customer funding                                 |
| **Funding received**   | Funds received, vendor payment is being initiated                              |
| **Payment processing** | Payment is in progress with the payment provider                               |
| **Paid**               | Vendor was paid successfully. Terminal state.                                  |
| **Payment failed**     | Payment attempt failed. Flagged for attention. Terminal state.                 |
| **Cancelled**          | Bill pay cycle was cancelled (bill deleted, or manual action). Terminal state. |
| **In exception**       | An issue was raised that paused the cycle. Resumes when resolved.              |
| **In dispute**         | A dispute was opened. Cycle pauses until the dispute is resolved.              |

## Late-risk escalation

When a bill is approaching its due date without being paid or delivered, Nectar automatically escalates through three [late-risk levels](/platform/glossary#late-risk-level):

| Level        | Timing                         | What happens                                  |
| ------------ | ------------------------------ | --------------------------------------------- |
| **Warning**  | Due date minus buffer days     | Early alert sent to configured recipients     |
| **Urgent**   | Approaching due date           | Escalation notification sent                  |
| **Critical** | Due date is imminent or passed | Final escalation — immediate attention needed |

The buffer period is configured per company and defaults to 7 days. Bills showing a late-risk badge in the funding table need prompt attention to avoid late fees.

<Note>
  Late-risk alerts are sent to users matched by your notification rules. Configure who receives these alerts in your [routing rules](/platform/bill-pay/rules).
</Note>

## Using the funding table

The table below the pipeline shows individual bill pay cycles. Each row includes:

* **Status** — current lifecycle position (color-coded badge)
* **Utility provider** — who issued the bill
* **Bill date** and **Due date** — timing context
* **Risk** — late-risk badge if approaching due date
* **Total charges** — the bill amount
* **Funds requested** — when funding was requested (centralized path)

### Available actions

From each row, you can:

* **Preview the bill** to see full bill details in a side panel
* **Open in new tab** to navigate to the bill's detail page
* **View routing history** to see how rules evaluated this bill

### Filtering

Use the filter bar to narrow the table by status, date range, risk level, or utility provider. Filters persist for your session so you can come back to the same view.

## What happens when a bill changes

Bill Pay handles changes to bills that are already in the pipeline:

* **Bill is deleted** — the payment cycle is cancelled. If payment was already in-flight, Nectar flags it for reconciliation.
* **Bill is revised** — the old cycle is cancelled and a fresh cycle begins for the new version.
* **Charges change** — if payment hasn't started yet, the amount is updated. If payment is in-flight, the change is flagged for attention.

## Related pages

* [Bill Pay overview](/platform/bill-pay/overview) — how the module works end-to-end
* [Rules](/platform/bill-pay/rules) — configure routing and GL coding rules
* [Glossary — Bill pay status](/platform/glossary#bill-pay-status) — full status definitions
* [Glossary — Late-risk level](/platform/glossary#late-risk-level) — escalation tier definitions