<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Duty27 blog</title>
    <link>https://duty27.com/blog</link>
    <description>EU VAT for developers: rates, rules and data.</description>
    <language>en</language>
    <item>
      <title>You sold to EU customers before registering for OSS. Now what?</title>
      <link>https://duty27.com/blog/eu-sales-before-oss-registration</link>
      <guid isPermaLink="true">https://duty27.com/blog/eu-sales-before-oss-registration</guid>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <description>Many digital sellers learn about EU VAT months after their first sale. What OSS covers, what it doesn't, and how to get your past sales in order.</description>
      <content:encoded><![CDATA[<p>It&#39;s a very common story. You&#39;ve been selling e-books, templates or software for a while. Sales pick up, someone on Reddit mentions EU VAT, and you realise you should have been charging it all along.</p>
<p>The good news: this is fixable, and it&#39;s a normal situation for tax advisers. The less good news: registering now doesn&#39;t automatically fix the past.</p>
<h2>First, stop the problem growing</h2>
<p>Before anything else, make new sales correct:</p>
<ol>
<li><strong>Register for OSS.</strong> If your business is outside the EU, that&#39;s the non-Union OSS: one registration in an EU country of your choice, covering all 27. If you&#39;re established in an EU country, it&#39;s the Union OSS (and below €10,000 a year in cross-border sales you may not need it yet).</li>
<li><strong>Start charging VAT</strong> at the customer&#39;s country&#39;s rate, or move to a merchant of record that does it for you.</li>
<li><strong>Collect location evidence</strong> for every sale: billing address, IP address, card country.</li>
</ol>
<h2>OSS starts from your registration, not from your first sale</h2>
<p>OSS registration normally takes effect from the first day of the next quarter. If you register by the 10th day of the month after your first eligible sale, it can apply from that first sale. Beyond that, OSS doesn&#39;t reach back.</p>
<p>So sales made before your registration are outside OSS. Technically, VAT on them was due in each customer&#39;s country under that country&#39;s own rules.</p>
<h2>Work out what you&#39;re dealing with</h2>
<p>Before deciding anything, measure it. Export your past orders and sort them:</p>
<ul>
<li><strong>by customer country</strong>, using the evidence you have (billing country is usually the best you&#39;ll get for old orders),</li>
<li><strong>by date</strong>, so each sale gets the rate that applied at the time,</li>
<li><strong>consumer or business</strong>: sales to businesses with a valid EU VAT number usually didn&#39;t need VAT from you at all,</li>
<li><strong>by product type</strong>, because e-books often have a reduced rate and templates don&#39;t.</li>
</ul>
<p>Then estimate the VAT that should have been charged, country by country. Use the rate on the date of each sale, not today&#39;s rate.</p>
<p>For many small sellers the total is smaller than feared. If you&#39;re outside the EU and sold a few thousand euros to EU consumers in total, spread across a dozen countries, the VAT involved per country can be small.</p>
<h2>Then decide, with an adviser</h2>
<p>What to do about the past depends on the amounts, the countries involved and how long ago the sales were. The usual options include registering directly in the countries where most of the past sales were, or a voluntary disclosure to their tax authorities. Each country has its own approach to penalties and interest, and coming forward voluntarily is generally treated better than being found.</p>
<p>This is the part to take to an accountant who handles EU VAT, with your country-by-country summary in hand. The preparation above makes that conversation much shorter and cheaper.</p>
<h2>What not to do</h2>
<ul>
<li><strong>Don&#39;t add past sales to your first OSS return.</strong> OSS returns are for the period they cover.</li>
<li><strong>Don&#39;t assume it doesn&#39;t matter because you&#39;re small.</strong> There&#39;s no minimum for sellers outside the EU.</li>
<li><strong>Don&#39;t ignore it and hope.</strong> EU countries share information, and since 2024 payment providers in the EU report cross-border payment data to tax authorities (the CESOP system). The obligation doesn&#39;t expire quickly either.</li>
</ul>
<hr>
<p>Duty27 calculates VAT by country and date, including past dates back to 2016, so a list of old orders can be priced at the rates that applied at the time. See the <a href="https://duty27.com/docs">docs</a> and the <a href="https://duty27.com/vat-rates/history">EU VAT rate history</a>.</p>
]]></content:encoded>
      <category>vat</category>
      <category>eu</category>
      <category>oss</category>
      <category>compliance</category>
    </item>
    <item>
      <title>Stripe Tax says &quot;threshold exceeded&quot; after one EU sale. Here is why.</title>
      <link>https://duty27.com/blog/stripe-tax-threshold-exceeded-non-eu-seller</link>
      <guid isPermaLink="true">https://duty27.com/blog/stripe-tax-threshold-exceeded-non-eu-seller</guid>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <description>If you sell digital products from outside the EU, the EU's €10,000 VAT threshold doesn't apply to you. Why one sale is enough, and what to do next.</description>
      <content:encoded><![CDATA[<p>A common surprise for founders outside the EU: you turn on Stripe Tax, make one or two sales to customers in Germany or France, and the dashboard says the EU threshold is exceeded and the country needs attention.</p>
<p>It looks like a bug. It isn&#39;t.</p>
<h2>The €10,000 threshold is only for EU businesses</h2>
<p>The EU has a €10,000 threshold for cross-border sales of digital services to consumers. Below it, a business can charge its own country&#39;s VAT instead of the customer&#39;s.</p>
<p>That rule only applies to a business established in one EU country. If your company is in the US, the UK, Canada or anywhere else outside the EU, there is no threshold. You owe VAT in the customer&#39;s country from the first sale to an EU consumer.</p>
<p>So when Stripe flags the EU after one sale, it is applying the rule correctly. It is telling you that you have an obligation, not that you crossed a limit.</p>
<h2>Which country&#39;s VAT applies</h2>
<p>The customer&#39;s. A sale to a consumer in Germany is taxed at Germany&#39;s rate, a sale to a consumer in France at France&#39;s rate, and so on. Where you or your company are based doesn&#39;t change that.</p>
<h2>You don&#39;t register in 27 countries</h2>
<p>The EU has a scheme for exactly this situation: the <strong>non-Union OSS</strong> (One-Stop Shop for businesses outside the EU).</p>
<ul>
<li>You register in <strong>one</strong> EU country of your choice.</li>
<li>You file <strong>one</strong> quarterly return there, listing your sales per EU country.</li>
<li>You pay the total in one payment, and that country passes each share on.</li>
</ul>
<p>There is also a Union OSS. That one is for businesses established in the EU, so it isn&#39;t the one you want.</p>
<h2>Timing</h2>
<p>Registration normally takes effect from the start of the next quarter. There is an exception worth knowing: if you register by the 10th day of the month after your first sale, the registration can apply from that first sale.</p>
<p>If you&#39;ve already been selling for a while, the sales from before your registration are the part to take to an accountant. OSS doesn&#39;t automatically cover them.</p>
<h2>Two things Stripe Tax doesn&#39;t do for you</h2>
<p>Stripe Tax calculates and collects the VAT at checkout. It doesn&#39;t register you or file your OSS return. You still need to:</p>
<ol>
<li><strong>Register</strong> for the non-Union OSS.</li>
<li><strong>File and pay</strong> each quarter.</li>
</ol>
<p>Also keep <strong>two pieces of evidence</strong> of each customer&#39;s location (for example billing address and IP address, or card country). Tax authorities can ask how you decided which country&#39;s VAT to charge.</p>
<h2>Business customers are different</h2>
<p>If the customer is a business with a valid EU VAT number, you normally don&#39;t charge VAT at all. The customer accounts for it under the reverse charge. Check the number in VIES, the EU&#39;s VAT number lookup, and keep the result.</p>
<h2>The UK is separate</h2>
<p>The UK left the EU, and OSS doesn&#39;t cover it. A business outside the UK selling digital products to UK consumers registers with HMRC from the first UK sale.</p>
<hr>
<p>Duty27 is an API for the calculation side of this: the right rate for each country on the date of the sale, reverse charge for validated business customers, and quarterly OSS report exports. See <a href="https://duty27.com">how it works</a> or the <a href="https://duty27.com/oss-threshold">€10,000 threshold explained</a>.</p>
]]></content:encoded>
      <category>vat</category>
      <category>eu</category>
      <category>stripe</category>
      <category>oss</category>
    </item>
    <item>
      <title>VIES is down. What do you do with the B2B sale in front of you?</title>
      <link>https://duty27.com/blog/vies-down-what-to-do</link>
      <guid isPermaLink="true">https://duty27.com/blog/vies-down-what-to-do</guid>
      <pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate>
      <description>The EU's VAT number check fails regularly, one country at a time. What an outage means for reverse-charge sales, your options at checkout, and how Duty27 handles it.</description>
      <content:encoded><![CDATA[<p>If you sell to businesses in other EU countries, you check their VAT numbers in VIES, the European Commission&#39;s VAT number lookup. A valid number is what lets you skip VAT and apply the reverse charge.</p>
<p>VIES isn&#39;t one database. It&#39;s a search service that asks each country&#39;s own system, and those systems go offline independently: for maintenance, under load, or for no stated reason. When Germany&#39;s or Spain&#39;s connection is down, every check for a German or Spanish number fails, while the rest of the EU works fine.</p>
<p>It happened while this post was being prepared: on the afternoon of 22 October 2026, the Commission&#39;s VIES status page listed Ireland as unavailable while Germany and the Netherlands answered normally. Every Irish VAT number check failed until Ireland&#39;s system came back.</p>
<p>So sooner or later a business customer will be at your checkout, and you won&#39;t be able to confirm their number.</p>
<h2>What an outage is, and isn&#39;t</h2>
<p>An unavailable check is <strong>not</strong> an invalid number. VIES tells you it couldn&#39;t reach the country (the error is typically <code>MS_UNAVAILABLE</code>, &quot;member state unavailable&quot;). It hasn&#39;t told you anything about the customer.</p>
<p>Treating &quot;unavailable&quot; as &quot;invalid&quot; means charging VAT to a real business that didn&#39;t owe it. Treating it as &quot;valid&quot; means skipping VAT you can&#39;t yet justify.</p>
<h2>Your options at checkout</h2>
<p><strong>1. Retry shortly.</strong> Many outages are short. If your integration can wait and retry, that&#39;s the cleanest fix. Don&#39;t retry in a tight loop: it adds load to a system that&#39;s already struggling and burns your own API usage.</p>
<p><strong>2. Use a recent result.</strong> If the same VAT number was checked successfully a short time ago, that result is still good evidence. Most outages don&#39;t coincide with a customer&#39;s very first purchase.</p>
<p><strong>3. Charge VAT now, correct it later.</strong> Complete the sale with VAT charged, and once VIES confirms the number, issue a corrected invoice and refund the VAT. The customer&#39;s purchase isn&#39;t blocked, and you never skip VAT you couldn&#39;t justify. The cost is a refund and a corrected invoice afterwards.</p>
<p><strong>4. Ask the customer to come back later.</strong> It works for big contracts, less so for a self-serve checkout.</p>
<p>Which is right depends on your business. A tool sold to developers at €20 a month can charge VAT and correct later. A large B2B invoice is better paused until the check works.</p>
<p>Keep a record either way: when you checked, what VIES answered, and what you did. If a tax authority later asks why you applied the reverse charge (or didn&#39;t), that record is your answer.</p>
<h2>How Duty27 handles it</h2>
<p>Duty27&#39;s <code>/v1/calculate</code> checks the buyer&#39;s VAT number as part of a business-to-business calculation. There are two kinds of check, and they behave differently in an outage:</p>
<ul>
<li><p><strong>Basic checks use a recent result first.</strong> On the free tier, or with <code>mode: &quot;BASIC&quot;</code>, Duty27 looks in its cache before asking VIES. A number checked in the last 24 hours is answered from the cache, marked <code>vat_validation_cached: true</code>, without contacting VIES at all, so an outage doesn&#39;t affect it.</p>
</li>
<li><p><strong>Qualified checks always ask VIES.</strong> Paid accounts with their own VAT number on file get a qualified check by default: the kind that returns a VIES consultation number as proof. That proof has to come from VIES on the day, so it&#39;s never served from a cache.</p>
</li>
<li><p><strong>When VIES can&#39;t answer, you get a clear error.</strong> The response is HTTP 503 <code>VAT_VALIDATION_UNAVAILABLE</code>, distinct from an invalid number, with a <code>Retry-After</code> header suggesting how long to wait before retrying (60 seconds). It&#39;s a starting point, not a promise: a country&#39;s outage can last much longer.</p>
<p>That error looks like this, so your code can tell it apart from a real &quot;invalid&quot;:</p>
<pre><code class="language-http">HTTP/1.1 503 Service Unavailable
Retry-After: 60
Content-Type: application/json

{&quot;error&quot;: &quot;VAT_VALIDATION_UNAVAILABLE&quot;, &quot;message&quot;: &quot;VAT number validation could not be completed&quot;}
</code></pre>
<p>An invalid number is not an error at all: the calculation succeeds with <code>&quot;vat_validation_status&quot;: &quot;INVALID&quot;</code>, VAT charged and <code>&quot;reverse_charge&quot;: false</code>.</p>
</li>
<li><p><strong>Or you choose to proceed.</strong> Send <code>on_validation_unavailable: &quot;ASSUME_INVALID&quot;</code> and Duty27 calculates with VAT charged and no reverse charge, as in option 3 above. That choice is logged, so you can show later why VAT was charged.</p>
</li>
</ul>
<p>When your own VAT number is on file, a valid check also returns the VIES consultation number: the reference that proves the check happened, for your records.</p>
<p>The free calculator on the <a href="https://duty27.com/">Duty27 homepage</a> does the same: when a country&#39;s registry is down, it says that VIES isn&#39;t returning results for that country, rather than reporting a failed lookup.</p>
<p>See the <a href="https://duty27.com/guides/vies-vat-number-check">VIES guide</a> for how the check works, and the <a href="https://duty27.com/docs">API docs</a> for the error codes.</p>
]]></content:encoded>
      <category>vat</category>
      <category>eu</category>
      <category>vies</category>
      <category>b2b</category>
      <category>api</category>
    </item>
    <item>
      <title>The EU's official VAT rate database got history wrong. Here's how we caught it.</title>
      <link>https://duty27.com/blog/eu-vat-rate-database-tedb-errors</link>
      <guid isPermaLink="true">https://duty27.com/blog/eu-vat-rate-database-tedb-errors</guid>
      <pubDate>Sat, 10 Oct 2026 00:00:00 GMT</pubDate>
      <description>TEDB, the European Commission's VAT rate database, returned wrong historical rates for Greece and Germany, and later changed one answer without notice. What we found and how we check.</description>
      <content:encoded><![CDATA[<p>If you need EU VAT rates in code, you will probably end up at TEDB, the European Commission&#39;s Taxes in Europe Database. It is free, it is official, and it has a SOAP API that answers one useful question: what was the VAT rate in this country on this date?</p>
<p>We built Duty27&#39;s rate history on it. Then we checked its answers against the law, and some of them were wrong.</p>
<h2>How a wrong rate hides</h2>
<p>We queried TEDB for every EU country four times a year, back to 2016, and flagged every place where the rate changed between two checkpoints. Each flagged change was then checked against the national law that made it.</p>
<p>That catches a change TEDB reports. It cannot catch one TEDB doesn&#39;t report. If TEDB returns the same wrong number before, during and after a real change, there is nothing to flag. The data looks perfectly calm.</p>
<h2>Two standard-rate errors</h2>
<table>
<thead>
<tr>
<th>Country</th>
<th>Date</th>
<th>Our August 2026 import</th>
<th>TEDB on 10 October 2026</th>
<th>Actual rate</th>
</tr>
</thead>
<tbody><tr>
<td>Greece</td>
<td>1 March 2016</td>
<td>24%</td>
<td>24%</td>
<td>23%</td>
</tr>
<tr>
<td>Germany</td>
<td>1 July 2020</td>
<td>19%</td>
<td>16%</td>
<td>16%</td>
</tr>
<tr>
<td>Germany</td>
<td>1 October 2020</td>
<td>19%</td>
<td>16%</td>
<td>16%</td>
</tr>
</tbody></table>
<p><strong>Greece</strong> raised its standard rate from 23% to 24% on 1 June 2016 (<a href="https://www.e-nomothesia.gr/kat-oikonomia/nomos-4389-2016-phek-94a-27-5-2016.html">Law 4389/2016, article 52</a>). TEDB reports 24% for the months before that too, and still did when we checked again on 10 October 2026. Any invoice, refund or correction for the first five months of 2016 that trusts TEDB uses the wrong rate.</p>
<p><strong>Germany</strong> cut its standard rate from 19% to 16% for the second half of 2020 (<a href="https://dejure.org/BGBl/2020/BGBl._I_S._1512">Zweites Corona-Steuerhilfegesetz</a>). Our August 2026 import from TEDB recorded 19% for both 1 July and 1 October 2020, so the cut was invisible to our checkpoints. When we queried the same dates again in October, TEDB returned 16%. Something changed in between. We didn&#39;t keep TEDB&#39;s raw August responses, so we can&#39;t show exactly what it sent then, and we saw no notice of a correction.</p>
<p>Germany has a second trap that is still there today. For those dates TEDB returns two entries marked &quot;standard&quot;: an import VAT entry at 19% and the real 16%. Code that takes the first entry it finds gets 19%.</p>
<p>We found both errors by comparing against the Commission&#39;s own historical &quot;VAT rates applied in the Member States&quot; document, a separately compiled table that covers every member state up to 2020.</p>
<h2>The reduced rates were worse</h2>
<p>Reduced rates (the lower rates for things like e-books, newspapers and magazines) were noisier. These findings are from our August 2026 checks:</p>
<ul>
<li><strong>Austria&#39;s e-book rate came back as 10% and 20% at the same time</strong> for every checkpoint in 2018 and 2019.</li>
<li><strong>A placeholder start date.</strong> Several countries&#39; digital publication rates were dated 1 January 2018. In reality they took effect at different points, mostly in 2019 after the EU allowed reduced rates on electronic publications. The 2018 date was never a real legal event anywhere it appeared.</li>
<li><strong>Spain was missing entirely.</strong> Spain cut VAT on electronic books, newspapers and magazines to 4% on 23 April 2020 (Real Decreto-ley 15/2020). TEDB had no data for those categories at all.</li>
</ul>
<p>Of the 34 country and category combinations we investigated, 21 needed a correction: a wrong rate, a wrong date, or a rate that never existed.</p>
<h2>Why it matters</h2>
<p>VAT is due at the rate that applied on the date of the sale. A current-rates table can&#39;t answer that, and a historical table is only as good as its history. The dates that need it most are the old ones:</p>
<ul>
<li>a refund or credit note for a sale made before a rate change,</li>
<li>a correction to an OSS return from an earlier quarter,</li>
<li>a tax audit asking you to show that the rate you charged was right on the day.</li>
</ul>
<h2>What we do now</h2>
<ul>
<li><strong>Every rate change cites its source.</strong> Each change in Duty27&#39;s data points to the law or the tax authority statement we actually read, and the build fails if a change has no source. You can see them on the <a href="https://duty27.com/vat-rates/history">EU VAT rate history page</a>.</li>
<li><strong>TEDB is a starting point, not the answer.</strong> We use it to find candidate changes, then confirm each one against the law or another independent source.</li>
<li><strong>The data is free to use.</strong> The full standard-rate history since 2016 is available as <a href="https://duty27.com/data/eu-standard-vat-rates.csv">CSV</a> and <a href="https://duty27.com/data/eu-standard-vat-rates.json">JSON</a>, with a source for every change.</li>
</ul>
<h2>If you use TEDB yourself</h2>
<ol>
<li><strong>Treat it as a lead, not a source.</strong> The Commission itself describes the database as information supplied by the member states, not a reference for legal purposes.</li>
<li><strong>Check for conflicting values on the same date</strong>, not only for changes between dates. That is how the Austria and Germany problems show up.</li>
<li><strong>Keep the raw responses.</strong> We didn&#39;t save TEDB&#39;s raw August answers, so for Germany we can show what our import recorded, but not exactly what TEDB sent. Store them, and you can prove what the source said on the day.</li>
<li><strong>Cite every change</strong> to the law that made it. When a source disagrees with the law, the law wins.</li>
</ol>
]]></content:encoded>
      <category>vat</category>
      <category>eu</category>
      <category>data</category>
      <category>api</category>
    </item>
    <item>
      <title>Selling e-books and templates? They're taxed at different VAT rates</title>
      <link>https://duty27.com/blog/ebooks-and-templates-different-vat-rates</link>
      <guid isPermaLink="true">https://duty27.com/blog/ebooks-and-templates-different-vat-rates</guid>
      <pubDate>Tue, 06 Oct 2026 00:00:00 GMT</pubDate>
      <description>In most EU countries and the UK, an e-book gets a reduced VAT rate and a template doesn't. Why, what counts as an e-book, and what that means for your checkout.</description>
      <content:encoded><![CDATA[<p>Plenty of digital sellers have a store that looks like this: a couple of e-books, a pack of Notion templates, a set of spreadsheets, maybe a course. To a payment processor it&#39;s all &quot;digital products&quot;. To VAT law it isn&#39;t.</p>
<h2>E-books get reduced rates. Templates don&#39;t.</h2>
<p>Since 2018, EU countries have been allowed to apply reduced VAT rates to electronic publications: books, newspapers and periodicals supplied electronically. Most of them do. The UK went further and zero-rated e-publications from 1 May 2020.</p>
<p>Templates, spreadsheets, stock files, software and most other downloads are &quot;electronically supplied services&quot;. They get the standard rate.</p>
<table>
<thead>
<tr>
<th>Country</th>
<th>E-book</th>
<th>Template or other download</th>
</tr>
</thead>
<tbody><tr>
<td>Germany</td>
<td>7%</td>
<td>19%</td>
</tr>
<tr>
<td>France</td>
<td>5.5%</td>
<td>20%</td>
</tr>
<tr>
<td>Italy</td>
<td>4%</td>
<td>22%</td>
</tr>
<tr>
<td>Spain</td>
<td>4%</td>
<td>21%</td>
</tr>
<tr>
<td>Netherlands</td>
<td>9%</td>
<td>21%</td>
</tr>
<tr>
<td>Ireland</td>
<td>0%</td>
<td>23%</td>
</tr>
<tr>
<td>United Kingdom</td>
<td>0%</td>
<td>20%</td>
</tr>
</tbody></table>
<p>So a checkout that applies one rate per country to every product is wrong for at least one of them. With the standard rate everywhere, your e-book buyers are overcharged. With the e-book rate everywhere, you under-collect VAT on templates and owe the difference yourself.</p>
<h2>What counts as an e-book</h2>
<p>The reduced rate is for publications. Roughly: something that would be a book, newspaper or magazine if it were printed.</p>
<ul>
<li><strong>Usually an e-book:</strong> a novel, a guide or handbook, a workbook, a cookbook, a PDF version of a printed book.</li>
<li><strong>Usually not:</strong> templates and planners meant to be filled in or reused, spreadsheets, stock photos, presets, fonts, software.</li>
<li><strong>Excluded explicitly:</strong> publications that are wholly or mainly advertising, or mainly video or music. Both the EU rule and the UK&#39;s say so.</li>
</ul>
<p>The edges are blurry, and countries draw them differently. A &quot;planner&quot; that is mostly blank pages is a template, not a book. A guide with a few worksheets at the back is still a guide. When a product is genuinely borderline, ask an accountant before picking the lower rate.</p>
<h2>Bundles</h2>
<p>A bundle of an e-book and templates sold for one price is a common headache. Depending on the country, a bundle may need splitting into its parts at their own rates, or may be taxed as one product. If bundles are a big part of your sales, get advice for your main markets rather than guessing.</p>
<h2>What to do in your store</h2>
<ol>
<li><strong>Tag each product</strong> with its VAT category: e-book (publication) or standard.</li>
<li><strong>Make your tax calculation use the tag</strong>, per country, on the date of the sale. Reduced rates change too, and not always at the same time as the standard rate.</li>
<li><strong>Check your merchant of record&#39;s settings</strong> if you use one: whether you can mark a product as an e-book, and which rate it uses if you don&#39;t.</li>
<li><strong>Keep the reasoning</strong> for any borderline product, in case a tax authority asks later.</li>
</ol>
<hr>
<p>Duty27&#39;s API (EU countries) takes a <code>category</code> field (<code>EBOOK</code>, <code>NEWSPAPER</code> or <code>PERIODICAL</code>) and returns the right rate for that country on that date, falling back to the standard rate where no reduced rate applies. See the <a href="https://duty27.com/docs">docs</a>, or <a href="https://duty27.com/vat-rates">EU VAT rates by country</a>.</p>
]]></content:encoded>
      <category>vat</category>
      <category>eu</category>
      <category>uk</category>
      <category>ebooks</category>
      <category>digital-products</category>
    </item>
    <item>
      <title>Why price × standard rate is the wrong way to calculate EU VAT</title>
      <link>https://duty27.com/blog/price-times-standard-rate-is-wrong</link>
      <guid isPermaLink="true">https://duty27.com/blog/price-times-standard-rate-is-wrong</guid>
      <pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate>
      <description>Multiplying the price by the country's standard rate is how most VAT code starts. Five ways it goes wrong: dates, product categories, business customers, where you are based, and rounding.</description>
      <content:encoded><![CDATA[<p>Most EU VAT code starts like this:</p>
<pre><code class="language-js">const vat = price * (standardRate[country] / 100);
const total = price + vat;
</code></pre>
<p>It works for the first sale and the demo. It is also wrong in at least five ways that show up later, usually at the worst possible time: during a refund, a correction or an audit.</p>
<h2>1. Rates change, and VAT uses the rate on the date of the sale</h2>
<p>A table of today&#39;s rates answers the wrong question. VAT is due at the rate that applied when the sale happened.</p>
<p>Rates change more often than people expect. Germany cut its standard rate from 19% to 16% for the second half of 2020. Finland went from 24% to 25.5% in September 2024. Each change means:</p>
<ul>
<li>a refund for a sale before the change must use the old rate,</li>
<li>a sale made in December and invoiced in January can straddle a change,</li>
<li>a correction to an earlier quarter&#39;s return uses that quarter&#39;s rates.</li>
</ul>
<p>So the lookup needs a date: <code>rate(country, date)</code>, not <code>rate(country)</code>. Historical rate data needs checking too: even official sources get past rates wrong.</p>
<h2>2. Not everything uses the standard rate</h2>
<p>EU countries may apply reduced rates to some products. For digital sellers the big one is electronic publications: e-books, e-newspapers and e-magazines.</p>
<table>
<thead>
<tr>
<th>Country</th>
<th>Standard rate</th>
<th>E-books</th>
</tr>
</thead>
<tbody><tr>
<td>Germany</td>
<td>19%</td>
<td>7%</td>
</tr>
<tr>
<td>France</td>
<td>20%</td>
<td>5.5%</td>
</tr>
<tr>
<td>Italy</td>
<td>22%</td>
<td>4%</td>
</tr>
<tr>
<td>Spain</td>
<td>21%</td>
<td>4%</td>
</tr>
<tr>
<td>Netherlands</td>
<td>21%</td>
<td>9%</td>
</tr>
<tr>
<td>Ireland</td>
<td>23%</td>
<td>0%</td>
</tr>
</tbody></table>
<p>If you sell e-books and multiply by the standard rate, you overcharge your customers. If you sell e-books and templates and use one rate for both, one of them is wrong.</p>
<h2>3. Business customers usually pay no VAT at all</h2>
<p>When the customer is a business with a valid VAT number in another EU country, you normally don&#39;t charge VAT. The customer accounts for it under the reverse charge, and your invoice says so.</p>
<p>That means the calculation depends on who the customer is, and the VAT number needs checking in VIES (the EU&#39;s VAT number lookup) before you rely on it. A number the customer typed into a form proves nothing until it&#39;s checked.</p>
<h2>4. Where you are based changes the answer</h2>
<p>For a business established in one EU country, cross-border sales of digital services to consumers below €10,000 a year can be taxed at the seller&#39;s own rate. Above it, the customer&#39;s rate applies. The test also looks at the previous year.</p>
<p>For a business outside the EU, there&#39;s no threshold: the customer&#39;s rate applies from the first sale.</p>
<p>So <code>standardRate[customerCountry]</code> can be wrong for a small EU seller, and right for a US one, for the same sale.</p>
<h2>5. Floating-point money and rounding</h2>
<pre><code class="language-js">0.1 + 0.2 === 0.30000000000000004 // true
</code></pre>
<p>Money in binary floating point drifts, and VAT amounts need rounding to the cent at a defined point. Rounding each invoice line and then adding gives a different total from adding and then rounding. Use integer cents or a decimal type, and pick one rounding rule on purpose.</p>
<h2>What the calculation actually needs</h2>
<p>Put together, a correct VAT calculation needs at least:</p>
<ul>
<li>the customer&#39;s <strong>country</strong>,</li>
<li>the <strong>date</strong> of the sale,</li>
<li>the <strong>product category</strong> (standard, or e-book and similar),</li>
<li>whether the customer is a <strong>business</strong>, and if so a <strong>checked VAT number</strong>,</li>
<li>where <strong>you</strong> are established, and for an EU seller, your cross-border sales so far this year and last year,</li>
<li><strong>decimal arithmetic</strong> with an explicit rounding rule.</li>
</ul>
<p>That is a lot more than a multiplication. It&#39;s the reason Duty27 exists. A request looks like this:</p>
<pre><code class="language-json">{
  &quot;country_code&quot;: &quot;DE&quot;,
  &quot;date&quot;: &quot;2020-08-01&quot;,
  &quot;amount&quot;: &quot;100.00&quot;,
  &quot;amount_type&quot;: &quot;NET&quot;,
  &quot;b2b&quot;: false,
  &quot;category&quot;: &quot;EBOOK&quot;
}
</code></pre>
<p>The response gives you the rate that applied on that date (<code>rate_percent</code>), the net, tax and gross amounts as decimal strings, and whether the reverse charge applies. You can <a href="https://duty27.com/">try a calculation on the homepage</a> without signing up, and the <a href="https://duty27.com/docs">API docs</a> cover the rest, including business customers and the €10,000 threshold.</p>
]]></content:encoded>
      <category>vat</category>
      <category>eu</category>
      <category>api</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
