> 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/ukg.md). # UKG This is the standard UKG timekeeping import that flaik produces. There are two files — a **Wages** punch file (dual punch) and an **Incentives** paycode-edit file — delivered by SFTP (PGP encryption where required). > This is a generic reference of the layout flaik generates today. Set it up and test it on your flaik site; if UKG needs a different layout after your interface review, contact flaik and we'll adjust the file. ## Wages file — Dual Punch One row per work segment, each row carrying a complete punch pair (In + Out). An instructor with several segments in a day gets one row per segment. The file has **30 columns** — the full list is below. Only the columns marked **Yes** carry data; the rest are always present in the header but sent blank. | # | Column | Sent? | Value / flaik source | | -- | -------------------------- | ----- | ----------------------------------------------- | | 1 | `PersonNumber` | Yes | Staff Profile → Payroll ID | | 2 | `InDate` | Yes | Segment date (`yyyy-mm-dd`) | | 3 | `InTime` | Yes | Segment start (`HHMM`, 24-hour) | | 4 | `InOverrideType` | Yes | Hardcoded `Punch In` | | 5 | `InBusiness StructureJOb` | Yes | Business Structure, formatted `/Employee` | | 6 | `InLCL1` | Yes | Wage Position ID | | 7 | `InLCL2` | Blank | | | 8 | `InLCL3` | Blank | | | 9 | `InLCL4` | Blank | | | 10 | `InLCL5` | Blank | | | 11 | `InLCL6` | Blank | | | 12 | `InWorkRule` | Blank | | | 13 | `InTimeZone` | Blank | | | 14 | `InComment1` | Blank | | | 15 | `InComment1Note1` | Blank | | | 16 | `OutDate` | Yes | Segment date (`yyyy-mm-dd`) | | 17 | `OutTime` | Yes | Segment end (`HHMM`, 24-hour) | | 18 | `OutOverrideType` | Yes | Hardcoded `Punch Out` | | 19 | `OutBusiness StructureJOb` | Yes | Matches `InBusiness StructureJOb` | | 20 | `OutLCL1` | Yes | Matches `InLCL1` | | 21 | `OutLCL2` | Blank | | | 22 | `OutLCL3` | Blank | | | 23 | `OutLCL4` | Blank | | | 24 | `OutLCL5` | Blank | | | 25 | `OutLCL6` | Blank | | | 26 | `OutWorkRule` | Blank | | | 27 | `OutTimeZone` | Blank | | | 28 | `OutComment1` | Blank | | | 29 | `OutComment1Note1` | Blank | | | 30 | `DeductionRuleToCancel` | Blank | | Within a row, the In and Out business structure and Position ID always match. **Example** (full rows — every one of the 30 columns shown; all values illustrative): ``` PersonNumber,InDate,InTime,InOverrideType,InBusiness StructureJOb,InLCL1,InLCL2,InLCL3,InLCL4,InLCL5,InLCL6,InWorkRule,InTimeZone,InComment1,InComment1Note1,OutDate,OutTime,OutOverrideType,OutBusiness StructureJOb,OutLCL1,OutLCL2,OutLCL3,OutLCL4,OutLCL5,OutLCL6,OutWorkRule,OutTimeZone,OutComment1,OutComment1Note1,DeductionRuleToCancel 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,,,,,,,,,, ``` ## Incentives file — Paycode Edit One row per employee, per pay code, per business structure. Amounts are dollar values. **6 columns**, all populated. | # | Column | Value / flaik source | | - | ------------------------- | ------------------------------------------------------------------------------ | | 1 | `Person Number` | Staff Profile → Payroll ID | | 2 | `Effective Date` | Paid Activity → Date (`yyyy-mm-dd`) | | 3 | `Pay Code` | Incentive → Paycode | | 4 | `Amount` | Calculated incentive dollars for that employee + pay code + business structure | | 5 | `Business Structures/Job` | Business Structure, formatted `/Employee` | | 6 | `Labor Category Level Id` | Wage Position ID | **Example** (all values illustrative): ``` Person Number,Effective Date,Pay Code,Amount,Business Structures/Job,Labor Category Level Id 900001,2026-01-15,Incentive - Combined,45,100200/Employee,P900001 900001,2026-01-15,Incentive - USA,30,100200/Employee,P900001 900002,2026-01-15,Incentive - Combined,52.50,100300/Employee,P900002 ``` *All employee numbers, position IDs, cost-centre codes, pay codes, and amounts shown are illustrative — not real 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/ukg.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.