Shopify EU VAT Customer Location Evidence for Digital Products: Billing, IP, and OSS Records

Start by separating B2C customer location from B2B VAT status

The first branch in the workflow is customer status. The European Commission's current place-of-taxation guidance says the basic B2B rule for services is the place where the business customer is established, while B2C telecommunications, broadcasting and electronically supplied services are taxed where the private customer resides. Those rules answer different questions, so one field should not drive both paths.

If a customer presents a business VAT number, route the order into the B2B validation and transaction-classification process rather than treating an IP address as the main tax-status signal. A VIES result can support that B2B process, but even a valid VAT number is not, by itself, proof that every transaction qualifies for reverse charge. The nature of the supply, the customer's status and the place-of-supply rules still matter.

For a B2C digital sale, the operating question is where the customer is established, has a permanent address or usually resides for the relevant rule. That is where the evidence framework below becomes useful. Keeping B2B and B2C separate also prevents a common reporting error in which a valid-looking company field is mixed into consumer location logic or a consumer billing country is mistaken for business VAT validation.

Know the evidence types the EU rules actually recognize

Article 24f of the current consolidated VAT Implementing Regulation lists evidence that can be used for customer location under Article 58. The list includes the customer's billing address, the IP address of the device or another geolocation method, bank details such as the location of the bank account used for payment or the billing address held by that bank, the Mobile Country Code stored on the customer's SIM card, the location of a fixed land line through which the service is supplied, and other commercially relevant information.

That does not mean every Shopify store should collect every signal. The better operating design is to identify which evidence already exists legitimately in your checkout, payment and delivery stack, which system is authoritative for each item, and how the country result is preserved with the order. Collecting more data than you can govern does not make a tax process stronger.

For many ordinary web-based digital sales, billing information plus a second independent location signal may be the practical pair available to the merchant. The exact pair depends on the transaction and systems involved. Do not invent a second signal after the sale or copy the billing country into another field and call it independent evidence. The useful question is whether two real, non-contradictory signals point to the same place under the rule you are applying.

• Billing address is an expressly listed evidence type.
• IP address or another geolocation method is expressly listed.
• Bank-location or bank-held billing details can be evidence.
• SIM Mobile Country Code and fixed-line location are listed for relevant service contexts.
• Other commercially relevant information can matter, but document why it is relevant instead of using a vague catch-all.

Store the evidence as an order-level decision trail

A useful evidence record should let a later reviewer reconstruct the decision without asking the original employee what happened. For each relevant order, keep the order reference, customer-status path, each location signal used, the country indicated by each signal, when the signal was captured, the resulting customer-country decision and any exception note. The goal is traceability, not a giant dossier.

Imagine a subscription download purchased with a German billing address and a second independent signal that also points to Germany. The operational record should preserve that those two signals agreed when the tax decision was made. If the store later prepares an OSS report by Member State of consumption, finance can see why the order was grouped under Germany instead of relying on a spreadsheet column with no provenance.

The European Commission's OSS record-keeping guidance specifically says records include information used to determine where the customer is established, has a permanent address or usually resides. It also says OSS records must be retained 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. That is why the evidence decision belongs with the durable VAT record, not only in a temporary checkout session or analytics dashboard.

Create an exception queue when the signals disagree

The most important orders are often the ones that do not fit the happy path. Suppose the billing address points to France, the IP-derived country points to Belgium and a bank signal points to France. Do not silently pick whichever country produces the easiest result. Put the order into a defined exception path and preserve the conflicting signals.

The ordinary Article 24b presumption for the relevant B2C electronic-service scenario refers to two non-contradictory items of evidence. A conflict is therefore an operational signal that the location conclusion needs review. The resolution may involve checking whether one signal is stale, whether the customer entered an old billing address, whether a VPN or travel situation explains the IP result, or whether another permitted and reliable piece of evidence is available. The tax conclusion should follow the applicable rule and facts, not an arbitrary priority list invented by the storefront team.

Give exceptions an owner and a status. A small queue can use fields such as order ID, conflicting countries, evidence sources, reviewer, decision, reason and completion date. That creates a reviewable trail and prevents quarter-close staff from discovering dozens of unexplained mismatches after the underlying transaction is hard to investigate.

Do not confuse the EUR 100,000 evidence simplification with the EUR 10,000 VAT threshold

Two different euro thresholds can appear in discussions of EU digital VAT, and mixing them creates bad rules. The current VAT Implementing Regulation includes a customer-location evidence simplification for qualifying supplies under Article 24b: where the stated conditions are met and the relevant supplies from a business or fixed establishment in a Member State do not exceed EUR 100,000 excluding VAT in the current and preceding calendar year, the presumption can be based on one listed item of evidence supplied by a person involved in the supply other than the supplier or customer.

That EUR 100,000 rule is not the same as the EUR 10,000 place-of-supply simplification discussed in Article 59c and Commission guidance. The EUR 10,000 rule has its own eligibility conditions and should never be presented as a universal trigger for every Shopify merchant. Establishment, transaction type and the current and preceding calendar year matter. A merchant established outside the EU should not assume the same simplification is available merely because a dashboard shows cross-border sales below EUR 10,000.

