Overview

The ETAS Batch File Integration supports the secure transfer of business and transaction data into the Newline DataMart environment. This guide provides implementation requirements, processing expectations, validation standards, and file submission procedures for organizations integrating with ETAS through batch file delivery.

The ETAS batch integration consists of two primary file types:

File Specifications

Detailed field-level specifications are maintained in the ETAS File Specs (Downloadable) reference documentation.

Business File Specification

Purpose

The Business File provides information about businesses participating in the Embedded Transaction Account Solution (ETAS) program.

This data is ingested into the Newline DataMart and supports:

• Customer identification
• Transaction-to-business association
• Operational reporting
• Reconciliation activities
• Regulatory monitoring
• Exception management
• Program oversight

The Business File should contain current and accurate information for all applicable businesses participating in the ETAS program.

File Requirements

Business Files must:

• Follow the approved file layout specification.
• Include all required fields.
• Adhere to approved formatting standards.
• Contain only valid business records.
• Be transmitted through the approved SFTP channel.
• Align with the requirements documented in the ETAS File Specs (Downloadable).

File Layout

Field definitions and technical specifications are maintained in the ETAS File Specs (Downloadable) document.

Typical business attributes include:

• Business ID
• Business Name
• DBA Name
• Tax Identification Number (TIN)
• Address Information
• Business Type
• Contact Information
• Status Information
• Beneficial Ownership Indicators
• Enrollment Information

Refer to the downloadable specification for complete field definitions, accepted values, lengths, formats, and conditional requirements.

Validation Requirements

Business Files should be validated prior to submission.

Required Fields

Verify that:

• All required fields are populated.
• Mandatory values are not null or blank.
• Required identifiers are properly formatted.

Data Integrity

Verify that:

• Business records are unique.
• Duplicate business identifiers do not exist.
• Status values are valid.
• Reference values comply with specification requirements.

Formatting Validation

Verify that:

• Date formats are valid.
• Field lengths fall within specification limits.
• File delimiters are consistent.
• Character encoding requirements are met.

Common Validation Errors

Examples include:

• Missing required fields
• Invalid business identifiers
• Invalid tax identifiers
• Duplicate business records
• Invalid country or state values
• Unsupported status values
• Formatting inconsistencies

Files containing validation errors should be corrected and resubmitted.

File Submission Process

Business Files should follow the process below:

1. Extract business data from the source system.
2. Generate the Business File.
3. Validate file structure and content.
4. Transmit the file through the approved SFTP channel.
5. Review processing and validation results.
6. Resolve any exceptions.
7. Complete reconciliation activities as required.

Transaction File Specification

Purpose

The Transaction File provides transaction-level activity associated with businesses enrolled in the ETAS program.

Transaction data supports:

• Transaction reporting
• Reconciliation activities
• Payment activity monitoring
• Exception management
• Operational oversight
• Regulatory reporting requirements

The Transaction File is one of the primary files required for ETAS batch integrations.

File Characteristics

Supported Payment Activity

Depending on the implementation, the Transaction File may contain:

• ACH transactions
• Wire transactions
• Book transfers

Only payment types supported by the implementation should be reported.

File Requirements

Transaction Files must:

• Follow the approved layout specification.
• Include all required fields.
• Represent the complete transaction population for the reporting period.
• Adhere to approved formatting standards.
• Be transmitted via the approved SFTP channel.
• Support reconciliation against source-system activity.

File Layout

The complete transaction data dictionary is maintained in the ETAS File Specs (Downloadable) document.

Typical transaction attributes include:

• Transaction ID
• Business ID
• Account Number
• Transaction Code
• Transaction Description
• Amount
• Debit/Credit Indicator
• Posting Date
• Available Date
• Payment Rail Information
• Network Reference Identifiers
• Status Information

Refer to the downloadable specification for complete field definitions, accepted values, conditional requirements, and sample records.

Validation Requirements

Transaction Files should be validated prior to submission.

Transaction Integrity

Verify that:

• Transaction identifiers are unique.
• Amounts are valid.
• Business references exist.
• Account references are valid.
• Payment rail values are supported.

Completeness

Verify that:

• All reportable transactions are included.
• Reporting periods are complete.
• Duplicate transaction records are not present.

Formatting Validation

Verify that:

• Date values are properly formatted.
• Field lengths meet specification requirements.
• Delimiters are correct.
• Headers match the approved file layout.

Common Validation Errors

Examples include:

• Missing transaction identifiers
• Duplicate transaction identifiers
• Missing business references
• Invalid payment rail values
• Invalid transaction codes
• Invalid date formats
• Invalid debit/credit indicators
• Missing required fields
• Invalid amount formats

Files should be corrected and resubmitted before production processing.

Reconciliation Requirements

Transaction Files support reconciliation between:

• Client source systems
• ETAS transaction activity
• Payment processing activity
• DataMart reporting outputs

Organizations should review:

• Transaction counts
• Debit and credit totals
• Exception transactions
• Failed transactions
• Returned transactions
• Processing variances

Any discrepancies should be investigated and resolved prior to production sign-off.

Transaction File Processing Flow

Transaction files should follow the standard processing lifecycle:

1. Extract transaction activity from source systems.
2. Generate transaction file output.
3. Validate record counts and file structure.
4. Upload files through SFTP.
5. Review processing results.
6. Perform reconciliation activities.
7. Resolve exceptions and resubmit when necessary.

File Transmission Requirements

Secure File Transfer

All ETAS batch files must be transmitted using the approved SFTP channel.

Transmission requirements include:

• Approved credentials
• Approved file naming conventions
• Approved directory structure
• Successful file delivery confirmation
• Adherence to onboarding configuration requirements

Refer to the SFTP Setup Guide for connectivity and authentication requirements.

Control Files

Where applicable, control files should be generated and transmitted alongside data files.

Control files may be used to:

• Validate record counts
• Verify successful delivery
• Support operational monitoring
• Assist reconciliation processes

Control file naming conventions and layouts are defined within the ETAS File Specs (Downloadable) document.

Support

For implementation assistance, contact your assigned implementation team.

Support is available for:

• Data mapping
• File specification questions
• Validation issues
• Testing support
• SFTP configuration
• Reconciliation discrepancies
• Production onboarding activities

Implementation teams will review file layouts, testing outcomes, validation results, and reconciliation activities throughout the ETAS onboarding process.