Migration assurance

Settlement Summary PDF vs Flat File V2

Settlement Summary PDF vs Flat File V2 focuses on migration mapping and reconciliation evidence, not generic API copy. Use it to turn a vague migration into a reviewable test case.

Run a free scan

Target keyword: Settlement Summary PDF vs Flat File V2
Removed: Seller Central Settlement Summary or Account Activity PDF totals
Replacement: Flat File V2 normalized amount rows
Removal date: November 11, 2026

TL;DR

Deprecated item	Removal date	Replacement	Migration risk	Scanner detection
Seller Central Settlement Summary or Account Activity PDF totals	November 11, 2026	Flat File V2 normalized amount rows	Finance users can reject a correct API migration if the new rows do not reconcile to the PDF they use for close.	AMZ-SET-RECON-001, AMZ-SET-COLUMN-001

Official status

Amazon documentation lists Seller Central Settlement Summary or Account Activity PDF totals 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.

Mapping table

Settlement Summary PDF vs Flat File V2 should be implemented as a small, reviewable mapping table before release.

Old field or behavior	New field or behavior	Validation rule
PDF settlement total	sum of Flat File V2 canonical amount rows	Match settlement currency and settlement period before comparing totals.
FBA sales	Order rows with amount-type ItemPrice	Separate principal, shipping and tax style rows before summing.
Refunds and promotions	Refund and Promotion amount rows	Explain signs and offsets instead of forcing a zero-delta result.
Disbursement	AmazonDisbursement or settlement transfer rows	Tie final transfer to the statement period and currency.

Validation scenario

Use one closed settlement where finance has the PDF and the raw Flat File V2 file; the proof is a reconciliation note that explains every delta.

Input evidence	Expected proof
Source scan finding	AMZ-SET-RECON-001, AMZ-SET-COLUMN-001 points to the old implementation.
Sample data	The migration sample covers the field, status, amount or identifier in this page.
Reviewer output	A short reconciliation note explains every accepted delta.

Parser or reconciliation example

Use this as the shape of the unit test or review snippet; adjust names to your codebase.

const pdfTotal = decimal('1234.56');
const flatFileTotal = sumCanonicalRows(rows, settlementId, currency);
assertExplainedDelta(pdfTotal.minus(flatFileTotal));

Removed resource and replacement

Old resource	Replacement	Deadline	Validation outcome
Seller Central Settlement Summary or Account Activity PDF totals	Flat File V2 normalized amount rows	November 11, 2026	Finance users can reject a correct API migration if the new rows do not reconcile to the PDF they use for close.

What breaks

Area	Breakage
Code pattern	Code still assumes Seller Central Settlement Summary or Account Activity PDF totals.
Payload or schema	The migration target is Flat File V2 normalized amount rows, so shape, naming or grouping changes.
Permission or data access	Field visibility, role access or accounting availability can differ by marketplace and workflow.
Pagination, status or field mapping	Mapping mistakes can hide under successful HTTP responses unless samples are reconciled.

Before/after example

The example is intentionally small so the migration shape is visible in a code review.

Before:
// Old assumption
Seller Central Settlement Summary or Account Activity PDF totals

After:
const pdfTotal = decimal('1234.56');
const flatFileTotal = sumCanonicalRows(rows, settlementId, currency);
assertExplainedDelta(pdfTotal.minus(flatFileTotal));

Scanner detection

Rule ID	Severity	Evidence pattern	False positive condition	Validation step
AMZ-SET-RECON-001, AMZ-SET-COLUMN-001	HIGH when mapping drift affects accounting, PII or order state	Seller Central Settlement Summary or Account Activity PDF totals	Documentation, comments, generated clients or test fixtures can require manual review.	Capture one production-like sample for Seller Central Settlement Summary or Account Activity PDF totals.

Migration checklist

Capture one production-like sample for Seller Central Settlement Summary or Account Activity PDF totals.
Normalize it into Flat File V2 normalized amount rows.
Run the mapping table against the sample and record unmatched fields.
Reconcile the expected totals, statuses, identifiers or access flags.
Attach the mapping output to the migration ticket.
Re-scan source and keep the sample evidence with the release gate.

Common mistakes

Mapping field names without proving semantic equivalence.
Using one happy-path sample instead of boundary samples.
Skipping re-scan after the mapper or parser is patched.

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.

View sample report Run free scan View pricing

FAQ

What should Settlement Summary PDF vs Flat File V2 prove?

It should prove that Seller Central Settlement Summary or Account Activity PDF totals maps safely to Flat File V2 normalized amount rows for the tested workflow.

What evidence belongs in the ticket?

The source finding, mapping table result, sample input, normalized output and reconciliation note.

Can the page replace production validation?

No. It gives the mapping contract and sample gate; production rollout still needs staged validation.

How does the scanner help?

It flags AMZ-SET-RECON-001, AMZ-SET-COLUMN-001 evidence and links findings to the relevant mapping or validator page.

Official sources

Internal migration links

Validate Settlement Summary PDF vs Flat File V2 in your source

Run a static scan, review the sample report shape, then unlock the detailed migration report when the evidence is useful.

Unlock detailed migration report