Skip to main content
Need help in this area? See Bill Pay FAQ.
Open Bill Pay > Funding Overview for 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:

​
Bill pay statuses

Each bill in the system has a bill pay status that indicates its current position in the lifecycle:

​
Late-risk escalation

When a bill is approaching its due date without being paid or delivered, Nectar automatically escalates through three late-risk levels: 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.
Late-risk alerts go to emails on matching routing-rule Forward to email destinations and Notify user actions (then the catch-all if needed). Configure recipients in your routing rules.

​
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)
  • Created — when the cycle was created

​
Available actions

From each row, you can:
  • Preview 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, utility provider, risk level, bill date, or due date. 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.
  • A revision link is added — the first explicit usage-row revision link cancels the earlier bill’s cycle. Overlap or duplicate detection alone does not cancel payment.
  • Charges change — if payment is in-flight, the change is flagged for attention. If the cycle is validated but payment has not started, the cycle is cancelled. Other open statuses are logged; the amount is not silently updated.