> 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/mt.-buller-ch21.md).

# Mt. Buller (CH21)

## Overview

<table data-header-hidden><thead><tr><th width="220.77783203125">EXPORT FILE META DATA</th><th width="402.7777099609375"></th><th data-hidden></th><th data-hidden></th><th data-hidden></th></tr></thead><tbody><tr><td>Payroll Contact</td><td>Ross</td><td></td><td></td><td></td></tr><tr><td>Payroll System</td><td>CH21</td><td></td><td></td><td></td></tr><tr><td>Files Required</td><td>Timekeeping - Wages and Incentives combined in a single file</td><td></td><td></td><td></td></tr><tr><td>Header Row</td><td>NO HEADER</td><td></td><td></td><td></td></tr><tr><td>SFTP</td><td>NO - Manual</td><td>What method is use</td><td></td><td></td></tr><tr><td>Payroll Frequency</td><td>Weekly - 7 days worth of date in the payroll file</td><td></td><td></td><td></td></tr><tr><td>File Naming Requirement</td><td>Require a .dat file (currently flaik only offers .csv)</td><td></td><td></td><td></td></tr><tr><td>Transfer Time</td><td>Currently Monday at 2:15 pm</td><td></td><td></td><td></td></tr></tbody></table>

## Payroll Export Fields

| Paid Activity -> Paycode | 110 - Regular PAy              |
| ------------------------ | ------------------------------ |
| Incentive -> Paycode     | 315 - Allowance, 360 Incentive |
| Paid Activity -> Jobcode | RTP Activity Code              |

## Timekeeping File Format

### Wage Payline Format (Regular Pay - Paycode 110)

<table><thead><tr><th width="158.44439697265625">Vendor Name</th><th width="64.33319091796875">Width</th><th width="120.3333740234375">Format</th><th>flaik origin of data for file</th></tr></thead><tbody><tr><td>Whitespace</td><td>8</td><td></td><td></td></tr><tr><td>Staff No.</td><td>5</td><td>Left Align</td><td>Staff Profile -> Payroll ID</td></tr><tr><td>Whitespace</td><td>13</td><td></td><td></td></tr><tr><td>Pay Period</td><td>6</td><td>DDMMYY</td><td>Apr 10: All Activities on date report is created rather than date activity occured<br>Timekeeping Report Date: DDMMYY</td></tr><tr><td>Whitespace</td><td>4</td><td></td><td></td></tr><tr><td>Pay Code</td><td>3</td><td></td><td>Paid Activity -> Paycode</td></tr><tr><td>Whitespace</td><td>1</td><td></td><td></td></tr><tr><td>Hardcoded String</td><td>4</td><td>"0000"</td><td></td></tr><tr><td>Activity Code</td><td>4</td><td></td><td>Paid Activity -> Jobcode</td></tr><tr><td>Hardcoded String</td><td>2</td><td>"00"</td><td></td></tr><tr><td>Work Hours</td><td>4</td><td>HHMM</td><td>Apr10: Wage lines should be grouped and the Work Hours Summed if all of these things are identical [Payroll ID | Pay Code | Activity Code | Hourly Wage]<br>Length of Paid Activity 2 hours and 30 minutes = 0250</td></tr><tr><td>Whitespace</td><td>1</td><td></td><td></td></tr><tr><td>Hardcoded String</td><td>2</td><td>"00"</td><td></td></tr><tr><td>Hourly Wage</td><td>4</td><td>DDCC</td><td>Staff Profile -> Hourly Wage</td></tr></tbody></table>

### Incentive Payline Format (Incentive - Paycode 360)

<table><thead><tr><th width="161.22222900390625">Whitespace</th><th width="63.4444580078125">8</th><th width="117"></th><th></th></tr></thead><tbody><tr><td>Staff No.</td><td>5</td><td>Left Align</td><td>Staff Profile -> Payroll ID</td></tr><tr><td>Whitespace</td><td>13</td><td></td><td></td></tr><tr><td>Pay Period</td><td>6</td><td>DDMMYY</td><td>Apr 10: All Incentives on date report is created rather than date activity occured<br>Timekeeping Report Date: DDMMYY</td></tr><tr><td>Whitespace</td><td>4</td><td></td><td></td></tr><tr><td>Pay Code</td><td>3</td><td></td><td>Incentive -> Paycode</td></tr><tr><td>Whitespace</td><td>1</td><td></td><td></td></tr><tr><td>Hardcoded String</td><td>4</td><td>"0000"</td><td></td></tr><tr><td>Activity Code</td><td>4</td><td></td><td>Paid Activity -> Jobcode</td></tr><tr><td>Hardcoded String</td><td>2</td><td>"00"</td><td></td></tr><tr><td>Work Hours</td><td>4</td><td></td><td>Apr10: Incentive lines should be grouped and the Work Hours Summed if all of these things are identical [Payroll ID | Pay Code | Activity Code | Hourly Wage]<br>Length of Paid Activity 2 hours and 30 minutes = 0250</td></tr><tr><td>Whitespace</td><td>1</td><td></td><td></td></tr><tr><td>Hardcoded String</td><td>2</td><td>"00"</td><td></td></tr><tr><td>Hourly Wage</td><td>4</td><td></td><td>Hourly Amount of Incentive / Allowance</td></tr></tbody></table>

## Requirements

* Fixed width spacing rather than .csv
* Combine Wage Lines - should be grouped and the Work Hours Summed if all of these things are identical \[Payroll ID | Pay Code | Activity Code | Hourly Wage]
* Combine Incentive Lines - should be grouped and the Work Hours Summed if all of these things are identical \[Payroll ID | Pay Code | Activity Code | Hourly Wage]


---

# 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/mt.-buller-ch21.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.