Connector for Workday Applications

01 · Basics — Understand the building blocks

The Workday connector documentation describes worktags used by outbound transactions to report costs to Workday. A cost value without its agreed financial classification is incomplete.

Decide which system owns each reference value and how inactive or missing mappings are handled.

Topics in this series

• Flow selection
• Worktags
• Reference synchronization
• Cost transactions
• Exception reconciliation

02 · Configuration — Work through the setup

Use a training environment and match the actions to the IBM guide for your installed build.

1. Select a documented connector flow and list the worktags it requires.
2. Map a training company/cost context and verify reference values in both systems.
3. Configure the flow through the supplied connector procedure for the installed version.
4. Send one test cost transaction with known values and inspect its receiving financial context.
5. Test an invalid or inactive worktag and record correction and retry behavior.

03 · Practical example

Fictional teaching example

A $150 training labor cost belongs to one cost center. Posting $150 to a default center balances numerically but fails the business requirement.

04 · Practice and verify

Reconcile one cost by amount, currency, transaction identity and every required worktag.

Expected result

The receiving transaction has the intended financial dimensions, and a missing required mapping cannot silently become a successful business outcome.

Common mistakes

• Checking only amounts.
• Treating a default worktag as a permanent fix for missing mapping.

05 · Advanced concepts

Extend to effective dates, inactive references and reversals. Finance and integration owners should agree the reconciliation rule.

IBM references

• IBM documentation — Connector for Workday Applications

Product explanations link to IBM sources. Scenarios and exercises are original Assetize guidance, not claims of executed lab procedures. Reviewed 2026-10-01.