> 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/3.-flaik-connect-api/timekeeping.md).

# Timekeeping

Calculated timesheet data for a resort, with wage, commission and incentive figures already computed against the configured rate cards. Use this group to ingest payroll-ready data into payroll exports, BI dashboards, or commission audit systems.

### Pages in this group

* [**Paid Activities by Date Range**](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/3.-flaik-connect-api/timekeeping/paid-activities-by-date-range) — paid-activity rows with computed wages and commission in a single feed (`GET /api/timekeeping/paidactivities/paidactivitiesbydaterange`).
* [**Wages by Date Range**](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/3.-flaik-connect-api/timekeeping/wages-by-date-range) — base activity wage only, one row per timesheet entry (`GET /api/timekeeping/wages`).
* [**Incentives by Date Range**](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/3.-flaik-connect-api/timekeeping/incentives-by-date-range) — staff incentives and commissions, one row per entry per component (`GET /api/timekeeping/incentives`).

All three take the same query parameters: `startDate`, `endDate`, `updatedAfterLocalDateTime` and `seasonId`.

### Which feed should I use?

{% hint style="info" %}
**Paid Activities is not deprecated.** It remains fully supported and is in production use today. Wages and Incentives are **complementary** — an alternative shape for integrations that want the two components separated, not a replacement.
{% endhint %}

| If you want...                                                                                | Use                               |
| --------------------------------------------------------------------------------------------- | --------------------------------- |
| One row per timesheet entry with wages **and** commission together                            | **Paid Activities by Date Range** |
| Base wages and incentives as **separate feeds**, each with its own pay codes and cost centres | **Wages** + **Incentives**        |

Choose one approach or the other. Pulling the combined feed *and* the split feeds for the same period will double-count.

{% hint style="warning" %}
**Wages and Incentives have different grains.** Wages returns one row per timesheet entry; Incentives returns one row per entry per incentive component. There is no entry-level join key between them — incentive rows are self-contained by design — so the two cannot be summed naively.
{% endhint %}

### Typical use

* **Payroll export** — pull the rows for a payroll period and feed into the payroll system. Wage, commission, and totals are already calculated; pay codes and cost centres are included for downstream allocation.
* **Commission audit** — pull a wider range and reconcile against the resort's expected wage/commission outputs.
* **Incremental sync** — pass `updatedAfterLocalDateTime` to receive only rows changed since your last successful pull. Note that this timestamp is interpreted in **resort-local time**, not UTC — convert using the `timezone` from [Resort Details](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/3.-flaik-connect-api/global-settings/resort-details).


---

# 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/3.-flaik-connect-api/timekeeping.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.