Full and final settlement in India: meeting the two-day wage rule

Why a missed deadline costs more than the money

The two-day wage rule has been in force since 21 November 2025, when the four labour codes took effect. Before that, the same two-day idea sat in the Payment of Wages Act, 1936, but only where the employer ended the job. The new wording also covers resignation, which is how most salaried people leave. For a business owner, that means the final salary run is no longer a monthly task that can drift. It is a short, fixed clock that starts when someone walks out.

The direct cost of a miss is usually small in rupees. The bigger costs come from rework and from the time staff spend chasing. A finance executive rebuilds leave balances from a register. A manager checks attendance that was already closed. A former employee calls twice, then escalates to a labour office. Each of those steps is a cost, even when the final amount is correct.

Gratuity is where the money is larger. The Act makes gratuity payable after five years of continuous service, and it applies to establishments with ten or more employees. A rough illustration helps. Take basic plus dearness allowance of 40,000 rupees a month and six completed years. The formula gives 15/26 x 40,000 x 6, which is about 1,38,462 rupees. If that is paid 30 days late, simple interest applies. Guides commonly quote 10 per cent a year, but the Act ties the rate to the one the central government notifies, so check the current notified rate. At 10 per cent, the interest on that one payment for 30 days would be roughly 1,138 rupees. The interest is small. The bigger risk is a dispute that goes to the Controlling Authority.

The four payments and their clocks

Most owners treat the final settlement as one number. The law treats it as several separate obligations with separate clocks. Splitting them is the single most useful change you can make.

Two points in that table need care. First, the Code caps total deductions in any wage period at 50 per cent of wages, and it only allows deductions from a closed list. A notice-pay recovery or a laptop charge must fit that list and the contract. If it does not, do not net it off in the final payslip. Ask your labour adviser to confirm the basis before you deduct.

Second, EPF needs the employer to do its part first. Several EPFO guides say a Form 19 claim is rejected if the last employer has not updated the exit date. Those guides also say the employee generally needs to be out of covered employment for two months before final settlement. One 2026 guide describes a 12-month waiting period under newer EPFO rules. The sources do not agree on that point, so check the current rule on the EPFO portal before you tell staff how long they must wait.

Where the two days start: a real disagreement

Legal commentators do not agree on the starting point. The text of Section 17(2) refers to the day of removal, dismissal, retrenchment or resignation. Read literally, a resignation letter handed in on a Monday would start the clock that day, even if the employee then serves a 60-day notice period. Most commentators reject that reading, because wages for the notice period have not yet been earned. The more common view is that the clock runs from the date the employment actually ends, which is the last working day.

A second question is scope. Some commentators read the rule as covering only wages earned up to the last working day. Others read it as covering the whole full and final package. The Code's wording does not settle that clearly, and at least one compliance note says the Government has not yet defined it.

The safe working rule is this. Treat the last working day as the start of the clock. Pay everything that is clearly wages within two working days of that date. Pay gratuity and EPF support items within their own timelines. Keep a dated record of every step. If you choose a stricter reading, you will rarely lose money, but a looser reading can leave you exposed if a former employee disputes it.

Manual process and automated process compared

The automated column does not remove the approval. It moves the person's time from typing and searching to checking and signing. For most owners, that is the real gain: the same person does the same final check, but in minutes instead of a day of reconstruction.

How to automate the exit, step by step

