A freelancer needs a sales tax permit only when their sales are taxable in a jurisdiction and a registration trigger requires collection. Start by classifying each offer by deliverable, then track physical presence and economic nexus one jurisdiction at a time. When a trigger is confirmed, register there before collecting tax and set up filing, remittance, and recordkeeping controls.
Start with what the client actually receives, not the label you use for your work. Classify each offer by the output delivered, because that shapes taxability and whether permit follow-through may be required.
Use these terms consistently:
Run this yes-or-no screen for every offer:
If the first three answers are mostly yes, treat the offer as higher risk until you verify state rules. If the last answer is no, treat that as a bundling red flag and review pricing, itemization, and any state true-object exceptions before you assume tax treatment.
| Preliminary tier | What the client gets | Common gray zone | Safe default pending state verification |
|---|---|---|---|
| Lower | Calls, advice, custom human-effort work | Strategy package with follow-up PDF summary | Treat as mixed. Add current state treatment after verification. |
| Medium | Custom file or document delivered to one client | Research memo, design files, implementation plan | Verify whether the state distinguishes custom work from digital products. |
| Higher | Standardized digital good, subscription, or remote software access | Course plus coaching, template library with office hours, SaaS onboarding bundle | Treat as review-required before sale in each target state. |
Do not assume there is one U.S. rule. California says electronic data products are generally not taxable, New York taxes prewritten software regardless of delivery method and excludes custom software made to one purchaser's specifications, and Washington taxes digital products regardless of access method and expanded certain taxable services effective Oct. 1, 2025.
Before Step 2, finish this checklist:
If you want a deeper dive, read The Ultimate Digital Nomad Tax Survival Guide for 2025.
Once you know what you sell, the next question is where that activity creates a tax connection. Map it one jurisdiction at a time, because nexus is jurisdiction-specific and a single national shortcut will fail you.
Start each jurisdiction review by separating two triggers:
Since Wayfair (June 21, 2018), economic nexus has become a core trigger for remote sellers, but the details still vary by state. Treat each state as its own rule set. Threshold formula, channel counting, registration timing, and marketplace handling are not uniform.
Use this workflow for every U.S. jurisdiction where you sell:
monitor, register, or escalate.A single live worksheet is usually the cleanest way to manage this. Keep one row per jurisdiction so you can show when a trigger appeared, what sales counted, and what you did next.
| Jurisdiction | Client type | Revenue channel | Transaction count | Trigger status | Evidence links | Next action |
|---|---|---|---|---|---|---|
| [State/Country] | [B2B/B2C/Mixed] | [Direct/Marketplace/Mixed] | [Count] | [No trigger/Potential trigger/Trigger met] | [Sales report, invoices, contracts, platform statements, taxability notes] | [Monitor/Register/Escalate] |
Two checks prevent many avoidable errors:
If you cannot show when a trigger was met and which sales counted, registration timing risk rises quickly.
Your footprint pattern tells you how quickly to move from monitoring into registration review.
| Footprint pattern | Nexus risk pattern | Permit urgency |
|---|---|---|
| Service-only custom work | Often lower at baseline because service taxability is not uniform | Usually monitor first, then verify state treatment |
| Digital deliverables | Higher where digital products or taxable digital categories are in scope | Move faster once a trigger appears |
| Direct + marketplace channels | Higher where jurisdictions require combined counting across channels | Verify counting rules early; escalate if unclear |
| Mix of taxable and exempt sales | Higher risk of threshold errors where exempt sales still count in threshold testing | Document taxable-base treatment before filing decisions |
Do not assume your U.S. process covers international exposure. Before you invoice cross-border sales, check these basics:
| Check area | What to verify |
|---|---|
| Customer location | Reliable country data, and province data where needed |
| B2B vs B2C treatment | Which place-of-taxation rule applies to this transaction type |
| Registration trigger | Whether the sale is direct, or platform-facilitated with possible platform collection responsibility |
| Invoicing impact | Whether local VAT or GST/HST rules change what must appear on invoices |
Bring in a tax professional when you face ambiguous multi-state exposure, marketplace-facilitator complexity, or conflicting rule interpretations. That is the point where a worksheet alone is no longer enough.
Related: Do I Have to Pay State Taxes While Living Abroad as a Digital Nomad?.
When a jurisdiction moves from monitor to register, the work changes. At that point, you need a repeatable process to register correctly, collect correctly, file on time, remit on time, and keep records you can defend.
Register when your facts show an actual obligation, and do it in the specific jurisdiction that triggered. In practice, sequence matters because timing mistakes can create avoidable cleanup work later.
Two timing controls deserve special attention:
Before moving on, make sure you can show the trigger date, application date, approval date, and first return due period.
Manual handling is workable only in a narrow setup. Once jurisdictions, exemptions, bundles, or invoice complexity grow, manual control becomes the weak point, and you should move to automation or a CSP.
| Decision criteria | Manual can work | Move to automation or CSP |
|---|---|---|
| Jurisdiction count | Limited footprint with low volume | Multi-state footprint or active expansion |
| Invoice complexity | Simple line items and stable taxability | Mixed items, bundles, digital deliverables, frequent exceptions |
| Exemption handling | Rare exemptions | Recurring exempt sales requiring certificate control |
| Audit trail needs | You can maintain complete records and reconciliations yourself | You need stronger calculation logs and easier return evidence retrieval |
| Error tolerance | You can absorb occasional manual corrections | Deadline misses or rate or sourcing errors are high-risk |
A Certified Service Provider (CSP) can perform most sales-tax administration functions under SSUTA. But the handoff is not instant. You remain responsible for collection and filing until CSP service is active.
The safest approach is a consistent cycle you can repeat every filing period. That rhythm matters more than any single filing.
| Control | Article detail |
|---|---|
| Tax calculation controls | Validate tax logic by jurisdiction; if a state applies destination-based sourcing, local tax is determined by where the sale is delivered |
| Invoice tagging | Tag each invoice by jurisdiction, taxability, customer type, channel, and tax-collected status |
| Return prep | Reconcile invoiced tax, collected tax, and taxable totals before filing |
| Zero-return check | A zero return is a required return for a period with no tax due; Texas and New York both require returns even in no-tax periods |
| Remittance confirmation | Save filing receipts, payment confirmations, and submission timestamps |
| Documentation retention | Keep complete sales and purchase records, returns, and supporting files; Texas guidance cites at least four years in remote seller and marketplace context |
| Exempt transactions | Retain the exemption certificate that supports the tax-free treatment |
For exempt transactions, retain the exemption certificate that supports the tax-free treatment. If you cannot produce it later, that exempt position is harder to defend.
Operational date example: Texas monthly filers are due on the 20th of the following month. Use each jurisdiction's confirmed due dates in your live calendar.
Do not wait for notices if the facts are already unclear. Bring in a tax pro immediately if any of these apply:
Also escalate if you discover late registration exposure. In some states, formal cleanup paths may reduce penalty risk compared with unstructured late filing.
You might also find this useful: How a German Freelancer Can Handle US Sales Tax with a US LLC.
Before you lock in a filing workflow, pressure-test your process for invoice collection, recordkeeping, and payout status visibility against the operational patterns in Gruv Docs.
A sales tax permit is not a one-time checkbox. Once registration is required, you are taking on an ongoing process: register correctly, collect correctly, file on schedule, remit on time, and keep records that support every return.
Assess your offers and your evidence. Classify each offer by deliverable, not just job title, flag where it may be taxable, and keep one sample scope, invoice, and delivery record per offer type so you can support how you treated it.
Map where registration may be triggered. Track sales by customer location every month and verify thresholds state by state, because nexus rules are jurisdiction-specific. Keep a verify current threshold field for each jurisdiction. For example, Washington references more than $100,000 in gross receipts, and Texas remote-seller language references $500,000 in the past 12 months.
Implement the recurring work registration creates. A seller's permit or a New York Certificate of Authority is part of the setup to collect tax where required, and it starts ongoing filing and payment duties. In New York, apply at least 20 days before making a taxable sale, and selling before proper registration can bring penalties up to $10,000. In Texas, returns may still be required even for periods with no taxable sales, and records must be kept for at least four years.
| Approach | Error risk | Time cost | Audit readiness | What you do |
|---|---|---|---|---|
| Reactive | High | Unpredictable | Weak | Fix issues after notices, missed filing, or missed collection |
| System approach | Lower | Planned, recurring | Stronger | Run a defined registration, filing, remittance, and recordkeeping process, manually or with tools or pro support |
Stay DIY when your offers are clearly classified, your jurisdiction count is low, and you can reliably verify thresholds, filing dates, and sourcing rules. Use automation when multi-state volume, digital-product complexity, or filing cadence makes manual checks unreliable. Streamlined registration and CSP options can reduce administrative load for some sellers. Escalate to a tax professional when you identify past under-collection, mixed bundles, marketplace-plus-direct sales, or cross-border exposure. Keep threshold fields as Add current threshold after verification, then validate non-US indirect-tax obligations, including whether Canada's $30,000 small-supplier reference point or the EU EUR 10 000 distance-sales threshold is relevant to your facts.
Add current threshold after verification, registration date, filing frequency, and record location.For a step-by-step walkthrough, see The Best Software for Calculating and Remitting Sales Tax.
If you want to reduce manual tax and payment ops as you scale, review whether Merchant of Record for freelancers is a fit for your setup where supported.
Not automatically. It depends on what you deliver and how your state treats that type of service. Verify the exact service type before invoicing as taxable or non-taxable, especially if the offer bundles advice with files, templates, code, or other outputs.
Economic nexus means your sales activity into a state is high enough to create a tax obligation there even without an in-state office or employee. Monitor sales by state every month and verify the current trigger before assuming you are below it. Physical presence nexus is separate and comes from an in-state business connection.
Cross-border treatment is jurisdiction-specific, so verify obligations before invoicing. Treat VAT or GST/HST handling as a separate verification step by customer jurisdiction rather than assuming your U.S. process covers it. Track customer country and billing location, and talk to a pro if you have multi-country exposure or unclear local treatment.
Do not guess, because sourcing rules vary by state. Verify the applicable sourcing rule for each jurisdiction before invoicing, and do not apply one state's rule everywhere. Collect the transaction details you need for jurisdiction checks and escalate if a sale spans multiple places or platforms.
Treat it as a cleanup issue, not a delay decision. Preserve records and verify the trigger date, registration timing, and affected periods before continuing with the same setup. Past noncompliance, multi-jurisdiction exposure, and unclear treatment are strong reasons to talk to a pro.
Sometimes yes, sometimes no. Classify the exact product first, then check taxability by product type and jurisdiction. Treatment is not uniform, and mixed bundles can need extra review. Collect only after verification and register only when your taxability and nexus facts support registration.
Maybe. First verify whether the marketplace is collecting and reporting your sales in that jurisdiction and whether any direct sales change your registration duty. Reconcile marketplace tax reports to your gross sales records. Register directly if you also sell outside the platform or cannot verify marketplace reporting.
A financial planning specialist focusing on the unique challenges faced by US citizens abroad. Ben's articles provide actionable advice on everything from FBAR and FATCA compliance to retirement planning for expats.
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.
First decision: stop treating digital nomad taxes as a hunt for the lowest rate. The high-value move is identifying where you are taxable, what filings follow, and what evidence supports your position if a tax authority asks questions later.
Living abroad does not end `state income tax` exposure by itself. The first decision is practical: choose a filing position your facts can support, then build records that support the same story all year.
Use this as your default: a U.S. LLC can change how you operate and document the business, but it does not turn German and U.S. tax questions into one answer.