Hire-to-retire: exception and recovery register
This register records every time the hire-to-retire process goes off course and what was done to put it right. HR, accounts or an administrator logs each exception as soon as it is found, and the owner reads the register to see which problems repeat. The aim is a clear trail: what went wrong, what it cost, who fixed it and when it was closed.
When to use it
Log an entry the moment you find a joiner without papers, a salary paid on the wrong terms, an exit that was not cleared, or any recovery of money from an employee. Use it also when a corrected entry replaces an earlier one, so the original is never overwritten.
The template
The first table lists the usual exception types and the first response. The second is the log itself, one line per exception.
| Exception type | What it looks like | First action | Recovery owner | Close when |
|---|---|---|---|---|
| Joined without papers | Employee working with identity or bank papers missing | Ask for papers within a set number of days and note the date | HR | Papers are filed and checked |
| Pay on wrong terms | Salary differs from offer or approved revision | Hold the next pay for that line and check the approval | Accounts | Corrected and difference settled |
| Excess or short payment | Amount paid differs from amount due | Compute the difference and tell the employee in writing | Accounts | Recovered or paid, with receipt |
| Uncleared exit | Employee left without handover or asset return | List what is pending and send a written reminder | Department head | Handover and assets confirmed |
| Late or missed review | Probation or pay review date passed | Schedule the review and record the reason for delay | Department head | Decision recorded |
| Reopened settlement | A paid settlement is questioned | Pull the file and recompute from records | Owner | Both sides accept in writing |
| Date found | Ref | Employee | Exception type | Amount in ₹ | Found by | Recovery step | Owner | Target date | Closed on |
|---|---|---|---|---|---|---|---|---|---|
How to fill it
- Ref: a running number, such as HR-EX-001, never reused.
- Exception type: choose from the first table; add a new type only when none fits.
- Amount in ₹: the money involved, positive for an overpayment to recover, and write "owed to employee" in the recovery step when the business owes money.
- Found by: the person who noticed it, so a reviewer can ask how it was found.
- Recovery step: the exact action, such as a written request or an adjustment against the next payment. Recoveries from wages or settlements are limited by law and by your terms of employment, so check before deducting.
- Closed on: fill only when evidence is filed.
Deductions from wages, recovery of advances and settlement dues are regulated. Check the current rule on the official portal or with your CA before acting.
Example row
| Date found | Ref | Employee | Exception type | Amount in ₹ | Found by | Recovery step | Owner | Target date | Closed on |
|---|---|---|---|---|---|---|---|---|---|
| 6 November | HR-EX-014 | Arun Das, store assistant | Excess or short payment | 3,500 | Accounts, during the monthly check | Written note to Arun; agreed adjustment against the December salary | Meera | 10 December |
Review and sign-off
- The owner reviews the register; the person who logged an exception does not close their own entry alone.
- Review monthly, and read all open entries past their target date.
- Escalate when an entry has passed its target date twice, when an amount is disputed by the employee, or when the same exception type appears three times in a month.
Keeping it up to date
- Keep the register and the evidence behind each closed entry for the period your CA or the law requires.
- Correct a wrong entry with a new line that refers to the old one, and never delete the original.
- At each month end, count open and closed entries by type, and use the counts to decide which step in the process needs a firmer control.