Amazon Settlement Report API Changes: Old Files on November 11, Six Orders v0 and Three Finances v0 Calls in 2027

By Bernardo Campelo, Forbes Business Council E-Commerce Leader, Amazon SPN Certified provider, Amazon SP-API authorized partner, and Founder of PrepVia.

As of October 28, 2026, Amazon's SP-API deprecation schedule lists three removals that land on a finance team's desk. Two settlement report types leave the Reports API on November 11, 2026. Six Orders API v0 operations follow on March 27, 2027, and three Finances API v0 operations on August 27, 2027. In Amazon's words, "Removed indicates that calls to the resources fail as of the removal date."

The first date has already moved once. When Amazon announced the settlement change on March 17, 2025, it said the two reports would be unavailable as of March 25, 2026. On March 9, 2026, it moved the removal to November 11, 2026, the date currently scheduled.

None of these removals changes what Amazon pays you. They change the file or the call that your accounting connector, your ERP integration or your own scripts use to book sales, fees and payouts. A tool still reading a removed source fails on the removal date, and the month-end close finds out after.

Every date and name below was checked on October 28, 2026 against Amazon's SP-API documentation and Seller Central help pages, linked where they first appear. Amazon has moved one of these dates before, so check the deprecation schedule again before you plan around it.

The Three Removals

The schedule gives a day, with no time or time zone. Amazon also defines its terms: "Deprecated indicates that the resource is no longer in active development as of the deprecation date," and, in a December 2025 reminder, "Calls to deprecated SP-API resources will continue to be successful until their removal date. After the removal date, calls will fail." The two wordings differ on the removal date itself, so plan for calls to fail on that day.

November 11: The Old Settlement Report Files

The two report types on the list are GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE and GET_V2_SETTLEMENT_REPORT_DATA_XML. Amazon's settlement report documentation names the replacement for both, the Flat File V2 Settlement Report, GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2, and the March 9, 2026 notice adds: "The Flat File V2 Settlement Report is available now and offers the same information in fewer columns and streamlined formatting. An XML replacement report is not available." Both notices say: "This change applies to all marketplaces."

Watch the names. The two reports being removed and their replacement all carry "V2" in their reportType values. What goes on November 11 is the Flat File and XML formats; the Flat File V2 is what stays.

What Amazon says about the V2 file:

• Columns. The separate price and fee columns are condensed into three general-purpose columns, amount-type, amount-description and amount. Amazon's documentation says "Amount values always populate in a single amount column, so there's no need to parse the rows to find a number, even if new fees or transaction types are introduced in the future."
• Format. The file is tab-delimited. Amounts use local currency formats, which Amazon illustrates with 95,00 for the EU instead of 95.00. Quantities appear on every row, and posted dates come in two formats, posted-date (MM/DD/YY) and posted-date-time (YYYY-MM-DD HH:MM:SS UTC).
• Role. Amazon's documentation lists only the Finance and Accounting role for the V2 report. The flat file being removed also listed the Inventory and Order Tracking and Amazon Fulfillment roles, so check which roles each app that reads your settlements holds.
• Retrieval. "Settlement reports cannot be requested or scheduled. They are automatically scheduled by Amazon. You can search for these reports using the getReports operation." Through the Reports API, Amazon says, "Reports are retained for a maximum of 90 days." If your controls depend on settlement history in the old format, archive those files on your side.

Amazon's notices map the old fields to the new ones. The table below follows them.

Two cautions before you assume anything about Seller Central. First, Amazon's notices are SP-API developer notices: they name the two Reports API report types, and the March 9, 2026 notice says the reports "will be removed for sellers," but neither notice mentions the download buttons in Seller Central. As of October 28, 2026, Amazon's Seller Central help page on downloading payment reports still lists Download XML, Download Flat File and Download Flat File V2 for each settlement period, and no Amazon page we found says whether those buttons change on November 11. Second, Amazon describes the V2 file as available to "Seller Central sellers" and, in Seller Central help, as a file that "Fulfillment by Amazon sellers can use." It does not say on those pages that every account already receives it. Check that V2 files exist for each selling account now. Amazon's older help page on the payments statement view, written for the classic Reports > Payments > Past Settlements page, says that if there is no Download button for a period, you can click Request Report and come back in a few minutes; in the new Seller Central, Amazon's download help points to Finance Report instead.

