W-8BEN-E for Foreign SaaS Companies: Entity Classification and Step-by-Step Guide

You are here because Stripe, AWS Marketplace, the App Store, Google Play, or a U.S. enterprise customer asked your software company for IRS Form W-8BEN-E before releasing payouts or signing a vendor agreement. That request is normal for foreign legal entities that receive U.S.-source income. A SaaS business is not a special IRS category—but the way you sell software (subscriptions, licenses, usage fees, or professional services) affects which treaty articles you claim in Part III and how payers classify each payment.

Most foreign SaaS companies are legal entities—a GmbH, Ltd., S.L., BV, or LLC—not individual founders. When the contract party, bank account, and tax onboarding name match that entity, Form W-8BEN-E is the certificate, not Form W-8BEN. The hard part is translating your local company type into Chapter 3 status on Part I, Line 4, choosing the right FATCA box on Line 5, and completing Part III only when your facts support a treaty rate.

This guide covers when a SaaS company needs W-8BEN-E, Corporation vs. LLC on Line 4, Active NFFE on Line 5, royalty vs. service income, Part I and Part III, and what Stripe, AWS, app stores, and enterprise buyers expect. Outcomes depend on your structure and country of residence—this page explains mechanics, not individualized tax or legal advice.

Ready to map your SaaS entity to Line 4 and Line 5 without guessing? Start the W-8BEN-E wizard on W8GetEasy ($30, downloadable PDF after guided questions).

When does a SaaS company need W-8BEN-E?

Form W-8BEN-E is the IRS certificate of foreign status for entities that receive U.S.-source income and want to document their tax classification to a withholding agent. A foreign SaaS company needs W-8BEN-E when the legal entity—not the individual founder—is the payee on the contract, vendor record, or payout account. U.S. payment platforms and enterprise customers act as withholding agents: without a valid certificate on file, they may apply backup withholding—commonly up to 30%—on reportable amounts.

• Entity is the customer of record: Your GmbH, Ltd., S.L., or LLC invoices U.S. customers, holds the Stripe or bank account, and appears on marketplace tax forms—not the founder personally.
• U.S.-source income flows through U.S. rails: Subscription revenue via Stripe, AWS Marketplace listings, App Store or Google Play payouts, affiliate programs, or direct ACH from a U.S. buyer can trigger documentation requests even when your team works entirely outside the United States.
• Not a substitute for a U.S. tax return: W-8BEN-E goes to the payer, not the IRS. It tells the withholding agent which documentation rules and rates apply before net proceeds reach your account.
• Founders still use W-8BEN: If only the individual receives payment in a personal name, Form W-8BEN may apply instead. See our W-8BEN vs W-8BEN-E comparison when a platform dropdown lists both.

Official instructions are on the IRS W-8BEN-E page. See our complete W-8BEN-E guide for businesses for the full certificate.

Which Chapter 3 status applies: Corporation vs. LLC

Part I, Line 4 is Chapter 3—your entity type for U.S. withholding. For SaaS companies, the correct box follows U.S. federal tax classification of the legal entity on the contract, not whether you sell software. Most foreign SaaS vendors fall into one of three patterns:

• Foreign corporation (GmbH, Ltd., S.L., S.A., BV, K.K.): typically Corporation on Line 4. See our W-8BEN-E for corporations guide for Line 4 and Active NFFE pairing.
• Foreign LLC with one owner disregarded for U.S. tax: the owner entity certifies on Line 1; the LLC may appear on Line 3. Line 4 reflects the owner's status—often Corporation for a corporate parent. Full walkthrough: W-8BEN-E for LLCs.
• Foreign LLC with two or more members or partnership classification: usually Partnership on Line 4, not Corporation— even when the product is software.
• U.S. single-member LLC under a foreign parent: the foreign corporation certifies; the U.S. LLC is commonly the disregarded payment recipient on Line 3, not the Chapter 3 box on Line 4.

FATCA status for SaaS companies (Active NFFE is most common)

After Line 4, Line 5 asks for your Chapter 4 FATCA classification. Most operating SaaS companies that build and sell their own software—not passive holding shells—qualify as Active NFFE when they meet the form's passive income and passive asset tests. You certify in Part XXV that the entity runs an active trade or business and is not a financial institution.

Active NFFE is not automatic because you write code. IP holding companies or groups where more than 50% of income is passive may need Passive NFFE instead—triggering Part XXVI and owner disclosures. Product-led SaaS with subscription revenue usually analyzes Active NFFE first.

Revenue types that trigger withholding (royalties vs. service income)

U.S. payers classify each payment type before applying a treaty rate from Part III. SaaS income is not one label—platforms and enterprise AP teams may treat the same product as business profits, royalties on software licenses, or fees for services depending on contract language and product delivery model.

• SaaS subscriptions and usage fees: Often treated as business profits when you provide access to a platform you operate, with no U.S. permanent establishment. Many treaties allow 0% withholding on Article 7 business profits when facts support that classification and Part III is completed correctly.
• Software license royalties: Downloads, white-label licenses, or revenue shares classified as copyright or know-how royalties may fall under treaty royalty articles (often Article 12). Rates vary by country—verify against current IRS treaty tables before signing.
• Implementation and professional services: Onboarding, custom development, training, or support billed separately may be service fees. Match Part III to the income type the payer reports—not only the product marketing name on your website.
• Marketplace payouts: AWS Marketplace, App Store, and Google Play withhold on amounts they remit. Treaty claims must align with how each platform classifies seller income.

