> 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/cardrona-day-force.md).

# Cardrona (Day Force)

### Cardrona (Dayforce)

#### Overview

| Field                | Value                              |
| -------------------- | ---------------------------------- |
| Payroll System       | Ceridian Dayforce                  |
| Payroll Contact      | Mandy Fugler (RealNZ)              |
| Files Used           | Wages, Incentives, Leave (TAFW)    |
| Frequency            | Daily                              |
| Lookback Window      | 14 days back, including day of run |
| Header Row           | Yes (all files)                    |
| Wages File Name      | `Flaik_EmployeePunchImport.csv`    |
| Incentives File Name | `Flaik_EmployeePayAdjust.csv`      |
| Leave File Name      | `Flaik_EmployeeTAFW.csv`           |
| Transfer Method      | TBA                                |

#### Wages Export File Format

| Column Name           | Sample Data              | flaik Source Field                        |
| --------------------- | ------------------------ | ----------------------------------------- |
| EmployeeXrefCode      | C288                     | Staff → Payroll ID                        |
| StartTime             | 2026-05-11T09:00:00      | Paid Activity → Start Time                |
| EndTime               | 2026-05-11T11:00:00      | Paid Activity → End Time                  |
| NetHours              | 2                        | Calculated = End Time minus Start Time    |
| Operation             | insert                   | Hardcoded to "insert"                     |
| JobXrefCode           | SNOW\_SPORTS\_INSTRUCTOR | Paid Activity → Jobcode                   |
| OrgUnitXrefCode       | CAR\_Sport\_School       | Paid Activity → Export Business Structure |
| PayAdjustCodeXrefCode | WRK                      | Paid Activity → Paycode                   |

Date/time format: `YYYY-MM-DDTHH:MM:SS`

#### Incentives Export File Format

| Column Name           | Sample Data              | flaik Source Field                           |
| --------------------- | ------------------------ | -------------------------------------------- |
| (Column A)            | EmployeePayAdjustment    | Hardcoded to "EmployeePayAdjustment"         |
| (Column B)            | EmployeePayAdjustment    | Hardcoded to "EmployeePayAdjustment"         |
| EmployeeXrefCode      | C288                     | Staff → Payroll ID                           |
| JobXrefCode           | SNOW\_SPORTS\_INSTRUCTOR | Paid Activity → Jobcode                      |
| PayAdjustCodeXrefCode | GEARMTNALLOW\_050        | Incentive → Paycode                          |
| PayDate               | 2026-05-11               | Paid Activity → Date                         |
| Hours                 | 1.00                     | Incentive value when Pay Code Type = Hours   |
| Amount                | 5.50                     | Incentive value when Pay Code Type = Dollars |

Date format: `YYYY-MM-DD`

**Notes**

**Hours vs Dollars routing**

The incentive's Pay Code Type determines which column the value populates:

| If Pay Code Type is… | Hours column | Amount column |
| -------------------- | ------------ | ------------- |
| Hours                | Populated    | Blank         |
| Dollars              | Blank        | Populated     |

JobXrefCode is populated on every row regardless of Pay Code Type.

**No aggregation**

Each incentive record produces one row. Rows are not combined even when other fields match.

**Single value field**

Each row populates either the Hours OR Amount column, never both.

#### Leave (TAFW) Export File Format (in Timekeeping link)

| Column Name           | Sample Data         | flaik Source Field                     |
| --------------------- | ------------------- | -------------------------------------- |
| EmployeeXrefCode      | C288                | Staff → Payroll ID                     |
| StartTime             | 2026-05-14T09:00:00 | Paid Activity → Start Time             |
| EndTime               | 2026-05-14T10:00:00 | Paid Activity → End Time               |
| AllDay                | false               | Hardcoded to "false"                   |
| StatusXrefCode        | APPROVED            | Hardcoded to "APPROVED"                |
| PayAdjustCodeXrefCode | UNPLVE              | Hardcoded to "UNPLVE"                  |
| NetHours              | 1                   | Calculated = End Time minus Start Time |

Date/time format: `YYYY-MM-DDTHH:MM:SS`

**Notes**

**TAFW routing**

Only paid activities with paycode UNPLVE route to the TAFW file. All other paid activities route to the Wages or Incentives file.

**One row per day**

Each TAFW record covers a single day. A leave period spanning multiple days produces multiple rows.


---

# 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/cardrona-day-force.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.