Prepare NAPSA onboarding through 3 distinct records: the authorised person’s iCARE profile, the employer account and each employee’s Social Security Number. Connecting those records correctly is more useful than treating “registration” as a single completed task. Check what already exists before creating another profile or employer application.
NAPSA’s opened guidance describes iCARE and also retains a separate registration FAQ referring to eNAPSA. This guide distinguishes them instead of combining their screens into an invented sequence. It covers preparation and recorded outcomes, not contribution rates, statutory deadlines or a claim that an employer application has been submitted or approved.
How do personal profiles, employer accounts and employee SSNs differ?
The official iCARE FAQ describes a platform for members and employers to manage accounts, contributions, benefits and compliance. It says someone managing contributions must attach an employer account to their profile. A personal login therefore serves a different purpose from the employer record it can administer. Keep both identities visible in your onboarding notes.
For a new employer account, the FAQ describes logging in and selecting Register an Employer Account, filling in the details and receiving a reference after approval. Record the stage actually reached. Opening the form, completing it and receiving an approval-related reference are not interchangeable events. Do not label a partially prepared application “registered” in an internal handover.
For existing employer accounts, the FAQ describes an attachment option using the employer number and mobile OTP where the account is not on eNAPSA. That is a specific documented option, not evidence that every migration situation uses the same steps. If your account history does not fit it, retain the difference and ask NAPSA which route applies before creating a duplicate employer.
Each authorised user needs their own iCARE profile to manage the employer account, according to the same FAQ. Build the access arrangement around named people rather than a password shared across the payroll team. Identify who is authorised, which employer they manage and who maintains that responsibility when a colleague leaves or changes role.
Employee onboarding is separate again. NAPSA says employees with SSNs can receive contributions on their behalf without having iCARE profiles. Do not make creation of every employee’s online profile an invented prerequisite for the employer’s contribution workflow. Check the employee identifier and the employer relationship rather than judging readiness only by who has a login.
For an individual applying for an SSN, the FAQ describes using an ID such as a passport or NRC, completing KYC and security questions, then choosing Apply for SSN. It describes an OTP and the SSN appearing on screen and by SMS. Treat those as the authority’s documented steps; this article has not tested an individual application or observed an issued number.
The older-style registration FAQ lists a company registration certificate, proof of business address and contact details of the authorised person. Those are useful preparation records. Its screen sequence explicitly refers to eNAPSA, so do not present it as a tested iCARE walkthrough or assume that the document list resolves every entity-specific question.
Use this original identity map during preparation. Keep the detailed identifiers restricted rather than copying them into general project notes.
| Record | Belongs to | Evidence to establish | Common confusion to avoid |
|---|---|---|---|
| iCARE profile | Named person | Correct identity and controlled access | Assuming it is the employer registration |
| Employer account | Employing organisation | Existing number or actual application outcome | Creating another account because access is missing |
| Authorised access | Person acting for employer | Named authority and attached account | Treating a shared password as authorisation |
| Employee SSN | Employee | Correct identifier for the person | Requiring an online profile where the FAQ does not |
| Onboarding exception | Responsible team member | Missing record and next action | Hiding unresolved cases in a “complete” list |
What should the employer check before calling onboarding complete?
Prepare an employer record sheet containing the registered name, organisation reference, address evidence and authorised custodian. Match it against the documents you intend to use. If the names or references differ, record the discrepancy. Do not edit an official document to make the form appear consistent or treat a website’s trading presentation as a replacement for the registered record.
Review the mobile contact used for account access. The iCARE FAQ says that where the mobile number on the employer account is not working, the person should visit a NAPSA office with a letter requesting an update to enable OTP functionality. That makes access continuity a practical onboarding dependency, not a detail to leave until the usual custodian is unavailable.
Keep the distinction between a profile-creation reference and an employer outcome. NAPSA describes a reference by SMS and email after submitting profile creation and a confirmation after approval. The employer-account answer also refers to an approval-related reference. Retain the actual message and its context instead of inferring which process a bare reference number belongs to.
Check the employee list against identifiers already held through an authorised business process. Flag an absent SSN, an inconsistent name or uncertainty about the correct record. The exception should name the issue and responsible follow-up, without exposing unnecessary personal information. This is a preparation control, not a claim that a particular employee is eligible or already registered.
Build a small exception register with columns for record type, problem, evidence requested, owner and next action. For example, a fictional employee record might have a missing SSN while the employer account is already attached. Keeping those problems separate prevents the team from reopening employer registration to solve an employee-identifier issue.
Retain actual approvals and correspondence in the controlled record. If the platform cannot be accessed or a message is unclear, label the result unresolved. A screenshot of the login page does not prove account attachment, and a prepared employee spreadsheet does not prove that contributions were submitted. Record only what was observed.
Plan a handover for authorised access and record maintenance. The next operator should know the employer account involved, the unresolved employee cases and how to reach the proper support route without receiving somebody else’s password. Test that the responsibility is understandable while the current custodian is available.
For separate digital workflow requirements, see Spout’s web development page. Get started with a redacted description of the administrative task you want to organise. This article does not represent Spout as a NAPSA registration intermediary, and your initial enquiry should not include NRC copies, employee identifiers or account credentials.
By Spout Team. AI-assisted drafting by Codex, grounded in the linked primary sources.