Common ECR upload errors, and how to fix them

Why ECR uploads fail

The portal checks every row of your file before it accepts it. It checks the file format, each UAN (the employee's lifelong PF account number), the dates and the amounts. One wrong row can stop the whole file.

The portal shows what went wrong. The exact words can change, so below we describe each problem in plain words.

Quick checklist before you upload

• The file is a .txt file, not Excel or CSV.
• Each employee is on one line, with the details split by #~#.
• There is no heading row and no empty line.
• Every UAN is correct, linked to Aadhaar, and added to your business on the portal.
• New staff have a joining date. Staff who left have an exit date.
• Wages and PF amounts match this month's salary sheet.
• Each UAN appears only once.
• Earlier months' ECRs are already filed.

The common errors, and how to fix them

1. Wrong file format or separator

What's wrong: the portal can't read the file at all, or says a line has the wrong number of fields.

Why: the portal needs a plain text file. Each line has the same fields, in the same order, split by #~# (hash, tilde, hash). A comma, a tab or a missing field breaks the line.

The fix: keep the columns in the right order: UAN, name, gross wages, EPF wages, EPS wages, EDLI wages, the employee's PF, the EPS amount, the employer's EPF amount, NCP days and refund of advances. Make the text file with our free EPF Excel to Text converter. It joins the fields with #~# for you.

2. Wrong UAN

What's wrong: the portal rejects a row because the UAN is not valid.

Why: a digit is typed wrong, or two digits are swapped. Sometimes Excel changes a long number when you copy it.

The fix: copy each UAN from the portal's list of your employees, not from old files. Names are different. The PF goes to the UAN, under the name in EPFO's records. A small spelling difference usually does not stop the upload. If the name in EPFO's records is wrong, get it corrected there.

3. UAN not linked to Aadhaar (KYC not done)

What's wrong: the portal won't take PF for one employee.

Why: EPFO needs each employee's UAN linked to their Aadhaar. KYC means the ID details, like Aadhaar, PAN and bank account, saved against the UAN. If the Aadhaar link is missing or not checked yet, that employee's row can fail.

The fix: check the employee's KYC status on the employer portal. Ask the employee to finish any step that is pending. New staff get their UAN with a quick face scan on the UMANG app. We guide them.

4. Employee not linked to your business

What's wrong: the UAN is valid, but the portal says it is not part of your business.

Why: a new employee's UAN was never added to your business on the portal. This is common when someone brings a UAN from their old job.

The fix: add the employee on the employer portal, with the date they joined. Then upload the ECR again.

5. Wage mistakes: EPF wages, EPS wages and the wage limit

What's wrong: the wages in a row don't make sense together, or don't match the amounts.

Why: the four wage columns mean different things:

• Gross wages: the full pay for the month.
• EPF wages: PF wages, that is basic pay plus DA (dearness allowance), not the full salary. They can't be more than gross wages. PF wages must be at least half the total pay. If they come to less, the difference is added to PF wages.
• EPS wages: wages for the pension part, EPS (Employees' Pension Scheme). For most staff, these stop at the PF wage limit.
• EDLI wages: wages for EDLI (Employees' Deposit Linked Insurance), the staff insurance part. These also stop at the PF wage limit.

The PF wage limit went up from ₹15,000 to ₹25,000 a month on 17 September 2026. Payroll software that still uses the old limit gives wrong EPS and EDLI wages. Some staff are not in the pension scheme, for example most staff aged 58 or more. Their EPS wages are usually 0.

The fix: check that your software uses the new limit for wages from October 2026. Earlier months use the old limit. Check who is in the pension scheme. For September 2026 wages, EPFO has not yet confirmed how to treat the change in the middle of the month. Call us to check.

6. PF amounts don't match the wages

What's wrong: the amounts in a row don't add up from the wages.

Why: the employee pays 12% of EPF wages. The employer also pays 12%, split in two. 8.33% of EPS wages goes to EPS. The rest goes to EPF. A hand-typed amount, or a different way of rounding, gives a wrong figure.

The fix: work out the amounts with a formula in Excel, not by hand. Use whole rupees. Check a few rows with our free PF contribution calculator.

7. Wrong NCP days

What's wrong: the NCP days in a row don't fit the month, or don't fit the wages.

Why: NCP (non-contributory period) days are the days in the month the employee was not paid for, like unpaid leave. They can't be more than the days in the month. If someone had unpaid days, their wages should be lower too.

The fix: take NCP days from your attendance record. Put 0 if the employee was paid for the full month.

8. The same UAN twice

What's wrong: one employee appears in two rows, or was already filed for this month.

Why: two salary sheets were joined, or a row was copied twice. An employee can be in only one regular or supplementary return for a month.

The fix: sort the sheet by UAN and remove the extra row. If pay changed during the month, add it up into one row.

9. Staff who have left, or a wrong exit date

What's wrong: the portal rejects a row for someone who has left.

Why: the portal checks each employee's joining and exit dates against the wage month. If the exit date is before this month, they can't be in this month's ECR. A wrong exit date causes the same problem.

The fix: include staff only for the months they worked. Mark the date when staff leave, so your list of current staff stays correct. If an exit date was entered wrongly, call us. It may need a request to the PF office.

10. Empty lines or stray characters

What's wrong: the file looks right, but one line fails, often the last one.

Why: an empty line at the end, a space before a number, or a comma, quote mark or tab copied in from another file.

The fix: open the text file in Notepad before you upload. Every line should start with a UAN. Delete empty lines. Keep names to plain letters and spaces.

11. ECR already filed for the month

What's wrong: the portal won't take a new ECR for a month you already filed. Or it won't take this month's ECR yet.

Why: under EPFO's new ECR system (from September 2025 wages), each month has one regular return. You may also need to file earlier months first.

The fix:

• Before you approve it: check the summary. If something is wrong, reject it, fix the file and upload it again.
• Missed some staff: add them with a supplementary return.
• Wrong figures: fix them with a revised return. You can lower amounts only before you start the payment.
• An earlier month is not filed: file that month first.

How to avoid ECR errors next month

Most errors start in the salary sheet, not on the portal. A simple monthly routine stops them:

1. Add new staff and mark the date when staff leave, on the portal, before the month ends.
2. Fill in our ECR Excel format from your salary sheet, with formulas for the PF amounts.
3. Turn it into a text file with the EPF Excel to Text converter. It keeps the columns in order, joins them with #~#, keeps UANs whole and drops empty rows. Your file stays on your computer.
4. Upload it a few days before the 15th. Then you have time to fix an error and still pay the challan by the 15th.

The converter only changes the file format. It does not check your figures, so check the amounts first. For other mistakes that cost businesses money, read 6 common PF mistakes.

Rather not deal with this every month?

You send us the salary details. We prepare the ECR, check it and file it. We get the payment slip (challan) ready in time, so you can pay by the 15th. See our PF monthly filing service.