CSV Delivery Windows & SLA Details

Overview

This section defines when CSV reports are generated, when they are delivered, and how timing behaves across:

• Intraday reporting
• Prior Day reporting
• Weekends and holidays
• Empty file delivery
• Daylight Savings Time (DST) transitions

Newline CSV reporting is designed to be consistent, predictable, and automation-friendly, independent of transaction volume.

Prior Day Processing Window

Prior Day reporting is generated as part of a daily batch process.

• Prior Day processing begins after the close of the prior reporting period
• Reports are generated during the nightly processing window (midnight UTC batch)
• Generation is event-driven but not volume-dependent

This means:

• Files are generated even if no new transactions occurred
• Report generation timing does not depend on activity levels

Delivery Timeline

Prior Day Reports

Reports are generated shortly after midnight UTC as part of the daily batch process.

Delivery occurs within a consistent, predictable window following generation.

Expected behavior:

• Delivery timing is stable and repeatable

Minor variation may occur due to:

• System processing load
• MFT (Sterling) delivery timing

Clients should:

• Use delivery timing as a reliable anchor for downstream processing jobs
• Monitor for missing files, not delayed files within the normal window

Weekend & Holiday Behavior

CSV delivery continues regardless of banking activity:

• Files are still generated and delivered on weekends and holidays
• If no qualifying events occurred, files will be headers-only

Important distinctions:

• Settlement may occur on weekends (for example, RTP)
• Posting does not occur on bank-closed days

Implications:

• Posted Transactions CSV may show no changes on weekends
• Accounts statement_closing_balance remains unchanged until the next business day

Intraday Cadence Behavior

Intraday reporting operates on a client-defined cadence.

Clients must select a reporting interval during configuration.

Reports are generated at every interval, regardless of activity.

Behavior:

CSV files are delivered:

• On schedule
• Even when no new events occur

This results in:

• Predictable file delivery
• Frequent header-only files in low-activity periods

Newline CSV reporting is event-driven, meaning records appear only when lifecycle events occur.

Headers-Only File Behavior

A valid CSV file may contain:

• Only column headers
• No data rows

This occurs when:

• No settlement, update, or posting events occurred during the interval

This behavior:

• Is expected and correct
• Ensures consistent delivery for automation workflows

Header-only files allow systems to:

• Confirm successful delivery
• Maintain predictable ingestion timing

Daylight Savings Time (DST)

CSV generation and delivery are based on consistent system processing schedules, including UTC-based batch timing.

Implications for clients:

• Systems operating in local time zones may observe apparent shifts in delivery time during DST transitions
• Underlying generation logic and ordering of events does not change

Delivery Timeline Reference

Daily Flow (Simplified)

SLA & Delivery Expectations

Expected Behavior

Files are delivered:

• At every configured interval (Intraday)
• Once daily for Prior Day reports

Delivery is:

• Predictable
• Consistent
• Independent of transaction volume

Important Distinction

Escalation Guidance

Clients should contact support if:

• A scheduled file is not delivered
• File structure or headers are missing or malformed
• Delivery deviates significantly from expected timing

FAQs

When should I expect my Prior Day files?

Shortly after midnight UTC, following the prior day's processing window.

Why did my CSV arrive empty on a weekend?

Files are delivered regardless of activity. If no events occurred, the file will contain headers only.

Why does delivery time sometimes appear different?

This may occur due to:

• Daylight Savings Time adjustments
• Minor delivery timing variation

How does intraday cadence affect delivery?

Files are delivered at every configured interval, whether or not activity occurred.

What should I do if a file does not arrive?

Missing files (not empty files) should be investigated. Contact support if a scheduled file is not delivered.