Digital Goods and VAT: What Italy’s Probe of In‑App Purchases Means for U.S. Developers and Tax Reporting

Hook: Why Italy’s Activision probe should keep U.S. game developers up at night

Confused about foreign VAT, worried about audits, or unsure if your in‑app purchases trigger overseas taxes? You’re not alone. Italy’s January 2026 probe into Activision Blizzard’s in‑game purchase practices—framed as a consumer‑protection inquiry by the Autorità Garante della Concorrenza e del Mercato (AGCM)—is a reminder that regulators are treating digital monetization, UX design, and tax compliance as overlapping risk areas. For U.S. developers who sell digital goods or operate in‑game economies, this means adding cross‑border VAT and platform compliance to your core tax and product‑governance playbook.

Executive summary: Key takeaways up front

• Digital goods sold to EU consumers are subject to destination VAT—VAT is due where the consumer is located, not where the seller is.
• Who is the supplier of record matters: app stores, marketplaces and direct‑billing each create different VAT responsibilities and audit trails.
• Italy’s probe signals growing regulator linkage between consumer‑protection investigations (like AGCM’s on in‑game tactics) and tax/vat scrutiny—expect more cross‑agency reviews.
• U.S. developers must map customers, confirm supplier status, register (OSS/non‑Union OSS or local VAT), and update pricing and reporting—or pay penalties, interest, and reputational costs.

The context: What Italy is investigating and why it matters for VAT

In January 2026, the AGCM opened two investigations into Microsoft’s Activision Blizzard over alleged "misleading and aggressive" strategies to induce in‑game spending in Diablo Immortal and Call of Duty Mobile. The regulator highlighted UI design and bundled virtual currency sales that may obscure the real cost to consumers—especially minors.

"These practices... may influence players as consumers — including minors — leading them to spend significant amounts... without being fully aware of the expenditure involved." — AGCM press release, Jan 2026

While the AGCM’s mandate is consumer protection and competition, enforcement actions like this ripple into tax and VAT conversations in several ways:

• Consumer protection probes generate transaction records and internal communications that tax authorities can access or request during audits.
• When a regulator questions whether a sale is actually a purchase of virtual currency vs. a promotional bundle, it can change how VAT should be calculated and reported.
• Authorities are coordinating: EU member states increasingly share data on cross‑border digital transactions, raising the odds of VAT enforcement against non‑EU suppliers.

2025–2026 trend snapshot: Why VAT and digital goods enforcement is heating up

From late 2024 through 2026, jurisdictions accelerated rules and enforcement around VAT on digital services. Key trends to watch:

1. Destination taxation is firmly enforced. The EU and many other jurisdictions tax digital services where the consumer is located. Non‑EU suppliers are no longer out of sight.
2. Marketplace and platform liability is expanding. Regulators are pushing marketplaces to take responsibility for VAT collection in specific scenarios—this trend continued into 2025 and gained traction in 2026.
3. Consumer protection + tax enforcement crossover. Regulatory investigations now routinely prompt tax checks; consumer complaints about opaque pricing can become VAT audits.
4. Global parity on taxing digital consumption. Major markets—EU, UK, India, Brazil and parts of Latin America—tightened rules for foreign suppliers of digital goods in 2025–26.

How VAT applies to in‑app purchases and other digital goods

For VAT purposes, most in‑app items—virtual currencies, cosmetics, loot boxes, battle passes—are considered electronically supplied services or digital goods delivered electronically. Under EU rules and similar international frameworks, VAT is due where the consumer is located.

Supplier of record: Why it changes everything

The most consequential question is: who is the supplier of record? There are three common scenarios:

• Platform as merchant of record (MoR): If Apple, Google or a marketplace sells the IAP and collects payment, the platform often collects and remits VAT. The developer receives net proceeds; VAT compliance burden may shift to the platform.
• Developer as merchant of record: If you bill customers directly (via your own payment gateway), you’re responsible for calculating, collecting, and remitting VAT where the consumers are located.
• Marketplace intermediary: Some marketplaces simply facilitate payments; responsibility depends on local law and marketplace rules—sometimes both the platform and the seller can be held liable.

Practical actions: A tactical checklist for U.S. developers (2026 edition)

Start here to get VAT‑ready. These steps separate design assumptions from tax facts.

