Tax and VAT on Podcast Subscriptions

When you take payment for a podcast subscription, you are the seller. That means sales tax and VAT are your responsibility — not Benecaster’s, and not your payment processor’s.

This page explains what that means in practice, what Benecaster gives you to handle it, and where the line falls between what is automated and what is still yours to do.

This is not tax advice. Tax law varies by country, state, and business type. What follows describes the tools available, not whether or how any rule applies to you. Talk to an accountant who understands digital goods.

---

What Changed from Patreon

Patreon acts as the merchant of record for creator subscriptions in most places. They collect VAT from EU and UK subscribers, file the returns, and remit the money. You see a net payout and the tax complexity stays invisible.

With Benecaster, payments run through your Stripe account, or through your membership plugin’s. You are the merchant. The obligation moved with the money.

For plenty of podcasters this changes nothing immediately — a small subscriber base entirely inside your own country may create no obligation at all. But if you have subscribers in the EU or UK, or you cross an economic nexus threshold in a US state, it applies to you regardless of how small you are.

---

The Built-in Membership System

If you use Benecaster’s built-in membership — subscribers pay you directly through your own Stripe account — the answer is Stripe Tax.

Stripe Tax calculates the right amount at checkout and on every renewal, based on where each subscriber is, and adds it to what you collect. It covers US sales tax, EU VAT including the OSS scheme, UK VAT, and GST in Australia, New Zealand, Canada, Singapore and elsewhere. It handles reverse charge and validates business VAT numbers, which matters if any of your subscribers pay through a company.

Setting it up

Five steps: turn on Stripe Tax, add your registrations, set a tax category on each product, switch it on in Benecaster, and test a payment.

→ Setting Up Sales Tax and VAT walks through each one.

Two things to know before you start. Tax needs both halves switched on — Stripe Tax active in your Stripe account, with a default for Include tax in prices, and Calculate tax automatically ticked in Benecaster — plus a tax category on every paid tier and buy-up. If one half is on without the other, Benecaster tells you on the Payments settings screen or in a notice, rather than leaving you to discover it. And subscribers enter their billing address in a Stripe address form on your show’s own signup page, where they see the subtotal, tax and total before paying, so there is no extra form for you to configure.

Choosing a Tax Category

Different kinds of digital product are taxed differently, so once Stripe Tax is ready in your show’s Stripe account, each paid tier and each buy-up needs a tax category. A Tax category box appears when you create or edit one, and Benecaster adds no tax to the show until every one has a category. Until then, a notice titled Choose a tax category for your tiers and buy-ups names each one still missing a category, as the tier “…” or the buy-up “…”.

Benecaster doesn’t choose for you, and that’s deliberate. The category changes what your subscribers are charged, it applies to every payment, and the responsibility for getting it right is yours. Picking a default on your behalf would mean quietly making a tax decision for you — so we ask instead.

You answer two questions: What kind of content is it? and How do subscribers get it? That’s usually enough to land on the right answer:

Every option is a subscription category, because everything you sell through built-in membership is a subscription.

One thing we can answer for you: whether subscribers keep the files. They do. A private podcast feed is downloaded by the listener’s podcast app, and those episodes stay on their device after a subscription ends — that’s simply how podcast apps work. Some tax categories distinguish between content people keep and content they only stream, so that’s worth knowing when you choose.

If you’re unsure, ask your accountant. It’s a short question for them and it applies to every transaction you take, so it’s worth getting right once rather than discovering it later.

If nothing in the list fits, choose Enter a Stripe tax code and enter any code from Stripe’s list. Choose a subscription code.

Included, or added on top?

Stripe calls this tax behaviour, and you set it in your Stripe Dashboard under Settings → Tax → Include tax in prices. It changes what people pay:

Neither of the first two is wrong. Adding tax on top means you receive the price you set, but subscribers in some countries see a higher total on your signup page than on your tier card. Including it means the advertised price is what everyone pays, and you net less from subscribers in taxed jurisdictions.

Stripe recommends Automatic, which follows what buyers in each market already expect — US and Canadian prices with tax added at checkout, everywhere else tax-inclusive.

This is a Stripe setting rather than a Benecaster one, so it applies across everything you sell through that Stripe account, and you can change it there at any time. It does need a default, though: until one is set, Benecaster adds no tax.

Registration thresholds

Stripe Tax watches your sales and tells you when you approach the point where a country or US state expects you to register. This is the most useful thing it does, because crossing a threshold without noticing is the common way small sellers end up owing back taxes.

Before Stripe Tax is on, Benecaster sends your site’s admin address one email a year per show once its membership sales pass US$1,000 (or about the same in another currency), suggesting a conversation with your accountant. It is a prompt, not advice, and it is never sent while Stripe Tax is active.

---

You Are Still Responsible for Filing

