How can we retain payslip history without leaving acknowledgment tasks open indefinitely?
Retain useful payslip history while setting acknowledgment rules separately, without calling an automatic task status proof of employee review.
Read caseCUSTOMER NEEDS & DECISIONS
Match the requested employee action to its purpose without confusing automatic and active events.
Retain useful payslip history while setting acknowledgment rules separately, without calling an automatic task status proof of employee review.
Read caseSome customers need an explicit employee response; others do not need handwriting. These conversations distinguish viewing, active acknowledgment and a system-generated status, including questions about history and overdue tasks.
Describe the purpose of the action first. A button, a signature image and automatic closure are not interchangeable evidence. Do not infer payment or wider employment outcomes from a statement response.
Requirements checklist · All customer cases · Record your requirements
YOUR NEXT STEP
Leave your details so the SugarHR team can follow up.
Prefer email? office@sugarhr.com