[Analysis] 34 Common Payroll Mistakes under the Code on Wages 2019 – Errors by Payroll Area | Corrective Controls | Monthly Exception Report
- Blog|Labour & Industrial Laws|
- 18 Min Read
Treating CTC as wages heads the 34 common payroll mistakes in Taxmann’s HR Guide to Code on Wages. The control for each and the monthly exception report.
- By Taxmann
- |
- Last Updated on 16 November, 2026

Table of Contents
- What are the 34 common payroll mistakes under the Code on Wages?
- Can CTC be treated as wages?
- Can CTC be compared with minimum wage?
- What goes wrong in full and final settlement?
- What goes wrong with deductions from wages?
- Why are overtime and statutory bonus missed?
- Which employees and records get left out?
- Where do contractor wage controls fail?
- What is a payroll exception report?
- How should payroll mistakes be corrected?
- Quick answers
1. What are the 34 common payroll mistakes under the Code on Wages?
They are the errors that Chapter 28 of the book, Common Mistakes by HR and Payroll Teams, numbers from 1 to 34, each followed by the control the book recommends. Most of these payroll compliance mistakes under the Code on Wages, 2019 are not deliberate; they usually arise because salary structures, payroll software, appointment letters, contractor controls, attendance records, deduction approvals and monthly compliance reports are not aligned (para 28.1).
Repetition can turn small payroll errors into a large compliance exposure. In the book’s illustration, a Rs. 1,000 minimum wage shortfall for 100 employees over 12 months becomes Rs. 12,00,000, before considering claims, compensation, penalty or interest-type consequences where applicable (para 28.2).
The table groups the common payroll mistakes by area. The numbering is the book’s and the controls are condensed from it; the grouping is editorial.
| Area | No. | Mistake (book para) | Corrective control |
|---|---|---|---|
| CTC and wage definition | 1 | Treating CTC as wages (28.3) | Maintain CTC, gross salary payable, statutory wages, minimum wage payable, bonus wage, overtime wage base and full and final (F&F) wage base as separate values |
| CTC and wage definition | 2 | Applying the wrong wage definition (28.4) | Tag every payroll component as one or more of: included wage component, excluded component, included in 50% wage test, reimbursement, employer contribution, statutory benefit, variable pay, terminal benefit, remuneration in kind |
| CTC and wage definition | 3 | Excessive allowance-heavy salary structures (28.5) | Run the 50% wage rule test, add back the excess where applicable, recompute PF, gratuity, bonus, leave encashment and overtime, and update the salary annexure and payroll master; test at joining, revision, restructuring, new allowance creation and software migration |
| CTC and wage definition | 23 | Outdated appointment letters (28.25) | Issue updated appointment letters, addendums or salary annexures covering wage period, salary structure, statutory bonus, overtime, deductions, notice period, F&F, reimbursement, policy incorporation and work location, matching payroll configuration |
| CTC and wage definition | 27 | Treating fixed payments as reimbursements (28.29) | Treat actual bill-supported business expenses as reimbursements; a fixed monthly payment without bills is an allowance, and food coupons or mobile recharge need a remuneration in kind review |
| Minimum wages | 4 | Not checking minimum wages State-wise (28.6) | Record work State, city or zone, nature of employment, role, skill category, effective date, notification reference and wage period; multi-State employers should maintain a minimum wage master |
| Minimum wages | 5 | Not mapping skill category (28.7) | Map each role to a skill category after reviewing actual duties and the applicable notification; designation alone is not enough |
| Minimum wages | 6 | Comparing minimum wage with gross CTC (28.8) | Compare against the actual wage payable and legally relevant components, not total CTC |
| Full and final settlement | 7 | Delayed full and final settlement (28.9) | Create an off-cycle F&F workflow; payroll should receive the exit trigger immediately, not wait for the month-end payroll cycle |
| Full and final settlement | 8 | Counting two working days from the wrong date (28.10) | Count from the effective cessation date or relevant separation event (the safer approach) and define the trigger date clearly in the internal F&F policy |
| Full and final settlement | 9 | Holding entire F&F because an asset is not returned (28.11) | Pay earned wages within the statutory timeline and recover asset loss only through a lawful process; the F&F statement may show pending asset recovery separately |
| Deductions and deposits | 10 | Unsupported deductions (28.12) | Support every deduction with a legal or contractual basis, calculation, supporting document, employee communication, approval, deduction cap check, wage slip disclosure and register entry |
| Deductions and deposits | 11 | Ignoring the 50% deduction cap (28.13) | Keep total deductions within 50% of wages; for Central sphere establishments, carry the excess forward and recover it in instalments in succeeding wage periods |
| Deductions and deposits | 12 | Showing loss of pay (LOP) as a large deduction (28.14) | Show paid days and earned wages, then test other deductions against the earned wages for the wage period |
| Deductions and deposits | 28 | Not reconciling payroll with statutory deposits (28.30) | Reconcile PF, ESI, professional tax, TDS, labour welfare fund and contractor PF and ESI with the ECR, challan or payment proof, and bonus and wage payments with bank proof, every month |
| Overtime and bonus | 13 | Non-payment of overtime (28.15) | Capture extra hours in attendance or timesheet, take supervisor approval, check eligibility, pay through payroll, disclose on the wage slip, keep the overtime register and contractor overtime proof; no cash overtime outside payroll |
| Overtime and bonus | 14 | Treating performance incentive as statutory bonus (28.16) | Use separate payroll codes (STAT_BONUS, PERF_INC, SALES_INC, PROD_INC, FEST_BONUS, EXGRATIA, ESOP) and keep statutory bonus separate |
| Overtime and bonus | 15 | Bonus omission for eligible employees (28.17) | Prepare an annual bonus eligibility report that includes resigned and fixed-term employees, and compute bonus employee-wise, not only for employees active on the payout date |
| Overtime and bonus | 16 | Treating coupons and gifts as bonus (28.18) | Classify each payment or benefit, and pay statutory bonus clearly as statutory bonus with records and payment proof |
| Employee coverage | 17 | Ignoring white-collar employees (28.19) | Include managers, software, finance, HR, sales, remote, senior and fixed-term employees and support staff in the compliance review; do not exclude any category without review |
| Employee coverage | 32 | Not reviewing fixed-term, temporary and trainee categories (28.34) | Maintain separate but compliant records for fixed-term, temporary and daily wage employees, apprentices, trainees, interns and piece-rate workers; do not use labels to avoid compliance |
| Employee coverage | 33 | Ignoring remote employees (28.35) | Capture work location, home location, payroll State, attendance or timesheet, reimbursement and asset records, wage slip issue and the F&F process |
| Wage slips and records | 18 | Not issuing wage slips to all employees (28.20) | Issue wage slips to all employees, including senior, remote, white-collar, fixed-term, daily-rated and part-time employees, showing earnings, deductions, net pay and payment details |
| Wage slips and records | 19 | Weak attendance records (28.21) | Keep the suggested record for each employee type, such as an HRMS or approved timesheet for remote employees and vendor attendance plus site validation for contract workers; flexible work does not mean no records |
| Wage slips and records | 20 | Not preserving bank payment proof (28.22) | Preserve the bank upload file, bank debit confirmation, employee-wise credit report, transaction ID, failed payment report and reprocessing proof; do not close payroll until failed credits are resolved or escalated |
| Wage slips and records | 21 | Not maintaining statutory records and registers (28.23) | Generate the employee, attendance, wage, overtime, deduction and bonus registers, the F&F report and the contractor wage report from payroll software |
| Wage slips and records | 22 | Deleting old records during payroll migration (28.24) | Archive wage slips, wage registers, attendance, overtime and deduction records, bonus workings, bank payment proof, F&F statements, contractor wage records and audit logs before migration; do not switch off the old system until archives are verified |
| Contractors | 29 | Contractor wage gaps (28.31) | Do not clear contractor invoices without wage proof, and link contractor compliance with invoice approval |
| Contractors | 30 | Using contract labour in core activity without review (28.32) | Classify the activity as core, non-core, intermittent, temporary volume increase, specialist outsourced service or manpower supply, and document the reason before deployment |
| Contractors | 31 | Not verifying contractor licence and worker count (28.33) | Keep a contractor master tracking nature of work, worker count, licence requirement, number and validity, maximum permitted workers, PF and ESI registration, monthly wage proof, work order value and core or non-core classification; do not onboard without compliance due diligence |
| Systems and people | 24 | Poor payroll software configuration (28.26) | Configure payroll software as a compliance validation system: wage component mapping, 50% wage test, minimum wage master, deduction cap, overtime and bonus modules, F&F tracker, wage slips, register export, audit logs and maker-checker |
| Systems and people | 25 | Lack of maker-checker control (28.27) | Apply maker-checker approval to employee master creation, salary structure and bank account changes, deduction uploads, loan or advance recovery, overtime, bonus payout, F&F settlement and contractor invoice clearance |
| Systems and people | 26 | Not training line managers (28.28) | Train managers on attendance, overtime, contractor deployment, deductions, F&F triggers, work allocation, leave approval and employee communication |
| Systems and people | 34 | No monthly payroll exception report (28.36) | Every month, HR and payroll should review exceptions before closure; the target for most exceptions is nil |
2. Can CTC be treated as wages?
No. The book calls this the most common mistake: HR may compare CTC with the minimum wage, bonus ceiling, PF base or statutory wage definition, which is not correct (para 28.3). CTC, or cost to company, is an employer cost that can include employer PF, a gratuity provision, insurance and a variable incentive estimate that may not be wages actually payable for the wage period. Payroll should keep each value separate:
| Value | Purpose |
|---|---|
| CTC | Employer cost |
| Gross salary payable | Payroll processing |
| Statutory wages | Code on Wages and social security computation |
| Minimum wage payable | Minimum wage comparison |
| Bonus wage | Bonus eligibility and calculation |
| Overtime wage base | Overtime calculation |
| F&F wage base | Exit settlement |
The wage definition is the second trap (para 28.4). Some employers assume that only basic pay is wages, others that all allowances are excluded, and the book calls both approaches risky. Section 2(y) includes basic pay, dearness allowance and retaining allowance, if any, and if the specified excluded components exceed one-half, or such other notified percentage, of total remuneration, the excess is added back to wages (para 24.3). The common misclassifications:
| Component | Common mistake |
|---|---|
| Special allowance | Treated as automatically excluded |
| Fixed mobile allowance | Treated as reimbursement without bills |
| Fixed internet allowance | Treated as reimbursement without bills |
| Attendance allowance | Not reviewed as wage |
| Monthly assured incentive | Treated as variable even if guaranteed |
| Overtime allowance | Ignored in 50% wage calculation |
| Employer PF | Ignored in 50% wage calculation |
| Statutory bonus | Ignored in 50% wage calculation |
| Annual performance incentive | Mixed with statutory bonus |
| Food coupon or mobile recharge | Ignored as remuneration in kind |
On the three rows about the 50 per cent calculation, the Additional FAQ dated 16 March 2026 is explicit: overtime allowance forms part of the calculation, and employer PF and pension contributions and statutory bonus are included, while gratuity, ESI and other retirement benefits are not (para 24.3). As the book puts it, “A payroll code without legal classification is a compliance risk.”
Allowance-heavy structures build the error into the salary (para 28.5). In the book’s example, basic pay is Rs. 20,000 of a monthly salary of Rs. 80,000, with HRA of Rs. 25,000, conveyance of Rs. 5,000 and a special allowance of Rs. 30,000. Such a structure may appear efficient for reducing PF, gratuity or leave encashment exposure, but excessive excluded components may trigger add-back. The seven-step test should be run at joining, salary revision, restructuring, new allowance creation and software migration:
| Step | Control |
|---|---|
| 1 | Identify total remuneration |
| 2 | Identify included wage components |
| 3 | Identify excluded components |
| 4 | Check whether excluded components exceed 50% |
| 5 | Add back excess, where applicable |
| 6 | Recompute PF, gratuity, bonus, leave encashment and overtime impact |
| 7 | Update salary annexure and payroll master |
The book treats fixed monthly amounts paid without bills as allowances, even when they are labelled reimbursements (para 28.29). Appointment letters that mention only designation and CTC should be updated to match payroll configuration (para 28.25); Taxmann AI, a legal research and drafting assistant that answers questions against the law, can help draft the revised clauses.
3. Can CTC be compared with minimum wage?
No. Minimum wage comparison should be done against the actual wage payable and legally relevant components, not total CTC (para 28.8). The book’s example sets a monthly CTC of Rs. 24,000 against a minimum wage of Rs. 21,000, which is the book’s assumption for the illustration; the notified rate for the actual employment must be checked.
| Particular | Amount |
|---|---|
| Basic pay | Rs. 10,000 |
| HRA | Rs. 4,000 |
| Special allowance | Rs. 3,000 |
| Employer PF | Rs. 1,200 |
| Gratuity provision | Rs. 481 |
| Insurance | Rs. 319 |
| Variable incentive estimate | Rs. 5,000 |
| Monthly CTC | Rs. 24,000 |
| Actual fixed monthly salary payable | Rs. 17,000 |
| Minimum wage (the book’s assumption) | Rs. 21,000 |
On these figures the employer cannot simply say that CTC is Rs. 24,000 and therefore compliant, because the actual monthly wage payable may be only Rs. 17,000 (para 28.3). The Additional FAQ clarifies that minimum wages and wages are different: minimum wages are statutory rates fixed by the appropriate Government, and wages are determined by the terms of employment and section 2(y) of the Code.
Applying one minimum wage across India is incorrect, the book says, because minimum wages differ by appropriate Government, State, geographical area, zone, nature of employment, industry, scheduled employment, skill category and effective date (para 28.6). A generic “staff” mapping fails for the same reason: a helper, a cashier and a CNC operator may not fall in the same skill category, and designation alone is not enough (para 28.7).
4. What goes wrong in full and final settlement?
The book’s three F&F mistakes all concern the timing of wages payable on exit (paras 28.9 to 28.11). Section 17 requires wages payable on resignation, removal, dismissal, retrenchment or closure-related unemployment to be paid within two working days (para 28.9).
The first is processing F&F in the next payroll cycle, as where an employee relieved on 10 June is paid the F&F on 7 July; the book’s answer is an off-cycle F&F workflow. The second is counting from the resignation letter, acceptance, approval or payroll clearance date, when the safer approach is to count from the effective cessation date or relevant separation event and to define that trigger date in the F&F policy. The third is holding the entire settlement because a laptop, ID card or other asset has not been returned. Earned wages should be paid within the statutory timeline, not held indefinitely; asset loss should be recovered only through a lawful process, and damage recovery requires a record, valuation and an opportunity for the employee. The exit process is set out in full and final settlement under the Code on Wages.
5. What goes wrong with deductions from wages?
Deductions without documents, recoveries above the cap and loss of pay shown as a deduction. Section 18 of the Code permits only deductions authorised under the Code, and section 18(3) limits total deductions in any wage period to 50 per cent of wages (paras 26.2 and 9.6).
Payroll sometimes deducts on oral instructions, manager emails or owner directions (para 28.12). Every deduction should have the eight supports listed for mistake 10 above, and an amount may be commercially recoverable without being fully deductible from wages in one wage period. The cap applies to the total (para 28.13):
| Particular | Amount |
|---|---|
| Earned wages | Rs. 40,000 |
| PF and TDS | Rs. 4,000 |
| Loan recovery proposed | Rs. 25,000 |
| Total proposed deductions | Rs. 29,000 |
| 50% cap | Rs. 20,000 |
| Loan recovery allowed | Rs. 16,000 |
| Total deductions | Rs. 20,000 |
| Loan recovery carried forward | Rs. 9,000 |
For Central sphere establishments, rule 13 of the Wages (Central) Rules, 2026 requires the excess to be carried forward and recovered in instalments from succeeding wage periods, so that recovery in any month does not exceed 50 per cent of wages (paras 9.6 and 28.13).
Loss of pay needs clean presentation (para 28.14). Showing full monthly salary and then a large LOP deduction for 20 days of absence creates confusion about whether the cap has been breached. The book’s better approach, on a monthly wage of Rs. 30,000, shows 10 paid days and earned wages of Rs. 10,000, and tests other deductions against those earned wages.
Deposits are the last gap. “A deduction is incomplete unless the statutory amount is deposited where required,” so payroll should be reconciled monthly with the ECR, challans and payment proof (para 28.30). The rules for each recovery are in deductions from wages and the 50% limit.
6. Why are overtime and statutory bonus missed?
Often because overtime is paid informally or not captured, and statutory bonus is confused with incentives and gifts or assumed not to apply (paras 28.15 to 28.18).
The overtime errors include cash overtime outside payroll, overtime merged with incentive, unrecorded weekend work and blanket clauses stating that no overtime is payable. Section 14 requires overtime payment where an employee whose minimum rate of wages has been fixed works beyond the normal working day, and the Additional FAQ clarifies that such an employee, including a worker, is eligible for overtime. It should be paid through payroll, not in cash outside it.
Bonus fails in three ways. The first is treating an annual incentive as a substitute: the Additional FAQ clarifies that annual performance-based incentives do not form part of wages for computation under the Labour Codes, but the book notes that this does not remove the employer’s obligation to compute statutory bonus for eligible employees. The second is omission, because HR believes bonus is only for workers, or not due where the appointment letter is silent, the employee resigned before the payout date, an incentive was paid or the employer is loss-making. Section 26 provides eligibility based on wages not exceeding the notified amount and at least thirty days of work in the accounting year, subject to the provisions of the Code, so the annual eligibility review should include resigned and fixed-term employees, and bonus should be computed employee-wise. The third is treating gift vouchers, coupons or festival hampers as statutory bonus.
7. Which employees and records get left out?
White-collar, remote, fixed-term, temporary and trainee staff, and the records that prove payment.
Some HR teams assume that compliance with the Code applies only to workmen, factory workers or low-paid employees, but the Additional FAQ clarifies that timely payment provisions apply to all employees, including white-collar employees (para 28.19). Treating fixed-term, temporary, trainee or piece-rate staff as outside normal payroll compliance is also risky: fixed-term employees are direct employees, temporary status does not remove minimum wage protection, trainees may become employees depending on actual work, and piece-rate workers may require minimum time-rate protection (para 28.34). Remote work, the book adds, should not become record-free employment (para 28.35).
Section 50 requires wage slips in the prescribed form and manner, and for Central sphere establishments they must be issued electronically or physically on or before payment of wages (para 28.20). They should go to all employees, not only to factory workers or junior staff. Attendance, often kept only for factory workers, supports paid days, absence deduction, overtime, leave, bonus eligibility, F&F and wage claims defence, so the book suggests a record for each employee type (para 28.21):
| Employee type | Suggested record |
|---|---|
| Factory worker | Biometric or muster |
| Remote employee | HRMS or approved timesheet |
| Sales employee | CRM activity, attendance declaration or manager approval |
| Support employee | Login and shift record |
| Field employee | Route plan, work report or manager certification |
| Contract worker | Vendor attendance plus site validation |
| Consultant | Deliverable acceptance, not employee attendance |
In a wage claim, payroll processing is not enough and the employer should prove actual payment, so the bank proof listed for mistake 20 above should be preserved (para 28.22). For Central sphere establishments, the Central Rules require the employee register, wage and deduction-related registers and the attendance register-cum-muster roll, preserved for the prescribed period (para 28.23). Because claims may relate to earlier wage periods, the old system should not be switched off in a payroll migration until the archives are verified (para 28.24).
8. Where do contractor wage controls fail?
At invoice approval and at onboarding. Principal employers often verify contractor invoices but not worker wages, and the file may hold the invoice, GST details and an attendance summary without the worker-wise wage register, bank payment proof, minimum wage comparison or PF and ESI proof (para 28.31).
Under the Occupational Safety, Health and Working Conditions Code, 2020 (the OSHWC Code), the contractor is responsible for wage payment, but if the contractor fails to pay or short-pays, the principal employer may become liable to pay the full wages or unpaid balance and recover it from the contractor. Hence the book’s rule: do not clear contractor invoices without wage proof.
The OSHWC Code also restricts contract labour in core activities, subject to specified exceptions, and the concept of core activity requires examination of the activity for which the establishment is set up (para 28.32). The book classifies the activity before deployment:
| Classification | Review required |
|---|---|
| Core | Avoid or legally review |
| Non-core | Document support nature |
| Intermittent | Record temporary requirement |
| Temporary volume increase | Document sudden demand |
| Specialist outsourced service | Record expertise and service output |
| Manpower supply | Apply contractor controls |
A contractor engaged on a commercial quote alone may not have had its licence, worker count or statutory registrations checked, and none should be onboarded without compliance due diligence (para 28.33). The principal employer’s side is covered in principal employer and contractor wage compliance.
9. What is a payroll exception report?
It is the report of exceptions that HR and payroll review every month before payroll is closed, and not having one is the book’s mistake 34 (para 28.36). Closing payroll after salary computation and payment file generation is not enough. The exceptions, their targets and their owners:
| Exception | Target (para 28.36) | Owner (para 28.41) |
|---|---|---|
| Employees below minimum wage | Nil | HR |
| Employees without skill category | Nil | Not specified |
| Salary structures failing 50% wage test | Reviewed | Payroll |
| Deductions above 50% | Nil | Payroll |
| Overtime approved but unpaid | Nil | HR and department |
| Wage slips not issued | Nil | Payroll |
| Failed bank payments | Nil | Finance |
| F&F beyond two working days | Nil | HR and finance |
| Bonus eligibility not reviewed | Nil | Payroll |
| Contractor wage proof missing | Nil | Admin or procurement |
| Records not generated | Not specified | Compliance |
The targets are from para 28.36 and the owners from the book’s model payroll exception report in para 28.41, which also has columns for count, amount involved, target date and status. The report should be reviewed and signed off before payroll closure.
Under the Code, the book says, payroll software should function as a compliance validation system, not a salary calculator, with controls mapped to sections 2(y), 14, 17, 18 and 50 (para 28.26). If one payroll user can create an employee, change salary and bank details, upload deductions and process payment, the organisation has a serious control weakness. The book treats maker-checker as a compliance control, not only a fraud control (para 28.27).
10. How should payroll mistakes be corrected?
Through the book’s ten-step corrective action roadmap, which may be implemented in phases with the high-risk areas corrected first, and then a monthly control checklist used before every payroll closure (paras 28.38 and 28.39). For management, the book first condenses the common payroll mistakes into a matrix that may be used as a management review summary (para 28.37):
| Mistake | Risk | Corrective control |
|---|---|---|
| CTC treated as wages | Minimum wage and bonus errors | Separate CTC, gross pay and statutory wages |
| Low basic and high allowances | 50% wage rule exposure | Component mapping and add-back test |
| No skill mapping | Minimum wage shortfall | Role-wise skill matrix |
| F&F delay | Wage claim risk | Off-cycle F&F process |
| Unsupported deductions | Illegal deduction claim | Approval and documentation |
| Overtime unpaid | Wage claim | Attendance and overtime register |
| Bonus omitted | Bonus claim | Annual eligibility report |
| Contractor wage gaps | Principal employer exposure | Invoice hold until wage proof |
| No wage slips | Record violation | Automated wage slips |
| No bank proof | Payment dispute | Transaction ID archive |
| No registers | Inspection risk | Electronic statutory registers |
| No audit logs | Weak control | Maker-checker workflow |
The roadmap may be used by an employer that wants to correct its implementation of the Code (para 28.38):
| Step | Action |
|---|---|
| Step 1 | Conduct a payroll diagnostic covering salary structures, wage codes, deductions, wage slips, contractor files and F&F cases |
| Step 2 | Classify all earnings, allowances, reimbursements, employer contributions, benefits and deductions |
| Step 3 | Check all employees and contractor workers for minimum wage compliance by State, location and skill category |
| Step 4 | Run the 50% wage rule test for all salary structures |
| Step 5 | Configure the deduction cap, approval workflow and carry-forward logic |
| Step 6 | Link attendance, overtime approval and payroll |
| Step 7 | Prepare a bonus eligibility report including resigned employees |
| Step 8 | Link contractor invoice approval with wage proof and statutory proof |
| Step 9 | Create a two-working-day F&F wage settlement workflow |
| Step 10 | Generate the wage register, attendance register, overtime register, deduction register, wage slips, payment proof and audit logs |
Steps 2 and 3 turn on the text of section 2(y) and the applicable minimum wage notifications, and for that research Taxmann.com | Premium brings Research, Practice and Learning under one search. The monthly checklist should be used before payroll closure, not after salary is paid (para 28.39):
| Area | Monthly control |
|---|---|
| Minimum wages | Check State, location and skill category |
| Wage structure | Run 50% wage rule exception |
| Attendance | Freeze before payroll |
| Overtime | Approve and pay through payroll |
| Deductions | Check authorisation and 50% cap |
| Wage slips | Issue on or before payment |
| Bank proof | Preserve transaction ID |
| F&F | Track exits and pay wages within two working days |
| Bonus | Update eligibility and accrual |
| Contractors | Verify wage and statutory proof |
| Records | Generate and preserve registers |
| Audit logs | Review high-risk changes |
The book adds seventeen internal audit questions and a fifteen-point self-assessment scorecard; if more than three scorecard items are marked “No”, the employer should conduct a payroll compliance review (paras 28.40 and 28.42).
Line managers are part of the fix (para 28.28). HR may know the law, but supervisors and line managers often create the risk, for example by asking employees to work late without overtime approval, and a good payroll process can fail if managers are not trained. For that training, Taxmann.com | Learning runs webinars, workshops and masterclasses, live or recorded, with Labour Laws among its subject areas, and sessions can be arranged for an organisation.
The chapter ends with a test for the team itself (para 28.43): a good HR and payroll team can prove how salary was computed, why deductions were made and whether minimum wages were met, overtime paid, bonus reviewed, F&F timely and records inspection-ready.
11. Quick answers
What is the most common payroll mistake under the Code on Wages?
Treating CTC as wages. Taxmann’s HR Guide to Code on Wages says HR may compare CTC with the minimum wage, bonus ceiling, PF base or statutory wage definition under the Code on Wages, 2019, which is not correct. Payroll should keep CTC, gross salary payable, statutory wages and the other wage bases as separate values.
Can CTC be compared with minimum wage?
No. The minimum wage comparison under the Code on Wages, 2019 should be done against the actual wage payable and legally relevant components, not total CTC. An employer may still have a shortfall where employer PF, gratuity provision, insurance and variable incentive are included in CTC but are not wages payable for the wage period.
Should wage slips be issued to every employee?
Yes. Section 50 of the Code on Wages, 2019 requires wage slips in the prescribed form and manner, and for Central sphere establishments they must be issued electronically or physically on or before payment of wages. They should go to all employees, including senior, remote, white-collar, fixed-term, daily-rated and part-time employees.
What is a payroll exception report?
It is a monthly report of payroll exceptions that HR and payroll review before payroll is closed, such as employees below minimum wage, deductions above 50 per cent of wages, approved overtime left unpaid, wage slips not issued, failed bank payments, full and final settlement beyond two working days and missing contractor wage proof. Taxmann’s HR Guide to Code on Wages sets the target for most items at nil and says the report should be reviewed and signed off before closure.
How should payroll mistakes under the Code on Wages be corrected?
Taxmann’s HR Guide to Code on Wages sets out a ten-step corrective action roadmap, from a payroll diagnostic to generating registers, wage slips, payment proof and audit logs. It may be implemented in phases, with the high-risk areas corrected first, followed by a monthly control checklist used before each payroll closure.
Can a full loan be recovered from one month’s wages?
Not if total deductions for the wage period would exceed 50 per cent of wages, the cap in section 18 of the Code on Wages, 2019. For Central sphere establishments, rule 13 of the Wages (Central) Rules, 2026 requires the excess to be carried forward and recovered in instalments from succeeding wage periods.
Do the timely payment provisions apply to white-collar employees?
Yes. The Additional FAQ dated 16 March 2026 clarifies that timely payment provisions under the Code on Wages, 2019 apply to all employees, including white-collar employees. The practical impact may differ by category, but employees should not be excluded without review.
This article draws on Chapter 28 of Taxmann’s HR Guide to Code on Wages by CA Venugopal Gella (2026 Edition), which sets out thirty-four common mistakes by HR and payroll teams with the control for each, a common mistake matrix, a ten-step corrective action roadmap, a monthly HR and payroll control checklist, seventeen internal audit questions, a model payroll exception report and a fifteen-point self-assessment scorecard, and on related paragraphs of Chapters 9, 18, 24 and 26. Law stated as updated till August 2026.
Labour law Acts and Rules, case laws, circulars and notifications are available on Taxmann.com | Research under Labour Laws.
Related reading: the complete guide to the Code on Wages, 2019 · definition of wages and the 50% rule · floor wage under section 9.
More in this series: full and final settlement under the Code on Wages · wage slip format under the Code on Wages · statutory bonus calculation · new labour code salary structure · deductions from wages and the 50% limit · payment of wages: wage period and time limits · overtime rules under the Code on Wages · minimum wages as per the new labour code · principal employer and contractor wage compliance · monthly payroll compliance · labour code implementation roadmap · appointment letter format.
Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.
The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:
- The statutory material is obtained only from the authorized and reliable sources
- All the latest developments in the judicial and legislative fields are covered
- Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
- Every content published by Taxmann is complete, accurate and lucid
- All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
- The golden rules of grammar, style and consistency are thoroughly followed
- Font and size that’s easy to read and remain consistent across all imprint and digital publications are applied


CA | CS | CMA