> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# UKG Ready Changelog

> Release history for the UKG Ready connector. Each version lists what changed and which actions were affected.

<Card title="UKG Ready connector" icon="arrow-left" href="/connectors/ukg-ready" horizontal>
  Back to the connector overview, authentication methods, and actions.
</Card>

<Update label="v2.0.0" description="29 Sept 2026">
  `breaking` `bug-fix`

  The option to pick cost centers up from external rules is no longer offered when creating or updating a rate table. UKG accepts that setting and always stores it as off, so a request that asked for it reported success while changing nothing; removing it makes clear the behaviour is not available rather than silently ignored.

  <AccordionGroup>
    <Accordion title="Changed · 2 actions updated">
      `ukg-ready_create_rate_table`, `ukg-ready_update_rate_table`
    </Accordion>
  </AccordionGroup>
</Update>

<Update label="v1.6.0" description="29 Sept 2026">
  `new-feature`

  Adds native inbound webhooks through UKG Ready Webhook Subscriptions. Each connection now shows a Native Webhook URL and a Webhook Auth Token; paste the URL as the subscription Endpoint URL and the token as its Bearer token, because UKG Ready drops URL query strings when it sends events. A setup guide covers creating the subscription and choosing payload fields.
</Update>

<Update label="v1.5.1" description="28 Sept 2026">
  `description-fix`

  Linking a rate table to another now explains what the API actually requires: the alternate tables are stored only when an external table is named in the same create request and at least one of the three positional slots carries a table, so a request that sends the operators alone is accepted and stores nothing. Rate schedule updates state that a row's basis cannot be changed there — a differing basis is discarded while the new rate is still applied, which would leave a per-unit rate charged per hour — and that the way to change it is to delete the row and recreate it. Timesheet actions explain that reopen and correct depend on a pay period having been closed by payroll and should be treated as available only when the timesheet lists them. Rate table currency now names the action that reveals whether multi-currency is enabled for the company, and the rate table list warns that each entry carries a long download link so it should be paged when looking a table up by name.

  <AccordionGroup>
    <Accordion title="Changed · 5 actions updated">
      `ukg-ready_create_rate_table`, `ukg-ready_list_rate_tables`, `ukg-ready_timesheet_action`, `ukg-ready_update_rate_table`, `ukg-ready_update_rate_table_schedule`
    </Accordion>
  </AccordionGroup>
</Update>

<Update label="v1.5.0" description="24 Sept 2026">
  `bug-fix` `description-fix` `new-actions`

  A timesheet action no longer fails when the optional comment is left out. Timesheet actions also explain that the actions a timesheet will accept depend on its state and are listed on the timesheet itself, so a refused action is a state conflict rather than a permissions problem. Rate schedule updates now ask only for the rate items, because a row's basis is fixed when the row is created and a different basis sent on an update is ignored while the new rate is still applied — a rate meant per unit would otherwise be charged per hour — so a basis is changed by deleting the row and recreating it. Creating a rate table likewise asks only for a name, and a rate row only for its rate items. A rate table's external and alternate table links are set when the table is created, using the full three-slot form the API documents, and cannot be changed afterwards; the new Get Rate Table action returns a single table together with those links, which the rate table list leaves out entirely. The option to include cost centers from external rules is described as commonly not stored whatever is sent, so it should be read back before being reported as enabled.

  <AccordionGroup>
    <Accordion title="Added · 1 new action">
      `ukg-ready_get_rate_table`
    </Accordion>

    <Accordion title="Changed · 5 actions updated">
      `ukg-ready_create_rate_table`, `ukg-ready_create_rate_table_schedule`, `ukg-ready_timesheet_action`, `ukg-ready_update_rate_table`, `ukg-ready_update_rate_table_schedule`
    </Accordion>
  </AccordionGroup>
</Update>

<Update label="v1.4.3" description="23 Sept 2026">
  `bug-fix` `description-fix`

  Employee timesheets are now generally available, so the timesheet submit, approve, reject, reopen and correct operations can be reached from an employee and pay period rather than needing an internally sourced id. Extra-pay time entries document that they accept only a date and an amount, and that any other field is reported as a security violation rather than as a field error. Cost center lookups state that the configured trees cannot be discovered and that an index reported as not used simply means that tree is not configured, so an index is better taken from existing time entry or rate schedule data than found by scanning. Rate table currency no longer claims a specific cause for being ignored and states that the company's configured currency may be used regardless. Base compensation explains that an earning rejected for auto-pay reports the same message as one that does not exist, and the two compensation history actions now say which covers one employee and which covers everyone.

  <AccordionGroup>
    <Accordion title="Changed · 10 actions updated">
      `ukg-ready_batch_update_time_entries`, `ukg-ready_create_employee_base_compensation`, `ukg-ready_create_rate_table`, `ukg-ready_list_compensation_history`, `ukg-ready_list_employee_compensation_history`, `ukg-ready_list_employee_timesheets`, `ukg-ready_lookup_cost_centers`, `ukg-ready_timesheet_action`, `ukg-ready_update_employee_base_compensation`, `ukg-ready_update_rate_table`
    </Accordion>
  </AccordionGroup>
</Update>

<Update label="v1.4.2" description="21 Sept 2026">
  `description-fix`

  Corrected action descriptions across rate tables, time entries and base compensation to match how UKG Ready actually behaves. Batch time-entry updates now explain that both modes replace a date's entries rather than adding to them, and that clock times without a UTC offset are read as UTC. Rate table actions document the 20-character name limit, the settings UKG stores only under certain company configuration, the row-ordering rule for rate rows, and that a rate row's type is fixed once created. Base compensation documents that the effective date cannot be changed after creation, that only one record per date is allowed, and that auto-pay accepts only auto-pay eligible earnings. Paging limits and cost-center tree behaviour are now stated, and the overtime request action explains that it records planned overtime for approval rather than worked hours.
</Update>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.