Use cases

Start with what is actually going wrong

Sixteen problems HR and payroll teams in India bring us, what each one costs, and what changes when it stops.

Time, attendance and shifts

Getting an accurate picture of who worked when, across sites that all work differently.

The problem

Attendance arrives as registers, WhatsApp messages and a biometric export, and someone consolidates it into a spreadsheet at month end.

What it costs

The consolidation is redone every cycle and cannot be checked. Disputes about a missing day surface after payroll has run, when correcting them means an off-cycle adjustment rather than an edit.

How HRZyra handles it

Each site captures attendance however suits it — biometric device, geo-fenced mobile app, web or kiosk — and all of it lands in one record that leave and payroll read directly.

What changes

Month end starts with a payroll run instead of a reconciliation, and any disputed day has an auditable record behind it.

The problem

Rotating and night rosters are planned in a spreadsheet, sent out by WhatsApp, and the allowances they generate are worked out separately afterwards.

What it costs

Coverage gaps are found after the shift is missed, swaps happen informally with no record, and night and overtime allowances are recalculated by hand every cycle — which is where the pay disputes come from.

How HRZyra handles it

Rosters are built and published in the system with coverage visible by site, swap and cover requests approved on the record, and the resulting allowances flowing into payroll as a consequence of the roster.

What changes

The roster that was worked is the roster that gets paid, and gaps are visible while there is still time to fill them.

The problem

Leave is requested over email or chat, balances are tracked in a spreadsheet, and entitlement differs depending on which state the employee sits in.

What it costs

Nobody can say where a request is sitting, employees ask HR for a balance they should be able to see, and carry-forward and encashment are calculated by hand at year end — with the state-specific rules applied from memory.

How HRZyra handles it

Leave types, accrual, carry-forward and lapse configured once per location against the Shops & Establishments Act that applies there, with employees applying from mobile and seeing their balance before they submit.

What changes

Balances maintain themselves, entitlement follows the law of each location, and finance can see accrued leave liability without asking HR to work it out.

The problem

Project hours are logged in one tool for client invoicing and attendance in another for payroll, and the two never quite agree.

What it costs

Utilisation reporting is built on estimates, labour cost per project is approximate, and the same person fills in two systems every week.

How HRZyra handles it

Time booked against projects, clients and cost centres, approved alongside attendance, and reconciled against it so booked hours and paid hours agree.

What changes

Client invoicing and internal labour costing come from one approved set of hours rather than two competing ones.

Payroll and compliance

Paying people correctly under rules that change from one state to the next.

The problem

Payroll inputs come from four places, get keyed into a template, and the run takes days that the team cannot spend on anything else.

What it costs

The cycle consumes the finance and HR calendar every month, depends on one person who understands the spreadsheet, and leaves no time to check the output before the money moves.

How HRZyra handles it

One run that reads the attendance and leave your managers already approved, calculates statutory deductions per employee, and produces the bank file and the filings from the same numbers.

What changes

Payroll becomes a review step rather than a rebuild, and it stops being a single point of failure in one person’s file.

The problem

PF, ESI and TDS are recalculated by hand each cycle, and Professional Tax gets applied from whatever rule someone remembers.

What it costs

Errors surface after the salary credit, when fixing them means an adjustment, an apology and a correction to a filing that has already gone in. Trust is the expensive part, not the arithmetic.

How HRZyra handles it

Statutory deductions computed in the run against each employee’s own state and entity, with Form 24Q, Form 16 and ECR generated from the same calculation that produced the payslip.

What changes

The return and the payslip cannot disagree, because they come from one calculation — and every revision carries who changed it and when.

The problem

Offices in different states mean different rules, and the payroll system applies one national default to all of them.

What it costs

Professional Tax gets deducted in states that levy none, minimum wage notifications are missed because nobody tracks them per state, and each registration ends up with its own spreadsheet and its own filing calendar.

How HRZyra handles it

Each location carries its own statutory profile — Professional Tax position, minimum wages, Labour Welfare Fund and the applicable Shops & Establishments Act — applied automatically in a single payroll run.

What changes

One run covers every state correctly, and filing status is visible per entity and per state rather than per person’s memory.

The problem

Reimbursement claims arrive as photographed receipts in an email thread and get paid whenever finance next gets to them.

What it costs

Employees chase their own money, approval depends on who happens to be available, and out-of-policy claims are argued about after submission rather than stopped at it.

How HRZyra handles it

Claims raised from mobile with the receipt attached, policy limits applied at submission, routed for approval by amount and cost centre, and reimbursed through payroll with the right tax treatment.

What changes

Claims settle with the salary instead of a separate payment run, and spend is visible by department and cost centre.

