Is Ragenaizer HRMS only for India?

No. The payroll engine holds no country in its code. Contributions, income tax, regional levies and their eligibility conditions come from an uploaded, schema-validated and versioned country pack, and the calculator evaluates that pack's formulas. India ships configured; anywhere else is a pack to author, not a change to the software.

Can a payslip be corrected after approval?

Not by editing it. An approved or paid payslip is immutable. A correction is made as a new adjustment record against a later run, so a payslip cannot be quietly rewritten after the fact.

Does payroll post to the accounts automatically?

Yes. An approved payroll run is handed to Ragenaizer Accounts as a salary journal, with statutory dues raised as bills to pay. No payroll figure is re-keyed into the books.

What happens when an employee transfers office mid-year?

Transfers are kept as history with effective dates. Arrears are computed against the jurisdiction that applied at the effective date rather than the employee's current office, which is one of the seven invariants the engine asserts.

How do employees record attendance?

Geofenced clock-in against the office boundary with location pings recorded, or an NFC card tapped at the gate. A missed punch becomes a regularisation request routed to an approver rather than a silent edit.

Is there an employee self-service portal?

Yes. Employees see their payslips, leave balance and loan balance, and can raise profile-change requests that route to HR for review.

The business OS · People & payroll

Payroll that shows
its working.

Name: Ragenaizer HRMS
Price: 1200 INR
Author: Ragenaizer

Every payslip keeps the arithmetic that produced it — the days counted, the proration applied, the rule behind each statutory deduction — and the engine asserts a named set of checks before it will let the run through.

One module, 4 products. Sold separately almost everywhere else as core HR, payroll, recruitment and shift & attendance.

Walk one payslip through the five steps the engine records

Meera Iyer Payroll Executive · Pune office · India PAYSLIP PS-2026-07-0184 · JULY 2026

Country rules

The statutory rules are data, not code.

A payroll engine that hard-codes provident fund and professional tax can only ever run one country, and every rate change is a release. Here a country's rules are a versioned pack you upload — validated against a published schema before it is allowed anywhere near a payslip.

Uploaded

A pack, not a patch

Contribution rules, tax slabs, regional levies, eligibility conditions and the formulas between them all live in the pack. Nothing about a country is compiled into the engine.

Validated

Checked before it lands

Packs are validated against a published schema on the way in. A malformed rule is rejected at upload, not discovered on the twenty-eighth of the month.

Versioned

Every version kept

Each country keeps its version history and you activate the one that applies. When a rate changes mid-year, last quarter's payslips still explain themselves under the rules they were run on.

Resolved

Jurisdiction by office

The rules that apply are resolved from the office an employee sits in, and arrears are computed against the jurisdiction in force at the time — not wherever they work today.

The actual product

What the HR desk opens on.

Attendance for the last thirty days, who is in today, what is waiting on you, and the month's payroll — before you have opened a report or asked anyone for a number.

Ragenaizer HRMS — attendance over the last 30 days, today's headcount, pending approvals and the month's net payroll — **People** — today's attendance, what needs a decision, and this month's payroll on one screen.

What it covers

Hire to payslip to ledger.

The whole employment record in one place, ending where it should — a payroll run handed to finance as a journal rather than a spreadsheet emailed to the accountant.

PeopleThe full employment record — joining, designation, department, office, banking and registration IDs — with an org chart drawn from the reporting lines you actually set.

Geofenced attendanceClock in inside the office boundary, with location pings recorded and a live view of who is where — for the people whose work is somewhere rather than anywhere.

NFC cardsTap-in on a card for shop floors and sites where phones are impractical. Cards are issued, deactivated and reissued without touching the employee record.

Regularisation & overtimeA missed punch or an extra shift becomes a request with an approver, not an edit. What payroll consumes is a decision someone made, with their name on it.

LeaveLeave types with their own balances and accrual, a calendar the team can see, encashment, and an HR override that still records who marked it and why.

Payroll draftsProcess to a draft, read the numbers, recalculate, and only then approve. Payroll stops being a button nobody wants to be the one to press.

