Delivery Paths
Automated: Submit_Payroll_Input
The WWSPayroll service’s Submit_Payroll_Input operation adds and updates payroll input data from external systems. Toku posts one input per worker before your pay calculation runs. A trimmed, illustrative request:
Manual: EIB Spreadsheet Import
If your team prefers to review before anything lands in Workday, use an inbound Enterprise Interface Builder (EIB) integration instead: a spreadsheet template bound to the same Submit_Payroll_Input web service. Toku exports the populated file each pay period, and your payroll team uploads it through the EIB. See the Workday Web Services directory and Workday’s EIB documentation to validate both paths.If payroll runs outside Workday (Workday is HCM-only), the
Payroll_Interface service’s Put_External_Payroll_Input operation is used instead — the same one-deduction model, delivered to your external payroll provider’s interface.How the Amount Is Set
- The worker’s stablecoin election in Toku determines the amount for each pay period.
- Toku posts the input before each run, so one-off changes (paused elections, prorated periods) are handled automatically.
- The line item appears on the worker’s payslip under the dedicated Toku pay component, so payslips stay self-explanatory.
Guarantees
Reconciliation
After the run completes, Toku reads the payroll results, confirms each applied deduction, and releases the matching on-chain stablecoin payments. Any mismatch blocks settlement and is surfaced in the Toku dashboard before funds move.Next
Integration Overview
Back to the Workday integration overview
Worker Sync
How Toku reads your worker roster via RaaS
