A reorg is finished in Workday when the worker’s cost center assignment is effective. It is finished in NetSuite only when the department record and the employee record both match that assignment. Teams that send workers first, or that send the supervisory organization name and call it a department, leave NetSuite on the tree from before the reorg.
Workday has no published NetSuite connector on the pages checked for this guide. The Workday side is organization and staffing data. The NetSuite side is SuiteTalk REST, and only the records and fields Oracle’s current help pages actually show.
What Workday treats as the cost center
A cost center is an organization type used to track revenue and expense. Workday’s HCM course manual says cost centers hold financial transactions, budgets, and workers, and that they are often what a legacy system called a department. Cost centers roll up into cost center hierarchies, and those hierarchies store cost centers for reporting. A hierarchy is not a second membership on the worker.
Every worker belongs to a supervisory organization. The same manual says a worker hired or transferred into a supervisory organization becomes a member of that organization’s default assignments, including company and cost center. Subordinate supervisory organizations inherit those assignments unless someone overrides them. On the supervisory organization you can list many allowed organizations and one default.
Change Organization Assignments is how you change the cost center on a worker or a position. The organization type has to support staffing in Maintain Organization Types, and the check box Show in Change Organization Assignments and Job Requisition has to be selected. When it is not, Workday says some organization data is unavailable and the organization does not display on the worker position. A feed that reads only what the position screen shows will skip that cost center.
Workday also says the organizations on a correction must be active as of the new effective date. A cost center that is inactive on the date of the run is not a current assignment, even if the name still appears in an old file.
Why the worker row goes stale after the reorg
Default organization assignments do not all come from the same place:
| What happened in Workday | Where the cost center comes from |
|---|---|
| What happened in WorkdayHire, additional job, or contract contingent worker | Where the cost center comes fromJob requisition if it has assignments; otherwise hiring restrictions, then the supervisory organization. The staffing model changes which of those Workday checks. |
| What happened in WorkdayMove a worker onto a position that already has organizations | Where the cost center comes fromThose position organizations, except cost centers, custom organizations, gifts, and grants, which come from related worktags and supersede the position. |
| What happened in WorkdayMove a worker onto a position with no organizations, while the supervisory organization has defaults | Where the cost center comes fromThe supervisory organization, again with related worktags superseding cost center. |
| What happened in WorkdayMove onto a position with no organizations and no defaults | Where the cost center comes fromCost center still comes from related worktags. Other organizations do not fill in. |
Organization assignment worktags then flow onto expense reports, payroll costing, and other transactions. An invalid combination can save on the worker and fail later on the transaction. The report Workday names for finding those is Organization Assignment Exception Audit. Run it before you treat the feed as the chart of accounts.
A nightly file of “the worker’s cost center name today” misses four cases this model creates:
- The assignment is future-effective. The organization has to be active as of the effective date you meant, not as of the file’s run clock.
- The worker moved supervisory organizations and inherited a new default. The worker business process never shows a cost center edit.
- A related worktag replaced the cost center that is still sitting on the position.
- The cost center was inactivated, or it no longer displays because the organization type check box is off, and the previous file’s department is still active in NetSuite.
Blank organization fields after a job change that also changes the position are a separate Workday case, covered in why those fields are blank.
What Oracle documents on the NetSuite side
Confirm every field in your account’s REST API Browser. These are the records the public help pages expose. This guide does not add operations those pages do not show.
| Record | Record id | What the help page shows | What it does not show |
|---|---|---|---|
| RecordDepartment | Record iddepartment |
What the help page showsA sample body with isInactive, name, subsidiary.items as a list of id values, parent.id, and includeChildren. One subrecord, classTranslation. Read-only sublists, including system notes, are not supported. |
What it does not showNo sample URL, and no externalId in that sample. Do not assume a department external id until the REST API Browser lists it. |
| RecordEmployee | Record idemployee |
What the help page showsCreate with POST to https://{account}.suitetalk.api.netsuite.com/services/rest/record/v1/employee and a body of firstName, lastName, and subsidiary.id. Update a last name with PATCH to the same path plus /{id}. Prerequisites include Advanced Employee Permissions, the Employee Record, Perform Search, SuiteAnalytics Workbook, and SuiteScript. |
What it does not showThe create sample does not include a department. The 2018.1 SOAP employee schema lists department as an optional record reference. Confirm the REST field on your account’s browser before you write it. |
| RecordSubsidiary | Record idsubsidiary |
What the help page showsGET only, including externalid, name, parent, and isinactive. Requires OneWorld or the Subsidiaries feature. |
What it does not showPOST, PATCH, and DELETE are not supported. A reorg cannot create legal entities through this record. |
SuiteTalk REST is documented in the REST Web Services API Guide. The employee and subsidiary samples both address records as /services/rest/record/v1/{recordId}.
Send organizations, then workers
Match on an identifier you have confirmed in both systems. Workday’s pages cited here do not name a single “department code” field, and the department REST sample does not show an external id. Pick the writable department field your REST API Browser shows, store the Workday organization identifier there, and stop matching on the display name. Names change in a reorg. The parent changes too, and NetSuite’s parent is one department id, while Workday’s cost center hierarchy is a reporting rollup that can only store cost centers.
Order inside one run:
- Read cost centers that are active as of the effective date, including parentage in the hierarchy and the companies they are restricted to. The worktag page says invalid combinations are tied to the companies on the cost center.
- Create or update the NetSuite
departmentfirst:name,parent,subsidiaryitems,includeChildren, andisInactive. A worker row that references a department id you have not created yet has nowhere to land. - Read each worker’s cost center as of that same effective date, using the source in the table above, not the supervisory organization name.
- Update the employee only after the REST API Browser shows a department reference. The published create sample sets
subsidiary.idand does not set a department. Subsidiary itself is read-only, so the employee’s subsidiary has to already exist. - Inactivate a NetSuite department only after no employee you just sent still points at it. Oracle’s department page shows
isInactivein the sample and does not describe what a later employee write does against an inactive department. Check that in the account before you rely on it.
Kiweely Roots (coming next) is the external integration platform for this kind of finance feed: you describe what goes where, the agent builds and tests it on Sandbox, and the run is tested code. Register interest and name the cost center file that goes stale after each reorg.