Skip to main content
Each pay cycle, Toku applies one dedicated deduction per participating worker, using ADP’s Pay Data Input event API. This is the only write Toku performs against your ADP account.

Endpoint

Before posting, Toku calls the API’s meta endpoint — GET /events/payroll/v1/pay-data-input.modify/meta (filterable by companyCode/fileNumber) — to confirm the Toku deduction code is valid for your payroll group. It then submits a pay data batch:
A trimmed request envelope:
The scope used is /payroll/payrollManagement/payrollProcessing/payDataInputManagement/pay-data-input.modify. See ADP’s reference to validate the call: Pay Data Input v1 API Explorer and ADP’s sample payloads on GitHub.

How the Amount Is Set

  • The worker’s stablecoin election in Toku determines the amount for each pay cycle.
  • Toku recalculates and posts the deduction before each run, so one-off changes (bonuses, prorated periods, paused elections) are handled automatically.
  • The line item appears on the worker’s pay statement under the Toku deduction code configured during onboarding, so payslips stay self-explanatory.

Guarantees

ADP accepts a pay data batch only while the pay cycle is in the Entering Payroll Information or Correcting Input state, and a single invalid entry fails the entire multi-employee batch. Toku validates every entry against the meta endpoint before posting and retries per-employee, so one worker’s issue never blocks the rest of the run.

Reconciliation

After the payroll is processed, Toku reads the finalized payroll output, 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 ADP integration overview

Employee Sync

How Toku reads your worker roster