Amazon’s Legacy Settlement-Report Deadline Has Passed: Check V2 Imports

Amazon’s November 11 deadline for two legacy SP-API settlement formats has passed. Check Flat File V2 support and reconcile imports.

Two illustrated paper reports join an orange path leading to an aligned ledger sheet and a magnifying glass.

Amazon’s published SP-API schedule set November 11, 2026 as the removal date for two legacy settlement-report formats across all marketplaces. Sellers whose accounting or reconciliation tools still use the XML or older flat-file report should confirm that those tools now support Flat File V2.

This is a previously announced deadline. Amazon published the revised date on March 9, 2026. Its current notice and deprecation table retain November 11, but neither gives a cutoff hour or timezone. Seller Squash has not tested whether the legacy reports have stopped working.

Check the import, not just the download. Flat File V2 changes how amounts and fee descriptions are organized. A successful file download does not establish that an accounting tool has mapped the data correctly.

Which report formats the deadline covers

The removal covers these two report types in Amazon’s Selling Partner API:

  • Legacy XML: GET_V2_SETTLEMENT_REPORT_DATA_XML.
  • Legacy flat file: GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE.

Amazon names GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2 as the replacement. It is tab-delimited, and Amazon is not providing a replacement XML format. The identifiers matter because the older flat-file report and its V2 replacement have similar names.

The deprecation schedule distinguishes the March 17, 2025 deprecation date from the November 11, 2026 removal date. It says calls to removed resources fail from the removal date. That describes Amazon’s stated policy, not an observed failure in a seller account.

Where an unchanged importer can go wrong

Amazon’s migration mapping moves price and fee classification into amount-type and amount-description, with values in amount. The mapping is not entirely one-to-one. Some legacy transaction information moves into the amount description, and some previously separate amounts may be consolidated.

The settlement-report reference also says amounts use local number formatting, including comma decimals such as 95,00. An importer that assumes a period is always the decimal separator needs review. Sellers operating across marketplaces should have their provider check the formats used in each relevant currency and locale.

These are parsing and classification checks. The announcement does not establish that a named software provider is affected, that seller payouts are delayed or that every Seller Central download option is disappearing.

What to ask your accounting provider

  1. Confirm the exact report type. Ask which identifier the provider consumes now. Check internal scripts, spreadsheet import templates and other reporting connections as well.
  2. Validate a real V2 report. Have the person responsible for the integration check amount fields, fee categories, decimal separators, dates and quantities against the source file.
  3. Reconcile a known settlement. Compare the imported settlement total and fee breakdown with the original report. Investigate unmapped entries or unexpected differences before relying on the new import.
  4. Check retrieval and authorization. Amazon generates settlement reports automatically. Applications use getReports to locate them rather than requesting or scheduling their creation. The V2 reference lists the Finance and Accounting role, which the integration owner should verify.

For sellers using a service provider, confirmation of its migration and a checked import are more useful than changing report settings without knowing which connection depends on them.

Sources and verification

Checked November 17, 2026. The published November 11 removal date has passed. Primary sources: Amazon’s March 9 revised removal notice and field mapping, SP-API deprecation schedule and settlement-report reference. These are three pages from one organization, not independent confirmations.

This article reports the published removal schedule. No seller account, provider implementation or API call was tested. Actual enforcement, the precise cutoff time and any seller impact remain unverified. The illustration is an editorial depiction, not an Amazon interface or financial record.

Get seller news on WhatsApp

Follow the Seller Squash channel for Amazon, Walmart and e-commerce updates.

Follow Seller Squash on WhatsApp