CSV Reporting: Settled vs Updated Transactions

Use this guide to choose the correct transaction CSV report for reconciliation, posted transaction visibility, or transaction lifecycle monitoring.

Newline provides multiple CSV reports because settlement completion and transaction record updates are separate events. Settled Transactions and Updated Transactions reports show different parts of a transaction lifecycle.

Overview

Newline transaction CSV reports are event‑driven, not timeline‑driven.
A single transaction may appear in one report, both reports, or neither report, depending on its lifecycle events.

• Settled Transactions CSV focuses on settlement completion.
• Updated Transactions CSV focuses on material changes to an existing transaction record, including status changes or late‑populated fields. It does not include returns or reversals, which are recorded as new settled transactions.

Use the report that matches your workflow. For example, use Settled Transactions for reconciliation‑related processes and Updated Transactions for lifecycle monitoring.

Settled Transactions CSV

What It Represents

The Settled Transactions CSV provides visibility into transactions that have completed settlement.

A transaction appears in this report when settlement is finalized.

When Records Appear

• At settlement completion only.

Common Use Cases

• Reconciliation workflows.
• Posted transaction visibility.
• Balance alignment preparation.

What It Does Not Include

• Failed or canceled transactions.
• Post‑settlement metadata updates to an already‑settled transaction.
• Corrections or metadata changes applied to an existing transaction record.

Updated Transactions CSV

What It Represents

The Updated Transactions CSV provides visibility into meaningful changes made to an existing transaction record after it has been created, regardless of whether settlement occurred.

This includes material record‑level changes such as status updates, corrections, or newly populated fields. It does not include returns or reversals, which are represented as separate settled transactions.

In this report, “updated” refers to changed transaction data on the original record, not settlement timing or new financial movements.

What Qualifies as an “Updated” Transaction

A transaction appears in the Updated Transactions CSV when:

• Its status changes before settlement, including failure or cancellation.
• Approved post‑settlement record changes occur that do not create a new transaction.
• Corrections are applied to the existing transaction record.
• Fields that were previously unavailable are populated.

A transaction may appear multiple times if it undergoes multiple meaningful updates.

Key Differences Between Reports

Report behavior:

• A transaction may appear in Updated Transactions without appearing in Settled Transactions.
• Updated Transactions may include final pre‑settlement outcomes, such as failures or cancellations, but not returns or reversals.
• Records may not follow chronological settlement order.

Common Update Scenarios

Final Non‑Settled Outcomes

• Failed transactions.
• Rejected transactions.
• Cancellations before settlement.

These transactions do not appear in the Settled Transactions CSV but may appear in Updated Transactions.

ACH‑Specific Updates

• ACH Notices of Change (NOCs).

NOCs appear in Updated Transactions because they represent post‑settlement record corrections, not new settlement events.

ACH Returns, including R01–R85 return codes, are generated as new settled transactions and therefore appear in the Settled Transactions CSV, not the Updated Transactions CSV.

Corrections and Metadata Changes

• Corrections applied to an existing transaction record.
• Metadata populated after creation or settlement.

Transfer Trace ID Field

Description

Transfer Trace ID is a transaction‑level identifier used to trace the movement of funds across transaction lifecycle events.

Population Behavior

• The Transfer Trace ID may not be available at transaction creation or settlement.
• When it becomes available later, it is treated as a material update.
• The transaction will appear in the Updated Transactions CSV when this field is populated or changed.

This supports consistent traceability across returns, reversals, and other lifecycle events.

Timing Expectations

• Updates appear as soon as the change is processed.
• There is no fixed delay window.

Updates may occur:

• On the same day as settlement.
• Days later.
• Weeks later for ACH Notices of Change and other delayed record updates. ACH returns appear later as new settled transactions.

Settlement can precede later transaction-state changes.

When to Use Each Report

Report Comparison by Use Case

Scenario‑Based Guidance

Important Usage Notes

Do not use the Updated Transactions CSV for:

• Bank statement reconciliation.
• Daily balance tie‑outs.
• Posted‑date alignment.

Summary

• Settled Transactions CSV answers:
  Which transactions completed settlement, including returns and reversals as distinct transactions?

• Updated Transactions CSV answers:
  What changed on an existing transaction record?

Returns and reversals are not updates to an existing transaction. They are represented as new settled transactions and appear in the Settled Transactions CSV as distinct records.