> 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/setting-up-paycodes-and-business-structure.md).

# Setting Up Paycodes and Business Structure

STATUS: Work In Progress Document

### Setup List

1. **Paycodes Upload List** - Upload list of Paycodes
2. **Business Structures Upload List** - Upload list of Business Structures
3. **Add Paycodes to Activities  and Incentives**- setup paycodes relevant to your resort in flaik on each paid activity and/or incentives/commissions that should be sent to the payroll system. Note resorts that punch In and Out will not need to add these to Paid Activities.
4. **Business Structure to Activities** - setup Business Structure strings relevant to your resort in flaik on each paid activity that should be sent to the payroll system

{% hint style="info" %}
Please find your resorts paycodes and business structures: 

SRS//HRIS Integration site:

<https://alterramtnco.sharepoint.com/sites/SRS-HRIS/SitePages/SRS%20Instructor%20Payroll.aspx>
{% endhint %}

### New flaik Fields

<table data-header-hidden><thead><tr><th></th><th></th><th data-hidden></th></tr></thead><tbody><tr><td><strong>Field Name</strong></td><td><strong>Location</strong></td><td></td></tr><tr><td>Paycodes</td><td>Paid Activity &#x26; Incentives </td><td></td></tr><tr><td>Business Structure</td><td>Paid Activity</td><td></td></tr><tr><td>Payroll ID (Workday ID)</td><td>Instructor Profile -> Payroll ID</td><td></td></tr><tr><td>Secondary Payroll ID (Previous Payroll ID)</td><td>IInstructor Profile -> Secondary Payroll ID</td><td></td></tr><tr><td>Wage Position IDs (teaching, non-teaching, training) </td><td>Instructor Profile -> Wage Position IDs </td><td></td></tr></tbody></table>

### 1 | Paycodes Upload

<mark style="color:blue;">**Admin -> General Settings -> Timekeeping -> Paycodes**</mark>

Upload a list of your paycodes. Please assign a unique ID to each paycode.

![](https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2FVpOiXqrqOoQPFE4eJDrs%2Fimage.png?alt=media\&token=8d798947-f644-4300-ae32-d4368a39d048)

### 2 | Business Structures Upload

<mark style="color:blue;">**Admin -> General Settings -> Timekeeping -> Business Structure**</mark>

Upload a list of your Business Structures. Please assign a unique ID to each paycode.

![](https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2Fry6oX2FVuBAhbeRO1yGb%2Fimage.png?alt=media\&token=a6bd772e-3f6d-4b7e-940b-dfa3228e36de)

### 3 | Configure Paycodes on Incentives

#### Paid Activities -> Paycode <mark style="color:red;">-> Leave Paycode blank</mark>

<mark style="color:blue;">**Product Settings -> Paid Activities -> Alterra Kronos Settings -> Paycode**</mark>

This field is no longer passed to Kronos in the payroll file. It can be left blank. If there is already a value there (Hourly USA, Regular Hourly Pay CAN) is does not need to be removed, it is just ignored.

The base hourly type paycode will be automatically applied to the hourly type pay items in the payroll system (Hourly USA, Regular Hourly Pay CAN) based on the employees configuration, country and Position ID.

<figure><img src="https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2FGu7A1YF8ZXuxSigtnm67%2Fimage.png?alt=media&amp;token=148ee371-ef5f-4a71-9376-f91c8d51814b" alt=""><figcaption></figcaption></figure>

#### Incentives -> Paycode

All incentives will need to have the correct paycode attached

<mark style="color:blue;">**Admin -> General Settings -> Timekeeping -> Incentives -> Paycode**</mark>&#x20;

<figure><img src="https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2FFOBEPcqkP473IseiSaoX%2FScreen%20Shot%202022-10-11%20at%208.55.22%20PM.png?alt=media&amp;token=df9f8dd5-500a-46f8-930d-79bf5c31e65f" alt=""><figcaption></figcaption></figure>

### 4 | Configure Business Structures

Add a business structure to the paid activity. This will be included on all pay lines in the Pay Code Edit File and the Punch File (for resorts who don't Punch elsewhere)

![](https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2F2i3hTrwHIrBmn0VM6MRD%2Fimage.png?alt=media\&token=799d1d95-6985-488a-95bd-5276d5dcc3c8)

### 5 | Manually Export the Payroll Files

**Incentives** File (Incentives/Commissions)

**Wages Only** File (for resorts who don't punch)&#x20;

<figure><img src="https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2FPXv3WR0OkXHrQbK6x6MM%2Fimage.png?alt=media&amp;token=e50a6e5c-e5d5-445b-be17-183acf66b5ff" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}

#### Questions?&#x20;

Alterra SRS//HRIS Dat Integration Sharepoint-> <https://alterramtnco.sharepoint.com/sites/SRS-HRIS>\
Workday HR/Payroll Knowledge Base ->\
<https://enterprise.alterra.support/support/solutions>

flaik Application Support -> <resortsupport@flaik.com>
{% endhint %}


---

# 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/setting-up-paycodes-and-business-structure.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.