> 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/4-or-testing-and-sign-off.md).

# 4 | Testing and Sign-Off

This guide walks resorts through how to test the flaik payroll export before going live. All testing must be completed and signed off by the resort.

### Pre-Requisites

Before testing can begin:

* Please configure any necessary **Paycodes, Jobcodes, and Business Structures** in the environment that will be used for testing. 
* These values must be added to all of the relevant **Paid Activities** and **Incentives** that will be used during testing.
* You can use the "Download Paid Activities" link in the Paid Activity configuration screen to ensure all of the values are filled in. 
* A **test employee** must be created in:
  * The payroll system (with a known payroll ID)
  * The flaik staging environment (with the **same payroll ID**)

### Choosing Test Scenarios

The number of test scenarios depends on how your payroll is structured:

#### Single Base Wage Rate

If instructors are only paid one hourly rate and do not receive incentives:

* One simple test case is sufficient
* Example: one 6-hour lesson assigned to the test employee

#### Multiple Wage Types or Incentives

If your resort uses different pay types or includes incentive pay, you must test each:

**Recommended Minimum Test Case** **John Doe**:

* Teaches a 3-hour regular lesson (Teaching)
* Attends 2 hour of training (Training)
* Works 1.5 hour helping (Non-Teaching)
* Teaches a 1-hour private request (Private Request)
* Earns a $10/hour incentive for the Private Request lesson

These activities must use the same Paycodes, Jobcodes, and Business Structures configured in both systems.

### Steps for Testing

> **Important:** All pay lines must be finalized in flaik before exporting the payroll file. Only finalized pay records are included in the payroll export.

**Configure Payroll Export fields in flaik**

* Create Paid Activities for each wage type in use
* Assign the correct Paycode, Jobcode, and Business Structure
* Create Incentives and configure Paycodes if required

**Create/Choose a Test Instructor**

* ensure a payroll ID and wage rates are set up for that instructor
* Schedule that instructor for a date

**Creating Lessons**

* add the relevant lessons to the test instructor
* Approve the lessons
* Finalise the lessons

**Export the payroll file**

* Generate the .CSV file from the flaik Timekeeping screen using the links on the bottom right of the screen
* verify the file looks correct in excel being careful not to strip any leading zeroes that might be required

**Upload and verify in the payroll system**

* Upload the flaik .csv file (s)  to your payroll system
* Confirm that all wage/pay types and incentives (if used) appear correctly
* Verify no values are missing or miscategorized

**Sign-off**

* Once everything is correct, notify flaik that your export is tested and will not require any adjustments

### Notes

* Resorts are responsible for coordinating and executing testing
* Testing is complete only when all relevant scenarios are verified


---

# 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/4-or-testing-and-sign-off.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.