People records, time and payroll—with a clearer history

When someone asks “why”, have the record ready.

Bring employee details, leave, attendance and payroll review into one platform, with a history that helps your team understand what changed and which rules were used.

Availability. For evaluation with sample data. Production authentication and independent payroll-rule validation remain outstanding. Do not upload real employee or salary information to the demo.

Illustrative mock-up · sample data
Illustrative mock-up built from the product’s module names, using sample data. A real interface capture will replace it; see the availability details before using real data.
The HRMS koala, dressed in a navy HR waistcoat, welcomes you

Sound familiar?

“Why has my salary changed?” should not become a search through messages and spreadsheets.

HR handles the record. A manager approves the leave. Finance checks the payroll. When the details sit apart, even a simple question can move between several people.

Keep people workflows and their history connected, so your team has a clearer starting point for review.

An employee’s salary question travels between HR, a manager and finance when details sit apart; with a connected record it reaches one shared history. One record + history inputs · rule · review HRstaff record Managerleave approval Financepayroll check “Why did it change?”
One question, three places to look. A simple drawing, not measured data.

What makes the approach worth exploring

People operations you can explain.

A final number is only part of payroll. The employee record, time inputs, adjustment and applicable rule matter too. HRMS is built around keeping that history available for review.

Interactive illustration with sample figures.

  1. Employee record

    Basic pay ₹ 52,000 from the salary structure on file since January.

  2. Time inputs

    April attendance: one regularisation approved by the manager, no loss-of-pay days.

  3. Adjustment

    Travel ₹ 2,400 added as a run input by the payroll maker, with a reason.

  4. Rule version

    Tax calculated under rule version v2, effective 1 April, approved by a checker.

  5. Review stage

    Run inputs reviewed, calculated, approved and locked. Each step is a recorded event.

The difference to evaluate is the explanation trail: can your team trace a result back to the records and rules behind it?

Watch · about 40 seconds

The story behind one number

A short animated explainer follows one salary question from the employee record to the locked payroll run and the history check. It uses sample data and is not a screen recording.

Full walkthrough page

Follow one workflow through

How the journey works

  1. 1

    Build the employee picture

    Review employee records, departments, reporting lines and changes in employment.

  2. 2

    Bring time and people workflows together

    Work through leave requests, attendance corrections, onboarding tasks and employee notices.

  3. 3

    Review payroll in stages

    Move a payroll run through input review, calculation, approval and locking. Inspect the rules and adjustments behind the result.

  4. 4

    Keep a history you can inspect

    Review recorded changes and run the audit-history check. This supports investigation; it is not an external certification.

Illustrative mock-up · sample data
Step 1 · illustrative mock-up, sample data
Illustrative mock-up · sample data
Step 2 · illustrative mock-up, sample data
Illustrative mock-up · sample data
Step 3 · illustrative mock-up, sample data
Illustrative mock-up · sample data
Step 4 · illustrative mock-up, sample data

Find your situation

Start with the work you actually do.

Understand how the people side is being run.

Growing headcount makes informal approvals and scattered records harder to manage.

Review employee information, people workflows and payroll stages in a shared environment.

Bring your current HR process to a sample-data walkthrough.

A closer look, without the sales theatre

See what is there. Ask what still needs work.

24seeded sample employees in the local review
651recorded events in the local review’s history

The local review started the core platform with 24 seeded employees and 651 recorded events. It also exercised supporting AI, geolocation and document services. This is evidence of local evaluation, not a production customer result.

Availability. For evaluation with sample data. Production authentication and independent payroll-rule validation remain outstanding. Do not upload real employee or salary information to the demo.

Cover of the HRMS brochure: A payroll total should come with an explanation.

Take it to your team

A 14-page brochure for the people who were not in the room.

The same story in a format you can share: the problem, the four-step journey, what the sample-data preview shows and what still needs checking before live use.

Next step

Bring one real workflow question.

Bring your current HR process to a sample-data walkthrough. We can use that starting point to assess fit, show the relevant interface and make the remaining work clear.

Start with a question, not a commitment. Use sample or anonymised information.

Request a sample-data walkthrough