Program Level Configuration Flags

Overview

CSV reports may include different columns depending on your program configuration and enabled features.

Not all columns are universally present across all programs. Some fields appear only when specific reporting capabilities are enabled. This behavior is expected and reflects how reporting is tailored to each program.

Additionally, certain columns are populated only when:

The payment rail supports that data
The transaction lifecycle has reached a stage where the data exists
The program configuration includes the associated reporting feature

As with other CSV behavior, reporting is event-driven, and field population depends on available data and lifecycle state.

Key Concept

Condition	Impact on CSV Output
Feature enabled	Related columns are included in the CSV
Feature not enabled	Columns may be absent entirely
Data not applicable	Column present, but value may be empty

This means:

Missing columns do not indicate an error
Differences between programs are expected
CSV schemas may vary across environments and configurations

Configuration-Driven Column Behavior

The following high-level behaviors describe how program-level configuration affects CSV output.

Posting Metadata

When posting-aligned reporting is enabled:

Columns such as statement_posted_at may appear
Posted Transactions reporting is available
Statement-aligned fields are included in applicable CSVs

These fields represent when a transaction appears on the bank statement, which may differ from settlement timing.

ACH Batch Details

When ACH batch-level reporting is enabled:

ACH-related fields such as batch_id may be included
Batch-level grouping data becomes available for applicable transactions

Important:

Not all ACH transactions include batch data
Received ACH entries may still have empty batch_id values when that data is not provided

Closing Balance Alignment

When statement-aligned balance reporting is enabled:

Fields such as net_usd_closing_balance or statement_closing_balance may be included
Accounts CSV includes a statement-aligned closing balance derived from posted transactions

As documented:

Settled balance and statement closing balance are calculated differently
Posting timing may affect when these values become available

Column Availability Matrix

The table below reflects high-level column availability behavior.

Column	CSVs	Availability
`transaction_id`	All transaction CSVs	Always present
`amount`	All transaction CSVs	Always present
`settled_at`	Settled Transactions	Always present when settled
`status`	Settled / Updated	Always present when applicable
`statement_posted_at`	Posted / Accounts / (some transaction CSVs)	Available when posting-enabled reporting is configured
`batch_id`	ACH-related CSV rows	Present if provided by ACH processing and configuration enabled
`statement_closing_balance` / `net_usd_closing_balance`	Accounts (Prior Day)	Available when statement-aligned balance reporting is enabled

Rail-Specific Interactions

Column availability also depends on the underlying payment rail.

ACH

Batch-related fields may appear when available
Some received transactions may not include batch metadata
NOCs appear in Updated Transactions CSV, not Settled

RTP / Instant Payments

Settlement-related fields are always present at completion
Posting-related fields depend on posting-enabled reporting
Weekend settlement may not immediately produce posting-aligned fields

Cross-Rail Behavior

Some fields are conditionally populated across all rails.

CSVs may contain:

Fully populated rows
Partially populated rows
Empty values for non-applicable fields

How This Affects CSV Structure

Unlike static schemas, CSV structure may vary based on:

Program configuration
Feature enablement
Reporting scope

This means:

New columns may appear when features are enabled
Column sets may differ across programs
Column order and naming remain consistent within a given configuration

Newline CSV reports are designed to support this flexibility while remaining consistent within each program's configuration.

Backwards Compatibility

Enabling additional reporting features may introduce new columns to CSV outputs.

To ensure compatibility:

CSV ingestion systems should not assume a fixed column set.

Systems should:

Accept additional columns without failure
Process known columns dynamically

This ensures that future reporting enhancements do not break existing integrations.

FAQs

Why doesn't my CSV include `statement_posted_at`?

This column is only available when posting-aligned reporting features are enabled for your program.

Why do other programs have more columns than mine?

Different programs may have different reporting configurations enabled, resulting in different column sets.

Why is `batch_id` missing or empty?

Batch data depends on ACH processing. Some transactions (especially received entries) may not include batch-level information.

Why is the closing balance field missing from my Accounts CSV?

Statement-aligned closing balances are only included when enabled for your program.

Can additional columns be enabled for my program?

Contact your Newline Specialist to review available reporting configuration options.