Bank accounts of customers, suppliers and the company's own entities, verified before use, masked by default and audited on every read.
Objects are read through Workday web services and RaaS reports; the rows stay in Workday.
| Object | Read from | Fields the domain uses | Freshness |
|---|---|---|---|
| Settlement bank accounts | Get_Settlement_Bank_Accounts | Bank_Account_ID · IBAN · SWIFT · Status | live through web services; reports on schedule |
| Payments | Get_Payments | Payment_ID · Amount | live through web services; reports on schedule |
The first object above carries the strong keys; the standardised attributes come from the same rows. A bank account is master data with a verification record; a change creates a pending version that stays unusable until verified.
Writes go through the Workday web services (Put operations) with the reference id; each call returns the id or the error, logged beside the change.
| Interface | Used for | Result |
|---|---|---|
Put_Settlement_Bank_Account after verification | golden values approved for write-back: account; verification; usage | the id or error Workday returns, stored beside the change |
Write-back is off per object until a test write succeeds, and approval rules can require a person per object. Reconciliation compares the source row with the golden value on a schedule.
Workday security groups are mapped to Lima policies once; personal data stays under the HR policy.
Bank and payment details on
Other domains on Workday
The golden record reads the objects above in place. History the pivot needs at scale is landed in your lake by the Backbone, under the same keys, security and audit.
Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in Workday.
Yes. Write-back stays off per object until a test write succeeds; the golden view, the API and the pivots work from day one on reads.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.
