Foreign workers in South Korea can build a defensible tax filing plan by choosing a provisional filing position, collecting supporting records, and keeping unresolved issues visible before touching forms. Start with residency, income source, and rate-method assumptions, attach evidence to each one, verify current guidance and filing access early, and escalate to professional review when facts conflict or key reporting questions cannot be supported.
Use the first hour to narrow to a filing position you can defend later. Do not chase certainty you do not yet have. The safer move is to pick a working assumption, attach the records you already have, and mark the gaps before they turn into filing errors.
The material reviewed here is not detailed enough to treat every definition, rate, or residency threshold as settled. Treat those points as open items until you confirm them from substantive guidance. That is not a reason to stall. It is a reason to separate what you know from what you still need to verify.
Use status labels as draft positions, not conclusions. They help you sort the work, but they do not replace records. If you cannot show where a conclusion came from, you are not ready to file on it. That idea runs through the rest of this article: make decisions in the right order, keep the evidence visible, and escalate only when the file stops being explainable.
After the first pass, you should have three things: a draft position, an open-issues list, and a clear escalation trigger. That is enough to move forward without pretending the file is complete.
Add a confidence tag beside each assumption: High, Medium, or Low. That keeps weak points visible and helps you decide what to verify first instead of circling through the whole file again. A High tag should mean the record trail is already visible and there is no obvious contradiction. A Medium tag means the file is usable but still missing a confirmation step. A Low tag means the assumption is only holding the work in place until you verify it or hand it off.
Before you trust any page, run a quick source-quality check. If what you are seeing is mostly cookie or bot-protection text, such as cookieyes-consent, _GRECAPTCHA, or retention labels like 1 year and 6 months, stop and find actual tax guidance. It is easy to mistake page furniture for substance when you are moving fast.
Keep a short decision memo from the start. It should capture your assumptions, the records supporting them, unresolved questions, and the date you last checked each point. Update it as facts change. If core facts still conflict after this first pass, pause and get qualified cross-border advice before you move from planning into filing.
A good first hour does not solve everything. It gives you a file structure that keeps later work honest. The practical test is simple: when you open the file again tomorrow, you should be able to see what you decided, what still needs proof, and what would force you to change direction.
Forms are downstream. The real work starts with three decisions that drive them: residency assumption, income-source assumption, and rate-method assumption. Treat this as a working map, not a statement of Korean tax law. Each decision should have its own evidence note and unresolved-questions list so you can see what is solid and what is still provisional.
| Decision | Core question | Evidence to collect now | Red flag |
|---|---|---|---|
| Residency status | What status are you testing right now? | Entry and exit timeline, visa and contract dates, dated assumptions memo | You cannot explain the logic in two plain sentences |
| Income source | Which income items are you currently treating as potentially Korea-linked vs outside Korea, pending authoritative guidance? | Invoices, payer location, where work was performed, payment records | You put all revenue in one bucket |
| Rate method | If guidance presents multiple methods, which one are you testing first, and what could disqualify it? | Written reason for choice, list of missing confirmations | You choose a method before confirming terms |
This map matters because most filing rework starts the same way: someone opens a form, picks labels too early, and then tries to force the records to match. If status or sourcing is still fuzzy, pause form entry and tighten the file first. That usually feels slower in the moment, but it saves time once the return starts taking shape.
A practical sequence keeps the work grounded:
That order keeps the return anchored to evidence instead of whichever screen or worksheet you opened first. Once the map is stable, you can organize the underlying records so every later decision is easier.
Keep those three decisions visible on one page while you work. When a new document arrives, ask which decision it affects before you file it away. That turns record collection into decision support instead of admin work. It also makes it easier to see when one document matters to more than one part of the file, such as when a contract affects both status timing and income mapping.
Separate your working buckets early. This is an organization move, not a legal conclusion, but it saves a lot of cleanup later.
Before you go further, make sure you are reading actual Korean tax guidance. In this research set, some excerpts were unrelated U.S. congressional materials, so they are not a basis for Korean filing decisions. If the terminology on the page does not match the issue you are trying to solve, step back before you build anything on top of it.
Once you have the right Korean material, mirror its wording in your memo and in any advisor questions. If the terms are still vague, rewrite your own notes in plain language and state what record would settle each point. That keeps you from hiding uncertainty inside jargon and makes the next review faster and cleaner.
Operationally, these buckets can be as simple as separate tabs, folders, or ledger columns. What matters is that status issues, sourcing issues, and method-choice issues do not disappear into one running note. If all unresolved items live in the same place, they start to look equally important. When they stay in separate buckets, you can see which problem actually blocks filing and which one is just waiting for confirmation.
Residency is usually the first real fork in the road, so treat it as an evidence call, not a gut call. Keep resident and non-resident as draft positions until one is clearly supported by records.
Day count can help, but it is not the whole answer. The 183-day rule is a common signal, yet residency tests can involve more than a simple count. In practice, the useful question is not "What do I think I am?" but "What can I show from dated records if someone asks how I got there?"
That is why the status file comes before the return. If your date trail is weak, every later conclusion gets harder to defend.
Before you lock a filing position, build one reviewable file. The goal is simple: a defensible record set that someone else can follow without filling in gaps from memory.
Add a short contradiction log at the bottom of the file. If two records appear to conflict, note both records, note what differs, and assign an owner for resolution. That small step prevents silent assumptions from hardening into filing positions.
Build the file chronologically. Put the earliest dated record first and keep later changes in order, even if that feels repetitive. Chronology makes it much easier to spot the moments that matter, such as a new housing start date, an updated work agreement, or a gap where the records stop telling a clear story. If a date is missing, mark that directly rather than filling the space with a guess.
If the facts still conflict after you organize them, default to the more conservative working position and get professional confirmation before filing. It is much easier to do that now than to rebuild the logic after the return is already drafted.
Once your status position is framed, track income in a way that preserves both place and timing. Keep one ledger that shows what was earned where and when. For each payment, record the service period, payer, work location, invoice date, and payment date so the treatment stays consistent throughout the file.
When payment location and work location point in different directions, do not force an answer just to keep moving. Flag the row for review, keep the original documents linked, and leave the question visible until you resolve it. Ambiguity is manageable when it stays explicit. It gets dangerous only when it disappears into a summary sheet.
A practical check here is period integrity. The service period, invoice timing, and payment timing should tell one coherent story. If they do not, fix that mismatch before you finalize treatment. Many cross-border errors are really timeline errors wearing a tax label.
This matters most when a payment is received long after the work was performed or when an invoice covers more than one work period. In those cases, keep the original service period visible instead of letting the payment date do all the work. The goal is not to make the ledger more complex. It is to preserve enough sequence that the treatment still makes sense when you revisit it later.
Run one hard checkpoint before you file. Check your status assumptions against current guidance from the relevant tax authority and confirm that your filing channel is actually usable. Tax e-services may require identity authentication and first-time registration, so access should be verified early, not in the final week.
Use this as a gate, not as a casual review:
If any answer is no, the file is not ready. If key facts still conflict at this stage, stop DIY filing and escalate with a one-page memo that includes your status assumption, unresolved questions, and document index. That gives the next reviewer something usable instead of a loose pile of records.
One useful habit is to run this checkpoint before you enter figures anywhere final. If the status logic still feels fragile, resist the urge to keep going on the forms just to feel productive. A clean pause is usually cheaper than finishing a draft return that later has to be rebuilt around corrected facts.
Do not choose a rate path from a headline summary or gut preference. Write down the decision test first. A flat-style election can make sense in some cases, but progressive treatment may be stronger once both paths are tested against your actual facts.
This should not turn into an abstract flat-versus-progressive debate. The real question is narrower: after you test the likely upside, tradeoffs, and implementation risk, which path is stronger and easier to support?
| Path | Potential upside | Verify first | Common failure mode |
|---|---|---|---|
| Flat-style election | Targeted relief can be justified in some situations | Whether benefits continue to outweigh costs in your case | Choosing from a summary and skipping a structured benefits-versus-cost test |
| Progressive treatment | A broader-base approach can be beneficial when it reduces distortions | Whether this path gives the stronger overall outcome for your facts | Assuming it is automatically better and not testing the targeted-relief case |
If your facts are unusual, do not assume one path applies by default. Keep both open long enough to test them. A useful discipline here is side-by-side testing. Before you calculate anything, write the reason each path could fail. That makes it harder to drift toward the result you prefer and easier to explain later why one option was rejected.
Once you have that choice framed, you can turn it into a short pre-filing note instead of a last-minute judgment call.
Before filing, add a short memo to your return file. Keep it brief enough to reread quickly and specific enough to still make sense a month later.
Date-stamp the memo and recheck current guidance before filing. If material uncertainty remains, pause and get professional confirmation rather than filing on a half-tested preference.
A practical way to keep this honest is to compare the memo against the actual record set, not against your memory of the year. If the chosen path depends on facts you have not documented, the decision is not ready. If the rejected path was dropped only because it seemed inconvenient to model, reopen it long enough to show why it lost.
If you want a deeper dive, read South Korea's New Digital Nomad (Workation) Visa: What We Know.
For independent work, most preventable trouble starts months before filing, when records from different engagements get merged into one bucket. Treat each income stream as its own record from the start. One-bucket reporting feels efficient in the moment, but it is the fastest way to lose defensibility when you need to explain why different lines were treated differently.
Class A and Class B are employment income categories based on income source, with different withholding treatment, so do not force every consulting line into those labels too early. Use provisional tags until the facts are clear, then record why each stream was treated that way before year-end consolidation. The point is not to label faster. It is to keep enough detail that the label, once chosen, still makes sense.
| Monthly tag | What to capture now | Why it matters later |
|---|---|---|
| Payer identity | Legal entity paying you | Supports Class A and Class B screening for employment-income streams and keeps streams separate |
| Payment setup | How payment was made and whether payroll withholding appears | Class A is generally tied to monthly payroll withholding; Class B may not be withheld at payment |
| Working-conditions note | Brief note on actual working arrangement | Courts can assess real working conditions, not just contract labels |
| Stream ID | Separate ID per engagement, even with one client | Prevents collapsed records that are hard to defend |
Run one monthly checkpoint and keep it mechanical. If a line is tagged Class A, confirm payroll withholding appears in that month's records. If it is tagged Class B, do not assume withholding happened at payment and plan for annual self-declaration and voluntary payment. If useful, evaluate whether joining a licensed taxpayers' association fits your process, since it can remit monthly and may allow a 3% income-tax credit capped at KRW 1 million per person.
A common failure mode here is not the math. It is record collapse. Once invoices are merged and classified only at year-end, you lose the trail for why different streams were treated differently. That makes later review slow, and it also makes your own file harder to trust.
Keep a simple ledger you can actually maintain each month:
Add one more field for documentation completeness. A simple Yes or No flag shows whether each row has enough records to survive review and tells you where to focus before filing season gets busy.
If a client relationship changes mid-year, open a new stream ID instead of rewriting old rows. That preserves the history and makes the eventual classification logic much easier to follow.
It also helps to close each month with a short exception review. Look for rows still marked Review, rows with no linked support, and rows where the payment setup changed from prior months. Those exceptions are usually where classification problems start. Clearing them while the facts are still fresh is much easier than reconstructing them after year-end consolidation.
The calmest filing seasons usually come from calendar control, not from working faster in the last week. Lock your timeline early, but keep Korea filing dates marked as provisional until current National Tax Service guidance confirms them.
Start your filing folder with a date register for tax year close, filing window, and submission due date. For each line, track status as provisional or confirmed and include a last-checked date. If any key date is still provisional, pause deadline-dependent assumptions rather than building the rest of the file around an unverified calendar. That one habit prevents a lot of avoidable rework.
Use one prep sequence and stick to it unless the facts force a reset:
That order matters. If you draft the return before reconciliation and mapping are settled, every later correction ripples through the rest of the file. You end up rechecking totals, labels, and support at the same time, which is how small errors survive.
Keep one working folder as your central evidence pack with contracts, invoices, payment confirmations, and prior-year correspondence. Add a short index that maps each document to a ledger row or stream ID so you can reopen any issue without hunting through filenames.
Before submission, run these passes in order:
One more useful control is version discipline. When totals are frozen, mark the ledger version you used and keep later edits visible rather than silently replacing the old file. That way, if a difference appears during review, you can tell whether it came from a corrected payment record, a changed classification, or a calendar assumption that moved after confirmation.
The decision rule is straightforward: if any key date or status item is unverified, the file is not ready. Confirm timing, complete the review passes, and file from records another reviewer could follow without guesswork.
Related: Seoul, South Korea: The Ultimate Digital Nomad Guide (2025).
Before filing, consolidate your residency dates and evidence in one place with the Tax Residency Tracker.
If you are a U.S. person, bring the U.S. side into the plan early. Do not bolt it on at the end. That does not mean mixing the two systems together. It means using one fact set and mapping the U.S. implications early enough to avoid rework later.
Keep a simple U.S. checklist in your evidence folder and complete only what applies to your facts.
| Form or control | What it does | Practical checkpoint |
|---|---|---|
| U.S. income tax return reporting | Core U.S. return reporting layer | Confirm reportable income is captured before exclusions or credits |
| FEIE eligibility and calculation | Foreign earned income exclusion path | Verify qualifying status and day-count support first |
| Form 1116 | Foreign tax credit path | Use a separate Form 1116 for each income category and check only one category box per form |
| Potential self-employment items | Additional U.S. tax considerations may apply | Flag potential exposure early for review |
| Other U.S. information reporting controls | Additional reporting checks | Run a separate yes-or-no check and document your conclusion |
If you claim FEIE, treat eligibility as a hard gate. Under the physical presence test, you need 330 full days in a 12 consecutive month window. The days do not need to be consecutive, but each counted day must be a full 24-hour day. If you are below 330 days, the test is not met unless a waiver applies for conditions such as war or civil unrest.
Keep FEIE calculations tied to the tax year: $130,000 for 2025 and $132,900 for 2026. If you qualify for only part of the year, adjust the maximum by qualifying days. If you also claim a foreign housing exclusion or deduction, calculate that first because it reduces FEIE capacity.
If you use FTC, follow Form 1116 structure controls exactly: one income category per form, one checked category box per form, amounts in U.S. dollars except where specified otherwise, and separate country lines or columns when taxes were paid to more than one country or territory.
A clean sequence prevents a lot of rework:
The key judgment is not which method sounds better in general. It is which one holds up against your documents. If the Korea side is mapped but the U.S. side is still incomplete, stop and finish the U.S. checklist before you file either track.
A practical file rule helps here: do not create a separate fact pattern for the U.S. return. Use the same dates, same income streams, and same underlying payment records, then build U.S.-specific calculations on top. That reduces the chance that one system will describe the year one way while the other system describes it another way.
The biggest avoidable mistake here is bad sequencing. Once FEIE, FTC, and treaty ideas get mixed together after the forms are already half-built, it becomes hard to tell which conclusion came from which rule. Set the order before you file either side.
Start with the US-South Korea Tax Treaty as a scope check, then test FEIE and FTC against your records. Do not force a treaty result early. This evidence pack does not confirm specific treaty article outcomes, so keep treaty-dependent points open until reviewed. That is often the difference between a file that stays explainable and one that turns into a patchwork of borrowed conclusions.
| Decision area | What to verify first | Failure mode to avoid |
|---|---|---|
| FEIE qualification | 330 full days in a 12 consecutive month window | Counting days that are not full 24-hour days |
| FEIE amount control | Correct year cap for the filing year | Using the wrong annual cap |
| Housing sequencing | Figure foreign housing exclusion or deduction before FEIE | Overstating FEIE room by calculating in the wrong order |
| FTC structure | Separate Form 1116 by income category, one category box per form | Blending categories into one form |
| Multi-country FTC | Separate country lines or columns when taxes were paid to multiple places | Aggregating countries and losing traceability |
FEIE may reduce current U.S. taxable income, but excluded foreign earned income still has to be reported on the return. The physical presence test is strict: the 330 days do not need to be consecutive, but each counted day must be a full 24-hour period from midnight to midnight. If you miss the threshold, the test fails even for common disruptions such as illness, family issues, vacation, or employer direction.
Keep year-specific limits in view when you model outcomes: $130,000 for 2025 and $132,900 for 2026. Run FTC modeling with the same discipline because Form 1116 category and country structure is what makes the credit reviewable later. Coordinate this work with the Totalization Agreement when self-employment exposure is in play, and treat Totalization as a review checkpoint because this material does not provide agreement-rule details.
A simple two-column decision note can keep this straight. In one column, list FEIE gates and supporting records. In the other, list FTC structure controls and supporting records. That makes the tradeoffs visible and helps prevent assumptions from one method leaking into the other.
Another useful control is to freeze the order of analysis. First decide whether FEIE eligibility is actually supported. Then decide whether FTC structure is clean and complete. Only after that should treaty-dependent arguments remain in the file as active items. When you reverse that order, the later models tend to inherit assumptions that were never documented properly.
You might also find this useful: How to Legally Avoid Double Taxation: A Freelancer's Guide to Tax Treaties.
DIY is reasonable while the file is still explainable. Stop once you start guessing. A good practical trigger is this: if you cannot confirm your Form 8938 and FBAR position from your records without guessing, escalate before filing.
If you cannot verify whether you are a specified person, whether the applicable Form 8938 threshold is met, or whether FBAR maximum account values are supportable from your records, treat that as a hard stop instead of filing on assumptions. The issue is not just technical accuracy. Once you guess on one reporting track, it usually spills into others.
| Escalation trigger | Why it is a hard stop | What to prepare before review |
|---|---|---|
| Form 8938 scope or threshold is unclear | Form 8938 applies only to specified persons, and thresholds are not one-size-fits-all | Filing status, foreign asset list, prior return |
| You are treating Form 8938 and FBAR as one filing | Filing Form 8938 does not remove any FinCEN Form 114 requirement | Separate Form 8938 vs FBAR checklist |
| FBAR maximum values are uncertain | FBAR depends on maximum account value and the aggregate test | Account statements and a maximum-value worksheet |
| You still have unresolved Form 8938 or FBAR reporting uncertainty | Unresolved uncertainty can affect required filings and timing | Timeline memo and open-issue notes |
For Form 8938, use two controls: confirm whether you are a specified person above the applicable threshold, and confirm filing mechanics. Form 8938 is attached to your annual return and filed by that return due date, including extensions. If you are not required to file an income tax return for the year, you do not file Form 8938 for that year.
For FBAR, keep it on a separate track from day one. Filing is required if one account or aggregate maximum account value exceeds $10,000 during the calendar year. Use periodic statements to support your maximum-value estimate, record values in U.S. dollars, and round up to the next whole dollar. If you have fewer than 25 accounts and cannot determine whether aggregate maximum values exceeded $10,000, use the available amount unknown path.
When you stop DIY, add a short escalation memo. Include the exact unresolved question, the record you already checked, and the form affected. That reduces back-and-forth and gives a professional reviewer a clean starting point instead of a vague request for help.
If Form 8938 or FBAR analysis is still uncertain after this check, move from DIY to professional review before filing.
A useful threshold in practice is whether another person could take your notes and continue the work without calling you for basic explanations. If not, the file probably still depends too much on memory. That is usually the moment to step back and get review before a technical filing decision turns into a documentation problem.
Build the record set before you draft the return. That one choice removes a lot of deadline pressure because classification, math, and support are developed together instead of rebuilt at the end.
A good file is boring in the best way. Every major amount can be traced, every label can be explained, and the logic does not depend on memory or on a conversation you had weeks earlier. Once the records are stable, the return becomes a reporting exercise instead of an investigation.
Start with a practical pack that supports income classification and amounts from first record to final total. Treat this as a defensibility standard, not a fixed legal checklist.
This material does not confirm an official Korea-mandated document list, so treat the following as practical examples:
Use consistent file names so retrieval is fast. A simple pattern such as date, payer, amount, and stream ID is enough to keep the file reviewable without adding much admin work.
It also helps to store the summary note beside the source document rather than only in a separate master file. That way, if you open an agreement or payment record months later, the reason it matters is already attached. Small retrieval choices like that make review much faster when you are under deadline pressure.
Pick one reconciliation view and stick to it so each amount can be followed across records without manual reconstruction. As planning markers, one South Korea expat tax guide lists a January 1 to December 31 tax year, KRW as the currency context, and a May 31 filing deadline. Use those markers to structure your file, then confirm the live rule before you file.
When you convert or summarize amounts, keep the supporting note beside the number rather than in a separate document. That keeps context attached to the figure and reduces rework when you revisit a calculation later. Consistency matters more than elegance here.
The same goes for dates. If one part of the file is organized by service period and another by payment date, say that clearly in the header and keep it consistent within each sheet. Hidden switches between date logic create confusion that looks like a tax problem but is really a record-keeping problem.
Judgment calls need a short memo, not memory. Write down the reporting decisions that required interpretation, then run a blind trace test: can someone else follow a sample amount from source record to return entry without filling in missing logic?
Run that trace on at least one amount from each major income stream. If the same confusion appears twice, fix the underlying ledger note instead of patching a single line item. The goal is a file that still makes sense after some time has passed, not one that only works while the details are fresh in your head.
A good trace check starts with the return figure and walks backward to the ledger, then to the invoice or agreement, and then to the payment record. After that, reverse the direction once and make sure the same amount lands back in the same place. If the path breaks in either direction, the memo or ledger note probably needs work.
If the trace fails, stop there and escalate to credentialed review before filing. Cross-border work often looks manageable until you try to explain the path from record to return. The trace check tells you whether the file is actually ready.
The low-stress route is not doing less work. It is doing the work in the right order. Lock the decisions and the evidence before you draft returns. Your protection is a traceable record, not memory or confidence.
Keep two working files:
Keep Korea and U.S. filing on separate tracks, then reconcile them to the same fact set. That is the easiest way to catch mismatches before filing instead of after a late edit.
For the U.S. side, treat Publication 54 as a live checkpoint, not a one-time read. It moved to a continuous-use revision model in tax year 2025, and the December 2025 revision points readers to post-publication updates. It also directs readers to inflation-adjusted amount updates because those values were removed from the publication text, so a saved copy can miss current limits or time-limited relief.
Before filing, run four checks:
Add one final reconciliation step: compare the assumptions used in your Korea filing notes with the assumptions used in your U.S. forms. If a core fact is described differently across the two tracks, resolve that mismatch before submission.
A calm filing finish usually comes from being able to answer the same basic questions every time: what decision was made, what record supports it, and what fact would change it. If those answers stay stable from the first memo through the final return, the process usually stays manageable too.
Use one hard-stop rule: if a major assumption is not documentable, pause DIY and get credentialed review before filing.
Next step: complete the residency decision, rate-choice check, and evidence-pack checklist, then draft returns from that locked record set.
It depends on your facts, and this material does not establish which Korean rate method applies to your case. Test both the flat-style and progressive paths against your actual records, then document why the chosen path is stronger and what could invalidate it.
This article does not provide a verified individual filing deadline for Korea. Set an internal cutoff early, but confirm the live deadline for your filing year through current official Korea guidance before you file.
This material cannot support a firm yes or no answer on that rule. Confirm your residency classification first, then verify income scope under current local guidance before deciding what belongs in the file.
Yes. Claiming FEIE does not remove the need to file a U.S. return reporting the income. Keep the Korea and U.S. tracks separate enough to stay clear, but use the same underlying records so the facts remain consistent.
Neither wins by default, so model both before you choose. FEIE has a hard eligibility gate, including 330 full days in a 12 consecutive month window, and a foreign housing exclusion or deduction reduces FEIE capacity. Then compare that result with FTC mechanics on Form 1116 and choose the path your records support.
From this material, the key confirmed FTC form is Form 1116, completed one income category per form with one category box per form and generally reported in U.S. dollars. FBAR and Form 8938 should be treated as separate checks, because this article does not establish thresholds or filing triggers for every case. Use current official instructions and your own facts before filing.
Stop DIY when your file stops being explainable from records. If you cannot support FEIE day counts cleanly or your income streams cannot be classified without guesswork, get an international tax professional to review the file before submission.
Asha writes about tax residency, double-taxation basics, and compliance checklists for globally mobile freelancers, with a focus on decision trees and risk mitigation.
With a Ph.D. in Economics and over 15 years of experience in cross-border tax advisory, Alistair specializes in demystifying cross-border tax law for independent professionals. He focuses on risk mitigation and long-term financial planning.
Educational content only. Not legal, tax, or financial advice.
Treat this visa as a gate, not a travel detail. The Digital Nomad (Workation) Visa, also called the F-1-D visa, is presented as a route for remote work tied to non-Korean employers or overseas business activity. Practical order matters: confirm fit, build evidence, then choose where to file.
The safest way to approach Seoul is to treat the first 90 days as a live test, not as proof that every long-stay decision is already made. A lot of relocation trouble starts when early excitement gets mistaken for certainty. Then deposits get wired, lease dates get fixed, and move-in plans get locked before legal stay, admin timing, or daily work fit have been tested in real life.
Classify the tax problem before you touch a return. If your income is mostly personal service fees across borders, this guide fits. If your issue is C corporation profits and shareholder dividends, you are solving a different problem.