Migration assurance
Finances listFinancialEvents to listTransactions migration
On August 27, 2027 Amazon removes three Finances v0 financial-event operations. The replacement is listTransactions in Finances API v2024-06-19, which uses a single transaction model with breakdowns and a 180-day window limit.
- Removed operations: listFinancialEvents, listFinancialEventsByGroupId, listFinancialEventsByOrderId
- Replacement: listTransactions (Finances API v2024-06-19)
- Removal date: August 27, 2027
- Window limit: postedAfter..postedBefore must be 180 days or less
Breaking changes
Multiple event-specific lists collapse into a single transactions[] array with recursive breakdowns[]. By-order and by-group queries move to relatedIdentifierName filters. Date ranges over 180 days can return an empty response. If postedAfter and postedBefore are more than 180 days apart, split the range into windows of 180 days or less.
Exact scanner coverage
The scanner flags the three removed operations (AMZ-FIN-OP-001), the v0 financialEvents endpoints (AMZ-FIN-ENDPOINT-001), date windows over 180 days (AMZ-FIN-WINDOW-001), unsafe request-time cutoffs (AMZ-FIN-TIME-SAFETY-001), recent-data completeness assumptions (AMZ-FIN-COMPLETENESS-001), empty-page and argument-unsafe pagination (AMZ-FIN-PAGINATION-001 / AMZ-FIN-PAGINATION-ARGS-001), incomplete deferred/released status handling (AMZ-FIN-STATUS-001), unsupported identifier mappings (AMZ-FIN-IDENTIFIER-001), flat-only breakdown parsing (AMZ-FIN-BREAKDOWN-001), and missing transaction-ID deduplication (AMZ-FIN-DEDUP-001). listFinancialEventGroups is not part of this removal and is never flagged.
Example finding
BLOCKER AMZ-FIN-OP-001: Deprecated Finances operation listFinancialEvents. Mapping: listFinancialEvents -> listTransactions (v2024-06-19).
listTransactions completeness contract
| Risk | Documented behavior | Safe integration behavior |
|---|---|---|
| Request-time safety | postedAfter and postedBefore must be more than two minutes before request time | Use a persisted buffered watermark |
| Recent completeness | Financial events might not include orders from the latest 48 hours | Replay a rolling overlap |
| Large window | More than 180 days apart returns an empty response | Split into windows of 180 days or less |
| Empty page | A page can be empty while nextToken exists | Stop only when nextToken is null |
| Token arguments | Token calls require the same original arguments | Persist and reuse the complete request |
Transaction lifecycle and identifiers
- Handle DEFERRED, RELEASED and DEFERRED_RELEASED without dropping or double-counting transitions.
- Only ORDER_ID and FINANCIAL_EVENT_GROUP_ID currently support request filtering.
- Deduplicate retries, overlapping windows and pages by stable transaction ID.
- Traverse transaction and item breakdowns recursively; do not assume a flat fee list.
Finances Reconciliation Validator preview
Validate a listTransactions sample with its request/page manifest. The validator checks window size, two-minute request safety, page-chain completeness, empty pages with nextToken, repeated tokens, original argument preservation, duplicate transaction IDs and recursive breakdown totals.
| Input | Check | Failure surfaced |
|---|---|---|
| Request manifest | postedAfter/postedBefore, requestedAt and original arguments | Oversized window or unsafe recent cutoff |
| Page samples | nextToken progression, empty pages and repeated tokens | Skipped or repeated transactions |
| Transactions | Recursive breakdown sum vs total | Accounting delta or unknown breakdown type |
Frequently asked questions
Is listFinancialEventGroups removed?
No. Only the three listed financial-event operations are removed. listFinancialEventGroups is not flagged as a blocker.
What is the date window limit?
If postedAfter and postedBefore are more than 180 days apart, Amazon returns an empty response. Split larger ranges into windows of 180 days or less.
How do I query by order?
Use relatedIdentifierName=ORDER_ID with the Amazon order id on listTransactions.
Official sources
Last reviewed: 2026-07-02.
Open the interactive scanner: /app#/finances