Punches from the phone, ready for an audit
Every punch gets a sequential number and carries the hash of the previous one — changing any of them breaks the chain. Clocking in can require a photo and a geofence, and the legal exports come out ready.
Why use it
The problems Avos solves in everyday HR.
Inspectors ask for files, not spreadsheets
A spreadsheet produces no AFD or AEJ file, and companies find that out on the day they have to hand one over.
Both files are exported straight from the period's own records, and every punch leaves a receipt for the employee.
Records that can't be changed quietly
A punch edited later with no trace is what sinks a time-tracking system in a labour dispute.
Each record gets a sequential number and stores the previous record's hash: touching one breaks the chain. Adjustments require a reason and land in the audit trail.
Clocking in from the wrong place
A punch made by someone else, or far from the work site, turns into liability.
Companies can require a photo and a geofence, and every record stores where it came from.
How it works
The employee clocks in
From the app, with photo and location when the company requires it. They keep the receipt.
HR reviews the timesheet
Per person, with adjustments that require a reason and are recorded in the audit trail.
Export on demand
The period's legal files come out ready, and the hours feed payroll with no re-typing.
Frequently asked questions
Does Avos generate the AFD and AEJ files?
Yes. Both are exported from the period's records, in the format inspections expect.
Do employees get a receipt for each punch?
They do. Every punch produces a receipt, and employees browse their own in the portal and the app.
How does Avos prove a punch was not tampered with?
Every record carries a sequential number and the hash of the previous record. Altering any punch breaks the chain, which is visible on review.
Can I restrict where people clock in?
You can. The company sets a geofence and may require a photo; each record stores its origin location.