> ## Documentation Index
> Fetch the complete documentation index at: https://docs.toku.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Rippling Payroll Sync
> How Toku tracks payroll runs and pay periods in Rippling
Toku tracks your Rippling payroll calendar so the Toku line item is always applied to the right payroll run — and so on-chain delivery lines up with your pay date.
## Operations
Toku uses two documented, read-oriented operations from the [Rippling REST API](https://developer.rippling.com/documentation/rest-api):
| Operation | What it returns |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **List payroll runs** | Payroll runs with their pay periods (`PayrollRun`, `PayrollRunPayPeriod` schemas) |
| **List worker payroll records** | Per-worker line items on a run (`WorkerPayrollRecord`, containing `WorkerPayrollEarning`, `WorkerPayrollDeduction`, `WorkerPayrollGarnishment`, `WorkerPayrollTax`) |
A trimmed, representative payroll run shape:
```json theme={null}
{
"results": [
{
"id": "prun_8a77c3de91b4",
"pay_period": {
"start_date": "2026-07-01",
"end_date": "2026-07-15"
},
"status": "FINALIZED"
}
]
}
```
This is representative, not an exhaustive schema. Rippling's endpoint-level reference for these operations requires a Rippling developer sign-in — see the [REST API documentation](https://developer.rippling.com/documentation/rest-api) to validate them.
## What Toku Reads
| Data | Purpose |
| ---------------------------- | --------------------------------------------------------------- |
| Payroll run `id` | Ties each Toku pay cycle to the exact Rippling payroll run |
| Pay period start / end dates | Determines which elections apply to the run |
| Run status | Confirms the run is finalized before Toku settles |
| Worker payroll records | Reconciles the applied Toku line item against each worker's pay |
## Sync Behavior
* Upcoming payroll runs appear in the Toku dashboard as soon as they exist in Rippling.
* When a run is finalized, Toku reads the worker payroll records, reconciles the Toku line item on each participating worker's pay, and releases the corresponding stablecoin payments.
* Runs outside your regular pay schedule are detected and skipped by default (configurable during onboarding).
Payroll sync is read-only. Toku never creates, calculates, or submits payroll runs in Rippling — your team keeps full control of running payroll.
## Next
How the Toku line item is reflected on the pay run
OAuth 2.0 scopes and token handling