Indian Payroll Compliance Checklist for Global CFOs

Indian Payroll Compliance Is a Finance Control, Not Just an HR Process

For a global CFO, Indian Payroll Compliance is not simply about paying employees correctly. It is a control framework covering wage calculations, tax withholding, social security contributions, state-specific registrations, payroll evidence, employee exits and accounting reconciliation.

The risk is rarely one large payroll mistake. More often, it is a series of smaller control failures:

• A location is added without checking state registrations.
• A salary component is configured incorrectly.
• An employee crosses a statutory threshold without a payroll update.
• Tax is deposited, but the return does not reconcile.
• An employee exits, but final wages or gratuity are delayed.
• An Employer of Record submits a compliance summary without underlying payment evidence.

India’s four labour codes became effective nationwide on 21 November 2025, while the Income-tax Act, 2025 and its revised salary reporting forms apply from 1 April 2026. CFOs should therefore review payroll configurations, compliance calendars and evidence requirements rather than relying on processes designed around the earlier framework.

The CFO’s Quick Answer

A reliable Indian payroll control environment should answer five questions every month:

1. Who is the legal employer?
2. Which central and state obligations apply?
3. Were salary, deductions and employer contributions calculated correctly?
4. Were payments and returns completed within the prescribed timelines?
5. Can every payroll number be supported with evidence?

A payroll report alone is not proof of compliance. CFOs should require a traceable chain from approved employee data to the payroll register, bank payment, statutory challan, return acknowledgement and general ledger.

Indian Payroll Compliance Checklist

1. Confirm the Legal Employer and Payroll Registrations

Before the first employee is paid, document the employing structure.

The legal employer may be:

• An Indian subsidiary or other registered Indian entity
• An Indian branch or project office, where legally permitted
• An Employer of Record Service Provider
• Another approved employing arrangement supported by local advice

The payroll team should maintain a registration matrix covering, as applicable:

• Tax Deduction and Collection Account Number
• Employees’ Provident Fund registration
• Employees’ State Insurance registration
• Professional tax
• Labour Welfare Fund
• Shops and Establishments registration
• State-specific employment and payroll registrations

Do not treat India as a single payroll jurisdiction. Central obligations may apply nationally, but minimum wages, professional tax, Labour Welfare Fund, leave rules and establishment requirements can vary by state and employee location.

CFO control

Maintain a legal-employer and registration register containing:

• Employing entity name
• Registered address
• Payroll locations
• Registration numbers
• Effective dates
• Filing owner
• Renewal date
• Supporting certificate
• Compliance status

A registration should not remain listed as “in progress” once employees are being paid.

2. Establish a Controlled Employee Master

The employee master drives almost every payroll calculation. Unapproved or incomplete employee data can create tax, social security and financial-reporting errors.

At onboarding, validate and retain:

• Full legal name
• Permanent Account Number
• Bank account details
• Work location and state
• Date of joining
• Employment category
• Salary structure
• Tax declarations and supporting information
• Provident Fund Universal Account Number, where applicable
• Employees’ State Insurance details, where applicable
• Approved benefits and deductions
• Employment agreement or appointment letter

Changes to salary, work location, bank account, tax status or employment category should follow maker-checker approval.

CFO control

Run a monthly employee-master change report. It should identify:

• New employees
• Departures
• Salary changes
• Bank-account changes
• Location changes
• One-time payments
• Manual overrides
• Employees added after the payroll cut-off

No employee record should be created, changed or deactivated without documented approval.

3. Review the Salary Structure Against the Statutory Wage Definition

Under the labour-code framework, “wages” generally include basic pay, dearness allowance and retaining allowance. Certain excluded components may need to be added back when total exclusions exceed 50% of remuneration.

This means that moving a large portion of compensation into allowances does not automatically remove it from the statutory wage base. Payroll teams should test the complete remuneration structure rather than assessing individual components in isolation.

CFO control

Ask payroll to produce a wage-definition test showing:

• Total remuneration
• Included wage components
• Excluded components
• Percentage represented by exclusions
• Amount added back, where required
• Revised statutory wage base

Review the test whenever compensation structures, allowance policies or incentive plans change.