1. Write the exit map on one page. List each component from the table above, its deadline, its owner and the document that proves it. A shared Google Sheet or Microsoft Excel file is enough to start.
2. Create one trigger. Use a fixed resignation form, or a rule on the HR mailbox, that opens an exit case the day a resignation is accepted and records the last working day. The case becomes the single place where every later step is logged.
3. Connect the attendance and leave data. If you use Tally Prime, Zoho Payroll or another HRMS, schedule an export of attendance and leave balances for the last working day. If leave still sits in paper registers, scan the registers with an OCR tool such as Google Document AI or a similar service, then have a person check every figure before it enters the calculation. OCR on handwriting is error-prone, so treat it as a first pass.
4. Build the calculator once, then test it. Use a locked template with the statutory formulas for wages, leave encashment and gratuity. Run it against three past exits and compare the output with what was actually paid. Only use it live after the figures match.
5. Let an LLM draft, not calculate. A large language model can turn the approved figures into a plain-language letter that explains each line. It should never compute the numbers. Its draft goes to a person who checks every amount against the statement.
6. Add an approval gate. Finance approves the wages statement. HR approves the EPF and gratuity tasks. The system records both approvals with a date.
7. Connect payment. Prepare the bulk transfer file for your bank from the approved statement, so the payment step is one upload rather than dozens of single transfers. Reconcile the batch the same day.
8. Send the statement through the channel the employee uses. Many Indian staff read WhatsApp first. The WhatsApp Business Platform API can send a pre-approved template message with the PDF statement attached. Message templates need approval from Meta before use, so plan for that delay. Email is the fallback and the written record.
9. Schedule the slow clocks. Gratuity has a 30-day limit, so set reminders at intervals you choose, with the final one well before day 30. EPF needs the exit date on the portal, so make that a task on the same day the exit is recorded.

The exit workflow with cut-offs

The table below uses internal cut-offs that you set. They are not legal deadlines, except where the law is named. Adjust the times to your payroll calendar, but keep the order.

What breaks, and how to prevent it

Most failures come from data, not from the software. Leave balances are often wrong before anyone leaves, and the calculator simply repeats the error faster. Start by clearing the leave register once a year, not on exit day.

• Attendance changes after the lock. Prevention: set a written rule that corrections after the lock need a manager's sign-off and a reason, and log them.
• Leave encashment calculated on the wrong base. Prevention: write the base (basic, or basic plus dearness allowance) into the template and into each employment letter, then keep it consistent.
• Notice recovery that does not fit the law. Prevention: check each recovery against the closed list and the contract before it appears on the statement.
• EPF exit date missing. Prevention: make the update a same-day task, and have HR check the status before the employee applies.
• Contract workers. If a contractor employs the people on your site, the principal employer can be liable when the contractor delays wages. Put the exit timelines into the contractor agreement and ask for proof of payment.
• Rules still changing. The Ministry of Labour and Employment has notified central wage rules for 2026, and states are at different stages. Review the rules for your state each quarter, and keep the template's settings in one place so you can change them quickly.

One limit should be stated plainly. Automation cannot decide whether a deduction is fair, whether a notice period should be waived, or how to answer a former employee who disputes a figure. Those are judgement calls, and they belong to a person with authority to make them.

When not to automate

Automation is not worth building if you have only a handful of exits a year and each one takes a single person under an hour with a checklist. In that case, a well-kept template and a signed checklist will do more than a new system. The same applies if your employment contracts are unusual, if you have active disputes, or if your attendance data is so poor that the first step is cleaning it, not automating it. A business in litigation over gratuity should involve its lawyer before any workflow change.

Be careful with approval steps too. Do not let a workflow approve a waiver of notice pay or a write-off of an advance. Those decisions need a named person, and the system should show who made them.

What it takes, in time rather than price

Most of the effort is not in connecting software. It is in agreeing the rules. Someone who knows the contracts and the statutes has to sign off the exit map, the base for each calculation and the list of permitted recoveries. Expect that step to take longer than the build.

The data clean-up comes next. Reconcile leave balances for the people most likely to leave soon. Check that every employee has a verified UAN, an Aadhaar-linked number and a bank account in the right name. Then run the new process alongside the old one for the first two or three exits, and compare the figures line by line. Only switch off the manual check when the figures match for several exits in a row.

Once running, the work shifts to a short monthly review of the rules, the templates and any exits that needed correction. That review is where a business keeps the process compliant as the rules change.