Intern conversion to employee

Intern conversion is an employment-record event: the same person moves from intern terms to employee or regular terms, with a dated change in role, pay, and status. It is not a second hire of a stranger, and it is not a universal Indian legal conversion process. This page does not settle stipend-versus-salary tax as law. Join-path work for someone who is truly a new employee identity stays on Dayzen onboarding. Pay calculation after the terms change sits on Dayzen payroll. The trail that holds intern and active contract workspaces, and stipend proposals, is Dayzen employee lifecycle. Do not create a second employee ID for the same human; that failure mode is duplicate employee records.

Operational guidance only. Appointment letters, intern agreements, and your issued policy set whether conversion is offered at all. This is not legal advice.

Same person, new terms, dated event

Conversion means three facts on one identity:

• The intern record already exists (name, intern classification, start, expected intern end if you had one).
• A dated decision to employ them on new terms (role, reporting line, compensation you will actually pay, work location or entity as you classify it).
• An effective date when intern terms stop and employee terms start — which may be the day after intern end, a named Monday, or another date you wrote. Effective date is not “when HR got around to typing.”

If there is no intern record, you are not converting. You are hiring. Use recruitment and onboarding. If there is an intern record and you open add-employee as if they were unknown, you will duplicate. Search first, including people who look “not active yet.”

Dayzen lifecycle includes intern and active contract workspaces and stipend proposals. Moving intern → active (or your equivalent employee classification) is the workspace change that should match the event. A stipend proposal is not a salary structure by another name; it is intern pay as you configured it. When conversion happens, you stop intern stipend terms on the effective date and start the employee structure payroll will calculate. Do not explain that shift as a tax statute on this page. Finance and your advisor own tax characterisation. HR owns that the record and the payslip inputs match the terms you issued.

What conversion is not

Not automatic because the intern calendar ended. Calendar end without an event is either exit (intern ends) or an unnamed drift. Write convert, extend intern terms (if your policy allows an intern extension as its own event), or end.

Not onboarding theatre for someone who already has attendance, a badge, and a manager. You may still collect documents you did not collect for intern tenure, and you may still run a short orientation to a new role. That is a gap list, not a second hire-to-activate novel. Onboarding’s new-joiner pipeline is for new joiners. Conversion reuses the person. If you must collect a new bank proof or a new letter accept, list those as conversion tasks on the same ID.

Not a nationwide “intern must be confirmed as employee after X months.” There is no such constant on this page. Campus programmes, stipend internships, and trainee contracts differ. Your letter owns the path.

Not a performance-appraisal product. A manager may recommend conversion. The employment event is still confirm-as-employee (or refuse and intern-end), dated, on lifecycle.

The packet on one identity

Treat conversion like a handoff, except the identity keys already exist. What must be true before you flip workspaces:

1. One employee ID. No second wizard row. If a recruiter opened a candidate because the intern applied internally, link that application to the existing person; do not activate a parallel profile.
2. New terms in writing: designation, department, manager, location/entity, employee type, compensation structure you will load for payroll, joining-as-employee effective date (even if they never left the building).
3. Documents you require for employee status that intern status did not require — your gate, not a nationwide packing list. Do not delay the event forever for papers you could have collected during intern tenure if policy already asked for them.
4. Stipend end and salary start aligned to the effective date so one cycle does not pay both as if they were two people.
5. Access and assets: intern may already hold a laptop. Conversion is not an excuse to ignore assignment records, and it is not always a new device. Update role access if the new job needs more (or less) than intern access.

Dayzen onboarding can still help when conversion includes forms you use for new hires — only if you point them at the existing employee, not a candidate clone. Prefer lifecycle + master-data update on the same row. Candidate portals are for applicants you do not already employ as interns.

Payroll inputs, without tax law

Payroll needs an employee structure on the effective date: earnings components you use for employees, statutory calculation inputs you already configure for employees, and bank details you collect. Dayzen payroll calculates (including EPF/ESI/PT/TDS components as configured). It does not file, remit, or pay the bank. It does not auto-enrol PF as a hidden conversion gift. Whether an intern stipend was in or out of a statutory scheme is a facts-and-advisor question. This article will not declare a rule.

Mid-month conversion is a proration and structure-change problem. Pointer only: joiner/leaver proration is a payroll sibling topic. Here you require that intern end and employee start are the same seam so payroll is not asked to invent overlapping statuses.

Cost centre and attendance policy may change with the new role. Change them on the event. Leaving intern cost centre on an engineer salary is how finance spends a quarter reconciling. Leave balances and attendance history stay on the same person; conversion is not a reason to open a blank attendance record. If employee leave types differ from intern types, that is a policy configuration on the same ID, not a new hire’s year-zero.

Letters and internal story

Issue the employee appointment or conversion letter from the event: old intern end, new role, new pay, effective date. Dayzen lifecycle includes employment letter templates. If they must accept, file accept on the same person. Do not send an offer as if they were an external candidate and then create them again when they “accept.”

Tell the directory the truth. Org chart and manager should match the new role on the effective date, not on the date of the cake. If the role change is future-dated, record now and apply then — mechanics on the future-dated contract article; this page only insists you do not pretend intern status after the employee effective date.

When conversion is refused

If the intern will not become an employee, intern end is an exit-shaped event: LWD as intern, access, assets, letters you issue for internships. Use the exit checklist for last-week ops and the FNF guide only if your process actually settles intern dues that way. Do not leave intern workspace forever as a kind no. Do not convert “for payroll convenience” if the decision was no — that is a false employee.

Failure modes

Symptom	Cause	What to do
Two IDs, one human	Add-employee during conversion	Search, merge/convert on the intern row; see duplicate records
Stipend and salary in one month as two lives	No effective-date seam	One identity; intern end then employee structure
Still intern in HRMS, employee on LinkedIn	Letter without workspace change	Lifecycle event; directory follows
Full onboarding pipeline restarted	Treated as stranger hire	Gap documents only; same ID
Tax debate in HR chat	Blog used as statute	Advisor; HR keeps terms and dates accurate
Intern calendar ended, nobody decided	Silence	Convert, intern-extend if you allow it, or intern-end

A conversion sequence you can staff

1. Decision dated: convert or not. Manager recommendation filed, approver named.
2. Search directory: intern ID is the ID.
3. Write new terms; employee accepts if your process requires it.
4. Collect only the document gap your employee gate requires.
5. Lifecycle event: intern workspace → employee/active; stipend terms end; employee structure starts; effective date.
6. Payroll cycle uses that seam. Access updated for the new role.
7. Letter generated from the same facts. Org and manager as of effective date.

Conversion is one person, new terms, a date. Dayzen has intern and active workspaces and stipend proposals. Payroll calculates the new structure; it does not legislate stipend tax. Onboarding does not get a second human. If you needed a second employee ID, you did not convert — you duplicated.

Keep lifecycle as the event home. Keep onboarding for true new joiners and for forms you deliberately reuse on the same row. Keep payroll as calculation after the structure exists. Keep duplicate-records as the warning on the wizard. Stop this article before it becomes a trainee-statute essay or a tax explainer. The operating test: one ID before and after, intern terms ended on a date, employee terms started on that seam, and nobody can find a ghost profile created “just for salary.”