Workflow blueprint

Payroll software for payroll service providers should preserve the client handoff before a run

A page-specific review aid, not a universal product or compliance claim.

Use the provider client-run passport to keep client instructions, pay-period source, provider response and correction ownership connected for a Mauritius evidence review.

TL;DR — Use the provider client-run passport to keep client instructions, pay-period source, provider response and correction ownership connected for a Mauritius evidence review.
1

Frame the case

Name the client, period, supplied records, cutoff and missing information.

2

Trace the evidence

Relate worker source, configuration edition, approval and export identity.

3

Review the exception

Capture acceptance, rejection, partial result and correction request without overwriting the first response.

4

Assign the next owner

Assign wage, tax, benefits, filing, payment and client-communication questions.

Page-specific decision aid

Provider client-run passport

A client instruction, pay period, worker source, rule edition, provider response, rejected input and correction owner.

  • Client source stays attached to the run
  • Provider acceptance is not correctness
  • Corrections keep their first response
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.

  • Client and pay-period identity
  • Worker and time source
  • Provider response lineage
  • Named payroll specialist

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