What to Demand, What to Accept, and What to Walk Away From
Most payroll outsourcing agreements describe what a provider will do. Few specify when they will do it, how fast they will fix it when it fails, or what happens to you if they miss a commitment. That gap — between what is promised and what is contractually enforceable — is where the risk lives.
This article defines the SLA standards a professional payroll outsourcing arrangement in India should meet. For each area, we specify what to demand in the contract, what is acceptable when justified, and what signals a provider is not operationally serious.
A service level that is not written into the contract is not an SLA. It is a sales claim. Every standard in this document should be a contractual commitment — not a verbal assurance, not a slide in the proposal deck, not a “we aim for” statement in an email.
1. Payroll Processing SLAs
These are the SLAs your employees experience directly. A payroll that does not close on time, or that does not credit correctly, creates immediate visible damage. The processing SLA is the most fundamental test of operational capability.
| Metric | Demand this | Can accept if justified | Walk away if… |
| Data cut-off to payroll approval-ready output | 48–72 hours | 72–96 hours with documented complexity justification | “7–10 business days” |
| Salary credit confirmation to employees | By agreed salary day, no exceptions | T+1 if banking delays are documented and communicated same day | “We target end of month” |
| Payslip availability post salary credit | Within 24 hours | 48 hours maximum | “Within the week” |
| Payroll error correction (after approval, pre-credit) | Same day if caught before 2pm; next business day if after | 48 hours for complex multi-state revisions | No stated SLA |
| Off-cycle payroll for joiners / exits mid-month | 5 business days from data receipt | 7 business days for complex cases | “Processed in next regular cycle only” |
2. Statutory Compliance SLAs
These are the SLAs with direct financial and legal consequences. Missing a statutory deadline generates a penalty that accrues daily. A provider who targets the deadline rather than building a buffer before it is not protecting you — they are managing their own risk by running yours to the line.
| Statutory obligation | Legal deadline | Minimum SLA to demand | Why the buffer matters |
| PF contribution deposit (ECR) | 15th of following month | Filed by 10th — 5 days before | Bank failures, public holidays, and EPFO portal outages need recovery time. Deadline-day filing = zero buffer. |
| ESIC contribution deposit | 15th of following month | Filed by 10th | Same risk profile as PF. A rejected ESIC payment needs re-processing time within the window. |
| TDS deposit | 7th of following month | Deposited by 5th | Short window. A banking failure on 6th or 7th generates a 1% per month interest penalty with no recovery option. |
| TDS return (Form 24Q) | 31 Jul / 31 Oct / 31 Jan / 31 May | Filed 7 days before deadline | Late filing attracts ₹200/day penalty (Sec 234E). The return cannot be amended after the fact for missed quarters. |
| Professional Tax (per state) | Varies by state | Filed 5 business days before each state deadline | Provider must track state-specific PT deadlines separately — not as a single national task. Confirm they do. |
| Form 16 issued to employees | 15 June annually | Issued by 10 June | ₹100/day/employee under Sec 272A post-15 June. Employees who cannot file ITR accurately become hostile. Five extra days costs nothing. |
If a provider’s statutory SLA is “we file by the deadline” — that is not an SLA. That is a statement of minimum legal compliance. The SLA is the buffer they build before the deadline. Ask specifically: “If the EPFO portal goes down on the 14th, what happens to my ECR?” The answer tells you whether they have actually thought about this.
3. Employee Query and Support SLAs
How fast a provider resolves an employee query is a proxy for how seriously they take the human dimension of payroll. A payslip error that takes four days to acknowledge damages trust more than a payslip error that is acknowledged in two hours and fixed the next day.
| Query type | First response | Resolution | What “resolution” means |
| Payslip component discrepancy | 4 hours | 24 hours | Corrected payslip issued or written explanation of why the calculation is correct. |
| TDS deduction query / ITR discrepancy | 4 hours | 48 hours | Calculation walkthrough provided. If correction needed: revised Form 16 issued within 5 business days. |
| PF / ESIC contribution verification | Same day | 48–72 hours | ECR data or ESIC portal confirmation shared with employee. Provider should be able to pull this without escalation. |
| Escalated complaint (unresolved at 48 hours) | Named senior contact same day | Committed resolution date | The escalation path must be defined before an incident occurs. Ask for the named escalation contact in the contract. |
A provider whose support model is a ticketing system with a 2-business-day first-response SLA is not set up to handle payroll. Payroll issues affect employees on salary day. Payroll support must be people-first, same-day responsive for first-contact, and have a named contact your HR team can call directly.
4. Onboarding and Offboarding SLAs
These are the SLAs that affect your employer brand. A new joiner whose statutory registrations are delayed gets a poor first impression. A departing employee whose F&F is late leaves with a grievance.
| Activity | Demand | Acceptable | Walk away |
| New joiner: first payroll inclusion | If data received by cut-off: same month. If received after: next month confirmed in advance. | Pro-rated first month with clear communication to employee | “Depends on when data is received” with no defined process |
| New joiner: UAN generation and PF registration | 5 business days from joining date | 10 business days for complex cases | “We do it in the first payroll cycle” — that can mean 30+ days |
| Exit F&F calculation provided to HR for approval | Within 10 business days of last working day | 15 business days for senior roles with complex comp | “30–45 days is standard practice” |
| Relieving letter and experience letter issued | Same day as F&F settlement | Within 3 business days of F&F settlement | Issued only after all documents received and reviewed — no SLA |
5. What Must Appear in the Contract — Not Just the Proposal
Proposals are marketing documents. Contracts govern the relationship. These are the five things a payroll outsourcing contract must contain before you sign:
| Contract must-have | Why it matters |
| Every SLA stated as a specific number — hours or business days, not “promptly” or “in a timely manner” | “Promptly” has no legal meaning and cannot be enforced. Every SLA in this document should be numbered. |
| Defined consequence for missed SLAs — service credit, penalty, or right to remediation | Without consequences, SLAs are intentions. Ask: “What happens if you miss the payroll processing SLA?” If there is no answer, there is no SLA. |
| Data portability clause: your data in standard format on request, within 5 business days | Without this, your data is held in their system and cannot be migrated without their cooperation. This is a significant exit barrier. |
| Exit notice period of 30–60 days maximum, with full transition support obligation | Some providers bury 90-day notice periods in the contract. You discover this only when you want to leave. Read the termination clause before signing. |
| Liability clause: who bears the financial cost of a compliance failure caused by provider error | If a provider’s late ECR filing generates a PF penalty, is that penalty absorbed by the provider or passed to you? In most contracts without this clause: you bear it. |
| Get Paybooks’ written SLA commitment before your next contract review We publish specific, contractual SLAs for every metric in this article. Request the full SLA schedule — no sales call required. paybooks.in/outsourcing-services | info@paybooks.in | +91 80 4710 7171 |
