They photograph the screen
Nothing prevents it, and the displayed code is perfectly valid at that moment.
The entrance screen shows a code that renews continuously. By the time it has been photographed and sent, it is already worthless. Your staff clock in with the Madata app they already have, with no badge and no reader on the wall.
One message only, on the day the module opens. No newsletter.
Scan with the Madata app.
Direct answer
A screen at reception shows a code that renews continuously. The employee scans it with the Madata app they already have on their phone. The code works once per person and expires very quickly: sending it to an absent colleague therefore achieves nothing.
Continuous
Renewal of the displayed code. An expired code is worth nothing.
0
Use per employee and per code. The constraint sits in the database itself.
3
Modes to choose from: entry only, entry and exit, or with breaks.
0
Badges to buy, readers to fit, cards to replace when they get lost.
The number one objection
Every manager asks this first. Here is what actually happens, step by step.
Nothing prevents it, and the displayed code is perfectly valid at that moment.
Time enough to open the chat, attach the image and have the colleague receive it.
The screen has already changed code several times. The server refuses, and says why.
This QR code has expired. Scan the one now shown on the screen.
The code is still valid. Only at this point could the photo have been of any use.
For the employee
No. The employee clocks in with the Madata app on their own phone, the one they already use for leave requests and payslips. There is no badge to order, no card to replace, no reader to fix to the wall.
The entrance screen continuously realigns on the server clock and clearly signals a network outage. The phone, however, must be connected when scanning: the server is what decides whether a code is still valid, and that is exactly what makes the record defensible.
Frame the code shown at reception
For the manager
The dashboard answers three questions, in order of urgency: who is missing today, who is repeatedly late, and whether things are getting better.
0
Present today, out of 19 expected
0
Late today
0
Absent today
0%
Punctuality over the period, 23 working days
4 h 12
Cumulated lateness over the period
Aya Koffi
Commercial
Ibrahim Traoré
Atelier
Mariam Bamba
Comptabilité
Serge N’Guessan
Atelier
Fatou Diallo
Accueil · Congé payé
Kouassi Yao
Livraison
Features
Raw clocking records say who came in. They do not say who is missing, or why. Everything below exists to tell the difference.
Entry only to know attendance and lateness. Entry and exit to also get hours actually worked. Entry, exit and breaks for the full detail.
Lateness is computed against the employee's real working schedule, with a tolerance you set, five minutes by default.
An employee whose leave you approved is never counted absent. Half days are handled, with no setting on your side.
A missing record is corrected in two clicks. A reason is mandatory, the correction stays traced, and the day keeps its real status.
With no window defined, clocking is accepted at any hour. You can restrict it, and a scan outside the window is then refused.
An eight character code can be shown under the QR for phones whose camera will not cooperate. It is off to start with, deliberately: a code readable in plain sight can be photographed from a distance.
One button renews the screen key. The old link leads nowhere and every code already photographed becomes useless.
Someone who forgets to clock out on Monday evening would be blocked on Tuesday morning. A record left open is closed after sixteen hours, and flagged as automatic.
Payroll bridge
No, and that is guaranteed by design. On installation the payslip receives three counters but no amount moves: the injected lines carry zero hours, which leaves untouched the total the payroll uses to spread the salary. Deduction rules ship disabled.
July payslip
Kouassi Yao · Livraison
The counters are readable, no amount has changed.
You enable the rule, and only you
July payslip
Kouassi Yao · Livraison
Two days of unjustified absence deducted, at the rate you set.
An absence the manager recognises as justified keeps its real status in the history, but drops out of the counters sent to payroll. What happened is not rewritten, it is qualified.
Which businesses
Teams arriving together at a fixed hour, whose overtime gets argued over at the end of every month.
Several teams, staggered hours, and an opening time that depends on whoever arrives first actually being there.
Staff whose arrival times you want to know without fitting a turnstile or a fingerprint reader at the door.
One stop at the depot in the morning, and the rest of the day on the road.
Getting started
01
A tablet or a television at reception is enough. The page is self contained, it loads nothing else, and it works on old hardware and an unreliable network.
02
With the Madata app they already have. Each person needs an employee record linked to their account, and the dashboard names those who do not have one.
03
The dashboard fills up from the first scan. The payslip counters only take effect the day you enable a rule.
The Presence module is included in the Madata PME plan, at no extra cost. It cannot be activated yet.
Tell me as soon as it is available
One message only, on the day the module opens. No newsletter.
The module relies on the employment contract and the employee's working schedule, and its main value is the payslip link: that is why it is reserved to the PME plan. See also Madata in Côte d'Ivoire and the payroll software.
Frequently asked
Not remotely. The code on the screen expires very quickly and works once per employee: photographing it and sending it almost always takes longer than its lifetime. What remains is the case of two people physically very close, which the module does not claim to prevent. It does flag unusual grouped arrivals on the same code to the manager.
The Presence module is coming to the Madata PME plan. Leave your address and you will hear from us the day it opens.
One message only, on the day the module opens. No newsletter.