Payroll mistakes and how to undo them

Wrong salaries usually come from these setup slips. Here's how to spot and fix each one.

Good news first: a payroll run can always be processed again after you fix something. Nothing is final until you've paid the bank.

1. Processing before attendance is complete

What you see: many people with loss of pay.

Why: days with no attendance and no leave that nobody decided on are loss of pay.

Fix: clear the missing days on the dashboard (leave or forgot to punch), then process the run again. Next month, wait for the reminder email two days before the pay date and clear them first.

2. PF, ESI or TDS added as salary components

What you see: PF deducted twice, or tax looks doubled.

Why: Orgwise works out PF, ESI, Professional Tax, LWF and TDS itself when they're switched on in Payroll Settings. Adding them as components as well deducts them twice.

Fix: remove those components from Salary Components and from employees' salaries, then process again.

3. Someone missing from the run

Why: they have no active salary, or they joined after the period.

Fix: add their salary in Employee Salaries and process again.

4. TDS too high for a new joiner

Why: their salary and TDS from their previous job this year weren't entered, so Orgwise thinks this is their only income, or that no tax was paid yet.

Fix: add it under Employee Salaries → Earlier income this year (from their Form 12B), or ask new joiners to fill it in during pre-boarding.

5. Wrong tax regime

Why: the regime in the profile doesn't match what the employee chose. Investment declarations only reduce tax in the old regime.

Fix: set the right regime in the employee's profile and process again.

6. Increment typed straight into the salary

What you see: no arrears, no letter, no history of the change.

Fix: next time use Salary revisions. For a back-dated change already typed in, add the arrears in One-off Pay.

Frequently asked questions