Overview

This guide outlines the data specifications and implementation steps required to support transaction monitoring & sanctions screening for regulatory compliance.

1. Engagement and Setup

Initial Engagement
We will provide detailed implementation documentation that includes:

• File specifications
• Transaction templates
• Testing requirements
• Error handling procedures

These documents are designed to help your team prepare and validate the required data feeds.

2. File Specification Requirements

File Format

Type: CSV
Delimiter: Pipe (|)
Encoding: UTF-8
Header Row: Required

File Naming Convention

All files must follow a standardized naming convention to ensure consistency and facilitate automated ingestion and validation.

Format

CLIENTACRONYM_ENVIRONMENT_ENTITY_YYYYMMDD.csv

Components

• CLIENTACRONYM: Four-letter client identifier (provided by us).
• ENVIRONMENT:
  • T for Test

  • P for Production

• ENTITY: Type of data contained in the file (e.g., ACCOUNT, TRANSACTION, PERSON, etc.).
• YYYYMMDD: Date the file was created, representing the activity window (typically the previous calendar day).

Control Files

Each data file must be accompanied by a corresponding control file with the same naming convention, appending CONTROL to the entity name.
Control files must include:

• Record count of the associated data file.
  Record count of the associated data file.
  Format:
  CLIENTACRONYM_ENVIRONMENT_ENTITYCONTROL_YYYYMMDD.csv
  Examples
• Test Data File: ABCD_T_ACCOUNT_20240910.csv
• Test Control File: ABCD_T_ACCOUNTCONTROL_20240910.csv
• Production Data File: ABCD_P_ACCOUNT_20240910.csv
• Production Control File: ABCD_P_ACCOUNTCONTROL_20240910.csv

Delivery Cadence

Test Files

• Purpose: Used during implementation for integration testing.
• Frequency: Delivered as needed.
• Timing: No strict delivery time; coordination will occur between client and implementation team.

Production Files

• Frequency: Delivered daily, including weekends, and holidays are optional.
• Timing: Must be delivered prior to 9:00 AM EST each calendar day.
• Content Window: Each file must reflect activity from 12:00 AM to 11:59 PM EST of the previous calendar day.
• Zero-Activity Days: Files must still be delivered even if no activity occurred during the reporting window.

3. Kickoff Call

We’ll schedule a kickoff call to:

• Overview
• Outline the goals and objectives of the implementation.
• Align on timelines for milestones and key deliverables. (e.g. submission of test files and production files.)
• Data
• Client Data Review
• Relationship between the accounts, cards, and transactions.  
• File Specifications
• Provide an overview of the bank's data file specifications.

4. Path to Production

Sign-Off Before Implementation

A formal sign-off is required to confirm alignment before implementation begins.