Read the attendance record
- 1
Document Number is the durable audit reference for the attendance-day record.
- 2
Resource identifies the employee whose punches and day status are recorded.
- 3
Date is resolved in the resource's local branch timezone, not simply UTC.
- 4
Check-In and Check-Out preserve the first and last attendance boundaries for the day.
- 5
Branch fields retain where each boundary occurred and support location-aware review.
Mobile punches are consolidated into a dated Resource Availability record. Document Number provides the audit reference, Resource identifies the employee, and Date is the branch-local working day. Check-In and Check-Out hold the day's time boundaries, while their corresponding branch fields preserve where each punch was associated. Availability Type distinguishes attendance-derived time from leave, holiday or another scheduling exception.
When reviewing a disputed day, first verify the resource's timezone and branch, then compare the device punch timestamps, offline synchronization time, selfie or location evidence where policy permits, and the resulting first-in/last-out values. An auto-checkout should remain visibly synthetic rather than being mistaken for a manual punch. The screenshot uses visible synthetic demo2 data so readers can follow realistic rows, values and controls together; production exports and screenshots must still remain inside authorized channels.
Attendance in xMatix is a mobile check-in/check-out: the executive punches in at the start of the field day — optionally with a selfie and a captured location — and punches out at its end. An administrator decides who is gated and how strictly: for gated users the app can refuse to open at all until the day's check-in is done, or gate only specific screens. Punches build a per-day attendance record, and a background sweep closes the days people forget to close.
The gate
Whether check-in is required comes from the mobile app profile assigned to the user, in one of two modes: app mode shows a "Check in to start your day" screen instead of the app itself, and entity mode gates only the configured record screens. The check-in window captures the location and, where required, a selfie; a successful — or offline-queued — punch unlocks the app immediately.
What counts as a valid check-in is evaluated on the server, per the gates the administrator has enabled:
| Gate | What it checks |
|---|---|
| Location | Distance between the punch location and the executive's branch |
| Working day / hours | The executive's business-hours calendar — working days and day start/end |
| Holidays | The applicable holiday calendar |
| Leaves | Approved leave on the day |
Punches and the day record
Each check-in and check-out is a punch, stamped on the branch-local calendar day — a late-evening check-in lands on the local day it belongs to, not the UTC one, which is what payroll and day reports key on. Punches roll up into a per-day attendance record with first-in and last-out times, and multiple in/out pairs within a day are supported.
Working offline
Check-in does not depend on coverage: an offline punch is queued on the device, unlocks the app at once, and replays to the server when connectivity returns — the selfie upload follows once the punch exists server-side. One honest limit: a queued punch older than three days is rejected on replay, so attendance cannot be back-filled from a device that stayed offline for a week.
Automatic checkout
Forgetting to check out is routine, so an administrator can enable auto-checkout. Once a local day has ended — resolved in the executive's own timezone — any check-in still open from that day is closed with a synthetic checkout punch at 23:59:59, clearly labelled "Auto checkout", and the day record's last-out time is refreshed. The sweep looks back a bounded window (two weeks), so ancient stragglers age out rather than being rewritten.
Common questions
What happens if I forget to check out?
If your organization has auto-checkout enabled, the day is closed for you at end of day with a punch labelled "Auto checkout" — visibly synthetic, so a supervisor can tell a real 23:59 checkout from a forgotten one. If it is not enabled, the check-in simply stays open until you punch out.
Can I check in from anywhere?
That depends on which gates your administrator enabled. With the location gate on, the punch must be within the configured distance of your branch; other gates can require a working day, non-holiday, and no approved leave. The app tells you which gate refused a punch.
Is attendance check-in the same as checking in at an outlet?
No — they are separate. Attendance is one day-level punch pair governing your working day; visit check-in/check-out happens per outlet inside the visit flow and drives visit reporting. See Complete a visit.