Contract Labour Invoice Includes PF/ESI but Contributions Missing: Principal-Employer Audit File
By Ravi Sisodia · Reviewed by CA Divyanshu Sengar · Updated 5 October 2026
India-first finance and compliance workflow with primary-source anchors.
2-minute summary
- A contractor invoice that separately charges PF or ESI does not prove that contributions reached workers’ accounts. Principal-employer control should reconcile the billed labour population to attendance/gate records, wage sheets, UAN/IP identifiers, ECR/ESIC returns and payment evidence before releasing the compliance-linked portion of the invoice.
- The current social-security framework keeps employer and contribution obligations statutory; commercial wording between principal employer and contractor cannot make missing worker records disappear. For ESI, principal-employer concepts and recovery rights have historically required close contractor oversight, and the Code on Social Security continues the broader social-security compliance structure.
- The audit should be member-level and period-specific. A bulk challan, CA certificate or contractor declaration can support the file but should not substitute for matching the people who actually worked at the site to the contribution evidence.
Current position
Control and decision map
| # | Control / decision step |
|---|---|
| 1 | Obtain contractor attendance/gate/biometric population for the billing month. |
| 2 | Match each worker to wage sheet, UAN/member ID and ESIC IP number where applicable. |
| 3 | Reconcile wages/contributions to PF ECR and ESIC return/payment evidence. |
| 4 | Investigate workers on site who are missing from statutory returns or mapped to another establishment. |
| 5 | Apply contractual holdback/indemnity/escalation only after documenting the exception and giving the contractor a correction route. |
| 6 | Close the month with a signed exception register showing contribution posting or formal resolution for every gap. |
Evidence pack
- Contract and compliance clause
- Site attendance/gate register
- Contractor wage sheet
- PF ECR/challan and ESIC contribution proof
- Worker-wise exception/correction register
Worked example
A manpower contractor bills Rs 10 lakh plus separate PF/ESI lines and attaches two aggregate challans. Site attendance shows 120 workers, but the ECR extract contains only 106 matching names/UANs. Accounts payable should not approve the statutory charge solely because the challan total looks reasonable; the missing 14 workers must be reconciled before the compliance file is closed.
Common mistakes
- Accepting aggregate challans without worker matching.
- Reconciling invoice headcount only to contractor payroll, not site attendance.
- Ignoring wrong UAN/IP mapping because total contribution value is close.
- Using a contractual indemnity as a replacement for compliance monitoring.
Frequently asked questions
Is a PF/ESI line on an invoice proof of payment?
No. Validate statutory returns and member/insured-person records.
What should the principal employer retain?
Contract, attendance, wage sheet, contribution evidence and an exception-resolution log.
Can the contractor fix mapping later?
Potentially, through the prescribed portal/correction route, but track the correction to actual closure.
Official sources
- Ministry of Labour and Employment - Code on Social Security, 2020 (Act 36 of 2020; effective 21 Nov 2025)
- Employees' Provident Fund Organisation - Unified Portal - employer services and UAN/ECR framework (EPFO Unified Portal; current; portal updated Oct 2026)
- Employees' State Insurance Corporation - ESIC official portal / contribution and benefit administration (ESI / Social Security framework; current)
- Employees' Provident Fund Organisation - EPFiGMS grievance portal (EPFiGMS; current)
Disclaimer
Educational and professional reference only; confirm the current law, rates and the facts of your case before relying on this page.