Update: Finances API v0 now includes TransactionNumber
In early 2024 Amazon added a string field called TransactionNumber to the AdjustmentItem payload of the Finances API v0. The field appears in GET /finances/v0/transactions responses for adjustments originating from services like Amazon Shipping, e.g., "AMZSH-INV-20240715-00123" for July 2024 fees.
Overview
In early 2024 Amazon upgraded the Finances API version 0 by inserting a new attribute named TransactionNumber into the AdjustmentItem payload. This identifier connects financial adjustments directly to the originating transaction—such as an Amazon Shipping invoice—making it easier for sellers to reconcile accounts, generate accurate reports, and resolve disputes.
Key Points
- New attribute introduced — AdjustmentItem objects now return a string field called TransactionNumber that mirrors the identifier used in the source transaction.
- Invoice correlation enabled — Sellers using Amazon Shipping can align the TransactionNumber with the invoice number displayed in the Shipping console, establishing a one‑to‑one relationship between finance entries and shipping costs.
- No version migration required — The enhancement is delivered inside the existing v0 endpoint, so current integrations continue to function without switching to a newer API version.
- Field appears conditionally — TransactionNumber is populated only when the adjustment originates from a service that generates a transaction number; otherwise the field is null or omitted.
- Backward‑compatible response — All previously available fields (AdjustmentAmount, ReasonCode, etc.) remain unchanged, preserving existing parsing logic while adding the new identifier.
How the TransactionNumber Addition Works
- Request format stays the same — Sellers keep calling
GET /finances/v0/transactionswith the same query parameters (e.g., MarketplaceId, CreatedAfter, CreatedBefore). For instance, a seller pulling adjustments for the last 30 days still sends the identical URL string as before. - Response payload expands — Each AdjustmentItem now includes a TransactionNumber key. If a seller retrieved adjustments for July 2024, a sample JSON entry might read
"TransactionNumber": "AMZSH-INV-20240715-00123"alongside the adjustment amount and reason. - Population is selective — The new field is filled only when the underlying service supplies a transaction identifier. An adjustment tied to a generic Amazon rebate would return , signaling that no direct transaction link exists.
Analysis & Recommendations
Why This Matters
TransactionNumber gives sellers a one‑to‑one link between finance adjustments and the exact shipping invoice, cutting manual reconciliation time and enabling automated invoice matching for disputes. The field is conditionally populated, so null‑checks are required.
Key Takeaways
- AdjustmentItem now returns a string field TransactionNumber (e.g., "AMZSH-INV-20240715-00123").
- The new field is added to the existing v0 endpoint; no migration is needed.
- TransactionNumber is only populated for adjustments with a source transaction; otherwise it is null or omitted.
- Sellers can match TransactionNumber to internal shipping invoice numbers for July 2024 and later.
Recommended Actions
- →Update your finance API parser (e.g., in your SDK or custom code) to read the TransactionNumber field from AdjustmentItem objects returned by GET /...
- →Add a lookup step in your data pipeline that queries your shipping/invoice database for matching TransactionNumber values and tags records as verif...
- →Modify monthly profit‑and‑loss reports (e.g., in Excel or BI tool) to include a TransactionNumber column for each adjustment.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!