Updated Transaction CSV

The Updated Transactions CSV shows changes made to existing transaction records after they are created, whether those changes occur before or after settlement.

Use this report to monitor transaction record changes rather than reconcile balances. It complements the Settled Transactions CSV by capturing updates that occur outside of settlement events.

Overview

Newline transaction CSV reports are event‑driven rather than timeline‑driven.
A transaction may appear in:

• Only the Settled Transactions CSV
• Only the Updated Transactions CSV
• Both reports
• Neither report

This depends on how the transaction progresses through its lifecycle and whether record‑level changes occur.

The Updated Transactions CSV focuses on changes to an existing transaction record, not settlement timing or new financial movements.

What the Updated Transactions CSV Represents

The Updated Transactions CSV captures material updates to an existing transaction record, including:

• Status changes prior to settlement
• Approved post‑settlement record changes that do not create a new transaction
• Corrections or adjustments to previously recorded data
• Metadata populated after creation or settlement

Each row reflects an update to an existing transaction record, not transaction creation, settlement, returns, or reversals.

When Records Appear

A transaction appears in the Updated Transactions CSV when a qualifying record‑level update occurs.

There is no settlement requirement:

• Updates may occur before settlement
• Updates may occur after settlement
• Some transactions may never settle but still appear here

A single transaction may appear multiple times if it undergoes multiple qualifying updates.

What Qualifies as an “Updated” Transaction

A transaction appears in the Updated Transactions CSV when any of the following occur:

Status changes prior to settlement

• Failed
• Rejected
• Canceled

Post‑settlement record updates

• Approved non‑financial corrections to the existing record
• Record‑level changes that do not result in a new transaction

Corrections

• Adjustments applied after initial processing

Metadata enrichment

• Fields that were unavailable earlier become populated

“Updated” refers strictly to record‑level data changes, not settlement events or new financial transactions.

Common Update Scenarios

Final Non‑Settled Outcomes

Some transactions reach a final state without settling, including:

• Failed transactions
• Rejected transactions
• Cancellations prior to settlement

These transactions do not appear in the Settled Transactions CSV but may appear in the Updated Transactions CSV if their status changes.

ACH‑Specific Updates

The Updated Transactions CSV captures ACH record updates that do not generate new transactions, including:

• ACH Notices of Change (NOCs)

NOCs appear here because they represent post‑settlement record corrections, not settlement events.

ACH returns are represented as new settled transactions and do not appear in this report.

Corrections and Metadata Changes

Additional update scenarios include:

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

Transfer Trace ID Field

Description

Transfer Trace ID is a transaction‑level identifier that supports traceability across transaction records and related lifecycle activity.

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 record update
• The transaction may appear in the Updated Transactions CSV when this field is populated or changed

Timing Expectations

• Updates are reported after the change is processed
• Reporting timing can vary based on when the underlying update is received and recorded

For example, updates may occur:

• On the same day as settlement
• Days later
• Weeks later (commonly for ACH Notices of Change or delayed metadata updates)

Settlement alone should not be assumed to represent the final state of a transaction record.

Relationship to the Settled Transactions CSV

Important distinctions:

• A transaction may appear in Updated Transactions without appearing in Settled Transactions
• Returns and reversals appear only as new settled transactions, not as updates
• Record order does not necessarily align with settlement timing

When to Use the Updated Transactions CSV

Use this report if you need to:

• Monitor transaction record changes
• Track status changes for non‑settled transactions
• Capture ACH Notices of Change (NOCs)
• Identify corrections or late‑populated metadata
• Maintain transaction record lineage

Do NOT use this report to:

• Detect returns or reversals
• Perform bank statement reconciliation
• Support balance tie‑outs
• Confirm settlement completion
• Align settlement amounts or dates

Summary

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

• It reflects record‑level updates, not settlement or new financial transactions

• Transactions may appear multiple times as updates occur

• Returns and reversals do not appear in this report and are represented as separate settled transactions

Use this report alongside other transaction reports based on your specific visibility and processing needs.