PRODUCTS / 03 HR & PAYROLL — INDIA, UAE & US BY WEIRD LABS

ZIVOHR

The HR system
you can just ask.

People, attendance, leave, payroll, hiring and performance on one record. Ziva answers people's HR questions from their own record, and prepares the request instead of pointing at a form.

VISIT ZIVOHR.COM SEE IT WORK

LIVE AT ZIVOHR.COM

ZivoHR dashboard: 42 employees, 37 present today, 3 on leave and 84 pending requests, above a week of attendance by day and the requests that need action
Ziva, the assistant, offering to answer how many leaves are left, when the next holiday is, days present last month and last month's net pay
The ZivoHR phone app on the clock: checked in at 14:33, inside the Bangalore office's 200 metre geofence

REAL SCREENS FROM ZIVOHR DEMO DATA — NAMES AND FIGURES ARE GENERATED

10

Modules on one record. The hire becomes the employee, and attendance feeds payroll.

3

Payroll countries: India, the UAE and the US, each with its own rules and filings.

4

Punch sources, one timeline: biometric device, phone, browser and regularisation.

0

Spreadsheets in the payroll run. Loss of pay and overtime come from the timeline.

HR, BEFORE

The answer existed. It was four screens deep.

BEFORE

"How much leave do I have left?" is an e-mail to HR.

Attendance is exported, cleaned and pasted into the payroll sheet.

The night shift shows up as two half-days, and someone fixes it by hand.

The new hire's details are typed in again on their first day.

WITH ZIVOHR

Ziva answers from the asker's own record, with the same figures the screens show.

Payroll reads loss of pay and overtime straight from the attendance timeline.

A shift that crosses midnight is one record, belonging to the day it started.

The accepted offer becomes the employee record. Nobody retypes it.

01 — ZIVA, THE AI LAYER

The questions people used to e-mail HR.

How much leave is left, why the payslip moved, whether a cab needs a receipt. Ziva answers from the asker's own record. Ask it to put in leave and it prepares the request. You press Confirm. The model never writes anything itself.

  1. 01 Grounded in your workspace Your leave policy, your holiday calendar, your payslips and your expense policy. If the workspace has no rule for a question, Ziva says so rather than guessing.
  2. 02 Scoped to the person asking Every tool reads the asker's own record and nothing else. Ask about a colleague's salary and it tells you it can't see it.
  3. 03 It proposes, you confirm A proposal can't be edited, can only be confirmed once, expires in 15 minutes, and every leave or expense rule is checked again when you confirm.
  4. 04 Off means off Ziva is a feature on the workspace's plan. Switch it off and the launcher goes with it.
Ziva's panel: it answers about your own leave, attendance, payslips and reimbursements, and says it only ever sees your own records

02 — PAYROLL

The run is a function, not a spreadsheet.

One engine, and each country plugs in its own rules, filings and currency. Every input is explicit, every run can be recalculated before approval, and a rule change applies from the date it applies from.

  1. 01 India, the UAE and the US PF, ESI, TDS, PT and gratuity in India. WPS and end-of-service in the UAE. FICA, state income tax and W-2s in the US.
  2. 02 Variance before you approve See who moved against the last run and why: joiners prorated, an increment mid-cycle, someone crossing the PF wage ceiling.
  3. 03 Rules carry effective dates A rate change adds a version. Payroll already processed keeps the version it used, so last year's payslips never move.
  4. 04 Incentives and full & final Payouts priced from KPI achievement, and a leaver's settlement that can't be approved while their exit clearance is still open.
A processed August payroll run for 40 employees: gross, deductions, net pay and employer cost, the warnings that need attention, the bank transfer file and each payslip
Payroll statutory settings: PAN, TAN and registered state, with EPF, ESI, professional tax, labour welfare fund and gratuity switched on, beside a note that rules are versioned, not edited

PAYROLL RUN · STATUTORY SETTINGS DEMO DATA

