2 ms·
I hate to burst your bubble...but it does matter. Not for purposes of U.S. taxes, but for purposes of whatever countries you are in while you were traveling.
by gamblor956 13y ago
I hate to burst your bubble...but it does matter. Not for purposes of U.S. taxes, but for purposes of whatever countries you are in while you were traveling. If the app is even moderately successful, those countries could treat your app's income as wholly or partially subject to their income taxes. (This is not much of an issue with Canada, EU nations, China, Hong Kong, Taiwan, or S. Korea. It is very much an issue with most other countries, especially South American and African countries.)
It depends heavily on the tax laws of the countries in which you are traveling, the type of work you perform, and the amount of such work in proportion to work performed elsewhere.
There's a reason that so many multinational companies hold their board meetings in the Caymans, with a quorum of directors physically present. It's not because the Caymans are a great vacation destination (they are) but because they must hold the board meetings there to satisfy location requirements arising from the company's tax structure. (See e.g., the Dutch Sandwich structure and the Double Irish structure.)
- toomuchtodo 13y ago> If the app is even moderately successful, those countries could treat your app's income as wholly or partially subject to their income taxes. How would you suggest they treat it as income if your business is incorporated in US (Delaware preferably)? It doesn't become foreign income based on where you wrote the code. Also, how are countries in South America or Africa going to know where your business income is derived from when all your financial transactions occur with the US?
- gamblor956 13y agoThe issue is that performing business activities in a country, under current intentional tax conventions, gives that country jurisdiction to tax the income arising from that activity. So yes, under international tax law as it currently stands, your app's income does become foreign income based on where you wrote the code. In practice, most countries require a certain "level" of activity to subject a foreign enterprise to taxation (i.e., the US and all EU nations). And at any rate, we have treaties with most countries worth visiting which generally define the type and extent of activities that could give rise to taxation in the foreign country (see, e.g., "permanent establishment"). Thus, it is unlikely that simply writing some code for your app in the EU would result in an EU nation trying to tax your app's income. However, not all nations require a substantial threshold before they try to tax business activity. Such countries will tax income arising from any activities performed in that nation by a foreign entity. (For example, Peru and Venezuela have both generated headlines about this recently.) Worse, these countries will frequently try to lay claim to all of the income that arises from the activity, even if only a minor portion of it can be "sourced" to activities performed in that country. This isn't usually a problem for a US resident/company--U.S. courts won't enforce such foreign tax levies--however, many nations are willing to enforce the tax levies of other countries. Netherlands, in particular, is a danger on this front. The Netherlands has friendly relations with a good many countries which the US is not friendly with, and a Dutch judgment enforcing a foreign tax lien stands a good chance of being enforced by other member nations of the EU. As for your second point: say you blog about how you traveled while coding the app...or you give an interview to that effect. All it takes is one person in that country's tax authority to stumble upon the blog post/interview, and they'll try to go after you. (This doesn't mean they'll go as far as seeking a judgment, or that such a judgment would succeed, but foreign legal difficulties aren't something you'll ever want to deal with if you plan on letting your app get acquired.