> 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/archive/implementation-process-1.md).

# Implementation Process (single resort)

Payroll Export Definition and Implementation Process

*<mark style="color:red;">Please Note: Once the payroll export has been tested and moved into production, any change to the file will incur a new development fee</mark>*

<table data-header-hidden data-full-width="false"><thead><tr><th width="79"></th><th width="483"></th><th></th></tr></thead><tbody><tr><td></td><td><strong>Process Step</strong></td><td><strong>Responsible</strong></td></tr><tr><td>1</td><td>Capture Wage and Incentive Business Requirements</td><td>Resort and flaik Customer Success</td></tr><tr><td>2</td><td>Provide an Example of Payroll Export File</td><td>Resort</td></tr><tr><td>3</td><td>Provide details on any payroll export fields that are required: Paycodes, Jobcodes, Business Structures</td><td>Resort </td></tr><tr><td>4</td><td>Create Payroll Requirement based on example file and export fields required</td><td>Lauren</td></tr><tr><td>5</td><td>Define and document how flaik must be configured to support export field requirements</td><td>Lauren</td></tr><tr><td>6</td><td>Review Payroll Requirements</td><td>Lauren and Resort</td></tr><tr><td>7</td><td>Prepare Technical Requirement</td><td>Lauren</td></tr><tr><td>8</td><td>Approve Technical Requirement</td><td>Resort</td></tr><tr><td>9</td><td>Prepare End User Documentation</td><td>Lauren</td></tr><tr><td>10</td><td>Deliver Export </td><td>flaik Product Team</td></tr><tr><td>11</td><td>Initial Verification </td><td>Lauren</td></tr><tr><td>12</td><td>Resort Testing and Verfication</td><td>Resort</td></tr><tr><td>13</td><td>Approve for Production</td><td>Resort</td></tr><tr><td>14</td><td>Testing in Production</td><td>Resort</td></tr><tr><td>15</td><td>Resort Sign Off</td><td>Resort</td></tr><tr><td>16</td><td>Bug Fixes After Sign Off </td><td>flaik (no charge)</td></tr><tr><td></td><td><p>Changes due to new requirements after Sign Off (will incur</p><p>charge of ~$3000)</p></td><td>$3000 </td></tr><tr><td></td><td>New Payroll Integrations (one included with initial setup) additional interfaces</td><td>$4000</td></tr></tbody></table>

### **INTRODUCTION**

flaik integrates to your payroll system by sending instructor pay records in a .csv flat file.  This files can be sent automatically each day at 10pm using FTP or it can be manually created daily, weekly or fortnightly depending on your paroll software requirements.

### **EXAMPLE FILE**

1. **Example File** - flaik requires an example pay file of what you would like to have sent to  your payroll system. The example should include any hourly type pay records you want as well as examples of any incentive type pay you will use
2. **Field Description** - We will need to work through the file to provide an explanation of each field in your payroll file and where it is pulled or derived from. Values are either created by flaik lessons/incentives, added to lessons by the administrator (Jobcodes, paycodes, Departments, Business Structures, Accounting Strings) or hardcoded if the value is static.
3. **Frequency** - The file can contain 1 day, 7 days or 14 days worth of payroll records. If you would like the file daily it can be sent automatically with FTP

### **TESTING**

*Note: Once the export file and instructions are delivered, the resort is responsible for testing the file.*

1. **Deploy Code** - flaik will deploy payroll export functionality to your flaik staging server and notify you when it is available
2. **Setup Test Cases  (Resort)**- the resort should identify test cases they want to create in flaik  that touch on all types of hourly pay that have been set up (Teaching, Non-Teaching, Training and Private Request) and all types of incentives they will use (Staff, Metric, Head count). Once the test data is created it should then be downloaded from flaik and uploaded into the payroll system. Ideally these test cases will use data values that will accepted by the testing payroll server so you can successfully upload the file to validate the data.
3. **Export Test File -** Export a test payroll file and verifying the results in the .csv file
4. **Verify in Payroll System** - Upload the test file to your payroll system and validate that each of your unique requirements have been met. hourly pay rates and incentives appear as expected.
5. **UAT Sign-Off -** Sign-off on each of your resort specific requirements&#x20;

### **PRODUCTION VERIFICATION**

1. Once UAT Sign-off is complete flaik will move your code to production
2. A file export should be created, verified and uploaded to your payroll system
3. SFTP - If you desire an automatic file transfer using FTP/SFTP send flaik the FTP info&#x20;


---

# 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/archive/implementation-process-1.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.