Skip to main content
Each pay period, exactly one Toku line item is reflected per participating worker, using Rippling’s pay-input APIs. This is the only write Toku performs against your Rippling account.

​
How It’s Applied

Rippling’s documented write path for adding pay line items to a payroll run is its earnings inputs operations — list, create, and delete earnings inputs, plus List earning types. Rippling does not expose a public generic “create deduction” REST endpoint (deductions appear read-only inside worker payroll records), so the Toku line item is reflected on the pay run through these pay-input operations, using a dedicated earning type configured with Rippling during implementation. Toku first matches the participating worker through the workers resource:
Then, before each run, Toku creates the worker’s earnings input on the payroll run via the create earnings input operation. Rippling’s endpoint-level reference for the earnings-input operations requires a Rippling developer sign-in — see the REST API documentation to validate them.

​
How the Amount Is Set

  • The worker’s stablecoin election in Toku determines the amount for each pay period.
  • Toku recalculates and updates the pay input before each run, so one-off changes (paused elections, prorated periods) are handled automatically.
  • The line item appears on the worker’s pay with the Toku-dedicated earning type, so pay statements stay self-explanatory.

​
Guarantees

Toku never modifies compensation, tax withholding, benefits, or existing pay items in Rippling — the scope of write access is limited to the Toku line item itself.

​
Reconciliation

After the payroll run is finalized, Toku reads the worker payroll records for the run, confirms each applied Toku line item, 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 Rippling integration overview

Worker Sync

How Toku reads your worker roster