Do not confuse settlement reports with the Date Range reports in the Reports Repository. Amazon's help page on Date Range reports says they are separate from settlement reports: "Settlement reports reflect payout timing. Date Range reports reflect activity timing." Amazon changed the Date Range Transaction and Summary reports in 2026 for sellers under delivery date-based reserves such as DD+7, adding Transaction status and Transaction release date columns to the Transaction report. Amazon announced that change separately from the November 11 removal. Our post on Amazon FBA cash flow under DD+7 covers the reserve itself.

March 27, 2027: Orders API v0

Amazon launched the Orders API v2026-01-01 on January 28, 2026, and its notice is direct: "If you are using the Orders API v0, you must migrate to Orders API v2026-01-01 by March 27, 2027." According to the release notes, the new version "simplifies ten operations into two: getOrder and searchOrders." Amazon's rate limit page lists ten Orders v0 operations, and only six of them are on the removal schedule.

Amazon's Orders API migration guide maps getOrders to searchOrders, and getOrder, getOrderItems, getOrderBuyerInfo, getOrderAddress and getOrderItemsBuyerInfo to the new getOrder. Order items always come back, and buyer and address data come back through an includedData parameter. The guide labels three of the changes below as breaking (pagination, statuses and channels); the other three come from its mapping tables:

• Pagination. NextToken becomes paginationToken, and the token "expires after 24 hours."
• Statuses. OrderStatuses becomes fulfillmentStatuses, with different values. Canceled becomes CANCELLED, with a double L.
• Channels. FulfillmentChannels becomes fulfilledBy: MFN becomes MERCHANT and AFN becomes AMAZON.
• Filters. Searching by PaymentMethods or BuyerEmail is "Not available in v2026-01-01."
• Money. The order total moves to Order.proceeds.grandTotal and requires includedData=PROCEEDS. Amazon says the v0 item price "Could be tax-inclusive OR tax-exclusive; developers could not reliably determine which," while the new version has "Explicit tax handling."
• Missing fields. Some v0 fields have no equivalent yet, among them NumberOfItemsShipped, NumberOfItemsUnshipped and HasRegulatedItems, which Amazon lists as "Under consideration."

Buyer data works differently, not more openly. Amazon's guide says Restricted Data Tokens "are not required to access Personally Identifiable Information (PII) in v2026-01-01. To access PII in v2026-01-01, you only need the appropriate roles assigned." The restricted roles still decide access: for US orders, Amazon's PII table shows buyer name, buyer email, phone and the street lines of the delivery address as available only to apps with the Direct-to-Consumer Shipping (Restricted) role, and only for seller-fulfilled orders.

Two more points for whoever runs the integration. The new search call has a lower default rate limit: Amazon lists 0.0056 requests per second for searchOrders, against 0.0167 for getOrders in v0, and its case for the new design is that it "reduces the number of requests that are needed and improves throttling." And Orders v0 does not disappear entirely: confirmShipment, updateShipmentStatus, getOrderRegulatedInfo and updateVerificationStatus are not on the removal schedule.

August 27, 2027: Finances API v0

Amazon's July 21, 2025 notice deprecated listFinancialEvents, listFinancialEventsByGroupId and listFinancialEventsByOrderId: "If you use any of the deprecated operations, you must migrate to the listTransactions operation in the Finances API v2024-06-19 by August 27, 2027." The same notice points to the TRANSACTION_UPDATE notification, which Amazon sends whenever a new transaction posts to a seller's account. The Finances API v2024-06-19 itself has been available since September 25, 2024.

The data model changes from events to transactions. Finances v0 returns financial events sorted into dozens of typed lists, and, in Amazon's words, "deferred events don't show up in responses until they are released." listTransactions returns transactions with a status of RELEASED, DEFERRED or DEFERRED_RELEASED, related identifiers such as the order, shipment, settlement and financial event group IDs, and nested breakdowns that show how each total was calculated. One line in Amazon's documentation matters for anyone mapping fees to a chart of accounts: "breakdownType is an open-ended string; Amazon does not publish a closed list of values, and new values are added as needed. Build your integration to handle unknown values."

Some things do not change. Both versions say that financial events might not include orders from the last 48 hours, and both return an empty response if the posted-date window is more than 180 days. As of October 28, 2026, we found no field-by-field migration guide for Finances v0 in Amazon's documentation, unlike the one for Orders.

