Compliant EU/UK VAT invoices
Pull the VAT Invoice Data Report (GET_FLAT_FILE_VAT_INVOICE_DATA_REPORT) to get the per-shipment tax breakdown, then generate a legally valid VAT invoice for each order, FBA or seller-fulfilled. Requires VCS enrollment.
The Tax Invoicing (Restricted) role unlocks the buyer data you need to generate compliant tax invoices, VAT, GST and Brazil FBA documents, from Amazon order data. Because those operations require PII to enable tax invoice generation, Amazon does not gate the role on how good your software is. It gates it on compliance. We rebuild the exact security and data-handling file Amazon scores, so the reason behind your refusal is gone.
In Amazon's own words, the role “provides access to operations that generate tax invoices to comply with tax regulation.” It is marked Restricted because, again verbatim, “Operations that require this role require PII to enable tax invoice generation.”
Across three different APIs, the Tax Invoicing (Restricted) role controls access to four distinct things:
1. getOrderBuyerInfo: Orders API v0. Returns buyer information for an order you specify (3-7-7 order ID format), including the buyer’s identity and tax details. Rate 0.5 rps, burst 30. The operation is marked deprecated in the reference but is still listed under this role.
2. GET_FLAT_FILE_VAT_INVOICE_DATA_REPORT: via createReport in the Reports API v2021-06-30. The VAT Invoice Data Report (VIDR) carries transaction-level tax-calculation detail; it is only available to sellers enrolled in the VAT Calculation Service (VCS).
3. GET_EASYSHIP_DOCUMENTS: via createReport in the Reports API v2021-06-30. Contains the invoice, shipping label and warranty documents for an Easy Ship order (India seller-fulfilled program).
4. The Invoices API v2024-06-19, all operations. Released September 25, 2024, it retrieves Brazilian FBA invoices only and runs in the NA region.
Definition and PII wording above are Amazon’s, from the official Tax Invoicing role page and roles in the Selling Partner API.
Operation names, report types and API version strings are kept exactly as Amazon publishes them. These are the calls your invoicing logic will make once the role is approved.
The role is restricted because its operations require PII to enable tax invoice generation. These are the exact fields involved.
Buyer identity: through getOrderBuyerInfo, the OrderBuyerInfo object returns BuyerName, an anonymized BuyerEmail, BuyerCounty, the PurchaseOrderNumber the buyer entered at checkout, and BuyerTaxInfo.
Buyer tax identity: BuyerTaxInfo contains CompanyLegalName (the legal name of the buyer’s company), TaxingRegion (the country or region imposing tax) and TaxClassifications (the list of tax classifications, i.e. the buyer’s tax IDs / VAT / GSTIN type). This is the core PII/tax-ID data that makes the role restricted.
Transaction-level tax data and documents: the VAT invoice report rows, the Brazil FBA invoice documents and the Easy Ship invoices and labels all carry buyer name, address and tax IDs.
The Restricted Data Token (RDT). Reports that contain PII must be pulled via the RDT flow, not a plain LWA access token. Your app must also have the Tax Invoicing (Restricted) role selected on both the App registration page and the developer profile. Because all of this is PII, Amazon requires “additional information about your data use and security controls”, the compliance file we build.
The role is narrow: you only need it if your app actually generates or retrieves tax invoices or buyer tax data. General order sync does not need it. These are the concrete jobs it is built for.
Pull the VAT Invoice Data Report (GET_FLAT_FILE_VAT_INVOICE_DATA_REPORT) to get the per-shipment tax breakdown, then generate a legally valid VAT invoice for each order, FBA or seller-fulfilled. Requires VCS enrollment.
Search, retrieve and bulk-export Brazilian FBA invoice documents with the Invoices API v2024-06-19, getInvoicesDocument returns a ZIP of XML files, so sellers can manage their bookkeeping.
Pull GET_EASYSHIP_DOCUMENTS to print the invoice, shipping label and warranty document for each Easy Ship order in one step.
Use GET_GST_MTR_B2B_CUSTOM and GET_GST_MTR_B2C_CUSTOM to reconcile sales, refunds and cancellations against Amazon Business and consumer invoices.
Feed SC_VAT_TAX_REPORT and GET_VAT_TRANSACTION_DATA into accounting or tax software to reconcile shipments, returns, refunds and cross-border movements.
Use getOrderBuyerInfo to fetch the buyer’s CompanyLegalName and tax classification, and put them in the header of a compliant B2B invoice.
A restricted-role review is a data-protection assessment. Because this role exposes buyer tax PII, Amazon asks for documented evidence of your data use and security controls. We assemble that file for you, and we never need your code, your servers or your Amazon account.
Application answers, ready to submit: every questionnaire answer plus the free-form security and architecture responses, with a role justification stating exactly why you need getOrderBuyerInfo, the VAT/Easy Ship reports or the Invoices API, and why the buyer tax PII is genuinely necessary.
A publishable Data Handling & Privacy Policy: a ready-to-publish page covering how you collect, process, store, use, share and dispose of BuyerTaxInfo and the other PII fields. One of the two things Amazon checks for a private app.
A plain-language implementation checklist: every control Amazon scores: PII kept no longer than 30 days after delivery then securely deleted; the Restricted Data Token (RDT) flow for PII reports; the role selected on both the App registration page and the developer profile; encryption in transit and at rest; least-privilege access with MFA; PII-free logs; and an incident-response runbook. Your IT lead implements it point by point.
Amazon rarely tells you what went wrong. The decision almost always comes down to one phrase, your security and compliance documentation did not meet requirements. For this role specifically, that usually means one or more of these:
Amazon reviews evidence, not promises. We remove every one of these reasons, so there is no compliance ground left to refuse you on.
Start the form and we will confirm your roles, your path and your next steps. The standard restricted-role file is 650 €, delivered in 48 hours, obtained or refunded subject to our T&Cs. Building invoicing software for many sellers? Book a call for a tailored scope.
Content reviewed by Loïc Segui (COO & CTO), Fenchell’s Marketplace Compliance Team · last updated 29 June 2026. Technical facts, operation names, report types, API version strings and PII fields, are verified against Amazon’s live Selling Partner API documentation. We never promise approval: even when your file is prepared correctly, Amazon retains the right not to grant restricted access without justification. The figures shown on this page (accesses obtained, success rate) are based on real client cases and do not constitute a guarantee of outcome. Fenchell Capital OOD, Bulgarian firm based in Plovdiv (EIK 207945095).
Best Service. “Getting approved for access to the Amazon API was a real challenge for us. Fenchel and their team stepped in, audited our functionality, and helped us understand precisely what Amazon's software review team was looking for — which made all the difference.”