How to Get an ITIN as a Non-Resident

You Need an ITIN Without the Guesswork#

Approach an ITIN with an IRS-first sequence: verify your identifier path, prepare a complete Form W-7 package, then submit by mail or in person. If you run a business of one, treat it like an operations workflow. Make one clear identifier decision, build one clean package, and skip the guessing.

The point is to reduce rework, avoid compliance errors, and know exactly when to pause and escalate.

Before you start#

• Know the scope. An Individual Taxpayer Identification Number (ITIN) is a 9-digit number the IRS issues for federal tax purposes only.
• Check identifier eligibility first. If SSN eligibility is unclear, pause ITIN prep and confirm before you file.
• Set your return path. Plan around Form 1040 or Form 1040-NR from the start so your return workflow stays consistent.
• Plan per person. If family members apply, each applicant needs a separate Form W-7.

Run the decision framework#

Use this in order. Do not move forward until each line is clear.

Step 1. Run the IRS ITIN eligibility interview. It helps you decide whether to file and takes about seven minutes. Step 2. Complete Form W-7 for each applicant. Treat names and filing details as controlled data, not draft text. Step 3. Prepare the return workflow. Leave SSN fields blank for each ITIN applicant listed on the return. Step 4. Choose your submission channel. The IRS accepts mail or in-person submission. Step 5. Apply the safe default. If a requirement feels ambiguous, pause and use Form W-7 instructions as the final check before you submit.

Example: a consultant filing in the U.S. with a spouse checks eligibility first, packages each person's Form W-7 cleanly, and submits once instead of falling into a correction loop.

If you want a deeper dive, read The Ultimate Digital Nomad Tax Survival Guide for 2025.

Do You Need an ITIN or an SSN First?#

Start with one hard rule: if you have an SSN or can get one, do not start Form W-7.

This is the most important decision in the whole process. Get it wrong and everything downstream turns into wasted effort.

Run the binary gate first#

Step 1. Check current SSN status. Confirm whether you already have a Social Security number (SSN). Expected outcome: If yes, use that SSN on your U.S. federal income tax return and stop ITIN prep.

Step 2. Check SSN eligibility. If you do not have an SSN, confirm whether you can get one through SSA using Form SS-5. Expected outcome: If you are eligible, follow the SSN path and do not complete Form W-7.

Step 3. Check if an SSN application is pending. If you already applied for an SSN, wait for the result before filing Form W-7. Expected outcome: Keep Form W-7 paused until SSA gives a final determination.

Confirm federal tax purpose before filing#

Step 4. Validate your federal tax purpose. Request an Individual Taxpayer Identification Number (ITIN) only when you need it for U.S. federal tax purposes. Expected outcome: You can clearly state the federal tax purpose for the request.

Step 5. Lock scope and apply a safe default. Treat the ITIN as a tax identifier only, not work authorization. If SSN eligibility is still unresolved after your checks, keep Form W-7 on hold until SSA determines whether you are ineligible for an SSN.

Example: a consultant gets conflicting advice online and pauses. They confirm SSN ineligibility, then move ahead with Form W-7 only after the identifier path is settled.

What Should You Prepare Before You Start?#

Prepare the full ITIN application package upfront, with Form W-7 aligned to Form 1040 or Form 1040-NR (unless an IRS exception applies), so you file once instead of fixing preventable mismatches later.

Once you clear the SSN versus ITIN gate, the next job is building the package. A clean package prevents avoidable stalls.

Build the package before you fill anything#

Step 1. Choose your return workflow first. Pick Form 1040 or Form 1040-NR when required for your filing path. Expected outcome: You can state which U.S. federal income tax return you will attach, if applicable.

Step 2. Create one Form W-7 per applicant. Each person applying for an Individual Taxpayer Identification Number needs a separate Form W-7. Expected outcome: You have one clearly labeled W-7 for each applicant.

Step 3. Stage supporting records early. Prepare proof of identity and foreign status, plus U.S. residency proof for dependents when required. Expected outcome: You can map every supporting record to the correct applicant before assembly.

Run a preflight consistency pass#

Step 4. Reconcile fields across forms and records. Match names, addresses, and applicant details across your package, then fix missing information before assembly. Expected outcome: No conflicting or incomplete entries remain.

Step 5. Check common rejection triggers before submission. Run a final pass for misspelled names, incorrect addresses, and missing information. Expected outcome: You have removed obvious data-entry issues that can cause rejections.

Step 6. Use Form W-7 instructions as your final authority. When details conflict, follow that instruction set before you submit to the IRS. Expected outcome: Your package stays consistent from prep through submission.