Strategic implication

The 50% calculation can affect:

• Provident Fund assumptions
• Gratuity provisioning
• Bonus calculations
• Overtime calculations
• Leave-related payments
• Employee cost forecasts

CFOs should model the financial effect before approving a redesigned compensation structure.

4. Validate Minimum Wages, Wage Dates, Overtime and Deductions

Minimum wages are notified by the appropriate government and may depend on the state, scheduled employment, employee category, skill level and location.

Under the current labour-code framework:

• Monthly wages must generally be paid before the expiry of the seventh day of the succeeding month.
• Wages due when an employee leaves should generally be paid within two working days.
• Overtime must generally be paid at not less than twice the normal wage rate.
• Total deductions in a wage period should not exceed 50% of wages.
• A wage slip should be issued on or before the wage payment date.

CFO control

Before payroll approval, require confirmation that:

• No employee falls below the applicable minimum wage
• Payroll is scheduled within the legal wage-payment timeline
• Overtime hours have been approved and paid at the correct rate
• Deductions are legally permitted
• Aggregate deductions remain within the prescribed limit
• Wage slips reconcile to the payroll register

Where employees work in multiple states, the control should use the employee’s actual work location rather than only the company’s registered office.

5. Control Attendance, Leave and Variable Pay Inputs

Payroll errors often begin outside the payroll system.

Typical high-risk inputs include:

• Attendance
• Unpaid leave
• Overtime
• Shift payments
• Sales incentives
• Performance bonuses
• Joining bonuses
• Retention payments
• Expense reimbursements
• Recoveries
• Notice-period adjustments

Every input should have a documented source, approval and cut-off date.

CFO control

Use a payroll-input sign-off containing:

Manual changes after payroll lock should appear in an exception report reviewed by finance.

6. Manage Salary Tax Deduction and Reporting

Employers must deduct income tax from salary based on the employee’s estimated taxable salary, declarations, permitted evidence and applicable tax regime.

For non-government deductors under the rules effective from 1 April 2026:

• Tax deducted from April through February is generally payable within seven days after the end of the month.
• Tax deducted in March is generally payable by 30 April.

Salary tax reporting now uses:

• Form 138, replacing the earlier Form 24Q, for quarterly salary tax deduction reporting
• Form 130, replacing the earlier Form 16, for the annual salary tax certificate

Form 138 is generally due:

 

Form 130 must generally be provided by 15 June immediately following the relevant tax year. It should be generated from the filed salary return information and downloaded through the prescribed tax-reporting system.

CFO control

Reconcile these four values every month:

1. Tax calculated in payroll
2. Tax deducted from employees
3. Tax deposited with the government
4. Tax recorded in the general ledger

Quarterly returns should also reconcile to:

• Monthly payroll registers
• Tax challans
• Employee tax records
• General-ledger tax liability
• Annual employee certificates

A successful payment does not prove that the return contains the correct employee-level data.

7. Review Provident Fund Applicability and Contributions

The Employees’ Provident Fund framework generally applies to covered establishments employing 20 or more persons. Once an establishment becomes covered, coverage generally continues even if employee strength later falls below 20.

EPFO’s current public guidance states that:

• The employee contribution is generally 12% of basic wages, dearness allowance and retaining allowance.
• The employer also contributes 12%.
• Of the employer contribution, 8.33% is generally allocated to the pension scheme and 3.67% to the provident fund.
• The employer also bears the applicable Employees’ Deposit Linked Insurance contribution.

The ₹15,000 monthly wage threshold is relevant to mandatory entry into membership. It should not be treated as a general reason to discontinue contributions for an existing member whose salary later exceeds the threshold.

Provident Fund contributions are generally payable within 15 days after the close of the month.

CFO control

Obtain and reconcile:

• Provident Fund wage register
• Employee and employer contribution calculations
• Electronic Challan-cum-Return
• Payment challan and bank proof
• Universal Account Number mapping
• Joiner and leaver updates
• Payroll-to-Provident-Fund variance report

Pay particular attention to:

• Employees excluded without documented eligibility
• Employees transferred from another Indian employer
• International workers
• Employees whose wage structure has changed
• Employees included in payroll but missing from the statutory return
• Contributions deposited under an incorrect member identifier

