Amazon Settlement Report Parser

Drop your Flat File V2 settlement report and see exactly how the payout was built — fee breakdown, reserves, out-of-period postings, per-SKU net. Free, no sign-up.
中文 · Home
🔒 Your file never leaves this computer. Everything is parsed in your browser — there is no upload, no server, no analytics call. Disconnect from the internet and it still works. Open DevTools → Network and check for yourself.
Drop your settlement report here, or click to choose
Seller Central → Payments → All Statements → Download Flat File V2 (.txt or .csv — the contents are tab-separated)

Amazon Settlement Report (Flat File V2) — field and fee-code reference

Last updated: 2026-08-12 · Column list from Amazon's official SP-API documentation. Value enumerations are not published by Amazon and are collected from third-party documentation and from real reports. Corrections and new values are welcome — they get added here.

Report type

ItemValue
Current report typeGET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2 (Seller Central sellers)
DeprecatedGET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE, GET_V2_SETTLEMENT_REPORT_DATA_XML
DelimiterTab
How it is producedAutomatically scheduled by Amazon — it cannot be requested on demand
Where to downloadSeller Central → Payments → All Statements → Download Flat File V2
RetentionRoughly the last 90 days (about six settlement periods)

The file extension is commonly .txt or .csv while the contents are tab-separated. Detect the delimiter, do not trust the extension.

The 24 columns, in order

settlement-id · settlement-start-date · settlement-end-date · deposit-date · total-amount · currency · transaction-type · order-id · merchant-order-id · adjustment-id · shipment-id · marketplace-name · amount-type · amount-description · amount · fulfillment-id · posted-date · posted-date-time · order-item-code · merchant-order-item-id · merchant-adjustment-item-id · sku · quantity-purchased · promotion-id

Amazon's documentation lists these column names but does not give data types or nullability.

Observed values for amount-type → amount-description

amount-typeamount-description values seen
ItemPricePrincipal · Shipping · GiftWrap · Goodwill · RestockingFee · Tax · ShippingTax
ItemFeesCommission · FBAPerUnitFulfillmentFee · FBAWeightBasedFee · GiftwrapChargeback · ShippingChargeback · RefundCommission · VariableClosingFee · MarketplaceFacilitatorVAT-Principal · MarketplaceFacilitatorVAT-Shipping · DigitalServicesFee
Shipment-FeesFBAPerOrderFulfillmentFee · FBATransportationFee
other-transactionCurrent Reserve Amount · Previous Reserve Amount Balance · Storage Fee · Refund Reimbursal · StorageRenewalBilling · DisposalComplete · ShippingHB · Subscription Fee
Promotion(seen as a type; descriptions vary by account)

Known unknowns — what Amazon does not document

These gaps are the reason most reconciliation tools quietly get things wrong. Stating them plainly:

GapConsequence
No official enumeration for transaction-type. The Order / Refund / Transfer / Liquidations list circulating online has no citable Amazon source.Any tool that hard-codes those four will silently drop rows it doesn't recognise. This parser classifies nothing and shows every value.
No official enumeration for amount-type or amount-description.New fee codes appear without notice. A hard-coded mapping goes stale silently.
No documented sign convention.Whether a fee is negative is inferred, not specified.
No documented character encoding.Non-ASCII SKU or product names can corrupt on import.
No documented summary-row structure. In practice the first row carries only settlement-id, the dates, total-amount and currency.Read as a data row, it double-counts the total.
No data types or nullability for any of the 24 columns.Parsers guess.

Why your numbers don't match — five specific causes

1 · The reserve is missing

Under amount-type = other-transaction you will find Current Reserve Amount and Previous Reserve Amount Balance. Amazon withholds part of the money and releases it in a later period. Compute "order revenue minus fees" without these and the total will never equal the deposit. This is the single most commonly missed item.

2 · posted-date sits outside the settlement period

posted-date is when an individual line occurred. Settlement is cut by settlement-start-datesettlement-end-date. These do not have to coincide, and across a month boundary they usually don't. If your ERP aggregates by posted-date while Amazon settles by period, the two use different definitions — nothing is wrong with the data. Aggregate by settlement period.

3 · One order is many rows

A single order-id appears as several rows — Principal on one, Commission on another, the FBA fee on a third. To attribute to a SKU you must group by order-id plus order-item-code. Grouping by order-id alone merges an order containing two different items.

4 · quantity-purchased is repeated, not per-row

quantity-purchased is restated on every row belonging to the same order item. Summing the column multiplies the quantity by the number of rows. De-duplicate by order-id + order-item-code first. This one is easy to miss because nothing errors — you just get a plausible wrong number.

5 · Currencies get added together

Flat File V2 has one currency column and no exchange-rate column. Figures from different settlements in different currencies cannot be summed. Group by currency and keep them apart.

About this page

I build data pipelines and reconciliation tooling, and I spent several years in cross-border e-commerce before that. This parser runs entirely in your browser because financial exports are not something you should have to upload to a stranger. If you find a fee code that isn't listed above, send it over to support@nexusaistart.com — the reference gets updated and everyone benefits. If you need several accounts archived and merged automatically each month, that's the paid version of this: support@nexusaistart.com

Version 1.3 · 2026-08-12 · Contact support@nexusaistart.com
The fee-code reference below is updated as new values turn up. Your copy is static; the current one is always at nexusaistart.com/tools/amazon-settlement-parser/