People operations

Hiring, onboarding, documents and the questions that fill an HR inbox.

The problem

The employee master is a spreadsheet, and so are the salary structures, the leave balances and the joiner list — each maintained by a different person.

What it costs

The versions disagree, nobody can say which is authoritative, and the person who understands the formulas becomes a dependency the company cannot afford to lose.

How HRZyra handles it

One employee record holding personal, statutory, contractual and organisational detail, which payroll, attendance and compliance all read from, with every change attributed and dated.

What changes

There is one version to disagree with, and the company stops depending on one person’s file.

The problem

Contracts, ID proofs and policy acknowledgements sit in folders organised by whoever filed them.

What it costs

Producing a document for an audit means searching a shared drive, nobody can say who has access to what, and contracts and licences lapse because nothing was watching the dates.

How HRZyra handles it

Documents stored against the employee they belong to with role-based access and audit logging, expiry tracking on contracts and licences, and bulk letter generation from templates.

What changes

Retrieval is a lookup rather than a search, lapses become a calendar item rather than a compliance incident, and who saw what is answerable.

The problem

Documents are collected on the joiner’s first morning, statutory registration starts late, and IT and finance hear about the new hire the same day they arrive.

What it costs

A new joiner’s first impression is paperwork, their first payroll cycle is wrong because UAN and bank details arrived late, and the equipment they need is ordered after they need it.

How HRZyra handles it

Pre-boarding that finishes before the start date — document upload and verification, UAN, ESIC and bank collection, and tasks assigned across HR, IT, finance and the reporting manager.

What changes

Day one is about the job, the first payroll runs correctly, and what was issued at joining is what gets recovered at exit.

The problem

Requisitions are approved over email, CVs arrive in an inbox, and interview scheduling is a calendar negotiation.

What it costs

Nobody can say how many roles are open or where a candidate stands without asking the recruiter, roles get advertised before the budget is signed off, and an accepted candidate is typed into the HR system from scratch.

How HRZyra handles it

Requisition through offer in one pipeline — budget approval before a role goes live, AI-assisted shortlisting, scheduling against panel availability, and digital offers that hand the accepted candidate to onboarding.

What changes

Pipeline status is answerable without a conversation, and hiring stops leaking into re-entry at the offer stage.

The problem

Payslip requests, leave balance queries, tax declaration deadlines and address changes all arrive as individual messages to the same few people.

What it costs

Answering them is most of an HR generalist’s week, the same question gets answered differently depending on who takes it, and the work is invisible — it never appears as a project, only as a reason nothing else got done.

How HRZyra handles it

Payslips, Form 16, tax declarations, leave, attendance and requests moved to the employee’s phone, with detail changes submitted for approval rather than emailed.

What changes

The answer is available before the question gets asked, and HR time moves from responding to work that compounds.

The problem

Goals set at the start of the year are not opened again until the review, feedback is gathered by email, and the rating lives in a document.

What it costs

The review becomes an exercise in remembering, managers rate on different scales, and the outcome has no connection to the increment that follows — so the increment gets decided somewhere else entirely.

How HRZyra handles it

Goals cascaded from company to individual, continuous check-ins recorded through the period, 360° feedback, and configurable cycles whose increment recommendations flow into payroll.

What changes

The evidence already exists when the cycle opens, ratings are consistent across managers, and the outcome reaches pay without being re-entered.

Visibility and reporting

Answering questions about the workforce without assembling a spreadsheet first.

The problem

Leadership asks about headcount, workforce cost or attrition and the answer takes days to assemble.

What it costs

Decisions get made on the last figure anyone remembers, attrition is noticed after the resignations rather than before, and the true cost of the workforce is known only at year end.

How HRZyra handles it

Dashboards reading the same live records payroll and attendance run on — headcount, workforce cost, attrition by department, tenure, manager and location, and statutory filing status across entities.

What changes

Workforce questions resolve on a dashboard, and the reported cost reconciles with what was actually paid because it is the same record.

The problem

Every recurring report — headcount, muster, statutory register, cost by department — is rebuilt by hand from exports.

What it costs

The report is out of date by the time it is circulated, two people producing the same report get different answers, and the effort repeats every month regardless of whether anyone acts on it.

How HRZyra handles it

Reports generated from live operational data, scheduled to finance and leadership, with statutory registers maintained in the formats inspections expect and a full data export available.

What changes

Recurring reporting stops being a monthly task, and the numbers in it match the numbers in payroll.

Or start from your role

The same problems look different depending on which side of them you sit.

Which of these is costing you the most?

Bring the one that hurts. We will show you what it looks like once it stops being a manual job.

Free migration · No credit card