SaaS taxes for people who would rather not think about taxes

What this is, and what it is not

This is a map, not advice. The goal is that you finish it knowing which categories of obligation exist for a software business and which questions to take to someone qualified, so that the hour you spend with an accountant is efficient rather than exploratory.

We are deliberately not giving you percentages, thresholds or registration limits. Those depend on your country, your structure and where your customers are, they change, and a confidently stated incorrect number is considerably worse than no number. Every article that gives you one is either writing for a single jurisdiction without saying so, or guessing.

The set-aside habit

The single most useful financial habit for a solo founder has nothing to do with understanding tax law. It is this:

1. Open a second account at the same bank. It does not need to be anything special.
2. Ask an accountant, once, what percentage to set aside for your situation. This is a short conversation and it is the single highest-return question you will ask them.
3. Move that percentage the day money lands. Every payout, without exception, without deciding each time.
4. Never touch it. It is not your money. It has never been your money. Treating it as a buffer for a slow month is how founders end up owing an amount they have already spent.

The reason this matters more than any amount of tax knowledge is that the failure mode is almost never misunderstanding the rules. It is having spent the money before the bill arrived. A founder who set aside slightly the wrong percentage is fine. A founder who set aside nothing has a genuine problem regardless of how well they understood the rules.

Do the same with the processor fees if you find revenue numbers flattering. The number that matters for planning is what actually arrives, after fees and after the set-aside.

I’m not pretending it’s truly profitable yet. That number doesn’t include payment fees, taxes, or the hundreds of hours I’ve spent building it.

via r/SaaS

The one that actually catches software founders

Income tax is comparatively easy: you earn money, you declare it, you pay. Most founders manage it. The thing that produces genuinely nasty surprises for software businesses specifically is consumption tax on digital services, which shows up as sales tax, VAT, GST or their local equivalents.

Here is the structural problem, in one sentence: for digital services, many jurisdictions determine the tax by where your customer is, not where you are.

What that means in practice:

1. A subscription sold from your bedroom to a customer in another country may create an obligation in that country.
2. Those obligations can attach with no physical presence, no office and no local bank account.
3. Registration thresholds differ everywhere, and in some places for digital services there is effectively no threshold at all.
4. The customer’s location has to be determined and evidenced, which means your payment setup needs to capture and keep it.
5. Liability is generally backdated to when the obligation arose, not to when you found out about it. This is the part that hurts.

The practical implication is that "I will sort out tax once I am making real money" is a worse plan for a software business than for most others, because by the time the revenue is real the unregistered history exists. You do not have to solve it perfectly on day one. You do have to know which of two paths you are on before you take the first international payment.

Merchant of record, and why small teams use one

There are broadly two ways to take money, and the difference is not the checkout page:

The higher percentage looks expensive until you price the alternative, which is multi-jurisdiction registration and filing for a business whose median peer makes $145 a month. For a great many small software businesses the merchant-of-record cost is lower than the accounting work it removes, and considerably lower than the cost of getting it wrong.

The trade-offs are real and worth knowing: a larger cut, less direct control of the customer payment relationship, another party in your refund and dispute flow, and a dependency to consider if you ever sell the business. Founders discuss these choices constantly in public, and the practical detail in those threads, on review timelines and payout behaviour, is often more useful than vendor documentation.

When to get actual help

Earlier than most founders do, and for less money than they fear. The triggers:

1. Before your first international sale. This is the one. An hour here is the cheapest insurance available.
2. When you choose your business structure. The decision is much cheaper to make correctly than to change.
3. When revenue becomes regular. Not large, regular. Recurring revenue is what turns occasional questions into recurring obligations.
4. Before you hire anyone, including a contractor overseas. Employment and contractor classification is its own category of expensive mistake.
5. Before you sell the business. Diligence surfaces every historical tax decision you made, and unregistered obligations reduce what a buyer will pay or kill the deal.

Come to that first conversation with specifics: what you sell, whether it is a subscription, where your customers are, how you take payment, your rough monthly revenue, and what other income you have. Bring those and an hour is enough. Arrive with "I built an app, what do I do" and you will pay for an hour of the accountant working out what you do.

Then get back to the work. Tax is a solved problem that someone else can solve for you, which makes it a poor use of the attention that could go into the product.

BigIdeasDB Research. (2026). SaaS taxes for people who would rather not think about taxes. BigIdeasDB. Retrieved from https://bigideasdb.com/guides/saas-taxes-for-solo-founders