8. Confirm Employees’ State Insurance Coverage

Employees’ State Insurance coverage generally extends to factories and notified establishments meeting the applicable employee threshold. The threshold is commonly 10 employees, although a threshold of 20 may continue for specified establishments in some states.

The general wage ceiling is ₹21,000 per month, increasing to ₹25,000 per month for persons with disabilities.

Current contribution rates are:

• Employer: 3.25%
• Employee: 0.75%

Once coverage applies, the establishment should generally register within 15 days. Eligible employees should be registered when they join, and monthly contributions are generally due within 15 days after the end of the month.

CFO control

Reconcile:

• Gross wages used for coverage assessment
• Employee insurance numbers
• Contribution calculation
• Monthly contribution file
• Payment challan
• Joiners and departures
• Employees near the wage ceiling
• Employees continuing in a contribution period after crossing the ceiling, where applicable

Do not rely solely on total contribution values. Employee-level omissions can remain hidden even when the overall payment appears reasonable.

9. Build a State-by-State Payroll Compliance Matrix

A national checklist is not sufficient for a multi-location workforce.

Depending on the state and establishment, additional obligations may include:

• Professional tax
• Labour Welfare Fund
• Shops and Establishments registration
• State minimum wages
• Leave and holiday requirements
• Wage and attendance records
• Local notices and displays
• State-specific returns and renewals

For example, official state systems prescribe their own Labour Welfare Fund contribution periods and remittance processes. The applicable rules and dates must therefore be verified for each employee location.

Recommended matrix

 

Update the matrix before hiring in a new state, not after the first payroll has been processed.

10. Accrue Bonus, Gratuity and Maternity Costs Correctly

Statutory payroll obligations include costs that may not be paid every month but should still be considered in budgeting and accounting.

Statutory bonus

Where the eligibility conditions apply, the minimum bonus is generally 8.33%, while the maximum is 20%. Eligibility depends on the notified wage limit and other statutory conditions, including the required working period.

Gratuity

Gratuity is generally payable after five years of continuous service. Different rules can apply in cases such as death, disablement and fixed-term employment. A fixed-term employee may qualify after one year of service.

The usual calculation is based on 15 days’ wages for each completed year of service, subject to applicable rules and limits. Gratuity should generally be paid within 30 days after it becomes payable.

Maternity benefits

An eligible employee generally requires at least 80 days of service in the prescribed period. Maternity benefit may extend to 26 weeks, subject to statutory conditions. A crèche requirement applies to establishments meeting the prescribed employee threshold, including establishments with 50 or more employees.

CFO control

Maintain monthly provisions for:

• Gratuity
• Statutory bonus
• Leave encashment
• Incentive liabilities
• Employer social security
• Notice pay
• Other employment benefits

Payroll, actuarial reports and financial-statement provisions should use consistent employee data.

11. Treat Employee Exits as a Compliance Event

The final payroll should not be handled as a routine monthly adjustment.

The exit process may involve:

• Final wages
• Unpaid salary
• Leave adjustment
• Incentives
• Reimbursements
• Notice pay
• Permitted recoveries
• Provident Fund exit update
• Employees’ State Insurance update
• Gratuity assessment
• Tax recomputation
• Final tax certificate information

Wages due on exit should generally be paid within two working days. Gratuity, where payable, should generally be paid within 30 days.

CFO control

Use a departure checklist signed by HR, payroll and finance. It should record:

• Last working date
• Salary paid through date
• Leave balance
• Notice-period treatment
• Recoveries and legal basis
• Gratuity eligibility
• Final tax computation
• Statutory exit updates
• Payment date
• Accounting entries
• Supporting approvals

Do not delay undisputed statutory payments merely because an asset, expense or administrative clearance remains pending.

12. Retain Payroll Records and Build an Audit Trail

Employers are required to maintain prescribed records covering areas such as attendance, wages, overtime, deductions and related employment information. Under the current framework, specified records should generally be retained for five years, and employees should receive wage slips on or before payment.

Monthly evidence pack

The payroll owner should retain:

