> 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/alterra.md). # Alterra
Payroll System Kronos/UKG
Transfer MethodSFTP with PGP Encryption
Files Used

Wages

Incentives

FrequencyDaily
Time10:00 pm (local time)
## Overview | | | | ------------------- | --------------------------------------------------------------------------------------------------------- | | **Payroll System** | Workday | | **Transfer Method** | SFTP with PGP encryption | | **Files** | Wages (Dual Punch) · Incentives (Paycode Edit) | | **Frequency** | Daily, 10:00 pm local | | **Filenames** | `dual_punch___.csv` · `paycode_edit___.csv` | flaik produces the two files below. The Position IDs used to map each instructor to the correct wage are supplied by Workday through the Workday → flaik interface. ## Wages file — Dual Punch One row per work segment; each row carries a complete punch pair (In + Out). An instructor with several segments in a day gets one row per segment. Only the columns below are populated — every other column in the header (`LCL2`–`LCL6`, `WorkRule`, `TimeZone`, `Comment1`, `Comment1Note1`, `DeductionRuleToCancel`) is always left blank. | Column | flaik source / value | | ------------------------------------------------------ | --------------------------------------------------------------- | | `PersonNumber` | Staff Profile → Payroll ID | | `InDate` / `OutDate` | Segment date (`yyyy-mm-dd`) | | `InTime` / `OutTime` | Segment start / end (`HHMM`, 24-hour) | | `InOverrideType` / `OutOverrideType` | Hardcoded `Punch In` / `Punch Out` | | `InBusiness StructureJOb` / `OutBusiness StructureJOb` | Paid Activity → Business Structure, formatted `/Employee` | | `InLCL1` / `OutLCL1` | Staff → Wage Position ID | Within a row, the In and Out business structure and Position ID always match. ``` PersonNumber,InDate,InTime,InOverrideType,InBusiness StructureJOb,InLCL1, ... ,OutDate,OutTime,OutOverrideType,OutBusiness StructureJOb,OutLCL1, ... 900001,2026-01-15,0830,Punch In,100100/Employee,P900001, ... ,2026-01-15,1230,Punch Out,100100/Employee,P900001, ... 900001,2026-01-15,1230,Punch In,100200/Employee,P900001, ... ,2026-01-15,1630,Punch Out,100200/Employee,P900001, ... 900002,2026-01-15,0900,Punch In,100300/Employee,P900002, ... ,2026-01-15,1500,Punch Out,100300/Employee,P900002, ... ``` *All values shown are illustrative — not real employee, position, or cost-centre data.* ## Incentives file — Paycode Edit One row per employee, per pay code, per business structure. Amounts are dollar values. | Column | flaik source / value | | ------------------------- | ------------------------------------------------------------------------------ | | `Person Number` | Staff Profile → Payroll ID | | `Effective Date` | Paid Activity → Date (`yyyy-mm-dd`) | | `Pay Code` | Incentive → Paycode (e.g. `Incentive - SKS Combined`, `Incentive USA`) | | `Amount` | Calculated incentive dollars for that employee + pay code + business structure | | `Business Structures/Job` | Paid Activity → Business Structure, formatted `/Employee` | | `Labor Category Level Id` | Staff → Wage Position ID | ``` Person Number,Effective Date,Pay Code,Amount,Business Structures/Job,Labor Category Level Id 900001,2026-01-15,Incentive - SKS Combined,45,100200/Employee,P900001 900001,2026-01-15,Incentive USA,30,100200/Employee,P900001 900002,2026-01-15,Incentive - SKS Combined,52.50,100300/Employee,P900002 ``` *All values shown are illustrative — not real employee, position, or cost-centre data.* --- # 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/alterra.md?ask=&goal= ``` `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.