[Analysis] Monthly Payroll Compliance under the Code on Wages 2019 – Payroll Calendar | Pre-Closure Reconciliations | Master Compliance Checklist
- Blog|Labour & Industrial Laws|
- 15 Min Read
Monthly payroll under the Code on Wages 2019 should close only after compliance checks. The payroll calendar, reconciliations, exception report and scorecard.
- By Taxmann
- |
- Last Updated on 16 November, 2026

Table of Contents
- What does payroll compliance involve under the Code on Wages?
- How should the monthly payroll cycle be organised?
- What does a monthly payroll calendar look like?
- What should be checked in the employee master and minimum wages?
- How should attendance, overtime and deductions be validated?
- Which reconciliations should be completed before payroll is closed?
- What goes into the payroll exception report?
- Which registers, records and wage slips must be kept?
- What goes into the monthly payroll compliance file and dashboard?
- How does the master compliance checklist rate and score payroll compliance?
- Quick answers
1. What does payroll compliance involve under the Code on Wages?
Meeting the obligations that arise in every wage period, and being able to show each month that they were met. Payroll is often treated as routine salary processing, but according to Taxmann’s HR Guide to Code on Wages it should be treated under the Code on Wages, 2019 as a statutory compliance process (para 16.1).
The obligations that the Code creates for every wage period include payment of at least minimum wages under section 5, wage period fixation under section 16, timely payment under section 17, overtime payment under section 14, authorised deductions under section 18, and records and wage slips under section 50 (para 16.2). The Additional FAQ dated 16 March 2026 clarifies that wage protection for timely payment applies to all employees, including white-collar employees, and that minimum wages, fixed by the appropriate Government, are not the same as wages, which are determined with reference to the terms of employment and section 2(y).
Payroll therefore “should not be closed only because the net salary file is ready” (para 16.2). The book’s standard is no closure without a minimum wage check, attendance validation, overtime review, deduction review, wage slip generation, bank payment proof and exception reporting. References to the Wages (Central) Rules, 2026 apply to Central sphere establishments; State sphere establishments should check the relevant State Rules, minimum wage notifications, local forms and Shops and Establishments requirements (para 16.1).
2. How should the monthly payroll cycle be organised?
In stages, each with an owner, a checker and an approval record. Chapter 16 sets out five (para 16.3):
| Stage | Purpose | Typical owner |
|---|---|---|
| Pre-payroll input | Capture new joinees, exits, attendance, leave, overtime, salary changes and deductions | HR and payroll |
| Compliance validation | Check minimum wages, wage structure, overtime, deductions and payment timelines | Payroll and compliance |
| Payroll processing | Compute gross wages, deductions, net wages, employer cost and statutory liabilities | Payroll |
| Payment and documentation | Upload the bank file, issue wage slips, update registers and preserve payment proof | Payroll and finance |
| Post-payroll review | Review exceptions, failed payments, final settlements and contractor wage records | HR, finance and compliance |
The cycle should be followed every month. Payroll software, however advanced, “is only a tool”, and the compliance responsibility remains with the employer.
A maker-checker structure fixes who prepares, checks and approves each activity, since a payroll process without maker-checker control is vulnerable to error and misuse (para 16.22):
| Payroll activity | Maker | Checker | Approver |
|---|---|---|---|
| Attendance upload | HR executive | HR manager | HR head |
| Payroll input | Payroll executive | Payroll manager | Finance |
| Deduction upload | Payroll | HR and finance | Authorised person |
| Overtime upload | Department head | HR | Payroll head |
| Payroll processing | Payroll | Finance | Management or authorised signatory |
| Bank file | Finance executive | Finance manager | Bank approver |
| Wage slips | Payroll | HR | Payroll head |
| Contractor wage records | Admin or procurement | HR or compliance | Finance, before invoice release |
Smaller establishments may combine these roles, but approval evidence should still exist.
3. What does a monthly payroll calendar look like?
It should be designed around the statutory wage payment timeline, with inputs frozen and compliance checks run before payroll is processed (para 16.4). Section 17 of the Code requires monthly wages to be paid before the expiry of the seventh day of the succeeding month. Daily, weekly and fortnightly wage periods have shorter timelines, and wages payable on resignation, removal, dismissal, retrenchment or closure must be paid within two working days. The book’s sample calendar for a monthly wage period (para 16.4):
| Date range | Activity |
|---|---|
| 20th to 24th | Collect payroll inputs, new joinee data, exit data and salary revisions |
| 24th to 26th | Freeze attendance, leave and unpaid days |
| 26th to 27th | Approve overtime and deduction inputs |
| 27th to 28th | Run minimum wage and deduction cap checks |
| 28th to 30th | Process payroll and review exceptions |
| 30th to 5th | Complete payroll approval, bank upload and salary credit |
| On or before payment | Issue wage slips |
| Immediately after payment | Review bank failures and preserve payment proof |
| 7th to 10th | Close contractor wage verification and the payroll compliance file |
This is only an internal calendar. The legal timeline under section 17 should always prevail, and delays in attendance approval, manager sign-off or finance approval should not result in delayed wage payment.
Every employer should also define an attendance cut-off and communicate it to employees, managers and payroll teams (para 16.9). The cut-off should not be used to deny genuine wages: a valid input that is missed should be corrected in the current payroll where possible, or in the next one with clear documentation.
4. What should be checked in the employee master and minimum wages?
The employee master first, because if it is wrong the payroll output will be wrong, and then each employee’s wage against the minimum rate for the actual place of work and category (paras 16.5 and 16.6).
Before payroll is processed, HR should verify new joinees, exits, transfers, role changes, salary revisions, bank details, location, skill category and employment type. The master should also support minimum wage mapping and statutory register preparation. The review is a monthly control, not a year-end task.
Section 5 prohibits an employer from paying less than the minimum rate of wages notified by the appropriate Government, and rates may vary with category of work, skill level, geographical area and other notified factors. For Central sphere establishments, where a daily rate is fixed, rule 3 of the Central Rules arrives at the hourly rate by dividing it by eight and the monthly rate by multiplying it by twenty-six. The check should run every month for direct employees, contract workers, and temporary, fixed-term, daily wage, piece-rate and part-time employees, for employees transferred during the month and for those promoted or moved to a different role.
In the book’s illustration, the wage considered for a semi-skilled employee in Karnataka is Rs. 17,900 against an applicable minimum of Rs. 18,500, a shortfall of Rs. 600 that must be corrected before payroll. The rates are the book’s illustration, and the notified rate for the employee’s State and category must be checked. A common mistake is applying the head office State’s minimum wage to employees working in other States. The check cannot be done without a live notification tracker kept State-wise and category-wise, and where rates are revised retrospectively, arrears must be identified and paid without waiting for claims (para 16.7).
5. How should attendance, overtime and deductions be validated?
Against source records and approvals, before payroll is finalised, with the deduction cap controlled by the system (paras 16.8 to 16.14).
Attendance determines paid days, unpaid days, overtime, leave encashment, absence deductions and final settlement, so it should be validated and frozen before payroll, with changes after payroll closure routed through a supplementary payroll or an adjustment process with approval (para 16.8).
Section 14 requires overtime at not less than twice the normal rate of wages for every extra hour or part of an hour beyond a normal working day, where the employee’s minimum rate of wages has been fixed under the Code (para 16.10). Overtime should not be paid informally outside payroll, or ignored merely because the employee receives a monthly salary. Late logout should not automatically become payable overtime, but instructed and approved extra work should not be ignored.
Section 18 permits deductions only as authorised under the Code, and total deductions in a wage period should not exceed fifty per cent of wages (para 16.12). Payroll should not accept vague inputs such as “miscellaneous recovery” without supporting documents, and the cap should be system controlled. A deduction cap report may look like this (para 16.13):
| Employee | Wages | Total deductions | 50% limit | Excess | Payroll action |
|---|---|---|---|---|---|
| A | Rs. 40,000 | Rs. 12,000 | Rs. 20,000 | Nil | Process |
| B | Rs. 40,000 | Rs. 23,000 | Rs. 20,000 | Rs. 3,000 | Defer excess |
| C | Rs. 25,000 | Rs. 8,000 | Rs. 12,500 | Nil | Process |
The excess should be deferred unless the law specifically permits otherwise. Fines under section 19 and deductions for damage or loss under section 21 each require an opportunity to show cause, and a manager’s email is not a basis for recovering the full cost of a damaged laptop (para 16.14).
Statutory deductions such as PF, ESI, professional tax and TDS need a check of the calculation, and for the TDS figure Taxmann’s Tools include an Income Tax Calculator under the Income-tax Act, 2025. The wider rules are covered in deductions from wages and the 50% limit.
6. Which reconciliations should be completed before payroll is closed?
Eight, with the reconciliation signed off by both payroll and finance, and HR confirming the data wherever its inputs affect salary (para 16.21):
| Reconciliation | Purpose |
|---|---|
| Payroll register vs. bank file | Ensures all processed salaries are paid |
| Bank file vs. bank debit | Confirms actual payment |
| Gross wages vs. accounting entry | Ensures correct booking |
| Deductions vs. statutory challans | Ensures statutory deposit |
| Attendance vs. paid days | Avoids excess or short payment |
| Overtime vs. approval | Avoids unpaid overtime |
| Contractor invoice vs. wage records | Avoids contractor wage risk |
| Final settlement register vs. payroll | Avoids delayed exit payment |
The first two rows reflect the book’s point that payroll compliance is complete only when wages are actually paid, so the payroll file, bank upload file and employee-wise credit report should reconcile (para 16.16). A failed transfer should be reprocessed immediately, with proof of both the failed and the successful transaction preserved. A salary file prepared on time but rejected by the bank is not complete compliance (para 16.11).
Once the TDS deducted in payroll has been matched with the statutory challans, Taxmann’s e-TDS Returns can be used to prepare the TDS statements and certificates under the Income-tax Act, 2025, with TRACES integration.
Two further monthly checks sit alongside these reconciliations. Even where bonus is paid annually, payroll and finance should track eligibility monthly to identify new joinees, employees crossing wage thresholds, resigned employees, deemed working days and interim bonus payments, and finance should reconcile bonus accrual with payroll data (para 16.17). Section 26 provides annual minimum bonus for an eligible employee drawing wages up to the notified amount who has worked at least thirty days in the accounting year, subject to the provisions of the Code. In the book’s tracker, one employee’s eligibility reads “check notified ceiling”: the notified amount must be checked before eligibility is decided.
Contractor wages should be verified worker-wise before invoice approval (para 16.19). The contractor should submit the worker list, attendance, skill category, minimum wage mapping, wage register, deductions, overtime record, bank payment proof, wage slips and statutory contribution records wherever applicable, and the invoice should be held if records are incomplete. State sphere establishments should also check contractor payment rules under the State OSHWC Rules.
7. What goes into the payroll exception report?
Each exception found before salary payment, with its owner, the action taken and closure status (para 16.23). Payroll should generate the report every month before salaries are paid, and HR and finance should review it:
| Exception | Required action |
|---|---|
| Employee below minimum wage | Correct before payroll or pay arrears |
| Old minimum wage notification used | Update rates and recompute |
| Attendance not approved | Escalate to reporting manager |
| Overtime approved but unpaid | Process before payroll closure |
| Deduction above 50% | Defer excess |
| Damage recovery without show cause | Hold deduction |
| Wage slip not generated | Generate before payment |
| Failed bank transaction | Reprocess immediately |
| Exit wages pending | Process within statutory timeline |
| Contractor wage proof missing | Hold invoice |
| Bonus eligibility not updated | Update accrual |
The report should not be a formality. In the book’s worked example, ABC Manufacturing Pvt. Ltd. processes April payroll for 500 employees and 200 contractor workers and finds these issues before salary payment (para 16.26):
| Issue identified | Correct action |
|---|---|
| 8 employees below the revised minimum wage after a notification update | Revise wages and pay arrears |
| 12 employees with overtime approved but not uploaded | Upload approved overtime before payroll closure |
| 3 employees with loan recovery exceeding the deduction limit | Restrict recovery and defer the excess |
| 2 bank account errors | Correct bank details before payment |
| 1 contractor has not submitted wage payment proof | Hold the contractor invoice until proof is submitted |
The principal employer should also keep a monthly contractor exception report by vendor (para 16.20). In the book’s example, a housekeeping vendor with partial wage proof and a Rs. 12,000 minimum wage shortfall has its invoice on hold. The book’s view is that most of the common payroll mistakes it lists can be avoided if payroll is run with a fixed calendar, a maker-checker process and an exception report (para 16.27).
8. Which registers, records and wage slips must be kept?
Those required under section 50, updated every month as part of payroll closure rather than prepared when an inspection notice arrives (para 16.18). Section 50 requires registers of persons employed, muster roll, wages and other prescribed details, display of prescribed notices and issue of wage slips.
For Central sphere establishments, rule 51 of the Central Rules requires the Employee Register in Form I, the Register of Wages, Overtime, Advances, Fines and Deductions for Damage and Loss in Form IV, and the Attendance Register-cum-Muster Roll in Form IX. They may be kept electronically or physically and must be preserved for five years after the date of the last entry. Rule 52 requires wage slips in Form V, issued electronically or physically on or before payment of wages (para 16.15). Monthly register controls should include:
| Register or record | Monthly action |
|---|---|
| Employee register | Update joinees, exits, transfers and salary changes |
| Attendance register-cum-muster roll | Freeze after validation |
| Wage register | Update payroll values |
| Overtime records | Capture approved and paid overtime |
| Fine and deduction records | Record authorised deductions |
| Damage or loss records | Record show cause and recovery details |
| Wage slip archive | Store employee-wise wage slips |
| Bank proof | Preserve transaction reports |
A wage slip should show how wages were calculated, not merely net salary: overtime separately, deductions item-wise, gross wages reconciled with payroll and net wages matching the bank payment (para 16.15). If slips are emailed, proof of generation and delivery should be preserved. The layout is covered in wage slip format under the Code on Wages.
9. What goes into the monthly payroll compliance file and dashboard?
The file holds the evidence for each step of the month’s payroll, and the dashboard reports the exceptions to management (paras 16.24 and 16.25). HR and payroll should preserve the file every month, and it may be electronic, provided it is secure, searchable and accessible during audit or inspection:
| File item | Purpose |
|---|---|
| Payroll input sheet | Shows source data |
| Attendance freeze report | Supports paid days |
| Leave report | Supports paid and unpaid leave |
| Overtime approval report | Supports overtime payment |
| Minimum wage exception report | Supports statutory wage check |
| Deduction approval sheet | Supports authorised recoveries |
| Deduction cap report | Supports 50% limit control |
| Payroll register | Supports wage computation |
| Wage slip archive | Supports employee communication |
| Bank upload file | Supports payment instruction |
| Bank debit and credit confirmation | Supports actual payment |
| Failed transaction report | Supports payment follow-up |
| Statutory deduction summary | Supports remittance |
| Bonus accrual report | Supports finance provision |
| Final settlement report | Supports exit wage timeline |
| Contractor wage verification file | Supports vendor compliance |
| Payroll approval note | Supports maker-checker approval |
| Exception closure report | Supports management review |
The book calls this file the employer’s defence during inspection, employee claim, internal audit or due diligence. Its model monthly certification, which may be signed by payroll, HR and finance, confirms that the month’s payroll was processed after verifying the employee master changes, attendance, leave, overtime, minimum wage compliance, authorised and statutory deductions, wage slips, bank payment file, bonus accrual and contractor wage records, and that any exceptions were recorded in the exception report and escalated for corrective action (para 16.29). The certification should be supported by working papers, because a certification without records “has limited value”. For management, the book recommends a concise monthly dashboard focused on exceptions and statutory risk (para 16.25):
| Metric | Target |
|---|---|
| Salary paid within statutory due date | 100% |
| Employees below minimum wage | Nil |
| Wage slips issued on or before payment date | 100% |
| Bank payment failures unresolved beyond two working days | Nil |
| Deductions above statutory limit without review | Nil |
| Overtime approved but unpaid | Nil |
| Final settlement pending beyond statutory timeline | Nil |
| Contractor wage proof pending | Nil or explained |
| Bonus accrual report prepared | Yes |
| Payroll records updated | Yes |
Chapter 16 also gives a sixteen-area implementation checklist that works as a monthly payroll checklist, to be run as part of payroll closing rather than as a year-end exercise (para 16.31).
10. How does the master compliance checklist rate and score payroll compliance?
It asks management to confirm each control against evidence, rate the risk Red, Amber or Green, and track a weighted score over time (paras 29.5 to 29.9). Chapter 29 converts the earlier chapters into a management-level payroll compliance checklist. It is a control summary, not a substitute for detailed payroll workings (para 29.1).
Management should ask not only “Was salary paid?” but “Was salary paid after compliance validation?” (para 29.2). The master management checklist puts twenty-five questions, from applicability to claim readiness and management review, each with a Yes, No or NA status, the evidence to be reviewed and an owner (para 29.6).
An item should be marked “Yes” only when evidence is available, such as a minimum wage exception report or a deduction cap report, because “No evidence means the control is not complete” (para 29.5). Some of that evidence is legal rather than payroll data, such as the legal note identifying the appropriate Government for each establishment. For that research, Taxmann.com | Premium brings Research, Practice and Learning under one search.
Management should not rely only on “Yes” and “No”, because a risk rating is more useful (para 29.7):
| Rating | Meaning | Action |
|---|---|---|
| Green | Fully compliant and evidence available | Continue monitoring |
| Amber | Process exists, but evidence or consistency is weak | Correct within 30 days |
| Red | Non-compliance or high exposure identified | Immediate corrective action |
| NA | Not applicable | Document reason |
A checklist with many “Yes” responses but weak evidence should not be treated as Green. For monthly payroll closure, the checklist is used with a monthly management dashboard and a records and wage slips checklist (para 29.4). Each of the dashboard’s fourteen metrics carries a target, the current month’s figure, a Green, Amber or Red status and an owner, and the dashboard should show numbers: “3 F&F cases delayed” rather than “F&F under review” (para 29.8).
The rating model and a suggested scorecard are listed among the tools for the quarterly management review (paras 29.4 and 29.9):
| Area | Weight |
|---|---|
| Employee and establishment master | 10 |
| Minimum wage compliance | 15 |
| Wage definition and 50% rule | 15 |
| Wage payment and F&F timeline | 10 |
| Overtime and attendance | 10 |
| Deduction controls | 10 |
| Bonus compliance | 10 |
| Contractor compliance | 10 |
| Records and wage slips | 5 |
| Payroll system and audit logs | 5 |
| Total | 100 |
Suggested interpretation of the total:
| Score | Meaning |
|---|---|
| 85 and above | Controlled compliance position |
| 70 to 84 | Moderate risk, action plan required |
| 50 to 69 | Significant gaps, management intervention required |
| Below 50 | High risk, immediate compliance project required |
The scorecard should not hide Red items. Even with a high total, a Red item such as a minimum wage shortfall, delayed full and final settlement, an illegal deduction or a contractor wage default should be escalated separately.
11. Quick answers
What does payroll compliance involve under the Code on Wages?
Meeting the obligations that arise in every wage period under the Code on Wages, 2019: at least minimum wages (section 5), a fixed wage period (section 16), timely payment (section 17), overtime (section 14), authorised deductions (section 18), and records and wage slips (section 50). Each month the employer should be able to show that these checks were done.
What should be checked before payroll is closed?
Taxmann’s HR Guide to Code on Wages sets the standard as no payroll closure without a minimum wage check, attendance validation, overtime review, deduction review, wage slip generation, bank payment proof and exception reporting. Reconciliations such as payroll register against bank file and deductions against statutory challans should also be signed off by payroll and finance.
What is the due date for monthly wages under the Code on Wages?
Section 17 of the Code on Wages, 2019 requires monthly wages to be paid before the expiry of the seventh day of the succeeding month. Wages payable on resignation, removal, dismissal, retrenchment or closure must be paid within two working days, and the legal timeline should always prevail over the internal payroll calendar.
Which payroll records must be kept under the Code on Wages?
For Central sphere establishments, rule 51 of the Wages (Central) Rules, 2026 requires the Employee Register in Form I, the register of wages, overtime, advances, fines and deductions for damage and loss in Form IV, and the attendance register-cum-muster roll in Form IX, kept electronically or physically for five years after the last entry. Rule 52 requires wage slips in Form V on or before payment of wages. State sphere establishments should check the applicable State Rules.
What goes into the monthly payroll compliance file?
The evidence for each step of the payroll: the input sheet, attendance freeze, leave and overtime approval reports, the minimum wage exception report, deduction approval sheet and deduction cap report, payroll register, wage slip archive, bank upload file, bank debit and credit confirmation, failed transaction report, statutory deduction summary, bonus accrual and final settlement reports, contractor wage verification file, payroll approval note and exception closure report. The file may be electronic if it is secure, searchable and accessible during audit or inspection.
What should a payroll exception report show?
Each exception, such as an employee below minimum wage, a deduction above 50 per cent, a wage slip not generated or a failed bank transaction, with the required action, the owner, the action taken and closure status. Payroll should generate it every month before salary payment, and HR and finance should review it.
How should payroll compliance be rated or scored?
Taxmann’s HR Guide to Code on Wages suggests a Red, Amber and Green rating: Green means fully compliant with evidence available, Amber means the process exists but evidence or consistency is weak and should be corrected within 30 days, and Red calls for immediate corrective action. Its suggested 100-point scorecard treats 85 and above as a controlled compliance position, but Red items should be escalated separately whatever the total.
This article draws on Chapters 16 and 29 of Taxmann’s HR Guide to Code on Wages by CA Venugopal Gella (2026 Edition), which set out the monthly payroll process with a five-stage control cycle, a payroll calendar, eight pre-closure reconciliations, an exception report, an eighteen-item compliance file and a model payroll certification, and a twenty-five-point master management checklist with a red, amber and green rating, a management dashboard and a suggested scorecard. 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 chapter-wise guide to the Central Rules · TDS on salary · the complete guide to the Code on Wages, 2019.
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 · 34 common payroll mistakes · labour code implementation roadmap.
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