Shopify OSS VAT Record-Keeping: Build a Quarterly EU Reporting Workflow

Start by deciding which sales actually belong in the OSS workflow

Do not begin with a country-rate spreadsheet. Begin with scope. The European Commission describes the One Stop Shop schemes as optional special schemes for reporting specified supplies through one Member State of identification. The Union and non-Union schemes use calendar-quarter tax periods, while the import scheme uses monthly periods. That difference alone is a reason not to treat every EU sale as one generic 'OSS row'.

For an operating Shopify store, create a simple classification rule before the order data reaches finance: which sales are within the scheme you use, which belong in a domestic VAT return instead, which are B2B transactions requiring a separate VAT-status decision, and which are uncertain enough to enter an exception queue. The workflow should preserve the original order facts and the reason for the classification so that a later reviewer can understand why a transaction was included or excluded.

Vatuno's public listing is specifically framed around stores selling digital products. That is a meaningful fit boundary. A merchant selling digital services to EU consumers may have a relatively direct match to the advertised record-and-reporting job. A merchant importing physical goods, relying on IOSS, holding stock in several Member States or combining complex domestic registrations should confirm coverage with the relevant tax authority or adviser and with the app's current documentation before treating the same setup as equivalent.

Do not use the EUR 10,000 threshold as a universal switch

The EUR 10,000 threshold is frequently summarized as if every Shopify merchant starts charging destination-country VAT the moment cross-border EU revenue crosses one number. The Commission's OSS guidance is narrower. The simplification applies only when its conditions are met, including the supplier-establishment conditions, and it concerns the combined value of specified cross-border telecommunications, broadcasting and electronically supplied services plus intra-Community distance sales of goods in the current and preceding calendar year. A supplier not established in the EU does not get this threshold simplification.

That means threshold tracking is a monitoring tool, not a substitute for classifying the business. First establish whether the simplification can apply to your facts. Then monitor the relevant sales. A merchant can also choose the general destination rule before the threshold is exceeded, subject to the applicable commitment period. The operational point is simple: store the reason the threshold is relevant to you instead of letting a dashboard number silently decide tax treatment.

Keep this B2C threshold logic separate from VIES validation. A valid business VAT number and an eligible B2C threshold calculation answer different questions. If your store mixes B2B and B2C sales, give them separate decision paths even if the same VAT app surfaces both kinds of information.

Build the order record around the fields an audit may ask you to reconstruct

The Commission's OSS record-keeping guidance points to Article 63c and says records include, among other details, the Member State of consumption, the type and date of supply, the VAT payable, payments on account and information used to determine where the customer is established, permanently resident or usually resides. Treat those as a data-design problem. If one of those facts only exists in a staff member's memory, your reporting workflow has a weak joint.

For each covered Shopify order, preserve the order reference, transaction date, customer-location evidence used for the tax decision, Member State of consumption, supply classification, taxable amount, VAT rate applied, VAT amount collected and any later correction. Where your business receives payments on account, keep those details connected to the record as well. This is not an exhaustive legal field list; it is a practical minimum map from the Commission's published record categories to ecommerce operations.

Vatuno's listing says every EU order becomes a VAT record, compares collected VAT with the official rate for the buyer's country and flags mismatches. That is useful because it turns one common quarter-close problem into a visible exception rather than a hidden spreadsheet inconsistency. The merchant still needs to decide whether the underlying order belongs in the relevant VAT treatment and resolve the exception before relying on the period totals.

Run a monthly reconciliation even when the OSS return is quarterly

Quarterly filing does not mean quarterly housekeeping. Reconcile each month so that a wrong rate, refunded order, address anomaly or classification issue is discovered while the transaction is still easy to investigate. Compare order totals, taxable amounts and VAT by Member State with the records you intend to use for the return. Then separate mismatches into a queue with an owner and a resolution status.

A useful exception queue distinguishes at least four cases: the store collected a rate different from the expected country rate; customer-location evidence conflicts; B2B VAT status is unresolved; or a correction such as a refund or credit note affects a previous period. Do not 'fix' the report by editing a total with no trail. Preserve what happened on the order, document the correction and carry it into the reporting process in the way the applicable OSS rules require.

This is where a focused app can reduce repetitive checking without becoming the tax decision-maker. Vatuno can flag rate mismatches and create sequential PDF invoices according to its listing. Use those outputs as controlled records, then keep human review for cases where the facts or tax classification are uncertain.

Close the quarter against the Commission timetable, not an internal guess

