Customer Scenarios

How should we correct a payslip that was opened but not yet acknowledged?

An anonymized customer question, adapted to SugarHR’s published workflow. This is practical guidance, not a verified implementation result.

Identify the record's current state and follow the supported void, recall or correction process. Retain the relationship between the original and corrected versions.

The situation

An employer found an error after the statement had been read but before employee acknowledgment was complete.

Why this condition changes the workflow

Read status and acknowledgment are different facts. Verify what changes when a signature already exists, and avoid promising an invisible rollback merely because another unsent example can be edited.

A practical sequence for this situation

1. Correct the identified record. Find the affected employee and original batch, check its acknowledgment state and use the supported correction process. Preview the approved replacement and preserve the link between old and revised information.

2. Interpret each recorded event. Review delivery, opening, active acknowledgment and any automatic event separately. Confirm which fields are actually available and whether they establish the step the organization needs to document.

3. Schedule approved data deliberately. Verify the batch, date and relevant time settings before scheduling. Check the supported method for changing or cancelling the plan, and do not treat unapproved figures as ready for unattended release.

4. Define the purpose of an access window. Establish why a limit is needed, when it starts and how employees will obtain past details. Test access behavior and administrator record retention as separate questions.

What a useful test should demonstrate

Keep an identifiable original record, the reason for correction, the authorized replacement and the result of re-delivery. Review what the current state allowed the administrator to do. If the required change or record relationship cannot be demonstrated, do not treat a successful unrelated draft edit as proof that the live error is resolved.

Questions to resolve in this context

How should an incorrect amount, recipient or version be corrected?

Identify the affected employee and original batch, then check its current state. Use the supported void, recall or correction process, preview the approved replacement and retain its relationship to the original. Verify restrictions for acknowledged records instead of promising an invisible rollback. Read the general explanation.

How should delivery and acknowledgment events be used?

Use delivery records to investigate message arrival, opening to understand access, and active acknowledgment to record the requested employee action. Label automatic events separately. Decide what must be demonstrated before choosing a status; a completed task label alone can conceal important differences. Read the general explanation.

Related guidance

Test the conditions that matter to your team

Use a sample or anonymized approved file to check the specific conditions described here. Confirm any unverified account, channel or record requirement before a live send. Start Your Free 1-Month Trial.

Published by SugarHR Help Center. How we review guidance.

Start Your Free 1-Month Trial