Home› Celigo› Integrations› NetSuite ↔ Workday
NetSuite ↔ Workday on Celigo

NetSuite Workday integration on Celigo — sync HR data to finance without the manual handoff

Workday owns your people data. NetSuite owns your financial data. When those two systems don't talk, every new hire, payroll run, and expense approval creates manual re-entry work that is slow, error-prone, and hard to audit. Entech builds Celigo integrations that connect Workday and NetSuite — automating the employee-to-vendor sync, payroll-to-GL posting, and expense-to-bill flow that every finance team needs.

Talk to an integration expert в†’
What you get

What this integration does

The core outcome: HR events in Workday automatically update NetSuite records, and financial structure in NetSuite stays in sync with Workday's organizational model.

Workday
New employee hired or contractor added
в†’
NetSuite
Employee or vendor record created with department, subsidiary, and cost center mapping
Workday
Payroll run finalized — labor cost results by department and pay code
в†’
NetSuite
Journal entries posted to GL with correct accounts, departments, and subsidiaries
Workday
Expense report approved
в†’
NetSuite
Vendor bill created against the employee vendor record, ready for payment
NetSuite
Project or cost center structure
в†’
Workday
Worktags updated so time-tracking allocations match the NetSuite project hierarchy
Workday — optional
Termination or role change event
в†’
NetSuite
Employee record inactivated or role updated; access deprovisioning flag set for downstream systems
Field-level detail

What data moves and how

Workday's web services API uses SOAP with a proprietary object model. Entech configures Celigo's HTTP adapter to call Workday WWS endpoints, parse the XML response, and transform it into NetSuite's SuiteTalk REST format.

Worker в†’ Employee / Vendor record
Workday Worker fields — Legal Name, Email, Department, Manager, Location, Start Date, Worker Type (employee vs contractor) — map to NetSuite Employee or Vendor record fields. The Worker Type determines which NetSuite record type is created. Department maps to NetSuite Department and Subsidiary based on a configuration table Entech builds during discovery. The Workday Worker ID is stored on the NetSuite record as a custom field for reverse lookups.
Payroll results в†’ Journal entries
After each Workday payroll run, Celigo calls the Payroll Results web service to retrieve labor cost data by pay component and organizational cost center. Each pay component (base salary, OT, bonuses, employer taxes, benefits) maps to a NetSuite GL account defined in a pay code mapping table. The journal entry is dated to the pay period end date and split by department and subsidiary to match NetSuite's segment structure.
Expense report в†’ Vendor bill
When a Workday expense report reaches Approved status, Celigo retrieves the line items, merchant, amount, currency, and expense category. Each expense line maps to a NetSuite expense account via a category mapping table. The NetSuite vendor bill is created against the employee's vendor record, with the Workday expense report ID stored as a memo for audit traceability. Multi-currency expense reports trigger NetSuite's currency conversion using the exchange rate on the report date.
Cost center / Worktag sync
NetSuite Departments and Projects can be pushed back to Workday as Worktags so that time entry and project-based expense allocation in Workday matches the NetSuite cost structure. This reverse flow runs on a scheduled basis — typically nightly — and only sends changed records using a last-modified filter to keep API call volume low on the Workday side.
What makes this hard

Why NetSuite Workday integrations are complex

Workday and NetSuite are both enterprise-grade systems with strict data models. This integration is more complex than most — here is where the effort goes.

01
Workday's SOAP API and tenant configuration
Workday does not expose a simple REST API for most HR objects. The Workday Web Services (WWS) API is SOAP-based with a complex XML envelope and tenant-specific namespace. Each Workday tenant has different version requirements and security group configurations. The integration service account (ISU) in Workday must have exactly the right domain security policies enabled — this alone takes a dedicated Workday admin half a day to configure correctly. Entech handles this setup with your Workday team.
02
Mapping Workday's organizational model to NetSuite's segment structure
Workday uses Cost Centers, Organizations, and Worktags. NetSuite uses Departments, Classes, Locations, and Subsidiaries. These don't map one-to-one. A Workday Cost Center might correspond to a NetSuite Department in one subsidiary but a Class in another. Entech builds a mapping matrix during discovery and implements it as a lookup table in Celigo — this mapping is the foundation for accurate GL posting and cannot be skipped or estimated.
03
Payroll posting timing and period locks
NetSuite locks accounting periods. If a Workday payroll run is finalized after the period close date, posting the journal entry to the closed period in NetSuite will fail — or worse, post to the wrong period if not handled carefully. The Celigo flow needs logic to detect period lock status and either queue the entry for the next open period or alert the NetSuite admin. Entech configures this as part of the payroll integration flow.
04
Multi-subsidiary NetSuite with single Workday tenant
Many companies run multiple NetSuite subsidiaries under one Workday instance. The integration needs to correctly route each Workday worker and payroll result to the right NetSuite subsidiary based on their Legal Entity in Workday. Misconfigured subsidiary routing is one of the hardest problems to detect post-go-live because the records look correct in both systems individually — the error only surfaces in consolidated financial reporting.
Implementation

Typical project timeline

NetSuite Workday integrations are among the longer engagements on Celigo — Workday's API setup and the organizational mapping work add time that cannot be compressed. A focused payroll-to-GL integration runs 6–8 weeks; a full employee lifecycle + payroll + expenses integration typically runs 10–14 weeks.

1
Discovery
Weeks 1–2
Workday ISU setup. WWS API version confirmation. Organizational mapping workshop. Pay code в†’ GL account matrix. NetSuite segment structure review.
2
Build
Weeks 3–5
Celigo HTTP adapter config for Workday WWS. Transformation scripts for XML в†’ NetSuite objects. Payroll posting logic including period-lock handling. Sandbox testing with sanitized payroll data.
3
UAT
Weeks 6–7
Full payroll cycle test in sandbox. Employee hire/terminate scenarios. Expense report end-to-end. Finance team validation of GL entries against Workday source data.
4
Go-Live
Weeks 8+
Production cutover timed with payroll cycle. First live payroll run monitored in real time. 30-day hypercare period with Entech on call for any edge cases.
About Workday access
Entech needs read/write access to specific Workday web service domains — HR, Payroll, Expenses — through a Workday Integration System User (ISU). Your Workday administrator configures these access rights. We provide a detailed requirements list during kickoff so your Workday team knows exactly what to configure before the build phase begins.
Related work

Other integrations we build

NetSuite ↔ HubSpot
View в†’
NetSuite ↔ Shopify
View в†’
NetSuite ↔ Salesforce
View в†’
NetSuite integration overview
View в†’
Ready to connect Workday and NetSuite?
Entech is a certified Celigo partner with deep NetSuite expertise and experience navigating Workday's API complexity. We scope, build, and support this integration from discovery through go-live.
Get in touch в†’