Overview

The ETAS Batch File Integration enables clients to securely transmit business and transaction data to the Newline DataMart. This integration supports reporting, reconciliation, operational oversight, and regulatory monitoring requirements associated with the ETAS program. Unlike the API Integration, which is used to initiate payments, the Batch File Integration focuses on the secure exchange of data files through SFTP.

As discussed during onboarding planning, ETAS uses a simplified file integration model that centers on two primary file types:

Business File
Transaction File

This streamlined approach reduces implementation complexity compared to broader EDAS implementations.

Before You Begin

Before starting the Batch File Integration, confirm that:

ETAS onboarding has been initiated.
Technical contacts have been identified.
SFTP access has been requested.
Internal data sources have been identified.
File generation capabilities have been established.
Data owners have reviewed file specifications.

Integration Workflow

A typical Batch File implementation follows this sequence:

Step 1: Configure SFTP Connectivity: Establish secure file transfer access.

Step 2: Build Required Files: Generate Business and Transaction files according to the ETAS specifications.

Step 3: Validate File Structure: Confirm formatting and data quality requirements.

Step 4: Submit Test Files: Transmit sample files to the testing environment.

Step 5: Complete Reconciliation Testing: Validate processing results and reporting outputs.

Step 6: Production Deployment: Transition to production file delivery schedules.

SFTP Setup

Secure File Transfer Protocol (SFTP) is the standard method used to exchange ETAS data files with the Newline DataMart. The same SFTP onboarding approach currently used for existing Newline file integrations applies to ETAS.

Prerequisites

Before configuration:

Receive SFTP connection details.
Identify authorized users.
Configure secure network access.
Establish file encryption and storage procedures.
Review organizational security requirements.

SFTP Configuration

Implementation activities typically include:

Creating SFTP connections.
Configuring authentication credentials.
Testing connectivity.
Establishing folder structures.
Verifying upload and download capabilities.

Validation Checklist

Confirm that you can:

Connect successfully to the SFTP environment.
Upload files.
Download response files.
Access designated directories.
Handle connectivity failures appropriately.

Required Data Files

ETAS currently requires two primary file submissions into the Newline DataMart environment.

Business File

The Business File contains information about the businesses participating in the ETAS program. This file supports:

Operational oversight
Reporting
Customer identification processes
Regulatory monitoring activities

Typical Content

Examples may include:

Business identifiers
Business names
Company information
Program participation details
Status information

Field-level requirements are documented in the Business File Specification.

Implementation Tasks

Map internal business records.
Build export processes.
Validate file formatting.
Perform test uploads.
Review processing results.

Transaction File

The Transaction File contains payment activity generated through the ETAS program. This file supports:

Reporting
Reconciliation
Operational monitoring
Transaction oversight

Typical Content

Examples may include:

Transaction identifiers
Payment types
Amounts
Dates and timestamps
Status information
Associated business identifiers

Field-level requirements are documented in the Transaction File Specification.

Implementation Tasks

Map transaction sources.
Build extraction processes.
Validate transaction integrity.
Test file delivery.
Review validation results.

File Validation

Before files can be processed successfully, clients should validate:

File Format

Correct file type
Proper delimiters
Expected column structure
Required fields present

Data Quality

Accurate values
Complete records
Valid identifiers
Proper formatting conventions

Completeness

Required records included
No duplicate submissions
Scheduled deliveries completed

Clients are responsible for maintaining data quality within files submitted to ETAS.

Testing

All Batch File implementations must successfully complete testing before production approval is granted.

Connectivity Testing

Validate:

SFTP access
Authentication
File uploads
File downloads
Directory access

File Validation Testing

Validate:

File structure
Required field population
Data formatting
Error handling processes

Processing Testing

Validate:

Successful file ingestion
Expected processing outcomes
Response file handling
Issue remediation procedures

Reconciliation Testing

Verify that:

Transaction totals balance correctly.
Business counts match source systems.
DataMart outputs align with submitted files.
Ledger balances reconcile appropriately.
Reporting outputs are accurate.

User Acceptance Testing (UAT)

Prior to approval, clients should confirm:

Required files are generated correctly.
Delivery schedules are functioning as expected.
Operational procedures are documented.
Internal teams are prepared to support production processing.

Production Readiness

Before go-live:

Connectivity

SFTP access validated
Authentication verified
Folder structure confirmed

File Delivery

Business File tested
Transaction File tested
Scheduling confirmed
Monitoring established

Reconciliation

Balancing procedures documented
Reporting validated
Exception management processes defined

Operations

Support contacts identified
Escalation procedures documented
Production schedules approved

Support

Your implementation team will support the Batch File Integration throughout onboarding and testing. ETAS implementations commonly include walkthroughs of file specifications, SFTP requirements, validation processes, and reconciliation expectations.

Support During Implementation

Implementation support includes:

SFTP setup assistance
File specification reviews
Data mapping guidance
Validation troubleshooting
Testing coordination
Reconciliation reviews
Production readiness assessments

When to Contact Support

Contact your implementation team if:

SFTP connections cannot be established.
Files fail validation.
Required data elements are unclear.
Reconciliation discrepancies are identified.
Production delivery schedules require modification.

File Specifications

The following supporting documents should be reviewed during implementation:

Business File Specification

Contains:

Record layouts
Field definitions
Required fields
Formatting standards
Sample records

Transaction File Specification

Contains:

Transaction layouts
Field definitions
Payment reporting requirements
Formatting standards
Sample records Engineering teams frequently request downloadable spreadsheet-based file specifications and should reference these documents during development.

Next Steps

Once Batch File Integration activities have been completed:

Finalize reconciliation testing.
Complete user acceptance testing.
Obtain production approval.
Begin scheduled production file transmission.