@comchatx/cx-amazon-finance-playbook 0.0.0-stage → 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (71) hide show
  1. package/LICENSE +21 -0
  2. package/README.md +13 -2
  3. package/README.zh-CN.md +14 -0
  4. package/package.json +106 -4
  5. package/prompts/fees-review.md +5 -0
  6. package/prompts/money-where.md +5 -0
  7. package/prompts/product-earnings.md +5 -0
  8. package/prompts/refunds-review.md +5 -0
  9. package/prompts/settlement-check.md +5 -0
  10. package/research/README.md +65 -0
  11. package/research/areas/fulfilment-charges.md +881 -0
  12. package/research/areas/money-flow.md +1204 -0
  13. package/research/areas/product-profit.md +719 -0
  14. package/research/areas/reconciliation.md +722 -0
  15. package/research/areas/refunds-reimbursements-adjustments.md +813 -0
  16. package/research/areas/selling-fees.md +1019 -0
  17. package/research/areas/tax-and-invoices.md +721 -0
  18. package/research/beyond/sellers-tools-and-research.md +930 -0
  19. package/research/method/finance-surface.md +928 -0
  20. package/skills/fees-and-charges/SKILL.md +36 -0
  21. package/skills/fees-and-charges/references/fulfilment-charges.md +92 -0
  22. package/skills/fees-and-charges/references/inbound-freight.md +51 -0
  23. package/skills/fees-and-charges/references/program-fees.md +69 -0
  24. package/skills/fees-and-charges/references/selling-fees.md +87 -0
  25. package/skills/fees-and-charges/references/where-fees-land.md +51 -0
  26. package/skills/money-flow/SKILL.md +37 -0
  27. package/skills/money-flow/references/booking.md +18 -0
  28. package/skills/money-flow/references/currency.md +56 -0
  29. package/skills/money-flow/references/deferral.md +44 -0
  30. package/skills/money-flow/references/holds.md +46 -0
  31. package/skills/money-flow/references/payouts.md +73 -0
  32. package/skills/money-flow/references/reads.md +60 -0
  33. package/skills/money-flow/references/reserves.md +32 -0
  34. package/skills/money-reads/SKILL.md +39 -0
  35. package/skills/money-reads/references/finances.md +42 -0
  36. package/skills/money-reads/references/history.md +40 -0
  37. package/skills/money-reads/references/payouts.md +32 -0
  38. package/skills/money-reads/references/products.md +26 -0
  39. package/skills/money-reads/references/questions.md +54 -0
  40. package/skills/money-reads/references/reports.md +32 -0
  41. package/skills/money-reads/references/roles-and-tools.md +34 -0
  42. package/skills/product-earnings/SKILL.md +39 -0
  43. package/skills/product-earnings/references/amazon-views.md +58 -0
  44. package/skills/product-earnings/references/economics-dataset.md +52 -0
  45. package/skills/product-earnings/references/import-tax.md +42 -0
  46. package/skills/product-earnings/references/profit-choices.md +88 -0
  47. package/skills/product-earnings/references/research.md +12 -0
  48. package/skills/product-earnings/references/stock-and-landed-cost.md +60 -0
  49. package/skills/refunds-and-reimbursements/SKILL.md +41 -0
  50. package/skills/refunds-and-reimbursements/references/claims.md +41 -0
  51. package/skills/refunds-and-reimbursements/references/lines-and-reads.md +53 -0
  52. package/skills/refunds-and-reimbursements/references/refunds.md +58 -0
  53. package/skills/refunds-and-reimbursements/references/reimbursements.md +87 -0
  54. package/skills/refunds-and-reimbursements/references/tools.md +20 -0
  55. package/skills/refunds-and-reimbursements/references/value-recovery.md +72 -0
  56. package/skills/settlement-reconcile/SKILL.md +40 -0
  57. package/skills/settlement-reconcile/references/accounts-and-stores.md +36 -0
  58. package/skills/settlement-reconcile/references/books-and-tools.md +92 -0
  59. package/skills/settlement-reconcile/references/completeness.md +41 -0
  60. package/skills/settlement-reconcile/references/outside-the-settlement.md +59 -0
  61. package/skills/settlement-reconcile/references/payouts-and-transactions.md +63 -0
  62. package/skills/settlement-reconcile/references/settlement-report.md +42 -0
  63. package/skills/settlement-reconcile/references/timing-and-deferral.md +66 -0
  64. package/skills/tax-lines/SKILL.md +37 -0
  65. package/skills/tax-lines/references/china.md +61 -0
  66. package/skills/tax-lines/references/eu-uk.md +58 -0
  67. package/skills/tax-lines/references/imports.md +18 -0
  68. package/skills/tax-lines/references/lines.md +48 -0
  69. package/skills/tax-lines/references/other-marketplaces.md +37 -0
  70. package/skills/tax-lines/references/reads.md +40 -0
  71. package/skills/tax-lines/references/us.md +37 -0
