Skip to main content
Need help in this area? See Bill Pay FAQ or email [email protected].
The Workday Financials integration posts coded utility bills from Nectar into your Workday tenant as supplier invoices. Nectar connects to the Workday Financial Management and Procurement APIs using an Integration System User (ISU) with OAuth 2.0, configured through the Bill Pay destination wizard.

​
How the connection works

Nectar creates each bill as a Workday Supplier Invoice and submits it to the Supplier Invoice business process. Depending on your tenant configuration, this uses the REST supplierInvoices resource (/ccx/api/procurement/v1/{tenant}/supplierInvoices) or the Workday Web Services (WWS) Submit_Supplier_Invoice / Import_Supplier_Invoice operations for higher-volume, schema-validated loads. Each invoice payload references the company, supplier, invoice date, currency, and line items with the correct spend category and worktags (cost center, region, project, and other financial dimensions). Nectar resolves supplier and company Workday IDs before submitting, and checks for an existing invoice by supplier and invoice number to avoid duplicates.

​
Connection fields

Configure these fields when you select Workday Financials:
FieldDescriptionExample
Destination nameLabel for this connection in NectarWorkday Finance
Tenant nameYour Workday tenant identifieracme_corp
HostnameWorkday services hostnameimpl-services1.wd5.myworkday.com
Client IDIntegration client ID(secret)
Client secretIntegration client secret(secret)
Refresh tokenOAuth refresh token for the integration(secret)
Client ID, client secret, and refresh token are stored as encrypted credentials.

​
Set up in Nectar

1

Open the ERP wizard

Go to Bill Pay > Destinations, click AP/ERP Integrations, and select Workday Financials.
2

Enter connection details

Provide the destination name, tenant, hostname, client ID, client secret, and refresh token from your Workday integration administrator.
3

Review and create

Confirm the settings and click Create integration.
4

Add a routing rule

Create a routing rule with Route to AP integration targeting your Workday destination.

​
What your Workday team configures

Your Workday integration team typically:
  1. Creates an Integration System User (ISU) and registers an API Client (OAuth 2.0) with a refresh token, scoped to the Financial Management and Procurement endpoints used for supplier invoice submission.
  2. Grants the ISU a security group with access to the Supplier Invoice business process and provides the tenant, hostname, Client ID, Client secret, and refresh token.
  3. Confirms company, supplier, spend category, and worktag (cost center / financial dimension) mappings for utility bills.
Use a sandbox (implementation) tenant for initial validation when available. Teams that prefer file-based loads can use an EIB during onboarding.

​
FAQ

Yes. The Workday wizard requires a client ID, client secret, and refresh token from your registered API Client so Nectar can maintain authorized OAuth 2.0 access as the Integration System User.
Nectar maps your GL coding rules to Workday spend categories and worktags (cost center, region, project, and other financial dimensions) on each supplier invoice line. Confirm the worktag model with your Workday team during onboarding so invoices pass business-process validation.
Check the bill audit trail for the Route to AP integration action and delivery status on your Workday destination.