Transfer Pricing for Solo Founders: What to Document

Transfer pricing is one of those areas everyone assumes only matters to multinationals. Companies with thousands of employees, dedicated tax departments, intercompany transaction volumes in the billions. The entire regulatory infrastructure (OECD Transfer Pricing Guidelines, country-by-country reporting, advance pricing agreements) was built for them.

But the rules don't contain a size filter. They trigger based on related-party transactions, not headcount or revenue. If you run a US LLC and also operate through a personal entity in Portugal, you have two related parties. Management fees, IP licensing, service payments flowing between them? All within scope of transfer pricing rules in both jurisdictions. This matters most when your entity map doesn't match your income map — that gap between where entities sit and where income actually flows is exactly where transfer pricing obligations show up. The arm's length principle has no carve-out for one-person companies.

The mismatch is real. The regulatory framework assumes you have a compliance team. You don't. Documentation expectations assume analysts producing benchmarking studies. You're both the service provider and the service recipient. The obligation exists in full legal force, but most solo cross-border operators have never heard of it, even though their structures trigger it automatically.

Key Takeaways

• Transfer pricing rules apply based on related-party transactions, not company size — a solo founder with two entities triggers them automatically.
• The arm's length principle has no carve-out for one-person companies; intercompany fees, loans, and IP licensing all require defensible pricing.
• "Documentation not required" in a jurisdiction still leaves you exposed — the authority can adjust any transaction it deems mispriced.
• Each undocumented year adds to a rolling window of exposure; retroactive reconstruction becomes harder as records age.
• Without transfer pricing documentation, two jurisdictions can independently re-price the same transaction, creating double taxation with no established basis for resolution.

When Transfer Pricing Rules Apply to Solo Founders

The Related-Party Threshold

Transfer pricing rules activate when transactions occur between "related parties" or "associated enterprises." Definitions vary by jurisdiction, but the trigger is the same: common ownership or common control.

Under OECD guidelines, two enterprises are associated if one participates directly or indirectly in the management, control, or capital of the other, or if the same persons participate in both. If you own 100% of a US LLC and an Estonian OÜ, you've met this threshold automatically. No ambiguity. One person controls both entities. Every transaction between them is a related-party transaction.

You don't even need formal corporate structures. In many jurisdictions, a sole proprietorship in one country and a company in another, both run by the same person, create a related-party relationship. No holding company required. No formal group structure. The control relationship alone is enough.

Once you operate through more than one legal entity or tax presence across borders, transfer pricing rules are triggered. The only real question is whether you know it.

Common Structures That Trigger It

These are structures I see constantly among cross-border solo operators:

US LLC plus personal income in a residence country. You live in Portugal, run a US LLC, draw income from it as distributions or management fees. That's a cross-border related-party flow. How you characterize the payment (compensation, dividend, service fee) affects tax treatment in both the US and Portugal, and the pricing of any service arrangement falls within transfer pricing scope.

Holding company plus operating company. A holding entity in Cyprus, Netherlands, or Singapore with an operating entity elsewhere. Fees, dividends, or service payments flowing between the two are intercompany transactions. Full stop.

IP-owning entity plus service-providing entity. Software, brand assets, or methodologies sit in one entity while another generates revenue from them. The licensing arrangement and its pricing fall within transfer pricing rules. The IP assignment gap analysis maps the patterns that create ambiguous ownership here. Common among SaaS founders who separated IP from operations for liability or tax reasons.

Freelance entity plus contractor entity. You invoice clients through one entity, then subcontract to your own second entity in another jurisdiction. That subcontracting fee is an intercompany transaction.

The Arm's Length Principle

The core concept: transactions between related parties should be priced as if the parties were independent, dealing at market rates. If an unrelated service provider would charge $5,000/month for equivalent management services, your intercompany management fee should approximate that figure.

Multinationals establish arm's length pricing through extensive benchmarking studies. For solo founders, the principle is identical. The practical challenge is that "founder-level management of a one-person entity" has few directly comparable market transactions. That doesn't eliminate the obligation. It makes documentation harder to produce and more important to have.

The Five Transaction Types Solo Founders Face

Management Fees

When one entity pays another for management or strategic oversight, that's a management fee. In solo structures, this usually means an operating entity paying a holding entity (or vice versa) for the founder's time managing operations.

The tricky part: you're performing these services personally. Which entity is providing the service? Which is receiving it? That depends on where you're physically located, which entity you're acting on behalf of, and how your contracts are structured. A management fee of EUR 3,000/month from an Estonian OU to a Portuguese sole proprietorship needs an intercompany agreement specifying the services, their scope, and how you arrived at the price.

Service Fees

Service fees cover specific, defined work: development, consulting, marketing, customer support. If you write code through your US LLC but your Singapore entity owns the software, that development work is a service the US entity provides to the Singapore entity. The fee is an intercompany transaction.

