History and review controls

Know what changed. Check the recorded history.

Inspect events, applicable rule versions and a built-in check for changes to the recorded sequence.

The HRMS koala presenting a flow document
Illustrative mock-up · sample data
Audit trail · illustrative mock-up with sample events.

What to explore

  1. 01Review payroll and employee events.
  2. 02Use maker-checker stages for rule changes.
  3. 03Run the tenant audit-history check.

Where this helps

For administrators and reviewers who need an explanation trail.

What to check in a walkthrough

Ask to see the starting record, the action taken and the resulting state. Check what is saved, what uses sample data and what depends on another service.

Availability

The history check is tamper-evident, not independently immutable. It is not an audit certificate or a compliance guarantee.

Try the idea behind the history check

This small demo runs in your browser. It links each event to the one before it, so a quiet edit shows up when the sequence is checked.

  1. #0647
    LeaveApproved
    …
  2. #0648
    RuleVersionApproved
    …
  3. #0649
    PayrollRunCalculated
    …
  4. #0650
    PayrollRunApproved
    …
  5. #0651
    PayrollRunLocked
    …

Each event stores a fingerprint (SHA-256) of its own details plus the previous event’s fingerprint. Edit any event’s text, then run the check.

Working illustration in your browser with sample events. It shows the idea of a tamper-evident sequence; it is not an independent audit or a guarantee of immutability.

Illustrative mock-up · sample data
Effective-dated rules with maker and checker · illustrative mock-up.
Illustrative mock-up · sample data
History and review controlsModule recording · coming with real product captures
Module recording pending. Until it is ready, the animated explainer shows the overall story with sample data.

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