NCP Days in PF: What They Are and How They Change Your ECR

NCP days are the smallest field in the provident fund return and they carry more consequence than anything else on the line. Eleven fields go up in a monthly ECR. Ten of them are money. The tenth is a count of days, and it is the one that decides whether a month counts towards an employee's pension.

Most explanations stop at the definition. NCP stands for non-contributory period, it means days in the wage month for which no wages were paid, and you calculate it by subtracting paid days from days in the month. That is correct and it takes a sentence.

What it leaves out is everything that actually causes trouble. Whether a weekly off inside a spell of unpaid absence is an NCP day. What to report for somebody who joined on the 18th, where competent practitioners genuinely disagree and the two answers produce different pension records. What happens to the ₹15,000 ceiling when there are NCP days, which is not what most people assume. And what a wrong NCP figure costs, which since 29 June 2026 includes a family's insurance claim under a scheme whose rules were rewritten this year.

This article covers those. It is written for whoever files the ECR, and it assumes you already know what provident fund is.

Positions are current at September 2026 and reflect the Employees' Provident Funds Scheme, 2026, the Employees' Pension Scheme, 2026 and the Employees' Deposit-Linked Insurance Scheme, 2026, all notified under the Code on Social Security, 2020 and effective from 29 June 2026, together with the Code on Wages, 2019 as brought into force on 21 November 2025. Worked examples state their assumptions. Nothing here is legal advice, and where practice is genuinely unsettled this article says so rather than picking a side and presenting it as settled.

The short version, before the detail.

NCP days are days in a wage month for which an employee earned no wages, reported as a whole number in the tenth field of the ECR. Paid leave, weekly offs and paid holidays are not NCP days, because wages were paid for them. The count reduces the wage figure the contribution is computed on, including where wages are restricted to the ₹15,000 ceiling, which is prorated as well. A month in which wages and contributions are nil does not count towards the ten years of service that pension eligibility requires. And under the 2026 insurance scheme, continuous service is now assessed with weekly offs, holidays and gaps of up to 60 days disregarded, which makes the accuracy of this field a question about a death claim rather than a question about a challan.

What NCP Days Are

NCP stands for non-contributory period. An NCP day is a day inside the wage month for which the employee earned no wages, and therefore a day on which no provident fund contribution arises.

The logic is simple and it is worth stating in the direction that actually decides the answer. Provident fund is computed on wages. Wages are earned for days worked or otherwise paid for. A day with no wages generates no contribution. NCP days are how the employer tells the EPFO how many such days there were, so that a reduced contribution is understood as a reduced contribution rather than a short payment.

That last point is the reason the field exists at all. Without it, an employee earning ₹12,000 a month who is paid ₹10,800 in a particular month looks, on the return, like an employee whose employer under-remitted. The NCP figure is the explanation, and it converts an apparent shortfall into a documented one.

Two consequences follow from the definition and they cover most of the confusion in this subject.

The first is that NCP days are about wages, not about attendance. An employee can be absent for ten days and have zero NCP days, because the absence was paid leave. An employee can be present every working day and still have NCP days, if part of the month fell outside their employment. Attendance is the input. Wages are the test.

The second is that the count belongs to the wage month, not to a working calendar. A 31-day month has 31 days available to be NCP days. A February has 28. The field is not capped at 26 and it is not expressed in working days, whatever a payroll convention elsewhere in the same organisation might use.

Where NCP Days Sit in the ECR

The electronic challan cum return is the monthly filing that carries both the member-level detail and the payment. Each member occupies one line, and the line has eleven fields.

Field 10 is the one this article is about. Three properties of it cause most of the filing errors.

It takes whole numbers only. A half-day of unpaid absence has to be resolved into a whole number before the file is built, and the decision about which way to round has to be a policy rather than an improvisation, because rounding down consistently across a few hundred employees is a systematic under-report.

It is not validated against anything. The portal will accept an NCP figure of 4 on a line whose wages show a full month, and it will accept 0 on a line whose wages are plainly a fraction of the usual figure. There is no cross-check between field 10 and fields 3 to 6. Nothing objects, which is why wrong NCP days survive for years.

It is not derived by the portal. Whatever your payroll software puts in field 10 is what gets filed. If the software takes it from a leave register rather than from the paid-days figure that produced the wages on the same line, the two can disagree, and it is the wages that the employee's passbook will reflect while the NCP figure is what an examiner reads.

The return, with the contribution, is due by the 15th of the following month. There is no grace period; interest runs from the sixteenth. The wider calendar sits in our payroll compliance checklist.

The Arithmetic

The formula is total days in the wage month less paid days.