Treat the thresholds as separate policy fields in your documentation. One can affect the evidence presumption for qualifying customer-location cases; the other can affect where certain qualifying cross-border B2C supplies are taxed. Neither is a substitute for deciding whether the merchant and transaction satisfy the relevant conditions.

Feed the location decision into VAT-rate review, not the other way around

Once the customer-country decision is supported, compare the VAT actually collected with the treatment expected for that country and supply. Do not reverse the logic by choosing the country that matches the tax rate Shopify happened to charge. The evidence determines the location analysis; the tax calculation is then checked against it.

This is where Vatuno fits naturally for a suitable digital-product store. Its current listing says every EU order becomes a VAT record and that the app compares the VAT collected with the official rate for the buyer's country, flagging mismatches before filing. A mismatch can therefore become an exception for finance instead of disappearing inside a quarter total. Vatuno also advertises VIES validation for B2B VAT numbers, sequential PDF invoices and quarterly OSS CSV reports, which makes the same order record useful across validation, invoicing and reporting preparation.

Keep the fit boundary visible. The public listing is framed around stores selling digital products. It does not say that Vatuno registers a merchant for VAT, files an OSS return, makes the tax payment or guarantees that every customer-location conclusion is legally correct. Its explicit reporting output is a quarterly OSS CSV. Treat the app as a structured record-and-reporting layer and keep responsibility for classification, evidence quality and official filing with the merchant and its tax process.

Build the archive around the decision, not just the final CSV

An OSS export is only the end of a chain. If the report says a sale belongs to Spain, a later reviewer should be able to trace the order back to the evidence and classification that placed it there. Archive the reporting output together with the underlying VAT records, the location evidence or references to the systems that hold it, exception resolutions, invoice records and material corrections.

The Commission's OSS guidance requires the relevant records to be available electronically without delay when requested and retained for the 10-year period. That does not mean every team needs one enormous file per order. It means the records must remain retrievable and connected. Stable identifiers and documented retention ownership are more useful than a collection of screenshots scattered across staff folders.

If a payment provider or other third party is the source of an evidence item, document what is retained by your store and what remains in that provider's system. A tax workflow should not depend on data that disappears after a short dashboard-retention period without anyone noticing. Confirm retention and access against your actual providers rather than assuming the Shopify order record contains every signal used in the original decision.

Pilot four cases before you rely on the workflow at scale

Use a small test matrix for the operating design before applying it broadly. First, take a straightforward B2C digital order where two permitted signals point to the same Member State. Second, use a case where the signals conflict and make sure it enters the exception queue rather than being auto-resolved. Third, use a genuine B2B order and verify that VAT-number validation and transaction classification are kept separate from the B2C location-evidence path. Fourth, test a correction or refund and confirm that the location decision remains traceable when the financial record changes.

For the Vatuno portion of the workflow, verify the outputs the public listing actually promises: VAT records, rate-mismatch flags, VIES validation, sequential invoices and quarterly OSS CSV reporting for the advertised digital-product use case. As of September 15, 2026, the official Shopify App Store 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).

A good rollout ends with a written answer to five questions: which transactions enter this evidence workflow, which location signals are used, what happens when they disagree, where the decision trail is retained, and who owns the official VAT return and payment. If those answers are clear, software can remove repetitive work without becoming a substitute for tax judgment.

Apps mentioned in this guide

Frequently asked

Do EU digital-product sales always require exactly two pieces of customer-location evidence?

No. The current EU rules contain specific presumptions for certain service-delivery situations and a conditional EUR 100,000 evidence simplification. In the ordinary Article 24b case for relevant B2C electronic services outside those special situations, the presumption uses two non-contradictory evidence items. Apply the rule that fits the actual transaction rather than turning two pieces into a universal slogan.

Is the EUR 100,000 evidence threshold the same as the EUR 10,000 EU VAT threshold?

No. They address different issues and have different conditions. The EUR 100,000 rule relates to a customer-location evidence simplification in the VAT Implementing Regulation, while the EUR 10,000 Article 59c simplification concerns place of supply for certain qualifying cross-border B2C supplies. Neither should be treated as universal.

Does Vatuno collect every item needed for a two-evidence customer-location test?

The public Shopify App Store listing verifies EU VAT records, country-rate mismatch flags, VIES validation, sequential invoices, quarterly OSS CSV reports and threshold tracking for digital-product stores. It does not explicitly promise a complete two-evidence customer-location collection workflow, so verify that requirement separately rather than inferring it from data-access permissions.

Does a valid VIES result automatically prove that reverse charge applies?

No. VIES validation is one input into a B2B VAT workflow. The transaction still has to meet the applicable customer-status, place-of-supply and liability conditions. Keep validation evidence and transaction classification as separate steps.

Does a Vatuno OSS CSV mean the VAT return has been filed?

No. The current listing advertises quarterly OSS reports as CSV. Treat that as reporting preparation, not proof of VAT registration, official submission, acceptance or payment.

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).