This gets messy when you do everything across both entities without clear boundaries. Sales, development, admin — all through two entities. How do you allocate your time? How do you price each category? Without documentation, a tax authority in either jurisdiction will apply its own characterization. It may not match what you intended.

IP Licensing

When one entity owns IP and another uses it commercially, a licensing arrangement exists whether you've documented it or not. For SaaS founders, this is the most common pattern: software, algorithms, or brand assets sit in one entity while another generates revenue from them. The entity using the IP owes a royalty or license fee to the entity that owns it.

Comparable software licensing royalties between unrelated parties range from 5% to 30% of revenue, depending on the IP's value relative to other functions driving revenue (sales, marketing, support). If you've placed IP in one entity and revenue in another without a licensing agreement, you have an undocumented intercompany transaction.

Cost-Sharing Arrangements

One subscription to dev tools. One cloud hosting account. One contractor who works for both entities. Solo founders share costs across entities constantly, often without thinking about it.

The OECD framework expects cost-sharing to be proportional to the anticipated benefits each entity gets from the shared activity. In practice: document which entity benefits from each shared cost, then apply a reasonable allocation key. Revenue split, headcount (which is one person in both entities, so good luck with that), or usage-based metrics.

Without a cost-sharing agreement, costs get deducted by the wrong entity. Both jurisdictions can challenge the mismatch.

Loans and Capital Contributions

Your holding company funds the operating company's startup costs. Or the operating company lends excess cash back to the holding company. Either way, the loan is an intercompany transaction, and the interest rate needs to be at arm's length.

A zero-interest loan between your two entities fails this test. Tax authorities can impute interest income on the lending entity, creating taxable income you never actually received. The expected rate depends on the borrower's creditworthiness, the currency, the term, and comparable third-party lending rates.

Capital contributions (equity injections rather than loans) have different transfer pricing implications but raise their own problems, especially when a tax authority recharacterizes what you called a loan as equity.

Documentation Requirements by Jurisdiction

What a Transfer Pricing Memo Contains

A transfer pricing documentation package (called a "local file" in OECD terminology) follows the same structure regardless of entity size:

Functional analysis. Which entity does what? Which performs development, bears market risk, owns IP? For a solo founder, this means mapping functions across entities even though one person does everything.

Transaction descriptions. Each intercompany transaction with its terms, amounts, and contractual basis.

Method selection. The transfer pricing method used to establish arm's length pricing. The five OECD methods: Comparable Uncontrolled Price (CUP), Resale Price, Cost Plus, Transactional Net Margin (TNMM), and Transactional Profit Split.