@@ -0,0 +1,722 @@
1
+ # Reconciling a settlement or a month: tying Amazon's lines to the bank deposit and to the books
2
+
3
+ Read 2026-11-09 by the research seat. Tags: **[official]** Amazon's own page or model (title, URL, date read); **[opinion]** a named practitioner, vendor or developer; **[research]** published study; **[seat]** this seat's reasoning, never a position; **[command-verified]** a command run over a clone of Amazon's models repository (https://github.com/amzn/selling-partner-api-models, commit db2936aa, 2026-10-29) or over pages fetched today.
4
+
5
+ ## What this covers
6
+
7
+ **Scope.** The documents a seller uses to prove that Amazon's money ties out. These are the settlement report (V2 flat file), Seller Central's payment views and date-range reports, the deferred transaction report, and the Finances, Transfers and summary APIs used as reconciliation sources. It covers how each one is structured, how they key to one another (settlement-id, financial event group, trace ID, order-id), and where they disagree: time zone, posting versus release, the deferral, reserves, negative balances, currency and month boundaries. It also covers the accounting practices sellers and their tools apply on top: clearing account, gross versus net, pass-through tax, reserve as an asset, and the deferral accrual. Fees, refunds, money flow and per-product profit belong to sibling seats. This file states what those lines look like inside the reconciliation documents and goes no further.
8
+
9
+ **Feeds.** The pack's payouts/reconciliation skill and its `references/` (settlement columns, identifier map, which document counts what and when). It also feeds the accounting-export facts any profit skill relies on.
10
+
11
+ **Why a senior operator cares.** Every bookkeeper's month-end close is this job. The settlement total is the only Amazon figure that equals a bank line. Every other Amazon figure (Business Reports, the economics dataset, Date Range reports) counts a different set of transactions, or counts them on a different date or clock. Someone who ran this for a large seller knows these points:
12
+ - the settlement file is keyed to payout timing, not to the month;
13
+ - a settlement that crosses month-end has to be split;
14
+ - the reserve is an asset;
15
+ - since late 2024 the deferral has moved sales between months;
16
+ - and since 2026 the Date Range reports changed meaning.
17
+
18
+ **Dated changes since 2025-01-01**
19
+ - 2025-03-17: `GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE` and `…_XML` deprecated. The removal date moved from 2026-03-25 to **2026-11-11**, two days from today [official, deprecation schedule and changelog].
20
+ - 2025-04-30: `listTransactions` marks a released deferral `DEFERRED_RELEASED` [official, release notes].
21
+ - 2025 (changelog undated; GitHub issue opened 2025-06-17): new report type `GET_DATE_RANGE_FINANCIAL_HOLDS_DATA` (Deferred Transaction Report). It is retrievable by API only after the seller requests it in Seller Central [official].
22
+ - 2025-06-10: Amazon Shipping (the carrier service run from Shipper Central) lets shippers generate and pay invoices at any time and pay them automatically by card. These invoices sit outside the Seller Central settlement (§Amazon G) [official, shipping.amazon.com].
23
+ - 2025-06-25: `transactionStatus` filter on `listTransactions`; Amazon Haul `storeName` [official].
24
+ - 2025-07-21: Finances v0 `listFinancialEvents`, `…ByGroupId` and `…ByOrderId` deprecated, with removal on **2027-08-27**. `listFinancialEventGroups` is not on the schedule [official].
25
+ - 2025-09-29 (email quoted by sellers): reserve settings move to DD+7 on **2026-03-12** for accounts not yet on it [official text quoted in Seller Forums by sellers].
26
+ - 2025-12-03: `relatedIdentifierName=FINANCIAL_EVENT_GROUP_ID` filter on `listTransactions` [official].
27
+ - 2026-01-28: `ORDER_ID` filter on `listTransactions` [official].
28
+ - 2026-03-18 (US/CA/MX/BR, by 2026-04-30) and 2026-03-23 to 2026-05-31 (BE/FR/DE/IE/IT/NL/PL/ES/SE/IN/EG/SA/TR/AE/UK): Date Range Transaction and Summary reports now include deferred **and** released transactions. They are indexed by **posted date**, gain a deferred/released status column and a "Transaction Release Date" column, and apply to periods from 2025-01-01. Other stores followed "by June 30, 2026" [official, News_Amazon].
29
+ - 2026-07-29: `listSummary` and `listBalances` (Finances 2024-06-19), and `listPayouts` and `listExpectedPayouts` (Transfers). The release note also claims a `SETTLEMENT_ID` filter on `listTransactions`. The July model commit (dcb0ef91) did not add it. The filter text entered the model only on 2026-10-28 (df7c6298) and was removed the next day by "Finance API Rollback" (db2936aa, 2026-10-29). The live reference (updatedAt 2026-09-10) never listed it (§SP-API B) [official; command-verified, `gh api` commit patches].
30
+ - 2026-06-05: Amazon's Chinese seller site publishes a DD+7 explainer. It adds facts not in the English pages read: the EDD rule, Disburse on Demand restarting the 14-day cycle, and the deferred row having no payment button (§Amazon C) [official, globalselling.amazon.com].
31
+ - 2026-08-01 (deferred from 2026-04-15): Amazon moves "the small group of advertisers who have been contacted directly" from card billing to deduction from the seller account balance or Pay by Invoice. Amazon says balance deduction is already the method of "the overwhelming majority" of advertisers. Advertising charges then sit inside the settlement rather than on a card statement [opinion: ppc.land, quoting Amazon's announcement, 2026-04-15].
32
+ - 2026-07-29: Invoices API v2026-06-25 launched, **Vendors only**. 2026-09-30: Finance Remittance API v2026-03-17 launched, **Vendors only** [official].
33
+ - 2026-09-21 (practitioner date): the "Finance" workspace in new Seller Central replaces the Payments dashboard paths. Sellers report "Statement View went away" (2026-09-02) and only .txt/.xml settlement downloads under Finance → Reports Hub (2026-09-24) [opinion: selleressentials.com; seller threads].
34
+ - 2026-11-06 (announced): new `BusinessContext.storeName` value `AMAZON_FBA_FROM_ORIGIN` on `listTransactions` [official, changelog 2026-10-21]. The value entered the model on 2026-10-28 (df7c6298) and was removed by the 2026-10-29 rollback (db2936aa). The live reference lists only `AMAZON_HAUL` [command-verified]. Whether the value is returned is open.
35
+
36
+ ## Amazon's own rules
37
+
38
+ ### A. The settlement report (Flat File V2) is generated by Amazon, found, not requested
39
+
40
+ - "Settlement reports cannot be requested or scheduled. They are automatically scheduled by Amazon. You can search for these reports using the `getReports` operation." [official] Settlement Reports, https://developer-docs.amazon/sp-api/docs/report-type-values-settlement.md (updatedAt 2026-10-14), read 2026-11-09.
41
+ - V2 entry: "**reportType value**: `GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2` · **Role**: Finance and Accounting · **Availability**: Seller Central sellers · **Report output type**: Tab-delimited flat file. A settlement report. This report replaces the Flat File Settlement Report and XML Settlement Report. Price columns are condensed into three general-purpose columns: `amount-type`, `amount-description`, `amount`." [official] same page.
42
+ - "The `amount-type` and `amount-description` columns contain the type of charge or fee you have incurred, and indicates whether different fees are related to a common type. Amount values always populate in a single `amount` column … even if new fees or transaction types are introduced in the future. Additionally, amounts are displayed in local currency formats (for example, `95,00` for EU instead of `95.00`)." [official] same page.
43
+ - Attribute list, in Amazon's 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` (24 columns) [official] same page. Amazon gives **no prose definition per column**. The page lists names only.
44
+ - The deprecation notice adds format facts: "Provides quantities for all rows (in line with amounts) and posted dates are provided in two, easily-readable formats, `posted-date` (MM/DD/YY) and `posted-date-time` (YYYY-MM-DD HH:MM:SS UTC)". "Ensures that you don't have empty cells in the `amount-type`, `amount-description`, or `amount` columns". "Categorizes amounts in the `amount-type` and `amount-description` columns in the same row". The V1→V2 map: "price type name, fee type name (Example: item-related-fee-type) → amount-type"; "price type value, fee type value (Example: Commission) → amount-description"; "price amount, fee amount → amount"; "transaction-type → transaction-type or amount-description"; "price type, fee type (Example: other-fee-reason-description) → amount-description (disjointed amounts may be consolidated)". "There is no XML report replacement." "This change applies to all marketplaces." [official] Deprecation of two payment settlement report types, https://developer-docs.amazon/sp-api/changelog/update-deprecation-of-two-payment-settlement-report-types.md, read 2026-11-09. The dates are struck through on the page: "~~March 25, 2026~~ **November 11, 2026**".
45
+ - Removal: "`GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE`, `GET_V2_SETTLEMENT_REPORT_DATA_XML` | March 17, 2025 | November 11, 2026". "**Removed** indicates that calls to the resources fail as of the removal date." [official] SP-API Deprecation Schedule, https://developer-docs.amazon/sp-api/docs/sp-api-deprecations.md (updatedAt 2026-09-09), read 2026-11-09 (live page identical to `web01/sp-api-deprecations.md`).
46
+ - Retention through the API: `getReports` `createdSince` "The default is 90 days ago. Reports are retained for a maximum of 90 days." [official] reports_2021-06-30.json [command-verified]. A settlement older than about 90 days is not findable through `getReports` [seat, from that sentence; practitioners confirm, §What practitioners add].
47
+ - Amazon's staff names three primary payment reports and how they cross-reference: "**Settlement Report**: … including the 'Settlement Period' that covers each payout. **Date Range Report**: … a detailed or summary view of your transactions within a custom date range. **Deferred Transactions Report**: … any payments that have been deferred, including the reason and expected release date. … if you're looking for a specific order payment, you can first check the Transactions view to find the posted date, then use that date to locate the payment in either the Settlement or Date Range report." [official, Amazon staff] Where's My Money? — Mastering Payment Reporting and Reconciliation (Danny_Amazon, 2025-08-26), https://sellercentral.amazon.com/seller-forums/discussions/t/718bf5b9-5500-4e85-942b-7a0a0357354e, read 2026-11-09.
48
+ - What is **not** on Amazon's page today: the survey's search-snippet lines "(usually every 14 days) … tied to the disbursement cycle" and "a manual disbursement starts a new report" do not appear on the live settlement page (updatedAt 2026-10-14) [command-verified: full page read]. The 14-day cycle is stated elsewhere by Amazon (§E).
49
+
50
+ ### B. Settlement-level rows: reserve, previous reserve, and what has no order
51
+
52
+ - Amazon's model names the reserve event: `ReserveEvent`: "A reserve event that is generated at the time a settlement period closes. This occurs when some money from a seller's account is held back." [official] financesV0.json `AdjustmentType` [command-verified].
53
+ - The settlement-file labels "Current Reserve Amount" ("The reserve amount is the amount held back in a settlement period to cover potential expenses such as returns and refunds") and "Previous Reserve Amount Balance" ("The reserve amount from the previous settlement report") come from Amazon's field-definition text as reproduced by Intentwise and by wimoor (Chinese/English). Amazon's Seller Central help page is a JS shell to plain GET, so these are cited second-hand [opinion: Intentwise V1→V2 guide; wimoor 亚马逊财务项中文解释].
54
+ - `DebtRecoveryEvent`: "A debt payment or debt adjustment", with `DebtRecoveryType` `DebtPayment` / `DebtPaymentFailure` / `DebtAdjustment`, `RecoveryAmount`, `OverPaymentCredit`, `ChargeInstrumentList` (Description, Tail, "The amount charged to this charge instrument"), and per item `OriginalAmount`, `GroupBeginDate` and `GroupEndDate` ("The start date and time of the financial event group that contains the debt") [official] financesV0.json [command-verified]. A negative settlement charged to the seller's card therefore shows in v0 as a debt event tied to the group where the debt arose [seat].
55
+ - `FinancialEventGroup.OriginalTotal`: "For a closed financial group, this is the total amount of a disbursement **or a charge amount**. For an open financial event group, this is the current balance." [official] financesV0.json. A closed group can be a charge (money from the seller), not only a payout.
56
+
57
+ ### C. Seller Central's own reconciliation documents (Amazon's words)
58
+
59
+ - **Date Range reports.** "The Date Range reports include individual Transaction reports and Summary reports for orders within a specific range, based on the date when transactions were posted to your account. This may not correspond to the order date or the shipment date. Important: The Date Range reports capture all of the transactions between the first report date at 12:00 a.m. to the last report date at 11:59 p.m. **local time**". Summary is a PDF ("an overview of income, expenses, taxes and fund transfers"). Transaction is a CSV ("a detailed list of the transactions"). The Deferred Transaction report is a CSV ("transactions that are currently deferred"). Account type "All" gives "unified reports for all of your available accounts". There are Month and Custom ranges, with a month "up to one year in the future". "Reports can take up to three hours to generate." [official, Amazon staff] Quick Tip: Date Range reports (Jessica_Amazon_, 2024-04-17), https://sellercentral.amazon.com/seller-forums/discussions/t/a53226d8-554a-427d-a0d9-31c52420377d, read 2026-11-09. The help page it links (Payment Date Range Transaction and Summary reports, `/help/hub/reference/external/201824360`) is a JS shell to plain GET on the .com, .co.uk, -europe, .in, .com.au and .ca hosts [command-verified].
60
+ - **2026 change to Date Range reports.** "By April 30, 2026, we'll update the Date Range Transaction and Summary reports for our US, Canada, Mexico and Brazil stores. This change applies to … Sellers who are subject to delivery-date based reserve policies … **Developers who access transaction reports through the reports API**". "All posted transactions are in one place. Your reports will include both transactions that have already been released to your balance, as well as transactions that are deferred under delivery-date based policies." "Activity is indexed by posted date. The Date/Time column in Transaction reports will reflect the transaction posted date, rather than the release date or payout eligibility date." "There will be a new column in Transaction reports that shows whether a transaction is deferred or released. An additional column, transaction release date … If a transaction remains deferred, the release date field will be blank." "Note that reports for periods before January 1, 2025, will continue to follow the prior format." [official] Updated payment reports simplify accrual reporting for delivery date-based reserves (News_Amazon, 2026-03-18), https://sellercentral.amazon.com/seller-forums/discussions/t/0046a66f-915a-4aa1-b343-d8f47ffcc4aa (duplicate …/25d62b41-65fe-40dc-9a87-52d40c49eda3), read 2026-11-09. EU/UK/IN/Middle East version: "This rollout began on March 23, 2026, and it will continue until May 31, 2026" (News_Amazon, 2026-03-31), https://sellercentral-europe.amazon.com/seller-forums/discussions/t/8fe604f7-ecb8-4930-902e-a700f731ee66. A seller reply (2026-07-24) says the "All (unified reports)" account type was greyed out for them, leaving only "Standard Orders".
61
+ - **Deferred transactions on the dashboard (2024).** "we typically reserve your sales proceeds until seven days after an order is delivered … By November 1, your delivery date reserve amounts will display as Deferred transactions in the Total balance box … Until then, they may still display under the account-level reserve field". "When a transaction is updated from deferred to released, it will no longer be included on the Deferred Transaction report. To download all released transactions from a specific period, select the Transaction report type. Only new transactions posted after this change will show as deferred. Older transactions will remain reserved under account-level reserves until they are released". "You may also still see an account-level reserve if one of your orders has received a claim or chargeback, or if your account is under review." "deferred transactions won't be included in the chart on the Payments dashboard". [official] View your reserved payments in the new Deferred Transactions report (News_Amazon, UK, 2024-10-04), https://sellercentral.amazon.co.uk/seller-forums/discussions/t/5eb04dd2-c1e7-47bb-9bf4-57049bc7d1fe, read 2026-11-09. The 2021 US page post adds that settlement reports include only "transactions which have been disbursed" (survey, https://sellercentral.amazon.com/seller-forums/discussions/t/fa4dc3e343d8205930d783e0cf035427, 2021-09-20).
62
+ - **Statement view / Transaction view** (survey's reads, reused): the Statement view lines are Beginning Balance, Sales, Refunds, Expenses and Account Level Reserves, with the next disbursement. Transaction view lists transactions "within a statement period, up until the prior day's close" and is limited to the last 24 months. The Disbursements tab carries a trace ID [official, Amazon staff Quick Tips, via `04-job-money.md` §1]. GitHub discussion #4015 cites the Transaction view help as `sellercentral.amazon.com/gp/help/200141650`.
63
+ - **DD+7 definition (Amazon's email, quoted by sellers).** "On March 12, 2026 … we'll update your reserve settings to the standard reserve period of seven days after delivery date (DD+7). Most Amazon sellers worldwide already use DD+7. … if you sell a product on January 1 and it's delivered on January 3, then under the DD+7 policy, your funds for that order will become available for disbursement on January 11. When you ship an order, funds are collected and added to your deferred transaction amount. Upon delivery, funds become reserves … After seven days, the funds are moved into your account balance, which can be disbursed automatically through your choice of the automatic settlement cycle or a once daily disburse-on-demand request. The move to DD+7 may cause a one-time cash flow impact". [official text quoted by sellers] DD+7 March 12, 2026 (2025-09-29), https://sellercentral.amazon.com/seller-forums/discussions/t/cd0dfc4d-fbc5-4ded-a0b1-4c7ed989c107; same text at …/afacf90a-3e68-4d8d-87aa-8e66d3c24500, read 2026-11-09. Amazon's English examples count the release on the eighth calendar day after delivery: Jan 3 → Jan 11 here, and Jan 6 → Jan 14 in the staff post cited by the survey. Amazon's Chinese explainer (below) is not consistent with them or with itself. It gives "5月3日签收 … 5月10日资金即被释放" (delivered May 3, released May 10, the seventh day) and, with tracking, "5月5日实际签收 → 5月6日起算7天 → 5月13日资金释放" (delivered May 5, count from May 6, released May 13, the eighth day) [command-verified: arithmetic on Amazon's examples]. The release date of a given transaction is the `maturityDate` Amazon returns, not a count.
64
+ - **DD+7 as Amazon's Chinese seller site states it** (详解|亚马逊DD+7预留金政策:底层逻辑、新旧变化和实操建议, 2026-06-05, https://globalselling.amazon.com/news/news-notices-260605, read 2026-11-09) [official]:
65
+ - Stages: buyer pays (授权冻结); seller ships → "进入延迟交易状态" (deferred); delivered → "转入当前预留金" (current reserve); seven days later → withdrawable by Disburse on Demand or the next 14-day automatic settlement.
66
+ - Delivery date: with valid tracking, the actual delivery date, where "追踪号需被亚马逊记录到至少一次物理承运商扫描才算有效" (tracking counts only after at least one physical carrier scan). Without it, "系统使用最迟预计送达日期 (EDD),EDD = 处理时间 + 运输时间" (the latest estimated delivery date, handling plus transit time).
67
+ - The cycle: "DD+7是在原有结算周期基础上新增的储备金机制,自动结算的14天周期不变" (the 14-day automatic cycle is unchanged). And: "每次通过按需提现提款后,当前结算周期会被"截断"并重新开始计算14天" (each Disburse on Demand truncates the current settlement period and restarts the 14 days). So settlement periods are not all 14 days long [seat, from that sentence].
68
+ - The payment button: "需点击"标准订单"或"发票支付订单"行的"请求付款"按钮。"延迟交易"行的"请求付款"按钮不可用" (request payment on the Standard Orders or Invoiced Orders row; the Deferred transactions row's button is unavailable). DoD can be used once per 24 hours. It is greyed out when nothing is released, when refunds, fees, chargebacks or claims exceed available funds, or when the last request was under 24 hours ago.
69
+ - Migration: "此前已存在于账户级别的预留金额中的DD+7预留金不会迁移到延迟交易" (DD+7 reserves already in the account-level reserve are not moved into deferred transactions).
70
+ - Reports: the new Reports Repository reports show per transaction whether it is deferred or released, and its release date. On business reports not matching payment reports, Amazon recommends the repository's reports.
71
+ - Express Payout: US only; Professional account in good standing, eligible US bank account or eligible Visa/Mastercard debit card, active 90 days or more, no active policy violation. "单笔不超过100万美元,且不支持部分提款" (at most USD 1 million per payout, no partial withdrawal).
72
+ - The article states no transition date. Sellers' threads and cifnews (below) give 2026-03-12 for the remaining accounts, matching the email above.
73
+
74
+ ### D. The deferred transaction report reaches SP-API only after a Seller Central click
75
+
76
+ - "**Deferred Transaction Report** · `reportType` value: `GET_DATE_RANGE_FINANCIAL_HOLDS_DATA` · Roles: Finance and Accounting · Availability: Seller Central sellers · Comma-separated flat file. A point-in-time report that contains a list of deferred transactions. A single report can provide up to 10 years of data. … You must request the Deferred Transaction Report through the **Payments Reports Repository** on Seller Central before you can use the Reports v2021-06-30 API to retrieve the Deferred Transaction Report." [official] Payment Reports, https://developer-docs.amazon/sp-api/docs/report-type-values-payment.md, read 2026-11-09. Same wording, with "This change applies to all marketplaces", in the changelog New: Deferred Transaction Report type for the Reports API, https://developer-docs.amazon/sp-api/changelog/new-deferred-transaction-report-type-for-the-reports-api.md.
77
+ - Its columns are the Date Range Transaction report's columns: `ReportType`, `date/time`, `settlement-id`, `type`, `order-id`, `sku`, `description`, `quantity`, `store`, `fulfillment`, `order-city`, `order-state`, `order-post-code`, `tax-collection-model`, `product-sales`, `product-sales-tax`, `shipping-credits`, `shipping-credits-tax`, `gift-wrap-credits`, `gift-wrap-credits-tax`, `regulatory-fee`, `tax-on-regulatory-fee`, `promotional-rebate`, `promotional-rebate-tax`, `marketplace-withheld-tax`, `selling-fees`, `fba-fees`, `other-transaction-fees`, `other`, `total`, `Tax Amount`, `Total Amount` [official] same page.
78
+ - Amazon's reply on GitHub to "what is the point of report if it cannot be requested programmatically?": "Currently the behavior is consistent across other reports as well. However our team is looking into improving this experience" (weilinggu, "Amazon Selling Partner Services", 2025-06-26). Sellers were still asking for an update on 2026-07-06 [official reply on Amazon's repo] https://github.com/amzn/selling-partner-api-models/issues/4830, read 2026-11-09.
79
+ - **No Date Range Transaction or Summary report type exists in SP-API.** The Report Type Values page lists under Payment only `GET_DATE_RANGE_FINANCIAL_HOLDS_DATA`, and under Settlement only the three settlement types [official] Report Type Values, https://developer-docs.amazon/sp-api/docs/report-type-values.md (updatedAt 2026-09-10). MWS had `GET_DATE_RANGE_FINANCIAL_TRANSACTION_DATA`, "the same report as the Date Range Report that can be downloaded in Seller Central", and it was not carried into SP-API [opinion, developer, selling-partner-api-docs issue #967, 2021-06-30]. Amazon's News post mentions "Developers who access transaction reports through the reports API" (§C). The only such path visible in the docs is the Seller-Central-first pattern of `…_HOLDS_DATA` [seat]. Open question 1.
80
+
81
+ ### E. Payout cycle and disbursement
82
+
83
+ - "In general, Amazon settles seller accounts every two weeks". Deposits can "take up to five business days for the funds to appear in your bank account". Express Payout is for eligible US sellers, with "payouts within 24 hours" [official] How Amazon seller payments work, https://sell.amazon.com/blog/amazon-seller-payments (2025-07-30), via survey §1/§4.1.
84
+ - `FundTransferDate`: "The date and time when the disbursement or charge was initiated. Only present for closed settlements." `TraceId`: "The trace identifier used by sellers to look up transactions externally." `AccountTail`: "The account tail of the payment instrument." `ConvertedTotal`: "The total amount in the currency of the marketplace in which the funds were disbursed." `OriginalTotal`: "in the currency of the marketplace in which the transactions occurred" [official] financesV0.json [command-verified].
85
+ - Transfers `Payout.traceId`: "The banking network's unique identifier for a fund transfer request". `paymentRail`: "The underlying payment network or clearing system used to transmit the payout". `PayoutStatusName`: `STARTED`, `IN_TRANSIT`, `PAID`, `FAILED`, `CANCELLED`, `NO_PAYOUT`. `PayoutTypeName`: `SCHEDULED`, `ON_DEMAND`. `PayoutStatusEntry.failureReason`. `ExpectedPayoutStatusName`: `SCHEDULED`, `DISABLED`, `AT_RISK`, `NO_PAYOUT_EXPECTED`. `relatedIdentifiers` enum: `SETTLEMENT_ID` only [official] transfers_2024-06-01.json [command-verified].
86
+
87
+ ### F. Time zones Amazon states
88
+
89
+ - Settlement V2: `posted-date-time` is "YYYY-MM-DD HH:MM:SS **UTC**" (changelog, §A).
90
+ - Date Range reports: "12:00 a.m. … 11:59 p.m. **local time**" (§C).
91
+ - `listSummary`: "Financial summaries are calculated based on the **marketplace timezone** of the seller, not UTC." [official] Retrieve a financial summary, https://developer-docs.amazon/sp-api/docs/retrieve-financial-summary.md (updatedAt 2026-09-09).
92
+ - `listBalances.lastUpdatedTime`: "The value is in the marketplace's local time zone." [official] finances_2024-06-19.json.
93
+ - The same day's activity therefore falls under different calendar dates in the settlement file (UTC), the Date Range report and `listSummary` (local) [seat, from the four quotes].
94
+
95
+ ### G. Money Amazon bills or pays outside the settlement (gap fill 2026-11-10)
96
+
97
+ A settlement holds only what moves through the seller account's balance. Amazon's own pages name other paths, each with its own document.
98
+
99
+ - **Advertising.** The 2026-08-01 change is above (dated changes; money-flow G4). Amazon Ads: "With Pay by Invoice, we send an invoice at the end of each month, and payment is due 30 days later." "The existing payment method (such as a credit or debit card) will be retained as a backup payment method to ensure uninterrupted service in case of insufficient funds." "This update applies only to the small group of advertisers who have been contacted directly." [official] Update on advertiser payments, https://advertising.amazon.com/library/news/update-on-advertiser-payments, re-read 2026-11-10 (curl). Card and invoice billing therefore remain paths outside the settlement, and the card stays on file even for balance-deducted advertisers [seat, from those sentences].
100
+ - Ads invoices live in the ads console: "Sponsored ads advertisers can now choose to download invoices from the last 90 days for one country or for all countries in their global sponsored ads account … navigate to "Billing history" > click Download invoice statement (last 90 days)". The statement shows "all of your invoices, their payment status, and the amount due for each country" [official] Sponsored ads consolidated invoice statement download is now global (2024-01-12), https://advertising.amazon.com/resources/whats-new/sponsored-ads-consolidated-invoice-statement-download-now-global, read 2026-11-10 (curl).
101
+ - Inside the settlement, v0 `ProductAdsPaymentEvent` ("A Sponsored Products payment event") carries `transactionType` (`charge` / `refund`), `invoiceId` ("The identifier for the invoice that includes the transaction"), `baseValue`, `taxValue` and `transactionValue` ("Equal to `baseValue` + `taxValue`") [command-verified, financesV0.json]. The invoice id ties a balance-deducted ad line to its Ads invoice.
102
+ - **Amazon Lending.** UK: "Repayments are fixed amounts (principal and interest) across the term, and collected monthly directly via Direct Debit." The US page lists partner lenders and does not say how repayment is collected [official, money-flow D7, sell.amazon.co.uk / sell.amazon.com]. v0 `LoanServicingEvent` ("A loan advance, loan payment, or loan refund"; `LoanAmount`; `SourceBusinessEventType` `LoanAdvance` / `LoanPayment` / `LoanRefund`) records loan money that does pass through the account [command-verified]. A Direct Debit repayment shows on the bank statement, not in a settlement [seat, from "directly via Direct Debit"].
103
+ - **Amazon Global Logistics (AGL).** Amazon's help page *Paying for Amazon Global Logistics* (https://sellercentral.amazon.com/gp/help/external/GZJ4B4HXDUEWP4PC) is a JS shell to plain GET and to WebFetch. Search snippets, read 2026-11-10, give: payment in USD from the Seller Central disbursement account, or in CNY by wire transfer through Shipper Central, CNY payment requiring a Chinese tax bureau invoice; "you should have a sufficient balance in your Seller Central account", otherwise Amazon "may seek payment or reimbursement by other means permitted by your seller agreement or applicable law"; the charges appear as "FBA International Freight Shipping Charge" and "FBA International Freight Duties and Taxes Charge" under Reports > Payments; fees are charged against the account within 48 hours after the shipment is received at a fulfilment centre [official via search snippet; not read whole]. AGL paid in USD is therefore inside the settlement, and AGL paid in CNY by wire is outside it [seat].
104
+ - **Amazon Shipping (Shipper Central).** "You no longer have to wait for the end of your billing cycle to view and pay your Amazon Shipping invoice. Now in Shipper Central, you can generate invoices and make payments at anytime". "Do you use a credit or debit card to pay invoices? If so, you can now automatically pay your invoices and set specific payment limits." [official] Amazon Shipping product update: June 2025 (2025-06-10), https://shipping.amazon.com/insights-and-news/product-update-billing-delivery, read 2026-11-10 (curl). Finances v0 release note (2024-11-06): `AdjustmentItem.TransactionNumber` was added "to identify what the adjustment is related to. For example, Amazon Shipping customers can use this to get an invoice number that they can use to identify an Amazon Shipping invoice." [official, `web01/sp-api-release-notes.md`; field present in financesV0.json, command-verified]. So an Amazon Shipping invoice can surface in the seller account as an adjustment carrying its number. Whether every one does is not stated (open question 14). Buy Shipping labels bought in Seller Central are a different product, charged in the settlement (`Shipping label purchase`; selling-fees seat).
105
+ - **Amazon Freight.** "we review past bookings, payments and external financial and credit history so we can come back to them with a fair credit allowance"; "Credit limits can be reviewed on a monthly basis" [official] Amazon Freight UK newsroom, https://freight.amazon.co.uk/newsroom/streamline-credit-limit-approval, read 2026-11-10 (curl). "Amazon Freight is offered by Amazon Logistics, Inc., a freight broker licensed under MC826094." [official] https://freight.amazon.com/faq footer, read 2026-11-10. No Amazon page read says Amazon Freight charges pass through a seller account. Its billing is credit-based and its counterparty is a separate Amazon company [seat, from those lines]. Amazon Freight's US payment-terms page was not found (gap left).
106
+ - **Transparency.** A seller (Seller Forums, "Payment advice not being applied to invoices by Transparency", about 2024) writes "Every month since then, I have paid the bill". Amazon staff (Sandy_Amazon) reply: "The tpncy-noreply-remittance-US@amazon.com address is the correct invoice address", and "the ar-us-transparency@amazon.com is the email that follows up on past due." [opinion, seller; official staff reply on the addresses] https://sellercentral.amazon.com/seller-forums/discussions/t/08aa04b3-a699-4f08-883f-1ce2ead6ab54, read 2026-11-10. Payoneer advertised paying "Amazon Advertising and Amazon Transparency invoices" from a Payoneer account (search snippet; the page now redirects) [opinion]. Transparency codes are therefore invoiced and paid outside the settlement in this seller's case. No Amazon page read states the billing rule (gap left).
107
+ - **Vine** posts inside the settlement (`VineFee`, practitioners; selling-fees P-sell-27).
108
+ - **Seller Wallet and Express Payout.** "Enrolling in Seller Wallet does not change your settlement cycle"; the wallet's balance, transfers and fees are read through the Seller Wallet API with AISP/PISP only (money-flow F3, S5). Express Payout changes the speed of the disbursement (money-flow D4). The settlement ends at the disbursement. Conversion, onward transfers and wallet fees are recorded in the wallet's own statements [seat, from money-flow's quotes].
109
+ - **The card on file** for a negative balance (§B; money-flow G2).
110
+ - **Account-level movements the v0 model names** [command-verified, financesV0.json]:
111
+ - `AdhocDisbursementEvent`, with `TransactionType` "For example, "Disbursed to Amazon Gift Card balance"";
112
+ - `FailedAdhocDisbursementEvent`, with `FundsTransfersType` (e.g. `Refund`), `PaymentDisbursementType` (e.g. `CREDIT_CARD`) and `Status` (e.g. `HARD_DECLINED`);
113
+ - `ValueAddedServiceChargeEvent` ("For example, 'Other Support Service fees'");
114
+ - `CapacityReservationBillingEvent` ("For example, FBA Inventory Fee");
115
+ - `DebtRecoveryEvent.ChargeInstrumentList` (§B).
116
+
117
+ Each records money that moves to or from an instrument other than the bank deposit, or a charge billed at account level.
118
+ - **Amazon's VAT invoices for its own fees** (the tax evidence behind fee lines). Amazon staff (JiAlex_Amazon, about 2025), answering "Reconciling fees to Tax Document Library invoices": "Amazon fee invoices in the Tax Document Library are typically issued monthly"; "Payment reports show fees as they occur throughout the month"; "Use your Order ID as the key identifier"; "They should match, though timing differences at month-end might cause small variations" [official, staff reply] https://sellercentral-europe.amazon.com/seller-forums/discussions/t/2e4ae9c0-3814-4ec2-925a-dfc70f216cec, read 2026-11-10. The tax-and-invoices seat holds the rest: seller fee invoices are known from forum snippets only, and the Invoices API is vendor-only.
119
+
120
+ ### H. How a multi-marketplace, multi-region, multi-account seller is laid out (gap fill 2026-11-10)
121
+
122
+ - **Account shapes.** "Use a North America and Brazil unified account to reach Amazon customers in the US, Canada, Mexico, and Brazil." "Use a Europe account to reach Amazon customers in 28 countries." "Use country-specific Asia-Pacific accounts to reach Amazon customers in …". "Create a North America and Brazil unified selling account and any other regional or country-specific accounts, if needed." [official] Global Selling, https://sell.amazon.com/global-selling, read 2026-11-10 (curl).
123
+ - **SP-API regions and endpoints** [official] SP-API Endpoints (updatedAt 2026-09-09; `web01/sp-api-endpoints.md`):
124
+ - North America ("Canada, US, Mexico, and Amazon Brazil stores"): `https://sellingpartnerapi-na.amazon.com`;
125
+ - Europe ("Ireland, Spain, UK, France, Belgium, Netherlands, Germany, Italy, Sweden, South Africa, Poland, Saudi Arabia, Egypt, Turkey, United Arab Emirates, and Amazon India stores"): `https://sellingpartnerapi-eu.amazon.com`;
126
+ - Far East ("Singapore, Australia, and Amazon Japan stores"): `https://sellingpartnerapi-fe.amazon.com`.
127
+
128
+ Each store's `marketplaceId` is on Store Identifiers (updatedAt 2026-10-23; `web01/store-identifiers.md`).
129
+ - **Authorizations are per account.** "Choose **Authorize app** for each selling partner account that you want your application to access. Each time you choose **Authorize app**, a new refresh token appears." "For selling partner accounts that are merged with accounts in other regions: The **Authorize app** button appears for each of your merged accounts." "To self-authorize a Seller Central account, you must be the Primary User of that account." [official] Authorize Private Applications, https://developer-docs.amazon/sp-api/docs/self-authorization.md (updatedAt 2026-09-09), read 2026-11-10. Private applications: "Maximum of 10 self-authorizations. To add more authorizations, either update the application to be public or remove existing self-authorizations." [official] Authorization Limits (updatedAt 2026-09-09; `web01/application-authorization-limits.md`). The OAuth flows return `selling_partner_id`, "The identifier of the selling partner who authorized your application", and ask applications that "support multiple regions" to direct sellers "to the correct regional Seller Central or Vendor Central URL" [official] Website Authorization Workflow, …/website-authorization-workflow.md, read 2026-11-10. Amazon deactivates authorizations "that have not been renewed by the selling partner in more than 365 days and have not made an API call within this time frame" [official] Selling Partner Authorizations FAQ (updatedAt 2026-10-29).
130
+ - **The subscription across merged accounts** (News_Amazon, "Changes to Professional Selling Plan subscription fees for global sellers", effective 2021-08-01, raw HTML read 2026-11-10 [command-verified]): "if you have merged global accounts, your subscription fee will be divided across these accounts, and will be charged in the currency of each Amazon store. You will be charged subscription fees only where you have active listings during the current month." "All subscription fees will be billed on the same day of the month rather than on the monthly anniversary of your registration in each country or region." "Subscription fees for your Americas-region accounts (United States, Canada, Mexico, and Brazil) will be billed in each country in which you have active listings on your billing day rather than being billed in just one country. The total amount billed will not increase as a result. If you sell in our European stores, you will continue to be charged a subscription fee in just one European country." https://sellercentral-europe.amazon.com/seller-forums/discussions/t/a8ff250bb262db2136bedc7c9bc8d5d8. The cap figure is under Facts for human readers only. No later Amazon text read restates or replaces this. MX's 2026 subscription change is in selling-fees.
131
+ - **The money APIs answer per marketplace and account type** [command-verified, transfers_2024-06-01.json and finances_2024-06-19.json]:
132
+ - `initiatePayout`: "one on-demand payout for each marketplace and account type within a 24-hour period"; its `accountType`: "For supported EU marketplaces, the only account type is `Standard Orders`".
133
+ - `listPayouts`: "Results are grouped by the seller's account groups"; `marketplaceIds`: "If omitted, the response includes payouts from all applicable stores".
134
+ - `listBalances` and `listSummary`: `marketplaceIds` ("If omitted, balances from all applicable marketplaces may be returned") and `accountType` ("The type of account to include in the response").
135
+ - Each transaction carries `sellingPartnerMetadata` (`sellingPartnerId`, `accountType`, `marketplaceId`).
136
+ - The models' example `accountType` values are `Standard Orders`, `STANDARD_ORDERS` and `PAYABLE`. There is no enum.
137
+ - **Seller Central's account types.** Date Range reports offer account type "All" for "unified reports for all of your available accounts" (§C). The payment-request rows are "标准订单" (Standard Orders) and "发票支付订单" (Invoiced Orders) (§C, Amazon China). A2X tells sellers with both to select "Standard and Invoiced Orders" in the Account Type filter when requesting an archived settlement [opinion, A2X]. A seller with invoiced (Amazon Business pay-by-invoice) orders therefore has two account types per store, each with its own balance [seat, from these].
138
+ - **Where cross-border and account-level charges land, as far as Amazon states.**
139
+ - EU removal, disposal and liquidation: "Fees are charged in the currency of the country where your inventory is stored." [official, EU rate card via fulfilment-charges H3]
140
+ - Remote Fulfillment from the US: orders "will appear in your Canada or Mexico Seller account, based on where the customer bought your product", and referral fees "are based on the store where the product was bought" [official via search snippet of vender.amazon.com.mx Remote Fulfillment pages; the fetched page now serves the sell.amazon.com copy without these lines].
141
+ - EFN: the cross-border fee is per order, set by the store where the order is placed and the inventory pool it ships from [official via search snippets of sell.amazon.de/.fr/.co.uk FBA Europe pages].
142
+ - The subscription: as above.
143
+ - Not found in any Amazon text: which store's settlement carries Pan-EU monthly storage, AWD fees or account-wide service fees (gap left; open question 15).
144
+ - **Currency.** Each store settles in its own currency (money-flow P-flow-26; financesV0.json `OriginalTotal` "in the currency of the marketplace in which the transactions occurred"). The ACCS fee tier is computed over cross-currency net proceeds of linked accounts (money-flow P-flow-26, sell.amazon.com).
145
+ - **Not found:** an Amazon page on Seller Central's Global Snapshot (cross-store totals and the rate it converts at), and an Amazon Chinese page on 北美联合账户 / 欧洲联合账户 settlement (gap left).
146
+
147
+ ### I. Faces for testing revenue completeness: shipped units, posted sales, returns and refunds (gap fill 2026-11-10)
148
+
149
+ - **Amazon Fulfilled Shipments** (`GET_AMAZON_FULFILLED_SHIPMENTS_DATA_GENERAL`): "Contains detailed order/shipment/item information including price, courier, and tracking data. You can request up to one month of data in a single report." "This report can only be requested." The page states the request limit and the delay: "Amazon accepts a maximum of 12 requests for this report every 8 hours, per selling partner account. The count includes every request for the report, whether you submit it with `createReport` or a user requests it in Seller Central." "in most cases, there will be a delay of approximately one to three hours from the time a fulfillment order ships and the time the items in the fulfillment order appear in the report. In some rare cases there could be a delay of up to 24 hours." Its columns include `amazon-order-id`, `merchant-order-id`, `shipment-id`, `shipment-item-id`, `amazon-order-item-id`, `merchant-order-item-id`, `purchase-date`, `payments-date`, `shipment-date`, `reporting-date`, `sku`, `quantity-shipped`, `currency`, `item-price`, `item-tax`, `shipping-price`, `shipping-tax`, `gift-wrap-price`, `gift-wrap-tax` and buyer and recipient fields [official] FBA Reports, https://developer-docs.amazon/sp-api/docs/report-type-values-fba.md (updatedAt 2026-10-13), read 2026-11-10.
150
+ - **FBA Customer Shipment Sales** (`GET_FBA_FULFILLMENT_CUSTOMER_SHIPMENT_SALES_DATA`): "condensed item level data on shipped FBA customer orders including price, quantity, and ship-to location", with `shipment-date`, `sku`, `fnsku`, `asin`, `quantity`, `amazon-order-id`, `currency`, `item-price-per-unit` [official] same page.
151
+ - **All Orders** (`GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_GENERAL`, `…_BY_LAST_UPDATE_GENERAL`, `GET_FLAT_FILE_ARCHIVED_ORDERS_DATA_BY_ORDER_DATE`): "The reports return all orders, regardless of fulfillment channel or shipment status." "The date range for these reports is limited to 30 days. However, you can select any start date." The columns include `amazon-order-id`, `order-status`, `order-item-id`, `fulfillment-channel`, `sales-channel`, `sku`, `item-status`, `quantity`, `currency`, `item-price` [official] Order Reports, https://developer-docs.amazon/sp-api/docs/report-type-values-order.md (updatedAt 2026-10-28), read 2026-11-10.
152
+ - **FBA Returns** (`GET_FBA_FULFILLMENT_CUSTOMER_RETURNS_DATA`): "Contains customer returned items received at an Amazon fulfillment center, including Return Reason and Disposition. Content updated daily." Its columns are `return-date`, `order-id`, `sku`, `asin`, `fnsku`, `quantity`, `fulfillment-center-id`, `detailed-disposition`, `reason`, `status`, `license-plate-number`, `customer-comments` [official] FBA Reports.
153
+ - **Seller-fulfilled returns** (`GET_FLAT_FILE_RETURNS_DATA_BY_RETURN_DATE`): "You can request up to 60 days of data in a single report." Its columns include Order ID, Return request date, Return request status, Amazon RMA ID, Label cost, A-to-Z Claim, Return quantity, Resolution, Invoice number and Order Amount [official] Returns Reports, https://developer-docs.amazon/sp-api/docs/report-type-values-returns.md (updatedAt 2026-10-28), read 2026-11-10.
154
+ - **Orders API v2026-01-01**: "This API supports … FBM … FBA (Fulfilled by Amazon) - read only". The `FulfillmentStatus` enum is `PENDING_AVAILABILITY`, `PENDING`, `UNSHIPPED`, `PARTIALLY_SHIPPED`, `SHIPPED`, `CANCELLED`, `UNFULFILLABLE` [command-verified, orders_2026-01-01.json].
155
+ - **The finance side.** v0 `ShipmentEvent` is "A shipment, refund, guarantee claim, or chargeback". It has `AmazonOrderId`, `SellerOrderId`, `MarketplaceName`, `PostedDate` and `ShipmentItemList`. `ShipmentItem` has `OrderItemId`, `OrderAdjustmentItemId` ("An Amazon-defined order adjustment identifier defined for refunds, guarantee claims, and chargeback events") and `QuantityShipped` [command-verified, financesV0.json]. `listTransactions` returns `relatedIdentifiers` including `ORDER_ID` and `SHIPMENT_ID`, with item-level `ORDER_ADJUSTMENT_ITEM_ID`. It filters by `ORDER_ID` (2026-01-28), and "Financial events might not include orders from the last 48 hours" (§SP-API B). The settlement V2 keys are `order-id`, `merchant-order-id`, `adjustment-id`, `shipment-id`, `order-item-code`, `merchant-order-item-id`, `merchant-adjustment-item-id`, `sku` and `quantity-purchased` (§A).
156
+ - **What Amazon's own definitions imply for the test** [seat, from the quotes above; enters no skill as stated]:
157
+ - an order in `PARTIALLY_SHIPPED` has shipped in more than one piece, and each piece has its own `shipment-id` in the shipments report;
158
+ - a `CANCELLED` order appears in the All Orders reports, which cover every status, but has no shipment row;
159
+ - a refund carries an `OrderAdjustmentItemId`, while a return row in the returns reports carries only `order-id` and `sku`, so refunds and returns meet at order and SKU, not at an item id.
160
+
161
+ Whether Amazon posts one `ShipmentEvent` per shipment of a split order is not stated (open question 17). Refunds without a return (FBA Returnless Resolutions) and returns without a refund (claim territory) are the refunds seat's (A7, E1).
162
+
163
+ ### J. How far back each money face reaches (gap fill 2026-11-10)
164
+
165
+ | Face | Horizon Amazon states | Source |
166
+ |---|---|---|
167
+ | Report documents of any type, through the Reports API | "Reports are retained for a maximum of 90 days"; `createdSince` defaults to 90 days ago | reports_2021-06-30.json [command-verified] |
168
+ | Settlement V2 through `getReports` | about 90 days (same rule) | §A |
169
+ | Settlement in Seller Central | older settlements are listed but archived, and a "Request Report" click regenerates them. Amazon states no cut-off | practitioners (A2X, Link My Books); gap left |
170
+ | Date Range Transaction / Summary | "you can generate reports for up to 365 days at a time, going back as far as 2012"; periods before 2025-01-01 keep the old format | KJ_Amazon, "Where to find your Amazon selling reports" (2024-10-31, raw HTML read 2026-11-10); News_Amazon 2026-03-18 |
171
+ | Deferred Transaction report | "A single report can provide up to 10 years of data" | Payment Reports |
172
+ | Transaction view | last 24 months | Amazon staff Quick Tip via survey (§C) |
173
+ | v0 `listFinancialEventGroups` | 180 days per call; no earliest date stated | financesV0.json |
174
+ | v0 `listFinancialEventsByGroupId` | "only retrieves a group's data for the past two years"; removal 2027-08-27 | financesV0.json; Deprecation Schedule |
175
+ | `listTransactions` | 180 days per call; no earliest date stated | finances_2024-06-19.json |
176
+ | `listBalances` `asOfDate` / `listSummary` | no earliest date stated | finances_2024-06-19.json |
177
+ | Orders API v0 and v2026-01-01 | "does not display order data that is more than two years old, except in the JP, AU, and SG marketplaces, for which data from 2016 and after is available" | orders_2026-01-01.json, ordersV0.json [command-verified] |
178
+ | All Orders reports | 30 days per report, "you can select any start date" | Order Reports |
179
+ | Amazon Fulfilled Shipments | one month per report; no lookback stated | FBA Reports |
180
+ | Seller-fulfilled returns by return date | 60 days per report | Returns Reports |
181
+ | Data Kiosk `economics`, `salesAndTraffic`, `sellerAnalytics` | start date "must be no more than two years ago"; a query's documents are kept for the field's `@resultRetention`, which is `P30D` on every field of these schemas | schemas/data-kiosk [command-verified]; dataKiosk_2023-11-15.json |
182
+ | Amazon Ads invoices | consolidated statement of "the last 90 days" | Amazon Ads, 2024-01-12 |
183
+
184
+ Amazon states no horizon for: the Seller Central settlement archive, the earliest date `listTransactions` or `listFinancialEventGroups` return, Ads billing history beyond the 90-day statement, or Shipper Central, AGL, Freight and Transparency invoices (gap left). Once a face's horizon passes, the only copy is the one the seller kept, or a Seller Central document that reaches further back [seat, from the table].
185
+
186
+ ## The SP-API and report faces
187
+
188
+ Every row was checked against the models clone (rates from each operation's Usage Plan table) and Role Mappings for SP-API Operations (updatedAt 2026-10-28, `web01/role-mappings.md`; report types from `web01/role-mappings-for-types.md`) [command-verified]. The seller's ticked roles are Product Listing, Pricing, Brand Analytics, and Finance and Accounting (F&A).
189
+
190
+ ### A. Reports
191
+
192
+ | Report / op | Path | Rate (model) | Role (Role Mappings) | Facts for reconciliation |
193
+ |---|---|---|---|---|
194
+ | `getReports` with `reportTypes=GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2` | `GET /reports/2021-06-30/reports` | 0.0222/s, burst 10 | F&A (report type) | "Either reportTypes or nextToken is required"; `createdSince` default 90 days ago; "Reports are retained for a maximum of 90 days"; a `nextToken` call takes only the token ("Specifying `nextToken` with any other parameters will cause the request to fail"). `createReport` is refused for this type (§Amazon A). |
195
+ | `getReportDocument` | `GET /reports/2021-06-30/documents/{reportDocumentId}` | 0.0167/s, burst 15 | as for the type | URL "expires after 5 minutes" (door.md). Output is tab-delimited, with locale-formatted amounts. |
196
+ | `GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE` / `…_XML` | — | — | V1 flat: Amazon Fulfillment or F&A (Role Mappings); the settlement page also lists Inventory and Order Tracking. XML: F&A | **Removal 2026-11-11.** After that, calls fail. |
197
+ | `GET_DATE_RANGE_FINANCIAL_HOLDS_DATA` | found with `getReports` after a Seller Central request | as `getReports` | F&A | Point-in-time list of deferred transactions, "up to 10 years"; CSV with Date Range columns; a released item leaves the report. |
198
+
199
+ ### B. Finances API v2024-06-19 (`finances_2024-06-19.json`)
200
+
201
+ | Op | Path | Rate | Role | Reconciliation facts |
202
+ |---|---|---|---|---|
203
+ | `listTransactions` | `GET /finances/2024-06-19/transactions` | 0.5/s, burst 10 | F&A (NA, EU, FE) | "Financial events might not include orders from the last 48 hours"; `postedAfter` required unless a related identifier is given; ">180 days apart → empty"; `postedBefore` default and floor "two minutes before the time of the request"; US MFN: "do not supply the `marketplaceId` parameter"; returns `RELEASED`, `DEFERRED`, `DEFERRED_RELEASED` unless `transactionStatus` filters; up to 500 per page; "can return empty pages". |
204
+ | `listSummary` (2026-07-29) | `GET /finances/2024-06-19/summary` | 0.5/10 | F&A | "financial summary for the specified time period or settlement period"; `relatedIdentifierName` "The only possible value is `SETTLEMENT_ID`"; `periodStart`/`periodEnd` are ISO **dates**; marketplace time zone, not UTC; response `netProceeds`, nested `breakdowns`. The reference example's `breakdownType`s are `Sales` → `Product Charges`, `Expenses` → `FBA fees`, `Refunds` (the Statement view's categories) [official, listSummary reference, updatedAt 2026-09-10]. |
205
+ | `listBalances` (2026-07-29) | `GET /finances/2024-06-19/balances` | 0.5/10 | F&A | `balanceType` `AVAILABLE`, `RESERVED`, `TOTAL`, `DEFERRED`, `ACCOUNT_LEVEL_RESERVE`; `asOfDate` gives "historical balances at the specified date" (an ending balance for a month-end close [seat]); sub-balances by account type and marketplace; `lastUpdatedTime` local time. |
206
+
207
+ The `relatedIdentifierName` **response** enum is `ORDER_ID`, `SHIPMENT_ID`, `FINANCIAL_EVENT_GROUP_ID`, `REFUND_ID`, `INVOICE_ID`, `DISBURSEMENT_ID` ("The disbursement ID for Amazon's bank transfer"), `TRANSFER_ID`, `DEFERRED_TRANSACTION_ID`, `RELEASE_TRANSACTION_ID` and `SETTLEMENT_ID` ("associated with the transaction's settlement group"). Item level: `ORDER_ADJUSTMENT_ITEM_ID`, `COUPON_ID`, `REMOVAL_SHIPMENT_ITEM_ID`, `TRANSACTION_ID`. `sellingPartnerMetadata` has `sellingPartnerId`, `accountType` and `marketplaceId`; `marketplaceDetails` has `marketplaceId` and `marketplaceName` [command-verified].
208
+
209
+ **Filter conflict.** The 2026-07-29 release note says "Added the `SETTLEMENT_ID` value for the `relatedIdentifierName` query parameter for the [`listTransactions`] operation. You can use this value to filter transactions by their settlement ID." The model (clone 2026-10-29, commit titled "SPAPI October Release Finance API Rollback") and the live reference page (updatedAt 2026-09-10) both say instead: "`FINANCIAL_EVENT_GROUP_ID` and `ORDER_ID` are the only `relatedIdentifier` with filtering capabilities at the moment. While other `relatedIdentifier` values will be included in the response when available, they cannot be used for filtering purposes." [command-verified, both].
210
+
211
+ The model's history [command-verified, `gh api repos/amzn/selling-partner-api-models/commits?path=models/finances-api-model/finances_2024-06-19.json`, patches read]:
212
+ - The July release (dcb0ef91, 2026-07-29) added `listSummary`'s `SETTLEMENT_ID` but left `listTransactions`' filter list at two values.
213
+ - The October release (df7c6298, 2026-10-28) added "`SETTLEMENT_ID`: the settlement group ID associated with the transaction" to the filter list, together with `AMAZON_FBA_FROM_ORIGIN`.
214
+ - "Finance API Rollback" (db2936aa, 2026-10-29; +2 −13, this one file) removed both.
215
+
216
+ Today `SETTLEMENT_ID` filters `listSummary` only. A `listTransactions` filter by it appears only in the release note, which still carries it (updatedAt 2026-11-04). Open question 2.
217
+
218
+ **Amazon's own payment-to-transactions recipe.** "Call `listFinancialEventGroups` … to retrieve up to 100 financial event groups … find the `FinancialEventGroupId` of the payment … Call `listTransactions` with `relatedIdentifierName = FINANCIAL_EVENT_GROUP_ID`, `relatedIdentifierValue = FinancialEventGroupId`, `transactionStatus = RELEASED`. The response includes up to 500 released transactions associated with the specified financial event group." [official] Determine payment transactions, https://developer-docs.amazon/sp-api/docs/determine-payment-transactions.md (updatedAt 2026-09-09). "Determine which released transactions make up a payment based on matching identifiers" (Finances API page). Note `RELEASED`, not `DEFERRED_RELEASED`. Whether a payout's previously-deferred transactions carry `RELEASED` or `DEFERRED_RELEASED` under that group is not stated. Open question 3.
219
+
220
+ ### C. Finances API v0 (`financesV0.json`)
221
+
222
+ | Op | Path | Rate | Role | Removal | Facts |
223
+ |---|---|---|---|---|---|
224
+ | `listFinancialEventGroups` | `GET /finances/v0/financialEventGroups` | 0.5/30 | F&A; AISP (EU only) | **not scheduled** | Params `FinancialEventGroupStartedAfter`/`…Before` (">180 days apart, no financial event groups are returned"), `MaxResultsPerPage` max 100 default 10, empty pages possible. Amazon's tutorial "Retrieve the financial events …" says to call it "with the `PostedAfter` and `PostedBefore` query parameters", which are not this operation's parameters [command-verified: model vs guide, both 2026-09-09]. |
225
+ | `listFinancialEventsByGroupId` | `GET /finances/v0/financialEventGroups/{eventGroupId}/financialEvents` | 0.5/30 | F&A; AISP (EU) | 2027-08-27 | "Deferred events don't appear … until they are released"; "only retrieves a group's data for the past two years. A request for data spanning more than two years produces an empty response." |
226
+ | `listFinancialEvents` | `GET /finances/v0/financialEvents` | 0.5/30 | F&A; AISP (EU); Amazon Fulfillment (NA, FE) | 2027-08-27 | deferred hidden until released |
227
+ | `listFinancialEventsByOrderId` | `GET /finances/v0/orders/{orderId}/financialEvents` | 0.5/30 | F&A | 2027-08-27 | deferred hidden until released |
228
+
229
+ Amazon's v0 tutorials (all updatedAt 2026-09-09) state:
230
+ - payment amount: "select the financial event groups where `ProcessingStatus` is equal to `Closed`. The `OriginalTotal` property provides the total amount of disbursement or charge";
231
+ - current balance: groups "where `ProcessingStatus` is equal to `Open`" and their `OriginalTotal`.
232
+
233
+ These are Retrieve the amount and status of a payment (…/retrieve-amount-status-payment.md), Retrieve your current balance (…/retrieve-your-current-balance.md) and Retrieve the financial events that make up a financial event group (…/retrieve-financial-events-in-group.md) [official].
234
+
235
+ `FundTransferStatus` has no enum in the model; its only example is `"TRANSFERED"` [command-verified]. Practitioners name other values. Not recorded here.
236
+
237
+ ### D. Transfers API v2024-06-01 (`transfers_2024-06-01.json`)
238
+
239
+ | Op | Path | Rate | Role | Facts |
240
+ |---|---|---|---|---|
241
+ | `listPayouts` (2026-07-29) | `GET /finances/transfers/2024-06-01/payouts` | 0.5/10 | F&A (NA, EU, FE) | Filters `marketplaceIds`, `accountType`, `createdAfter`/`createdBefore`, `payoutId`; "Results are grouped by the seller's account groups … most recent appearing first". Payout carries `id`, `currentStatus`, `statusHistory`, `type`, `amount`, `accountTail`, `paymentMethod`, `creationDate`, `paymentRail`, `traceId`, `period`, `relatedIdentifiers` (`SETTLEMENT_ID`). Tutorial: "Call `listPayouts` with the `payoutId` query parameter to list all payouts for the specified settlement." [official, Retrieve payouts, updatedAt 2026-09-09]. |
242
+ | `listExpectedPayouts` (2026-07-29) | `GET …/payouts/expected` | 0.5/10 | F&A (NA, EU, FE) | `amount` ("Can be null when no payout is expected"), `status`, `period`, `scheduledDate`, `accountTail`, `paymentMethod`, `relatedIdentifiers`. |
243
+ | `getPaymentMethods` | `GET …/paymentMethods` | 0.5/30 | AISP, F&A or PISP (EU) | `paymentMethodType` `BANK_ACCOUNT`, `CARD`, `SELLER_WALLET`; tail; default assignment. |
244
+ | `initiatePayout` | `POST …/payouts` | 0.017/2 | F&A or PISP (EU) | Moves money; "one on-demand payout for each marketplace and account type within a 24-hour period"; returns `payoutReferenceId`, "The financial event group ID for a successfully initiated payout". |
245
+
246
+ **Marketplace conflict.** The model's `info.description` (and the reference page) say "This API supports the following marketplaces: DE, FR, IT, ES, SE, NL, PL, and BE". Role Mappings lists `listPayouts`/`listExpectedPayouts` for "NA, EU, FE" [command-verified]. Whether `listPayouts` answers for a US seller is open (question 4).
247
+
248
+ **Identifier evidence in Amazon's own examples** [command-verified, model examples; examples, not a guarantee]:
249
+ - `FINANCIAL_EVENT_GROUP_ID` example: `4MVaHcsAfaYAlwlaPWrXJxrfUiKfYZ2ooWtY7528FUA` (43-character string). `payoutReferenceId` ("financial event group ID") example: `3DM7DQi8DPAMOLOSaN5HxT0q2waNwH95fopx3AD2Lgc`.
250
+ - `SETTLEMENT_ID` examples: `11888387941` (Transfers; also the example payout `id`), `123456789` (listSummary), `SGI_20240308_001`.
251
+ - The two identifiers have different shapes. The example payout's `id` equals its `SETTLEMENT_ID`.
252
+
253
+ ### E. Notifications
254
+
255
+ `TRANSACTION_UPDATE` (2024-10-14) fires "whenever there is a new transaction posted". It needs an SQS/EventBridge destination [official, via survey §2.1]. It is not a reconciliation document. It is a trigger.
256
+
257
+ ### F. Not for sellers (Amazon says so)
258
+
259
+ - **Finance Remittance v2026-03-17** (`getRemittanceHeaders`, `getRemittance`; role F&A, NA/EU/FE): "programmatic access to **vendor** payment remittance data … the same data available on the **Payments** > **Remittance** view in Vendor Central"; Availability "**Vendors only**"; "remittance data is available from 1 January 2024 onward"; 90-day windows [official] Finance Remittance API, https://developer-docs.amazon/sp-api/docs/finance-remittance-api.md (updatedAt 2026-09-30); Reconcile payments to invoices, …/reconcile-remittance-payments.md. The model's own `info.description` says "selling partner payment remittance data" [command-verified]; the docs page decides: vendors. It is **not** a seller's bank-payment detail.
260
+ - **Invoices v2026-06-25** (`getInvoiceHeaders`, `getInvoice`; F&A per the Invoices API page, NA/EU/FE; **absent from Role Mappings 2026-10-28** [command-verified]): Availability "**Vendors only**"; "The Selling Partner API for Invoices is available for vendors"; "reconciliation with purchase orders"; ≤ 90-day issue-date range [official] Invoices API, https://developer-docs.amazon/sp-api/docs/invoice-api.md (updatedAt 2026-09-09). This settles the survey's open question on its audience.
261
+
262
+ ### G. What the door's roles reach
263
+
264
+ Every seller-side reconciliation read above needs **Finance and Accounting**, which the seller has ticked. Not needed for this area: Amazon Fulfillment (only the removed V1 flat file and v0 `listFinancialEvents` in NA/FE list it, as an alternative); AISP/PISP (EU alternatives, and Transfers' money move); Seller Wallet (AISP/PISP; a separate account product, survey §2.3). Nothing is to be built on those.
265
+
266
+ ### H. Revenue-completeness faces and their roles (gap fill 2026-11-10)
267
+
268
+ Roles from Role Mappings for SP-API Types (updatedAt 2026-09-09; `web01/role-mappings-for-types.md`) and Role Mappings for SP-API Operations (2026-10-28) [command-verified]. "Ticked" means reachable with Product Listing, Pricing, Brand Analytics or Finance and Accounting.
269
+
270
+ | Face | Roles (need at least one) | Ticked? | Facts |
271
+ |---|---|---|---|
272
+ | `GET_AMAZON_FULFILLED_SHIPMENTS_DATA_GENERAL` | Amazon Fulfillment, Inventory and Order Tracking, Pricing | yes (Pricing) | requested only; ≤ 1 month per report; request cap per 8 hours counts Seller Central requests too; 1–3 h lag, rarely 24 h; carries buyer and recipient columns |
273
+ | `GET_FBA_FULFILLMENT_CUSTOMER_SHIPMENT_SALES_DATA` | Amazon Fulfillment | no (asked to add) | item-level shipped FBA units with price |
274
+ | `GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_GENERAL` | Amazon Fulfillment, Direct to Consumer Shipping (Restricted), Inventory and Order Tracking, Pricing | yes (Pricing) | all statuses and channels; 30 days per report, any start date |
275
+ | `GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_GENERAL` | Amazon Fulfillment, Direct to Consumer Shipping (Restricted), Inventory and Order Tracking, Pricing, Product Listing | yes | as above, by last update |
276
+ | `GET_FLAT_FILE_ARCHIVED_ORDERS_DATA_BY_ORDER_DATE` | Amazon Fulfillment, Direct to Consumer Shipping (Restricted), Inventory and Order Tracking, Pricing | yes (Pricing) | archived orders, with `is-replacement-order` |
277
+ | `GET_FBA_FULFILLMENT_CUSTOMER_RETURNS_DATA` | Amazon Fulfillment, Pricing | yes (Pricing) | FBA returns received at a fulfilment centre; daily |
278
+ | `GET_FLAT_FILE_RETURNS_DATA_BY_RETURN_DATE` | Direct to Consumer Shipping (Restricted), Inventory and Order Tracking | **no** | seller-fulfilled returns; 60 days per report. It would open FBM return and label-cost rows. Nothing is built on it. |
279
+ | `searchOrders` (Orders v2026-01-01) | a long list including Finance and Accounting, Pricing, Product Listing | yes | `fulfillmentStatuses` filter; two-year horizon (JP/AU/SG from 2016) |
280
+ | `listTransactions` `relatedIdentifierName=ORDER_ID` | Finance and Accounting | yes | the posted money of one order, deferred included |
281
+
282
+ ### I. Regions, accounts and the money operations (gap fill 2026-11-10)
283
+
284
+ - Every money operation above is called on the regional endpoint of the account's region (NA, EU, FE) with that account's refresh token (§Amazon H). A seller with NA, EU and FE accounts has at least three authorizations, and each additional merged or separate account is another [seat, from Amazon's "Authorize app … for each selling partner account"].
285
+ - Within one authorization, `listBalances`, `listSummary`, `listPayouts` and `listExpectedPayouts` take `marketplaceIds` and `accountType`, and return all applicable stores when they are omitted. `listTransactions` takes one `marketplaceId`, and Amazon notes that US MFN calls should not supply it (§B) [command-verified].
286
+ - The settlement file carries one `currency` and one `total-amount` per file, with `marketplace-name` per row and empty on account-level rows (GitHub #5291, §What practitioners add).
287
+
288
+ ## What practitioners add
289
+
290
+ **English-language accounting connectors and firms**
291
+ - **A2X** (settlement-based summaries to Xero/QBO/NetSuite). A settlement that crosses a month is split "by the month each sale or fee occurred" using a "Carried Forward Balance" account. "The first invoice will total $0.00, and the second invoice will contain the total payout amount that matches your bank deposit"; both are matched to the one bank line. A $0 net settlement over month-end gives "two invoices for equal and opposite amounts" [opinion] A2X support 959804 (Xero), 1984021 (QBO), via search snippets, read 2026-11-09. Reserves: "'Account Level Reserve(s)' in Seller Central … 'Unavailable Balance(s)' in some of their reports, or … 'Current/Previous Reserve Amount(s)' in their settlement flat files. Each of these terms refer to the same thing". Reserve balances "should be recorded as a current asset". "If you sell on separate Amazon marketplaces, each marketplace will have its own reserve balance transactions". A "pending balance" is different: it "relate[s] to how Amazon manages negative settlement balances … Sometimes they will recover this amount from future sales, other times they will charge your credit card and report this amount as a Successful Charge" [opinion] Amazon Reserve Balances (and How to Account for Them), https://www.a2xaccounting.com/ecommerce-accounting-hub/amazon-reserve-balances. DD+7: deferred transactions "don't appear in the settlement file until the cash actually moves". A2X's "Monthly Adjustments for Amazon Deferred Transactions" posts "one journal per marketplace at month‑end" that "accrues orders still in Deferred status, reverses orders that moved from Deferred → Released", into an asset account, "without touching the settlement entry you use to match the bank feed"; the adjustment "is created only after all settlement periods for that month have closed". Vendor's figure: "as much as 20-25 % of your revenue can slip into the following month" [opinion] https://a2xaccounting.com/ecommerce-accounting-hub/amazon-dd-7-deferred-transactions-accounting-challenges-and-a2x-workarounds (2025-08-18).
292
+ - **Bookkeep.** The old Date Range Summary "included released transactions only". The new one includes released and deferred. "The Amazon Summary Entry still matches Amazon's All Statements view, which is organized by payout period and built from released transactions, but not the updated Date Range Summary Report", so Bookkeep retired that template for a "Deferred and Released Sales Summary". It carries two balance lines: "Deferred Balance" (sales not yet released) and "Amazon Balance" (released, awaiting deposit), each broken out "by the date each amount was originally deferred" [opinion] https://www.bookkeep.com/docs/apps/amazon/amazon-date-range-summary-report-update-released-deferred-transactions.
293
+ - **Finaloop** (Emily Burrows, help article "Updated this week"). It gives a three-era timeline of Payments-report timing:
294
+ - before late Oct 2024: sales and fees "Recorded on delivery date";
295
+ - late Oct 2024 to early 2026: "Recorded when funds are Released";
296
+ - early 2026 onwards: back to the deferred date, with status and release-date columns.
297
+
298
+ "Amazon did not adjust past reports … sales and transaction fees starting in late October 2024 are reported about one week later than they were under the old policy". "Amazon's 1099-K report still follows the old method (recording sales when deferred), while the Summary and Transaction reports now only recognize sales when released", so the 1099-K "is not reconciled with their Summary and Transaction reports". The cutover date per account is "typically between February and April 2026" (check the Transaction report). Finaloop does not restate Oct 2024–Dec 2025 [opinion] https://help.finaloop.com/en/articles/10499774-amazon-deferred-transactions-new-policy-update-implications. Amazon's own words say "posted date", not "delivery date" (§Amazon C). The posted date of a shipment-based sale is generally its shipment posting [seat]; Finaloop's "delivery date" wording is the vendor's.
299
+ - **Link My Books.** It describes Account Level Reserve as "not the same as a marketplace fee or a missing payment" and argues for recording fees, refunds, collected taxes and reserve movements separately, not the net deposit [opinion] https://linkmybooks.com/blog/amazon-account-level-reserve-explained-what-it-is-and-how-to-handle-it (2026-07-14). Its deferred add-on posts "deferred" and "released" reversal entries to an "Amazon Deferred Balances" asset account [opinion, survey §3]. Its help has how-tos for downloading Date Range transaction and summary reports (help.linkmybooks.com 10522067, 8727746; titles via search).
300
+ - **Synder** (per-transaction sync). The settlement row "Other Transaction → Current Reserve Amount Balance" is "the amount currently held by Amazon as a reserve (negative amount in the report)" and is booked as a transfer, debit asset "Balance Reserve" / credit clearing. "Previous Reserve Amount Balance" is "the reserve amount that Amazon has released (positive amount in the report)" and is booked the reverse way. For multi-currency, one reserve asset per currency is needed or the sync fails [opinion] https://synder.com/help/per-transaction-sync-synchronizing-amazon-account-level-reserves/.
301
+ - **beancount.io** (2026-08-17). Its chart of accounts: gross sales income, refunds as contra-income, "Amazon Settlement Clearing", "Amazon Reserved Balances", cash. "gross settlement activity always posts against the clearing account; cash moved to your bank is a transfer, not income. The reserve never touches profit and loss." A "full settlement hold" gives a $0 payout that still balances. "A pending balance … is what Amazon shows when you actually owe them money" [opinion] https://beancount.io/blog/2026/08/17/amazon-fba-reserve-holds-marketplace-reserves-asset-accounting-guide.
302
+ - **Webgility** posts each order to QuickBooks with fees, tracks the reserve, and reconciles payouts at deposit. It describes the cash timeline as "sale date plus delivery time plus 7-day hold plus time until next disbursement plus 3 to 5 days for bank transfer" [opinion] https://www.webgility.com/blog/account-level-reserve-amazon.
303
+ - **Nova (novadata.io).** "Business Reports and the ad console report by order date. Settlements report by posted date … The gap is usually 2 to 4 days of unposted orders at the month boundary." Refunds "often post one, two, or three cycles after the original sale". "Storage fees, aged-inventory surcharges, subscription fees … all have empty sku and empty order-id. If you filter the settlement to 'rows with a SKU' you drop these entirely". "The total-amount at the top of a settlement is what Amazon owes you for the cycle". Seller Central keeps "3 years" of settlement history (unverified; the page is behind sign-in) [opinion] https://novadata.io/resources/blog/amazon-settlement-report-guide.
304
+ - **Intentwise.** V1→V2 column map; V2 `amount-type`/`amount-description` pairs (ItemFees/Commission, FBAPerUnitFulfillmentFee, FBAWeightBasedFee, GiftwrapChargeback, RefundCommission, ShippingChargeback, VariableClosingFee; ItemPrice/Principal, Shipping, GiftWrap, Goodwill, RestockingFee; Other-Transaction/Current Reserve Amount, Previous Reserve Amount Balance, Refund Reimbursal, Storage Fee; Promotion/Shipping; Shipment-Fees/FBATransportationFee), with Amazon's definitions copied. These are "illustrative, not an official list" [opinion] https://help.intentwise.com/amazon-settlement-report-v1-to-v2-mapping-guide.
305
+ - **Improvado** (connector notice, September 2026): "Amazon only lists settlement reports generated in roughly the last 90 days, so a new V2 report cannot be backfilled further back than that — older settlements are no longer retrievable from the API at all." V2 "is not a drop-in replacement"; "each amount is its own row" [opinion] https://improvado.io/product-updates/connectors/amazon-seller-central-settlement-report-sunset.
306
+ - **Seller Essentials** (2026). "Amazon rolled out Finance Workspace in new Seller Central on September 21, 2026". It has Manage Payout (each row: payout date, status, the 14-day period, "a Trace ID with the last digit of your bank account, the Settlement ID, the amount", standard or invoiced account), Manage Transaction, and Reports Hub. Statement View is under "Finance, then Manage payments". "generated reports only stay downloadable for 90 days". "Settlement reports follow payout timing. Date Range reports follow activity timing". "Since September 21, 2026, Express Payout is on by default for eligible US sellers" (not confirmed by an Amazon page read today; Amazon Pay's page still describes Express Payout as a switch from "the default Standard Payout setting") [opinion] https://selleressentials.com/amazon-finance-workspace/, citing "Amazon Seller Central Help, New Seller Central Finance Experience".
307
+ - **Developers on Amazon's models repo** (named by handle; not Amazon staff unless stated):
308
+ - #5353 (mystery4f, 2026-08-10). In V2, "For FBA fee transactions the `order-id` column is either empty or contains an **FBA shipment ID**", e.g. `transaction-type FBAFees`, `order-id FBA19CD9HGQ8`, `amount-type Inbound Defect Fee`, `amount-description Base fee`. For `other-transaction - Reversal` rows the same shipment ID sits in `shipment-id`. The reporter also saw identifier columns carrying values other than their names on Order rows. A commenter (BrunnoPigatto, association "NONE", writing as if for the SP-API team) replied that this is "a known characteristic of the settlement flat file format" and the docs "do not describe these per-transaction-type semantics". He said an internal documentation request was filed and recommended `listTransactions` (`ORDER_ID`) for order attribution, with the settlement file kept for payout-level reconciliation. https://github.com/amzn/selling-partner-api-models/issues/5353
309
+ - #5291 (2026-06-30). One settlement file is one seller account. `marketplace-name` is filled on order rows and empty on account-level rows "storage fees, subscription fee, service fees, reserve and previous-reserve adjustments, FBA reimbursements". The same transactions carry `marketplaceDetails` in `listTransactions`. gabrielbarretodev: "A `FINANCIAL_EVENT_GROUP_ID` can hold transactions still deferred … alongside released ones. If you sum everything to match the settlement total, the deferred rows make it 'not balance.' Reconcile *released* amounts against the settlement net". https://github.com/amzn/selling-partner-api-models/issues/5291
310
+ - #2139 (selling-partner-api-docs) is titled a "regression from MWS to SP-API (using FinancialEventGroupId and PostedBefore)" (title only, via search).
311
+ - **Seller forum reports.** Statement View disappeared in new Seller Central (2026-09-02, 298 views, 20 replies). Only .txt or .xml settlement downloads under Finance Reports (2026-09-24). "Amazon starts and ends pay periods on the same day … with transactions on multiple pay period reports (i.e., deferred and released), it's a nightmare" (2026-06-12). Sellers point out that 2024 deferred-reporting changes made printed transaction periods change after the fact (reply on the 2024-10-04 News post). Unexplained "Other" charges with a blank order id (replies to the 2025-08-26 staff post). A Payments dashboard delay incident: "Seller Payment Dashboard Updates delayed" (cardo_Amazon, 2024-12-21) [opinion, sellers; Amazon staff for the incident title].
312
+
313
+ **Chinese-language tools and media**
314
+ - **领星 Lingxing 结算中心** (help articles SettlementCenter / SettlementCenter1, read 2026-11-09). "接入亚马逊财务API接口" (connects Amazon's finance API). "提供与summary月度账单的对账功能" (reconciles against the monthly Summary statement). Its record fields:
315
+ - 结算开始/结束时间 = when the Amazon statement first Opens/Closes, "对应站点的账单时间" (in the site's statement time);
316
+ - 结算区间 is "一般是从注册时间开始往后计算14天" (usually 14 days counted from registration), and "如果用户提前在 … Statement View中点击请求付款(Request Payment),账单会提前关闭" (a payment request closes the statement early);
317
+ - `Settlement ID` "只有亚马逊提供settlement report才能获取到…在待结算状态为空" (exists only once Amazon issues the settlement report; empty while open);
318
+ - 追踪编号 "即ACH编号"; 银行尾号 (account tail).
319
+
320
+ Reconciliation status "部分对账:亚马逊账单跨月,需要分月进行对账" (a statement that crosses months is reconciled month by month). Formulas: "本期结算=收入+退款+支出; 应收金额=期初余额+本期结算+信用卡扣款+预留退回+本期预留" (settlement = income + refunds + expenses; receivable = opening balance + settlement + card charge + reserve released + reserve held). Transfer currency can differ from receivable currency "原因是用户绑定了站点币种不一致的收款账户,亚马逊会根据当前的汇率牌价转换" (the bank account bound is in another currency, converted at the current rate). Card display converts "取账单开始时间对应月的汇率" (at the rate of the statement's start month). Transaction types include "信用卡扣款:当用户应收金额不足以支付账单费用" (card charge when the receivable cannot cover the statement) and "Liquidation Adjustment". Lingxing claims the reserve is "依据店铺最近28天的销售额的5%" (5% of the last 28 days' sales) and also says "目前无法预判预留金额" (cannot be predicted) [opinion]. The 5% figure traces to an older Amazon payments FAQ as Chinese sellers reproduce it. AMZ123 (大姐夫站外推广, 2022-01-18) quotes it as "亚马逊预留政策": new sellers' whole balance; established sellers the higher of the past 7 days' sales or 5% of the past 28 days. No current Amazon page read carries it, and it predates DD+7 [opinion, second-hand reproduction; unverified against Amazon]. 36kr (Lingxing's article) lists the manual monthly routine: export Transaction (opening/closing balance, period debits), export Settlement (receipts, period credits), match bank lines, match shipped vs settled orders (发出商品, goods shipped not settled) [opinion] https://www.36kr.com/p/2043364439314435.
321
+ - **积加 Gerpgo** 销售回款分析 (2022): payouts by country, site, settlement period and month, with currency switching. The pain points it names: "银行流水中的收款记录不会显示回款的店铺和站点信息" (bank lines do not show store or site), and expected vs actual payout differs by currency and FX [opinion] https://news.pedaily.cn/20220317/31837.shtml. Gerpgo's own site was unreachable in the survey.
322
+ - **wimoor** (open-source ERP) gives Chinese/English glossaries of Summary lines. "Transfers to bank account", "Failed transfers to bank account:亚马逊未能在结算周期结束时转账至卖家银行账户的金额,比如卖家在亚马逊转账前更换了收款账号 … 会在下个结算日转账此金额" (a failed transfer, e.g. after changing the deposit account, is paid on the next settlement date). 当前预留金额 / 上一期预留金 [opinion] https://wimoor.com/rule-c-535.html.
323
+ - **赛狐 Sellfox** (blog, read 2026-11-09; vendor marketing, so each line is the vendor's claim):
324
+ - "亚马逊DD+7锁死现金流?…" (2026-06-24, https://www.sellfox.com/blog/article/yamaxun-yuliujin-sellfox). It separates 交易级预留金 (transaction-level, shown as deferred) from 账户级预留金 (account-level, risk-driven), which "不会自动迁移成DD+7的交易级延迟交易" (does not migrate into DD+7 deferred). Its 延迟交易 feature splits each store's month into "当月结算金额" (settled this month), "前期延迟当月结算金额" (deferred earlier, settled this month) and "当月延迟后期结算金额" (deferred this month, settled later), "可用于资金流预测和月末对账" (for cash forecasting and month-end reconciliation). It separates deferred from settlement data "通过结算状态和关联ID" (by settlement status and related IDs).
325
+ - **Conflict with Amazon:** the same article says "手动DoD不会截断并重置当前结算周期" (a manual DoD does not truncate or reset the current settlement period). Amazon's Chinese explainer (2026-06-05, §Amazon C) says each DoD truncates the period and restarts the 14 days. Amazon's page is the one to cite.
326
+ - "亚马逊24小时到账新政落地!" (2026-09-30, https://www.sellfox.com/blog/content/36). It claims that from 2026-09-21 Amazon US turns Express Payout on by default for eligible sellers, which matches Seller Essentials (no Amazon page read confirms it). It also claims that from August 2026 advertising charges come out of the store balance first, which matches Amazon's ads-billing change for contacted advertisers (dated changes). Its tools: 结算中心 (settlement reports by store and period, settled vs unsettled, transfer rankings); 应收报表 (receivables "并转换时区", with time zones converted, counted "按'已发货'或'已结算'", by shipped or by settled, including shipped-not-settled accruals); 延迟交易 (1–3 month payout forecast).
327
+ - **智赢ERP Zying** 财务报告使用指南 (https://www.zying.net/helpdet-729.html, read 2026-11-09): settlements grouped by store and period with status 未结 / 已结 / 失败 (open / paid / failed). Columns are 期初余额 (opening balance), 扣留 (reserve held), 回款 (paid out, original currency) and 换算¥ (converted to CNY at the period's rate). Transaction-type filters: 订单付款, 服务费, 广告费, FBA入库, FBA仓储, 清算, 清仓盘点, 退货标签, 退款, AZ索赔退款, 信用卡拒付, 上期余额, 预留金额, 付款至亚马逊. "交易明细里的'小计'累加起来即对应回款分组里的'回款'金额" (the line subtotals add up to the group's payout) [opinion, vendor].
328
+ - **雨果网 cifnews** (contributor columns, "以上内容属作者个人观点"):
329
+ - 闯盟跨境, "亚马逊 2026 最新回款政策全解读" (2026-04-23, https://www.cifnews.com/article/185409). DD+7 "生效时间:2026 年 3 月 12 日 全球所有站点统一执行" (effective 2026-03-12 in every store). The old statement "只显示已结算(Released)订单", the new "显示所有出单(Posted),包含已释放 + 延迟两部分". The author's reconciliation identity: "当月总销售额 = Released(已到账)+ Deferred(延迟/预留)", "按订单发生月统计". Amazon's words are "posted date", not order month (§Amazon C) [opinion].
330
+ - 跨境电商张志强, "亚马逊实行'DD+7'的回款模式!且影响报税!" (2025-11-19, https://www.cifnews.com/article/180739). It quotes Amazon's example "1号卖的货3号妥投,得等到11号才能支取" (sold on the 1st, delivered on the 3rd, available on the 11th), the same as the English email. It says the policy had been trialled since the previous October on North American accounts ("送达日期政策"). It also claims Chinese tax is reported by order date, not cash date (outside this file; tax seat) [opinion].
331
+ - **AMZ123** (大姐夫站外推广, "关于亚马逊回款和收款你真的真的真的清楚吗?", 2022-01-18, https://www.amz123.com/t/K0djSBnw). A Chinese reproduction of Amazon's old payments FAQ [opinion, second-hand]:
332
+ - a new bank account carries "3 天安全保留期" (a 3-day security hold) before transfers;
333
+ - at a negative balance at period end Amazon charges the card and "将继续以每 24 小时一次的频率向您的信用卡扣费,直到您卖家账户中的余额偿清" (keeps charging every 24 hours until the balance is repaid);
334
+ - account-level reserve reasons include "当地法规要求我们预扣您的所得税(因商城而异)" (local rules requiring income-tax withholding, by marketplace);
335
+ - an "其他" ("Other") line of $39.99 is the monthly subscription, and several of them are carry-forwards from periods whose sales could not cover it;
336
+ - the author's own shortcut: 回款率 = total payout ÷ total sales from the Date Range summary, as a rough margin screen.
337
+ - **积加 Gerpgo** (投资界 2022, as above): syncs payment-report data daily around 03:00 [opinion, vendor marketing, 2022].
338
+ - **金蝶 Kingdee / 用友 Yonyou**: still no first-party page found on an Amazon settlement connector. Searches return Zoho Books China marketing and a 36kr Lingxing article only. A Yonyou claim (payment instructions via WorldFirst synced into Yonyou vouchers) is marketing without a document [unverified].
339
+ - **知无不言 (wearesellers.com)**: its threads are not indexed by the search tools used. No post could be cited.
340
+ - **Amazon China's knowledge pages** (globalselling.amazon.com/zhishi) carry the 14-day cycle and fees only. The DD+7 explainer above is the one Amazon-authored Chinese reconciliation page found.
341
+
342
+ **Gap fill (2026-11-10): money outside the settlement, multi-marketplace layout, completeness, history**
343
+ - **ConnectBooks** (help article "Advertising per product in QuickBooks"): "Ad spend taken out of the settlement is imported as 1 total amount with "Amazon fees" as the class." "ConnectBooks doesn't record ad charges paid by credit card, because most sellers use different cards." "We recommend that you also record your credit card spend for Amazon Sponsored Products with the same "Amazon fees" class." [opinion] https://help.connectbooks.com/en/articles/5084147-advertising-per-product-in-quickbooks, read 2026-11-10. ConnectBooks also says Amazon shares AWD fees only "as a lump sum through its API" (search snippet of help article 11459561) [opinion].
344
+ - **A2X**, "Reconciling Amazon seller fee invoices with A2X settlements": "Amazon Seller Central issues invoices for seller fees such as Product Ads". "Any fees that are deducted from your seller account will appear in your A2X settlements." There is "a time lag of up to four weeks between when the order transaction was completed" and the settlement, and the invoice uses the completion date. "You may also receive credit notes for refunded fees or retro-charges." "Each fee that appears in an invoice will appear in a settlement with a corresponding marketplace" [opinion] https://support.a2xaccounting.com/en/articles/7950961-reconciling-amazon-seller-fee-invoices-with-a2x-settlements, read 2026-11-10.
345
+ - **A2X on regions** ("Amazon regions and marketplaces", 2025-08-27): "A separate A2X for Amazon account is required for each region in which you sell." "if any of your marketplaces within a region have different Amazon Seller IDs, … a separate A2X account will be required for each Seller ID", with Amazon.co.jp and Amazon.sg as the example. Its Europe region lists UK, BE, FR, DE, IE, IT, NL, PL, ES and SE. AE and SA form a separate Middle East region, and AU, IN, JP and SG an Asia-Pacific one. The SP-API puts IN, AE, SA, EG, TR and ZA on the EU endpoint (§Amazon H) [opinion] https://support.a2xaccounting.com/en/articles/1132528-amazon-regions-and-marketplaces. On currency (2024-04-29): "settlements come into A2X in the currency of those marketplaces"; "The conversion to your home currency happens in your accounting software." [opinion] https://support.a2xaccounting.com/faqs/how-does-a2x-convert-a-foreign-currency-to-my-home-currency-so-i-can-reconcile-deposits.
346
+ - **A2X on archived settlements**: "Amazon archives older settlement reports after a certain period, which prevents A2X from importing them via the API." The fix A2X gives is Finance > Finance Reports, "Understand Payout" tab, selecting Standard and Invoiced Orders in the Account Type filter, then "Click the Request Report button next to the settlement". Once "you should see a Download flat file V2 button", "A2X can access the data via the API." [opinion] https://support.a2xaccounting.com/faqs/why-are-some-of-my-settlement-files-missing. On first connection "approximately 10 settlements will come into your settlements list automatically" (2023-08-01) [opinion] …/1132581-how-to-request-settlement-history-inside-a2x.
347
+ - **Link My Books** ("Accessing Historical Data", updated 2026-10-05): "We only import 3 months worth of data from your sales channel when you first connect it". For Amazon, "Max History Available" is "24 months", and "There are limits on how far back each sales channel's API allows us to retrieve data." It tells Amazon sellers to request each settlement in Seller Central first, because "archived reports won't come through" [opinion] https://help.linkmybooks.com/en/articles/7923978-how-do-i-get-older-data.
348
+ - **ConnectBooks** history: "Historical data can only be retrieved for up to two years." [opinion] https://help.connectbooks.com/en/articles/9533258-how-far-back-can-connectbooks-import-amazon-settlements.
349
+ - **领星 Lingxing 发货与结算差异报告** (ShipSettlVarReport, read 2026-11-10) [opinion, vendor]:
350
+ - Purpose: "帮助财务或老板追溯每一笔订单从下单到发货再到结算最后回款的时间节点" (trace each order from order to shipment to settlement to payout). Data sources: "亚马逊结算中心、成本中心、亚马逊货件配送报告" (settlement centre, cost centre, Amazon's shipment report).
351
+ - The accounting it assumes: on shipment, goods move from 库存商品 (inventory) to 发出商品 (goods shipped); on settlement, revenue is recognised and cost carried from 发出商品 to 主营业务成本 (cost of sales). The 发出商品 balance is "已经发货但是尚未结算的订单成本" (the cost of orders shipped but not settled). Skipping 发出商品 "会导致每个月结存的数量和亚马逊库存分类账的结存数量对不上" (makes month-end units disagree with Amazon's inventory ledger).
352
+ - The vendor's figure: "99%以上的数据,都是在发货之后三个月内会结算。也会有极少的情况,会先结算后发货,比如先试后买的场景" (over 99% settles within three months of shipment; rarely settlement comes first, e.g. try-before-you-buy).
353
+ - Buckets: 已发货未结算 (shipped, not settled), 已结算未转账 (settled, not transferred) and 未发货已结算 (settled, no shipment). The last excludes the latest three days because "亚马逊配送报告会有3天数据延迟" (Amazon's shipment report runs three days late). The roll-forward is 期末已发货未结算 = 期初 + 本期发货 − 本期发货已结算 − 前期发货本期结算 (closing shipped-not-settled = opening + shipped − shipped-and-settled − earlier-shipped-settled-now).
354
+ - 回款率 (payout rate) is counted in units, "因为亚马逊的回款剔除了各种费用…用金额计算没有实际意义" (payouts are net of fees, so amounts are meaningless here). History is counted only from 2023 ("只统计23年后"), and a missing month of finance data shows as shipped-not-settled until "补拉历史数据" (a re-pull of history).
355
+ - **Seller threads on completeness**: "any orders where the customer cancels, these still show up in Sales reports, even though the orders did not complete" (UK forum, about 2023, "Anyone ever reconciled their Amazon transaction reports vs what they've actually shipped?") [opinion] https://sellercentral.amazon.co.uk/seller-forums/discussions/t/c9392c0e-b985-465e-86e1-8121a53b70ee.
356
+ - **AMZ123 answers on 北美联合账户** say a unified NA seller pays only the US monthly fee and not CA or MX [opinion, AMZ123 ask pages via search]. **Conflict:** Amazon's 2021 rule (§Amazon H) divides one capped fee across the Americas stores with active listings, each in its own currency. Amazon's page is the one to cite.
357
+
358
+ **What practitioners say breaks reconciliation** (collected; each is named above):
359
+ 1. the time zone (UTC settlement vs local reports);
360
+ 2. the V1→V2 switch (row shape, locale-formatted amounts);
361
+ 3. deferred lines (missing from settlement until released; split across payouts; 2024 and 2026 report changes; 1099-K mismatch);
362
+ 4. reserve lines (current vs previous, asset not expense, per marketplace);
363
+ 5. negative settlements and card charges (pending balance, "Successful Charge");
364
+ 6. account-level rows with no order-id, sku or marketplace (storage, subscription, reimbursements);
365
+ 7. `FBA Inventory Reimbursement` and other `Adjustment` rows with no order;
366
+ 8. chargebacks and A-to-z reversals posting cycles later;
367
+ 9. a settlement crossing month-end;
368
+ 10. currency of deposit ≠ marketplace currency;
369
+ 11. failed transfers re-sent next cycle;
370
+ 12. the 90-day API window;
371
+ 13. settlement periods shortened by a Disburse on Demand (Amazon China, 2026-06-05; Sellfox says the opposite);
372
+ 14. advertising charges moved into the settlement for advertisers switched off card billing (from 2026-08-01);
373
+ 15. DD+7 reserves held in the account-level reserve before migration not moving into deferred transactions (Amazon China; Sellfox).
374
+ 16. charges billed outside the settlement: ads on card or invoice, Transparency invoices, AGL paid in CNY by wire, Amazon Freight and Amazon Shipping invoices, Lending by Direct Debit (gap fill 2026-11-10);
375
+ 17. several stores and two account types under one login, account-level rows with no store, and a subscription split across stores;
376
+ 18. shipped-not-settled and settled-not-shipped orders at month-end (Lingxing);
377
+ 19. settlements archived in Seller Central, and report documents gone from the API after 90 days.
378
+
379
+ ## Published research
380
+
381
+ None found. No peer-reviewed or institutional study of marketplace settlement reconciliation surfaced in this session's searches. The ecosystem's knowledge is vendor documentation and Amazon's own posts.
382
+
383
+ ## Stable enough for a skill
384
+
385
+ 1. Settlement reports are made by Amazon on the payout cycle. They are found with `getReports` and never created. Only `…_FLAT_FILE_V2` remains after 2026-11-11.
386
+ 2. V2 is long-format: one amount per row, classified by `amount-type` + `amount-description`. Amazon publishes no closed list of either.
387
+ 3. V2 amounts are in the marketplace's locale number format. `posted-date-time` is UTC.
388
+ 4. Through the API, a settlement report is findable for about 90 days. Older ones are only in Seller Central.
389
+ 5. The settlement file counts released money in a payout period. It equals the deposit, plus or minus reserve movement and charges. It is not the month's sales.
390
+ 6. Deferred transactions are absent from settlement files and from v0 event lists until released. They are present in `listTransactions` (`DEFERRED`).
391
+ 7. Date Range reports run midnight-to-midnight local time on posted date. Since 2026 they include deferred and released (periods from 2025-01-01). No SP-API report type produces them.
392
+ 8. The Deferred Transaction report is retrievable by API only after the seller requests it in Seller Central.
393
+ 9. `listSummary` gives net proceeds and breakdowns for a date range (local time) or a settlement id. `listBalances` gives AVAILABLE / DEFERRED / RESERVED / ACCOUNT_LEVEL_RESERVE / TOTAL, now or as of a date.
394
+ 10. A financial event group is a settlement period. Closed = paid or charged (`OriginalTotal`, `ConvertedTotal`, `FundTransferDate`, `TraceId`, `AccountTail`). Open = current balance.
395
+ 11. Account-level rows carry no order-id, sku or marketplace. Some fee rows carry an FBA shipment id in `order-id` (practitioner-observed).
396
+ 12. Remittance and Invoices (2026) are vendor APIs.
397
+ 13. Accounting choices sellers make (state, don't pick): cash vs accrual; settlement-as-journal vs per-order; gross vs net; clearing account; reserve as asset; deferral accrual; month-split of a settlement; tax as pass-through.
398
+ 14. Several Amazon charges never pass through a settlement: advertising billed to a card or by invoice; Lending repaid by Direct Debit (UK); AGL paid by wire in CNY; Amazon Freight and Amazon Shipping invoices; Transparency invoices (per a seller and Amazon staff). Each has its own statement outside Seller Central's payments pages.
399
+ 15. `ProductAdsPaymentEvent.invoiceId` ties an ad line in the settlement to its Ads invoice, and `AdjustmentItem.TransactionNumber` can carry an Amazon Shipping invoice number.
400
+ 16. The NA, EU and FE regions each have their own SP-API endpoint, and every selling account, merged or not, is authorized separately with its own refresh token. Private applications have a self-authorization limit.
401
+ 17. Moved to What cx must read at run time (correction 1, 2026-11-10): how a merged account's subscription is split and charged by store is a fee and currency rule that varies by store.
402
+ 18. Payouts, balances and summaries are kept per store and per account type (Standard Orders, Invoiced Orders).
403
+ 19. The completeness faces are the Amazon Fulfilled Shipments report (Pricing reaches it), the All Orders reports, the FBA Returns report, `searchOrders` and `listTransactions` by order. Seller-fulfilled returns need a role the seller has not ticked.
404
+ 20. Each face has its own horizon (§Amazon J). After it, only the seller's own copy or a longer Seller Central document remains.
405
+
406
+ ## What cx must read at run time
407
+
408
+ | What moves | Where cx reads it |
409
+ |---|---|
410
+ | Which settlements exist, their ids and document ids | `getReports` `reportTypes=GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2` (`createdSince`/`createdUntil`, page via `nextToken` alone) |
411
+ | A settlement's lines and its total, start/end, deposit date, currency | `getReportDocument` → the TSV (header row; the totals row; locale-formatted `amount`) |
412
+ | Payout amount, status, trace id, account tail, conversion | v0 `listFinancialEventGroups` (`ProcessingStatus`, `FundTransferStatus`, `OriginalTotal`, `ConvertedTotal`, `FundTransferDate`, `TraceId`, `AccountTail`, `BeginningBalance`); Transfers `listPayouts` where it answers |
413
+ | Next expected payout | Transfers `listExpectedPayouts` (`scheduledDate`, `status` incl. `AT_RISK`) |
414
+ | The transactions that make up a payout | `listTransactions` `relatedIdentifierName=FINANCIAL_EVENT_GROUP_ID` (+ `transactionStatus`) |
415
+ | Every transaction in a month, deferred or not | `listTransactions` `postedAfter`/`postedBefore` (≤180-day windows, UTC timestamps) |
416
+ | A settlement or a day/month summary in Amazon's categories | `listSummary` (`SETTLEMENT_ID` or `periodStart`/`periodEnd`, local time) |
417
+ | Balances at a month-end | `listBalances` `asOfDate` |
418
+ | Deferred items at a point in time | `GET_DATE_RANGE_FINANCIAL_HOLDS_DATA` after the seller requests it in Seller Central; else `listTransactions` `transactionStatus=DEFERRED` |
419
+ | Account's reserve policy, cycle length, deposit currency | not exposed as a setting by any operation read; inferred from groups' start/end and `ConvertedTotal` currency [seat] |
420
+ | Removal dates and new enum values | SP-API Deprecation Schedule; changelog / release notes |
421
+ | Which stores and account types the account has, and their balances | `listBalances` (by `marketplaceIds`, `accountType`); `listPayouts` grouping; `sellingPartnerMetadata` on transactions |
422
+ | Which regions and accounts are authorized | the authorizations the seller made (one refresh token per account); the regional endpoint each answers on |
423
+ | Ad lines inside the settlement and their invoice | v0 `ProductAdsPaymentEvent` (`invoiceId`, `baseValue`, `taxValue`); `listTransactions` breakdowns |
424
+ | Charges outside the settlement | no SP-API face read carries them: the Amazon Ads console Billing page, Shipper Central, the Amazon Freight portal, Transparency invoices, the bank statement (Lending Direct Debit), AGL wire payments |
425
+ | Shipped units in a month | `GET_AMAZON_FULFILLED_SHIPMENTS_DATA_GENERAL` (≤ 1 month per report, request cap per 8 h); FBM via the All Orders reports or `searchOrders` |
426
+ | Posted money per order | `listTransactions` `relatedIdentifierName=ORDER_ID`; settlement rows by `order-id` |
427
+ | FBA customer returns | `GET_FBA_FULFILLMENT_CUSTOMER_RETURNS_DATA` |
428
+ | A settlement older than about 90 days | Seller Central "Request Report", after which practitioners say `getReports` finds it (open question 18) |
429
+ | How a merged account's subscription is split and charged by store (as read: since 2021-08-01, split across the Americas stores with active listings, each in its own currency, and charged in one European country for European stores) | the subscription rows of each store's settlement V2 and `listTransactions` (`marketplaceDetails`, `totalAmount.currencyCode`); the rule on Changes to Professional Selling Plan subscription fees for global sellers (https://sellercentral-europe.amazon.com/seller-forums/discussions/t/a8ff250bb262db2136bedc7c9bc8d5d8) |
430
+
431
+ ## What only Seller Central shows
432
+
433
+ - **Date Range Transaction and Summary reports** (CSV, PDF). No SP-API type exists. The closest API equivalents are `listTransactions` (transactions) and `listSummary` (summary) [official pages above; the equivalence is the reading of the GitHub answer in discussion #4015 (stefnats, 2026-03-18), opinion].
434
+ - **Requesting the Deferred Transaction report.** The API only retrieves it afterwards.
435
+ - **Settlement history beyond about 90 days** (All statements / Reports Hub "Understand payout"). The API cannot list them.
436
+ - **Statement view as a page** (now under Finance → Manage payments in new Seller Central). `listSummary` with `SETTLEMENT_ID` returns the same categories as data.
437
+ - **Request Payment / disburse-on-demand** outside the EU8 (`initiatePayout` is EU-only), changing deposit method or settlement cycle, the Currency conversion (ACCS) settings, and the 1099-K / tax document library (tax roles are a sibling's).
438
+ - **The reserve reason** ("View details" on the unavailable/reserved balance). No operation returns why a reserve is held [seat: none of the models carries a reason field for `ACCOUNT_LEVEL_RESERVE`].
439
+ - **Charges billed outside Seller Central's payments pages** (gap fill 2026-11-10): Ads invoices and billing history (Amazon Ads console; the Ads API is another seat's), Shipper Central invoices (Amazon Shipping; AGL paid in CNY), the Amazon Freight portal, Transparency invoices, and Lending statements. No SP-API operation read returns them.
440
+ - **Amazon's VAT invoices for its fees** (Tax Document Library), typically monthly per Amazon staff.
441
+ - **Re-requesting an archived settlement** ("Request Report", Finance > Finance Reports > Understand Payout, per A2X). The API can find it only afterwards (practitioners).
442
+ - **Global Snapshot**, Seller Central's cross-store view. No Amazon page about it was read, and no API reproduces it.
443
+
444
+ ## Facts for human readers only
445
+
446
+ - Survey and vendors put a typical settlement at 14 days (sometimes 7 for large accounts, per Nova). The bank transfer takes up to 5 business days (Amazon, 2025-07-30). Express Payout is within 24 hours for eligible US sellers (Amazon); the claim that it is on by default from 2026-09-21 is a practitioner's.
447
+ - Per A2X (vendor, 2025-08-18), 20–25% of revenue can slip into the next month under DD+7.
448
+ - Per Lingxing (vendor), the reserve is 5% of the last 28 days' sales. Amazon publishes no figure.
449
+ - Practitioners put typical account-level reserve periods at 14–90 days (A2X, Synder, beancount).
450
+ - Per Nova (vendor), account-level fee rows dropped by filtering on SKU are worth 1–3 margin points.
451
+ - Subscription across merged accounts (News_Amazon, effective 2021-08-01): total "limited to no more than the equivalent USD 39.99 per month (exclusive of tax, except in Mexico and Brazil, and any foreign transaction fees charged by your bank or credit issuer)". MX changed its subscription on 2026-02-17 (selling-fees).
452
+ - Amazon Ads Pay by Invoice: invoice at month-end, "payment is due 30 days later" (Amazon Ads, 2026-04-14). The consolidated invoice statement covers the last 90 days (2024-01-12).
453
+ - Amazon Fulfilled Shipments report: at most 12 requests per 8 hours per selling account; 1–3 hours' lag, rarely 24 (FBA Reports, 2026-10-13).
454
+ - Authorizations: private apps allow at most 10 self-authorizations (Authorization Limits, 2026-09-09). Authorizations not renewed in more than 365 days and with no call in that time are deactivated (FAQ, 2026-10-29).
455
+ - Lingxing (vendor): over 99% of shipped orders settle within three months of shipment, and its shipment-report feed runs about three days late.
456
+ - Connector history limits (vendors): Link My Books imports 3 months on connection, up to 24 months for Amazon (2026-10-05); ConnectBooks up to two years; A2X about 10 settlements automatically, then on request.
457
+ - Date Range reports: up to 365 days per report, back to 2012 (Amazon staff, 2024-10-31).
458
+
459
+ ## Pages read
460
+
461
+ | Title | URL | Date read | Tag |
462
+ |---|---|---|---|
463
+ | Settlement Reports (updatedAt 2026-10-14) | https://developer-docs.amazon/sp-api/docs/report-type-values-settlement.md | 2026-11-09 | official |
464
+ | Deprecation of two payment settlement report types | https://developer-docs.amazon/sp-api/changelog/update-deprecation-of-two-payment-settlement-report-types.md | 2026-11-09 | official |
465
+ | SP-API Deprecation Schedule (updatedAt 2026-09-09) | https://developer-docs.amazon/sp-api/docs/sp-api-deprecations.md | 2026-11-09 | official |
466
+ | Report Type Values (updatedAt 2026-09-10) | https://developer-docs.amazon/sp-api/docs/report-type-values.md | 2026-11-09 | official |
467
+ | Payment Reports (Deferred Transaction Report) | https://developer-docs.amazon/sp-api/docs/report-type-values-payment.md | 2026-11-09 | official |
468
+ | New: Deferred Transaction Report type for the Reports API | https://developer-docs.amazon/sp-api/changelog/new-deferred-transaction-report-type-for-the-reports-api.md | 2026-11-09 | official |
469
+ | Finances API (updatedAt 2026-09-09) | https://developer-docs.amazon/sp-api/docs/finances-api.md | 2026-11-09 | official |
470
+ | Get the latest transactions (updatedAt 2026-09-24) | https://developer-docs.amazon/sp-api/docs/get-latest-transactions.md | 2026-11-09 | official |
471
+ | Determine payment transactions | https://developer-docs.amazon/sp-api/docs/determine-payment-transactions.md | 2026-11-09 | official |
472
+ | Retrieve the amount and status of a payment | https://developer-docs.amazon/sp-api/docs/retrieve-amount-status-payment.md | 2026-11-09 | official |
473
+ | Retrieve your current balance | https://developer-docs.amazon/sp-api/docs/retrieve-your-current-balance.md | 2026-11-09 | official |
474
+ | Retrieve the financial events that make up a financial event group | https://developer-docs.amazon/sp-api/docs/retrieve-financial-events-in-group.md | 2026-11-09 | official |
475
+ | Retrieve a financial summary | https://developer-docs.amazon/sp-api/docs/retrieve-financial-summary.md | 2026-11-09 | official |
476
+ | listTransactions / listSummary / listBalances / listFinancialEventGroups / listPayouts references | https://developer-docs.amazon/sp-api/reference/{listtransactions,listsummary,listbalances,listfinancialeventgroups,listpayouts}.md | 2026-11-09 | official |
477
+ | Transfers API; Retrieve payouts; Retrieve expected payouts | https://developer-docs.amazon/sp-api/docs/transfers-api.md; …/retrieve-payouts.md; …/retrieve-expected-payouts.md | 2026-11-09 | official |
478
+ | Invoices API (v2026-06-25); Retrieve invoice headers | https://developer-docs.amazon/sp-api/docs/invoice-api.md; …/retrieve-invoice-headers.md | 2026-11-09 | official |
479
+ | Finance Remittance API; Reconcile payments to invoices | https://developer-docs.amazon/sp-api/docs/finance-remittance-api.md; …/reconcile-remittance-payments.md | 2026-11-09 | official |
480
+ | SP-API changelog RSS; "…New Enum Value for Finances API" (2026-10-21) | https://developer-docs.amazon/sp-api/changelog.rss; …/changelog/sp-api-updates-new-shipment-notification-…-finances-api.md | 2026-11-09 | official |
481
+ | SP-API site index | https://developer-docs.amazon/sp-api/llms.txt | 2026-11-09 | official |
482
+ | Local: Role Mappings (2026-10-28), Role Mappings for types, release notes, deprecations | saved copies of https://developer-docs.amazon/sp-api/docs/role-mappings.md, its types page, https://developer-docs.amazon/sp-api/docs/sp-api-release-notes.md and https://developer-docs.amazon/sp-api/docs/sp-api-deprecations.md | 2026-11-09 | official, command-verified |
483
+ | Local: financesV0.json, finances_2024-06-19.json, transfers_2024-06-01.json, financesInvoices_2026-06-25.json, financeRemittance-2026-03-17.json, reports_2021-06-30.json | models clone db2936aa | 2026-11-09 | command-verified |
484
+ | Local: survey `04-job-money.md`; listing playbook `research/method/report-lifecycle.md`; door.md | as named | 2026-11-09 | reused |
485
+ | Updated payment reports simplify accrual reporting… (News_Amazon, US, 2026-03-18) | https://sellercentral.amazon.com/seller-forums/discussions/t/0046a66f-915a-4aa1-b343-d8f47ffcc4aa | 2026-11-09 | official |
486
+ | Same, duplicate thread | https://sellercentral.amazon.com/seller-forums/discussions/t/25d62b41-65fe-40dc-9a87-52d40c49eda3 | 2026-11-09 | official |
487
+ | Updated payment reports… (News_Amazon, EU, 2026-03-31) | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/8fe604f7-ecb8-4930-902e-a700f731ee66 | 2026-11-09 | official |
488
+ | View your reserved payments in the new Deferred Transactions report (News_Amazon, 2024-10-04) | https://sellercentral.amazon.co.uk/seller-forums/discussions/t/5eb04dd2-c1e7-47bb-9bf4-57049bc7d1fe | 2026-11-09 | official |
489
+ | Where's My Money? (Danny_Amazon, 2025-08-26) | https://sellercentral.amazon.com/seller-forums/discussions/t/718bf5b9-5500-4e85-942b-7a0a0357354e | 2026-11-09 | official (staff) |
490
+ | Quick Tip: Date Range reports (Jessica_Amazon_, 2024-04-17) | https://sellercentral.amazon.com/seller-forums/discussions/t/a53226d8-554a-427d-a0d9-31c52420377d | 2026-11-09 | official (staff) |
491
+ | DD+7 March 12, 2026; Your account will be migrated to DD+7 (sellers quoting Amazon's email, 2025-09-29) | …/t/cd0dfc4d-fbc5-4ded-a0b1-4c7ed989c107; …/t/afacf90a-3e68-4d8d-87aa-8e66d3c24500 | 2026-11-09 | official text, seller-posted |
492
+ | Seller Payment Dashboard Updates delayed (cardo_Amazon, 2024-12-21) | https://sellercentral.amazon.com/seller-forums/discussions/t/54f5e8d6-607e-4016-a224-a4357baa0cfb | 2026-11-09 | official (title only) |
493
+ | Seller threads: Statement View went away (2026-09-02); no .csv in new Seller Central (2026-09-24); Reports to Reconcile Payments? (2026-06-12); DD+7 Debacle (2026-03-29); Payment Summary Way Off (2024-11-08); Monthly Summary Reports (2024-10-04); Deferred roll-over 31 Dec 2025 (2026-04-27); amount-description in V2 (2024-11-11) | sellercentral(.amazon.com/-europe/.co.uk) …/t/929a0bef…, 4165e9d2…, 3ff0915a…, c3338073…, f737d545…, 1840070e…, 4206577e…, 328bfeed… | 2026-11-09 | opinion (titles/OPs; replies are JS-loaded) |
494
+ | Payment Date Range Transaction and Summary reports (help 201824360) | https://sellercentral.amazon.com/gp/help/external/201824360 (+ .co.uk, -europe, .in, .com.au, .ca) | 2026-11-09 | unreachable (JS shell) |
495
+ | GitHub selling-partner-api-models #4830, #5291, #5353; discussion #4015; selling-partner-api-docs #967 | https://github.com/amzn/selling-partner-api-models/issues/4830 etc. | 2026-11-09 | official reply (#4830) / opinion |
496
+ | A2X: reserve balances; DD+7 adjustments; split settlement (959804, 1984021, snippets) | https://www.a2xaccounting.com/ecommerce-accounting-hub/amazon-reserve-balances; …/amazon-dd-7-deferred-transactions-…; https://support.a2xaccounting.com/en/articles/959804-… | 2026-11-09 | opinion |
497
+ | Bookkeep: Date Range Summary Report update | https://www.bookkeep.com/docs/apps/amazon/amazon-date-range-summary-report-update-released-deferred-transactions | 2026-11-09 | opinion |
498
+ | Finaloop: Amazon deferred transactions | https://help.finaloop.com/en/articles/10499774-amazon-deferred-transactions-new-policy-update-implications | 2026-11-09 | opinion |
499
+ | Link My Books: account level reserve (2026-07-14) | https://linkmybooks.com/blog/amazon-account-level-reserve-explained-what-it-is-and-how-to-handle-it | 2026-11-09 | opinion |
500
+ | Synder: account-level reserves | https://synder.com/help/per-transaction-sync-synchronizing-amazon-account-level-reserves/ | 2026-11-09 | opinion |
501
+ | beancount.io: reserve holds (2026-08-17) | https://beancount.io/blog/2026/08/17/amazon-fba-reserve-holds-marketplace-reserves-asset-accounting-guide | 2026-11-09 | opinion |
502
+ | Webgility: account-level reserve | https://www.webgility.com/blog/account-level-reserve-amazon | 2026-11-09 | opinion |
503
+ | Nova: settlement report guide | https://novadata.io/resources/blog/amazon-settlement-report-guide | 2026-11-09 | opinion |
504
+ | Intentwise: V1→V2 mapping guide | https://help.intentwise.com/amazon-settlement-report-v1-to-v2-mapping-guide | 2026-11-09 | opinion |
505
+ | Improvado: settlement report sunset (Sept 2026) | https://improvado.io/product-updates/connectors/amazon-seller-central-settlement-report-sunset | 2026-11-09 | opinion |
506
+ | Seller Essentials: Finance Workspace | https://selleressentials.com/amazon-finance-workspace/ | 2026-11-09 | opinion |
507
+ | Amazon Pay Express Payout (snippet) | https://pay.amazon.com/business/express-payout | 2026-11-09 | official (Amazon Pay; snippet) |
508
+ | 领星 亚马逊结算中心功能介绍 (two versions) | https://www.lingxing.com/help/article/SettlementCenter; …/SettlementCenter1 | 2026-11-09 | opinion (vendor) |
509
+ | 36氪: 领星 回款 | https://www.36kr.com/p/2043364439314435 | 2026-11-09 | opinion |
510
+ | 投资界: 积加 销售回款分析 (2022) | https://news.pedaily.cn/20220317/31837.shtml | 2026-11-09 | opinion |
511
+ | wimoor 亚马逊财务项中文解释 | https://wimoor.com/rule-c-535.html | 2026-11-09 | opinion |
512
+ | gorillaroi settlement page | https://www.gorillaroi.com/amazon-seller-central-reports/settlement-report | 2026-11-09 | unreachable (404) |
513
+ | 详解|亚马逊DD+7预留金政策:底层逻辑、新旧变化和实操建议 (Amazon China, 2026-06-05) | https://globalselling.amazon.com/news/news-notices-260605 | 2026-11-09 (verifier) | official |
514
+ | 亚马逊 2026 最新回款政策全解读 (闯盟跨境, 2026-04-23) | https://www.cifnews.com/article/185409 | 2026-11-09 (verifier) | opinion |
515
+ | 亚马逊实行"DD+7"的回款模式!且影响报税! (跨境电商张志强, 2025-11-19) | https://www.cifnews.com/article/180739 | 2026-11-09 (verifier) | opinion |
516
+ | 赛狐: 亚马逊DD+7锁死现金流? (2026-06-24); 亚马逊24小时到账新政落地! (2026-09-30) | https://www.sellfox.com/blog/article/yamaxun-yuliujin-sellfox; https://www.sellfox.com/blog/content/36 | 2026-11-09 (verifier) | opinion (vendor) |
517
+ | 智赢ERP 财务报告使用指南 | https://www.zying.net/helpdet-729.html | 2026-11-09 (verifier) | opinion (vendor) |
518
+ | AMZ123: 关于亚马逊回款和收款… (2022-01-18) | https://www.amz123.com/t/K0djSBnw | 2026-11-09 (verifier) | opinion (reproduces an old Amazon FAQ) |
519
+ | Amazon Ads delays advertiser payment overhaul to August (ppc.land, 2026-04-15) | https://ppc.land/amazon-ads-delays-advertiser-payment-overhaul-to-august-after-pushback/ | 2026-11-09 (verifier) | opinion (quotes Amazon) |
520
+ | selling-partner-api-models commit history of finances_2024-06-19.json (dcb0ef91, df7c6298, db2936aa) | `gh api` (read-only GET) | 2026-11-09 (verifier) | command-verified |
521
+ | Searches with no citable result: 知无不言 (not indexed), 金蝶/用友 Amazon connectors, 马帮/易仓 reconciliation | WebSearch | 2026-11-09 | — |
522
+ | Update on advertiser payments (Amazon Ads, 2026-04-14) | https://advertising.amazon.com/library/news/update-on-advertiser-payments | 2026-11-10 (gap fill, curl) | official |
523
+ | Sponsored ads consolidated invoice statement download is now global (2024-01-12) | https://advertising.amazon.com/resources/whats-new/sponsored-ads-consolidated-invoice-statement-download-now-global | 2026-11-10 (gap fill, curl) | official |
524
+ | Paying for Amazon Global Logistics (help GZJ4B4HXDUEWP4PC) | https://sellercentral.amazon.com/gp/help/external/GZJ4B4HXDUEWP4PC | 2026-11-10 (gap fill) | official via search snippet (JS shell to GET and WebFetch) |
525
+ | Amazon Shipping product update: June 2025 (2025-06-10) | https://shipping.amazon.com/insights-and-news/product-update-billing-delivery | 2026-11-10 (gap fill, curl) | official |
526
+ | Amazon Freight UK newsroom: credit limit approval; freight.amazon.com footer | https://freight.amazon.co.uk/newsroom/streamline-credit-limit-approval; https://freight.amazon.com/faq | 2026-11-10 (gap fill, curl) | official |
527
+ | Payment advice not being applied to invoices by Transparency (seller; Sandy_Amazon reply) | https://sellercentral.amazon.com/seller-forums/discussions/t/08aa04b3-a699-4f08-883f-1ce2ead6ab54 | 2026-11-10 (gap fill) | opinion / official staff reply |
528
+ | Reconciling fees to Tax Document Library invoices (JiAlex_Amazon reply) | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/2e4ae9c0-3814-4ec2-925a-dfc70f216cec | 2026-11-10 (gap fill) | official (staff reply) |
529
+ | Changes to Professional Selling Plan subscription fees for global sellers (News_Amazon, effective 2021-08-01) | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/a8ff250bb262db2136bedc7c9bc8d5d8 | 2026-11-10 (gap fill, raw HTML) | official, command-verified |
530
+ | Where to find your Amazon selling reports (KJ_Amazon, 2024-10-31) | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/5a7d44ff-358e-4c39-a6de-e67aff1a2770 | 2026-11-10 (gap fill, raw HTML) | official (staff) |
531
+ | Global Selling | https://sell.amazon.com/global-selling | 2026-11-10 (gap fill, curl) | official |
532
+ | SP-API Endpoints; Store Identifiers; Authorization Limits | `web01/sp-api-endpoints.md`, `web01/store-identifiers.md`, `web01/application-authorization-limits.md` | 2026-11-10 (gap fill) | official, command-verified |
533
+ | Authorize Private Applications; Website Authorization Workflow; Selling Partner Appstore Authorization Workflow; Selling Partner Authorizations FAQ | https://developer-docs.amazon/sp-api/docs/self-authorization.md; …/website-authorization-workflow.md; …/selling-partner-appstore-authorization-workflow.md; …/seller-authorizations-faq.md | 2026-11-10 (gap fill, curl) | official |
534
+ | FBA Reports (updatedAt 2026-10-13); Order Reports (2026-10-28); Returns Reports (2026-10-28) | https://developer-docs.amazon/sp-api/docs/report-type-values-fba.md; …/report-type-values-order.md; …/report-type-values-returns.md | 2026-11-10 (gap fill, curl) | official |
535
+ | Remote Fulfillment with FBA FAQ (MX) | https://vender.amazon.com.mx/remote-fulfillment-fba/frequently-asked-questions | 2026-11-10 (gap fill) | official via search snippet (page now serves the sell.amazon.com copy) |
536
+ | Sell in Europe / FBA Europe pages (EFN fee wording) | https://sell.amazon.co.uk/fulfilment-by-amazon/fba-europe; sell.amazon.de/.fr copies | 2026-11-10 (gap fill) | official via search snippet |
537
+ | Local: orders_2026-01-01.json, ordersV0.json, data-kiosk schemas, dataKiosk_2023-11-15.json, financesV0.json event definitions | models clone db2936aa | 2026-11-10 (gap fill) | command-verified |
538
+ | ConnectBooks: Advertising per product in QuickBooks; how far back can ConnectBooks import | https://help.connectbooks.com/en/articles/5084147-advertising-per-product-in-quickbooks; …/9533258-… | 2026-11-10 (gap fill) | opinion |
539
+ | A2X: reconciling seller fee invoices; regions and marketplaces; currency; missing settlements; settlement history | https://support.a2xaccounting.com/en/articles/7950961-…; …/1132528-…; …/faqs/how-does-a2x-convert-…; …/faqs/why-are-some-of-my-settlement-files-missing; …/1132581-… | 2026-11-10 (gap fill) | opinion |
540
+ | Link My Books: Accessing Historical Data (2026-10-05) | https://help.linkmybooks.com/en/articles/7923978-how-do-i-get-older-data | 2026-11-10 (gap fill) | opinion |
541
+ | A2X: VAT on Amazon seller fees (2024-08-19) | https://a2xaccounting.com/ecommerce-accounting-hub/amazon-vat-seller-fees | 2026-11-10 (gap fill) | opinion |
542
+ | 领星 发货与结算差异报告 | https://www.lingxing.com/help/article/ShipSettlVarReport | 2026-11-10 (gap fill, curl) | opinion (vendor) |
543
+ | Seller thread: reconciled transaction reports vs shipped (UK) | https://sellercentral.amazon.co.uk/seller-forums/discussions/t/c9392c0e-b985-465e-86e1-8121a53b70ee | 2026-11-10 (gap fill) | opinion |
544
+ | Searches with no citable result: Amazon Freight US payment terms; Transparency billing rule; Global Snapshot; 欧洲联合账户 settlement split; Pan-EU storage settlement attribution; 领星/积加 history-sync limits; Taxomate history | WebSearch | 2026-11-10 (gap fill) | — |
545
+
546
+ ## Open questions
547
+
548
+ 1. Can any Date Range Transaction or Summary report be found with `getReports` after the seller requests it in Seller Central, as `…_HOLDS_DATA` can? Amazon's 2026 post addresses "Developers who access transaction reports through the reports API". A `getReports` call over all types after a Seller Central request would show it.
549
+ 2. Does `listTransactions` accept `relatedIdentifierName=SETTLEMENT_ID` (release note, 2026-07-29; in the model only on 2026-10-28), or only `FINANCIAL_EVENT_GROUP_ID`/`ORDER_ID` (model after the 2026-10-29 rollback, and the reference)? One call answers it. Does any reply carry `storeName` `AMAZON_FBA_FROM_ORIGIN`?
550
+ 3. For a closed group, does the sum of `listTransactions` (group filter) equal the settlement `total-amount`, and with which status: `RELEASED` only (Amazon's tutorial) or also `DEFERRED_RELEASED`? How do reserve and previous-reserve rows appear in `listTransactions`?
551
+ 4. Does `listPayouts` / `listExpectedPayouts` answer for a NA seller (Role Mappings NA/EU/FE vs the model's EU8 list)? What is a payout's `id` against the settlement-id and the `FinancialEventGroupId`?
552
+ 5. Is `settlement-id` (report) = `SETTLEMENT_ID` (Finances, Transfers) ≠ `FinancialEventGroupId`, as Amazon's examples suggest? Lingxing says the settlement id exists only once the report is out.
553
+ 6. The V2 file on a real account: is there a header row plus a first totals row (practitioners) with blank detail columns? Date formats of `settlement-start-date`/`deposit-date` per marketplace (US vs EU/JP)? Is `posted-date` still MM/DD/YY in EU files? The decimal separator per marketplace?
554
+ 7. Which `transaction-type` values appear (Order, Refund, Adjustment, ServiceFee, FBAFees, other-transaction, other-transaction - Reversal, …), and which carry `order-id`, `shipment-id` and `sku` in which sense (GitHub #5353)?
555
+ 8. How a negative settlement and the card charge appear on a real account: in the file, in `listFinancialEventGroups` (`OriginalTotal` negative? `FundTransferStatus`?), in `listTransactions`.
556
+ 9. How a multi-marketplace account (EU unified, NA unified) splits settlements per marketplace and currency, and what `ConvertedTotal` shows when the deposit currency differs.
557
+ 10. Whether `listSummary` with `SETTLEMENT_ID` reproduces the Statement view's lines, including Beginning Balance and reserves.
558
+ 11. The "June 29, 2026" Finances release-note link in the Finances API page has no matching entry in the saved release notes. What changed, and is it what the "Finance API Rollback" model commit reverted?
559
+ 12. The account's DD+7 migration date and whether its Date Range reports already show the 2026 format.
560
+ 13. Do settlement periods on the account run shorter than 14 days after a Disburse on Demand (Amazon China) or not (Sellfox)? The groups' start and end dates show it.
561
+ 14. Does every Amazon Shipping invoice appear in the seller account as an `Adjustment` with `TransactionNumber`, or only those settled from the balance? Do ads paid by card leave any trace in the finance faces?
562
+ 15. Which store's settlement carries Pan-EU monthly storage, EFN fees, AWD fees, account-wide service fees, and the EU subscription ("one European country")? Is it the store of registration, the storage country, or the store of sale?
563
+ 16. Is the `selling_partner_id` the same across the seller's merged NA, EU and FE accounts? How many authorizations does the seller's set of accounts need against the private application's limit?
564
+ 17. Does an order shipped in several shipments post one `ShipmentEvent` and one settlement row group per `shipment-id`? Does the settlement's `order-item-code` equal the shipments report's `amazon-order-item-id`?
565
+ 18. After the seller requests an archived settlement in Seller Central, does `getReports` list it, with a new `createdTime` (practitioners say the API then reaches it)?
566
+ 19. How far back do `listTransactions` and `listFinancialEventGroups` return data? No earliest date is stated.
567
+ 20. Settlement currency per European store on the account (SE, PL, TR, BE, NL, IE), and whether TR or AE/SA sit in the same login.
568
+
569
+ ## Positions
570
+
571
+ - **P-rec-1.** Settlement reports cannot be requested or scheduled. Amazon generates them, and cx finds them with `getReports` filtered by `reportTypes=GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2`, then fetches each through `getReportDocument`. Source: Settlement Reports (Amazon, 2026-10-14); reports_2021-06-30.json.
572
+ - **P-rec-2.** `GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE` and `GET_V2_SETTLEMENT_REPORT_DATA_XML` are removed on 2026-11-11 (deprecated 2025-03-17; the removal date moved from 2026-03-25). Calls fail from that date. `…_FLAT_FILE_V2` is the only settlement report, and there is no XML replacement. Source: SP-API Deprecation Schedule; changelog "Deprecation of two payment settlement report types".
573
+ - **P-rec-3.** The V2 settlement report is tab-delimited with 24 named columns (list in this file). Amazon publishes the names but no per-column or per-transaction-type definition. Source: Settlement Reports; Amazon-side acknowledgement in GitHub #5353 is [opinion].
574
+ - **P-rec-4.** In V2 every amount sits in one `amount` column, classified by `amount-type` and `amount-description`. New fee types arrive as new values, not new columns, and Amazon publishes no closed list of either. Source: Settlement Reports; deprecation changelog.
575
+ - **P-rec-5.** V2 amounts are written in the marketplace's local number format (Amazon's example: `95,00` for EU instead of `95.00`). `posted-date` is MM/DD/YY and `posted-date-time` is "YYYY-MM-DD HH:MM:SS UTC" (Amazon's changelog). Source: Settlement Reports; deprecation changelog.
576
+ - **P-rec-6.** Reports are retained for at most 90 days, and `getReports` looks back 90 days by default, so the API cannot list a settlement report older than about 90 days. Older settlements are downloadable only in Seller Central. Source: reports_2021-06-30.json; Improvado (opinion) agrees.
577
+ - **P-rec-7.** Settlement reports require Finance and Accounting. So do `listTransactions`, `listSummary`, `listBalances`, `listFinancialEventsByOrderId`, `listPayouts` and `listExpectedPayouts`. `listFinancialEventGroups` and `listFinancialEventsByGroupId` take Finance and Accounting or, in the EU only, Account Information Service Provider. The Deferred Transaction report is Finance and Accounting per the Payment Reports page and is absent from Role Mappings for Types. Source: Role Mappings for SP-API Operations (2026-10-28); Role Mappings for SP-API Types (2026-09-09); Payment Reports.
578
+ - **P-rec-8.** A settlement covers released money in one payout period. Deferred transactions are not in a settlement until they are released, and only disbursed transactions enter settlement reports. Source: News_Amazon 2021-09-20 and 2024-10-04; A2X (opinion).
579
+ - **P-rec-9.** Finances v0 event operations (`listFinancialEvents`, `…ByGroupId`, `…ByOrderId`) do not show deferred events until they are released. `listTransactions` (2024-06-19) returns `DEFERRED`, `RELEASED` and `DEFERRED_RELEASED` unless filtered by `transactionStatus`. Source: financesV0.json; finances_2024-06-19.json; Get the latest transactions.
580
+ - **P-rec-10.** A financial event group is a settlement period. Its `ProcessingStatus` is `Open` (`OriginalTotal` is then the current balance) or `Closed` (`OriginalTotal` is then the disbursement *or charge* amount). It carries `FundTransferDate` (closed only), `TraceId`, `AccountTail`, `BeginningBalance` and `ConvertedTotal` (in the disbursed currency). Source: financesV0.json; Retrieve the amount and status of a payment; Retrieve your current balance.
581
+ - **P-rec-11.** Amazon's documented way to list the transactions behind a payment: take the payment's `FinancialEventGroupId` from `listFinancialEventGroups`, then call `listTransactions` with `relatedIdentifierName=FINANCIAL_EVENT_GROUP_ID` and `transactionStatus=RELEASED`. Source: Determine payment transactions (2026-09-09).
582
+ - **P-rec-12.** `listTransactions` filters by `FINANCIAL_EVENT_GROUP_ID` or `ORDER_ID` only: these are "the only `relatedIdentifier` with filtering capabilities at the moment", per the model and the live reference. The 2026-07-29 release note announces a `SETTLEMENT_ID` filter. It was in the model for one day (2026-10-28) and was removed by the 2026-10-29 "Finance API Rollback". `SETTLEMENT_ID` is returned in responses and filters `listSummary`. Source: finances_2024-06-19.json at db2936aa; listTransactions reference (2026-09-10); release notes 2026-07-29; commits df7c6298 and db2936aa [command-verified].
583
+ - **P-rec-13.** `listSummary` returns `netProceeds` and nested `breakdowns` for a date range (ISO dates) or for one settlement (`relatedIdentifierName=SETTLEMENT_ID`). Amazon's reference example uses the Statement view's categories (Sales, Product Charges, Expenses, FBA fees, Refunds). Source: finances_2024-06-19.json; listSummary reference; Retrieve a financial summary.
584
+ - **P-rec-14.** `listBalances` returns `AVAILABLE`, `RESERVED`, `TOTAL`, `DEFERRED` and `ACCOUNT_LEVEL_RESERVE`, by account type and marketplace, either now or as of a past date (`asOfDate`). Source: finances_2024-06-19.json; release notes 2026-07-29.
585
+ - **P-rec-15.** Amazon uses different clocks across documents: settlement `posted-date-time` is UTC; Date Range reports run 12:00 a.m. to 11:59 p.m. local time; `listSummary` "is calculated based on the marketplace timezone of the seller, not UTC"; `listBalances.lastUpdatedTime` is in the marketplace's local time. A transaction near midnight can fall on different dates in each. Source: deprecation changelog; Quick Tip: Date Range reports; Retrieve a financial summary; finances_2024-06-19.json.
586
+ - **P-rec-16.** Finance windows on the APIs: a `listTransactions` window over 180 days returns empty, not an error, and so does a `listFinancialEventGroups` window over 180 days. `postedBefore` must be at least two minutes in the past. Events from the last 48 hours may be missing. Pages may be empty while `nextToken` continues. `listFinancialEventsByGroupId` covers only the last two years. Source: finances_2024-06-19.json; financesV0.json.
587
+ - **P-rec-17.** Date Range Transaction (CSV) and Summary (PDF) reports are requested in Seller Central (Payments/Finance → Reports Repository). They cover transactions by the date posted to the account, "may not correspond to the order date or the shipment date", and can take up to three hours to generate. Source: Quick Tip: Date Range reports (Amazon staff).
588
+ - **P-rec-18.** From 2026, for periods from 2025-01-01, Date Range Transaction and Summary reports include deferred and released transactions. Their Date/Time is the posted date, and the Transaction report gains a deferred/released status column and a Transaction Release Date (blank while deferred). The rollout was US/CA/MX/BR by 2026-04-30; BE/FR/DE/IE/IT/NL/PL/ES/SE/IN/EG/SA/TR/AE/UK from 2026-03-23 to 2026-05-31; other stores by 2026-06-30. Periods before 2025-01-01 keep the old format. Source: News_Amazon 2026-03-18 and 2026-03-31.
589
+ - **P-rec-19.** No SP-API report type produces the Date Range Transaction or Summary report. The Report Type Values page lists, under Payment, only `GET_DATE_RANGE_FINANCIAL_HOLDS_DATA`. Source: Report Type Values (2026-09-10); Payment Reports.
590
+ - **P-rec-20.** `GET_DATE_RANGE_FINANCIAL_HOLDS_DATA` (Deferred Transaction Report) is a point-in-time CSV of currently deferred transactions, covering up to 10 years. The API can retrieve it only after the seller requests it in Seller Central's Payments Reports Repository, and a released transaction leaves it. Source: Payment Reports; changelog "New: Deferred Transaction Report type"; News_Amazon 2024-10-04; Amazon's reply on GitHub #4830.
591
+ - **P-rec-21.** Delivery-date reserve (DD+7): funds are deferred at shipment, become reserves on delivery, and move to the balance seven days later. The delivery date is the tracked delivery (at least one physical carrier scan) or, without valid tracking, the latest estimated delivery date (handling plus transit time). Amazon's worked examples disagree on the day count: the English ones land on the eighth calendar day after delivery, and one Chinese one on the seventh. A transaction's own release date is its `maturityDate`. Invoiced (B2B) orders are also deferred, and `DeferredContext.deferralReason` names `DD7` or `B2B`. Amazon moved remaining accounts to DD+7 on the date its e-mail gave each account: a US e-mail gives 2026-03-12, and UK/EU sellers report e-mails giving 2026-03-05, 2026-03-12 or 2026-03-19 (EU forum thread 7d30d954, 2025-09-30). No Amazon page gives these dates; they are known only from e-mails sellers pasted in Seller Forums. Source: Amazon's email quoted in Seller Forums (US, 2025-09-29); Amazon's e-mails as UK/EU sellers posted them, "DD+7 Deferred Again" (https://sellercentral-europe.amazon.com/seller-forums/discussions/t/7d30d954-dd74-4c46-b01e-48a7cc7f5c45, 2025-09-30, via money-flow P-flow-14); Amazon China DD+7 explainer (2026-06-05); finances_2024-06-19.json; Amazon staff post via survey. Read at run time: the reserve period that applies to the seller's own marketplace is read per transaction from `listTransactions` (`DeferredContext.deferralReason` and `maturityDate`, against `postedDate`), and the deferred total from `listBalances` (`DEFERRED`).
592
+ - **P-rec-22.** An account-level reserve is distinct from a deferred transaction. It can remain for a claim, a chargeback or an account review. Amazon reports it as `ReserveEvent` at settlement close (v0) and `ACCOUNT_LEVEL_RESERVE` (balances). Practitioners name the settlement-file rows "Current Reserve Amount" and "Previous Reserve Amount Balance". Source: News_Amazon 2024-10-04; financesV0.json; finances_2024-06-19.json; Intentwise, wimoor, A2X (opinion) for the row labels.
593
+ - **P-rec-23.** When a settlement's balance is negative, Amazon recovers the debt from the seller's charge instrument or later proceeds. v0 records this as `DebtRecoveryEvent` (`DebtPayment`, `DebtPaymentFailure`, `DebtAdjustment`, with charge instrument tail and amount, and the begin/end of the group where the debt arose), and a closed group's `OriginalTotal` can be a charge. Source: financesV0.json; A2X, beancount, Lingxing (opinion) on "pending balance" / "Successful Charge" / 信用卡扣款.
594
+ - **P-rec-24.** A payout's money can arrive in a currency other than the marketplace's. `OriginalTotal` is in the transactions' currency and `ConvertedTotal` in the disbursed currency. Source: financesV0.json; Lingxing (opinion) on bank accounts bound in another currency.
595
+ - **P-rec-25.** Transfers `listPayouts` returns payouts with status history (`STARTED`, `IN_TRANSIT`, `PAID`, `FAILED`, `CANCELLED`, `NO_PAYOUT`), type (`SCHEDULED`/`ON_DEMAND`), `traceId` ("The banking network's unique identifier"), `paymentRail`, `period`, account tail and `SETTLEMENT_ID`. `listExpectedPayouts` returns the next payout's `scheduledDate` and status (`SCHEDULED`, `DISABLED`, `AT_RISK`, `NO_PAYOUT_EXPECTED`). The model names EU8 marketplaces, while Role Mappings lists NA/EU/FE. Source: transfers_2024-06-01.json; Role Mappings; Retrieve payouts.
596
+ - **P-rec-26.** `initiatePayout` is the only payout-moving write. Role Mappings give it Regions "EU" and "Required roles (need at least one)": Finance and Accounting, or Payment Initiation Service Provider, so either role alone suffices. The model lists DE, FR, IT, ES, SE, NL, PL and BE, and allows "one on-demand payout for each marketplace and account type within a 24-hour period". It returns `payoutReferenceId`, "The financial event group ID for a successfully initiated payout". Source: transfers_2024-06-01.json; Transfers API page; Role Mappings for SP-API Operations (2026-10-28). Read at run time: the marketplaces and the once-per-24-hours limit are stated in the `initiatePayout` operation's own description (reference https://developer-docs.amazon/sp-api/reference/initiatepayout.md, updatedAt 2026-09-10), and an on-demand payout already made shows in `listPayouts` (`type` `ON_DEMAND`, `creationDate`).
597
+ - **P-rec-27.** The Finance Remittance API (v2026-03-17) and the Invoices API (v2026-06-25) are documented "Vendors only". Remittance mirrors Vendor Central's Remittance view. Neither carries a seller's settlement or bank-payment detail. Source: Finance Remittance API page; Invoices API page.
598
+ - **P-rec-28.** In Amazon's examples, a financial event group id is a long opaque string while a settlement id is numeric, and the example payout's `id` equals its `SETTLEMENT_ID`. The two identifiers are not interchangeable without a lookup. Source: finances_2024-06-19.json, transfers_2024-06-01.json examples [command-verified]; Lingxing (opinion): the settlement id exists only once the report is issued.
599
+ - **P-rec-29.** Settlement lines with no order (storage, subscription, service fees, reserves, reimbursements) have empty `sku` and `order-id`, and per practitioners an empty `marketplace-name`. Filtering a settlement by SKU or order drops them. Some FBA fee rows carry an FBA shipment id in `order-id`. Source: [opinion] Nova; GitHub #5291, #5353. Amazon-side acknowledgement in #5353 is [opinion].
600
+ - **P-rec-30.** Amazon's staff gives the cross-reference route: find an order's posted date in Transaction view, then find the payment in the Settlement or Date Range report by that date. Source: Where's My Money? (Amazon staff, 2025-08-26).
601
+ - **P-rec-31.** Each document counts a different set of transactions on a different date:
602
+ - the settlement: released transactions by payout period;
603
+ - Date Range: posted transactions by local posted date (deferred included from 2026);
604
+ - Business Reports and the economics dataset: ordered sales by order date;
605
+ - `listTransactions`: every posted transaction by UTC posted date.
606
+
607
+ A month's figure from one will not equal another's without stating the difference. Source: Amazon pages above; Nova (opinion) on 2–4 days of month-boundary gap.
608
+ - **P-rec-32.** A settlement that crosses month-end can be booked whole on its period or split by the month each line posted. Practitioner tools split it (A2X's carried-forward account; Lingxing's "部分对账,需要分月进行对账"). The choice is the seller's. Source: [opinion] A2X support 959804/1984021; Lingxing.
609
+ - **P-rec-33.** Accounting choices practitioners describe, none of them Amazon's rule: a clearing ("Amazon Settlement Clearing") account that receives each settlement, with the bank deposit as a transfer; gross sales with fees as expenses vs net; reserves as a current asset; marketplace facilitator tax as a pass-through Amazon "withheld" (v0 `MarketplaceFacilitatorTax-*`); a month-end deferral accrual (A2X, Link My Books, Bookkeep). Each changes what the P&L and balance sheet show. The seller picks. Source: [opinion] A2X, beancount, Synder, Link My Books, Bookkeep; financesV0.json for the tax charge types.
610
+ - **P-rec-34.** The deferral changed Payments-report timing twice: from late October 2024 deferred sales entered the Transaction/Summary reports on release, and from 2026 by posted date with status columns. Amazon did not restate past reports, and per practitioners the US 1099-K follows the deferred/posted timing. A comparison across these dates carries that shift. Source: News_Amazon 2024-10-04 and 2026-03-18; Finaloop, Bookkeep (opinion).
611
+ - **P-rec-35.** Settlement and payment document paths moved in new Seller Central (Finance workspace, practitioner date 2026-09-21). Sellers report the Statement view moved under Finance → Manage payments, and settlement downloads as .txt/.xml under Finance → Reports Hub. A seller following an older path guide may not find the page. Source: [opinion] selleressentials.com; Seller Forums threads 2026-09-02 and 2026-09-24.
612
+ - **P-rec-36.** Amazon's changelog (2026-10-21) announces a `BusinessContext.storeName` value `AMAZON_FBA_FROM_ORIGIN` on `listTransactions` "Starting 6 November 2026", in addition to `AMAZON_HAUL`. It tells integrations to handle unknown enum values gracefully. The model added the value on 2026-10-28 and removed it in the 2026-10-29 rollback, and the live reference lists only `AMAZON_HAUL`. `storeName` values in replies may therefore go beyond the model's enum. Source: SP-API changelog 2026-10-21; commits df7c6298, db2936aa [command-verified]; listTransactions reference.
613
+ - **P-rec-37.** No operation returns the reason for an account-level reserve, the seller's settlement cycle setting, or a Date Range report. These are Seller Central's. Source: [seat] from the models read (no such field or operation) — enters no skill until a live account confirms (open questions 1, 10).
614
+
615
+ - **P-rec-38.** Per Amazon's Chinese explainer, the automatic settlement cycle stays 14 days, but each Disburse on Demand truncates the current settlement period and restarts the 14 days. A settlement period's length is therefore read from its start and end, not assumed. On the Payments dashboard the request button works on the Standard Orders or Invoiced Orders row, not the Deferred transactions row. Sellfox (vendor) says the opposite on truncation. Source: Amazon China DD+7 explainer (2026-06-05) [official]; Sellfox blog 2026-06-24 [opinion]. Read at run time: the seller's own settlement periods are read from `listFinancialEventGroups` (`FinancialEventGroupStart`, `FinancialEventGroupEnd`), and the next payout's period and date from `listExpectedPayouts` (`period`, `scheduledDate`).
616
+ - **P-rec-39.** DD+7 reserves held in the account-level reserve before an account's switch were not moved into deferred transactions, so both can carry DD+7 money in the transition. Source: Amazon China DD+7 explainer (2026-06-05) [official]; Sellfox [opinion].
617
+ - **P-rec-40.** From 2026-08-01, advertisers Amazon contacted pay for ads by deduction from the seller account balance (the default if no choice is made) or by monthly invoice. Amazon says balance deduction is already the method of most advertisers. Ad charges then appear in the settlement. Source: [official] Amazon Ads, Update on advertiser payments (2026-04-14), https://advertising.amazon.com/library/news/update-on-advertiser-payments, re-read 2026-11-10 by the money-flow verifier (money-flow P-flow-34, G4): Amazon "let a small number of advertisers know" it would update "their available payment methods to pay with their seller or vendor account balance or Pay by Invoice… deferring this change until August 1, 2026", and "If an advertiser doesn't select a preference… we'll automatically update their default payment method to deduction from available seller or vendor account balance". Amazon's page does not say whether the change took effect; ppc.land (2026-04-15, quoting Amazon) and Sellfox report it from 2026-08-01 [opinion].
618
+ - **P-rec-41.** Chinese ERPs present reconciliation in named shapes, each a fact about that tool, none Amazon's:
619
+ - Lingxing: statement-level reconciliation against the monthly Summary, split by month when a statement crosses months.
620
+ - Sellfox: per-store monthly split into settled-this-month, deferred-earlier-settled-this-month and deferred-this-month-settled-later; receivables by shipped or settled basis, with time-zone conversion.
621
+ - Zying: settlement groups with status open / paid / failed, opening balance, reserve held, payout and a CNY conversion at the period rate.
622
+
623
+ Source: [opinion] Lingxing SettlementCenter; Sellfox blog 2026-06-24 and 2026-09-30; Zying help 729.
624
+
625
+ - **P-rec-42.** Advertising reaches the books by two paths. Balance-deducted ad charges sit in the settlement as `ProductAdsPaymentEvent` lines carrying the Ads `invoiceId`, base and tax. Card-paid and Pay-by-Invoice charges are billed outside the settlement on monthly invoices due 30 days later. A card stays on file as backup even for balance-deducted advertisers. Ads invoices sit in the ads console's Billing history, per country, with a consolidated statement of the last 90 days. Source: Amazon Ads, Update on advertiser payments (2026-04-14) and consolidated invoice launch (2024-01-12) [official]; financesV0.json [command-verified]; ConnectBooks (opinion): card-paid ads are not in its settlement import. Read at run time: the invoice terms are on Amazon Ads' page Update on advertiser payments (https://advertising.amazon.com/library/news/update-on-advertiser-payments) and the statement window on Sponsored ads consolidated invoice statement download is now global (https://advertising.amazon.com/resources/whats-new/sponsored-ads-consolidated-invoice-statement-download-now-global); no SP-API operation gives either.
626
+ - **P-rec-43.** Amazon Lending in the UK is repaid "monthly directly via Direct Debit", outside the settlement. Loan money that does pass through the account posts as v0 `LoanServicingEvent` (`LoanAdvance`, `LoanPayment`, `LoanRefund`). The US page lists partner lenders and does not say how they collect. Source: sell.amazon.co.uk and sell.amazon.com Amazon Lending (via money-flow D7) [official]; financesV0.json [command-verified]. Read at run time: the repayment method is on the Amazon Lending page of the seller's own store (UK https://sell.amazon.co.uk/programmes/amazon-lending; US https://sell.amazon.com/programs/amazon-lending, both as money-flow lists them); no SP-API operation gives it.
627
+ - **P-rec-44.** AGL is paid either in USD from the Seller Central disbursement account, where it appears as "FBA International Freight Shipping Charge" and "FBA International Freight Duties and Taxes Charge", or in CNY by wire through Shipper Central against a Chinese tax bureau invoice, outside the settlement. Source: Paying for Amazon Global Logistics (GZJ4B4HXDUEWP4PC) [official via search snippet; the page was not read whole]. Read at run time: the payment currencies and paths are on Amazon's help page Paying for Amazon Global Logistics (https://sellercentral.amazon.com/gp/help/external/GZJ4B4HXDUEWP4PC, a JS shell to plain GET), and the USD charges as they posted are the settlement V2 rows by `amount-description`.
628
+ - **P-rec-45.** Amazon Shipping (the carrier service) bills by invoice in Shipper Central, payable at any time and by card with autopay (2025-06-10). Finances v0 `AdjustmentItem.TransactionNumber` can carry an Amazon Shipping invoice number (2024-11-06). Amazon Freight extends credit allowances to shippers and is offered by Amazon Logistics, Inc., a separate Amazon company. Seller Central's Buy Shipping labels, by contrast, are charged in the settlement. Source: shipping.amazon.com product update; SP-API release notes 2024-11-06; freight.amazon.co.uk newsroom; freight.amazon.com [official].
629
+ - **P-rec-46.** Transparency codes were invoiced monthly and paid outside the settlement in a seller's account, with Amazon staff naming the invoice-remittance and past-due addresses. No Amazon page read states the billing rule. Source: Seller Forums thread 08aa04b3 (seller) [opinion], with Sandy_Amazon's reply [official, staff].
630
+ - **P-rec-47.** Amazon's fee invoices sit in the Tax Document Library, "typically issued monthly". Payment reports show fees as they occur, Order ID is the matching key, and month-end timing differences are expected. A2X adds that the invoice uses the transaction completion date, can lag the settlement by up to four weeks, and is followed by credit notes for refunded fees or retro-charges. Source: JiAlex_Amazon reply, Seller Forums 2e4ae9c0 [official, staff]; A2X 7950961 [opinion]. No operation or page gives this; the value stands as read on 2026-11-10, EU.
631
+ - **P-rec-48.** The v0 event model names account-level money that does not reach the bank deposit or that is billed at account level: `AdhocDisbursementEvent` (e.g. "Disbursed to Amazon Gift Card balance"), `FailedAdhocDisbursementEvent` (e.g. `CREDIT_CARD`, `HARD_DECLINED`), `DebtRecoveryEvent.ChargeInstrumentList`, `ValueAddedServiceChargeEvent` and `CapacityReservationBillingEvent`. Source: financesV0.json [command-verified].
632
+ - **P-rec-49.** Seller Wallet does not change the settlement cycle. Money moved, converted or charged inside the wallet after disbursement is recorded in the wallet's statements, and its API needs AISP or PISP, not Finance and Accounting. Source: sell.amazon.com Seller Wallet and the Seller Wallet model (via money-flow F3, S5) [official].
633
+ - **P-rec-50.** Amazon sells through a North America and Brazil unified account (US, CA, MX, BR), a Europe account, and country-specific Asia-Pacific accounts. The SP-API serves them from three regional endpoints: NA (CA, US, MX, BR), EU (IE, ES, UK, FR, BE, NL, DE, IT, SE, ZA, PL, SA, EG, TR, AE, IN) and FE (SG, AU, JP). Source: sell.amazon.com/global-selling; SP-API Endpoints (2026-09-09) [official].
634
+ - **P-rec-51.** Each selling account is authorized separately, and each authorization yields its own refresh token. For accounts merged across regions, "The **Authorize app** button appears for each of your merged accounts." Only the Primary User can self-authorize. A private application has a self-authorization limit (figure under Facts for human readers only). Amazon deactivates authorizations not renewed and not called for more than 365 days. Source: Authorize Private Applications; Authorization Limits; Selling Partner Authorizations FAQ [official]. A2X (opinion): one connection per region, and one per Seller ID where stores in a region have different Seller IDs. Read at run time: the self-authorization limit is on Authorization Limits (https://developer-docs.amazon/sp-api/docs/application-authorization-limits.md) and the 365-day rule on Selling Partner Authorizations FAQ (https://developer-docs.amazon/sp-api/docs/seller-authorizations-faq.md).
635
+ - **P-rec-52.** For merged global accounts, the Professional subscription is "divided across these accounts, and will be charged in the currency of each Amazon store", only where there are active listings in the month, on one common billing day. Americas stores are each billed where they have active listings on the billing day. European stores are "charged a subscription fee in just one European country". Source: News_Amazon, effective 2021-08-01 [official, command-verified on raw HTML]. AMZ123 answers saying only the US fee is charged conflict, and Amazon's text is the one cited. Read at run time: where and in which currency the seller's subscription was charged is read from the subscription rows of each store's settlement V2 and `listTransactions` (`marketplaceDetails`, `totalAmount.currencyCode`), and the rule from Changes to Professional Selling Plan subscription fees for global sellers (https://sellercentral-europe.amazon.com/seller-forums/discussions/t/a8ff250bb262db2136bedc7c9bc8d5d8).
636
+ - **P-rec-53.** Amazon keeps payouts, balances and summaries per store and per account type: one on-demand payout "for each marketplace and account type" per 24 hours; `listPayouts` "grouped by the seller's account groups"; `listBalances` and `listSummary` filter by `marketplaceIds` and `accountType`; each transaction carries `sellingPartnerMetadata.accountType` and `marketplaceId`. Seller Central shows Standard Orders and Invoiced Orders rows and an "All" option on Date Range reports. Source: transfers_2024-06-01.json, finances_2024-06-19.json [command-verified]; §Amazon C.
637
+ - **P-rec-54.** Where Amazon states where a cross-store charge lands: EU removal, disposal and liquidation fees are charged "in the currency of the country where your inventory is stored"; Remote Fulfillment orders appear in the Canada or Mexico account where the customer bought, with referral fees by the store of purchase; the EFN fee is per order, set by the store of sale and the inventory pool. Amazon states no store for Pan-EU storage, AWD or account-wide service fees, which appear on rows with an empty `marketplace-name`. Source: EU rate card (via fulfilment-charges H3) [official]; vender.amazon.com.mx Remote Fulfillment and sell.amazon EU FBA pages [official via search snippet]; GitHub #5291 [opinion]. Read at run time: the currency and store of each charge are on the charge itself (`listTransactions` `totalAmount.currencyCode` and `marketplaceDetails`; settlement V2 `currency` and `marketplace-name`), and the rules on Rate Card Europe Fees (effective 2 November 2026, https://m.media-amazon.com/images/G/02/sell/images/261014-FBA-Rate-Card-EN.pdf, as fulfilment-charges cites it), Remote Fulfillment with FBA FAQ (https://vender.amazon.com.mx/remote-fulfillment-fba/frequently-asked-questions) and FBA Europe (https://sell.amazon.co.uk/fulfilment-by-amazon/fba-europe).
638
+ - **P-rec-55.** The faces for tying shipped units to posted sales, with their roles: Amazon Fulfilled Shipments (Amazon Fulfillment, Inventory and Order Tracking or Pricing; ≤ 1 month per report; requests capped per 8 hours including Seller Central requests; 1–3 hours late, rarely 24); the All Orders reports (all statuses and channels; 30 days per report, any start date; Pricing or Product Listing reach them); FBA Returns (Amazon Fulfillment or Pricing; daily); `searchOrders` (`fulfillmentStatuses` including `PARTIALLY_SHIPPED` and `CANCELLED`); and `listTransactions` by `ORDER_ID`. Seller-fulfilled returns by return date need Inventory and Order Tracking or Direct to Consumer Shipping (Restricted). Source: FBA Reports, Order Reports, Returns Reports pages; Role Mappings for Types (2026-09-09); orders_2026-01-01.json [official; command-verified]. Read at run time: the shipments report's request cap, span and lag are on FBA Reports (https://developer-docs.amazon/sp-api/docs/report-type-values-fba.md), the All Orders span on Order Reports (https://developer-docs.amazon/sp-api/docs/report-type-values-order.md), and the returns span on Returns Reports (https://developer-docs.amazon/sp-api/docs/report-type-values-returns.md).
639
+ - **P-rec-56.** The identifiers that meet across these faces:
640
+ - shipments report: `amazon-order-id`, `shipment-id`, `shipment-item-id`, `amazon-order-item-id`, `merchant-order-item-id`, `sku`;
641
+ - settlement V2: `order-id`, `shipment-id`, `order-item-code`, `merchant-order-item-id`, `adjustment-id`, `sku`;
642
+ - v0 `ShipmentEvent`: `AmazonOrderId`, with item `OrderItemId` and, for refunds, guarantee claims and chargebacks, `OrderAdjustmentItemId`;
643
+ - `listTransactions`: `ORDER_ID`, `SHIPMENT_ID`, `ORDER_ADJUSTMENT_ITEM_ID`;
644
+ - returns reports: order id and SKU only.
645
+
646
+ Practitioners report that settlement identifier columns do not always hold what their names say. Source: FBA Reports; Settlement Reports; financesV0.json; finances_2024-06-19.json [command-verified]; GitHub #5353 [opinion].
647
+ - **P-rec-57.** Lingxing's 发货与结算差异报告 is a named practitioner shape for this test, a fact about that tool. It traces each order through ship, settle and transfer; carries a 发出商品 (goods shipped, not settled) balance with roll-forward opening + shipped − shipped-and-settled − earlier-shipped-settled-now; and separates shipped-not-settled, settled-not-transferred and settled-not-shipped (rare, e.g. try-before-you-buy). It notes its shipment-report feed runs about three days late. A seller thread adds that cancelled orders remain in sales reports though they never complete. Source: Lingxing ShipSettlVarReport [opinion, vendor]; UK seller thread c9392c0e [opinion].
648
+ - **P-rec-58.** Each money face has its own horizon (table in §Amazon J): report documents 90 days; Date Range reports up to 365 days per report back to 2012; Deferred Transaction report up to 10 years; Transaction view 24 months; v0 by-group data two years; `listTransactions` and v0 groups 180 days per call with no earliest date stated; Orders API two years (JP/AU/SG from 2016); Data Kiosk start dates two years back with results kept 30 days; Ads invoice statement 90 days. Source: reports_2021-06-30.json, financesV0.json, finances_2024-06-19.json, orders models, Data Kiosk schemas [command-verified]; Payment Reports; Amazon Ads 2024-01-12; KJ_Amazon 2024-10-31 [official]. Read at run time: each horizon is stated on its face's own text — `getReports` (reports_2021-06-30.json), `listTransactions`, `listFinancialEventGroups` and `listFinancialEventsByGroupId` (finances models), `searchOrders` (orders_2026-01-01.json), the Data Kiosk schemas' `@resultRetention`, Payment Reports (https://developer-docs.amazon/sp-api/docs/report-type-values-payment.md), Where to find your Amazon selling reports (https://sellercentral-europe.amazon.com/seller-forums/discussions/t/5a7d44ff-358e-4c39-a6de-e67aff1a2770) and Sponsored ads consolidated invoice statement download is now global (https://advertising.amazon.com/resources/whats-new/sponsored-ads-consolidated-invoice-statement-download-now-global) — except the Transaction view's 24 months, which no operation or page read gives and which stands as read on 2026-11-09, US (Amazon staff Quick Tip via the survey).
649
+ - **P-rec-59.** Seller Central archives older settlements, and a "Request Report" click (Finance > Finance Reports > Understand Payout) regenerates one. Practitioners say the API reaches it after that. Amazon states no archive age. Connectors cap history on their side: Link My Books 24 months for Amazon, ConnectBooks two years, A2X about 10 settlements before a history request. Source: A2X, Link My Books, ConnectBooks help [opinion]; reports_2021-06-30.json for the 90-day API rule [command-verified].
650
+
651
+ 59 positions; P-rec-37 is [seat] and enters no skill. P-rec-41 rests on practitioners only; P-rec-46, P-rec-57 and P-rec-59 rest mainly on practitioners, and P-rec-44 on search snippets of an Amazon page.
652
+
653
+ ## Verification
654
+
655
+ Verified 2026-11-09/10 by the verifier seat (brief 306, `_verify.md`).
656
+
657
+ **What was checked**
658
+ - Every [official] quote a position rests on, re-read from the raw source with plain GETs of the `.md` pages on developer-docs.amazon. Pages: Settlement Reports, Payment Reports, the deprecation changelog, the Deprecation Schedule, Report Type Values, Determine payment transactions, Retrieve a financial summary, Retrieve the financial events in a group, Retrieve payouts, Get the latest transactions, the listTransactions reference, Release Notes, the 2026-10-21 changelog, Invoices API, Finance Remittance API and Reconcile payments to invoices. All quoted phrases were found. Two differ only in markup: "disjointed amounts may be consolidated" has a double space on the page; "statuses `RELEASED`, `DEFERRED`, and `DEFERRED_RELEASED`" is in backticks.
659
+ - Roles against `web01/role-mappings.md` (2026-10-28; live page identical for the Transfers block) and `role-mappings-for-types.md` (2026-09-09).
660
+ - Operations, rates and enums against the models clone at db2936aa, and the commit history of `finances_2024-06-19.json` through `gh api` (read-only).
661
+ - Cross-file: the Positions sections of money-flow, selling-fees, refunds-reimbursements-adjustments, product-profit, fulfilment-charges, sellers-tools-and-research, finance-surface and tax-and-invoices.
662
+
663
+ **Changes made (old → new, why, source)**
664
+ 1. Dated change 2026-07-29 and §SP-API B "Filter conflict": "release note claims; model and reference contradict" → the full history. The July commit dcb0ef91 never added the filter; df7c6298 (2026-10-28) added it; db2936aa (2026-10-29) removed it. Source: `gh api` commit patches.
665
+ 2. Dated change 2026-11-06 and **P-rec-36**: "`AMAZON_FBA_FROM_ORIGIN` appears from 2026-11-06" stated as fact → announced by the changelog, added to the model 2026-10-28, removed by the 2026-10-29 rollback, absent from the live reference. Why: the rollback patch deletes it. Meaning changed: the value is no longer a documented enum.
666
+ 3. **P-rec-12**: reworded around Amazon's exact "only `relatedIdentifier` with filtering capabilities" text and the one-day life of the filter in the model.
667
+ 4. **P-rec-21** and §Amazon C: "Amazon's examples make funds available on the eighth calendar day" → Amazon's examples disagree. The English ones give the eighth day; the Chinese explainer gives May 3 → May 10 (seventh) and May 5 → May 13 (eighth). The release date is the transaction's `maturityDate`. Also added Amazon's EDD rule. Meaning changed: no fixed day count is stated. Source: Amazon China, 2026-06-05.
668
+ 5. **P-rec-7**: "the Deferred Transaction report … Source: Role Mappings for report types" → the report is absent from Role Mappings for Types (0 hits) and its role comes from the Payment Reports page. Added the AISP (EU only) alternative for `listFinancialEventGroups` and `…ByGroupId`.
669
+ 6. **P-rec-26**: now quotes the Role Mappings row exactly (Regions "EU"; "Required roles (need at least one)": Finance and Accounting, Payment Initiation Service Provider) and the model's eight marketplaces.
670
+ 7. §Chinese tools: "赛狐 no reconciliation page; 金蝶/用友 no source; 雨果网/知无不言 no on-topic post" → new sourced entries for Amazon China's DD+7 explainer, two cifnews columns, two Sellfox articles, Zying ERP help and an AMZ123 reproduction of Amazon's old FAQ. 金蝶/用友 and 知无不言 remain without a citable source.
671
+ 8. Lingxing's "5% of 28 days" is now traced to Amazon's old payments FAQ as AMZ123 reproduces it (2022). It is still unverified against any current Amazon page.
672
+ 9. Added P-rec-38 (DoD truncates the cycle; Amazon vs Sellfox), P-rec-39 (pre-migration DD+7 reserves stay account-level), P-rec-40 (ads billed from balance from 2026-08-01; practitioner-sourced) and P-rec-41 (Chinese ERP shapes, facts about tools). Added two dated changes, three break-list items, nine pages-read rows and open question 13.
673
+
674
+ **Positions checked:** 37. Changed: 5 (P-rec-7, 12, 21, 26, 36). Made [seat]: 0 (P-rec-37 already was). Removed: 0. Added: 4 (38–41). D233 check: no position asks the seller, fixes a sequence, sets a threshold of ours or limits cx. P-rec-32 and P-rec-33 state choices without picking one.
675
+
676
+ **Could not verify**
677
+ - Seller Central help pages (JS shell). The settlement-file reserve row labels stay second-hand (Intentwise, wimoor).
678
+ - Express Payout on by default in the US from 2026-09-21 (Seller Essentials and Sellfox agree; no Amazon page found).
679
+ - The ads-billing change is read through ppc.land's quotes of Amazon. Amazon's own ads page was not read.
680
+ - Open question 11: the 2026-06-29 release-note link is still unresolved. The rollback reverted the 2026-10-28 October-release edits, not a June entry.
681
+
682
+ **Gaps left** (what a long-time operator would still look for)
683
+ - How a settlement shows a Disburse on Demand, an Express Payout or a failed transfer as rows (live file only).
684
+ - Per-marketplace `amount-description` vocabularies from real V2 files. Practitioner lists only.
685
+ - The EU unified-account and NA unified-account split of one settlement across marketplaces and currencies.
686
+ - Currency conversion (ACCS) fees as a settlement line: not researched.
687
+ - 金蝶/用友 and 马帮/易仓/通途 reconciliation features: no first-party page found. 知无不言 threads are not indexed.
688
+
689
+ **Gap fill (2026-11-10)** — by a research seat, against five gaps named by two completeness critics (a US/EU controller and a Chinese 财务总监). Limits held: no Amazon API host, no help-hub content call, plain GETs and search only, no repository writes outside this file.
690
+
691
+ What was added:
692
+ 1. *Money outside the settlement* (was thin: ads and card charge only). New §Amazon G, the list. It covers ads billing paths and `ProductAdsPaymentEvent.invoiceId`; Lending by Direct Debit and `LoanServicingEvent`; AGL's two payment paths and their labels (snippet); Amazon Shipping invoices and `AdjustmentItem.TransactionNumber`; Amazon Freight credit and its separate counterparty; Transparency invoices (seller and staff); Vine inside; Seller Wallet and Express Payout; v0 account-level events; fee VAT invoices in the Tax Document Library (staff). Positions P-rec-42 to P-rec-49.
693
+ 2. *Multi-marketplace, multi-region, multi-account layout* and 4. *consolidation* (was open question 9 only). New §Amazon H and §SP-API I. They cover Amazon's account shapes, the three regional endpoints, per-account authorizations and the private-app limit, the 2021 subscription rule for merged accounts (one EU country; Americas split by active listings, per-store currency), the per-store and per-account-type money APIs, and where Amazon says cross-store charges land. Positions P-rec-50 to P-rec-54. Open question 9 is now answered in part; questions 15, 16 and 20 carry the rest.
694
+ 3. *Revenue completeness.* New §Amazon I and §SP-API H. They cover the shipments, All Orders, FBA returns and FBM returns reports with roles, request caps and lags; Orders `FulfillmentStatus`; v0 `ShipmentEvent` identifiers; the cross-face key list; Lingxing's 发货与结算差异报告. Positions P-rec-55 to P-rec-57.
695
+ 5. *History horizons.* New §Amazon J (table) and positions P-rec-58 and P-rec-59.
696
+
697
+ Also added: one dated change (2025-06-10), break-list items 16–19, stable items 14–20, run-time rows, Seller-Central-only items, human-only figures, 23 pages-read rows, and open questions 14–20. Existing positions were not renumbered or changed. D233 check: P-rec-42 to P-rec-59 state facts and sources, and none sets a threshold, a sequence or a limit on cx. The [seat] inferences in §Amazon G–J stay outside the positions.
698
+
699
+ **Gaps left (gap fill 2026-11-10)**
700
+ - Transparency's billing rule on an Amazon page (only a seller thread and a staff reply on addresses).
701
+ - Amazon Freight's US payment terms; whether Freight ever bills through a seller account.
702
+ - The AGL payment page read whole (JS shell; snippets only).
703
+ - Which store's settlement carries Pan-EU storage, EFN fees, AWD fees and account-wide service fees (open question 15).
704
+ - Seller Central's Global Snapshot (no Amazon page); an Amazon Chinese page on 北美/欧洲联合账户 settlement.
705
+ - Amazon's own archive age for settlements in Seller Central; the earliest date `listTransactions` and v0 groups return.
706
+ - 领星/积加 history-sync limits (Lingxing's report counts only from 2023; no general limit found); Taxomate's history limit; 积加 multi-store settlement views.
707
+ - Whether a split shipment posts one finance event per shipment (open question 17).
708
+
709
+ **Correction 1 (2026-11-10)** — brief 306 correction 1 and the plugin zen's item 4: a value that differs by marketplace or changes from year to year is looked up, not carried. Limits held: no Amazon API host, no help-hub content call; plain GETs of three public developer-docs pages only to confirm their addresses (Authorization Limits, Selling Partner Authorizations FAQ, the `initiatePayout` reference). Operation and field names checked against the models clone at db2936aa (`DeferredContext.deferralReason`/`maturityDate`, `FinancialEventGroupStart`/`End`, `ExpectedPayout.period`/`scheduledDate`, `Transaction.totalAmount`/`marketplaceDetails`, `initiatePayout`'s description).
710
+
711
+ Positions changed:
712
+ 1. **Read at run time added**, value kept as evidence: P-rec-21 (DD+7 reserve period: `listTransactions` `DeferredContext`, `listBalances`), P-rec-26 (on-demand payout limit and marketplaces: `initiatePayout` reference; `listPayouts`), P-rec-38 (settlement cycle: `listFinancialEventGroups`, `listExpectedPayouts`), P-rec-42 (Pay by Invoice terms, 90-day statement: Amazon Ads pages), P-rec-43 (Lending repayment by store: Amazon Lending pages as money-flow lists them), P-rec-44 (AGL currencies: Paying for Amazon Global Logistics), P-rec-51 (self-authorization limit, 365-day rule: Authorization Limits; Authorizations FAQ), P-rec-52 (subscription split and currency: settlement and `listTransactions` rows; the 2021 News_Amazon post), P-rec-54 (cross-store charge currency and store: the charge's own fields; EU rate card, MX Remote Fulfillment FAQ, FBA Europe), P-rec-55 (report request cap, spans, lag: FBA, Order and Returns Reports pages), P-rec-58 (horizons: each face's model or page; the Transaction view's 24 months stands as read).
713
+ 2. **No operation or page gives it**: P-rec-47 (fee invoices "typically issued monthly"; stands as read on 2026-11-10, EU).
714
+ 3. **Aligned with money-flow** (verified 2026-11-10):
715
+ - P-rec-21: "Amazon moved remaining accounts to DD+7 on 2026-03-12" → the US e-mail gives 2026-03-12; UK/EU sellers report e-mails giving 2026-03-05, 2026-03-12 or 2026-03-19 (EU forum thread 7d30d954, 2025-09-30); no Amazon page gives them, only e-mails sellers pasted in forums. Source: money-flow P-flow-14. Meaning changed: no single migration date.
716
+ - P-rec-40: "Source: [opinion] ppc.land …; No Amazon page was read directly" → cites Amazon Ads, Update on advertiser payments (2026-04-14, https://advertising.amazon.com/library/news/update-on-advertiser-payments), re-read 2026-11-10 by the money-flow verifier, with its words ("deferring this change until August 1, 2026"; the balance-deduction default); whether it took effect stays ppc.land's and Sellfox's [opinion]. Source: money-flow P-flow-34, G4 and its Verification. The closing count line no longer says P-rec-40 rests on practitioners only.
717
+
718
+ Stable enough for a skill: item 17 (subscription split across merged stores, per-store currency) moved to What cx must read at run time, with where it is read; its number is kept as a pointer. Item 14 stays: it states that charges outside the settlement exist, and the existing run-time row "Charges outside the settlement" says where they are read.
719
+
720
+ Left untouched as history or interface contract: P-rec-2 (removal date of the V1 settlement reports), P-rec-18 (Date Range rollout dates by store), P-rec-34, P-rec-35, P-rec-36, P-rec-40's 2026-08-01 date; P-rec-6 and P-rec-16 (90-day report retention, 180-day windows, two-minute and 48-hour lags), which the models state as how the interface answers. Body sections outside Positions (the dated-changes line of 2025-09-29 and §Amazon C, which quote the US e-mail's 2026-03-12; "Could not verify" on the ads page) keep their wording; the positions above supersede them.
721
+
722
+ Positions checked: 59. Changed: 13 (P-rec-21, 26, 38, 40, 42, 43, 44, 47, 51, 52, 54, 55, 58). Removed: 0. Renumbered: 0.