Migration assurance
GET_V2_SETTLEMENT_REPORT_DATA_XML replacement: migration guide and scanner checklist
GET_V2_SETTLEMENT_REPORT_DATA_XML replacement explains what replaces GET_V2_SETTLEMENT_REPORT_DATA_XML, the removal date, the migration risks to validate, and how API Migration Guard detects the pattern.
- Target keyword: GET_V2_SETTLEMENT_REPORT_DATA_XML replacement
- Removed: GET_V2_SETTLEMENT_REPORT_DATA_XML
- Replacement: No XML replacement; rebuild on Flat File V2
- Removal date: November 11, 2026
TL;DR
| Deprecated item | Removal date | Replacement | Migration risk | Scanner detection |
|---|---|---|---|---|
| GET_V2_SETTLEMENT_REPORT_DATA_XML | November 11, 2026 | No XML replacement; rebuild on Flat File V2 | XML parsing code has no one-to-one replacement and needs a new tab-delimited parser. | AMZ-SET-XML-001, AMZ-SET-REPORT-001 |
Official status
Amazon documentation lists 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. |
No-XML replacement decision tree
This page should make a hard decision obvious: there is no XML successor to wait for. Every XML-specific request, parser and XPath mapping needs to be removed from the cutover path and replaced with a Flat File V2 row normalizer.
| Current evidence | Migration action | Proof before release |
|---|---|---|
| GET_V2_SETTLEMENT_REPORT_DATA_XML constant | Switch the request to GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2. | Scanner no longer reports AMZ-SET-XML-001 or AMZ-SET-REPORT-001. |
| DOM, SAX or XPath parser | Delete the XML parser path and create a tab-delimited parser by header name. | A raw Flat File V2 sample parses without XML dependencies. |
| XML element-to-ledger mapper | Rebuild as canonical amount rows keyed by transaction, amount-type, amount-description and currency. | Ledger totals reconcile on the V2 sample. |
Removed resource and replacement
| Old resource | Replacement | Deadline | Validation outcome |
|---|---|---|---|
| GET_V2_SETTLEMENT_REPORT_DATA_XML | No XML replacement; rebuild on Flat File V2 | November 11, 2026 | XML parsing code has no one-to-one replacement and needs a new tab-delimited parser. |
What breaks
| Area | Breakage |
|---|---|
| Code pattern | Legacy settlement report type or parser path for 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'; new DOMParser().parseFromString(xml);
After:
const type = 'GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2'; parseFlatFileV2(tsv);Scanner detection
| Rule ID | Severity | Evidence pattern | False positive condition | Validation step |
|---|---|---|---|---|
| AMZ-SET-XML-001, AMZ-SET-REPORT-001 | BLOCKER for XML or legacy report type evidence; HIGH for parser assumptions | 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 GET_V2_SETTLEMENT_REPORT_DATA_XML replacement?
No XML replacement; rebuild on 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 GET_V2_SETTLEMENT_REPORT_DATA_XML replacement in your source
Run a static scan, review the sample report shape, then unlock the detailed migration report when the evidence is useful.