Disclaimer — YMYL content. Visa rules and renewal procedures change. Information current as of June 2026. Always verify with the relevant consulate or official immigration website before applying. This is not legal or tax advice.
A remote-work-visa holder is, by definition, already employed. Payroll, taxes withheld at source, social contributions, payslips — most of the income story lives in the employer's HR systems, not in a workspace tool. The temptation to skip COLO entirely is real and reasonable.
But two patterns recur in the remote-work-visa population that make COLO the right tool to have ready:
- A side practice develops — consulting on the side, freelance projects, small contracts. Most remote-work visas allow this within strict limits; the documentation of the side practice matters at tax filing and (sometimes) at visa renewal.
- The remote-work visa is a stepping stone, not the destination — many holders transition to a longer-term residence (freelancer, self-employed, EU Blue Card, work permit) within the first 12-24 months. The COLO records of any side practice during the remote-work period become the foundation of the next visa application.
This article covers both patterns. For the wider remote-work-visa context, read Remote Work Visa Guide 2026 and Remote Work Visa Application Process first.
TL;DR
- Remote-work-visa holders are typically employees of foreign companies — most of the income workflow lives at the employer, not in COLO.
- COLO becomes relevant in two situations: a side practice on top of the foreign employment, or a transition from remote-work-visa to freelancer or self-employed visa for the longer term.
- Three illustrative scenarios cover an Estonia-based UK employee moonlighting, a Norway-based contractor restructure, and a Latvia-to-Spain transition.
Pattern 1 — Side practice on top of foreign employment
Most remote-work visas allow some level of self-employed side activity, with restrictions. The rules vary:
- Iceland Long-Term Remote Worker — closed May 2026. On 13 May 2026 the Directorate of Immigration (Útlendingastofnun) announced that the long-term visa provision of the Foreign Nationals Act was repealed by the new Visa Act No. 37/2026. The short-term residence permit that replaced it is open only to close family members making an extended visit and to artists, scientists or athletes — not to remote workers. While it ran, side work was permitted as long as the foreign-employer relationship was the primary income source
- Bermuda — the WFB certificate closed to new applicants on 28 February 2025. While it ran, the Government of Bermuda's own condition was that holders "cannot seek work in Bermuda", so side practice had to be for clients outside Bermuda. The Government has not published equivalent side-work guidance for the successor Permission to Reside — confirm your specific arrangement with the Bermuda Department of Immigration before taking any side client
- Estonia D-visa (remote-worker stream) — side work for foreign clients is permitted; local Estonian clients require careful structuring
- Norway Independent Contractor — already structured as self-employed, so "side" practice is just additional client work
- Latvia DNV — side work for foreign clients permitted
The line that matters in every case is local-client work. Local clients in the host country usually require a different visa or, at least, registration with the local tax authority for self-employed work. Side practice for clients outside the host country is typically the safer path.
COLO supports the side-practice workflow:
- Client management — store all side-practice clients separately, tagged by location (EU, US, UK)
- Contracts — store side-practice contracts with electronic signatures
- Invoicing — issue invoices in the client's currency; the reporting currency aggregates everything for tax purposes
- Finance — separate the side-practice revenue from the employer salary cleanly for your accountant
- Reports — generate the per-period side-practice revenue summary at year-end
The cleaner the side-practice records, the cleaner your tax filings in the host country (and your home country, if you remain tax-resident there). The cleaner those tax filings, the stronger any future visa application.
Pattern 2 — Transitioning from remote-work to freelancer or self-employed visa
The remote-work visa is often the first step in a longer plan:
- A six-month Estonia D-visa stay leads to a deeper European search (this pattern was originally written around Iceland's 180-day remote-work visa, whose legal basis was repealed in May 2026)
- A one-year Latvia DNV leads to a Spanish DNV or Portuguese D8 for longer-term residency
- A one-year Bermuda Permission to Reside leads to a Mauritius Premium Visa or similar (the WFB certificate this pattern was originally written around closed on 28 February 2025)
- A two-year Norway Independent Contractor stay leads to Norwegian PR or to a Swiss / German self-employed visa
In each transition, the documentation that you built during the remote-work-visa year becomes the application evidence for the next visa. The freelancer or self-employed visa application typically wants:
- Income history for the previous 12-24 months
- Customer evidence (contracts, signed proposals, invoices)
- Tax compliance from the previous jurisdiction
- Continuity of operation — proof that the business is viable, not just a paper construct
If you ran a side practice through COLO during the remote-work-visa period, the export at transition time is straightforward. If you didn't, you'll need to reconstruct the records from email and bank statements — painful and slower.
The transition is also a moment to register the business locally in the new country. COLO's client management and contracts modules support entity-aware operation — store the new local entity's tax ID and VAT number; they appear on new invoices automatically. Old invoices issued under the previous entity remain as historical records.
Pattern 3 — Pure salaried employee, no side practice, no transition plan
If you're a pure salaried employee on a remote-work visa with no side activity and no plan to transition to a freelancer or self-employed visa, COLO is genuinely unnecessary for the visa itself. The visa renewal pack at year one or two is your employer's payslips, employment contract, employer cooperation letter and standard personal documents — none of which COLO touches.
You might still find COLO useful for personal financial admin — tracking shared household expenses, occasional consulting requests, hobby invoicing — but it isn't a visa-driven need.
Where COLO becomes relevant is when one of these conditions changes: a side practice starts, the employer relationship restructures, you decide to settle longer-term. At that point, starting fresh in COLO is straightforward; the workspace is designed for incremental adoption.
Multi-currency considerations for side practice
Remote-work-visa holders by definition earn in at least one foreign currency (the employer's). A side practice often adds more currencies. A common pattern:
- Employer salary — USD (US employer) or GBP (UK employer) or EUR (EU employer) paid into a home-country bank account
- Side-practice income — USD from US clients, EUR from EU clients, GBP from UK clients, paid into a local or international business account
COLO's invoicing handles per-customer currency:
- Per-invoice currency — set on each customer
- Reporting currency — set on the workspace (usually the host-country currency or the home-country currency)
- Conversion at invoice date — invoices record with the conversion rate at the date of issuance
- Aggregate views — finance dashboard and reports show totals in the reporting currency
This matters because the host-country tax authority typically wants a consolidated view in the local currency. If you're tax-resident in Estonia for the year, you'll file in EUR; the aggregated USD/GBP/EUR invoice history needs to roll up to a single EUR figure. COLO does this without manual spreadsheet work.
Records to keep through the visa year
Whether for side-practice tax compliance, visa renewal or visa transition, the operational records that matter through a remote-work-visa year:
- Employment: payslips (employer), employment contract, employer cooperation letter (saved in personal documents)
- Side practice: signed contracts (COLO contracts), invoices issued (COLO invoicing), payments received (COLO finance), customer records (COLO client management)
- Tax: filings in the host country (your accountant), home-country filings (your accountant), residency-day records (personal log or app)
- Banking: monthly statements from all accounts, both personal and business
At year-end, your accountant pulls the COLO export and reconciles to bank statements. At visa renewal or transition, the same export becomes the application's income-history evidence.
Three remote-worker scenarios
Scenario 1 — Mark, 31, UK-employed software engineer in Tallinn (Estonia D-visa)
Mark is employed by a UK fintech earning GBP 75,000/year, on a one-year Estonia D-visa. Within three months of arrival, two former contacts ask him to consult on a side project — paying EUR 4,500 for six weeks of part-time work, then asking for a longer retainer.
Where COLO sits in his workflow:
- Client management — two side-practice clients added, separate from his (unrecorded) UK employer
- Contracts — the side-practice retainer agreement stored with electronic signature
- Invoicing — monthly EUR invoices to the side clients; reporting currency set to EUR for Estonian tax purposes
- Finance — the side practice's revenue rolls up cleanly, separately from any other workspace activity
- Reports — at Estonian tax filing time, his accountant pulls the EUR-denominated year report
Two practical considerations Mark works through with his tax adviser:
- Estonian tax compliance — he becomes tax-resident in Estonia after 183 days. The side-practice income is taxable in Estonia (he's tax-resident there) and his UK employer income is taxable in Estonia under the UK-Estonia tax treaty's source rules — UK income taxed in the UK at source, with Estonia applying a tax-treaty exemption or credit.
- UK side — he files a UK tax return for the partial UK tax year before he became Estonian tax-resident, then declares his change of tax residency.
His side practice doesn't trigger any special Estonian registration as long as he stays under the small-business turnover thresholds. The Estonia D-visa accommodates this profile cleanly; COLO's clean records make the tax filings straightforward.
Scenario 2 — Lena, 34, German engineer, restructured as Norway Independent Contractor
Lena was a salaried employee at a Berlin engineering firm earning EUR 90,000/year. She wanted to move to Oslo for personal reasons. Her employer wouldn't accept the PE risk of an employee in Norway, but agreed to restructure her as a contractor — she'd register a German GmbH, the German firm becomes a customer of her GmbH, and she applies for the Norway Independent Contractor visa using the GmbH income.
Where COLO sits in her workflow:
- Client management — primary customer (her former employer, now a client of her GmbH), with the GmbH's tax ID and VAT number stored
- Contracts — the consulting agreement between her GmbH and her former employer, signed via COLO's electronic signature
- Invoicing — monthly EUR invoices to the former employer at the same total as her previous salary, with reverse-charge VAT applied per EU rules
- Finance — the GmbH's revenue picture shown in EUR
- Reports — at Norwegian tax filing time, her accountant pulls the year's records; the German GmbH files separately with the German tax authority
The visa application uses the GmbH's contracts and projected revenue as evidence. The renewal at year two repeats the exercise with two years of actual revenue. The Norway Independent Contractor visa counts toward Norwegian PR after three years; she's on track. COLO's records are central to both visa applications and to the dual German/Norwegian tax compliance.
Scenario 3 — David, 39, US-employed product manager in Riga, transitioning to Spanish DNV
David is on a one-year Latvia DNV, employed by a US company earning US$140,000/year. He likes Riga but the European weather is brutal six months of the year. He decides to apply for the Spanish DNV for year two, structuring himself as a foreign-client freelancer rather than continuing as an employee.
Where COLO sits in his transition:
- Through the Latvia year, his side practice has been small — three EUR-denominated freelance projects for European clients totalling EUR 18,000
- Client management holds the three side-practice clients with full contract history
- Contracts stores signed agreements with electronic signatures
- Invoicing holds the EUR invoices and payment records
- Reports generates a one-year side-practice revenue summary in EUR
For his Spanish DNV application, he restructures: his US employer agrees to convert him to a US-based contractor (1099) billing through his US LLC. His Spanish DNV application uses:
- 12 months of side-practice freelance income (from COLO) — supplementary evidence
- The new US LLC contractor relationship with his former employer — primary evidence
- Tax compliance from his Latvia year — clean, thanks to COLO records his accountant used for the Latvian filing
He moves to Valencia for the second year. His COLO workspace travels with him — the same clients, same contracts, same invoicing setup, with the Spanish entity registration added once his DNV is approved and the tax IDs in place.
What this means for COLO users
The remote-work-visa segment is COLO's "optional today, valuable tomorrow" segment. If you're a pure salaried employee for a one-year stay with no transition plan, COLO isn't a forced purchase. If you anticipate a side practice or a transition, starting with the free Solo plan from day one of the visa year saves real time at the transition point.
The product positioning is therefore conservative for this segment:
- Solo (free) is enough for the first year of light side practice or as a personal records repository
- Pro at $18/user/month becomes worthwhile when the side practice generates consistent income or you're preparing a visa transition with reporting needs
- Grow at $24/user/month is appropriate for those who restructure into a fully self-employed model with team or client portal needs
For the wider context, see Remote Work Visa Guide 2026, Remote Work Visa Application Process, the Digital Nomad Visa vs Freelancer Visa comparison, and the freelancer workflow with COLO which fits the transition pattern. For multi-country operation, see solutions for digital nomads. COLO's pricing shows the full plan comparison.
FAQ
Q: I'm employed by a foreign company on a remote work visa. Do I even need a workspace tool like COLO?
Not for the employer income itself. COLO matters if you develop a side practice or plan to transition to a freelancer or self-employed visa.
Q: Can I run a side practice on a remote work visa?
Sometimes. Most programmes restrict income to the foreign employer; check the specific rules and your tax adviser.
Q: Is COLO useful for a one-year stay?
Yes if a side practice or transition is anticipated. Solo (free) is enough for the first year.
Q: How does COLO help with a visa transition?
The historical revenue, customer and contract records become the application evidence for the next visa.
Q: Can COLO handle multi-currency invoicing?
Yes — per-invoice currency, with reporting in your chosen home currency.
Q: What plan should a remote-work-visa holder pick?
Solo (free) for first-year side practice. Pro at $18/user/month when the side practice is consistent or a transition is in view.
Q: Does COLO replace my accountant?
No — COLO produces clean records; your accountant builds the filings.
Q: Will COLO send invoices in the local currency of my host country?
Yes — set the per-invoice currency to whatever the client uses.
Q: How does COLO handle the permanent-establishment risk?
It doesn't directly — PE is a tax-legal matter for your employer's advisers. COLO does cleanly separate any side practice from your employer salary.
Q: Can COLO export records to my home-country tax authority?
COLO exports CSV and PDF for your accountant or filing service. It does not file directly.
Q: What if I switch to a freelancer or self-employed visa mid-stay?
Your COLO records continue uninterrupted; update the invoicing entity per the new business registration.
Q: Does COLO comply with GDPR?
COLO is hosted with standard EU data protection measures. Verify current compliance status before storing EU personal data.
Sources
- Iceland — Directorate of Immigration (Útlendingastofnun): visa services transferred to the Ministry for Foreign Affairs (long-term visa repealed, 13 May 2026)
- Estonia — Police and Border Guard Board: D-visa for digital nomads
- Norway — UDI (Directorate of Immigration): Self-employed
Use the visa year to build the next visa's evidence
Most remote-work-visa stays end in one of three ways — back home, on to the next short stay, or transitioning to a longer-term residence in the same country. The first ending leaves COLO unused; the second and third are exactly what COLO is built for. The cost of starting from day one is zero (Solo plan); the cost of starting late is reconstructing records from email and bank statements.
For wider context, see Remote Work Visa Guide 2026 and Remote Work Visa Application Process. For the freelancer workflow that often follows a remote-work transition, see Freelancer Workflow with COLO and Self-Employed Workflow with COLO. For multi-country patterns, see solutions for digital nomads.