What follows the count is the part worth working through, because the reduced wage figure has to be produced consistently with it.

Take an employee whose monthly wages are ₹12,000, below the ceiling, with three days of unpaid leave in a 30-day month.

In a full month the employee's contribution would have been ₹1,440, so the three days cost ₹144 of contribution on the employee's side and the same again on the employer's.

Now the case that surprises people. Where an employer restricts contributions to the ₹15,000 statutory ceiling, the ceiling is prorated too. It is not a floor and it does not survive the absence.

A payroll that reports EPF wages of ₹15,000 and NCP days of 3 on the same line has contradicted itself, and it has over-contributed relative to the wages actually paid. This is common and it is usually the result of the ceiling being implemented as a fixed value rather than as a cap applied after proration.

The ₹15,000 ceiling itself was re-notified on 29 May 2026 under Chapter III of the Code on Social Security, 2020. It was given fresh legal backing under the new code and it was not raised. It has been ₹15,000 since September 2014, and the repeated reports of a move to ₹21,000 or ₹25,000 remain proposals.

What Is Not an NCP Day

More errors come from over-reporting NCP days than from under-reporting them, and every one of them comes from treating a paid day as unpaid.

Paid leave is not an NCP day. Casual leave, earned leave, sick leave and any other leave for which salary is paid all carry wages, so they carry contributions. An employee who takes twelve days of earned leave has zero NCP days for that month. This is the single most common error in the field and it usually comes from a payroll that reads a leave register instead of a paid-days figure.

Weekly offs are not NCP days. A Sunday is a day the employee is paid for. It stays paid whether or not the surrounding days were.

Paid holidays are not NCP days. National and festival holidays are paid days.

Maternity leave under the Maternity Benefit Act is not an NCP day, because maternity benefit is paid. This one causes real harm when it is got wrong, because it converts a protected absence into a gap in the employee's contribution record.

The genuinely hard case is a spell of unpaid absence that spans a weekly off. An employee is absent without pay from Thursday to Monday. Thursday, Friday, Saturday and Monday are clearly unpaid. What about the Sunday in the middle?

Practice divides here, and the honest answer is that it depends on your own leave rules rather than on anything the EPFO has published. If your policy treats a weekly off falling inside a spell of unpaid absence as unpaid, it is an NCP day and the wages you paid should reflect that. If your policy pays it, it is not. What is not defensible is having no policy, because then the answer varies by whoever runs the month, and the same employee gets different treatment in March and in June.

The test that resolves it every time: did you pay the employee for that day? If yes, it is not an NCP day, whatever the leave register says. Get your leave rules written down first and the ECR field follows. Our guide to leave policy requirements under Indian labour laws covers what those rules have to contain.

The Mid-Month Joiner and Leaver

This is where competent people disagree, and any article that gives you one answer without telling you that is doing you a disservice.

An employee joins on 18 September. September has 30 days. She is paid for 13 of them. What goes in field 10?

The first position is 17. The formula is total days less paid days, 30 less 13 is 17, and the days before she joined were days on which she earned no wages, so they are non-contributory by definition. This is the arithmetically consistent reading and it is what most payroll software does by default.

The second position is 0. The argument is that NCP days exist to explain an absence during employment, and the days before a person was employed are not an absence. Practitioners who take this view point out that the EPFO's pension service computation runs from date of joining to date of leaving, so the pre-employment days are already excluded by the dates, and reporting them again as NCP days double-counts. On this reading, a joiner and a leaver should both show 0.

Both are argued in practice and neither has been settled by a published EPFO clarification that resolves it for all cases. Here is what to do about that.

Report the joining and leaving dates correctly. This matters more than the NCP figure and it is the thing that actually drives the record. A date of exit that is never marked is the most damaging error in this whole subject, because the employee cannot withdraw and the account stays live.

Then pick one of the two positions, write it down, and apply it to joiners and leavers alike. The failure that causes real problems is not choosing the less common answer. It is choosing 17 for joiners and 0 for leavers, which is what happens when nobody decides and two different people configure the two cases. That produces a record where arriving and leaving are treated differently, and it is not defensible on either theory.

Then make sure the wages on the same line agree with whatever you chose. A line showing 13 days of wages and 0 NCP days is at least internally coherent under the second reading. A line showing a full month of wages and 17 NCP days is coherent under neither.

If you want a single recommendation: report 17, because it follows the formula the field is defined by, and because a figure derived from paid days can be reproduced by anybody who looks at the payslip. The second position depends on an inference about how a different calculation treats the same period, and inferences are harder to defend at an inspection than arithmetic is.

