Migration assurance
Settlement Report V2 migration: migration guide and scanner checklist
Settlement Report V2 migration explains what replaces GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE and GET_V2_SETTLEMENT_REPORT_DATA_XML, the removal date, the migration risks to validate, and how API Migration Guard detects the pattern.
- Target keyword: Settlement Report V2 migration
- Removed: GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE and GET_V2_SETTLEMENT_REPORT_DATA_XML
- Replacement: GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2
- Removal date: November 11, 2026
TL;DR
| Deprecated item | Removal date | Replacement | Migration risk | Scanner detection |
|---|---|---|---|---|
| GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE and GET_V2_SETTLEMENT_REPORT_DATA_XML | November 11, 2026 | GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2 | Legacy parser and XML workflows must be rebuilt before the closest deadline. | AMZ-SET-REPORT-001 |
Official status
Amazon documentation lists GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE and GET_V2_SETTLEMENT_REPORT_DATA_XML as in-scope for this migration. Use the official source before code freeze because deadlines and replacement details can change.
Amazon settlement report removal changelog Amazon SP-API deprecation schedule
Production Settlement validation plan
Settlement migration is a finance parser rebuild. The production gate is not simply requesting the new report type; it is proving that amount rows, currencies, descriptions and totals reconcile under realistic sample files.
| Validation area | Production proof to collect |
|---|---|
| Report type | Confirm no code path still requests XML or the legacy flat-file report type. |
| Parser contract | Parse by header name and retain amount-type, amount-description, amount and currency together. |
| Locale handling | Validate decimal comma and decimal point samples with deterministic decimal arithmetic. |
| Accounting totals | Reconcile principal, fees, refunds and transfers before replacing close workflows. |
Settlement proof pack
Settlement Report V2 work belongs in the finance release gate. The proof pack should include the requested report type, raw TSV sample, normalized rows, reconciliation totals and an explicit note that XML has no replacement.
- Remove XML parser dependencies from the cutover path instead of waiting for an XML successor.
- Parse by header name so column order changes do not corrupt amount rows.
- Normalize amount values with decimal-safe logic and preserve currency on every row.
- Reconcile amount-type plus amount-description totals before changing financial close jobs.
Removed resource and replacement
| Old resource | Replacement | Deadline | Validation outcome |
|---|---|---|---|
| GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE and GET_V2_SETTLEMENT_REPORT_DATA_XML | GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2 | November 11, 2026 | Legacy parser and XML workflows must be rebuilt before the closest deadline. |
What breaks
| Area | Breakage |
|---|---|
| Code pattern | Legacy settlement report type or parser path for GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE and GET_V2_SETTLEMENT_REPORT_DATA_XML. |
| Payload or schema | Flat File V2 is tab-delimited and collapses discrete fee/price columns into amount fields. |
| Permission or data access | Flat File V2 can require Finance and Accounting role access in Seller Central. |
| Pagination, status or field mapping | Header-name parsing, locale decimal commas and canonical totals replace positional parsing assumptions. |
Before/after example
The example is intentionally small so the migration shape is visible in a code review.
Before:
const type = 'GET_V2_SETTLEMENT_REPORT_DATA_XML'; parseXml(settlement);
After:
const type = 'GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2'; parseTsvByHeader(settlement);Scanner detection
| Rule ID | Severity | Evidence pattern | False positive condition | Validation step |
|---|---|---|---|---|
| AMZ-SET-REPORT-001 | BLOCKER for XML or legacy report type evidence; HIGH for parser assumptions | GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE and GET_V2_SETTLEMENT_REPORT_DATA_XML | Documentation, comments, generated clients or test fixtures can require manual review. | Request a Flat File V2 sample and verify it downloads for the marketplace. |
Migration checklist
- Request a Flat File V2 sample and verify it downloads for the marketplace.
- Parse by header name and normalize amount-type, amount-description, amount and currency.
- Run the Settlement Flat File V2 sample validator with locale decimal examples.
- Reconcile canonical totals before turning off the legacy report path.
Common mistakes
- Looking for an XML replacement even though Amazon removed XML with no XML replacement.
- Reading columns by index rather than by header name.
- Using parseFloat on locale comma amounts such as 95,00.
Sample report preview
The public sample report shows the same evidence shape used by paid reports: rule ID, severity, file location, redacted evidence, migration mapping, validation step and quality gate.
FAQ
What replaces Settlement Report V2 migration?
GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2
Is there an XML replacement?
No. XML settlement workflows must be rebuilt on Flat File V2.
What should finance teams validate?
Header mapping, currency grouping, amount normalization and totals reconciliation against accounting expectations.
Official sources
Validate Settlement Report V2 migration in your source
Run a static scan, review the sample report shape, then unlock the detailed migration report when the evidence is useful.