Guide
Full and final settlement, step by step
By the Capstan team at PeopleCap · Last updated 18 August 2026 · About 7 min read
A full and final settlement is the last piece of arithmetic between a company and someone who used to work there, and it is the piece most likely to end badly. Not because it is hard, but because it is the first moment anyone checks whether the record was kept properly. Every loose end from three years of employment arrives at once: the leave balance nobody reconciled, the expense claim that was approved in a chat message, the salary revision that was agreed verbally in April, the laptop that went home during a lockdown.
This guide sets out what a settlement covers, the order to run it, who owns each step, and how to make it uneventful. It describes no statutory rate, deadline or threshold, because those vary by country and by state and change over time. Where a number is required, that number belongs to your payroll partner or a qualified local adviser.
What a settlement actually is
It is a closing of accounts in both directions.
Owed to the employee typically includes salary for the days worked in the final period, any leave balance the policy or the law says is encashable, approved but unpaid reimbursements, variable pay or commission that has been earned under its own rules, and any statutory lump sum that becomes payable on exit in that jurisdiction.
Owed to the company typically includes recovery for notice not served, where the contract provides for it, any outstanding salary advance or loan, the cost of company property not returned, and anything else the appointment letter says is recoverable.
The net of the two is the settlement, and the statement showing how it was reached matters as much as the payment. A person who receives an amount with no breakdown will assume it is wrong, and they will often be assuming correctly, because a settlement produced without a statement is usually a settlement produced without a check.
The order to run it
Settlements go wrong when finance starts computing before HR has finished confirming. Run it in this sequence.
1. Fix the last working day. Everything else is calculated from it. Record the resignation or termination date, the notice served, and the agreed last working day as three separate facts, because they are frequently not the same date and the difference is exactly what the notice recovery turns on.
2. Freeze and confirm the leave balance. Send the employee their balance and get an acknowledgement before you compute anything. This single step removes most settlement disputes. If your system shows employees their own balance continuously, there is nothing to confirm, because they have been watching it for two years.
3. Close attendance and count the days. Payable days, loss of pay days, and any overtime in the final period. This is the input your payroll partner needs and it is a day count, not an amount. The payable days calculator does the arithmetic for one person if you are still doing this by hand.
4. Sweep reimbursements. Ask explicitly whether anything is outstanding, set a cut-off, and approve or reject what comes in. An expense claim submitted after the settlement is paid is the most common reason a closed settlement gets reopened. If you run an expenses module, the pending queue is the sweep.
5. Collect assets and close access. Both, and log both. The value of unreturned property is a settlement line, so this has to happen before the number is finalised, not after. Access removal is a security step with its own deadline and should not wait for finance. Asset Management tracks what was issued to whom if you want that answer to be a lookup rather than a memory.
6. Compile the inputs and hand them over. Day counts, confirmed balance, compensation components with their effective dates, approved reimbursements, recoveries and their basis. Every line traceable to where it came from.
7. Let your payroll partner compute. Gross to net, the statutory deductions and lump sums, and the tax treatment. This is their work and it should be, because the rules change and vary by jurisdiction. The division of labour is set out in why payroll should be a partner.
8. Pay, and file the documents back. The settlement statement, the final payslip, and the exit documents go onto the person’s record, not only into an email.
Who owns what
Small companies get this wrong by assuming HR owns all of it. Four functions have a step, and the settlement stalls whenever one of them is not named.
| Step | Owner | What they produce |
|---|---|---|
| Last working day, notice, leave balance | HR | The dates and the confirmed balance |
| Attendance close and day counts | HR or the manager | Payable and loss of pay days |
| Reimbursements, advances, recoveries | Finance | The approved and outstanding list |
| Asset return and access removal | IT, or whoever holds the laptop | Returned, or valued as a recovery |
| Computation, tax and statutory amounts | Payroll partner or accountant | The settlement figure |
| Statement, letters and filing | HR | Documents on the record |
Put names against those rows before your first exit rather than during it.
The documents
An exiting employee needs more than money. What they typically expect, and what a future employer or a bank may ask them for, includes the settlement statement itself, the final payslip, a relieving letter confirming the last working day and that dues are settled, and an experience or service certificate stating the role and the dates worked. Some jurisdictions add statutory forms or year-to-date tax documents.
Two rules save trouble. Agree the list before anyone resigns, so nobody is negotiating a certificate under time pressure. And generate the documents from the record rather than retyping them, because a relieving letter with the wrong last working day on it is a document the person will need to come back and have corrected, possibly years later.
The Capstan core generates letters from record fields with merge templates and files each one against the person automatically, with an audit trail. That is not a large feature, but it is the difference between an exit that produces a clean paper trail and one that produces three follow-up emails.
The dispute you are actually preventing
Look again at the three things settlements are argued about: the leave balance, the notice recovery, and a reimbursement.
None of those is a settlement problem. They are all record problems that become visible at settlement.
The leave balance is disputed because it lived in a spreadsheet only HR could see. The notice recovery is disputed because the terms were in an appointment letter nobody has opened since the day it was signed and the resignation date was agreed in a conversation. The reimbursement is disputed because approval happened in a chat thread that has since scrolled away.
A system of record fixes all three by making them boring in advance. Balances are visible to the employee continuously. Terms live on the record with the document attached. Approvals go through a workflow that logs who approved what and when. By the time someone resigns, there is nothing left to reconstruct.
That is the whole argument for holding this data properly, and it is the same argument as an HR system is a record of the past: the value shows up at the moment somebody asks a question about a date that has already gone.
After the settlement
Two things outlive the payment.
Retention. You will be obliged to keep employment and pay records for a period after someone leaves, and the period is set by law rather than by preference. Deleting a leaver’s record the week they go is not tidiness, it is a compliance failure. HR data security and compliance covers how to think about retention alongside deletion obligations.
The leaver who writes to you in 2028. Every exit adds one more person who will eventually need a payslip, a letter or a tax document from an address they no longer have. At twenty leavers a year that becomes a standing tax on whoever answers the email. Alumni Access lets a former employee fetch their own documents on their personal email, scoped to what was already theirs, which is the version of this problem that does not grow with headcount.
The short version
Fix the dates. Confirm the balance with the person. Count the days. Sweep the reimbursements. Collect the laptop. Hand clean inputs to whoever computes. Pay with a statement. File the documents on the record.
Run in that order, a settlement takes an afternoon. Run in any other order, it takes a fortnight and produces an argument.
Common questions
What is a full and final settlement?
It is the closing of accounts between an employer and a departing employee. Everything owed to the person is added up, everything owed back to the company is deducted, and the net amount is paid with a statement showing how it was reached. It usually covers salary to the last working day, any encashable leave balance, pending reimbursements and variable pay, set against recoveries such as unserved notice, advances, or unreturned company property. The statutory elements and the deadline depend on the country and often the state, so confirm both locally.
What documents should an employee receive when they leave?
At minimum, the settlement statement itself so the person can see how the number was reached, and their final payslip. Most employers also issue a relieving letter confirming the last working day and that dues are settled, and an experience or service certificate stating the role and the dates. Depending on the country there may be statutory forms or year-to-date tax documents to provide as well. Agreeing this list in advance is what turns an exit into a process instead of a negotiation.
Why do settlements get disputed?
Almost always over one of three things: the leave balance, the notice period, and a reimbursement someone submitted but nobody approved. All three are record-keeping failures rather than payroll failures. If the leave balance was visible to the employee every day of their employment, it is not a surprise on their last day. If the notice terms were in the appointment letter and the resignation date is recorded, the recovery is arithmetic. Disputes are what happen when the record only gets assembled at the end.
Does Capstan calculate a settlement?
No. Capstan holds no rate, slab, threshold or formula anywhere, and computes no statutory amount. What it does is hold the facts the settlement is built from, the confirmed leave balance, the payable and loss of pay day counts, the last working day, the compensation history with its effective dates, approved and unapproved expenses, and the assets issued, and compile them into a documented export for your payroll partner. Your partner computes the settlement and files their result back onto the record.