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

# Bill audit

> Audit trail of routing decisions, GL coding, and ERP delivery for every bill.

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

The bill audit page — labeled **Routing history** in the platform — shows a complete audit trail of how every bill was evaluated against your [routing rules](/docs/platform/glossary#routing-rule). For each bill, you can see which rules matched, what actions were taken, whether ERP delivery succeeded, and any manual overrides.

Navigate to [**Bill Pay > Routing history**](https://dash.nectarclimate.com/bill-pay/decisions) to open the audit table.

## Understanding the audit table

The table shows one row per bill evaluation. Key columns include:

| Column               | What it shows                                              |
| -------------------- | ---------------------------------------------------------- |
| **Evaluated**        | When the bill was evaluated against rules                  |
| **Utility Provider** | The utility company that issued the bill                   |
| **Bill Date**        | The date on the bill                                       |
| **Due Date**         | When payment is due                                        |
| **Total Charges**    | The bill amount                                            |
| **Rules Matched**    | How many of your rules matched this bill (e.g., **2 / 5**) |

A green check indicates at least one rule matched and actions were taken. An unmatched bill shows a neutral indicator (not an error) — the bill may be waiting for manual assignment or routed to the catch-all destination.

## Viewing evaluation details

Click any row to open the evaluation detail panel. This shows the complete trace of how your rules were evaluated:

### Condition trace

For each rule, you can expand the evaluation to see:

* Each condition that was tested (e.g., "Commodity equals Electricity")
* Whether each condition passed or failed
* The actual value the bill had for that field

This makes it straightforward to understand why a rule matched or didn't match a particular bill.

### Actions fired

For rules that matched, you'll see which actions executed:

* **Forward to email** — shows the destination name and delivery status (Delivered, Pending, or Failed)
* **Route to AP integration** — shows the ERP system and delivery status
* **Request funds** — shows the funding request status
* **Assign GL code** — shows the GL account code assigned (status **Applied** when non-delivery)
* **Notify user** — shows who was notified (status **Applied** when non-delivery)

### GL coding summary

If GL coding rules assigned a code, the detail panel shows:

* The GL account code and name
* Whether it was assigned by a rule or manually

## Sending a bill to another destination

If a bill needs to go somewhere that the rules didn't send it — for example, a one-time review by a different team — you can create an **additional forward** without undoing the original routing.

<Steps>
  <Step title="Open the evaluation detail">
    Click the bill row in the routing history table to open the detail panel.
  </Step>

  <Step title="Click 'Send to another destination'">
    At the bottom of the panel, click the button to open the override dialog.
  </Step>

  <Step title="Select a destination and reason">
    Choose an active destination from the dropdown. Optionally add a reason explaining why you're sending it elsewhere.
  </Step>

  <Step title="Send">
    The bill is immediately forwarded to the selected destination. This action is logged in the evaluation detail alongside the original routing.
  </Step>
</Steps>

<Note>
  Additional forwards don't undo or replace the original routing. The bill is delivered to both the rule-determined destination and any manually-selected destinations.
</Note>

## Filtering and searching

Use the filter bar above the table to narrow results by:

* **Decision Date** — when the evaluation happened
* **Utility Provider** — the utility that issued the bill
* **Total Charges** — bill amount range
* **Rule** — show only evaluations for a specific rule
* **Match Result** — bills with matches (**Has matches**) or without (**No matches**)
* **Additional Forwards** — whether an extra manual forward was sent

## Related pages

* [Rules](/docs/platform/bill-pay/rules) — configure the rules that drive routing decisions
* [Destinations](/docs/platform/bill-pay/destinations) — manage where bills are sent
* [ERP integrations](/docs/platform/bill-pay/erp-integrations/overview) — SAP, Oracle, Workday, and NetSuite setup
* [Glossary — Routing decision](/docs/platform/glossary#routing-decision) — definition
* [Glossary — Additional forward](/docs/platform/glossary#additional-forward) — definition