A new overtime policy takes effect on 1 October, while September payroll and attendance must remain tied to the previous rule.
Policy history and change control
Change the policy from the right date without rewriting the past.
Preserve historical policy outcomes while making attendance, leave, payroll, employee and organisational changes active from an approved effective date.
Representative operating scenario Current boundaries stated clearly
Employee & organisationIllustrative product interaction
AM
Aarav MenonOperations · Chennai
ManagerLocationGradePolicy
One governed employee record
Addresses, dependants, prior experience, bank details and documents remain attached to the same employee identity.
98%Profile complete
12Documents
3Dated changes
Organisation context follows the employee
Business unit, department, location, grade, employment type and reporting line can guide policy, access and workflow.
6Policy dimensions
4Reporting levels
2Active locations
History stays effective-dated
Transfers, promotions, manager changes, salary revisions and exits retain the date from which each change applies.
01 OctNext transfer
7Lifecycle events
100%History retained
Who this page is for
For HR teams that need policy changes, transfers, salary revisions and workforce events to retain defensible history.
The operating problem
What usually breaks before the software conversation begins.
Use these symptoms to determine whether the issue is data, policy, ownership, monthly closure or an unsupported product requirement.
01
Policy updates silently overwrite previous logic.
02
Payroll and attendance cannot be reproduced after a change.
03
Transfers and salary revisions are recorded as current-state edits.
04
Audit reviews cannot determine which rule applied on a past date.
A practical operating approach
Resolve the policy first, then automate the cycle.
The exact product setup is validated during discovery and demonstration. The sequence below keeps the rule, owner and downstream result connected.
Set the effective date
Create a dated change instead of overwriting the previous record.
Preview the affected population
Identify which employees and transactions the change will influence.
Activate with approval
Use authorised review before the new policy becomes active.
Retain before and after
Keep the historical rule and resulting transaction history available for review.
Connected product scope
View the full product The outcome depends on more than one isolated feature.
Review the upstream source, policy resolver, approval path and downstream output together.
Policy Configuration
Configure attendance, leave, payroll, approvals, permissions and notifications around the way your organisation actually works, while keeping every policy scoped, dated and reviewable.
ExploreCore HR
Centralise employee records, organisation structures, dated lifecycle changes and policy scope so downstream attendance, leave, payroll, performance and access decisions use the same governed foundation.
ExplorePayroll
Connect effective-dated salary structures, attendance and leave inputs, earnings, deductions, reimbursements, recoveries and statutory calculations in a payroll run that can be reviewed and rolled back before finalisation.
ExploreCompliance & Audit Logs
Use role and data scopes, operational audit, security events, sensitive-data access records, effective dates and controlled exports to make important actions easier to reconstruct.
Explore
Evaluation questions
Bring this use case into a demo Confirm the exact policy, evidence and product boundary.
The answers below reflect the supplied product source. Customer-specific commitments still require live-product and commercial validation.
What does effective-dated mean?
The system stores when a rule or employee change becomes applicable instead of simply replacing the previous value.
Can a policy be previewed before activation?
The product material describes previewing which policy resolves for a given employee and date.
Does this remove the need for approvals?
No. Effective dates preserve timing and history; authorised review and organisational governance remain necessary.
Policy history and change control
Validate this use case with one real policy or transaction.
Bring a representative employee, location, shift, payroll month or output. We will shape the walkthrough around the exact operating case.