Comparability analysis. Evidence that pricing matches what unrelated parties would agree to. This ranges from formal database searches (Bureau van Dijk's Orbis or similar) to simplified analyses using publicly available data.

Conclusion. A statement that intercompany transactions are priced at arm's length, supported by the analysis above.

US Requirements

The US requires reporting intercompany transactions on Form 5472 (foreign-owned US entities) or Form 5471 (US persons owning foreign entities). If you have a US LLC owned by a foreign entity, or own a foreign corporation, your filing obligations include disclosure of intercompany transactions.

There is no revenue threshold. Section 6662(e) of the Internal Revenue Code imposes penalties for transfer pricing adjustments unless you maintained contemporaneous documentation. "Contemporaneous" means the documentation existed when you filed your tax return, not something you created after an audit begins.

EU Requirements

European jurisdictions vary widely. Portugal requires transfer pricing documentation for entities exceeding roughly EUR 3 million in net revenue, but the arm's length pricing obligation applies regardless of size. Estonia applies transfer pricing rules without a specific revenue threshold, though simplified documentation may be accepted for smaller entities. The Netherlands follows the OECD framework closely and expects documentation for all material intercompany transactions.

This variation is the problem. A transaction below the documentation threshold in one country may exceed it in the other. You're mapping compliance requirements across multiple jurisdictions simultaneously.

The Size Assumption

Most solo operators assume transfer pricing rules don't apply below a certain size. In many jurisdictions, that's wrong. The obligation to price intercompany transactions at arm's length exists independently of documentation thresholds. A country may not require a formal transfer pricing study below a given revenue level, but it retains full authority to adjust any related-party transaction it considers mispriced.

"Documentation not required" and "rules do not apply" are very different statements. The first means no filing obligation, but full exposure to adjustment. The second, which applies in very few jurisdictions, means the risk is genuinely absent. Confusing these two creates a gap most founders never see until an adjustment letter arrives.

Practical Documentation for One-Person Operations

The Simplified Transfer Pricing Memo

Your documentation doesn't need to look like the 200-page reports Big Four firms produce for multinationals. A simplified memo covering functional analysis, transaction descriptions, method selection, and arm's length justification can be 10 to 20 pages.

Three things to document: what each entity does, what flows between them, and why the pricing reflects what unrelated parties would agree to. Two entities, three transaction types (management fee, service fee, cost-sharing), a concise memo for each. That's your documentation backbone.

Selecting a Transfer Pricing Method

For service-based solo operations, two methods fit best:

Comparable Uncontrolled Price (CUP). Find comparable service arrangements between unrelated parties — freelance management consulting rates, for example — and use those prices directly. Straightforward, but requires actual comparables.

Transactional Net Margin Method (TNMM). When direct price comparables don't exist, TNMM looks at the net profit margin a comparable independent entity would earn from similar transactions. For a service-providing entity, this means showing the entity earns a margin consistent with independent service providers doing similar work.

Cost Plus also works when one entity provides services to another and the costs are identifiable. Add a markup to the cost of providing services.

Finding Comparables as a One-Person Operation

Here's the honest problem: transfer pricing comparability analysis assumes a market of independent parties performing similar functions. The market for "solo founder providing strategic management to their own entity" is thin.

Practical approaches: freelance platform data (Toptal, Upwork) for comparable hourly rates by function, published industry surveys on consulting fees, and the cost-plus method where costs are identifiable and you can justify a reasonable markup from publicly available margin data for service companies.

Perfection isn't the standard. A reasonable, good-faith effort to establish that pricing falls within the range of what unrelated parties would agree to is enough.

Documentation Frequency

Annual updates, aligned with the tax year. Material changes (new transaction types, significant shifts in revenue or cost allocation, new entities) trigger updates outside that cycle.

For solo founders, the most practical cadence is annual review alongside tax return preparation. Update the intercompany agreements and memo to reflect the actual transactions and pricing applied during the year. It's not glamorous work, but it's the kind of thing that pays for itself the moment someone asks questions.

What Happens Without Documentation

Tax Authority Adjustments

Without documentation, a tax authority can apply its own transfer pricing analysis and adjust your reported income. They can impute income you never received, or disallow deductions for payments they determine weren't at arm's length.

An adjustment in one jurisdiction increases your taxable income there. If the other jurisdiction doesn't make a matching adjustment downward, the same income gets taxed twice.

Double Taxation Risk

Two jurisdictions both taxing the same income is the primary risk of undocumented transfer pricing. Resolution mechanisms exist (mutual agreement procedures, tax treaties), but they're slow, expensive, and not guaranteed to work. For a solo founder, the cost of resolving a double taxation dispute can exceed the total tax liability at issue.

The documentation is your defense. It establishes the pricing basis and gives both jurisdictions a framework for resolution. Without it, each jurisdiction applies its own analysis independently, and the results may be irreconcilable.

The Compounding Problem

Transfer pricing exposure doesn't reset annually. Each undocumented year adds another year of potential adjustment. Five years without documentation across two entities means five years of intercompany transactions, each of which either jurisdiction can re-price. Aggregate exposure grows, and reconstructing documentation retroactively gets harder as records age.

Statute of limitations vary. The IRS has three years from filing for most adjustments, six years if there's a substantial omission of income. Most European jurisdictions have similar windows. The result is a rolling window of exposure that can reach back several years, compounding quietly the entire time.

Key Structural Observations

Transfer pricing documentation for solo founders isn't compliance theater. It's establishing a defensible basis for how income gets allocated across jurisdictions when you control every entity on both sides of every transaction.

I've watched founders build multi-entity structures across three or four countries without ever learning that transfer pricing rules applied to them. It's not willful avoidance. The compliance infrastructure that larger organizations maintain by default simply doesn't exist at the solo scale. The gap is structural.

Intercompany agreements, a transfer pricing memo, annual pricing reviews — this is one of the critical documentation elements your CPA needs to see but most founders don't have. Without it, every intercompany transaction sits in an undocumented state, open to adjustment by any jurisdiction with taxing rights over either entity. With it, you have a position. That position may be challenged, but it exists as a starting point rather than a blank page.

Transfer pricing rules are already relevant to you. The only open question is whether your documentation supports the structure you've already built.

---

Related Reading

• The Invoice Trail: How Cross-Border Income Gets Classified
• IP Ownership Across Borders: The Assignment Gap
• Entity Decision Framework for Cross-Border Founders
• When Multi-Entity Complexity Becomes Structural Liability
• The Holding Company That Doesn't Hold Anything
• The Documentation Gap: What Authorities See
• Cross-Border Compliance Checklist 2026

References

• IRS: Transfer Pricing — IRS transfer pricing examination guidance
• OECD Transfer Pricing Guidelines — OECD guidelines for multinational enterprises and tax administrations
• OECD: Mutual Agreement Procedure Statistics — MAP dispute resolution data
• IRS: Form 5472 — Information return for foreign-owned US entities
• IRS: Form 5471 — Information return for US persons with foreign corporation interests
• IRS: Section 6662(e) Penalties — Transfer pricing penalty provisions

Check your risk profile →