> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/payroll-export-configuration/resort-specific-info/sunvalley-and-snowbasin-kronos-ukg.md).

# Sunvalley and Snowbasin (Kronos/UKG)

## Overview

| Payroll System  | Kronos (UKG) |
| --------------- | ------------ |
| Files Used      | Timekeeping  |
| Transfer Method | Manual       |
| Days to Include | 7 days       |
| Header Row      | Yes          |

## flaik UI Fields Required

<table><thead><tr><th width="323.370361328125">FIELDS REQUIRED</th><th>Kronos Name</th></tr></thead><tbody><tr><td>Paid Activity -> Jobcode</td><td>Description</td></tr><tr><td>Paid Activity -> Paycode</td><td>Not Required</td></tr><tr><td>Paid Activity -> Business Structure</td><td>Not Required</td></tr><tr><td>Incentive -> Paycode</td><td>Not Required</td></tr></tbody></table>

## Timekeeping File Format

<table><thead><tr><th width="249.29638671875">Column Name</th><th>flaik Source</th></tr></thead><tbody><tr><td>ActivityDate</td><td>Paid Activity → Date (date the lesson(s) occurred)</td></tr><tr><td>IPCode</td><td>Staff → Staff ID</td></tr><tr><td>EmployeeID</td><td>Staff → Payroll ID</td></tr><tr><td>Description</td><td>Paid Activity → Job Code</td></tr><tr><td>PayPeriodEndDate</td><td>The date that is selected in Timekeeping in the UI that the report is being pulled from</td></tr><tr><td>TotalPay</td><td>Gross pay for this activity (base wage + applicable incentives).</td></tr><tr><td>TotalWorkHours</td><td>Hours worked for this activity.</td></tr><tr><td>ROP</td><td>Rate of Pay = TotalPay ÷ TotalWorkHours. Includes incentives averaged in.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/payroll-export-configuration/resort-specific-info/sunvalley-and-snowbasin-kronos-ukg.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.