SaaS & Software Business Tax

Setup Fees and Recurring Revenue for Foreign-Owned SaaS LLCs (2025-2026)

10 min readArticle
Filing path

How to approach this

A source-based path from understanding the rule to filing and recordkeeping.

  1. Determine the requirement

    Confirm whether and how the rule applies to you.

  2. Identify the forms

    Map the requirement to the specific IRS forms involved.

  3. Prepare and file

    Complete the forms accurately and submit on time.

  4. Retain records

    Keep documentation supporting every figure you report.

Key formsIRS guidance

Key Takeaways

  • A SaaS agreement can contain both recurring access fees and service-style setup revenue.
  • Implementation and onboarding work should usually be tracked separately from subscriptions.
  • Service-income analysis often starts with where the work was performed.
  • A clean contract and ledger split makes later ECI analysis much easier.

A SaaS contract can contain more than one tax story

Foreign SaaS founders often write one agreement that includes onboarding, custom setup, migration help, training, and the recurring subscription itself. Commercially that feels like one deal. Tax-wise, it can be several different items sitting in one contract. The recurring software-access fee often gets discussed as platform or license-style revenue, while the setup block can look more like service income tied to actual work performed by people.

That difference matters because service income analysis usually starts with where the services were performed, while recurring platform revenue often leads founders into a different sourcing and withholding conversation.

The contract should separate the money before year-end does it for you

If setup work is real work with real labor behind it, give it its own line item, timing rule, and internal ledger account. When the agreement collapses everything into one monthly invoice, the accounting file becomes much harder to defend later. Founders then end up guessing how much of a year was consulting, how much was implementation, and how much was pure access to software.

A simple revenue map does more than help bookkeeping. It makes later ECI analysis, owner-return analysis, and treaty review far less speculative.

Keep the operating file stronger than the marketing story

Plenty of founders describe heavy onboarding or custom deployment work as 'just SaaS' because that sounds cleaner to customers and investors. The tax file should be more precise. Save statements of work, kickoff notes, hours logs, deployment emails, and invoices showing whether the team was performing meaningful setup activity. If a founder personally spent days in the United States doing implementation or training, that belongs in the tax file even if the website still says the business is fully remote.

The cleaner the operating record, the less likely you are to overstate or understate the U.S. tax risk.

Frequently Asked Questions

Should setup fees and subscription revenue be booked in the same account?

Usually no. Separating them makes the contract economics and later tax analysis much easier to support.

Does a setup fee automatically create ECI?

No. It raises a services-income question, but the answer still depends on where the work was performed and whether the business was carried on in the United States.

What records matter most for setup-fee analysis?

Statements of work, invoices, work logs, travel records, and emails showing what implementation work was actually performed.

SaaSsoftware businessStripesubscription revenueforeign SaaS LLC

Never miss an IRS deadline

Get free email reminders for Form 5472, state annual reports, quarterly estimated tax, and OBBBA rule changes — built for foreign-owned LLC owners. No spam. Unsubscribe anytime.

We respect your privacy. No spam, ever.

More on SaaS & Software Business Tax

Read the in-depth guides