Freeze the worker record
Record employee, role, effective date, period and source owner.
Workflow blueprint
An employee payroll system should show who supplied each pay input
A page-specific review aid, not a universal product or compliance claim.
Keep employee record, period, time, rule reference and returned response distinct without making a Mauritius tax conclusion.
TL;DR — Keep employee record, period, time, rule reference and returned response distinct without making a Mauritius tax conclusion.
Trace the time
Relate attendance, absence, overtime note, approval and missing evidence.
Review the run
Keep compensation, deduction, export, rejection and response distinct.
Escalate locally
Assign wage, tax, leave, social-security, benefit and filing questions.
Page-specific decision aid
Employee pay-input passport
A worker, effective date, pay period, time source, compensation instruction, approval, export and correction passport.
- ✓Worker changes keep effective dates
- ✓Provider response is not a ruling
- ✓Local questions remain assigned
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Worker and period identity
- ✓Time and effective-date source
- ✓Approval and export history
- ✓Local specialist owner
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow