Employer correction
Correct master data, return and remittance with a preserved audit trail; do not overwrite the original default.
Paragraph 28: Payment of contributions etc.
Paragraph-wise legal explanation, implementation control, evidence, remedy and transition mapping for Employees’ Provident Funds Scheme, 2026.
Chapter VI — Responsibilities, forms and returnsG.S.R. 525(E)Contributions and default
What this paragraph regulates
Paragraph 28 is the canonical current-scheme provision for Payment of contributions etc.. It must be read with the Code on Social Security, 2020, the defined terms, current Central Government notifications, EPFO implementation directions and saved legacy rights.
Legal source: Employees’ Provident Funds Scheme, 2026, notified under section 15(1)(a) of the Code on Social Security, 2020. It supersedes Employees’ Provident Funds Scheme, 1952, except for things already done or omitted before supersession. Open Gazette copy.
Paragraph-specific legal and control map
Control 1: Requires electronic payment of contribution and charges within fifteen days after close of the month
Requires electronic payment of contribution and charges within fifteen days after close of the month.
Implementation test: Identify the responsible person, source data, statutory event, approval and retained evidence for this control. A payroll label or portal status alone is not conclusive where underlying facts differ.
Control 2: Employer bears remittance cost and remains accountable for direct and contract labour
Employer bears remittance cost and remains accountable for direct and contract labour.
Implementation test: Identify the responsible person, source data, statutory event, approval and retained evidence for this control. A payroll label or portal status alone is not conclusive where underlying facts differ.
Control 3: Electronic return, challan, bank confirmation and ledger must reconcile exactly
Electronic return, challan, bank confirmation and ledger must reconcile exactly.
Implementation test: Identify the responsible person, source data, statutory event, approval and retained evidence for this control. A payroll label or portal status alone is not conclusive where underlying facts differ.
Control 4: Late correction should not overwrite evidence of the original due date or default period
Late correction should not overwrite evidence of the original due date or default period.
Implementation test: Identify the responsible person, source data, statutory event, approval and retained evidence for this control. A payroll label or portal status alone is not conclusive where underlying facts differ.
Responsible parties
- Employer / principal employer
- Payroll and compliance owner
Code linkage
Sections 16, 17, 127 and 128.
Timing and trigger
Within 15 days of the close of each month.
Decision questions
- Is the establishment and person covered on the event date?
- Is this a current-scheme event, a saved legacy event or a correction?
- Which wage, service, balance, family or fund data is legally relevant?
- Which form, portal, authority and evidence are required?
Evidence and audit trail
- wage register
- contribution computation
- electronic return/challan
- bank proof
- interest and damages working
Minimum review controls
- Maker-checker sign-off tied to employee/member ID.
- Reconciliation to payroll, contractor, fund and bank records where relevant.
- Current rate, ceiling, circular and portal version check.
- Exception log and legal basis for overrides or delayed correction.
- Retention of acknowledgement, order and proof of payment/benefit.
Non-compliance, remedy and escalation
Possible consequences include contribution assessment, interest, damages, recovery, penalty, benefit correction, delayed-claim interest, cancellation of exemption or litigation. The exact pathway depends on whether the issue concerns coverage, contribution, a Fund decision, a member benefit or an exempted establishment.
Member/claimant remedy
Use the prescribed claim, grievance, review or appeal route with complete supporting evidence.
Authority action
Assessment, interest, damages and recovery should be separately quantified and linked to the applicable Code order.
Worked control scenario
An establishment receives a transaction or employee event that falls within Payment of contributions etc.. The compliance owner first fixes the event date and member status, then retrieves wage/service/nomination or fund data as relevant. The maker prepares the statutory computation or claim; an independent reviewer checks the Code link, paragraph conditions, current ceiling/rate and prior transactions. Only after reconciliation is the portal filing or payment completed. The acknowledgement, calculation and supporting records are retained together.
Failure pattern: treating an EPFO portal acceptance as proof that the underlying legal classification, wage base or claimant entitlement is correct. Portal processing does not eliminate assessment, recovery, damages, benefit-revision or competing-claim risk.
Practical Q&A
Can a contract or payroll policy override this paragraph?
No. A contract may allocate operational responsibility but cannot reduce statutory liability or member entitlement.
Can an old-scheme paragraph still matter?
Yes, for things done, omitted, accrued or pending before supersession. Document the event date and savings basis; do not mix historic and current rules.
Is the Gazette page alone enough for live compliance?
No. Check later notifications, EPFO circulars, portal specifications, court orders and establishment-specific exemption orders.