Example: a consultant preparing an ITIN package for a spouse catches a name mismatch during preflight. They fix it before filing and avoid a rejection cycle. If your residency position still feels unclear, settle it first with 183-Day Rule Explained: Stop the Tax Myths Before They Cost You.

How to Submit the ITIN Application Package Step by Step#

Submit your ITIN package in one controlled sequence: align Form W-7 to your return, assemble in filing order, then file only after every consistency check passes.

Prep gets you most of the way there. Submission is where last-minute errors creep in, so run it like a checklist.

Run the submission sequence#

Step 1. Complete Form W-7 and align core fields. Match names, dates, and applicant details to your U.S. federal income tax return before you move forward. Expected outcome: Your ITIN form and return read as one coherent record.

Step 2. Assemble in filing order. Attach Form W-7 to the front of the return and include all required items tied to allowable tax benefits. If you qualify for an exception to attaching a return, include the substitute documentation required for that exception. Expected outcome: Your package follows the filing path for your case, without partial assumptions.

Step 3. Run a preflight against IRS instructions. Recheck identity details, return attachment, and SSN handling on every page. Leave SSN fields blank for each ITIN applicant listed on the return. Expected outcome: You remove internal conflicts before submission.

Use a safe default when details get fuzzy#

Step 4. Pause when document authentication rules are unclear. Do not guess. Taxpayer Assistance Centers can authenticate most documents in person, but dependent school or medical records still require mailing with the package. Expected outcome: You choose the right submission path for each document type.

Step 5. Keep a full copy and a tracking log. Keep a copy of your application for your records. Then log the send date, method, and key follow-up dates for status checks. Expect status notice timing around 7 weeks, or 9-11 weeks in tax season or overseas cases; if you mailed supporting documents, IRS says they are returned within 60 days. Expected outcome: You can respond quickly if you receive an assigned ITIN notice, a correction request, or a rejection notice.

Example: a freelancer pauses when a dependent document rule looks unclear. They choose the correct handling path and avoid a preventable resubmission cycle.

Should You Apply by Mail or In Person?#

Choose mail when your ITIN application package is complete and stable, and choose in person when you want stronger document-handling confidence before submission.

At this point, the question is not preference. It is operational risk. Where are your unknowns, and which channel reduces them?

Use this channel decision rubric#

Use one rule to break ties. Pick the path with fewer unknowns today. Do not optimize for speed if your package still has ambiguity.

Follow the channel playbook#

Step 1. Confirm package readiness. Verify Form W-7 and the rest of your ITIN application package are complete and consistent. Expected outcome: You can submit without changing core fields.

Step 2. Select your channel with the rubric. Score certainty, urgency, and rework risk before you act. Expected outcome: You can explain your choice in one sentence.

Step 3. Execute mail submission when ready. Send the full ITIN application package only after final checks pass. Expected outcome: You keep your process organized.

Step 4. Execute in-person submission when confidence is the priority. Book ahead for an IRS Taxpayer Assistance Center with ITIN services and confirm scope before you go. The IRS notes appointments may take several weeks. Expected outcome: You avoid surprises at the appointment.

Step 5. Confirm support model if using a CAA. Ask how they will review Form W-7, what fees apply, and how they will coordinate with the IRS if issues appear. Expected outcome: You know who owns each next action.

Example: one freelancer mails a fully preflighted package. Another chooses an in-person path because document-handling confidence is the bottleneck.

What Happens After Submission and How Do You Recover Fast?#

Track your case in three lanes, act on the exact IRS notice you receive, and trigger a recovery checklist the moment anything breaks.

Submission is not the finish line. Your post-submit process is what keeps a small issue from turning into a multi-week detour.

Track your status lane and act fast#

Step 1. Start a status clock on submission day. Use a baseline of seven weeks for an IRS status notice, and plan for nine to eleven weeks during tax season or if you applied from overseas. Expected outcome: You follow a realistic follow-up window instead of reacting too early.

Step 2. Classify your notice into one lane. Use the first notice to route your next move.

Step 3. Watch your document return timing. If you mailed supporting documents, track the 60 day return window and update your archive when they arrive. Expected outcome: You keep a complete record for ITIN renewal and future filings.

Recover quickly and keep filings consistent#

Step 4. Use the lost ITIN safe default. If you lose your ITIN, do not apply for a new number. Expected outcome: You avoid duplicate identifier problems.

Step 5. Run an ITIN renewal path for expired numbers. Renew in person, by mail, or by submitting Form W-7 with your tax return. Expected outcome: You restore a valid identifier before it blocks filing.

Step 6. Keep return workflow consistent. Enter the ITIN in the same space where your federal tax return asks for an SSN. Expected outcome: Your federal return processing stays aligned.

