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.
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:
| Record | What it holds |
|---|---|
| Clock-in / clock-out event | One 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 session | The header-and-lines shape a worked session takes once events are paired up |
| Payroll attendance adjustment | The 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. Two 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 has not been started: its menu is still the generator’s own Company and Generic Example entries.
Neither is in the registry, so neither is reachable by a customer in any case.
What to do instead, today
| If you need | Use |
|---|---|
| The employee record itself — identity, employment dates, branch, reporting lines, bank details | Employee Maintenance |
| To make an existing customer or supplier an employee as well, or to maintain employee categories | Entity Maintenance |
| Employee expenses, including amounts to be paid through payroll | Claim Applet and Claim Cycle Applet |
| The honest, whole picture of people administration in BigLedger | HR & 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
- HR & Payroll Module — what people administration can actually do today, and what it cannot
- Employee Maintenance — the employee master every attendance record would point at