Making your own VAT on Digital Services sounds like something you’d hear in a tax seminar that runs a bit late. But it’s actually a practical question: when you sell or provide digital services across borders, who charges VAT, how do you report it, and what does “internet tax” have to do with any of this?
Below is a clear, grounded guide to VAT on digital services, with emphasis on how businesses typically handle VAT “themselves” (instead of waiting for a platform to do everything). I’ll also explain what people commonly mean by internet tax in this context, and why the rules tend to catch otherwise tidy businesses off guard.
What “Making your own VAT on Digital Services” really means
In everyday terms, VAT on digital services is about charging the right tax to the right customer, then reporting and remitting it to the right tax authority.
“Making your own VAT” usually refers to one (or more) of these situations:
- You sell digital services directly to customers (not through a marketplace that handles VAT reporting for you).
- You’re responsible for determining the correct VAT rate and VAT location (often the customer’s location).
- You must file VAT returns yourself, whether in your home country or via a special registration process.
- You need to build billing systems, invoices, and recordkeeping so VAT is calculated correctly every time.
If you sell through a platform (like a large app store or reseller), the platform may handle certain VAT obligations. If you sell directly, the tax obligations land squarely on your shoulders. It’s not always dramatic, but it is very procedural.
Internet tax: the phrase people use, not the one tax offices use
“Internet tax” is a catch-all term. Politicians, journalists, and business folks often use it to mean “taxing online activity.” In practice, that usually includes VAT/GST on cross-border digital services.
The reason it’s discussed so much is simple: digital services cross borders without shipping anything physical. Once regulators realized the tax base was shifting, lawmakers responded with VAT rules that make it harder for businesses to avoid VAT by selling “online.”
So when you hear internet tax, think: “VAT rules for online services” more than some separate new tax category.
Core VAT concepts you need before you compute anything
Before you touch rates or filings, you need three building blocks: place of supply, customer status/location, and taxability of the service.
VAT is not a general sales tax
VAT is a consumption tax, which means it’s designed to be paid by the final consumer (or end user) and collected along the supply chain. For businesses, VAT can often be recovered via VAT input credits, depending on local rules. For cross-border digital services, the “final consumer” concept shows up in where tax is charged.
Place of supply for digital services
For many digital services, the place of supply (where VAT is due) is tied to the customer’s location rather than your business location. That’s one of the reasons cross-border sales become a VAT puzzle: you calculate based on customer location, not where you’re sitting.
Rules can vary by service type and customer type, but the overall direction in most places is the same: tax the service where the customer is established or located.
B2C vs B2B is not a trivia question
VAT treatment often changes depending on whether you sell to:
- B2C (business to consumer): the customer is typically an individual end user.
- B2B (business to business): the customer is another business (often with a VAT number).
For B2C, many regimes require VAT to be charged based on customer location. For B2B, reverse-charge mechanics may apply more often, but not always in the way people guess.
Which digital services count for VAT purposes
A common mistake is assuming “digital service” is the same thing as “anything online.” Tax rules use a narrower set.
In most VAT systems, digital services include categories like:
- Electronic services (downloads, streaming, online content)
- Software access (SaaS, app access, hosted software)
- Online advertising services
- Online platforms that provide listings or access to digital resources (depending on structure)
- Remote access to digital functionality
If you’re providing a service that’s partly digital and partly physical, you’ll need to split components where required. If you’re only providing consultancy or advice, that may not be treated the same way as a digital access service (depends on the facts and local rules). VAT is picky like that; it cares about the contract wording and the actual delivery.
Do you really need to charge multiple VAT rates?
If you’re selling to customers in multiple jurisdictions, yes, you might need to handle different VAT rates. But it doesn’t mean you need to start doing cartography on your invoices.
VAT rate selection depends on the VAT regime governing your situation. For digital services, the rate often depends on the customer’s location and the service category. Even within a single country, rates can differ by service type.
If your business uses an automated billing system, this is usually manageable. If you’re invoicing manually, it becomes an error-prone chore—like sorting socks by volume.
How businesses typically “make their own VAT” for cross-border digital services
Here, the practical workflow matters. The tax question is one part; the operational process is the other.
Step 1: Identify your role in the supply chain
Are you the supplier of record? Are you an agent? Are you reselling a third party’s digital service? These facts affect who charges VAT and who reports it.
Sometimes the biggest VAT savings come from structuring correctly at the contract and billing level. Not because “VAT is optional,” but because the rules allocate responsibility differently based on your role.
Step 2: Determine customer location (and how seriously you do it)
For VAT on digital services, location evidence often matters. Businesses typically use a combination of signals such as:
- Billing address
- Payment card billing country
- IP address location (with safeguards)
- Mobile country code (where relevant)
- Bank account details
What matters is that you can justify your system. Tax authorities don’t love “trust me, we guess.” If a VAT assessment happens, you’ll want documentation that your location determination method is reasonable and consistent.
Step 3: Classify the transaction as B2C or B2B
If you’re selling to businesses, collect VAT IDs (where applicable) and verify them if your local rules require verification. For B2C, you typically can’t expect VAT IDs, so customer location usually drives VAT.
If you mix B2C and B2B selling, you need clean onboarding logic in your systems. Many businesses end up with a mess because they treat all customers the same in the billing layer.
Step 4: Calculate VAT and generate invoices/receipts
You calculate VAT using:
- Correct VAT rate for the service and the customer location
- Correct taxable amount (net vs gross handling rules vary)
- Correct currency conversion approach (often needs to match your accounting policies)
Invoices and receipts must show VAT details in a way your jurisdiction accepts. The exact format requirements vary, but “include VAT amount and VAT rate where required” is usually non-optional.
Step 5: File returns and remit VAT
This is the part where many businesses either (a) get professional help, or (b) use a special registration mechanism to file centrally instead of registering in every country. The mechanics depend on where you’re established and where you have customers.
If you’re in the EU, many businesses use a system commonly referred to as OSS (One-Stop Shop) for certain cross-border VAT reporting. If you’re elsewhere, analogous mechanisms may exist, but the name and rules will differ.
Step 6: Keep records that survive an audit
Recordkeeping isn’t glamorous. It also isn’t optional.
You typically need to retain:
- Customer location evidence
- Service descriptions tied to tax categories
- Billing records and VAT calculations
- VAT returns filed and how amounts were derived
- Proof of VAT payments
If you can’t reconstruct how VAT was determined, you’re in for a long conversation with someone who doesn’t care that your billing system was “mostly right.”
Where the “internet tax” concern comes from in the first place
The internet made commerce frictionless. That reduced the value of old border checks. VAT systems, which were designed around physical supply chains and clear customs points, had to adapt.
Digital services created two problems:
- Tax avoidance through location: a provider might operate in a low-tax area and sell across borders.
- Administrative difficulty: without physical goods, enforcement relies on data and classification.
VAT on digital services responds by moving responsibility to the supplier and using customer location as a tax trigger. It’s a regulatory attempt to preserve tax revenues while keeping compliance manageable for legitimate businesses.
EU-style VAT logic (how it works in practice)
Even if you’re not in the EU, the EU approach often influences other VAT jurisdictions. It’s worth understanding because many businesses sell into the EU and build systems around this reality.
General direction: VAT charged where the customer is
For many electronically supplied services, the supplier charges VAT based on the customer’s country. That means you need a rate lookup and a way to tie each sale to a VAT jurisdiction.
Special reporting systems reduce registration sprawl
Instead of registering in every customer country, many companies use a central filing mechanism. You usually register once with your “identification” authority and then report VAT by customer country in periodic filings.
That’s usually less painful than dozens of local registrations, but it still requires clean data and correct filing.
Do-it-yourself VAT setup: what to build in your billing and accounting
If you’re determined to handle VAT yourself (which you can), your systems need to be able to do three things consistently:
- Determine VAT correctly at the time of sale
- Record it so you can reconcile returns
- Provide evidence if a tax authority asks questions
1) Service catalog mapped to VAT categories
Your product and service catalog should be mapped to the VAT treatment categories used by your tax engine or accountant workflow. “Our software subscription” might be clear to humans, but tax categories often require more specific classification.
Where this breaks down:
- You bundle multiple services (support, hosting, content access)
- You have add-ons with different taxability
- You change packaging over time
Keep versions and history. VAT doesn’t forgive “we changed the bundle mid-year.”
2) Customer data model that supports location and B2C/B2B
For VAT, your customer record shouldn’t be just name and email. It should store:
- Billing address (and proof it’s captured)
- VAT ID if the customer is B2B
- Determined VAT country for that transaction
- Evidence used for location determination
A lot of “DIY VAT” projects fail because developers store the location determination result, but not the evidence signals.
3) Tax calculation logic you can explain
If you use tax calculation software, make sure you can export:
- Invoice-level VAT calculations
- VAT rates applied
- Tax jurisdiction determined
- Totals by country for reporting
What you want is transparency. If someone audits you, you should be able to explain how a €29.99 subscription became a specific VAT amount.
4) Accounting reconciliation that matches VAT returns
VAT returns often require aggregated totals by country and tax rate. Your accounting system should allow reconciliation:
- Revenues by jurisdiction
- VAT output amounts by VAT treatment
- Refunds, chargebacks, and adjustments
If you handle refunds, you need VAT adjustment rules. Those are often where VAT reporting gets messy.
Handling edge cases: refunds, trials, and mixed usage
Real-world trading has less cinematic simplicity than a tax example.
Refunds and chargebacks
If you issue refunds, VAT treatment generally requires adjustment. Your systems should record:
- Original transaction and VAT booked
- Refund amount and whether it covers VAT fully
- Accounting and reporting period allocation
Chargebacks can be tricky because revenue recognition and VAT adjustments might follow different timing rules. “We refunded, but the VAT report was already filed” is the kind of mess that becomes expensive.
Free trials and converting upgrades
Free trials can create confusion if your billing engine treats trial conversions differently than paid upgrades. Often, VAT should apply at the moment a paid service is supplied. Your system must:
- Know when the service becomes paid
- Determine location at that time
- Apply correct VAT to the paid component
If you collect location evidence during the trial, keep it stored; it can matter for later VAT determination, depending on the rules.
Usage-based billing (metered SaaS)
If you charge based on usage, you still need VAT calculated for each billing period. Your taxable amount might adjust each cycle, and the VAT output should reflect the final billed amount.
The biggest practical challenge usually isn’t the math; it’s ensuring your billing ledger can reproduce what the customer was billed and which VAT country was used.
Bundles and “which component is the real service?”
When you bundle content, software access, support, and maybe some digital add-ons, VAT classification can become a debate. Some regimes classify based on the dominant supply; others look at separate supplies.
If you want to do this yourself, keep your bundles consistent and document how you classify them. If you’re constantly changing packages, your compliance cost grows faster than your revenue.
Choosing between DIY VAT and using a tax provider
This is less about morals and more about risk management.
DIY VAT is viable when
- Your product catalog is stable
- Your billing system can capture location and tax evidence
- You have someone who will maintain the logic as rules change
- Your volume is manageable enough to audit internally
DIY VAT often works well for businesses with a clean subscription model and light variation.
DIY breaks down when
- You have complex bundles with shifting components
- You sell into many countries with different reporting mechanics
- You rely on manual invoice creation
- You don’t have consistent data capture for customer location
If your compliance process depends on “someone remembering to select the right rate,” DIY is going to be a slow-motion faceplant.
Tax providers: what they usually do for you
Tax services typically handle:
- VAT rate determination by jurisdiction
- VAT calculation and invoice tax lines
- Reporting exports and aggregation
- Sometimes the filing interface (depends on service)
They can reduce error rates and save engineering time. The tradeoff is cost and vendor dependence—your compliance becomes a function of their data updates and system behavior.
Interpreting VAT rate changes and rule updates
VAT rates change. Rules change. Even if governments don’t change the world, they still change VAT tables.
A DIY setup needs a maintenance calendar:
- Monitor rate updates by relevant jurisdictions
- Update VAT mapping for service categories
- Ensure invoices and receipts reflect current rates
- Confirm reporting systems match the new logic
If you use a tax engine, rate updates are usually handled, but you still need to confirm you’re using the right product category mapping. Software won’t fix your classification choices if your catalog is wrong.
Common compliance mistakes (and why they happen)
This is the portion tax professionals enjoy because it’s a list of ways people got caught. But it’s also useful because prevention beats panic.
Mistake 1: Treating B2B like B2C
If you don’t verify VAT IDs (where required) and you charge B2C VAT to businesses that should be reverse-charged, you may create refund obligations or under/overpayment risk.
Mistake 2: Bad customer location evidence
Location signals are not just “nice to have.” They are often the basis for why you charged the VAT country you did. If you cannot show consistent evidence, calculations get questioned.
Mistake 3: Wrong service categorization
Many VAT errors come from classifying your service too broadly. A “software subscription” could be treated differently if it includes certain digital elements or if your contract describes a different type of service.
Mistake 4: Not adjusting VAT on refunds
If you refund after filing, you need an adjustment mechanism. Some businesses forget to adjust VAT until they receive regulator attention. That’s expensive learning.
Mistake 5: Poor audit trail
A VAT assessment is easier to defend when you can produce:
- transaction-level invoices
- VAT calculation outputs
- jurisdiction determination evidence
- accounting reconciliation
Without an audit trail, even “small” errors become big problems.
Example scenarios: DIY VAT in the real world
These are simplified, but the point is to show how decisions map to actions.
Scenario A: You sell SaaS subscriptions directly to customers
You sell monthly subscriptions. Customers are mostly individuals across Europe. Your workflow looks like this:
- At checkout, you collect billing address.
- You determine VAT country based on supported evidence rules.
- You apply the correct VAT rate for the SaaS digital service category.
- You invoice with VAT included (or shown separately, depending on your local invoicing approach).
- You file VAT returns periodically using a central reporting mechanism.
If you handle refunds, you adjust VAT output for refunded amounts in the relevant period.
Scenario B: You offer online advertising services to businesses
Your customers are companies, not individuals. You collect VAT IDs during onboarding and you verify them according to local requirements.
Depending on the jurisdiction and the nature of your service, you may not charge VAT at invoice level in the same way as for B2C. You still need to document customer status and supply location logic.
In either case, your system must store the customer’s VAT ID and the logic used to decide the VAT treatment.
Scenario C: You use a marketplace but also sell direct
If the marketplace handles VAT for sales made through it, you don’t automatically apply the same logic to direct sales. Your accounting and returns need to separate:
- marketplace-reported sales (where responsibility may differ)
- direct sales (where you remain responsible)
Mixing them without clear segregation is a classic “we thought it was fine” problem.
VAT records you should keep (minimum workable set)
Without going full paperwork goblin, a usable VAT file should include the ability to reconstruct VAT calculations at the transaction level.
A practical minimum set:
- Invoice/receipt copy for each transaction
- Customer location evidence used at/for checkout
- Service description and the tax mapping you applied
- VAT calculation outputs (rate, VAT amount, jurisdiction)
- Refund and adjustment records tied back to original invoices
- VAT return filings and reconciliation reports
If your system can export this, you’re already ahead of the curve.
Operational checklist for “making your own VAT” (without the checklist fatigue)
Rather than a giant list that nobody reads, here’s a more grounded ordering of tasks that tends to work.
First, confirm: What digital service category is your offering? If you don’t know how the service classifies, everything after becomes guesswork.
Second, confirm: Who is your customer (B2C or B2B) and can you collect the necessary identifiers (VAT IDs for B2B)?
Third, confirm: How will you determine customer location, and can you produce evidence later?
Fourth, implement: Billing logic that calculates VAT and produces invoice lines that match your filing requirements.
Fifth, implement: Recordkeeping and reconciliation so you can file returns without rebuilding spreadsheets at 2 a.m.
That order prevents the most common failure: implementing a VAT calculation first, then discovering your service classification or customer status logic is wrong.
FAQ: practical questions businesses actually ask
Do I need to register for VAT just because I sell online?
Sometimes yes, sometimes no. Registration requirements depend on where you’re established, where you sell, thresholds (if any), and whether you use special reporting mechanisms. Digital services are commonly treated as a place-of-supply problem rather than a physical nexus problem, so the question becomes: do you trigger VAT obligations in jurisdictions where your customers are located?
Can I just charge VAT based on my own country?
If your sales are cross-border digital services and the rules tie VAT to customer location, charging your own domestic VAT is usually wrong. The correct VAT rate and liability generally depend on the customer’s jurisdiction, not yours.
What if customers pay with cards from a different country?
That’s why tax rules allow multiple location signals and evidence approaches. Your system typically combines billing address and payment-related clues, rather than trusting one data point blindly.
Does “internet tax” mean I must pay a separate tax?
Not usually. In most discussions, “internet tax” is shorthand for VAT/GST and compliance obligations tied to online cross-border services.
Bottom line: DIY VAT is mostly a data problem
Making your own VAT on digital services is less about mastering tax theory and more about getting the operational details right: classification, customer status, location evidence, and reconcilable reporting.
If your billing and recordkeeping can explain how VAT was charged for each transaction, you’ll sleep better. The tax math matters, yes. But the audit trail matters almost as much—because tax authorities don’t run on vibes, they run on evidence.
If you tell me your target jurisdictions (for example, EU only, or EU plus a few specific countries), your business model (SaaS, downloads, coaching video, online ads, marketplace or direct), and whether you sell B2C, B2B, or both, I can outline what the most likely compliance workflow looks like for your exact setup.