The leaver is the same problem in reverse and it is worth working through, because this is where the inconsistency usually shows up. An employee resigns with a last working day of 12 November. November has 30 days. She is paid for 12 of them.

Under either reading the wages are the same. What differs is the day count beside them, and the only combination that is wrong under both is 12 paid days reported with 0 NCP days for the joiner and 18 for the leaver, or the reverse. Pick one row and use it for both directions.

The date of exit is the field that actually matters on this line, and it is separate from the NCP count. Mark it in the month the employee leaves. An account with no date of exit stays live, the member cannot withdraw, and the first you hear of it is usually a phone call from a former employee some months later asking why their claim was rejected.

One related convention deserves a mention because it appears constantly in contract labour payrolls. Where wages are conceived as a daily rate over a 26-day month, teams sometimes compute NCP against 26 rather than against the calendar. The field is a calendar-day field. A 26-day basis produces a number that cannot be reconciled to the month and it is the reason some ECR lines show NCP days that exceed the days actually unpaid.

What NCP Days Actually Change

Four, and they get worse as the list goes on.

The contribution for the month. Covered in section 3. It is arithmetic and it corrects itself if you fix the wages.

The employee's passbook. A month with NCP days shows a smaller credit. Employees notice this and ask, and the answer is a sentence: you had unpaid days, so wages were lower, so the contribution was lower. If your payslip shows paid days, the conversation ends there. If it does not, add it; our guide to the payslip format in India covers what else belongs on it.

Pensionable service. The Employees' Pension Scheme counts months in which a contribution was actually made. A month with some NCP days still counts, because a contribution was made. A month in which wages were nil, and therefore no contribution arose, does not. Pension eligibility requires ten years of contributory service, so a member with several nil months across a career reaches ten years later than their employment dates suggest. This is not a small effect for anybody who has taken long unpaid leave, and it is invisible until they claim.

A death claim under the insurance scheme. This is the one that changed in 2026 and it is the reason this field deserves attention it has never had.

The Employees' Deposit-Linked Insurance Scheme, 2026 was notified under the Code on Social Security and took effect on 29 June 2026. The assurance benefit is not less than ₹2.5 lakh and does not exceed ₹7 lakh. Where a member dies without having rendered twelve months of continuous service and with an average balance below ₹50,000, a minimum benefit of ₹50,000 is payable.

The 2026 scheme changed how continuous service is assessed, and it changed it in the direction of the family. A gap of up to 60 days between two spells of employment is now disregarded. Saturdays, Sundays, declared weekly offs, and national, gazetted, state and restricted holidays are not treated as a break in service. Service across those is treated as continuous.

Set that against section 4. A payroll that reports weekly offs and holidays as NCP days is recording, month after month, a version of that employee's service that is more broken than the scheme now says it is. The contribution consequence of that error is small. The consequence at a claim, for a member who dies inside their first year, is the difference between a family receiving an assurance benefit and a family being told the service was not continuous. That is not a challan problem. Our note on EDLI covers the scheme itself.

There is a fifth consequence that sits slightly outside the scheme and catches people at withdrawal.

Provident fund withdrawn after five years of continuous service is not taxable in the member's hands. Withdrawn before that, it is. Continuous service for this purpose is measured across employments where the balance was transferred rather than withdrawn, so an employee who moves jobs and transfers their account keeps the clock running. Long nil-contribution months do not by themselves reset that clock, but they are the same records an examiner reads when the question is whether service was continuous, and a member whose history is littered with nil months for what were actually paid weekly offs has a harder conversation than the facts warrant.

The four consequences, in one place.

Look down the last column. Three of the four surface at a moment when the record can no longer be corrected, which is the argument for the controls in section 8 rather than the corrections in section 7.

How Wrong NCP Days Are Found and Corrected

They are almost never found by the system, because nothing in the filing chain checks them.

The portal accepts the figure. The challan clears. The passbook updates with the contribution, not with the day count. The employee sees a smaller credit and either does not look or assumes it is right. There is no rejection, no notice, and no reconciliation report that surfaces it. It is found at an exit, at a claim, or at an inspection, which are the three worst times to find anything.

So finding them takes a deliberate exercise, and there are three checks worth running.

Reconcile field 10 against paid days, for every line. Paid days plus NCP days should equal the days in the wage month, for every employee, every month. This is a one-line query against your own payroll data and it should return nothing. If it returns anything, those lines were filed with a day count that contradicts the wages on the same line.

Look for NCP days on lines with full wages. These are the over-reports, and they are usually paid leave or weekly offs being counted. They cost the employee service record and they cost you nothing, which is why nobody notices.

