Migration assurance
Flat File V2 settlement parser: migration guide and scanner checklist
Flat File V2 settlement parser explains what replaces Position-based or legacy settlement parsers, the removal date, the migration risks to validate, and how API Migration Guard detects the pattern.
- Target keyword: Flat File V2 settlement parser
- Removed: Position-based or legacy settlement parsers
- Replacement: Header-name Flat File V2 parser with canonical amount rows
- Removal date: November 11, 2026
TL;DR
| Deprecated item | Removal date | Replacement | Migration risk | Scanner detection |
|---|---|---|---|---|
| Position-based or legacy settlement parsers | November 11, 2026 | Header-name Flat File V2 parser with canonical amount rows | Index-based parsing can corrupt item, fee and currency totals. | AMZ-SET-POSITIONAL-001, AMZ-SET-COLUMN-001 |
Official status
Amazon documentation lists Position-based or legacy settlement parsers 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. |
Flat File V2 parser contract
The parser should accept a raw TSV file and output canonical rows that are stable enough for accounting tests. This gives engineering a concrete target beyond merely downloading the new report type.
| Parser concern | Production rule | Failure mode caught |
|---|---|---|
| Header handling | Trim BOM, normalize header names and read by name, not index. | Column-order changes corrupt totals silently. |
| Amount grouping | Keep transaction-type, amount-type, amount-description, amount and currency together. | Fees and principal amounts merge into the wrong bucket. |
| Locale decimals | Normalize comma and dot decimals before arithmetic. | EUR or marketplace-local samples reconcile incorrectly. |
| Unknown columns | Retain or log unmapped headers during rollout. | Amazon adds a column and the parser drops useful evidence. |
Removed resource and replacement
| Old resource | Replacement | Deadline | Validation outcome |
|---|---|---|---|
| Position-based or legacy settlement parsers | Header-name Flat File V2 parser with canonical amount rows | November 11, 2026 | Index-based parsing can corrupt item, fee and currency totals. |
What breaks
| Area | Breakage |
|---|---|
| Code pattern | Legacy settlement report type or parser path for Position-based or legacy settlement parsers. |
| 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 principal = row[7]; const fee = row[12];
After:
const amount = normalize(row['amount'], row['currency']); const type = row['amount-type'];Scanner detection
| Rule ID | Severity | Evidence pattern | False positive condition | Validation step |
|---|---|---|---|---|
| AMZ-SET-POSITIONAL-001, AMZ-SET-COLUMN-001 | BLOCKER for XML or legacy report type evidence; HIGH for parser assumptions | Position-based or legacy settlement parsers | 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 Flat File V2 settlement parser?
Header-name Flat File V2 parser with canonical amount rows
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 Flat File V2 settlement parser in your source
Run a static scan, review the sample report shape, then unlock the detailed migration report when the evidence is useful.