1. Map revenues by customer location. Use IP geolocation, billing addresses, and payment methods to estimate where buyers are located. For EU, member state rates vary—Italy is 22% standard VAT as of 2026.
2. Confirm supplier of record in contracts and app‑store agreements. Review your agreements with Apple, Google, Microsoft and other platforms. Who is explicitly titled the seller? Save screenshots of store checkout flows.
3. If you’re the seller, register for VAT or OSS. Non‑EU sellers can use the non‑Union OSS (One‑Stop Shop) to report VAT across EU member states instead of registering in every country—verify eligibility and register with a member state’s tax authority.
4. Consider appointing a fiscal representative where required. Some EU countries require non‑EU businesses to appoint a fiscal representative to register for VAT locally. Check Italy’s rules specifically if you have significant Italian users.
5. Revise pricing and UX to show VAT clearly. Display VAT inclusive/exclusive pricing consistently. If you absorb VAT, model margin impacts; if you pass it through, make the charge transparent in product pages and receipts.
6. Update accounting systems and invoices. Capture customer country, VAT rate, invoice lines that show VAT separately, and keep 10+ years of records per EU audit expectations.
7. Implement customer‑type validation. Differentiate B2C vs. B2B: for B2B EU customers with a valid VAT number, the reverse charge may apply (no VAT charged, customer self‑accounts).
8. Prepare for audit linkage with consumer probes. If your UX or bundling is under scrutiny, gather documentation showing how prices, currency bundles, and promotional mechanics were disclosed to users.
9. Discuss VAT and income tax implications with a cross‑border tax advisor. VAT is a consumption tax; for U.S. federal income tax, it’s generally treated as an expense/deduction, not a foreign tax creditable as income tax.

Concrete example: How VAT changes the math on a €10 in‑game purchase

Example assumptions: Consumer in Italy (22% VAT), the developer is the merchant of record, app store fees are 30% before negotiation.

• Customer pays listed price: €10 (you decide whether this is VAT‑inclusive).
• If you display VAT inclusive price: VAT portion = €10 × 22/122 = €1.80. Net price before VAT = €8.20.
• App store fee (30%) applies to the developer gross or net depending on agreement—assume 30% of gross receipts = €3.00.
• Developer receives: €8.20 – €3.00 = €5.20. Developer must remit €1.80 to tax authority via VAT filings.

Net cash to developer = €5.20; VAT remitted = €1.80. If the platform is MoR and remits VAT, the platform keeps VAT and the developer receives a net payment—your income tax reporting still reflects the net proceeds.

U.S. tax reporting: What changes and what stays the same

Two immediate questions U.S. developers ask:

1. Is foreign VAT a foreign tax credit? No—VAT is generally a consumption tax and not creditable as a foreign income tax for U.S. federal foreign tax credits. It’s typically deductible as a business expense on U.S. returns (consult your CPA).
2. Does VAT create U.S. withholding or additional reporting? Not usually. However, payments reported on 1099s and revenue patterns may trigger IRS questions—keep reconciliations and proof of platform remittances.

Also consider these U.S. reporting touches:

• Recognize gross revenue vs. net proceeds based on who is merchant of record—document whether marketplace fees or VAT were deducted before you recognized revenue.
• For U.S. state sales tax: in‑app purchases sold to U.S. consumers may still be subject to state sales tax depending on state rules; integrate state‑level compliance with international VAT obligations.

Marketplace liability and contractual protections

Platform agreements matter more now than ever. Consider these contract and operational controls:

• Get clarity in writing. Ensure your platform agreement states which party is responsible for VAT collection and remittance, who issues invoices, and how VAT is shown to customers.
• Retain proof of platform remittance. If the platform claims to remit VAT, keep confirmation emails, monthly statements and invoices that show VAT collected and remitted by the platform.
• Negotiate indemnities. Ask for indemnification for tax liabilities arising from platform misrepresentations or failures to remit, where feasible.

Responding to enforcement: Steps if you get a VAT or consumer‑protection notice

1. Don’t ignore the notice. In cross‑border matters, silence compounds risk. Respond within deadlines and gather requested transaction logs.
2. Coordinate counsel. Use both a local VAT/fiscal representative in that jurisdiction and a U.S. tax attorney or CPA for income implications.
3. Preserve UX and marketing records. Regulators may probe screenshots, experiment logs (A/B tests), and bundle definitions—retain these for at least the statutory audit period.
4. Perform a retroactive VAT assessment. Quantify potential VAT exposure and model penalties. Many jurisdictions offer voluntary disclosure programs with reduced penalties.

