Settled Transaction CSV

Use the Settled Transactions CSV to confirm completed settlement events and when those records appear.

This report shows settlement outcomes for reconciliation workflows. This guide explains what the Settled Transactions CSV represents, when records appear, how to use it, and how it differs from other transaction reports.

Important Note: Each record represents an individual settled event. Related transactions (e.g., original settlement, return, or reversal) may appear as separate records and must be correlated externally.

Overview

Newline CSV reports are event-driven, not cumulative timelines.
The Settled Transactions CSV captures settlement events.

Each settled transaction appears as a separate record at the moment settlement is finalized.
If a transaction never settles, it will not appear in this report.

Returns and reversals are represented as distinct settled transactions, separate from the original transaction.

Use the Settled Transactions CSV alongside other reports, such as Updated Transactions, because each report serves a different purpose.

What the Settled Transactions CSV Represents

The Settled Transactions CSV includes transactions that have:

• Completed settlement
• Resulted in finalized funds movement
• Passed all required processing checks for settlement eligibility

Each row represents a single settlement event.
This includes original transactions and any resulting returns or reversals, which appear as their own settled records.

When Records Appear

A transaction appears in the Settled Transactions CSV:

• When settlement is finalized
• Once per settlement event

If a return or reversal occurs, it appears as a new record when that return or reversal settles.

Settlement timing may vary depending on payment method, network, or processing window, but records appear only after settlement has completed.

Common Use Cases

Use the Settled Transactions CSV when you need to:

• Identify transactions that have completed settlement
• Identify settled returns or reversals as separate financial movements
• Prepare data for reconciliation workflows
• Align with downstream accounting or reporting systems that require settlement-finalized data

What the Settled Transactions CSV Does Not Include

The Settled Transactions CSV does not include:

• Failed transactions
• Rejected or canceled transactions
• Transactions that never reached settlement
• Corrections or metadata updates applied to an existing transaction record
• Lifecycle updates that do not result in a new settlement event

Record-level changes after settlement are reflected in other reporting, not by modifying records in this file.

Relationship to Other Transaction Reports

The Settled Transactions CSV focuses on settlement events only.
Other reports capture changes that occur outside of settlement.

The table below compares this report with Updated Transactions.

Important behaviors to understand:

• Some transactions appear in Updated Transactions but never appear in Settled Transactions
• Returns and reversals appear only as new settled records, not as updates
• Settlement does not represent the end of all possible transaction activity

Settlement and Finality

Settlement indicates that funds movement for a transaction has been completed.

In some cases (such as ACH), additional financial movements may occur after the original settlement.
When this happens, those movements (for example, returns or reversals) generate new settled transactions and appear as separate records in this report.

Timing Expectations

• Settlement timing depends on payment method and processing rules
• Records appear as soon as settlement is finalized
• There is no fixed settlement schedule across all transaction types

Use this report to confirm settlement for the transactions included, but do not use it to infer the status of transactions that are absent.

When to Use the Settled Transactions CSV

Use this report if you need to:

• Confirm settlement completion
• Identify settled returns or reversals
• Prepare reconciliation-ready settlement data
• Support accounting or financial reporting based on completed funds movement

Do NOT use this report to:

• Monitor transaction lifecycle changes
• Detect transaction failures
• Track corrections or metadata updates
• Perform end-to-end lifecycle monitoring

Summary

• Use this report to identify settlement events
• Each record represents a completed settlement, including returns and reversals as distinct transactions
• The file is event-driven and does not change after records are written
• Use it alongside other reports when broader transaction lifecycle visibility is required