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

> Automate how utility bills flow to your accounts payable team or ERP system.

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

Bill Pay automates the handoff between Nectar and your accounts payable process. Once a bill is collected and processed, Bill Pay evaluates it against your routing rules and delivers it to the right place — whether that's an email inbox, an ERP system like SAP, Oracle, Workday, NetSuite, or QuickBooks Online, or a centralized payment workflow managed by Nectar.

Instead of manually downloading bills and forwarding them to AP, you configure the logic once and let every future bill flow automatically.

## How it works

When a new bill is processed in Nectar, Bill Pay takes over:

<Steps>
  <Step title="Validation">
    The bill is checked for data quality issues. If any unresolved issues exist, it pauses until they're addressed.
  </Step>

  <Step title="Review">
    Nectar reviews the bill before routing. The bill waits for Nectar approval so only verified bills reach your AP systems.
  </Step>

  <Step title="Rule evaluation">
    Your routing rules and GL coding rules are evaluated against the bill. Conditions like utility type, site, total charges, or flagged status determine which actions fire.
  </Step>

  <Step title="Delivery">
    The bill is forwarded to the matched destinations — emailed to your AP team, pushed to your ERP, or both. If no rules match, the catch-all destination receives the bill when one is set; otherwise the bill stays in pending routing until you assign a destination or add a rule.
  </Step>
</Steps>

## Two integration paths

<CardGroup cols={2}>
  <Card title="Delivered (AP-coded)" icon="envelope">
    Bills are forwarded to your AP team via email or pushed directly to an ERP system. The bill pay cycle ends at delivery — your team handles payment from there.
  </Card>

  <Card title="Centralized (Nectar pays)" icon="credit-card">
    Nectar handles payment on your behalf. Bills progress through funding, payment processing, and reconciliation. You receive confirmation once the vendor is paid.
  </Card>
</CardGroup>

Most companies start with the **Delivered** path — routing bills to their existing AP workflow. The **Centralized** path is available for companies that want Nectar to manage vendor payments directly.

## Module pages

<CardGroup cols={2}>
  <Card title="Rules" icon="list-check" href="/docs/platform/bill-pay/rules">
    Configure routing and GL coding rules that automatically process incoming bills.
  </Card>

  <Card title="Destinations" icon="route" href="/docs/platform/bill-pay/destinations">
    Set up email addresses and ERP integrations where bills are delivered.
  </Card>

  <Card title="ERP integrations" icon="building-columns" href="/docs/platform/bill-pay/erp-integrations/overview">
    Connect SAP, Oracle, Workday, NetSuite, or QuickBooks Online.
  </Card>

  <Card title="Routing history" icon="clock-rotate-left" href="/docs/platform/bill-pay/decisions">
    View routing decisions, GL coding, and ERP delivery status for every bill.
  </Card>

  <Card title="Funding overview" icon="chart-simple" href="/docs/platform/bill-pay/funding">
    Track the payment lifecycle from review through delivery or payment.
  </Card>
</CardGroup>

## Who is Bill Pay for?

Bill Pay is designed for companies that:

* Manage utility bills across many sites and want to eliminate manual forwarding
* Need bills coded with GL accounts before reaching their ERP
* Want a complete audit trail of which bills went where and why
* Use multiple AP teams or systems for different locations or utility types

## Related pages

* [Rules](/docs/platform/bill-pay/rules) — configure routing and GL coding
* [Destinations](/docs/platform/bill-pay/destinations) — email and ERP delivery targets
* [Funding overview](/docs/platform/bill-pay/funding) — payment and delivery lifecycle
* [Routing history](/docs/platform/bill-pay/decisions) — decisions and delivery status per bill
* [Bill Pay FAQ](/docs/platform/bill-pay/faq) — common questions
* [Data Inventory — Bills](/docs/platform/data-inventory/bills) — browse the bills being routed
* [Data Quality — Issues](/docs/platform/data-quality/issues) — resolve issues that can block bill pay routing
* [Glossary — Bill pay status](/docs/platform/glossary#bill-pay-status) — status definitions