Know who's really at work, and pay exactly the hours they worked.
Clock-ins from home, registers retyped into payroll, overtime paid before anyone approves it. Meridian checks every clock-in against the site, builds timesheets from them and pays only approved overtime.
Today, across your sitesMonday 2 November · 09:40
Example data
In79
Late6
Absent2
On leave3
Nairobi HQPhone and web
42 in3 late1 absent2 on leave
Mombasa warehouseBiometric readers
Morning, 06:00 to 14:00
28 in2 late1 absent1 on leave
Afternoon, 14:00 to 22:00
Starts at 14:00 · 31 scheduled
Kisumu field teamPhone, with location
9 in1 late0 absent
Latest clock-ins
Joseph MainaNairobi HQ · PhoneRefused
412 m from Nairobi HQ (geofence 250 m)Shown to Joseph on his phone.
Peter NjorogeNairobi HQ · Entered by Lucy Wanjiku, his managerRecorded
Faith ChebetKisumu field team · Phone, 60 m from siteAccepted
Hassan AliMombasa warehouse · Reader 2Accepted
Sites and location
Stop people clocking in from home.
A phone clock-in normally accepts wherever the person happens to be. When location is required, Meridian refuses clock-ins outside your sites and shows why.
Each site has its own location and radius.
Refuse clock-ins when the phone's location is too rough to trust.
One set of rules for the company, or different ones for phone, web and readers.
When a manager records a clock-in for someone, the record shows who entered it.
Nairobi HQGeofence 250 mExample data
250 m
Nairobi HQ
Try a clock-in from
Refused
“412 m from Nairobi HQ (geofence 250 m)”
Way of clocking in
Location required
Location accuracy limit
Phone
Yes
50 m
Web
Yes
100 m
Biometric reader
No, the reader is on site
Not used
Biometric readers
Use the biometric readers you already have.
Swapping readers is costly, and retyping their logs wastes hours. Meridian connects to ZKTeco, Hikvision, BioStar 2 and Jibble, and never drops a punch it can't match.
01Connect your devices. Use a connector, or import your device list from CSV.
02Match people once. Each device user is matched to an employee by employee number or ID number.
03Confirm the rest. Punches that can't be matched wait in a queue for HR to confirm.
SettingsAttendanceDevicesExample data
ZKTecoMombasa, readers 1 and 2Last punch 09:38
HikvisionNairobi HQ, main gateLast punch 09:31
BioStar 2Not set upConnect
JibbleNot set upConnect
Match device users byEmployee numberthenID number
Unmatched punches
Waiting for HR to confirm
Device user 0417Mombasa, reader 2 · Mon 2 Nov, 06:04
ID number
HAHassan AliWarehouse operative · suggested by ID number
Device user 0388Mombasa, reader 1 · Sun 1 Nov, 13:58
employee number
ZNZawadi NjeriForklift driver · suggested by employee number
Timesheets
Timesheets built from clock-ins, not retyped from a register.
Someone usually copies a paper register into payroll every month. Meridian builds each day's timesheet from the clock-ins and checks it before payroll. Choose a step to see how.
Daily timesheet
Step 2 of 5
Each day is worked out from the punches and marked on time, late, partial, absent, on leave or holiday. Your schedule's grace period and rounding apply.
Who acts
Meridian, using your schedules
What is kept
Each day's status and hours.
What this unlocks
Manager review.
Amina Otieno, week of 26 OctExample data
MonOn time8.0
TueLate7.5
WedPartial4.0
ThuAbsentNo punches0.0
FriOn leaveAnnual leave0.0
07:0009:0011:0013:0015:0017:00
ScheduledWorkedPunchGrace
Overtime
Overtime paid once, and only when it's approved.
Overtime often gets paid from a supervisor's note, then argued about later. Meridian proposes it from timesheets, routes it for approval and pays only what's approved.
October payroll can't be computed yet.One overtime request is still waiting for approval.
Brian KipropSeptember, 2 h added after paymentBack pay
Peter NjorogeSeptember, 1 h removed after paymentClaw back
From timesheet to payslip
Overtime is paid at the rate for that day type, through the payroll you already run.
DetectedFound in the timesheets, against your policies.
ProposedSent for approval, or approved automatically under your limit.
ApprovedThrough your own approval workflow.
PaidIn payroll. Later corrections become back pay or claw back.
Schedules
Rosters that match the shifts people really work.
One fixed nine-to-five rarely fits a warehouse, a branch and a field team. Set the schedule each group works, and approve day changes through your workflow.
SchedulesExample data
FixedNairobi HQMonday to Friday, 08:00 to 17:00
RotatingMombasa warehouseMorning and afternoon shifts, swapping each week
FlexibleKisumu field teamStart any time, 45 hours a week
ProjectInstallations teamHours set for each project
OpenDriversNo fixed hours
Grace for lateness10 minutes
RoundingNearest 15 min
Expected a week45 hours
Expected a month195 hours
Day changesExample data
HAHassan AliMombasa warehouse · Swap request
WorkSat 7 Nov
Take offMon 9 Nov
Shift supervisorApproved
HRWaiting
Reports
Attendance reports ready at month-end, without a spreadsheet.
Month-end usually means stitching attendance figures together in a spreadsheet. The reports come straight from your clock-ins and timesheets.
Daily attendance
Lateness
Absenteeism
Overtime
Compliance
Monthly summary
Raw clock logs
Timesheet export
Bring your history
Import clock logs, overtime and corrections from spreadsheets, so your first month on Meridian starts with your real figures.
Clock logs
Overtime
Corrections
Attendance bonus, if you pay one
Set up your own attendance bonus. Keep it in reports only, or add it to payroll as an earning.
Reports only
Payroll earning
Common questions
About clocking in, devices, overtime and schedules.
Got readers on several sites?
Plan the setup with our implementation team.
If location is required, the clock-in is refused and the person sees why, for example “412 m from Nairobi HQ (geofence 250 m)”.
You can also refuse clock-ins when the phone’s location isn’t accurate enough. Set the rules for the whole company, or for each way of clocking in.
ZKTeco, Hikvision and Suprema BioStar 2 devices, through Meridian’s connectors, plus Jibble. You can also import your devices from CSV. Device users are matched to employees by employee number or ID number.
Meridian finds overtime in the timesheets and proposes it. It’s approved through your workflow, or automatically under a limit you set, then paid in payroll at the rate for that day type.
Corrections after payment become back pay or claw back. You can also stop payroll being computed while overtime for the period waits for approval.
People can swap a working day for a day off, one for one: work Saturday and take Monday off, for example. They can also ask for a day off, an extra working day or a partial day. Each request goes through your approval workflow.
It waits in a queue for HR to confirm. Meridian never drops it. Punches are matched by employee number or ID number.
Pay next month's hours from real clock-ins.
Bring your clock logs and device list. Start on your own, or plan the move with our implementation team.