> ## 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.

# Workday Worker Sync

> How Toku syncs your worker roster from Workday via a RaaS custom report

Toku keeps its worker roster in sync with Workday so stablecoin elections always map to the right person. Sync is read-only and runs through a **Reports-as-a-Service (RaaS)** custom report — a Workday report enabled as a web service — automatically after connection and on a rolling schedule.

## Endpoint

RaaS reports follow a standard URL format:

```text theme={null}
https://<host>/ccx/service/customreport2/<tenant>/<report_owner>/<Report_Name>?format=json
```

The `format` parameter also accepts `csv` and `xml`, and any report prompts pass as additional query parameters. Toku reads the worker demographics report your team creates during onboarding, authenticating with HTTP Basic as the ISU:

```bash theme={null}
curl -u "ISU_TOKU@acme_tenant" \
  "https://<host>/ccx/service/customreport2/acme_tenant/ISU_TOKU/Toku_Worker_Sync?format=json"
```

A trimmed example response — RaaS JSON always wraps rows in a `Report_Entry` array:

```json theme={null}
{
  "Report_Entry": [
    {
      "Employee_ID": "10023",
      "Worker": "Ada Lovelace",
      "Work_Email": "ada@yourcompany.com",
      "Country": "United States of America",
      "Currency": "USD",
      "Total_Base_Pay": "180000.00",
      "Worker_Status": "Active",
      "Pay_Group": "US Semi-Monthly"
    }
  ]
}
```

See the [Workday Web Services directory](https://community.workday.com/sites/default/files/file-hosting/productionapi/index.html) and this [RaaS reference](https://docs.workato.com/connectors/workday/workday_raas.html) to validate the URL format and response shape.

## What Toku Reads

| Field                  | Purpose                                                   |
| ---------------------- | --------------------------------------------------------- |
| `Employee_ID`          | Stable identifier used to match the worker across systems |
| `Worker`, `Work_Email` | Roster display and employee-portal invitations            |
| `Country`, `Currency`  | Determines payment rails and settlement currency          |
| `Total_Base_Pay`       | Validates election limits against compensation            |
| `Worker_Status`        | Marks departed workers inactive in Toku                   |
| `Pay_Group`            | Ties each worker to the right payroll calendar            |

## Sync Behavior

* **New workers** appear in Toku automatically once they show up in the report.
* **Updates** (name, email, compensation, pay group) flow through on the next sync.
* **Terminated workers** are marked inactive and stop receiving stablecoin payments.
* A manual sync can be triggered anytime from **Settings → Payroll Integrations** in Toku.

<Note>
  Worker sync never writes to Workday. The report is owned by your tenant — your team controls exactly which fields it exposes, and Toku only sees what the report returns.
</Note>

## Next

<CardGroup cols={2}>
  <Card title="Payroll Sync" icon="calendar" href="/integrations/workday/payroll-sync">
    How Toku tracks pay runs and payroll results
  </Card>

  <Card title="The Toku Deduction" icon="money-bill-transfer" href="/integrations/workday/deduction">
    How the deduction is applied as payroll input
  </Card>
</CardGroup>