
Yes: treat every invoice as two distinct determinations, then document both before billing. For german freelancer us sales tax decisions, the U.S. LLC is one input, not the final answer. Keep German VAT logic and state-level U.S. nexus analysis in separate tracks, and record offer type, buyer type, customer location, tax note, and reviewer date in a short log. If any entry is unclear, hold issuance and escalate first.
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.
This guide stays narrow on purpose. It focuses on cross-border services and digital work so you can make usable invoicing decisions. It is not a full corporate filing strategy, payroll guide, or catch-all for every multi-country edge case.
Treat the LLC as one fact in the file, not the conclusion. Entity treatment can depend on eligibility checks and documented activity, and some regimes apply at the company level rather than the individual level. Formation documents help, but they are not the whole test by themselves.
For each invoice, treat these as two separate questions to verify:
Do not let one conclusion stand in for the other. If a key fact is missing, pause, record the uncertainty, and verify before you issue the invoice. A simple log helps: what you sold, who bought it, where they are, which tax question you tested, and why you chose that treatment.
The rest of this guide gives you a practical sequence. Get your facts straight, classify the sale, run the two tax checks separately, and keep enough evidence to support the result later. If you want a deeper dive, read The Ultimate Digital Nomad Tax Survival Guide for 2025.
Before you bill, get the inputs right so your German invoice and VAT treatment rest on the same facts every time.
Write down the tax status you are actually using now, especially whether you are invoicing under standard VAT handling or the small-scale entrepreneur exemption under Section 19 UStG.
If anything is unclear, do not guess. Record what your current registrations and bookkeeping show, and use that same fact pattern consistently until you verify it.
Review the template you actually send to clients and check three basics:
| Check | What to verify | Detail |
|---|---|---|
| Tax-number field | Check the tax-number field first | In this source set, the 11-digit Steueridentifikationsnummer is not for freelance client invoices. The Steuernummer, with 10 digits, is the number referenced for client invoicing. |
| VAT wording | If you are not charging the standard 19% VAT, include a legal statement on the invoice | For Section 19 UStG treatment: "Gemäß § 19 UStG wird keine Umsatzsteuer berechnet." |
| Invoice numbering | Check invoice numbering | Keep it logical and consistent. |
If any of these are inconsistent, fix the template before you send the next invoice.
For each pending invoice, note:
If one invoice includes mixed services, separate the line items so VAT handling is easier to apply and review.
Keep a short written record of each invoice decision. Note the date, the VAT treatment used, the customer location, the service type, and the VAT statement used on the invoice.
This is a practical control, not a legal form. A brief log is much easier to review and defend later than trying to reconstruct decisions years afterward.
Do not start with U.S. state analysis. First make sure your German classification, registration, and VAT process are documented and consistent.
Start with the work you actually do. In Germany, freiberufliche Tätigkeit is a defined category under §18 EStG, while other activity can be treated as Gewerbe. Use a registration check, not assumptions:
If your case is borderline, treat the classification as a documented working position. The Finanzamt can decide freiberuflich versus gewerblich case by case, and final classification may be confirmed later in a Betriebsprüfung.
Write down your current VAT setup before you look at any U.S. tax question:
As a general rule, businesses submit Umsatzsteuer-Voranmeldungen monthly or quarterly. NRW guidance also states that from 01. Januar 2021 bis 31. Dezember 2026, pre-returns are generally quarterly and due by the tenth day after each pre-return period. Use that as a prompt to verify your own filing cadence, not as a universal default.
If your classification, registration path, or VAT treatment is unclear, stop there. Resolve the German side first with a qualified advisor.
Your contracts, invoices, bookkeeping labels, and Finanzamt records should tell the same story about the activity and VAT position. Include onboarding records such as the Fragebogen zur steuerlichen Erfassung and any Gewerbeanmeldung, where applicable.
That consistency is what makes the position defensible. Once that foundation is stable, you can review what you sell and who buys it without carrying basic status confusion into every invoice.
For a step-by-step walkthrough, see How to Get a Sales Tax Permit as a Freelancer.
If you want later tax decisions to hold up, classify the real offer first. A simple offer matrix is easier to maintain now than to rebuild after volume grows.
Start from what the customer actually receives, in plain language. Then map each offer to the legal status check that applies in Germany: potential Freiberufler activity (Section 18 EStG) or potential Gewerbe activity.
Use engagement facts, not labels alone. Contract wording by itself is not enough if your contract, invoice, and day-to-day delivery describe different things.
As a records check, keep your offer list aligned with billing records. If you combine employment and self-employment, keep separate books, and make sure invoices carry the correct tax number and, where applicable, VAT ID.
Then duplicate each offer row by buyer type: business customer and end consumer. Treat this as documentation, not a final legal-status conclusion.
What matters for status is the nature of the work and how it is actually performed. In ambiguous cases, the tax office decides.
| Offer/activity | Buyer type | Status checkpoint | Required verification checkpoint |
|---|---|---|---|
| Potential liberal-profession work | Business customer | Check whether activity fits Section 18 EStG or is analogous | Contract scope, invoice description, and actual delivery model match |
| Potential liberal-profession work | End consumer | Check whether activity fits Section 18 EStG or is analogous | Service description, invoice records, and actual delivery model match |
| Potential commercial/trade work | Any buyer type | Review as potential Gewerbe activity | Scope of activity and operating model are documented consistently |
| Mixed or unclear activity | Any buyer type | Ambiguous, escalate early | Keep contract, invoice, and real working conditions aligned for review |
For every row, document the same four facts:
These facts do not produce an automatic answer, but they are core inputs for a reliable review.
Use a simple rule. If you cannot clearly place an offer into Freiberufler or Gewerbetreibende based on documented facts, escalate before scaling.
Classification mistakes can lead to back taxes, penalties, and administrative burden. Where false self-employment risk is present, retroactive social-security exposure can also arise.
Keep this matrix with your contracts, invoices, and client records. If a new offer does not fit an existing row, add a new one, document the facts, and escalate before expansion.
For more detail, read The Best Software for Calculating and Remitting Sales Tax.
Run this as two independent checks every time: the German side first, then the U.S. state sales and use tax review. One result does not replace the other.
If the invoice outcome is "no VAT charged in Germany," that answers only the Finanzamt question. It does not answer whether the customer's U.S. state requires a separate sales tax determination.
In VAT terms, the U.S. is a third country, or Drittland. Third-country transactions are generally VAT-free, but only with clean documentation and invoicing. For services to businesses in third countries, that treatment is usually tied to required invoice notation, and the exemption reason should be stated clearly when applicable. One wording reference is: "According to §3a Abs. 2 UStG taxable at the recipient location."
On the U.S. side, rules vary by state, so exposure has to be reviewed state by state. "No VAT charged in Germany" is not a U.S. tax conclusion.
| Decision point | German side / Finanzamt check | U.S. state tax jurisdiction check |
|---|---|---|
| Main question | Is VAT due under UStG rules? | Does this sale need sales tax review under the customer's state rules? |
| Core location test | Germany plus EU and third-country VAT treatment | Customer state, because rules vary by state |
| What "no tax" means | VAT may be uncharged if the transaction qualifies and invoice wording is correct | No tax may still be correct, but only after a separate state-level review |
| Key evidence | Invoice wording, buyer status, proof of export, service-delivery records | Customer location and a written state review note |
| Rule owner | Finanzamt and German VAT law | Individual state sales and use tax rules |
Before you send the invoice, confirm in writing the customer location, the buyer type, and the exact tax note for that invoice. Keep support for the German side, including proof of export or service delivery, separate from your U.S. state review records. Rates like 19% and 7% belong to the German layer only. They do not answer the U.S. layer.
Treat this as a state-by-state screening step, not a national conclusion. If a decision is not tied to a real state tax source or written professional advice, mark it verify before invoicing.
Start with a working log for every customer state you serve, plus the District of Columbia. The goal is to see where review is needed, not to guess outcomes from memory.
| Field | What to track | Detail |
|---|---|---|
| Jurisdiction | Customer state or District of Columbia | The goal is to see where review is needed, not to guess outcomes from memory. |
| Buyer type | Business or end consumer from Step 2 | Track buyer type with each jurisdiction. |
| What you sold | Consulting, SaaS, or a mixed bundle | Use the offer actually sold in that jurisdiction. |
| Billing pattern | One-time or recurring | Record the billing pattern for that jurisdiction. |
| Volume | Invoice count and revenue for that jurisdiction from your records | Use your records for invoice count and revenue. |
| Non-invoice footprint | Travel, contractors, local events, or marketplace use | Log activity beyond invoices. |
| Current status | no current signal, verify before invoicing, or escalated for review | Keep the working status explicit. |
| Review trail | Last review date and reviewer | Update the log when the review changes. |
For each jurisdiction, keep two separate judgments:
Because the provided materials do not include state thresholds or state taxability rules, do not fill those gaps with assumptions. If details are missing, keep the entry verify before invoicing.
Also keep source vetting strict. In the provided excerpts, one source is cookie-consent text, and another is front matter from a German federal economic report (publisher: BMWK; status: February 2024). Those can be logged as vetting artifacts, but they are not U.S. state sales-tax authority.
If your footprint is spreading across states, recurring digital revenue is growing, or treatment is still unclear, escalate early. These are practical review triggers, not legal thresholds.
| Red flag | Why it triggers re-check | Next action |
|---|---|---|
| Sales concentration rises in one state or D.C. | Exposure may have changed from your prior review | Reopen that jurisdiction and keep verify before invoicing if still unclear |
| Offer changes, for example consulting to recurring SaaS, or a mixed bundle | Prior working assumptions may no longer fit | Save updated offer terms and a sample invoice for review |
| Marketplace expansion | Channel setup can change how transactions are documented | Review channel documentation and retain agreement records |
| Repeated unresolved questions in one jurisdiction | Open issues can carry across invoices | Escalate to a U.S. tax professional and attach written guidance to the log |
The output of this step is a living log, not a one-time opinion. Each entry should include a re-check date and a small evidence set you can retrieve quickly. Keep the customer location record, contract or order form, offer description, invoice sample, and a short determination note.
If a conclusion is uncertain, say so plainly: verify before invoicing. Re-check when business facts change.
Once the tax decision is made, put it into the invoice workflow before anything goes out. If either the Germany-side VAT treatment or the U.S. state decision is still marked verify before invoicing, hold the invoice and escalate first.
Your template should show clearly who billed, who bought, what was sold, and how tax was treated. Keep it simple, but remove ambiguity.
| Invoice element | What to show | Detail |
|---|---|---|
| Seller entity | Seller entity used for billing | Align with the contract party and payout account. |
| Customer details | Customer legal name and billing location details | Use the details used in your jurisdiction review. |
| Service description | What was sold | For example consulting, SaaS subscription, or a mixed bundle. |
| Tax treatment note | Tax treatment note tied to your recorded determination | Keep the tax treatment explicit on the invoice. |
| German registration details | Registration details used in the billing path | Keep them consistent with your actual registration records, including the Steuernummer obtained through the Fragebogen zur steuerlichen Erfassung where relevant. |
Those fields should be explicit on every invoice.
Use one internal rule: show a VAT line only when your documented determination says it applies to that invoice. If it does not apply, omit it deliberately and keep a short linked note showing why.
Do not guess treatment from memory, and do not let entity structure decide it by default. If it is still unclear, escalate before issuing the invoice.
Also keep the e-invoicing checkpoint in view. The Germany guidance, updated Mar 5th, 2026, highlights mandatory data fields, transaction-scope checks, and formats such as XRechnung and ZUGFeRD. If your flow falls within that scope, verify scope and format before finalizing.
Treat "not charged" as a recorded decision, not a silent omission. Add an internal template field or linked record for:
charged, not charged, or verify before invoicingThis is a documentation control, not a claim about legally required customer-facing wording.
Each invoice should link back to the evidence behind the tax treatment. Keep a compact pack:
If someone cannot trace the decision quickly, fix the template now by linking the decision log and storing any gray-area memo with the billing record.
Related reading: A Deep Dive into the 'Dividend' Article of the US-Germany Tax Treaty for LLC Owners. Before you send the next invoice, lock in consistent tax-note wording with this free invoice generator.
Your evidence pack should let someone reconstruct each tax decision quickly. A practical approach is one client file for core records, with German VAT notes and U.S. sales-tax notes organized separately for clarity.
Create a client file that mirrors the real transaction. At minimum, keep the contract or order form, final invoice, and tax-classification or jurisdiction notes together so the record is easy to follow.
A compact structure:
| Folder or subfolder | What to keep | Verification point |
|---|---|---|
| Client core | Contract, order form, invoice, customer billing details | Core details and service description align across the record |
| German VAT | VAT reasoning note, VAT return support, relevant Finanzamt correspondence | VAT treatment on the invoice aligns with your VAT notes and return support |
| U.S. sales tax (if applicable) | Jurisdiction review note, tax handling result | Keep U.S. determination notes distinct from German VAT files |
Use consistency as the control. If the contract, invoice, and tax note do not match, fix the record before the next invoice.
Separate German VAT records from U.S. determinations. For organization, keep VAT and U.S. sales-tax notes in different subfolders, even for the same invoice. They both sit under taxes on goods and services, but they are different determinations.
On the German side, keep the VAT reasoning and filing trail together, including relevant Finanzamt letters. Those letters are important, so do not leave them scattered across inboxes or paper files.
On the U.S. side, keep jurisdiction-level determination notes separate from return support for Germany. If one note starts trying to justify both regimes, split it and restate each conclusion clearly.
Write a memo for gray-area cases. When classification is hard, add a short decision memo. Non-cash compensation is one clear trigger to document carefully.
Keep the memo concise: facts reviewed, classification chosen, and open uncertainty. If compensation includes gifted products or services, store market-value evidence in the same client file because non-cash benefits can count as business income.
A 2025 practitioner guide recommends keeping digital records and receipts for ten years. If you cannot trace contract -> invoice -> tax note -> filing support, the evidence pack still needs work.
This pairs well with our guide on How to Get a German Tax ID as a Freelancer Without Mix-Ups.
Do this monthly, not as a year-end cleanup. For a Germany-based freelancer dealing with cross-border tax questions, drift often starts with small changes in offers, customer mix, or invoice setup.
Reconcile sales by customer location, customer type, and offer type. At month end, reconcile sales in a simple sheet by customer location, customer type, and offer type. Focus on movement, not just totals: where volume is shifting, whether the B2B and B2C mix is changing, and which offers are becoming dominant.
Make sure the sheet ties back to issued invoices and bookkeeping totals before you make new tax decisions. A monthly cadence keeps visibility current and helps prevent reactive reviews.
Use columns like month, customer location, B2B or B2C, offer name, invoice total, tax charged or not charged, and a link to the determination note.
Re-check offer changes against your original mapping. Treat offer changes as a trigger for review. New tiers, add-ons, bundled setup plus recurring access, or renamed packages can make your earlier mapping stale.
Compare what you sell now against your original classification memo. If your live offer description, proposal wording, and invoice line item no longer match, update the mapping before scaling that offer.
Verify invoice logic against German VAT and your tax determinations. Do a monthly spot check for each offer type. Confirm that the tax line behavior, seller and customer details, and service description still match your current VAT position in Germany and your determination notes.
Keep the checks separate. On the German side, invoice treatment should align with your VAT reasoning and records for the Finanzamt. Where tax is not charged, keep a documented determination rather than relying on a blank default.
Maintain an escalation log for anything that changed. Keep a dated escalation log with what changed, when you reviewed it, what you checked, your conclusion, and whether you obtained a professional opinion. This connects monthly monitoring to the evidence pack.
Use it for tax changes and classification risk signals on the German side as your activity evolves. If an item is still unclear after the first review, mark it open and set a follow-up date so it gets resolved rather than buried.
When this goes sideways, the fastest recovery is to rebuild the documented facts. Do not rely on memory, and do not assume the LLC setup itself fills the gaps.
Separate LLC setup from documentation and tax analysis. LLC formation does not substitute for withholding documentation. Re-check the documentation track and the tax-analysis tracks separately.
If you are relying on treaty-based withholding relief, confirm Form W-8BEN is filed and paired with a valid ITIN. Missing setup can lead to unnecessary 30% withholding. Also keep this clear in your file: an ITIN is not a work permit or visa.
Replace borrowed advice with a written determination. If your current approach is based on copied advice, replace it with a short written determination tied to your own facts. Document what you sold, who paid, and which records support your conclusion.
Use a simple test: can another person read your note and understand why withholding relief was claimed, not claimed, or escalated? If not, tighten it before the next invoice cycle.
Rebuild missing evidence before a payer or advisor asks. If past invoices are weakly documented, reconstruct the file now. Pull invoices, contracts or proposals, payment records, customer details, and tax forms exchanged with U.S. payers.
Include ITIN-related documentation where payer reporting requires it. Mark any period as uncertain if support is incomplete, and escalate early, especially where withholding already occurred or a Form 1040-NR may be required.
Treat U.S. state sales-tax and German VAT specifics as case by case until you have complete, source-backed facts.
Gruv is most useful here when your live setup is traceable in practice. Treat it as an operational record layer, not a tax-decision engine.
Verify traceability on one real transaction. Before you rely on it, test one real transaction flow end to end. Make sure you can follow the path from your internal decision notes to the final outcome without rebuilding context from memory.
If that trail breaks or requires manual patching, do not use it as your primary compliance evidence path yet.
Export and archive evidence on a schedule. Where exports are available in your setup, pull them on a fixed cadence and store them with your own determination notes.
Do this before review pressure hits. Records that are easy to see today can become harder to retrieve later, and missing artifacts turn routine checks into reconstruction work.
Separate platform records from tax conclusions. Even with cleaner records, keep your tax determinations in a separate written decision.
If a workflow or policy gate is not clearly documented and testable in your environment, treat it as unconfirmed. Keep manual controls in place until you verify the scope.
Start with your German setup and document each decision before you send the next invoice. Treat this as two separate checks every time: VAT on the German side and potential U.S. sales and use tax exposure.
Verify the status you already use with the Finanzamt, and keep the classification in your records consistent. Confirm your VAT workflow, including whether you file Umsatzsteuer returns monthly or quarterly based on local tax-office instructions, typically via ELSTER. Verification point: your registration details, bookkeeping labels, and invoice header should match. If you rely on Kleinunternehmer treatment, compare revenue against the commonly cited €22,000 and €50,000 thresholds, then confirm current official guidance before relying on them.
List what you sell line by line, for example consulting, SaaS, e-commerce-related services, support, retainers, or bundles, then mark each line as business or consumer buyer. Verification point: every invoice line should map to one offer type and one buyer type.
For VAT, keep customer location explicit in your analysis, whether Germany, other European countries, or non-European countries. For U.S. exposure, run a separate verify-before-claim review rather than treating the VAT outcome as your U.S. answer. Recommendation: keep two distinct fields in your decision log, not one blended note.
Review customer locations, revenue concentration, and whether recurring digital sales now require a fresh jurisdiction check. Screen each relevant state separately before assuming treatment. Red flag: if your footprint is expanding, mark the file "verify before invoicing" instead of guessing.
Make sure each invoice clearly reflects what was sold and the tax treatment you decided. Keep the contract, invoice, customer location evidence, and written determination together. On the German side, keep VAT terms consistent in your files. If you reclaim Vorsteuer, retain purchase invoices that show VAT, commonly 7% or 19%.
Re-check new jurisdictions, offer changes, and escalation triggers once per month. Compare what you billed with what your template and decision log say you intended. Outcome to aim for: one short monthly note with the date, reviewer, what changed, and whether outside advice is needed.
For your monthly compliance cadence, track changes and review dates in one place with the tax residency tracker.
Not automatically. First classify the customer under EU VAT place-of-supply rules: for B2B services, the general rule points to where the recipient is established, while for non-taxable recipients in a B2C context, the general rule points to where you as the supplier are established. Keep evidence of who the customer is, where they are established, and why you treated the invoice that way.
No. U.S. sales tax exposure is determined state by state, not by LLC formation alone. Physical presence is not required in some states, so a non-resident LLC can still have collection duties if it crosses a state threshold or otherwise creates nexus.
No. U.S. sales and use tax is generally administered at the state and local level, while the IRS administers federal tax law. Treating it like one nationwide VAT system can cause missed registration or taxability issues.
It depends on the state and on what you actually sell. New York says services are generally exempt unless specifically taxable, while Washington taxes listed IT services starting Oct. 1, 2025 and treats software as a service as a retail sale in that guidance context. If your offer mixes consulting, support, and recurring software access, split those items before deciding tax treatment.
Keep records that substantiate your tax position, including the contract, invoice, customer identity and location evidence, and notes on service classification and tax treatment. The IRS frames recordkeeping as a burden-of-proof issue, so your file should show how you reached the result, not just the final invoice. As one practical baseline, Virginia requires businesses to keep records for at least three years after the return due date or payment date, whichever is later, and you should verify retention rules in the states relevant to you.
Hire one when your facts no longer produce a clear answer. Potential triggers include recurring SaaS revenue, sales into multiple states, approaching a published nexus threshold such as Virginia’s more than $100,000 in annual gross retail sales or 200 transactions, or situations where services and software are hard to classify. If your guidance is outdated, get a current review before you scale.
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.

With digital nomad taxes, the first move is not optimization. It is figuring out where you may be taxable, where filings may be required, and what proof supports that position.

The right pricing model matches uncertainty and cashflow risk. It should fit how clearly the work can be defined, approved, and defended, not just what you are used to selling. Hourly billing gives you room to work while requirements are still moving. Fixed project pricing gives the client stronger budget clarity once deliverables are stable enough to pin down.

Start with one sequence and keep it boring. Decide the business question. Choose one primary reporting source. Verify tracking against the origin. Then review it on the same day each week. That order matters more than which tool wins your shortlist.