Skip to content

Workday’s SOAP web services and Report-as-a-Service (RaaS) document the interfaces this connector uses.

The connection authenticates with an Integration System User (ISU) — a Workday user type built for system-to-system integration, secured by an Integration System Security Group that grants it just the access this connector needs (report access for reads, the Submit Accounting Journal business process for posts). Requests carry the ISU’s username and password; there is no interactive sign-in.

Field Type Description
Name Text Display name for this connection.
Tenant Host Text Your Workday host, e.g. wd5-impl.workday.com.
Tenant Name Text Your Workday tenant name.
ISU Username Text The Integration System User’s username.
ISU Password Text The Integration System User’s password. Stored encrypted.

Workday Financials has no fixed set of canned entities. Instead, the Import Workday Entity step calls a Report-as-a-Service (RaaS) report you build in Workday and publish with Web Service access — you supply its URL. The step supports filters on company, ledger, period, accounting_date (range), ledger_account (range), and cost_center, each passed through as a report parameter, so a filter only works if your report defines a matching prompt. See Import Workday Entity for the full field reference.

The Workday Financials: Post Journal Entry step posts accounting journals through PlaidCloud’s shared ERP write pipeline, using Workday’s Submit_Accounting_Journal SOAP operation and polling the entry’s business-process status to a terminal state before reporting it posted. A correction posts a new, debit/credit-swapped reversing entry rather than editing the original. See Workday Financials: Post Journal Entry for the field reference, and Connect to Workday Financials for the full posting walkthrough.

Limitation What it means
Import shape depends on your RaaS report PlaidCloud has no canned entities for Workday Financials — the report’s fields, prompts, and access control all live in Workday. A report change there can change your import’s shape without any change on the PlaidCloud side.
Business-process approval adds latency A journal routed through an approval step in your Submit Accounting Journal business process stays pending until approved in Workday; the terminal-state poll waits for that.