Handling VAT on platform billing: a practical guide for European platforms
Learn how European platforms manage VAT on payment-related fees. Explore the tax rules, Connect Billing, and how to reconcile Mollie transaction reports.
Learn how European platforms manage VAT on payment-related fees. Explore the tax rules, Connect Billing, and how to reconcile Mollie transaction reports.
Luke Rynne Cullen
Senior Product Marketing Manager
Mollie and its affiliates do not provide tax, legal, or accounting advice. This material has been prepared for informational purposes only.
When you scale a software-as-a-service or marketplace platform, the initial focus stays locked on growth: onboarding users, refining the product, and expanding into new territories. However, the moment you implement a monetisation strategy like adding application fees or a margin to your agreed buy rates via Mollie Connect, you must consider the tax implications of this new revenue stream.
If your platform invoices merchants for payment-related fees, you need to know whether to add VAT to those invoices and, if so, exactly how much. This is not an academic exercise. If you treat these charges as exempt when they are legally taxable, your platform can incur significant back taxes and penalties during an audit.
This guide delivers a practical operational blueprint for platform finance and product teams. We will cover why VAT applies to your platform fees, how to structure your onboarding stack, how to manage cross-border variations, and how to build a reliable monthly reconciliation workflow.
Why do application fees attract VAT?
A common misconception among finance teams is that any fee tied to a payment transaction automatically qualifies for VAT exemption. This belief comes from a misinterpretation of Article 135 of the EU VAT Directive (2006/112/EC), which exempts certain financial transactions, including the execution of payments, transfers, and the management of credit.
However, the European Court of Justice (ECJ) consistently rules that this exemption must be interpreted narrowly. It only covers the specific entity that directly executes the transfer of funds between bank accounts, thereby altering the legal and financial position of the parties.
As a platform, you are not a licensed financial institution moving interbank funds. We handle the regulated payment execution. Your platform provides the underlying software architecture, client support, and commercial enablement. This makes your supply a standard-rated technology service in several European jurisdictions.
Two ECJ rulings and a UK Supreme Court decision reached the same conclusion:
DPAS (C-5/17): The court ruled that sending instructions to financial institutions to execute payments is an administrative service, not an exempt financial transaction.
Bookit (C-607/14): Transmitting authorisation codes and data settlement files does not alter the financial legal status of a transaction. It remains a taxable tech service.
Target (UK Supreme Court): The court reaffirmed that only the specific entity moving money from one ledger account to another qualifies for the financial exemption. Simply issuing instructions or managing an interface is fully taxable.
The core lesson is clear: the label you print on your invoice (payment processing fee or transaction commission) does not dictate the tax treatment. The economic substance of what you provide does. Because you may be providing a software interface that connects merchants to a payment provider, you could be classified as supplying a standard-rated technology and enablement service, which is subject to standard VAT.
The calculus of the taxable base: full fee versus markup
Once you establish that your fees are taxable, you must address a critical question: Do you calculate VAT on the full fee amount invoiced to your merchant, or only on the markup you make above our base cost?
The answer usually is to apply VAT to the full amount you invoice a client for.
Consider this operational loop. Your platform uses a resell pricing model. For a single transaction, we charge your platform a base fee of €1.00. You choose to charge a merchant €1.50 for that same transaction, retaining a €0.50 margin. When you generate an invoice for that merchant, the taxable base is the full €1.50.
Your relationship with us is an entirely separate business-to-business (B2B) transaction. We invoice your platform for the baseline processing costs, and you may be able to reclaim any input VAT associated with those costs through your VAT return.
To help finance teams track this variance, we provide the Transaction Margin Report within your Mollie Dashboard. This report shows data at the individual transaction level, highlighting the buy rate (our cost to you) and the application fee (what your business paid). While this report is invaluable for tracking your net revenue and margins, your forward invoicing engine must always treat the gross application fee as the taxable amount.
The onboarding blueprint: data collection and verification
To automate your tax workflows without experiencing operational friction, you must capture specific data points during your business onboarding programme. If you wait until the end of the financial quarter to classify your users, your platform will suffer data gaps and compliance failures.
At the point of registration, your platform stack must collect four critical compliance blocks:
The legal entity name and trading address: This establishes the physical presence of the business.
The country of establishment: This is the primary anchor that determines which country’s tax jurisdiction applies.
The corporate business status: You must confirm whether the user is a commercial business (B2B) or an unregistered entity.
A valid VAT identification number: For European entities, this is the definitive proof of B2B status.
The moment a merchant inputs its VAT number, your system should automatically validate it using the European Commission’s VIES (VAT Information Exchange System) API. This step is non-negotiable for cross-border trade and is something that Mollie does automatically during onboarding.
An unverified VAT number creates an immediate exposure. If you apply the reverse charge mechanism to an invalid VAT number, your local tax authority can treat that transaction as a domestic sale and demand the missing output VAT from your balance sheet. Your onboarding database should log the VIES confirmation timestamp and store it as a permanent audit trail.
The three invoicing scenarios shaping European operations
Once your onboarding workflow verifies a business's location and tax status, your billing engine can route it into one of three standard invoicing profiles.
Scenario A: Domestic businesses
If your platform is established in the Netherlands and your business is also registered there, you are dealing with a domestic transaction. You should apply the standard Dutch VAT rate of 21% to the full net fee amount.
If a German platform invoices a German business, the platform must apply the standard 19% Umsatzsteuer. There are no exemptions or cross-border loops here. You collect the tax from the business and remit it to your local tax office through your routine filings.
Scenario B: Intra-EU B2B merchants
If your company is based in Amsterdam and you supply services to a verified, VAT-registered business in Paris or Berlin, the transaction qualifies as an intra-EU cross-border B2B service supply.
Under the place-of-supply rules set out in the EU VAT Directive, the service is taxed where the customer is established. This allows you to deploy the reverse charge mechanism.
Your invoice will show the net fee amount with a 0% VAT rate. Crucially, the invoice must display both your VAT number and the customer’s validated VAT number, alongside a clear legal notation. Invoices typically need to reference the explicit text: “VAT reverse charge applies, Article 196 Council Directive 2006/112/EC.”
This shifts the administrative obligation to the business, which self-accounts for the local VAT on its own tax return.
Scenario C: Non-EU merchants
When your platform invoices merchants established outside the European Union – such as the UK, Switzerland, or Norway – the supply falls entirely outside the scope of EU VAT.
You issue the invoice with 0% VAT. Your system must apply an invoice notation indicating that the transaction represents a service provided to a non-EU recipient.
Keep in mind that while the transaction is exempt from EU VAT, the business's home country will usually require them to self-assess tax under their local imported-services framework, such as the UK reverse charge rules or the Swiss Bezugsteuer.
Automate your platform billing
Let Mollie Connect Billing automate the generation of compliant invoices detailing the application fees processed by your merchants on a monthly cadence.
Different lines of platform revenue are subject to distinct tax treatments. The matrix below outlines how the standard rules apply to the common revenue streams generated by platforms that use Mollie Connect.
Fee type
VAT status
Taxable base
Operational justification
Application fees (markups or commissions)
Taxable at the standard rate
The total gross fee charged to the business
You are supplying a technology interface and commercial onboarding software. We handle the regulated fund transfer.
SaaS subscription fees
Taxable at the standard rate
The recurring subscription price
This represents an electronically supplied service, which is universally taxable.
Chargeback or dispute fees
Taxable at the standard rate
The fixed administrative fee
Administrative costs linked to payment friction do not qualify for the financial services exemption.
Anatomy of a compliant platform invoice
Mollie Connect Billing supports your payments infrastructure by automating invoice generation from your platform to your merchants. To ensure these documents survive a tax audit anywhere in Europe, our billing template includes these 10 mandatory components:
Your platform’s full legal corporate name and registered business address.
Your platform’s official VAT identification number.
The business’s registered corporate name and billing address.
The business’s validated VAT identification number (mandatory for cross-border transactions).
A unique, automated, and strictly sequential invoice number.
The precise invoice date and the tax point date (if different from the issuance date).
A clear, descriptive itemisation of the supply (e.g., “Payment processing services for March 2026”).
The total net taxable amount, categorised by currency.
The applicable VAT rate is applied per line item, and the resulting total VAT amount is calculated.
For all cross-border EU invoices, the explicit statement: “VAT reverse charge applies – Article 196 Council Directive 2006/112/EC.”
The digital reporting shift: e-invoicing is no longer optional
The days of relying on a basic PDF invoice sent via an email attachment are coming to an end across Europe. Governments are aggressively migrating toward structured, machine-readable e-invoicing to combat fraud and close the continent’s multi-billion-euro VAT gap.
An e-invoice is a highly structured data file, typically formatted in XML, transmitted over a secure network like Peppol. It bypasses human inboxes and lands directly inside the recipient’s accounting ledger for automated validation.
[Platform Billing Engine] --> (Structured XML file via Peppol access point) --> [Business Accounting Ledger]
The shift to e-invoices is taking place throughout Europe. As of the time of writing this article, Belgium has legislated mandatory B2B e-invoicing starting on 1 January 2026. France will follow with a phased rollout beginning in September 2026, and Germany has established a mandatory framework starting in January 2027.
These localised initiatives align with the European Commission’s broader VAT in the Digital Age (ViDA) package, which aims to standardise digital reporting and eliminate traditional paper-based documentation for all intra-EU trade by 2030.
If your platform serves businesses in these regions, you must ensure your invoicing output can produce compliant, structured data feeds that meet local specifications.
Regional nuances across fragmented markets
While the EU VAT Directive provides a shared framework, individual countries introduce unique complexities that impact how you manage your platform operations. To cross-reference specific rates across the 30 countries mentioned here, finance teams can consult the PwC Worldwide Tax Summaries.
With Mollie, you can send structured e-invoices via the Peppol network. We handle all the technical heavy lifting – registering you in the relevant network, converting your billing data into the required XML format, and routing it securely to your customer’s access point.
Denmark
Denmark presents a distinct challenge for platforms with a standard VAT rate of 25%. If you attempt to treat your payment fees as VAT-exempt financial services, the Danish tax authority (Skattestyrelsen) can levy a specific payroll tax known as lønsumsafgift.
This tax can reach up to 15.3% on all corporate wages linked to your exempt financial activities. For the vast majority of software platforms, charging the standard 25% moms on your gross payment fees is significantly simpler and eliminates this payroll tax risk.
Finland
Finland retains one of the highest standard tax rates in Europe. The country adjusted its operational landscape by increasing its standard VAT rate from 24% to 25.5%. Your platform’s billing rules must reflect this precise fraction to avoid reporting discrepancies.
Italy
Italy operates a strict, centralised digital reporting framework called the Sistema di Interscambio (SDI). Every single domestic B2B invoice must be converted into a specific XML format known as FatturaPA and routed directly through government servers.
A PDF generated outside the SDI network carries zero legal weight in Italy. If you invoice Italian merchants domestically, your system must integrate with the SDI channel.
Germany
Germany applies a standard 19% Umsatzsteuer (value-added tax, VAT) to software services. For early-stage platforms, Germany offers a small business exemption (Kleinunternehmerregelung) if your total taxable revenue remains below a threshold of €25,000 per year.
If you opt into this status, you do not collect VAT from your users, but you also surrender your right to reclaim any input VAT on your bills.
Hungary
Hungary features the highest standard VAT rate inside the European Union at 27%. The Hungarian tax authority mandates real-time data reporting (RTIR) for invoices. This means your platform’s backend infrastructure must programmatically report transaction data directly to the government’s NAV system immediately after an invoice is generated.
The monthly reconciliation playbook: running a tight finance operation
This routine applies to platforms using Connect Billing to invoice their merchants. If you're generating invoices through your own billing system, run the equivalent checks against your own invoicing records.
Reconciliation is where your billing, tax, and accounting records come together. Five steps, first week of the month.
1. Download the reporting data
Once the period closes, pull the Transaction Margin Report from your Mollie Dashboard (Reports tab). It gives you the transaction-level detail your finance team needs on application fees, Mollie's transaction costs, and the related VAT amounts.
2. Review merchant tax classifications
Isolate the Client Country Code column within the report. Group your transactions by customer jurisdiction. This grouping allows you to verify that your billing software has routed each business into the correct tax track (Domestic, Reverse Charge, or Non-EU).
3. Record the period's activity in your accounts
Use the Connect Billing invoices together with the Transaction Margin Report to post the period's fee revenue, VAT, and costs. The invoices are the billing documents your merchants receive. The report gives you the transaction-level detail behind them for your own reporting and reconciliation.
4. Process merchant information changes
Review any changes to registered addresses, countries of establishment, or VAT numbers. A merchant may have relocated, or provided a VAT ID they didn't have at onboarding. Update the classification before the next invoicing cycle runs, so future invoices carry the right treatment. Changes applied mid-cycle are messier than changes applied at the start of one.
5. Review your input VAT position
Collect the invoices we issued to your platform covering your baseline buy-rate costs. Use the Transaction Fee and Transaction Fee VAT Amount columns from the Transaction Margin Report to match our charges against your accounts payable ledger. Whether your business is eligible to recover VAT on these costs depends on your specific situation. Please consult a qualified tax advisor to understand your tax position.
Your operational setup checklist
Before you run your next billing run, verify that your platform team has completed these 10 core requirements:
Verify your platform’s current VAT registration status and record your official VAT identification number.
Integrate automated fields for country and VAT number collection into your business onboarding funnel.
Wire your registration stack to the VIES API to validate business VAT numbers programmatically at onboarding.
Build an automated storage system to log VIES verification dates and confirmation tokens as an audit trail.
Configure your invoicing template to display both your platform’s VAT number and the business's VAT number.
Apply the mandatory legal notation text to all cross-border EU reverse charge invoices.
Structure your pricing matrix to calculate VAT on the gross fee invoiced to the business, rather than the net markup.
Implement an automated monthly routine to cross-reference your Transaction Margin Reports against your invoices.
Audit your target customer base to ensure your technical stack can support country-specific e-invoicing formats.
Schedule an independent review with a qualified regional tax advisor to validate your tax setup.
Reduce the operational work with Connect Billing
Managing VAT rates, cross-border reverse charges, and e-invoicing mandates can quickly drain your operational resources. You do not have to build and maintain this infrastructure from scratch.
Mollie Connect Billing handles the heavy lifting of your platform’s invoicing. Our infrastructure automatically applies your configured pricing rules, generates compliant invoices, and provides the transparent margin reporting your finance team needs to close the books efficiently each month.
Do I need to register for VAT in every country where my merchants are located?
No. If you operate a standard B2B model and your cross-border merchants have valid VAT numbers, you may not need local tax registrations, depending on the goods and services you provide. You may apply the reverse charge mechanism, which transfers the reporting obligation to the business. However, if you deliberately sell to non-registered entities or open physical corporate offices abroad, you may trigger local registration requirements.
Can I structure my platform fees as a pure pass-through to avoid charging VAT?
This is rarely permissible in a commercial platform environment. To qualify as a tax-free pass-through, you must pay the underlying expense in the exact name and for the exact account of the business, with zero markup, zero commercial margin, and zero alteration of the service. Because the Mollie Connect model involves adding a commercial margin or software markup, the full fee represents a taxable forward supply.
My merchants are partially VAT-exempt (such as healthcare providers or charities). How do I handle their concerns about VAT on fees?
Businesses operating in healthcare, education, or charitable sectors cannot fully reclaim input VAT. For them, your VAT charge represents a direct, non-recoverable cash cost. This is a commercial negotiation rather than a tax variable. You cannot omit legally required VAT to accommodate a business's tax profile; doing so transfers the financial liability directly to your platform.
Does Mollie Connect Billing automatically calculate my VAT liabilities?
Connect Billing calculates and records VAT based entirely on the specific country profiles, tax rules, and merchant overrides that you configure within your system. Your platform retains full legal responsibility for determining the correct tax treatment. We provide the infrastructure, but your finance team holds the pen.
What records should we keep to defend our platform during a tax audit?
European tax authorities generally require you to retain all relevant records for a minimum of seven years, though countries like Germany require 10 years for digital accounting assets. You must archive all invoices issued via Connect Billing, all incoming invoices from us, your historical VIES verification logs, and your monthly Transaction Margin Reports.
What changes when my platform merchants are based in the United Kingdom or Switzerland?
Post-Brexit, the United Kingdom operates outside the EU VAT ecosystem, while Switzerland relies on its own independent framework. You do not use the EU reverse charge legal references on these invoices. You categorise the transactions as outside the scope of EU VAT. The merchant will typically self-account for their local tax using the UK reverse charge rules or the Swiss Bezugsteuer protocols.
Let Mollie Connect Billing automate the generation of compliant invoices detailing the application fees processed by your merchants on a monthly cadence.
Whether you want to grow internationally or focus on a specific
market, everything is possible. Mollie supports all known payment methods, so you can grow your business regardless of location.
