The month closed. The report is already calculated, signed and ready for payroll.
A time clock that works out overtime, rest days and holidays on its own — and sits inside the system your work, your clients and your billing already run in.
In an argument about hours, the burden of proof is yours
Amendment 24 to Israel's Wage Protection Law requires an employer to keep a running record of hours actually worked. Without one, the labour court puts the burden of proof on the employer — and a report assembled after the fact is rarely accepted.
A month-end that eats a whole day
Somebody collects hours out of a spreadsheet, out of WhatsApp and off signed paper, works out the overtime by hand, and types the lot in again at the payroll desk.
From the punch to the payroll file, with no typing in between
A time clock that goes all the way to the payroll file
Everything it takes for month-end to finish with an approval and a file, rather than with another evening of arithmetic.
Clock in and out from mobile or desktop
Every punch is recorded with its source — mobile, desktop, a manager's manual entry, or an automatic close.
A geofence around the office
You can require a self-punch to happen inside a radius you set, and the punch is stored with its coordinates.
Rate ladders you define
125% for the first two hours then 150%, a separate weekly ladder, and rates of their own for rest days and holidays.
A built-in holiday calendar
Holidays and holiday eves are recognised automatically, an eve gets a shortened standard, and you can add days of your own.
Leave, sickness, reserve duty and bereavement
A whole day or a few hours out of one, with a pay percentage per type — including a graduated sick-pay ladder.
Leave and sick balances
Accrual under your policy, usage derived from the absences themselves, and an opening balance you enter.
Correction requests with an approval path
The employee asks, the manager approves or declines with a note, and the request keeps both the old value and the requested one.
Export to payroll
A Michpal QDIV file and a standard punch CSV — instead of keying the month in a second time.
People who never reach the office clock in from where they actually are
Installations, maintenance, deliveries, cleaning and security — teams whose day starts at a customer's door rather than next to a wall-mounted clock. They punch from the phone, and the location is stored with it.
The hours that were clocked are the hours you bill for
A standalone time clock is one more island: the data in it is right, but it never talks to the tasks, the client file or the collection plan. Here it's the same place.
Overtime, rest days and holidays — under your own rules
The defaults are the standard Israeli set, but nothing is hardcoded: every rate step, every standard and every absence type is part of a work policy you can change.
"I forgot to clock out" becomes a request, not a thread
Every correction runs down one documented path: what it was, what is being asked for, who approved it and when. Nobody quietly edits somebody else's hours.
The month ends in a file, not in data entry
Instead of handing payroll a spreadsheet and hoping every figure survived the copy, the approved month comes out as a file their system knows how to read.
12/08/2026,08:12:00,0Businesses where hours are not a technicality
If somebody sits down at month-end and assembles everyone's hours by hand, this was built for you.
Everything you wanted to know
What the system does: it keeps a running record of hours actually worked for each employee, stores every change in a log with the previous value, who changed it and when, and produces a monthly report the employee signs, the manager approves and the system locks together with a snapshot of the rules it was calculated under. That is exactly the kind of record the amendment is about — but whether it fully covers your particular case is a question for a lawyer, not a claim for us to make.
No. They can clock in from the browser on a computer or from the app on a phone, and each punch is recorded with its source. The app matters mainly for field teams, where the location is part of the report.
A shift left open past the threshold you set is closed automatically at a best guess — the end of their working hours, or the start of the shift plus their standard hours. It's flagged as needing attention, the employee fills in the real finish time, and the whole sequence stays in the log.
Yes. You set a location and a radius, and from then on a self-punch outside it is rejected on the server. The radius never goes below 50 metres, a manager punching on an employee's behalf is exempt from the check, and a fence that isn't properly configured never locks anyone out.
The defaults are the standard Israeli set: 8.6 hours a day, 42 hours a week, 125% for the first two overtime hours and 150% after that, an increased rate on rest days and holidays, and a shortened standard on holiday eves. That said, the engine isn't locked to Israel — every rate and standard is configuration you can change.
Yes — a Michpal QDIV file and a standard punch CSV, including the statutory quantities for days and hours actually worked alongside the standard ones. Worth knowing: this is a file rather than a live API, and your payroll clerk maps our codes through the translation table in their own system.
By default every employee sees only themselves. Separate permissions open up viewing all employees, editing and approving other people's shifts, and full control of the policies and the locking — so a shift manager can look without editing, and a payroll clerk can export without managing.
Let next month close itself, with nobody assembling it by hand
Leave your details and we'll set up your hours policy with you, then walk a full month from the first punch to the file that comes out of it.