• What stays. listFinancialEventGroups is not on the removal list, and Amazon's own tutorial for matching transactions to a payout still pairs it with listTransactions, filtered by FINANCIAL_EVENT_GROUP_ID and the RELEASED status.
• Roles. listTransactions requires the Finance and Accounting role. In v0, listFinancialEvents also accepted the Amazon Fulfillment role in North America and the Far East and the Account Information Service Provider role in Europe, so an app that relied on either role needs the Finance and Accounting role to migrate.
• New in 2026. The July 29, 2026 release notes added listSummary, for a financial summary by date range or settlement, and listBalances, for a current or past balance. They also added a SETTLEMENT_ID filter value for listTransactions, although the operation's reference page still says only FINANCIAL_EVENT_GROUP_ID and ORDER_ID filter, so test it before you rely on it.
• November 6, 2026. From that date, according to an October 21, 2026 notice, listTransactions can return a new store name value, AMAZON_FBA_FROM_ORIGIN. Amazon calls it "an additive, backwards-compatible change," and tells developers to update their parser "if your application uses strict enum validation."

"When a report your accountant depends on stops existing, the books do not break loudly. They just stop matching."

Bernardo Campelo, Founder of PrepVia

What to Ask Every Vendor Before Each Date

Many accounts do not call these APIs themselves. An accounting connector, an ERP integration, a repricer, a BI dashboard or an agency script does. Amazon publishes these notices for developers, so the questions below have to come from you.

Where a Prep Center Fits

A prep center sits on the other side of the reconciliation: the units that arrived, which become the inventory Amazon receives and, later, the fees and reimbursements in your payouts.

PrepVia receives inventory at our Miami warehouse and routes it into Amazon FBA, and discrepancies are reported within 24 hours of arrival, with photos. Receiving is the 3PL leg of a reconciliation that also runs through the Amazon inventory ledger and your ERP, which our guide to three-way inventory reconciliation walks through.

Frequently Asked Questions

When does Amazon remove the old settlement reports from the SP-API?

Amazon's deprecation schedule lists November 11, 2026 for GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE and GET_V2_SETTLEMENT_REPORT_DATA_XML. The date has moved once already: Amazon first gave March 25, 2026, and changed it on March 9, 2026. Check the schedule again before you plan around it.

What replaces the XML settlement report?

Nothing in XML. Amazon says the Flat File V2 Settlement Report, GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2, replaces both the Flat File and the XML settlement reports, and that "An XML replacement report is not available."

Do the settlement report downloads in Seller Central change on November 11?

Amazon's two notices on this change, from March 17, 2025 and March 9, 2026, are SP-API developer notices. The March 9 notice says the two report types "will be removed for sellers," and neither notice mentions Seller Central. As of October 28, 2026, Amazon's Seller Central help page on downloading payment reports still lists Download XML, Download Flat File and Download Flat File V2, and no Amazon page we found says whether those buttons change.

What replaces getOrders in the Orders API?

searchOrders, in the Orders API v2026-01-01. Amazon says Orders API v0 users must migrate by March 27, 2027, and its migration guide maps the other five removed operations to the new getOrder. confirmShipment, updateShipmentStatus, getOrderRegulatedInfo and updateVerificationStatus are not on the removal schedule.

What replaces listFinancialEvents in the Finances API?

listTransactions, in the Finances API v2024-06-19. Amazon says users of the three deprecated v0 operations must migrate by August 27, 2027.

Is the whole Finances API v0 being removed?

No. The schedule lists three operations: listFinancialEvents, listFinancialEventsByGroupId and listFinancialEventsByOrderId. listFinancialEventGroups is not on it, and Amazon's own tutorial for matching transactions to a payout still uses it with listTransactions.

Does the new Finances API remove the 48-hour delay?

No. Both Finances v0 and listTransactions say financial events might not include orders from the last 48 hours.

Final Take

Three Amazon data sources that many finance stacks still read have removal dates: the Flat File and XML settlement reports on November 11, 2026, six Orders v0 operations on March 27, 2027 and three Finances v0 operations on August 27, 2027. Amazon has published a replacement for each, and none of them is a drop-in swap. The work is finding every tool that reads the old source, getting its migration date in writing and checking the deprecation schedule again before each date.