Why Recomputed Tax Reports Are Wrong

Oss reporting: banner

A VAT report that multiplies sales by today's tax rates restates returns you have already filed. Read the tax your orders actually charged instead.

There are two ways to build a VAT report for a WooCommerce shop. One reads the tax each order actually charged. The other takes each order's net amount and works the tax out again from the rates in your tax settings today. On the day you build it, both give the same number. The second one is wrong the moment anything changes — and it never tells you.

Not legal or tax advice. This post is about how reports are built. What you owe and file is between you and your accountant.

What you owe is what you charged

When a customer checks out, WooCommerce works out the VAT from the rate that matches their address and the product's tax class, adds it to the price, and takes the money. That VAT is now a fact: the customer paid it, you hold it, and it is what you report. The OSS rules ask for "the VAT payable" on each supply (European Commission, record keeping) — not for what it would be under rates you set later.

WooCommerce writes that fact onto the order. Every order carries tax lines: one per rate applied, each with the rate's label, its percentage, the tax on the products and the tax on delivery, exactly as charged. Those lines do not change when your tax table does.

Three ways a recomputed report drifts

1. A country changes its rate. Member states move their standard and reduced rates from time to time. You update WooCommerce on the day. A report that recomputes now applies the new rate to every past order, and your figures for earlier quarters change — even though you charged, and filed, the old rate.

2. You fix a mistake in your tax table. Say a reduced rate was set up wrongly for three months and you correct it. The customers in those months were still charged the wrong rate; that is the money you hold. A recomputed report hides the error by pretending you charged the right rate all along, which is precisely the thing you need to see to put it right.

3. You move a product to a different tax class. A product sold at standard rate in spring is moved to a reduced rate in summer. Recompute the spring quarter and its tax falls, though not one spring customer paid less.

In every case the report looks fine. The numbers add up, the columns balance, nothing is flagged. That is what makes this failure expensive: it is plausible. Under OSS, once a return is submitted any correction has to be made in a later return (Commission, declare and pay), so a report that silently rewrites a filed quarter leaves you comparing two numbers with no way of telling which one you sent.

A small example

A shop charged 20% VAT to French customers all through July–September: €5,000.00 net, €1,000.00 VAT. It filed exactly that on its OSS return.

In November, preparing for a product launch, it adds a reduced-rate tax class and accidentally assigns it to the French standard rate row instead of creating a new one — the French row now reads 10%. Re-running July–September:

  • A recomputing report: €5,000.00 × 10% = €500.00 VAT.
  • A report reading the orders' tax lines: €1,000.00 VAT, unchanged.

The first one tells you that you over-declared €500.00 in Q3 and might claim it back. You didn't. The second one tells you the truth — and when the October–December report starts showing French sales at 10%, that is the moment you spot the misconfiguration, not a year later in an audit.

What should move an old report

Reading the order is not the same as freezing the report. Two things change what an order is worth, and they ought to show:

  • A refund. A returned item is not a sale, and the VAT on it is not VAT you owe. If a September order is refunded in November, re-running July–September should show less — and the difference is the correction the OSS rules ask you to make in a later return.
  • A cancelled order. If an order leaves the statuses that count as a sale, it should leave the report.

Both are changes to the order itself. A change to your settings is not.

One more belongs in the same list: the order's address. The country an order is reported under is read from its shipping (or billing) address when you run the report, so if somebody edits the address on an old order, that order moves to the new country's row — carrying the tax it was actually charged. Edit addresses on past orders only to correct a genuine mistake.

How Gatemi's reports do it

Gatemi Sales by Country (free) and Gatemi Tax Reports for WooCommerce (the full edition) follow one rule: every figure comes off the order.

  • The tax for each order is the order's own total tax, less any tax refunded.
  • The net is the order's total less that tax, after refunds.
  • The gross is the order's total, after refunds.
  • In the full edition, the per-rate table reads each order's tax lines and shows the label and percentage the line itself carries — so a rate you renamed or deleted since still appears as it was charged. Its net is what the order's own lines recorded under that rate, and refunds come off rate by rate, using what each refund itself recorded.

Neither plugin reads WooCommerce's tax rate table at all. Neither writes anything to your orders, so running a report is safe at any time. And both say so on the screen: "Nothing is worked out again from the store's current tax rates, so a rate that changes today does not restate a return you have already filed."

Because net plus tax equals gross in every row by construction, the report also gives you a quick sanity check: if your own figures for a period don't balance that way, something outside the report changed an order after it was placed.

Next step

Install Gatemi Sales by Country, run it for a quarter you have already filed, and compare it with what you sent. Then read the WooCommerce OSS VAT report guide for the rest of the return.

Shopping Cart
Scroll to Top