# Killington (Paycom)

## Overview

Killington is transitioning to Paycom for Summer 2025.

<table><thead><tr><th width="265.8148193359375">Payroll Contact</th><th></th></tr></thead><tbody><tr><td>Payroll System</td><td>Paycom</td></tr><tr><td>File Types</td><td>Wages</td></tr><tr><td>Header Row</td><td>Not Included</td></tr><tr><td>Payroll Frequency</td><td>Daily</td></tr><tr><td>File Naming Requirement</td><td>TBA?</td></tr><tr><td>Transfer Type</td><td>FTP or manual transfer?</td></tr></tbody></table>

## Payroll Export Fields

<table><thead><tr><th width="207.07403564453125">Vendor Field</th><th>flaik Field</th><th>flaik Config Location</th></tr></thead><tbody><tr><td>Labor Allocation -> Position Code</td><td>Job Code</td><td>Paid Activity</td></tr><tr><td>Deparment Code</td><td>Business Structure</td><td>Paid Activity</td></tr></tbody></table>

## Wage File Format

<table><thead><tr><th width="253.25927734375">Vendor Field Name</th><th>flaik Source Field Name</th></tr></thead><tbody><tr><td>Employee ID</td><td>Payroll ID</td></tr><tr><td>Department Code</td><td>Paid Activity -> Business Structure</td></tr><tr><td>Date (MM/DD/YYYY)</td><td>Paid Activity -> Date</td></tr><tr><td>Punch Time (Military Time)</td><td>Start or End Time of Paid Activity<br>*****Leading Zero Required for single digit hours</td></tr><tr><td>Punch Type</td><td>First punch of the day = ID<br>First punch out = OB<br>Next in = IB, then alternate OB/IB<br>Last out = OD</td></tr><tr><td>Earning Code</td><td>blank</td></tr><tr><td>Tax Profile Code</td><td>blank</td></tr><tr><td>Comments</td><td>blank</td></tr><tr><td>Labor Allocation</td><td><p>Paid Activity -> Jobcode Column I (Labor Allocation): needs to be in this format 16S01 (hard coded)|Subsidiary code (KL or PICO)|Position Code|UNA (hard coded). </p><p></p><p>Subsidiary and Position code could change based on the location and lesson type, but the first and last hard coded items will always be the same.</p></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/payroll-export-configuration/resort-specific-info/killington-paycom.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.