Workday Integration — Proposed Guide
Planned API — Reference OnlyWorkday Integration: A possible Workday workflow would synchronize approved workforce attributes into expense-related organization records. Employment…
Overview
A possible Workday workflow would synchronize approved workforce attributes into expense-related organization records. Employment lifecycle and application-access lifecycle require separate decisions.
Key concepts
Map stable worker identifiers, organizational units and effective dates. Preserve historical expense attribution when workers move.
Implementation considerations
No Workday data is read. Do not interpret every worker change as authorization to alter financial approvals or account privileges.
Illustrative data model
This local fixture shows a possible representation for the concepts above. It is not an endpoint response, production configuration or a claim that the described capability is implemented.
{
"reference_only": true,
"topic": "Workday Integration",
"external_id": "external_example_123",
"user_id": "usr_example_123",
"subsidiary_id": "sub_example_123",
"effective_on": "2026-01-15"
}Design review checklist
- Document which organization owns the workday integration representation and which actor may view or change it.
- Test the boundaries of external id, user id, subsidiary id, effective on using synthetic values, including missing or inconsistent references.
- Before future implementation, obtain an approved contract and review failure behavior. This documentation does not authorize production activation.
Proposed data types
| Name | Type | Description |
|---|---|---|
| external_id | string | Fictional source/provider correlation value, not a credential or proof of synchronization. |
| user_id | string | Stable fictional user reference; not a secret and not evidence that a resource exists. |
| subsidiary_id | string | Stable fictional subsidiary reference; not a secret and not evidence that a resource exists. |
| effective_on | string (date) | Synthetic calendar date in YYYY-MM-DD form; period inclusivity must be defined by the future contract. |