# Practical Sales Tax, VAT, and GST Basics for Solo SaaS Founders > A practical, non-advice guide to spotting SaaS tax obligations, tracking customer locations, and organizing registration, collection, remittance, and records. Source: https://indiefounder.me/finance/practical-sales-tax-vat-gst-for-solo-saas/ Published: 2026-11-04 Most solo SaaS founders treat sales tax, VAT, or GST as a problem that appears later, after revenue is meaningful. The surprise usually arrives earlier: a customer in a new country asks for a tax invoice, a payment processor flags a threshold, or a marketplace payout includes a deduction you did not expect. Ignoring it creates avoidable friction with customers and future cleanup work. Treating it as a full-time finance function is also unrealistic. This is an operating guide, not tax advice. Rules differ by jurisdiction, product type (SaaS is often treated as a digital service), your business entity, and whether you sell B2B or B2C. Thresholds, registration requirements, and filing frequencies change. When revenue is material, you sell into many countries, or you receive a formal notice, involve a qualified professional. The goal here is a short, consistent process you can actually run. ## When the obligation usually appears Tax collection for digital services is typically triggered by one or more of these: - You have customers in a jurisdiction that requires the seller (or a marketplace) to collect tax on digital services or SaaS once a revenue or transaction threshold is crossed. - A customer (especially enterprise or EU/UK) requests a proper tax invoice or reverse-charge documentation. - Your payment processor or accounting tool surfaces a warning or begins withholding. - You incorporate in a place with its own registration rules and then sell elsewhere. B2B sales often allow the customer to handle the tax under reverse-charge rules if you provide the right details (your tax ID and theirs). B2C sales more often require you to collect. Pure domestic sales inside one country with a simple threshold are the easiest case; multi-country digital sales are the common complication for indie products. Illustrative example only: a founder based in one country starts selling a $20/month tool. After several customers appear in the EU, the founder needs to decide whether to register for VAT in a member state (or use a simplified scheme) and begin collecting the local rate on B2C invoices. The exact trigger and rate are jurisdiction-specific and must be verified. ## Build a simple customer and product inventory first Before changing checkout or invoices, list what you already know: - Countries (or states/provinces) where you currently have paying customers. - Rough monthly revenue from each location. - Whether those customers are individuals (B2C) or companies with tax IDs (B2B). - What your product is treated as (digital service, software download, subscription access). - Which billing system you use and whether it already supports tax calculation, tax IDs, and invoice generation. This inventory tells you which jurisdictions matter right now and which can wait. It also reveals whether your existing invoices already collect the data you will need (customer country, tax ID, billing address). Update the list monthly while revenue is growing. ## Practical steps to get operational 1. **Confirm the rules for your top one or two locations.** Use official government pages or a short conversation with an accountant who knows digital services. Note the registration threshold, the rate for SaaS/digital services, filing frequency, and any simplified schemes (for example, a one-stop registration that covers multiple countries). Do not rely on blog summaries as the final source. 2. **Decide who collects.** Options usually include: you collect and remit yourself; you use a payment processor or tax automation service that calculates and sometimes remits; or, for qualifying B2B sales, the customer self-assesses under reverse charge. For early revenue, many founders start with the processor’s built-in tax tools for the highest-volume location and handle the rest manually. 3. **Update checkout and invoices.** Collect the minimum data needed (billing country, and tax ID for B2B). Display the tax amount clearly before payment. Generate invoices that show the tax, the rate, and your tax registration number once you have one. If you are not yet registered, do not add a tax line or claim a registration number. 4. **Register only when required.** Complete the official registration for the jurisdiction that has crossed the threshold. Keep the confirmation and number in a simple folder. Many processes can be done online; some require a local agent or representative. Factor the time and any fees into your decision to enter that market. 5. **Set a remittance cadence.** Once registered, note the filing deadlines. Put a recurring calendar event and a checklist (export transactions, calculate, file, pay, save confirmation). Missing a filing is usually more expensive than the tax itself. 6. **Keep records that match what you collected.** Store the customer location, tax amount, rate, and invoice for the retention period required by the jurisdiction (often several years). Your billing provider’s export plus a simple spreadsheet or accounting tool is usually enough at small scale. Illustrative invoice fields (adapt to your system and local rules): customer name and address, your tax registration number, invoice date and number, description of the SaaS subscription, net amount, tax rate and amount, total, and any reverse-charge note for B2B. ## Common edge cases for indie products - **Free trials and discounts.** Tax is usually calculated on the amount actually charged. Document how your billing system treats $0 invoices or coupons. - **Refunds and credits.** Most jurisdictions require you to adjust the tax you previously collected. Your process should include a tax-adjusted credit note or refund record. - **Currency conversion.** Tax is typically based on the local currency amount. Note the rate your processor used. - **Marketplaces and platforms.** If you sell through a platform that is required to collect tax, confirm whether you still have residual obligations. - **Changing rates or rules.** Set a reminder to re-check the top jurisdictions once or twice a year, or when you add a new major customer country. ## What your billing system needs to support You do not need a full tax engine on day one. Minimum useful features: - Ability to attach a customer country and optional tax ID. - Tax calculation (or a clear way to add a manual tax line) for the locations you care about. - Invoice PDF or email that shows the tax breakdown. - Export of transactions with tax amounts for filing. - Support for credit notes or refunds that reverse the tax. If your current tool cannot do these, the practical path is usually to enable the built-in tax features of the payment processor you already use, or to switch the billing layer before volume grows. Adding tax logic only in a spreadsheet after the fact creates reconciliation work. ## Practical checklist before you start collecting - [ ] Customer-location inventory completed for the last 90 days. - [ ] Confirmed registration threshold and rate for the highest-volume foreign jurisdiction (official source). - [ ] Decision recorded on who will calculate and remit (you, processor, or reverse charge). - [ ] Checkout collects billing country (and tax ID for B2B) and shows tax before payment. - [ ] Invoices include the required fields once you are registered; no false registration numbers appear before then. - [ ] Refund/credit process adjusts tax. - [ ] Filing calendar events and a simple records folder exist. - [ ] Privacy Policy and Terms mention that tax may be collected where required (consistency with the rest of your legal pages). - [ ] You have a named accountant or advisor to contact when the next country appears or revenue jumps. ## Common pitfalls - Adding a tax line on invoices before you are actually registered. - Collecting tax but never filing or remitting it. - Treating every country the same and missing a simplified scheme that would have reduced work. - Storing customer tax IDs without a clear retention and deletion story that matches your Privacy Policy. - Relying on a customer’s claim that “they will handle tax” without keeping the documentation that supports reverse charge. - Letting the tax process live only in your head so it breaks when you are offline. ## When the simple approach is no longer enough Revisit or seek professional help when: - You have material revenue in three or more countries with different rules. - A jurisdiction sends a registration notice or assessment. - Enterprise customers require specific tax invoice formats or certifications you cannot produce. - You add physical goods, downloads with different classifications, or usage-based pricing that complicates the tax base. - The time spent on filings exceeds a few hours per month and automation or an accountant would be cheaper. Until then, an honest inventory, registration only where required, clear invoices, and a recurring filing habit will cover most early solo-SaaS situations. The process should describe the customers and billing system you have today, not the multi-country operation you might build later. Accurate tax handling is mostly operational consistency. When the amount on the invoice, the amount in your processor export, and the amount you remit all match, you spend less time reconciling and more time on the product.