• Approved employee-master changes
• Attendance and leave inputs
• Payroll register
• Variance report
• Bank-payment file
• Bank confirmation
• Payslip control report
• Salary tax challan
• Provident Fund return and challan
• Employees’ State Insurance contribution record
• State payment and filing evidence
• Joiner and departure register
• General-ledger posting
• Payroll reconciliation
• Exception approvals

CFO control

Evidence should be stored by payroll month and legal entity, not across individual email inboxes.

A reviewer should be able to select one employee and trace:

Employment terms → payroll inputs → gross-to-net calculation → bank payment → statutory reporting → general ledger

CFO-Grade Indian Payroll Compliance Calendar

State dates and establishment-specific obligations should be added as separate rows rather than forced into a single national calendar.

Five Payroll Risks Global CFOs Commonly Miss

1. Salary components are approved without a wage-definition test

A salary structure may look commercially reasonable but still alter the statutory wage base. Finance should review cost impact before the structure is released to employees.

2. A remote employee creates a new state footprint

One employee working permanently from another state can trigger minimum-wage, professional-tax, establishment or Labour Welfare Fund questions. HR should not change an employee’s location without a compliance assessment.

3. Statutory totals are reviewed, but employee-level exceptions are not

A monthly contribution can appear consistent while one employee is missing or mapped incorrectly. Review exception reports, not just aggregate numbers.

4. Payroll does not reconcile to accounting

Gross pay, employer costs, deductions, payable balances and bank payments must reconcile to the general ledger. Old payroll liabilities should be investigated rather than carried forward indefinitely.

5. The service provider gives a dashboard but not evidence

A dashboard can show that a task is “complete.” It does not replace a challan, filing acknowledgement, employee-level return or bank confirmation.

Where EOR Services in India Fit

EOR services in India can support companies that need to employ talent before establishing their own Indian entity or while deciding whether a permanent GCC is commercially justified.

In an EOR arrangement, the provider typically acts as the local legal employer, while the client directs the employee’s day-to-day work. The exact allocation of responsibilities must be documented in the contract and confirmed against the provider’s registrations and operating model.

SansoviGCC’s EOR model covers payroll and statutory obligations such as Provident Fund, Employees’ State Insurance, salary tax deduction and employment compliance, while the client retains operational control over the workforce.

However, using an Employer of Record Service Provider does not remove the CFO’s governance responsibility.

Monthly evidence CFOs should request from an EOR

• Employee-level payroll register
• Gross-to-net reconciliation
• Bank-payment confirmation
• Sample or complete payslip control report
• Provident Fund return, challan and payment proof
• Employees’ State Insurance contribution file and payment proof
• Salary tax challan
• Quarterly Form 138 acknowledgement
• State filing and payment evidence
• Joiner and departure report
• Payroll exception log
• Payroll-to-invoice reconciliation

Contract controls for an Employer of Record Service Provider

The agreement should address:

• Identity of the employing legal entity
• Responsibility for registrations and filings
• Payroll-input and approval deadlines
• Funding and salary-payment timelines
• Statutory payment deadlines
• Audit and document-access rights
• Treatment of interest, penalties and compliance failures
• Employee-data protection
• Approval of salary and employment changes
• Handling of disputes and employee claims
• Exit and termination responsibilities
• Transfer of employees from EOR to the company’s own entity
• Record handover after contract termination

The CFO should also verify that the employer named on employment documents, payslips, statutory filings and bank records is consistent.

When Should a Company Move From EOR to Its Own GCC Entity?

An EOR can be effective during market entry, early hiring or a time-sensitive launch. It should not become an automatic long-term decision without periodic review.

A move to an owned entity may become appropriate when:

• Indian headcount becomes predictable
• The company requires greater control over employment policies
• Senior or regulated roles are being hired
• The cost of the EOR model exceeds entity and operating costs
• The company is creating long-term intellectual property in India
• Customers or regulators require a local entity
• India becomes a permanent delivery or capability location

The decision should compare total cost, legal exposure, speed, operating control and transition risk—not only the provider’s per-employee fee.

SansoviGCC supports companies across early hiring, EOR payroll in India, payroll and HR operations, compliance design, legal-entity setup and EOR to GCC transition.