EPFO ECR validator

Paste an Electronic Challan-cum-Return file and we run twelve validations: UAN format, NCP-day bound, percentage check, gross-wage cap, and the rest.

  • Twelve validations matching the EPFO portal
  • UAN format and gross-wage cap enforced
  • NCP days bounded and employer-share matched
Validation result
Rows submitted: [N]
UAN format: Pass ([N] rows checked)
NCP-day bound: Pass / Fail
Employer share matches employee share: Pass / Fail
Gross-wage cap (₹15,000 default): Pass / Fail
[N] validations passed of 12.

Use the validator

Fill in the fields below. The tool runs entirely in your browser; no data leaves the page.

Why the ECR is the dispute hotspot

The Electronic Challan-cum-Return has fourteen fields per row. Any field wrong and EPFO either rejects the file or accepts it with a silent error that surfaces months later when the employee tries to withdraw or transfer.

Common failure modes: UAN missing or wrong, gross wages not capped at the wage ceiling, employer EPS share computed from the wrong base, and the establishment code mismatched between the file and the portal.

What the twelve validations cover

UAN format, NCP days bound, percentage check on EPF and EPS shares, gross-wage upper bound for the establishment, employer-share match against employee-share for standard cases, the cap-handling logic for grandfathered employees, and a few more.

The cap-handling logic is the most subtle. The cap must apply pre-percentage, not post; getting this wrong is the most frequent under-deduction issue.

How to use the validator

Paste the tab-separated rows from your ECR file into the form. We don't store the file; the validation runs in your browser and the result is shown inline. For full audit logs, run the same engine inside pPULSE Payroll.

If validation fails, the result panel surfaces the specific rows that failed which check, so the cycle owner can fix and re-validate.

Frequently asked questions

Does this submit to EPFO?

No. This is a pre-submission validator. After you fix any issues, submit through the EPFO portal as usual. The validator catches issues before submission, not in place of it.

What happens if validation fails on a few rows?

Fix those rows in your source data, re-export the ECR, and re-validate. The validator can be run as many times as needed; nothing is persisted.

Is the wage ceiling configurable?

Yes. The default cap is ₹15,000 per the act, but companies that contribute on actual wages (above the cap) can disable the cap-check during validation.

Where do the validation rules come from?

They mirror the EPFO portal's server-side validations plus a few additional checks we have observed catch issues that the portal does not flag clearly. See the field-by-field walkthrough.

Ready to get started?

Join the waitlist and try pPULSE the moment your slot opens, or talk to us about a custom rollout for your team.

See what you'll pay

Clear per person pricing. No surprise setup or onboarding fees.

See pricing details

Book a demo

A 30 minute walkthrough, tailored to how your team actually works.

Schedule a demo