Excel is the tool almost every seller starts VAT management with. It’s flexible, familiar and free. The problem doesn’t show up right away: it shows up when your channels become 3, your countries become 15 and your transactions become tens of thousands.
When Excel is still enough
Being honest about the breaking point helps you make the right decision. Excel is sufficient if:
- you sell on a single channel (e.g. only Amazon.it) with modest volume;
- you have a single dominant country of consumption and very few cross-border sales;
- your annual cross-border sales are below the €10,000 OSS threshold and you don’t expect to exceed it;
- you have an accountant who handles the entire aggregation process from the raw files themselves.
In these cases, a well-structured spreadsheet with a VLOOKUP on the EU rate table works. The problem shows up as soon as one of these four points changes.
The example that shows the risk: the broken VLOOKUP
Imagine this real-world scenario:
You have a rate_mapping table with two columns: country and rate. You use =VLOOKUP(A2, rate_mapping, 2, 0) on 4,800 rows of transactions.
Halfway through the quarter you add a new row for Bulgaria (BG, 20%) at the top of the table instead of the bottom. You don’t notice that the formula uses a fixed range $A$1:$B$27 instead of a dynamic table. Result:
| Country | Transactions | Correct rate | Declared rate | VAT error |
|---|---|---|---|---|
| DE | 1,240 | 19% | 19% | ✅ 0 |
| FR | 890 | 20% | 20% | ✅ 0 |
| PL | 310 | 23% | 20% | ❌ −€8,370 |
| RO | 180 | 19% | 23% | ❌ +€3,240 |
| BG | 95 | 20% | 19% | ❌ −€1,140 |
The error is silent. The total in the VAT column looks plausible. The OSS return is filed with wrong data for 3 countries. Poland’s VAT is under-declared by €8,370.
This kind of error is far more common than people think, and it doesn’t surface until a tax audit or until your accountant does a manual cross-check.
Limit 1: managing multiple countries and rates
With OSS you handle cross-border B2C sales to up to 27 EU countries, each with standard and reduced rates that change over time. In Excel:
- the country → rate mapping needs to be updated manually every time it changes;
- exceptions by product category (reduced rate on food, books, medicines) are handled with increasingly complex formulas;
- a single error in the mapping table propagates to every row using that formula.
Limit 2: consolidating multiple channels
Amazon, eBay, Shopify: each channel has its own CSV format. Normalisation — country codes, currency, transaction type — happens by hand in Excel. The risk of forgetting a file or a channel is high, and there’s no system to flag it for you.
Limit 3: checks and anomaly detection
Before the OSS export you’d need structured checks: are all months covered? Has no country disappeared compared to the previous quarter? Are there no impossible rates? In Excel these checks depend entirely on the memory and discipline of whoever works the file — they’re not automatic.
To understand how dedicated software handles these checks: Anomaly detection on VAT reports: what it’s for.
Limit 4: repeatability and audit trail
The OSS return is quarterly. For every quarter you should be able to reconstruct exactly the steps taken to arrive at the per-country totals. Informally used Excel makes it hard to:
- know who changed what and when;
- repeat the exact same process the following quarter;
- respond to a tax audit years later.
Limit 5: collaboration with your accountant
Excel files get copied, renamed, emailed around. It’s unclear which is the official version. Your accountant receives inconsistent attachments to interpret. A centralised system always produces the same layout and keeps the data in a single accessible place.
Excel vs. dedicated software: a direct comparison
| Capability | Excel | Dedicated software |
|---|---|---|
| Automatic import from Amazon/eBay/Shopify | ❌ Manual | ✅ Automatic |
| Up-to-date EU rate mapping | ❌ Manual | ✅ Updated by the system |
| Anomaly and outlier detection | ❌ Not built in | ✅ Structured |
| OSS / domestic / B2B separation | ❌ Depends on formulas | ✅ Automatic |
| Change audit trail | ❌ Absent | ✅ Operation log |
| Output ready for your accountant | ❌ Needs formatting each time | ✅ Fixed template |
| Spot analysis and simulations | ✅ Excellent | ⚠️ Limited (export to Excel) |
| Cost | ✅ Free | ❌ Subscription |
Excel wins on flexibility and cost. Dedicated software wins on reliability, traceability and time saved every quarter.
Where VATManager fits in
VATManager doesn’t replace Excel for spot analysis. It sits upstream: it imports the files from marketplaces, normalises countries and currencies, applies EU VAT rules, runs consistency checks and produces the per-country report ready for your accountant. If you want to do further analysis, you can always export to Excel from there.
The critical part — OSS calculation, multi-country management, audit trail — is handled by a tool designed for that purpose, not a fragile macro nobody remembers how to fix.
📎 Learn more: E-commerce VAT software — 2025 comparison — EU VAT rates: why you can’t manage them by hand — How to choose VAT software for European marketplaces
Frequently asked questions
At what sales volume does it make sense to move from Excel to dedicated VAT software? There’s no precise volume threshold. The signal is qualitative: more than 2 active channels, FBA stock in multiple countries, or an accountant spending hours interpreting your files. With a single country and a single channel, Excel can be enough for a few years too.
Can Excel cause errors in the OSS return? Yes. The most common error is a broken VLOOKUP on the rate table: a row inserted in the wrong place can make thousands of transactions calculate the wrong rate with no visible error message.
Do I need to abandon Excel entirely? No. Excel remains useful for spot analysis and simulations. The idea is to use a dedicated tool for the critical part (VAT calculation, per-country aggregation, audit trail) and export to Excel when you need further analysis.