Look for zero NCP days on lines with reduced wages. These are the under-reports, and they look like short remittances to anybody examining the return.

Correcting a past month is the unglamorous part. There is no self-service amendment for a filed ECR line, so a correction goes through the regional office with supporting records: the muster roll or attendance record for the period, the wage register, and the payslips. Whether it is entertained depends on how far back it goes and on the office. This is why the controls in the next section are worth more than the corrections in this one.

The exception worth knowing is a date of exit that was never marked. That one you can and should fix immediately, because the employee cannot withdraw until it is done, and it is the single most common reason an ex-employee comes back to a former employer months later.

The Controls That Keep NCP Days Right

None of these four takes long.

Derive field 10 from paid days, not from a leave register. The paid-days figure already exists, because it is what produced the wages on the same line. Deriving the NCP count from anything else creates a second source that can disagree with the first. If your payroll software offers both, use the one that comes from the payroll, not the one that comes from leave.

Write down the weekly-off rule. One sentence, covering whether a weekly off inside a spell of unpaid absence is paid. Apply it in the leave policy and let payroll follow it. Without this, the answer varies by month and by whoever is running it.

Make the exit gate happen before the payroll cut-off, not after. Date of exit marked, final NCP days computed, settlement flagged. An exit processed after the cut-off produces a leaver who is paid a full salary the following month and an account that stays open.

Run the reconciliation from section 7 as a standing monthly report, not as an investigation. It belongs on the standing monthly list alongside the other comparisons in our piece on the payroll reports HR teams need, not on a list of things to look into when somebody complains. Paid days plus NCP days equals days in the month. It is a comparison between two records that were produced separately, which is the only kind of check that finds an error that looks correct.

One more thing, and this one is about ownership. This field is usually nobody's job. Attendance belongs to HR, the contribution belongs to payroll, and the day count sits between them, which is how it ends up being whatever the software defaulted to. Give it to whoever signs off the ECR, and make the reconciliation above the thing they sign off against rather than the challan total, because the challan total will reconcile perfectly on a return whose day counts are all wrong.

The structural version of all four is to keep attendance, leave and payroll on one record, so that paid days is a single number instead of three that agree most of the time. That is what our attendance management software, leave management software and payroll management system are built to do together, and it is why the reconciliation above is a query in that setup rather than an exercise.

Questions People Ask

What are NCP days in PF?

NCP stands for non-contributory period. NCP days are the days in a wage month for which an employee earned no wages, so no provident fund contribution arises for them. The employer reports the count as a whole number in field 10 of the monthly electronic challan cum return, which tells the EPFO that a lower contribution reflects lower wages rather than a short payment. The test is whether the employee was paid for the day, not whether they attended. Paid leave, weekly offs and paid holidays are all paid days and none of them is an NCP day.

How do you calculate NCP days?

Total days in the wage month less paid days. A 31-day month in which an employee had three days of unpaid leave gives 31 less 28, which is 3 NCP days. The count is on calendar days of the wage month, not on working days or on a 26-day basis, so a February has 28 days available to be NCP days and a 31-day month has 31. Only whole numbers are accepted, so a half-day of unpaid absence has to be rounded under a written policy rather than case by case.

Are weekly offs and holidays counted as NCP days?

No. A weekly off and a paid holiday are days the employee is paid for, so contributions arise on them and they are not NCP days. This matters more since the Employees' Deposit-Linked Insurance Scheme, 2026 took effect on 29 June 2026, because that scheme expressly provides that Saturdays, Sundays, declared weekly offs and national, gazetted, state and restricted holidays are not a break in service. A payroll that reports them as NCP days is recording a service history that is more broken than the scheme itself treats it as being. The one genuinely unsettled case is a weekly off falling inside a spell of unpaid absence, which depends on whether your own leave policy pays it.

Is paid leave counted as an NCP day?

No. Casual leave, earned leave, sick leave and maternity leave are all paid, so wages arise and contributions arise with them. An employee who takes twelve days of earned leave in a month has zero NCP days. Counting paid leave as non-contributory is the most common error in this field, and it usually happens because the payroll takes the figure from a leave register rather than from the paid-days figure that produced the wages on the same line.

What should NCP days be for an employee who joins mid-month?

Practice genuinely divides. Applying the formula, an employee joining on the 18th of a 30-day month is paid for 13 days and has 17 NCP days, and that is what most payroll software reports. Some practitioners report 0 instead, on the argument that the pre-employment days are not an absence and that the pension computation already runs from date of joining, so reporting them again double-counts. Our recommendation is 17, because it follows the formula the field is defined by and can be reproduced by anyone reading the payslip. What matters more than the choice is that joiners and leavers are treated the same way, that the choice is written down, and that the wages on the line agree with it.