For the Union and non-Union schemes, the Commission sets the tax period as the calendar quarter and requires the electronic return and accompanying payment by the end of the following month. That means Q1 is due 30 April, Q2 31 July, Q3 31 October and Q4 31 January of the following year. The import scheme is monthly, so do not reuse this quarterly timetable for IOSS.

The Commission also states that a nil return is required when a taxable person using a scheme has no OSS supplies at all during the period and no prior-return corrections to make. That is another reason a quarter-close checklist should begin with scheme status rather than with 'do we have sales?'. Being registered for a scheme creates reporting duties that are not visible from Shopify order volume alone.

Vatuno's current listing advertises quarterly OSS reports as CSV. Treat the CSV as prepared reporting data. The Commission notes that Member State portals allow electronic file transfer of OSS return data, but the actual submission takes place through the relevant Member State process. An export from an app is not evidence that the return was submitted, accepted or paid. Keep separate status fields for report prepared, return submitted and payment completed.

Archive the evidence for the full OSS retention period

The Commission says OSS records must be retained for 10 years from the end of the year in which the transaction was made, even if the taxable person later stops using the scheme. It also says the records must be made electronically available without delay when requested by the Member State of identification or a Member State of consumption.

A quarter-close folder therefore should not contain only the final CSV. Keep the period export, the underlying order-level records, exception resolutions, evidence used for customer location, relevant invoice records and a note of any corrections. Use stable naming and access controls so a later finance team can reconstruct the quarter without depending on the employee who originally filed it.

Retention is where a 'reporting app' and a real operating process diverge. Software can produce records, but the business still needs an archive policy, ownership and a way to retrieve the evidence years later. Make that responsibility explicit when you choose the tool and when staff roles change.

Where Vatuno is a strong fit, and where to verify more before buying

Vatuno is a strong fit when your Shopify VAT workload is centered on the EU record trail advertised in its listing: digital-product sales, country-rate checks, VIES validation, sequential invoices, quarterly OSS CSV reporting and threshold monitoring. As of September 15, 2026, the official listing shows Starter at $49 per month, Growth at $99 and Enterprise at $149, each with a 14-day free trial. Vatuno is available in English, German, French, Spanish, Italian and Portuguese (Portugal).

Choose it for the documented job, not for features the listing does not promise. The listing's explicit reporting feature is quarterly OSS CSV. If your core problem is monthly IOSS reporting for imported consignments, complex physical-goods movements, registrations in several jurisdictions or tax filing outside the EU, verify the required coverage separately. Likewise, VIES validation is one input into B2B treatment; it is not proof that every transaction qualifies for reverse charge.

A practical rollout is to run one completed period through the workflow before expanding it. Reconcile a sample of orders back to Shopify, inspect every mismatch, confirm that the fields your adviser needs are present, and document who performs the actual submission and payment. The goal is not to outsource judgment to a dashboard. It is to turn repeatable evidence collection and reporting preparation into a process that is easier to review.

• Classify scheme scope before you aggregate country totals.
• Keep the conditional EUR 10,000 threshold separate from B2B VIES decisions.
• Reconcile monthly even when your Union/non-Union OSS return is quarterly.
• Track report preparation, official submission and payment as separate statuses.
• Retain the underlying OSS records for 10 years from the end of the transaction year.
• Verify IOSS, physical-goods and multi-jurisdiction requirements instead of inferring them from an OSS export feature.

Apps mentioned in this guide

Frequently asked

Does Vatuno file my OSS return automatically?

The current Shopify App Store listing advertises quarterly OSS reports as CSV. Treat that as report preparation and export support, not as a claim that Vatuno registers you for OSS, submits the return or makes the tax payment on your behalf.

How long do OSS records need to be kept?

The European Commission says OSS records must be kept for 10 years from the end of the year in which the transaction was made and made electronically available to the relevant tax authorities on request.

Are OSS returns always quarterly?

No. The Union and non-Union schemes use calendar-quarter tax periods, while the import scheme uses monthly periods. Do not treat a quarterly OSS export as proof of monthly IOSS reporting support.

Does every EU Shopify store use the EUR 10,000 threshold?

No. The threshold simplification has specific eligibility conditions and covers specified cross-border B2C supplies. Establishment and transaction type matter, and non-EU-established suppliers do not get that threshold simplification.

Is Vatuno available in English?

Yes. Vatuno is available in English. Its current Shopify App Store listing also shows German, French, Spanish, Italian and Portuguese (Portugal).