How to fill Part I and Part III

Part I establishes who the entity is and how it is classified for Chapter 3 and Chapter 4. Part III documents treaty benefits when a reduced withholding rate applies. For SaaS companies, accuracy on identity fields prevents onboarding delays; accuracy on Part III prevents wrong withholding on subscription and license revenue.

Enter information exactly as it appears on formation documents, your Stripe or marketplace seller profile, and bank KYC. Even small name differences between the form, contract, and payout account are a common reason payers reject certificates or leave backup withholding in place.

• Part I — Identity and classification: Legal name, country of incorporation, address, and tax ID must match Stripe or marketplace records. Line 4 is Corporation, Partnership, or Disregarded entity per U.S. rules—see our LLC guide and corporations guide.
• Line 5 — FATCA status: Active NFFE for most operating SaaS vendors; complete Part XXV. Answer the hybrid/treaty question consistently with Part III.
• Part III — Treaty benefits: Country of residence, treaty article, withholding rate, and income type (business profits vs. royalties). Claim only rates your facts support.

Step-by-step: W-8BEN-E for a foreign SaaS company

Use this sequence for a standard operating software vendor.

1. Step 1 — Confirm the entity on the contract: If the platform pays your company—not you personally—W-8BEN-E applies. Gather formation documents and U.S. classification.
2. Step 2 — Complete Part I and Line 4–5: Match identity fields to vendor records. Corporation + Active NFFE is the common path for capital companies running SaaS products.
3. Step 3 — Align Part III with payer classification: Ask how Stripe, AWS, or your customer labels subscription vs. license revenue before signing.
4. Step 4 — Sign and upload: An authorized officer signs. Deliver to the withholding agent—not the IRS. Renew when facts change or the certificate expires.

Platforms that require W-8BEN-E (Stripe, AWS, App Store, Google Play, enterprise)

Each U.S. payment channel hosts its own tax onboarding. The underlying IRS fields are the same, but timing, upload location, and how each platform classifies SaaS income can differ. Below are the patterns foreign software companies see most often.

Stripe

Stripe requests W-8BEN-E in Dashboard tax settings when you enable payouts to a non-U.S. entity. Line 4 and Line 5 must match the entity on the account—not the founder on W-8BEN. Part III should reflect how Stripe classifies SaaS subscription revenue. See Stripe W-8BEN-E onboarding.

AWS Marketplace

AWS Marketplace sellers submit W-8BEN-E during registration or tax profile updates. SaaS listings, AMI software, and professional services may be classified differently—match Part III to AWS's seller tax interview.

Apple App Store

App Store Connect prompts for W-8BEN-E when the legal seller is a company. Mobile app revenue is often treated as royalties for treaty purposes—confirm Part III against current U.S. treaty tables.

Google Play

Google Play Console requires tax documentation for foreign publishers. The entity on your payments profile must match Part I. In-app purchase revenue may use royalty treaty articles depending on your tax residence.

Enterprise U.S. customers

U.S. enterprise buyers request W-8BEN-E during vendor onboarding in Coupa, Ariba, or AP portals—often before the first invoice. Send a signed PDF to accounts payable, not the IRS. Ask how AP classifies your contract: hosted SaaS vs. licensed software.

Platform flows and treaty rates change. Verify current IRS instructions before signing; consult a qualified tax adviser for complex structures.

Where to go next

SaaS tax onboarding is entity classification first, income type second, platform upload third. Use these resources when your structure or revenue mix differs:

• W-8BEN-E for corporations: Line 4 and Active NFFE
• W-8BEN-E for foreign LLCs and disregarded entities
• W-8BEN-E wizard on W8GetEasy

Common W-8BEN-E mistakes SaaS companies make

• Submitting W-8BEN for the founder instead of W-8BEN-E for the company: When Stripe or a customer pays your GmbH or Ltd., the entity form applies. Individuals use Form W-8BEN.
• Checking Corporation because you are a "tech company": Line 4 follows U.S. tax classification. Multi-member LLCs are often Partnership, not Corporation.
• Using Passive NFFE for an active SaaS product business: Triggers unnecessary FATCA disclosures. Review the 50% passive income and asset tests before checking Line 5.
• Claiming the wrong treaty article for subscription vs. license income: Article 7 business profits and Article 12 royalties carry different rates. Match Part III to payer classification.
• Skipping Part III while expecting 0% withholding: Line 4 and Active NFFE do not by themselves reduce tax. Treaty benefits require a valid Part III claim.

Frequently asked questions about W-8BEN-E for SaaS companies

For most foreign SaaS companies, the path is W-8BEN-E with the correct Chapter 3 box on Line 4, Active NFFE on Line 5 for operating businesses, Part XXV certification, and Part III only when a valid treaty claim exists. Match every line to formation documents, how each payer classifies your revenue, and the entity name on Stripe or marketplace accounts.