Search

reasonautomation.com

Transactions (New)
Transactions (New)

Transactions (New)

icon
Table Name: transactions
⚠️ Migration in progress — transactions replaces transaction_standard_orders and transaction_invoiced. Legacy tables will be retired on June 15, 2026. See the Migration Guide for full details.

The Transactions table is a ledger style view that gives details on every financial transaction that occurs in Seller Central. It includes deferred transactions, and fee details by order.

This structure makes it easier to work with programmatically, eliminates custom column mappings per marketplace, and provides unique transaction identifiers that were not available in the legacy reports.

Business questions & scenarios

What is this data useful for?

  • Revenue & fee reconciliation: Break down each transaction into its component charge types — product sales, FBA fees, shipping, taxes, promotions, and reimbursements — using the breakdown_type column.
  • Settlement tie-out: Use settlement_id and financial_event_group_id to reconcile transactions against your settlement report.
  • Deferred payment tracking: Identify which transactions are pending payment vs. released, and avoid double-counting B2B invoiced orders.
  • Refund & returns analysis: Filter to transaction_type = 'Refund' to analyze return patterns by ASIN or marketplace.

Schema & update details

UI Report path
N/A
Amazon update frequency
Daily, with ~24-hour latency
Reason update frequency
Daily
Time Zone
date_time in PST · maturity_date in UTC
Granularity
1 row per _partneruuid ×transaction_id × breakdown_type× item_index

Historical data & change management

History available from Amazon
2 years
Reason lookback period
30 days

Data dictionary: fields in this table

Table & data nuances

  • Deferred transactions appear twice: When a transaction is deferred, Amazon sends it once at order time (DEFERRED) and again when payment releases. Filter using deferred_transaction_id IS NULL to avoid double-counting. See the How to Query section below.
  • Timezone split: date_time is in PST; maturity_date is in UTC. Keep this in mind when joining or aggregating across date fields.

How to query this table

Use the deferred_transaction_id filter to control how deferred transactions are handled. Two common patterns:

Use Case 1 — All sales and costs (deferred status doesn't matter):

select
    date_time::date as date,
    transaction_id,
    asin,
    item_description,
    transaction_type,
    breakdown_type,
    breakdown_amount,
    currency,
    marketplace_name,
    fulfillment_network
from public.transactions
where transaction_type = 'Shipment'
    and deferred_transaction_id is null
    and date_time >= '2025-01-01'
order by date_time desc

Use Case 2 — Only transactions that have been paid:

select
    date_time::date as date,
    transaction_id,
    asin,
    breakdown_type,
    breakdown_amount,
    settlement_id
from public.transactions
where transaction_status in ('Released', 'DEFERRED_RELEASED')
    and deferred_transaction_id is null
    and date_time >= '2025-01-01'
order by date_time desc

Net revenue by ASIN (current month):

image