# Cardrona (Day Force)

***

### Overview

| Field                | Value                                      |
| -------------------- | ------------------------------------------ |
| Payroll System       | Ceridian Dayforce                          |
| Files Used           | Wages, Incentives                          |
| Frequency            | Daily                                      |
| Header Row           | Yes (both files)                           |
| Wages File Name      | `EmployeePunchImport_yyyymmddhhmmss.csv`   |
| Incentives File Name | `EmployeePayAdjustment_yyyymmddhhmmss.csv` |
| Transfer Method      | Manual to move to FTP                      |

### Wages Export File Format

| Column                | Sample Data              | flaik Source                              |
| --------------------- | ------------------------ | ----------------------------------------- |
| EmployeeXrefCode      | `101891`                 | Staff → Payroll ID                        |
| StartTime             | `2026-03-12T10:00:00`    | Paid Activity → Start Time                |
| EndTime               | `2026-03-12T11:00:00`    | Paid Activity → End Time                  |
| NetHours              | `1.0`                    | Calculated (End Time − Start Time)        |
| Operation             | `update`                 | Hardcoded                                 |
| 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

The incentives file uses Dayforce's row-prefix import convention. Every row begins with a row type (`H` for header, `D` for data) and the import type (`EmployeePayAdjust`).

| Column                | Sample Data              | flaik Source                                      |
| --------------------- | ------------------------ | ------------------------------------------------- |
| (Row Type)            | `D`                      | Hardcoded `H` (header) or `D` (data)              |
| (Import Type)         | `EmployeePayAdjust`      | Hardcoded                                         |
| EmployeeXrefCode      | `101891`                 | Staff → Payroll ID                                |
| JobXrefCode           | `SNOW_SPORTS_INSTRUCTOR` | Paid Activity → Jobcode (conditional — see Notes) |
| PayAdjustCodeXrefCode | `EXTRAS_GROUP_LESSON_HC` | Incentive → Paycode                               |
| PayDate               | `2026-03-12`             | Paid Activity → Date                              |
| Hours                 | `8.0`                    | 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 goes in and whether JobXrefCode is populated:

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

**No aggregation**

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

**Single value field**

Each row populates either Hours or Amount, never both.


---

# Agent Instructions: 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:

```
GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/payroll-export-configuration/resort-specific-info/cardrona-day-force.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.