---
title: "Retrieve an employee’s monthly time sheet"
method: GET
path: "/companies/{company}/time-balances/monthly-sheet"
tags: ["Time Balances"]
---

# Retrieve an employee’s monthly time sheet

`GET /companies/{company}/time-balances/monthly-sheet`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/time-balances/monthly-sheet`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Return the live monthly time sheet of an employee for the open period: expected vs worked minutes, balance and overtime per day, and totals (minutes).
- `employee_id` is required; `month` (`YYYY-MM`) defaults to the current month.
- `total_*` project the whole month; `to_date` holds the closed days up to `through_date`. Computed resource: no `id`.

## Path parameters

- `company` string, uuid, required

## Query parameters

- `employee_id` string, uuid, required
- `month` string, nullable

## Headers

- `Factuarea-Version` string, date

## Response `200`

- object
  - `data` MonthlyTimeSheet, required: The live monthly time sheet of an employee for the open (in-progress) period of the Control Horario (time tracking) module. A computed resource with no entity identity: it is keyed by employee + month, so it exposes `employee_id` (UUID v7) and never an `id`. Totals are in minutes; `days` is the daily breakdown. It is recomputed on every request, so a just-recorded clock entry is reflected without closing the month. The `total_*` fields cover the whole month and, in the current month, are a projection; `to_date` holds the actual accumulation of the closed days (every day before today).
    - `object` 'time_sheet', required: Always `time_sheet`.
    - `employee_id` string, uuid, required: UUID v7 of the employee the sheet belongs to.
    - `month` string, required: Month of the sheet (YYYY-MM).
    - `total_expected_minutes` integer, required: Total expected working minutes of the whole month, including today and the remaining days (holidays, approved absences, days without a schedule and days outside the employment period already count as 0).
    - `total_worked_minutes` integer, required: Total worked minutes of the month so far, today included.
    - `total_balance_minutes` integer, required: Month balance in minutes as the sum of the daily balances. In the current month it is a projection that already subtracts the expected minutes of today and of the remaining days; use `to_date.balance_minutes` for the actual balance.
    - `total_overtime_minutes` integer, required: Total overtime minutes of the month.
    - `to_date` TimeBalanceToDate, required: The month-to-date accumulation of the closed days (every day before today) for the Control Horario (time tracking) module. It is computed from the same daily breakdown as the `total_*` fields, which instead cover the whole month and are a projection: in the current month they already subtract the expected minutes of today and of the remaining days. Today is left out because its workday is still in progress. In a finished month it equals the `total_*` fields; when no day of the month has closed yet (its first day, or a future month), `through_date` is `null` and the four figures are 0.
      - `through_date` string, date, nullable, required: Last closed day included in the accumulation (YYYY-MM-DD), normally yesterday; `null` when no day of the month has closed yet.
      - `expected_minutes` integer, required: Expected working minutes of the closed days.
      - `worked_minutes` integer, required: Worked minutes of the closed days.
      - `balance_minutes` integer, required: Balance of the closed days in minutes: the sum of the daily `balance_minutes`, so days without a schedule or outside the employment period add 0.
      - `overtime_minutes` integer, required: Overtime minutes of the closed days.
    - `days` DayBalance[], required: Daily breakdown of the month. Each day includes `is_unscheduled` and `is_outside_employment`.
      - `date` string, date, required: Day of the breakdown (YYYY-MM-DD).
      - `expected_minutes` integer, required: Expected working minutes of the day derived from the schedule (0 on holidays, approved absences, rest days, days without a schedule in effect and days outside the employment period).
      - `worked_minutes` integer, required: Worked minutes of the day. Always the minutes actually clocked, also on days without a schedule in effect or outside the employment period, except under a `validated` schedule, where a scheduled day counts its expected minutes.
      - `balance_minutes` integer, required: Day balance in minutes (worked − expected); negative when the employee worked less than expected. 0 on days without a schedule in effect or outside the employment period (no reference to compare against).
      - `overtime_minutes` integer, required: Overtime minutes of the day (worked above the configured threshold, with the tolerance applied). 0 on days without a schedule in effect or outside the employment period: minutes clocked on those days never count as overtime.
      - `is_holiday` boolean, required: Whether the day is a public holiday for the employee.
      - `is_approved_absence` boolean, required: Whether the day is covered by an approved absence.
      - `is_rest_day` boolean, required: Whether the day is a rest day (no shift in the schedule).
      - `is_unscheduled` boolean: Whether the day falls within the employment period but no work schedule is in effect for it. Expected, balance and overtime minutes are 0; worked minutes are the minutes actually clocked. Never `true` together with `is_outside_employment`. Absent from the daily detail of a monthly close report.
      - `is_outside_employment` boolean: Whether the day is before the employee’s `hire_date` or after their `termination_date`. Expected, balance and overtime minutes are 0 even if a schedule assignment covers the day; clock entries recorded before this rule existed still show as worked minutes. Absent from the daily detail of a monthly close report.

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The employee or monthly sheet was not found.
- `422`: Validation failed. The `error.param` field identifies which input is invalid.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)