Do NCP days affect pension?

Yes, but only in one specific way. The pension scheme counts months in which a contribution was actually made. A month with some NCP days still counts, because a contribution was still made on the reduced wages. A month in which wages were nil, and so no contribution arose, does not count. Since pension eligibility requires ten years of contributory service, a member with several nil months reaches ten years later than their employment dates suggest. Short spells of unpaid leave have essentially no pension effect; long unpaid absences do.

What happens if NCP days are reported wrongly?

Nothing, immediately, which is the problem. Field 10 is not validated against the wage fields on the same line, so the portal accepts a figure that contradicts the wages next to it. The challan clears, the passbook updates and there is no rejection. The error surfaces at an exit, at a death or withdrawal claim, or at an inspection. Correcting a filed month has no self-service route and goes through the regional office with the muster roll, the wage register and the payslips in support, so the monthly reconciliation is worth considerably more than the correction process.

Does the ₹15,000 ceiling change when there are NCP days?

Yes, and this catches a lot of payrolls. Where contributions are restricted to the ceiling, the ceiling is prorated for NCP days like any other wage figure. An employee on ₹30,000 with three unpaid days in a 30-day month has EPF wages of ₹13,500, not ₹15,000. A line reporting ₹15,000 of EPF wages alongside NCP days of 3 contradicts itself and over-contributes relative to the wages actually paid. This usually happens when the ceiling is implemented as a fixed value rather than as a cap applied after proration.

Do NCP days affect PF withdrawal or its taxability?

Not directly. Withdrawal is governed by the balance and by the date of exit being marked, and a month with NCP days simply carries a smaller credit. The indirect effect is on continuous service. Provident fund withdrawn after five years of continuous service is not taxable, and service carries across employments where the balance was transferred rather than withdrawn. Nil-contribution months do not by themselves reset that, but they are part of the record that gets read when continuous service is assessed, so a history showing nil months for what were really paid weekly offs makes a straightforward case look complicated. The field that actually blocks a withdrawal is not NCP days at all. It is a date of exit that was never marked.

Where are NCP days shown in the ECR?

Field 10 of the eleven fields on each member line, after the contribution figures and before refund of advances. The return is due by the 15th of the following month, with no grace period. Nothing in the portal derives or checks the figure, so whatever your payroll software places there is what gets filed and what an examiner later reads.

Where This Leaves You

The reconciliation is the place to start, and it will take longer to explain than to run.

Run the reconciliation. Paid days plus NCP days should equal days in the wage month, for every employee, on every line you have filed. It is one query and it should return nothing. Whatever it returns was filed with a day count that contradicts the wages beside it.

Check whether weekly offs and paid leave are being counted. If your NCP figure comes from a leave register rather than from paid days, they probably are, and the 2026 insurance scheme has made that a more expensive habit than it was.

Decide the joiner and leaver convention and write it down. Either answer is arguable. Using one for joiners and the other for leavers is not.

NCP days stay wrong because nothing objects to them. There is no rejection, no notice and no report that surfaces the contradiction, so the only thing that finds an error is a deliberate comparison against a record produced separately. That is easy when attendance, leave and payroll sit on one system and awkward when they sit on three, which is the whole argument for our payroll management system and the HR management software around it. Book a demo and bring a month with a long unpaid absence in it, because that is the month that shows whether the two records agree.

Related reading: how to calculate payroll in India, the payroll compliance checklist, common payroll compliance mistakes, and attendance compliance under the labour codes.

Sources

• Ministry of Labour and Employment, labour.gov.in. The Employees' Provident Funds Scheme, 2026, Employees' Pension Scheme, 2026 and Employees' Deposit-Linked Insurance Scheme, 2026, notified under the Code on Social Security, 2020 and effective 29 June 2026, and the ₹15,000 wage ceiling notified on 29 May 2026 under Chapter III of that Code.
• Employees' Provident Fund Organisation, epfo.gov.in. The electronic challan cum return format and its member-level fields, contribution rates, and the return due on the 15th of the following month.
• Code on Wages, 2019, enacted text on India Code. Section 2(y) on the definition of wages, which is the base the contribution is computed on.
• EPFO insurance scheme, epfindia.gov.in. The assurance benefit range and the continuous service provisions under the deposit-linked insurance scheme.

Worked examples state their assumptions and were computed rather than estimated. Where practice on a point is divided, this article says so. Verify the current position on the EPFO portal before configuring a return.