03 — ATTENDANCE & LEAVE

Four punch sources. One timeline.

The monthly attendance view for September: one row per employee, a square per day marked present, late, leave, absent or weekend, and each person's attendance rate
The phone app showing the employee inside the office area, 18 metres from the office against an allowed radius of 200 metres

HR VIEW · EMPLOYEE'S PHONE DEMO DATA

A factory uses a device, a field team uses the phone, head office uses a browser, and someone always forgets. All four land on one timeline, on the clock of the office they happened in, and payroll reads that timeline.

  1. 01 Biometric, phone, web eSSL and ZKTeco readers push punches as they happen. The app checks in against the office's geofence, 200 m unless you draw it otherwise.
  2. 02 Night shifts that cross midnight A 21:00 to 05:30 shift is one record belonging to its start date, not two half-days that each look like an absence.
  3. 03 Leave that accrues and approves itself Accrual, carry-forward, encashment and holiday calendars per location, on the same approval engine as everything else.
  4. 04 A missed punch is a request Regularisation goes to an approver with a reason, and the correction stays visible as a correction.

04 — HIRING & PERFORMANCE

Requisition to review. On the same record.

Jobs, candidates, interviews and offers in one pipeline, and the hire becomes an employee without anyone retyping them. Then weighted KRA scorecards, anonymous 360 reviews, and calibration that locks when it's signed off.

The recruitment pipeline: candidates in applied, screening, interview, offer and hired columns, with stage conversion under each

CANDIDATE PIPELINEDEMO DATA

A signed-off calibration session on a nine-box grid, with employees placed from risk to star by performance and potential

NINE-BOX CALIBRATIONDEMO DATA

/01 One pipeline Requisition, stages, interview panels and offers, with conversion shown under every stage.
/02 KRA & KPI scorecards Weighted goals, with achievement imported in bulk rather than typed in two hundred times.
/03 Anonymous 360 Peer reviews stay anonymous, with a floor of three reviewers under every result.
/04 Calibration that locks Place people on a nine-box grid. Once the session is signed off, it can't be quietly changed.

05 — THE REST OF HR

Joining to exit. One system.

/01 People & org Employees, locations, departments, teams and reporting lines: the spine every other module reads from.
/02 Onboarding & exit Task templates, documents by signed link and asset handover, and an exit clearance that has to close before the final settlement can.
/03 Expenses & assets Claims with line-level approval, per-km and per-day categories priced by the server, and the laptop register nobody wants to keep in a sheet.
/04 Helpdesk & comms An HR helpdesk with SLAs, announcements targeted by location or department with read receipts, and pulse surveys.
/05 One approvals engine Leave, expenses, regularisation and onboarding go through the same chain. Managers learn one inbox.
/06 Who sees what Permissions are codes, not job titles. Each role sees its own record, its reporting subtree or everything.
/07 Single sign-on Okta, Microsoft Entra ID or any OpenID provider, on the web and the phone. It never signs strangers up.
/08 An audit trail Every consequential change is recorded with who made it, the workspace and the source IP, and is never edited in place.

HOW WE BUILT IT

Built by Weird Labs.

Multi-tenant from the first table

Every row carries its company. The data layer refuses to read without one, and a login token from one workspace fails on another.

Payroll core, country rules on top

One engine runs periods, structures and payslips. India, the UAE and the US are separate rule sets on top of it.

Web, iOS and Android

A Django and PostgreSQL API behind a React web app and a Flutter phone app with geofenced check-in.

2,500+ automated tests

Payroll, leave and approvals are tested before every release, so a policy change does not quietly break a payslip.

BUILD YOURS

Need a system like this? We build them.

ZivoHR is sold and supported at zivohr.com. If your business needs its own HR, payroll or approvals system, we build it in two-week cycles, and you own the code.

BOOK A CALL PRICING AND PROCESS VISIT ZIVOHR.COM