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

# ERP integrations

> Connect Bill Pay to SAP, Oracle, Workday, NetSuite, or QuickBooks Online.

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

ERP integrations let you route coded utility bills from Nectar directly into your accounts payable system. After a bill is collected, validated, and matched to your [routing rules](/platform/bill-pay/rules), Nectar formats the invoice data for your ERP and delivers it to the destination you configure.

## Supported systems

<CardGroup cols={2}>
  <Card title="SAP S/4HANA" icon="building-columns" href="/platform/bill-pay/erp-integrations/sap-s4hana">
    Connect to SAP S/4HANA Cloud or on-premise using a communication user and API host.
  </Card>

  <Card title="Oracle Fusion" icon="building-columns" href="/platform/bill-pay/erp-integrations/oracle-fusion">
    Connect with your Oracle Cloud instance URL, identity domain, and OAuth client credentials.
  </Card>

  <Card title="Workday Financials" icon="building-columns" href="/platform/bill-pay/erp-integrations/workday-financials">
    Connect with tenant, hostname, and Workday API credentials.
  </Card>

  <Card title="NetSuite" icon="building-columns" href="/platform/bill-pay/erp-integrations/netsuite">
    Connect with your NetSuite account ID and integration credentials.
  </Card>

  <Card title="QuickBooks Online" icon="building-columns" href="/platform/bill-pay/erp-integrations/quickbooks-online">
    Connect through an OAuth authorization flow tied to your QuickBooks company.
  </Card>
</CardGroup>

## How ERP delivery fits into Bill Pay

<Steps>
  <Step title="Collect and validate the bill">
    Nectar ingests the utility bill, checks for [data quality issues](/platform/data-quality/issues), and opens a bill pay cycle.
  </Step>

  <Step title="Apply GL coding and routing rules">
    Your [GL coding rules](/platform/bill-pay/rules) assign cost categories. Routing rules select the ERP destination.
  </Step>

  <Step title="Review before handoff">
    Bills pass through Nectar's review controls before they are sent to your ERP.
  </Step>

  <Step title="Deliver to your ERP">
    Nectar formats vendor, invoice, date, amount, tax, and GL coding fields for your accounting system and posts the AP document.
  </Step>

  <Step title="Audit the result">
    Every evaluation, GL assignment, and delivery attempt is recorded in the [bill audit trail](/platform/bill-pay/decisions).
  </Step>
</Steps>

## What Nectar sends

When a bill is routed to an ERP integration, Nectar delivers structured AP data including:

* Vendor and account identifiers from the bill
* Invoice or statement reference numbers
* Billing period, bill date, and due date
* Total charges, taxes, and line-item detail where available
* GL account and cost object assignments from your rules
* The bill PDF for attachment or reference, where your ERP supports it

Nectar posts to each system's **native AP document** using that vendor's standard API, so a Nectar-created record behaves like any other AP document in your accounting system:

| System             | AP document      | API / mechanism                                                                        | Authentication                          |
| ------------------ | ---------------- | -------------------------------------------------------------------------------------- | --------------------------------------- |
| SAP S/4HANA        | Supplier invoice | Supplier Invoice Integration (`SAP_COM_0057`), `API_SUPPLIERINVOICE_PROCESS_SRV` OData | Communication user (Basic + CSRF token) |
| Oracle Fusion      | Payables invoice | Fusion Financials REST (`invoices` / Import Payables Invoices)                         | OAuth 2.0 (OCI IAM identity domain)     |
| Workday Financials | Supplier invoice | Financial Management / Procurement APIs, Supplier Invoice business process             | OAuth 2.0 (Integration System User)     |
| NetSuite           | Vendor bill      | SuiteTalk REST record service (`vendorBill`)                                           | Token-based auth or OAuth 2.0           |
| QuickBooks Online  | Bill             | Accounting API `Bill` object (`/v3/company/{realmId}/bill`)                            | OAuth 2.0                               |

Exact field mapping depends on your ERP and chart of accounts. Nectar works with your finance and IT teams during setup to align bill fields with your AP document structure.

## Setting up an integration

<Steps>
  <Step title="Create the destination">
    Go to [**Bill Pay > Destinations**](https://dash.nectarclimate.com/bill-pay/destinations/new/integration) and choose **AP/ERP Integrations**.
  </Step>

  <Step title="Follow the system-specific guide">
    Each ERP has different credential requirements. Use the guide for your system:
    [SAP](/platform/bill-pay/erp-integrations/sap-s4hana),
    [Oracle](/platform/bill-pay/erp-integrations/oracle-fusion),
    [Workday](/platform/bill-pay/erp-integrations/workday-financials),
    [NetSuite](/platform/bill-pay/erp-integrations/netsuite), or
    [QuickBooks Online](/platform/bill-pay/erp-integrations/quickbooks-online).
  </Step>

  <Step title="Validate in a test environment">
    Point your first destination at a sandbox or QA client when possible. Run sample bills through routing rules and reconcile the resulting ERP documents before go-live.
  </Step>

  <Step title="Add routing rules">
    Create [routing rules](/platform/bill-pay/rules) with a **Route to AP integration** action that targets your new destination.
  </Step>
</Steps>

<Note>
  Bill Pay must be enabled for your company before ERP destinations appear. If you do not see Bill Pay in the sidebar, contact [support@nectarclimate.com](mailto:support@nectarclimate.com).
</Note>

## Security

* Credentials are encrypted at rest and shown masked in the Nectar UI.
* Each integration uses a dedicated technical user or OAuth client scoped to AP posting — not a named employee login.
* You can configure separate destinations for sandbox and production environments.

## Related pages

* [Destinations](/platform/bill-pay/destinations) — create and manage ERP connections
* [Bill audit](/platform/bill-pay/decisions) — verify deliveries and rule evaluations
* [Bill Pay overview](/platform/bill-pay/overview) — full bill pay workflow
* [Glossary — Destination](/platform/glossary#destination)