Accounts (Prior Day) CSV Guide

Use the Accounts (Prior Day) CSV to understand end-of-day account balances derived from prior-day activity, including both settled balances and (when available) statement-aligned closing balances.

This report is designed for financial reporting, reconciliation workflows, and balance continuity tracking.

What This Report Represents

Each row represents the state of an account as of the prior reporting period.

The report includes:

Balances derived from prior-day settled transactions
Optional statement-aligned closing balance (when available)
Account-level metadata and identifiers

Key Question This Report Answers:

What were my account balances at the end of the prior day?

Balance Types in This Report

1. Settled Balance (Primary Calculation Method)

Balances are calculated from:

All settled transactions from the prior reporting period

This reflects:

Financial activity that completed settlement
The baseline end-of-day balance for operational tracking

2. Statement Closing Balance

Field Name
statement_closing_balance

Definition

End-of-day closing balance aligned to the bank statement posting window for the prior business day.

Data Type

Decimal (currency)
Typically USD unless otherwise specified

How It Is Calculated

Based on posted transactions from the prior business banking day
Not derived from the intraday settled stream

This means:

Settled balance ≠ statement_closing_balance
Posting determines final statement alignment

Timing Dependency:

This field depends on posted transaction data and bank posting cycles. As a result, availability may lag settlement-based balances and can impact overall report delivery timing.

Key Characteristics

Reflects the bank statement view of balances
Aligns with Fifth Third reporting and reconciliation workflows
May differ from settled balances due to timing differences

Behavior & Timing

Population Timing

Available after prior-day posting completes
Generated as part of Prior Day processing (midnight UTC batch)

Immutability

Once generated for a given day:
- Values are final and do not change
Updates occur only in rare correction scenarios

Weekend & Holiday Behavior

No posting occurs on bank-closed days
Therefore:
- statement_closing_balance remains unchanged
- Values persist from the last business day

Edge Cases

You may observe differences due to:

End-of-month posting adjustments
Holiday or weekend rollover timing
Settlement / posting mismatch (e.g., RTP on weekend settles but posts Monday)

Positioning vs Other Reports

This report is one part of the broader reporting model.

Intraday Accounts

Operational, real-time balances
Derived from intraday settled activity
Continuously updating

Prior Day Accounts (this report)

End-of-day balances
Derived from:
- Settled transactions (core)
- Posted transactions (statement_closing_balance)

Posted Transactions (Prior Day)

Statement-level activity
Represents what actually posted to the bank statement

When to Use Each

Use Case	Recommended Report
In-day monitoring	Intraday Accounts
End-of-day financial reporting	Prior Day Accounts
Statement reconciliation	Posted Transactions

File Behavior and Delivery

Delivery Characteristics

Delivered once daily
Generated at midnight UTC
Typically delivered within ~1 hour

Consistency Guarantees

Files are always delivered, even if no activity occurred
Header-only files are expected under low or no activity conditions

Special Consideration — Posted Transactions Dependency

If Posted Transactions reporting and the statement_closing_balance field are enabled, delivery timing may differ from the standard Prior Day schedule.

Because statement_closing_balance depends on bank posting cycles (which follow business-day processing), the report may be delivered by the end of the next calendar day rather than within the typical ~1 hour window.

This is expected behavior and ensures that balances align with finalized bank statement data.

Weekend / Holiday Behavior

Files still generated and delivered daily
Common outcomes:
- Header-only files
- Unchanged balances
- No new posting activity

Field-Level Expectations

Some rail-specific fields may be blank
Transaction-level detail is not included
This report reflects account state, not lifecycle events

Program Configuration & Availability

statement_closing_balance may not be available in all programs
Availability depends on:
- Program configuration
- Feature rollout status

Important:
If the column is not present, contact your Newline support team to confirm availability.

Ingestion & Reconciliation Guidance

Best Practices

Treat statement_closing_balance as:
- Authoritative end-of-day balance for statement reconciliation
Store by:
- Account ID
- Statement date

Recommended Processing Approach

Use idempotent ingestion
Do not overwrite historical values
Maintain a daily balance history

Interpreting Differences

If values differ between reports:

Intraday ≠ Prior Day → timing differences
Prior Day ≠ Posted → settlement vs posting differences

Example CSV

Populated Example

account_uid,available_balance,settled_balance,statement_closing_balance
ACC123,10500.25,10300.25,10275.25
ACC456,5000.00,5000.00,5000.00

Weekend / No-Change Example

account_uid,available_balance,settled_balance,statement_closing_balance

Explanation:

Header-only file
No settlement or posting activity occurred
This is expected behavior

FAQs

Why didn’t the statement_closing_balance change over the weekend?

Posting does not occur on bank-closed days, so the closing balance remains the same as the prior business day.

Why doesn’t this match my intraday balance?

Intraday balances include real-time settlement activity. The statement_closing_balance reflects only posted transactions at end-of-day.

Can this field appear later than settlement?

Yes. Posting may occur after settlement, sometimes on a different business day.

Is this available in Sandbox and Production?

Availability may vary by program and environment. Check with your support team.

What should I do if the column is missing?

Confirm whether your program has access to the statement_closing_balance feature. It may require enablement.

Key Takeaways

Prior Day Accounts provides end-of-day balances
statement_closing_balance aligns with bank statement posting
Settlement and posting are separate concepts
Weekend behavior is expected and predictable
The report supports reconciliation, not lifecycle tracking