What happens to SSB contributions when an employee leaves?

How SSB works for Myanmar employers

When an Insured Person (IP) leaves the company, the employer's SSB obligations don't disappear — they shift to deregistration. Within 30 days of the IP's last working day, the employer must notify the township SSB office of the separation. Contributions stop from the next pay cycle. The IP's contribution history stays linked to their SSB ID and travels with them; it does not reset, and it is not refunded.

If the leaver joins another covered employer, the new employer reuses the same SSB ID, and the contribution history continues to count toward benefit qualifying periods (e.g., the 1-year sickness benefit qualifier).

What changes vs what continues

Item	What happens on exit
Future contributions	Stop from the next pay cycle
SSB ID	Remains the IP's lifelong record; reused by next employer
Past contributions	Stay in the SSB pool — not refunded
Contribution history	Carries forward; counts toward future eligibility
Active medical access	Continues briefly per SSB schedule, then suspends until re-enrolment
Pending claims (e.g. work-injury)	Continue to be processed even after exit

Contribution rates and the wage-base cap

Item	Rate	Maximum (cap = MMK 300,000)
Employee contribution	2%	MMK 6,000 / month
Employer contribution	3%	MMK 9,000 / month
Total	5%	MMK 15,000 / month per employee

Worked example — mid-month leaver

An IP earning MMK 800,000/month leaves on the 15th. They worked 15 days, paid MMK 400,000 for the part-month:

Final-month wage paid	MMK 400,000 (above cap)
SSB wage base (capped)	MMK 300,000
Final-month employee SSB	MMK 6,000
Final-month employer SSB	MMK 9,000
Reported on next month's return	Yes; deregister within 30 days

Registration and monthly returns

• Compute final-month SSB on the part-month wage paid (cap still binds at MMK 300,000).
• File the deregistration notice at the township SSB office within 30 days of the last working day.
• Issue the IP a service certificate / wage history that confirms contribution dates — useful for the next employer.
• Settle final wages, leave encashment, and severance under ESDL alongside the SSB deregistration.
• Retain the leaver's SSB and personnel records 7 years post-exit.

Benefits SSB provides

• Medical (IP + dependants while active; brief continuation post-exit per schedule).
• Sickness cash benefit (after 1+ year of contributions).
• Maternity — 14 weeks of paid leave with cash benefit through SSB.
• Work-injury benefit (Day 1).
• Funeral grant + survivors' pension.

Common variations

• Resignation — handled the same as any other leaver.
• Termination — handled the same; ESDL severance applies separately.
• Death — funeral grant + survivors' pension claim alongside deregistration.

Common SSB mistakes

• Forgetting to deregister, leaving phantom contributions and audit exposure.
• Telling employees their contributions are "lost" — they aren't, the history carries forward.
• Withholding the service certificate, blocking the leaver's ability to transfer cleanly.

Practical workflow for HR teams

Whether the SSB obligation in question is registration, contribution calculation, a benefit claim, or a leaver event, three operational habits prevent most non-compliance issues:

1. Anchor the SSB calendar to payroll close. The 15th of the following month is non-negotiable for the contribution return at the township SSB office. Treating SSB as a payroll-close output, not a separate task, eliminates last-minute filings.
2. Reconcile the SSB register against the payroll register monthly. Joiners enrolled within 30 days, leavers deregistered within 30 days, dependant changes captured — these are the three reconciliation lines that catch most defects before they become audit findings.
3. Cap discipline. Apply the MMK 300,000/month wage cap on every Insured Person, every month, before computing 2% / 3%. Most Myanmar SSB overpayments trace back to a payroll system that runs the rate against full gross.

Payslip transparency

Show the SSB withholding line distinctly on the payslip, alongside Personal Income Tax (PIT). Employees should see the 2% line item, the wage base it was applied to, and the SSB ID. Transparent payslips reduce employee queries about take-home pay and create a clean trail for any future SSB or IRD audit. Where the wage cap binds, label the line "SSB (capped at MMK 300,000 base)" so the maths is self-explanatory.

Multi-site coordination

For employers operating across more than one township, the township SSB office for the workplace — not the corporate head office — is the operational counterparty. Maintain a per-site SSB ledger covering: employer code, township office, monthly return file location, and copy of stamped acknowledgements. Centralised SSB tracking with site-level sub-ledgers is the simplest way to reconcile a multi-site monthly return. The same logic applies for PIT remittances to the IRD office covering the workplace.

Recordkeeping checklist

• Original employer registration acknowledgement.
• Per-IP enrolment forms with stamped SSB receipts.
• Dependant registration forms — track updates for life events (marriage, birth).
• Monthly contribution returns + payment vouchers (12 per year).
• Annual SSB summary return.
• Wage / service certificates issued on benefit claims.
• Deregistration acknowledgements for leavers.
• Penalty assessments and remediation correspondence (if any).

Retention rule: at least 7 years for SSB records, aligned with the payroll-record retention requirement under the Income Tax Law and the personnel-record requirement under ESDL.

Related: SSB on resignation, SSB on termination, Registering a new employee.