> 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/dayforce.md).

# Dayforce

## Dayforce Integration Mapping Summary

### Tier Overview

| Tier   | Model Name    | File(s) Used                  | What flaik Sends                | Dayforce Engine   | Resorts  |
| ------ | ------------- | ----------------------------- | ------------------------------- | ----------------- | -------- |
| Tier 1 | Payroll-Only  | Pay Adjustment Import         | Hours OR Amount totals          | Payroll           | Panorama |
| Tier 2 | Punch-Only    | Punch Import                  | StartTime + EndTime             | WFM (Time Engine) | Tamarack |
| Tier 3 | Full Two-File | Punch Import + Pay Adjustment | Start/End + Separate Incentives | WFM + Payroll     | Cypress  |

***

## Field-Level Mapping Summary

### Tier 1 – Payroll Only (Panorama)

| flaik Field             | Dayforce Column (Typical)       | Notes                  |
| ----------------------- | ------------------------------- | ---------------------- |
| Staff → Payroll ID      | EmployeeXrefCode / Employee No. | Must match Dayforce    |
| Paid Activity → Date    | PayDate / Business Date         | Date only (no time)    |
| Calculated Hours        | Hrs.                            | For hourly pay         |
| Incentive Amount        | Amount                          | For commission/bonus   |
| Paid Activity → Paycode | PayAdjustCodeXrefCode / Code    | Must exist in Dayforce |

No StartTime or EndTime used.

***

### Tier 2 – Punch Only (Tamarack)

| flaik Field                | Dayforce Column            | Notes               |
| -------------------------- | -------------------------- | ------------------- |
| Staff → Payroll ID         | EmployeeXrefCode           | Required            |
| Paid Activity → Start Time | StartTime                  | ISO format          |
| Paid Activity → End Time   | EndTime                    | ISO format          |
| Paid Activity → Paycode    | PayAdjustCodeXrefCode      | Required            |
| (Optional) Job/Dept        | JobXrefCode / DeptXrefCode | If costing required |

Hours are calculated inside Dayforce.

***

### Tier 3 – Full Two-File (Cypress / Cardrona)

#### File 1 – Punch File

| flaik Field | Dayforce Column       |
| ----------- | --------------------- |
| Payroll ID  | EmployeeXrefCode      |
| Start Time  | StartTime             |
| End Time    | EndTime               |
| Paycode     | PayAdjustCodeXrefCode |

#### File 2 – Incentive File

| flaik Field       | Dayforce Column       |
| ----------------- | --------------------- |
| Payroll ID        | EmployeeXrefCode      |
| Incentive Paycode | PayAdjustCodeXrefCode |
| Activity Date     | PayDate               |
| Incentive Total   | Amount                |

***

## Architecture Summary

| Question                   | Tier 1 | Tier 2 | Tier 3           |
| -------------------------- | ------ | ------ | ---------------- |
| Uses punch policies?       | No     | Yes    | Yes              |
| Sends Start/End times?     | No     | Yes    | Yes              |
| Separate incentive file?   | No     | No     | Yes              |
| Dayforce calculates hours? | No     | Yes    | Yes              |
| flaik calculates hours?    | Yes    | No     | No (for punches) |

***

## Quick Classification Rule

If the resort sends:

* Only totals → Tier 1
* Start/End only → Tier 2
* Start/End + separate bonus file → Tier 3


---

# 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/dayforce.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.