OSS filing looks simple on paper: quarterly data, one return, one deadline. In practice the problem is timing. If the company starts collecting the data only at the end of the quarter, errors accumulate quickly.
This article shows what to prepare, how to spot problems before filing, and what to do if you need to correct a filed return later on.
Deadlines you should actually plan around
OSS is filed quarterly, so the filing deadline belongs in the company calendar well before the quarter closes. I recommend treating the deadline as the final review date, not the first day you start working on the numbers.
| Quarter | Sales period | Practical deadline |
|---|---|---|
| Q1 | 1 January - 31 March | End of April |
| Q2 | 1 April - 30 June | End of July |
| Q3 | 1 July - 30 September | End of October |
| Q4 | 1 October - 31 December | End of January |
The owner should not rely on memory alone. Put the deadline into the same workflow as your monthly sales export and bank reconciliation.
What to prepare before filing
The cleanest filing starts with a short but disciplined pack: country split, VAT rate, returns, credit notes, and a clear separation between OSS data and ordinary Estonian VAT data.
- Sales by country and channel.
- Returns and discounts linked to the original order.
- Marketplace orders marked by VAT role.
- A separate view for ordinary Estonian VAT.
If the accountant cannot see those elements in five minutes, the filing process is probably too weak already.
A practical quarter-end workflow for a small seller
For a small online store, the cleanest OSS quarter is usually built backwards from the filing deadline. I normally suggest one internal cut-off for collecting exports, one review pass for country logic and returns, and one final check before submission.
| Step | What should happen | Why it matters |
|---|---|---|
| Week 1 after quarter-end | Collect country-level exports from store and marketplaces | Stops missing data from surfacing on filing day |
| Week 2 | Match returns, discounts, and credit notes to original orders | Keeps corrections from drifting into the wrong period |
| Week 3 | Review country totals, VAT rates, and exception cases | Catches logic errors before the return is filed |
| Final days | Submit only after one clear sign-off on the data pack | Prevents last-minute guesswork |
This is not a corporate process. It is the minimum discipline that keeps a quarterly OSS filing predictable for a founder-led store.
How to spot a problem before submission
I usually look for four warning signs. The country total does not match the store report. VAT looks strangely high or low. Amazon or another marketplace shows a different payout from the expected sales. Or a return from one month lands in another month without a link to the original order.
None of those issues is unusual by itself. The risk is when the company notices them only at filing time, when the deadline is already too close to investigate properly.
What to do if a correction is needed
If you find an error after submission, do not panic and do not try to rebuild the whole quarter as if it were an ordinary VAT return. In OSS, corrections are usually handled through the next filing with a proper reference to the original mistake.
The important part is a correction log: what country, what order, what period, and why the correction is needed. That is what keeps the process auditable.
| Correction field | What to record | Why it helps later |
|---|---|---|
| Country | Where the original sale was reported | Keeps the adjustment tied to the right destination VAT |
| Period | Which OSS quarter the original sale belongs to | Stops corrections from being mixed across quarters |
| Order reference | Original order or transaction ID | Makes the change traceable for bookkeeping and review |
| Reason | Return, wrong VAT rate, cancellation, price adjustment | Explains why the correction exists at all |
What to send your accountant if the quarter is already closed
If the quarter is already over, the accountant should not receive only a panic message saying that the OSS return is due. The handoff should include the minimum pack needed to review the filing without rebuilding the whole quarter from scratch.
- Country-level sales export for the quarter.
- Returns, credit notes, and discounts linked to original orders.
- Marketplace exceptions flagged separately.
- A short note on anything unusual: new country, rate issue, warehouse movement, or missing report.
Most OSS filing problems start with late data, not with the form itself. A clean monthly export is the best deadline insurance.
The deadline matters, but the data discipline matters more. If your monthly export is clean, the quarterly return is manageable. If not, the last week of the quarter becomes an expensive rescue job. Related topic: register OSS Estonia.
If you want a second pair of eyes on the filing, use our contacts page and we will review the quarter, the correction log, and the filing pack with you.
Sources cited in this article
Need help with OSS or IOSS? We work with Estonian founders, e-residents, and online stores that need a clean VAT setup. Contact us and we will review the flow with you.