This is the part to be clear about, because automation makes it easy to assume otherwise.

Stripe Tax collects tax. It does not make you compliant. Three things remain yours:

• Registering. Stripe only collects where you have told it you are registered. In any location where you are not registered, it calculates nothing and reports no error — you simply collect no tax there. A podcaster who never registers anywhere gets a working integration that collects nothing, and nothing on screen will look wrong.
• Filing returns. Somebody has to submit them on schedule.
• Remitting the money. The tax you collected is not yours; it is held on behalf of a tax authority.

Getting any of these wrong is your liability, not Benecaster’s and not Stripe’s.

If you would rather not do it yourself

Stripe offers help with each step, at additional cost:

• Registering — Stripe can register on your behalf in the US, and through a partner elsewhere.
• Filing and remitting — Stripe can prepare and submit returns automatically in over 90 countries and every US state, with reminders before each one and copies of completed filings.

These are paid services on top of the per-transaction fee, and Stripe’s Tax plans bundle a set number of registrations and filings for a monthly price. Check Stripe’s current tax pricing before deciding — figures change.

Even with filing fully automated, the legal responsibility stays yours. You are still the registered seller; Stripe is doing the paperwork, not assuming the liability.

---

Getting Your Numbers at Filing Time

Everything Stripe Tax collects is reportable from your Stripe Dashboard, under Tax → Locations:

• Itemised exports — every transaction, broken down by jurisdiction, for places that want detail
• Summarised exports — totals per jurisdiction, which is what most country-level filings and EU OSS returns need
• Location reports — for the US and Canada, already laid out to match each jurisdiction’s own filing periods

Exports show amounts in both your own currency and the tax authority’s filing currency, so you are not converting by hand. You can have them emailed to you on a schedule.

You can also give your accountant direct access by inviting them to your Stripe account as a view-only team member, which is usually easier than emailing spreadsheets back and forth.

---

If You Use a Membership Plugin Instead

When a third-party membership plugin handles your payments, tax is handled by that plugin, not by Benecaster and not by Stripe Tax. Benecaster manages podcast feeds and access; it never sees the transaction.

Capabilities differ a lot between plugins, and they change between versions, so check the current documentation for the one you use rather than relying on a summary here:

Two questions are worth asking of any of them before you rely on it: does it handle EU VAT and the OSS scheme, not just a flat rate; and does it give you reports you can actually file from. Those are the two places coverage tends to run out.

If tax compliance is a significant concern and your current plugin does not handle it well, the built-in membership system with Stripe Tax is a reasonable reason to switch.

---

Where Tax Appears for Subscribers

Subscribers see the tax before they pay, on your signup page, and again on Benecaster’s payment receipt email. The receipt lists what the payment covers — the tier and each buy-up — then the subtotal, tax and total. If tax is included in your prices, it shows the total and the tax it includes instead.

The receipt also links to the Stripe invoice and a PDF copy. That Stripe invoice is the tax receipt, and it carries your business details — your name, address and tax registration, as you entered them in your Stripe account — because you are the merchant, not Benecaster.

So a subscriber who needs a proper tax receipt, or whose accountant does, already has one. Benecaster does not issue a competing invoice of its own.

The receipt email itself is yours to change — override subscription-receipt.php in your theme, or edit it without code if you have the Email Editor add-on.

See Built-in Membership Billing Emails for what each email contains.

---

Billing Addresses and Your Privacy Policy

Calculating tax means asking each subscriber for a billing address at checkout. It is worth knowing exactly where that address goes.

It goes to Stripe, and stays there. The subscriber types it into a Stripe address form on your signup page. It passes through your WordPress site’s server on its way to Stripe, so Stripe can work out the tax before they pay, but Benecaster does not store it or log it — Benecaster keeps no billing addresses at all. Stripe holds it, uses it to work out the right tax, and prints it on the invoice. The same is true when a subscriber updates their address on their account page.

That is deliberate. Everywhere else Benecaster is sparing with location data: when it looks up where a feed request came from, it keeps a country and region code and discards the precise location. Holding home addresses would also mean holding them for years, because tax rules require invoices to be retained long after a subscription ends.

What to put in your privacy policy: you still need to account for the address, since it is collected as part of your transaction — but you are describing data held by your payment processor, not by your website. If you already disclose Stripe as your payment processor, that may cover it. Worth checking rather than assuming.

See GDPR and Subscriber Privacy.

---

The Short Version

If you have subscribers only in your own country and are under the relevant thresholds, you may have nothing to do yet — but confirm that with an accountant rather than assuming it.

If you have subscribers in the EU or UK, it applies from your first sale, and the EU OSS scheme has no small-seller grace period for cross-border digital sales.

Turn Stripe Tax on early. It costs little at low volume, and the threshold monitoring means you find out you need to register before it becomes a problem rather than afterwards.