Overview of VAT Processing in VATify
VATify prepares indirect tax filings for Amazon, Stripe and Zalando sellers using the the VAT Transaction Reports from these marketplaces as the primary data source.
The result of our processing work is an Excel file including all relvant information in different tabs that you can easily navigate. This file contains detailed information relating to sales, returns, cross-border fulfilment centre transfers made through the relevant warehouses.
This article explains how Marosa processes transaction reports for VAT compliance purposes. It provides clarity and confidence in:
- The source data used
- The classification logic applied
- The validations and exception controls in place
- The current scope of the process
Our approach ensures structured, transparent and jurisdiction-consistent VAT reporting across all EU registrations.
Amazon Data Retrieval
- The monthly Amazon VAT transactions report becomes available on the 3rd day of the following month.
- It is downloaded automatically via API through VATify’s secure integration.
- All 95 columns of the original Amazon VAT transactions report are imported into VATify to ensure full traceability and audit transparency.
No manual filtering or pre-processing is applied prior to import.
Zalando Data Retrieval
Zalando reports are available monthly during the first week of the month.
They are downloaded automatically via API with the permissions granted by each merchant
All 3 data sources are mapped into VATIFY, including the raw data received and transformations done.
VATify Workings: Outputs Generated
Based on the Amazon and Zalando VAT Transaction Report, Marosa has developed automated logic to calculate in VATify:
- OSS return figures
- Local VAT return figures
- European Sales & Purchases Listings (also known as ESL and ESPL returns, or recapitulative statements)
- SAF-T & Control Statements where required, e.g. Poland and the Czech Republic.
This ensures consistent treatment across jurisdictions and reporting regimes.
All Amazon and Zalando columns are imported into VATify. Additionally, VATify generates three supplementary columns that classify and control the data:
1. ACCEPTED
- YES → Transaction included in calculations.
- NO → Transaction excluded pending clarification or correction.
2. VALIDATIONS
This column shows system-generated messages triggered by specific scenarios. Examples of real validations currently in place include:
- “Amazon reported OSS transactions. According to our database the Company is not registered in OSS. Please confirm the status of your registration and communicate the date of registration.”
- “The Company performed transactions in a country without being VAT registered in it.”
- “Some of the ASIN numbers included in the report are unavailable in your client data. Because of that, we did not calculate all your movements of stock (intra-Community transactions classified in Amazon as INBOUND or FC_TRANSFER). Download the missing ASIN numbers by clicking on ‘Download missing ASINs file’. Upload the completed ASINs file to your ‘My Company’ section and click on ‘Reprocess Amazon Invoices’ to recalculate the return result. You can also choose to proceed without reporting your movements of stock, but please keep in mind that penalties may apply.”
- “Line excluded: Slovakian repair center movements.”
These validations ensure transparency and provide clear corrective actions where necessary.
3. TAX CODES
Marosa has developed a harmonised tax code system to standardise VAT classification across jurisdictions. This column:
- Converts Amazon tax indicators into simplified VAT codes
- Enables automatic mapping to VAT return boxes
- Supports OSS, ESL, ESPL and SAF-T reporting
The first two digits will always correspond to the country code of the taxable jurisdiction of reporting, then the type of transaction, and finally, the VAT rate or exemption applied. This ensures immediate identification of jurisdiction and VAT treatment.
Example: ES_EXG_Z
Where:
- ES = Spain
- EXG = Export of goods
- Z = Zero-rated
A detailed explanation of these codes is available in a separate article.
Additional Data Required in Certain Scenarios
Intrastat Returns
The Amazon or Zalando VAT Transaction Report does not contain commodity codes. If Intrastat thresholds are exceeded in a country:
- Additional information must be requested from the client
- Intrastat cannot be fully completed based solely on the Amazon report in VATify
Intrastat reporting is therefore outside the scope of the automated Amazon VAT logic.
Amazon VAT Calculation Service (VCS)
If sellers wish Amazon to issue invoices on their behalf, Amazon VAT Calculation Service (VCS) must be activated.
Where VCS is not activated, invoice issuance responsibilities remain with the seller and VATify will not be able to generate the Amazon report for VAT filings.
If further clarification is required regarding specific transaction scenarios or jurisdictional treatment, please contact the Marosa VAT team.
Ebay, Shopify and other sources
VATIFY allows users to import data from third party sources directly into VATIFY. The same native file downloaded from your marketplace can be dragged and dropped into VATify, withour software running the transformation in our end.
A dedicated mapping is available for the major third party systems used by VATify users. Reach out to support if you need help finding your mapping file.
Additional information: Structure of the VAT Transaction Report
Key Fields Used for VAT Determination
- TRANSACTION_TYPE: FC_TRANSFER or Inbound represent cross-border fulfilment centre transfers. Additionally, to determine the country of dispatch and arrival of the goods for VAT reporting purposes, we use the columns: DEPART_COUNTRY & ARRIVAL_COUNTRY.
-
SALE_DEPART_COUNTRY and SALE_ARRIVAL_COUNTRY: Used to determine the other types of transactions:
- Domestic transactions
- Intra-Community supplies
- Intra-Community distance sales
- Exports
- EXPORT_OUTSIDE_EU: Indicates whether the transaction qualifies as an export. Supports zero-rating treatment and correct VAT return reporting.
- TAX_CALCULATION_DATE: Date on which VAT is calculated. Determines the VAT reporting period.
- TOTAL_ACTIVITY_VALUE_AMT_VAT_EXCL: Corresponds to the taxable base excluding VAT.
- PRICE_OF_ITEMS_VAT_RATE_PERCENT: VAT rate applied.
- TOTAL_ACTIVITY_VALUE_VAT_AMT: VAT amount charged.
- TOTAL_ACTIVITY_VALUE_AMT_VAT_INCL: Total transaction amount including VAT.
- TRANSACTION_CURRENCY_CODE: Currency of the transaction. If the currency of issuance differs from the reporting country currency, we use "VAT_INV_EXCHANGE_RATE" column to convert amounts into the reporting currency for VAT return purposes.
- BUYER_VAT_NUMBER and BUYER_NAME: Key field for ESL preparation. Used to identify intra-Community B2B supplies.
- TAXABLE_JURISDICTION: Country in which VAT is due. Ensures correct allocation to local VAT or OSS reporting.
- VAT_INV_NUMBER: Invoice reference number.
- TAX_REPORTING_SCHEME: Indicates whether the transaction falls under OSS, local VAT registration or other reporting mechanisms. This field ensures correct allocation to the appropriate return.
- TAX_COLLECTION_RESPONSIBILITY: Identifies whether VAT is collected by Amazon (e.g. deemed supplier scenarios) or by the seller. Where Amazon is responsible, the transaction is excluded from the seller’s output VAT to prevent double reporting.
How does VATify calculate the taxable base for FC_Transfers and Inbound?
When the transaction type is FC_TRANSFER or Inbound, these represent stock movements between Amazon fulfilment centres located in different EU countries where the legal ownership of goods remains with the seller and no change of ownership occurs.
However, these movements give rise to deemed intra-Community transactions and must be recognised for VAT purposes. From a VAT perspective, these generate:
- An intra-Community supply in the country of dispatch
- A corresponding intra-Community acquisition in the country of arrival of the goods.
Amazon does not provide stock valuation in the VAT Transaction Report. Therefore, to calculate the taxable base for FC_Transfers and Inbound movements VATify uses the following metrics:
- ASIN
- Quantity (QTY)
- A client-provided cost list per ASIN (in EUR) uploaded in VATify
The ASIN cost list is mandatory. If cost data is missing, a system validation is triggered, and the movement cannot be fully calculated. Learn more about how to upload the ASIN template in VATify.
Comments
0 comments
Please sign in to leave a comment.