Step 7. Route adjacent reporting separately. Evaluate Form 8938 and FBAR obligations as separate tracks, and file FBAR with FinCEN, not with the IRS. Expected outcome: You avoid mixing forms that follow different filing systems.

Example: a consultant receives a correction notice and fixes what the IRS asked for that same week. They log every change and keep the next filing cycle on schedule.

Common ITIN Mistakes and the Recovery Playbook#

Prevent ITIN delays by enforcing five gates: confirm SSN ineligibility, reconcile every field, limit ITIN scope to federal tax purpose, map downstream filings, and escalate early on ambiguity.

These are the repeat offenders that turn a straightforward filing into a correction cycle. Use this as a reset sequence whenever something breaks.

Run the five step recovery sequence#

1. Step 1. Stop Form W-7 work until you clear SSN eligibility. If SSN eligibility stays unclear, pause and validate your identifier path first. Restart Form W-7 only after you confirm you need an Individual Taxpayer Identification Number for a federal tax purpose.

Expected outcome: You avoid filing on the wrong track.

1. Step 2. Reconcile Form W-7 against your return field by field. Match applicant details and entries exactly. For each ITIN applicant, leave SSN fields blank on the return and attach a separate Form W-7.

Expected outcome: Your submission reads as one consistent package.

1. Step 3. Reset ITIN scope before you share it. Treat the ITIN as an IRS tax processing identifier only, not work authorization and not a general legal ID.

Expected outcome: You prevent scope drift that creates downstream filing mistakes.

1. Step 4. Map downstream filings after issuance. Check whether Schedule SE applies to your self-employment workflow, then test FBAR and Form 8938 separately because one does not replace the other. File FBAR with FinCEN, not with the IRS.

Expected outcome: You manage recurring obligations as distinct tracks instead of one blended guess.

1. Step 5. Set escalation triggers now. Escalate to an acceptance agent when application issues need IRS coordination, or involve a qualified tax professional when rules conflict, facts stay ambiguous, or a correction cycle repeats.

Expected outcome: You stop compounding risk with DIY assumptions.

Example: a consultant finds a name mismatch between Form W-7 and the return. They pause submission, reconcile every applicant line, and escalate one unresolved tax residency question before filing.

Related: The Best Bank Accounts for Freelancers in the UK.

Run the Playbook and File With Confidence#

Run this in order: clear SSN eligibility, confirm federal tax purpose, submit a clean ITIN application package, then monitor status and renewal triggers.

You have the system. Now run it once, end to end, without side quests.

1. Step 1. Confirm SSN eligibility status first. If you have or can obtain a Social Security number, stop the ITIN path. Use an Individual Taxpayer Identification Number only when you are not eligible for an SSN.

Expected outcome: You avoid filing the wrong identifier request.

1. Step 2. Confirm your federal tax purpose. Tie your filing to a clear U.S. federal tax requirement before touching Form W-7. Keep scope tight, because an ITIN supports federal tax administration only.

Expected outcome: You file for the right reason and avoid scope drift.

1. Step 3. Complete Form W-7 with per-person discipline. Prepare one Form W-7 for each applicant if a spouse or dependents also need an ITIN. Do not treat one form as a family shortcut.

Expected outcome: Your package matches IRS processing logic.

1. Step 4. Prepare Form 1040 or Form 1040-NR to match the ITIN flow. Keep return data consistent with Form W-7 and leave SSN fields blank for ITIN applicants listed on the return.

Expected outcome: You reduce mismatch notices and correction cycles.

1. Step 5. Choose your submission path based on document risk. Apply by mail if your package is complete and you accept asynchronous handling. Choose an IRS Taxpayer Assistance Center or Certifying Acceptance Agent if you want in-person document support and prefer not to mail original documents.

Expected outcome: You align process speed with document-handling confidence.

1. Step 6. Track post-submission milestones. Use seven weeks as a baseline status window, and expect nine to eleven weeks during peak season or for overseas applications. If you mailed original documents and they do not return within 60 days, contact the IRS.

Expected outcome: You catch delays early and recover fast.

1. Step 7. Set renewal and escalation guardrails. If an ITIN goes unused on a federal return for three consecutive tax years, it expires on December 31 after the third year. Escalate through an IRS ITIN service channel or an acceptance agent when eligibility or cross-border facts remain unclear.

Expected outcome: You keep non-resident tax compliance stable over time.

Example: a freelancer pauses before submission and confirms there is no SSN path. They fix one mismatched field between Form W-7 and Form 1040-NR, choose a TAC appointment, and reduce resubmission risk.