Skip to content

Time and Attendance

Where time and attendance stands in BigLedger today: the backend holds clock-in and clock-out events, attendance sessions and payroll attendance adjustments, each with an API, but there is no applet a customer can install to use them. The working attendance dashboard an earlier version of this page described does not exist; for the employee record itself, use Employee Maintenance.

There is no time-and-attendance applet you can install today. One has been registered — Staff Time Attendance, on 20 October 2026 — but it is in no catalogue, so the Applet Store does not offer it, and its deployed screens are still the applet template’s. What exists is a data model and an API in the HR backend, described below, and an unfinished prototype front end that does not yet read it. It is not separately installable and nothing installs it: HR & Payroll is a planned module, not yet offered. Do not plan around this page.

Your job, and the screen for it

The jobScreen or tabRead
Record or review staff attendance — not possible: there is no time-and-attendance applet to installNone — the admin prototype’s screens read the company master, not attendanceWhat does not exist
Maintain the employee record — identity, employment dates, branch, reporting lines, bank detailsEmployee Maintenance appletWhat to do instead, today
Make an existing customer or supplier an employee as well, or maintain employee categoriesEntity Maintenance appletWhat to do instead, today
Handle employee expenses, including amounts paid through payrollClaim Applet and Claim Cycle AppletWhat to do instead, today
Feed clock events from a device or attendance system — confirm with your BigLedger contact first: it belongs to no offered moduleThe clock-in/out event API (it has no form)What exists in the backend; What to do instead, today

Why this page exists

An earlier version of this page described a working administrative dashboard: a filterable attendance log, a reporting engine, exports to payroll, configurable grace periods, branch whitelisting and anomaly alerts. None of that exists. The page is kept, at the same address, so that anyone who followed a link or a search result to it gets the true position rather than a 404.

What exists in the backend

Time and attendance is a real part of the HR domain in BigLedger’s backend. Three records carry it:

RecordWhat it holds
Clock-in / clock-out eventOne entry per tap. The employee (as an entity), the company, an event time and an event type, a free-text location, GPS coordinates, the device that recorded it (id and type), a description, and free-form properties and a log
Attendance sessionThe header-and-lines shape a worked session takes once events are paired up
Payroll attendance adjustmentThe attendance correction a pay run carries

Each has an API: the clock event can be created and read, including by an employee’s own login for their own taps; the attendance session is read-only; the payroll adjustment can be maintained.

An employee is an entity with the EMPLOYEE flag, so the record every clock event points at is the one maintained in Employee Maintenance.

What does not exist

A front end. Three applet repositories carry the name:

  • The admin repository has two screens, TimeAttendanceLog and Report, and a settings container. Both screens query the company master, not attendance: their grids carry attendance column headings (Employee Name, Activity, Time, Date, location, Status) bound to company fields. Nothing in it reads a clock event. It is a scaffold that was renamed and not yet wired.
  • The staff repository is registered and deployed as Staff Time Attendance (20 October 2026), but its menu is still the generator’s own Company and Generic Example entries.
  • The internal repository is empty: it holds a README and no code.

Only the staff applet has a registry row, and it is in no catalogue, so none of the three can be installed or offered on a customer’s launchpad.

What to do instead, today

If you needUse
The employee record itself — identity, employment dates, branch, reporting lines, bank detailsEmployee Maintenance
To make an existing customer or supplier an employee as well, or to maintain employee categoriesEntity Maintenance
Employee expenses, including amounts to be paid through payrollClaim Applet and Claim Cycle Applet
The honest, whole picture of people administration in BigLedgerHR & Payroll Module

To record clock events from a device or an external attendance system while no applet exists, the clock-in/out event API is the integration point. Treat it as a platform API rather than a product feature: it belongs to no offered module, so confirm with your BigLedger contact before you build against it.

Related documentation

Last updated on