Skip to main content

PROTAX INSIGHTS

Payroll Outsourcing Services in India: What the Scope Should Cover

A practical guide to defining payroll outsourcing scope, monthly inputs, approvals, TDS responsibilities, statutory work and data controls.

Laptop, calculator and open notebook arranged for monthly payroll processing

Payroll outsourcing can move the recurring calculation, documentation and filing work to an external team. The employer still controls employee data, compensation decisions, approvals and the money used for salaries and statutory payments. A useful proposal should say exactly what the provider will prepare, what the employer must supply, and who signs off each step.

That level of detail matters because "managed payroll" can mean anything from salary calculations and payslips to a wider service covering TDS statements, provident fund, employee state insurance and state-specific obligations.

Begin with the payroll setup

Before the first live cycle, the provider should review the information that drives payroll:

  • employee master data and joining dates;
  • approved salary structures and pay frequency;
  • PAN and bank details;
  • leave, attendance and loss-of-pay rules;
  • opening balances for salary TDS;
  • existing statutory registrations and applicability; and
  • year-to-date payroll and challan data when the change happens mid-year.

The employer should approve a clean opening file. If old records contain inconsistent names, missing tax identifiers or unexplained balances, carrying them into a new payroll system will reproduce the same problems.

Agree which document is the system of record. HR software, an attendance platform, email and spreadsheets should not compete with one another after the monthly cut-off.

Define the monthly input and approval cycle

A written calendar should identify the cut-off for attendance, new joiners, exits, salary revisions, reimbursements, bonuses and one-time deductions. It should also name the people authorised to submit or approve changes.

A practical monthly sequence is:

  1. the employer sends approved payroll inputs and exceptions;
  2. the provider validates changes against the employee master;
  3. a draft payroll register and variance report are prepared;
  4. the employer reviews unusual movements and approves the run;
  5. the provider produces the final register, payslips and agreed payment files; and
  6. both sides preserve the approval and supporting records.

The provider should not infer a salary revision or recover an amount from an employee without documented authority. Late changes need a defined process so that everyone knows whether they will be included in the current run or carried to the next one.

Specify the outputs

At minimum, the scope should list the deliverables for each payroll cycle. These may include:

  • employee-wise gross-to-net payroll register;
  • variance report against the previous period;
  • payslips;
  • salary bank advice or upload file, if agreed;
  • department or cost-centre summary for accounting;
  • leave and attendance exception report;
  • full-and-final settlement working for approved exits; and
  • journal-entry support for the books.

Ask how corrections will be handled after payroll approval. The answer should distinguish a calculation correction from a change in the underlying HR instruction.

Separate salary TDS from other payroll work

Salary TDS needs its own responsibility table. The scope can cover annual tax projections, employee declarations, investment-proof review, monthly deduction workings, payment support and quarterly statement preparation.

For Tax Year 2026, 27, the Income Tax Department identifies Form 138 as the quarterly statement for reporting TDS deducted on salary, pension or specified interest income. It was earlier known as Form 24Q.

Confirm who will:

  • collect and review employee declarations or proofs;
  • compute monthly salary withholding;
  • prepare challan information;
  • reconcile deductions with deposits;
  • prepare and validate Form 138 data;
  • upload or submit the statement through the authorised account; and
  • resolve defaults, corrections or identifier mismatches.

The employer should retain access to its registrations, filing accounts, challans and acknowledgements. Outsourcing the preparation does not transfer the employer’s legal responsibility for correct and timely compliance.

Use a scope matrix for PF, ESI and state obligations

Do not accept a broad line stating "all statutory compliance." List each item separately and record whether it applies, who calculates it, who funds and pays it, who files it, and who keeps the acknowledgement.

Provident fund, ESI, professional tax and labour welfare fund coverage can depend on facts about the employer, employees and location. The engagement should not assume that every item applies in every case.

A multi-state workforce needs extra care because state registrations and local obligations may differ. Changes in employee location should reach the payroll team through a controlled update, not an informal message after the run.

Agree the control and data rules

Payroll contains bank details, tax identifiers, compensation data and employee records. Ask where the data will be stored, who can access it, how files will be exchanged, and how access is removed when a team member leaves.

The monthly control pack should show who prepared, checked and approved payroll. It should also record changes to bank details, duplicate employees, negative net pay, large salary movements, missing PAN data and unprocessed leavers.

Set a retention period for registers, working papers, challans, statements and approvals. The provider should return the employer’s records in a usable format when the engagement ends.

Questions to ask before appointing a provider

Ask for precise answers to these questions:

  • Which services are included and which require a separate engagement?
  • What are the employer’s monthly cut-off and approval duties?
  • Who makes salary and statutory payments?
  • Which returns or statements will the provider prepare and submit?
  • How are late inputs, revised payroll and correction statements handled?
  • What information-security and access controls are used?
  • What reports, source files and acknowledgements will the employer receive?
  • How will payroll be transferred back or to another provider?

Avoid proposals that promise "complete compliance" without defining responsibility. Also be cautious when the provider wants to control employer credentials, cannot produce calculation workings, or treats every correction as an informal adjustment in the next month.

How ProTax can support the payroll cycle

ProTax Consultancy’s TDS & Payroll Compliance service can help structure the monthly input process, prepare payroll and salary-TDS workings, reconcile records and support agreed filings. The engagement scope should be matched to the employer’s workforce, registrations and internal approval process.

A clear scope makes the service easier to supervise. It also gives the employer a complete set of records for accounting, employee queries and statutory review.

*Photo: Jakub Zerdzicki / Pexels (free Pexels licence).*

Discuss This With ProTax

FROM THE PROTAX LIBRARY

Recent Articles & Guides

Practical reading on business records, tax filings and the decisions that come with running a company.

Newsletter

Stay ahead on compliance, tax & business updates

Get selected business and compliance updates by email. Once a month, no spam.

  • 100% privacy
  • 1 email / month
  • Unsubscribe anytime
Contact ProTax
Chosen by individuals and businesses

Get Help With Your Business

Tell us what you need help with. Our team will review your enquiry and explain the next steps.

Free Consultation No Obligations Expert Advice
FREE Consultation Get Started @ ₹299 ₹0

Talk To ProTax

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice
FREE Consultation Get Started @ ₹299 ₹0

Request a Free Quote

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice