Skip to main content
Need help in this area? See Bill Pay FAQ.
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, Nectar formats the invoice data for your ERP and delivers it to the destination you configure.

​
Supported systems

SAP S/4HANA

Connect to SAP S/4HANA Cloud or on-premise using a communication user and API host.

Oracle Fusion

Connect with your Oracle Cloud instance URL, identity domain, and OAuth client credentials.

Workday Financials

Connect with tenant, hostname, and Workday API credentials.

NetSuite

Connect with your NetSuite account ID and integration credentials.

QuickBooks Online

Connect through an OAuth authorization flow tied to your QuickBooks company.

​
How ERP delivery fits into Bill Pay

1

Collect and validate the bill

Nectar ingests the utility bill, checks for data quality issues, and opens a bill pay cycle.
2

Apply GL coding and routing rules

Your GL coding rules assign cost categories. Routing rules select the ERP destination.
3

Review before handoff

Bills pass through Nectar’s review controls before they are sent to your ERP.
4

Deliver to your ERP

Nectar formats vendor, invoice, date, amount, tax, and GL coding fields for your accounting system and posts the AP document.
5

Audit the result

Every evaluation, GL assignment, and delivery attempt is recorded in the bill audit trail.

​
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:
SystemAP documentAPI / mechanismAuthentication
SAP S/4HANASupplier invoiceSupplier Invoice Integration (SAP_COM_0057), API_SUPPLIERINVOICE_PROCESS_SRV ODataCommunication user (Basic + CSRF token)
Oracle FusionPayables invoiceFusion Financials REST (invoices / Import Payables Invoices)OAuth 2.0 (OCI IAM identity domain)
Workday FinancialsSupplier invoiceFinancial Management / Procurement APIs, Supplier Invoice business processOAuth 2.0 (Integration System User)
NetSuiteVendor billSuiteTalk REST record service (vendorBill)Token-based auth or OAuth 2.0
QuickBooks OnlineBillAccounting 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

1

Create the destination

Go to Bill Pay > Destinations and choose AP/ERP Integrations.
2

Follow the system-specific guide

Each ERP has different credential requirements. Use the guide for your system: SAP, Oracle, Workday, NetSuite, or QuickBooks Online.
3

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

Add routing rules

Create routing rules with a Route to AP integration action that targets your new destination.
Bill Pay must be enabled for your company before ERP destinations appear. If you do not see Bill Pay in the sidebar, contact [email protected].

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