Future predictions for 2026–2028: What developers should budget for

Expect these developments in the next 24 months:

• More platform accountability. EU and some non‑EU regulators will expand requirements for marketplaces to collect VAT on behalf of sellers.
• Greater data sharing across agencies. Tax, consumer protection and competition authorities will coordinate, so a UX complaint can trigger a tax audit.
• National rules diverge on fiscal representation. Some countries will tighten representative requirements, making local fiscal agents more common and costly.
• Increased audit activity. As remote sales rise, expect more audits of small and mid‑sized developers who previously flew under local tax radars.

Checklist: Immediate 30‑day plan for U.S. game and app developers

1. Inventory all IAPs, virtual currencies and subscription products and document how each is presented and priced in the EU.
2. Pull revenue by country for the last 12–24 months using payment provider data.
3. Review platform agreements for merchant‑of‑record language and VAT responsibilities; request written confirmation if ambiguous.
4. If you bill directly to customers, register for the non‑Union OSS or local VAT where you have significant sales, or appoint a fiscal representative where required.
5. Update your product pages and receipts to be transparent about VAT and prices for EU consumers.

Real‑world case study: Hypothetical mid‑sized studio

Studio Alpha, a U.S. mid‑sized mobile game maker, sold $4M in 2025 from EU consumers via direct billing. They assumed Apple/Google remitted VAT. After an AGCM‑like consumer complaint in Italy, Italian authorities requested transaction logs. Studio Alpha discovered €180k in unremitted VAT liabilities for Italian buyers where billing addresses were Italian but platform statements didn’t show VAT remitted. The studio used voluntary disclosure, negotiated reduced penalties, registered for non‑Union OSS, and updated checkout UX to clearly display VAT inclusions.

Key lessons from this hypothetical:

• Relying on assumptions about platform remittance is risky—get documented proof.
• Proactive registration and transparent checkout displays reduce both financial and reputational risk.

When to get outside help

Hire specialist help if any of these apply:

• You have >€50k annual EU B2C digital sales (or local threshold that makes registration sensible).
• Your platform agreements are ambiguous about VAT or you use mixed billing models.
• You received a cross‑border notice from a consumer regulator or tax authority.
• You run major in‑game monetization experiments that could attract consumer scrutiny (loot boxes, limited‑time bundles aimed at minors).

Final thoughts: Treat VAT as product risk management, not just bookkeeping

Italy’s probe into in‑game purchases is a signal flare. Regulators are converging: consumer protection, competition law and tax authorities are all scrutinizing how digital goods are designed, priced and sold. For U.S. developers the practical implication is simple—be proactive. Map your customer base, nail down the supplier of record, register appropriately, and make VAT visible in UX and accounting. The cost of prevention—system updates, advice, and registration—will usually be far lower than the combined cost of taxes, penalties, and a damaged brand.

Actionable next steps (downloadable checklist)

• Export 24 months of sales by country and product SKU.
• Identify merchant of record for each sales channel and gather platform VAT remittance evidence.
• Decide whether to absorb VAT, display VAT inclusive pricing, or pass VAT to customers.
• Register for OSS/non‑Union OSS or local VAT where required; appoint fiscal rep where necessary.
• Schedule a tax‑tech integration: map payments → accounting → VAT returns.

Call to action

If you sell digital goods and haven’t audited your cross‑border VAT exposure in the last 12 months, start now. Download our 30‑day VAT readiness checklist, or book a consultation with a cross‑border VAT specialist to run an exposure model based on your actual transactions. The next enforcement wave is already underway—make compliance a competitive advantage.

Related Reading

• Designing an AI-Powered Nearshore Content Ops Team: Lessons from MySavant.ai
• Compact PC or Prebuilt? Choosing the Right Brain for Your MAME Cabinet in 2026
• The Perfect Teacher Contact Card: What Email, Phone, and Messaging App to Put on Your Syllabus
• Secure Messaging Procurement Guide: Should Your Org Adopt RCS or Stick to Encrypted Apps?
• Pitching Your Travel Series to Big Players: What BBC-YouTube Talks Mean for Creator-Led Travel Shows