Time tracking (control horario)
Manage work schedules, time entries, absences, balances and presence through the API and MCP, using the same permission model as the rest of the platform.
Factuarea now covers the Spanish employer's duty to keep a daily working-time
record — RD-ley 8/2019, art. 34.9 of the Workers' Statute — and exposes the
whole workforce system over the same v1 contract. It is the VeriFactu of
attendance: an append-only ledger sealed by a per-company SHA-256 hash chain,
where nothing is ever edited or deleted and any tampering breaks the chain. The
whole surface is gated by the new control_horario module. Start with the
Time tracking overview.
- Eight new domains — employees (with invitations and per-seat billing), work schedules, time entries (clock in/out, pauses, retroactive entries and corrections), monthly register closes, payroll exports, absences (types, policies, requests, balances and calendar), presence, and public holidays.
- New scopes — a dedicated set in the closed catalog:
employees:*,time_entries:*,work_schedules:*,absences:*,presence:read,holidays:readandpayroll_exports:read, all behind thecontrol_horariomodule. See Scopes & irreversibility. - Sealed monthly close — freeze a finished month, then seal it with a
detached RSA-SHA256 signature over the snapshot; the seal is irreversible (one
per close) and independently verifiable. Export the daily record in the
rdley_8_2019format, or a payroll incidents file for A3, Sage or NominaSOL. See Monthly time-record close. - Portal-only employee role — an employee clocks in, follows a schedule and
requests absences from the portal, and never counts against the plan
userslimit. - Per-seat add-on — employees are billed through a dedicated monthly
employee-seatssubscription whose quantity follows your active roster; contracting it activates the module. An enterprise account billed by contract gets it for free. See Employee seat billing. - MCP parity — every v1 route mirrors a public MCP tool, so an agent drives the same operations. See the MCP tools catalog.
Two domains are read-only over the API — presence and public holidays
expose only reads. Declaring office/remote presence and creating custom local
holidays are portal-only tasks, with no presence:write nor holidays:write
scope.