Send to financeAn approved run hands the salary journal to Accounts and raises the statutory dues as bills to pay. Nobody re-keys a payroll figure into the books.

Bank filesExport the run as a bank transfer file, or as CSV when your bank wants its own shape. Payment day is an upload rather than an evening of typing.

Statutory recordsEstablishment registrations, employee registration IDs, tax regime elections and investment declarations that are validated rather than merely collected.

Loans & advancesApprove a loan, disburse it, and the EMI recovers itself from payroll each month — with the balance visible to the person repaying it.

Self-servicePayslips, leave balance, loan balance and profile changes that route to HR for review — so the answer to most questions is a screen rather than an email.

RecruitmentJob postings, applications and internal moves, ending in an employee record rather than a fresh form somebody retypes on day one.

Transfers with historyMove someone between offices, departments or managers and the change is kept as history — which is what lets arrears be computed on the jurisdiction that applied then.

Salary versioningSalary structures are versioned with effective dates, so a mid-year revision produces arrears against the right structure instead of quietly rewriting history.

One employee record

Where the month actually goes.

Attendance, leave, loans and a salary revision all end up in the same payslip, and the payslip ends up in the books. Each step is a document with an owner, not a message somebody has to remember to forward.

Clock-in inside the boundary — or a card tapped at the gateAttendance

26 working days

A missed punch regularised, approved by the reporting managerApprovals

named approver

One day of unpaid leave becomes the month's proration factorLeave

25 / 26

Draft payroll reviewed, checks asserted, then approvedPayroll

7 checks

Sent to finance — salary journal posted, statutory dues raised as billsHRMS → Accounts

0 re-keying

one record, start to finish0 spreadsheets in between

Straight answers

The things people ask on the first call.

Is this only for India?

No. The engine holds no country in its code. Provident-fund style contributions, income tax, regional levies and their eligibility conditions all come out of an uploaded country pack, and the calculator evaluates that pack's formulas.

India ships configured. Anywhere else is a pack to author and validate, not a change to the software.

Can we see how a payslip was calculated?

Yes — that is the point of the page above. Every processed payslip stores a calculation proof: working days, days present, loss of pay, the proration factor, each earning, each statutory rule that ran (including the ones that did not apply), and the invariant assertions with the figures they were checked against.

What stops a bad payroll run going out?

Seven named invariants are asserted before a run proceeds. Two are hard stops — a negative net pay and a payslip without a recorded engine version will block processing outright. The other five are raised for review with their evidence attached.

Can we correct a payslip after approving it?

Not by editing it. An approved or paid payslip is immutable; a correction is a new adjustment record against the next run. That is deliberate — a payslip somebody could quietly rewrite is not evidence of anything.

Does payroll reach the accounts?

Directly. An approved run is handed to Accounts as a salary journal, with the statutory dues raised as bills to pay. Nobody re-keys a payroll figure, so there is no second version of the number to disagree with.

What if someone changes office mid-year?

Transfers are kept as history with their effective dates. Arrears are then computed against the jurisdiction that applied at the time rather than the current one — which is one of the seven checks the engine asserts.

How do people clock in?

Geofenced clock-in against the office boundary with location pings recorded, or an NFC card tapped at the gate for shop floors and sites where phones are impractical. A missed punch becomes a regularisation request with an approver, not a silent edit.

Can employees answer their own questions?

Self-service carries payslips, leave balance, loan balance and profile-change requests that route to HR for review. Most of what lands in an HR inbox is a screen the person already has.

Let the payslip answer the question.

Give your team a number they can check themselves, and give payroll a month-end that ends.

This is one module of the business OS, not a point tool. HRMS on its own does what is usually sold as four: people, payroll, recruitment and shifts. The same seat opens Meetings, Mail, Chat, Drive, CRM, HR, Accounts, Projects, Procurement, Learning and Research — eleven modules covering about twenty-eight products' worth, on one login, one permission model and one ledger. You are not buying an HRMS; you are putting the company on one system.

See pricing Book a walkthrough →