MODULE: PRO-CHEX. Implementation & Operational Guide

Transcription

1 MODULE: PRO-CHEX Implementation & Operational Guide

2 Table of Contents I. PRO-CHEX Module...3 A. PRO-CHEX Configuration Overview...3 I. Deployment Type...4 II. Deployment Type...4 III. Data Decision & Presenting Rules...4 IV. Notification Methods...4 B. PRO-CHEX Deployment Options...5 I. FI Matched Model Process Flow Chart...6 II. ACH Alert Matched Model Process Flow Chart...7 III. Third Party Data Center Process Flow...8 C. PRO-CHEX Data Formats...9 I. PRO-CHEX Daily Input Files...9 II. File Filtering Rules & Configuration Options III. PRO-CHEX Output Files IV. PRO-CHEX Custom File Exchange Options D. PRO-CHEX Image Retrieval E. Client Settings F. Accounts G. Client User Account Mapping H. Client User Access Rights II. Training A. PRO-CHEX Training Agenda I. General II. Process Flow III. Sample Files and File Format Specifications A. Supported Payment Files: B. Supported Exception Files: C. Supported Issuance Files: D. Supported Disposition Files: III. Appendix IV. Exhibits Page 2 of 32

3 I. PRO-CHEX Module PRO-CHEX protects account holders from fraudulent check activity. FIs nationwide use PRO-CHEX as their preferred Check Positive-Pay solution.pro-chex processes provide end-to-end automation, enabling FIs to provide Check positive pay services to all Clients efficiently and profitably. PRO-CHEX will work for any financial institution, regardless of size or processing scenario. PRO-CHEX doesn t require a financial institution to change processing systems, it is designed to enhance existing systems. ACH Alert s Fed Command connection enables FIs that don t receive their own in-clearing check file to use PRO-CHEX without the cost of involving their data center. PRO-CHEX boast an array of configurable options to meet the needs of the diverse group of FIs we service. This guide is designed to outline all the implementation and configuration options available today and the steps required to complete them. In addition, user documentation and information to aid in supporting day-to-day operational processing is provided with the goal of insuring a successful, efficient implementation and excellent on-going experience for our FIs customers and their Clients. The User guides for PRO-CHEX can be found in the Appendix. ACH Alert provides tools to help FIs sell PRO-CHEX to their Clients. They include: Client Sales Videos Client Training Videos Sample marketing collateral Service introduction letter Rack cards/statement stuffers/brochures Web banner, lobby signage, window signage Ask your Account Manager for details. A. PRO-CHEX CONFIGURATION OVERVIEW The PRO-CHEX module is highly configurable to help each financial institution define the experience for themselves and their Clients. A brief overview of each configuration option is summarized below. More details can be found in the PRO-CHEX Special Configuration Options portion of this guide. Product Name The default product name is PRO-CHEX, however, FIs that elect to brand the application can define their own product name to appear as the module name in the FI & Client portals. Issuance End of Day Each FI can specify a daily cut-off time/time zone for PRO-CHEX to prepare and make the Client issuance files available to the FI. Decision End of Day Each FI can specify a daily cut-off time/time zone for PRO-CHEX to prepare and make the disposition files available. All Pay/Return decisions are final at that time. Alert Methods and SMS text alerting is available. FIs may choose to allow one or both. The Client portal will display options for entry for whichever alert methods have been enabled for the FI. Alert Content The FI can specify the From and Reply To content of the alerts. Page 3 of 32

4 I. Deployment Type FI Matched ACH Alert Matched FIs that have systems available to reconcile issuance items to the checks being presented for payment. FIs that DO NOT have systems available to reconcile issuance items to the checks being presented for payment can allow PRO-CHEX to perform the reconcilement function. II. Deployment Type If the FI will match issued items to checks being presented for payment to create exceptions, the FI must use one of the supported issuance/exception/disposition file formats listed in the PRO-CHEX Output Files section and PRO-CHEX Data Formats section of this guide. The FI may also provide ACH Alert a sample file and file specifications for custom coding. If ACH Alert will reconcile issuance items to checks being presented for payment to create exceptions, PRO-CHEX requires one of the listed supported formatted files to match enrolled accounts. The supported file formats are listed in the PRO-CHEX Data Formats section of this guide. III. Data Decision & Presenting Rules Pay & Adjust Exception Reasons Return Reasons By default, PRO-CHEX will present Clients with a Pay button only. However, if FI s want to allow Clients to request an item serial number or amount be adjusted and paid, the system can be configured to provide an Adjust link where a pop-up appears to allow serial number and amount to be modified. PRO-CHEX comes with a standard list of exception reasons, which can be modified during configuration by the FI. PRO-CHEX comes standard with a list of return reasons supported by the Federal Reserve Bank. FI s may choose to modify the return reasons presented. IV. Notification Methods PRO-CHEX supports two (2) notification methods. SMS Text This section of the guide will outline information important to note about each method. a) notification capabilities are standard with PRO-CHEX. The Notification Delivery Report in the FI portal provides information for undeliverable s. notifications can be customized, inserting the FIs name as outlined in Exhibit 2: PRO-CHEX Branding Message Questionnaire. Page 4 of 32

5 b) SMS Text SMS text notifications are an option. FIs must decide during implementation if this is a notification method they want to make available to their Clients. There is an additional charge for each SMS text message and ACH Alert s agreement with our SMS gateway provider requires a pass-through agreement requirement from the carriers which can be found as a special in the ACH Alert Master Services Agreement executed when signing up for the service with ACH Alert. ACH Alert currently uses a shared short code for SMS text delivery. This is the number that will be displayed as the sender of a text message. The short code being displayed today is: NOTE: If the Client has ever opted out of receiving SMS text messages from another company that shares this short code, SMS test messages will not be delivered to the Client. ACH Alert reserves the right to change the short code without notice. The Notification Delivery Report within the FI portal will display any undelivered SMS text messages. B. PRO-CHEX DEPLOYMENT OPTIONS FI Matched ACH Alert Matched FIs that choose to reconcile issuance items to checks presented. A process flow diagram can be found at Error! Reference source not found.. FI s that are unable to reconcile issuance items to checks presented. A process flow diagram can be found at Error! Reference source not found.. Third Party Data Center FI s whose check in-clearing files are delivered to a third-party data center can take advantage of ACH Alert s access to the Federal Reserve and designate ACH Alert to receive a Supplemental MICR file on their behalf. A process flow diagram can be found at Error! Reference source not found.. Page 5 of 32

6 I. FI Matched Model Process Flow Chart Step Description 1 Customer enters Issuance data into PRO-CHEX either manually or uploading a file through the UI 2 PRO-CHEX Service Module generates an Issuance File 3 FIIT, which is installed at the FI, connects to the PRO-CHEX and downloads the Issuance File 4 FI generates an Exception File and uploads to PRO-CHEX via FIIT 5 PRO-CHEX reads the Exception File 6 PRO-CHEX sends ALERTs to the Customer 7 Customer makes pay/no pay decision via PRO-CHEX 8 At EOD, PRO-CHEX generates the Disposition File 9 At EOD, FIIT, which is installed at the FI, connects to the PRO-CHEX and downloads the Disposition File Page 6 of 32

7 II. ACH Alert Matched Model Process Flow Chart Step Description 1 Customer enters Issuance data into PRO-CHEX either manually or uploading a file through the UI 2 FI uploads a x9.37 file via FIIT, which is installed at the FI 3 PRO-CHEX generates an Exception File 4 PRO-CHEX sends ALERTs to the Customer 5 Customer makes pay/no pay decision via PRO-CHEX 6 OPTIONAL: At EOD, PRO-CHEX generates the Issuance and Disposition File 7 OPTIONAL: At EOD, FIIT, which is installed at the FI, connects to the PRO-CHEX and downloads the Issuance and Disposition File Page 7 of 32

8 III. Third Party Data Center Process Flow Step Description 1 ACH Alert makes a secure connection to the Fed via a Fed VPN Tunnel 2 ACH Alert downloads the Supplemental MICR File 3 ACH Alert generates 2 files: File 1: Unmatched Transactions and immediately destroys; File 2: Matching Transactions and sends to PRO-CHEX 4 PRO-CHEX generates an Exception File 5 PRO-CHEX sends ALERTs to the Customer 6 Customer makes pay/no pay decision via PRO-CHEX 7 OPTIONAL: At EOD, PRO-CHEX generates the Issuance and Disposition File 8 OPTIONAL: At EOD, FIIT, which is installed at the FI, connects to the PRO-CHEX and downloads the Issuance and Disposition File Page 8 of 32

9 C. PRO-CHEX DATA FORMATS ACH Alert Matching configured FI s: FI s who are configured for ACH Alert to do the exception matching, must send ACH Alert a daily payment file to compare against the clients issued items file to determine exception items. ACH Alert supports the following Transaction/Payment/Posting files containing all incoming transaction items for ACH Alert Matched Financial Institutions: Catalyst FIS Horizon export FIServ DNA X9.37 (ICL) ACH Alert s standard payment file Financial Institutions may also provide a custom transaction/payment/posting file format to be sent to ACH Alert through the applicable file transfer method. FI Matching configured FI s: Financial Institutions doing their own exception matching must determine exception items and send those exception items to ACH Alert via an exception file. Once this exception file has been received and processed, clients can make pay/return decisions. This exception file would be loaded daily via the applicable file transfer method. ACH Alert supports the following Exception files containing only exception items determined by the FI prior to sending to ACH Alert: Basic Exception File Template Finastra Phoenix Core Exception File Financial Institutions may also provide a custom exception file format to be sent to ACH Alert through the applicable file transfer method. Refer to your Implementation Project Manager for the content detail of each available file format. I. PRO-CHEX Daily Input Files The PRO-CHEX application requires one of the above listed file formats or a FI custom file to be loaded daily. FIIT will read the file and send relevant information to ACH Alert s MFT server. The daily file sent to ACH Alert depends on the FI s configuration of either FI Matching or ACH Alert matching. Instructions for FIs sending/receiving files via SFTP are as follows: Issuance File Pickup Location: cpp/download/issuance_files Issuance File Naming Convention: customizable based on format Disposition File Pickup Location: cpp/download/disposition_files Disposition File Naming Convention: customizable based on format Exception File Delivery Location: cpp/upload/exception_files Exception File Naming Convention: *.pgp (all incoming files must be PGP encrypted with ACH Alert's public key) Payment File Delivery Location: cpp/upload/ processing_files Payment File Naming Convention: *.pgp (all incoming files must be PGP encrypted with ACH Alert's public key) Page 9 of 32

10 II. File Filtering Rules & Configuration Options By default, FIIT or the PRO-CHEX hosted application reads the daily input file/files to capture check transactions for active, enrolled routing/account numbers. By default, PRO-CHEX will select transactions that match enrolled routing/account number combinations and will search for the account number. However, ACH Alert offers special configuration options in FIIT and PRO-CHEX host to support: Ignore Leading Zeros Ignore Routing Numbers when Matching This configuration option is used to ignore the zeros in front of an account number within an input file. This feature cannot be used if an FI has account numbers that legitimately start with a zero. This configuration option is used to ignore the routing numbers within transaction/payment/posting files. This feature would only be used when ACH Alert is doing the exception matching to determine exception items. a) EOD Cut-Off Time FIs can determine the daily Issuance File EOD time so issuance items submitted up until that time by the Client, can be used to build the Issuance files for delivery to the FI. The Issuance EOD time can be specified in hours, minutes and time zone. The Issuance EOD time is sometimes referred to as the Issuance cut-off time. Files loaded before the daily cut-off time generate issuance EOD files the same day. Files loaded after issuance cut-off time generate issuance EOD files the next business day. b) Return Handling The following exception reasons are standard in PRO-CHEX, however, FI s may choose to customize the list. Exception Reason Missing The exception reason present in the file does not exist in CP_EXCEPTION_REASON_TBL Issuance Already Used Check presented with a serial number previously presented Issuance Amount Check presented where amount of check differs from issue amount Mismatch Issuance Not Found Check presented where no issue item is found to match against Issuance Payee Mismatch Check presented where payee name differs from issue payee name Issuance Stopped Check presented with a serial number of an issued item marked with a stop status Issuance Voided Check presented with a serial number of an issue item marked with a void status Page 10 of 32

11 c) Holidays & Weekends If any of the dates above fall on a weekend or holiday, PRO-CHEX will automatically adjust to the next business day. ACH Alert observes the Fed holiday calendar, however, ACH Alert can support customized holiday calendars for an FI upon receipt of a change request. d) Input File Confirmation When an input file is received at the PRO-CHEX host, an confirmation is sent to the financial institution. Most FIs choose to setup a group address so multiple department can be advised. A second is sent once the input file has been successfully processed and there were no issues with the input file. NOTE: If the first is not received, there was probably an issue with file transmission. If the Processed is not received, there was probably an issue with the format of the input file. Page 11 of 32

12 e) File Load Failure Notification Invalid File s: To FI Users with Receive Alerts selected. Example: Duplicate File fails File Load Failure s: To ACH Alert admin users. Examples: Incorrectly formatted files loaded III. PRO-CHEX Output Files PRO-CHEX can be configured to create an EOD or disposition file at EOD to automate processing for pay/return decisions made by Clients. The FI can choose to use only the pay/return reports within PRO- CHEX or they can choose to receive a EOD/disposition file. Depending on the FI configuration, the daily EOD output files can include any the following: Issuance File Outstanding Issued Items File EOD Disposition File Details of each EOD file type and naming conventions are defined below and apply for all FIs regardless of the data exchange method. FIs that are exchanging data using the Direct Send method should note the following: Direct Send FIs must download from the following folder: /alert/download NOTE: FI s that choose file encryption should expect files to contain the standard naming convention plus the extension.pgp. a) Issuance File The issuance file represents a collection of check issuance information submitted by Clients through the Client portal. FI s may choose to receive one issuance file per account per Client or a combined issuance file that represents issuance files submitted by all Clients on all accounts. Issuance files that that have been system or Client approved prior to the Issuance EOD cut-off time are released no later than 10 minutes after the Issuance EOD cut-off time. ACH Alert supports the following Issuance file formats: Basic Issuance File FIS Horizon export Issuance File Finastra Phoenix Core Issuance File Outstanding Issued Items File Financial Institutions may also provide a custom Issuance file format for ACH Alert to send through the applicable file transfer method. Page 12 of 32

13 ACH Alert also offers a Custom Extract File of Issuance Data which is a configurable option per FI. If an FI is configured to receive this file, depending on the method of file transfer selected, the FI will receive a file containing all outstanding issuance data at decision end of day. If there is no new outstanding issuance data for a day, then this file will not be generated and sent to the FI. Refer to your Implementation Project Manager for the content detail of each available file format. b) Disposition File The disposition file contains pay/return decisions for check transactions that have been decisioned by the Client prior to the Decision EOD cutoff time. An FI can be configured to receive the EOD/Disposition file or can be configured to simply review the pay/return report offered within PRO-CHEX. ACH Alert supports the following Disposition File formats: Standard Disposition File 001 Standard Disposition File 002 Standard Disposition File 003 Financial Institutions may also provide a custom Disposition file format for ACH Alert to send through the applicable file transfer method. Refer to your Implementation Project Manager for the content detail of each available file format. c) EOD Process Confirmation At the FIs designated Decision EOD cut-off time, a processing job begins for each input file processed earlier. An confirmation is sent to the financial institution. Most FIs choose to setup a group address so multiple department can be advised. Page 13 of 32

14 IV. PRO-CHEX Custom File Exchange Options ACH Alert offers several other file input and output options to support FIs that want to automate the import or export of information from the PRO-CHEX system. The following import/export files are available upon receipt of a Change Request. Import File This section of the guide will outline the purpose of each file type, content and format. File Naming Convention prochexaccountnumber.txt Detail Records Field Number Description 1 Primary Routing Number 2 Routing Number 3 Account Number Example: , ,12345 Page 14 of 32

15 D. PRO-CHEX IMAGE RETRIEVAL Financial Institutions configured to present check images within the FI and Client Portals will need an image provider configured during implementation. FI s who will be loading a x9.37 file to ACH Alert will send those check images through that x9.37 file, therefore an image provider is not necessary in this case. ACH Alert supports the following image providers: Catalyst Image Provider JHA ImageCenter FISC Image Provider FiServ Director Image Provider Summit Financial Solutions check image interface Check Works ImageExplorer Enterprise ACH Alert Standard Image Provider (The FI s can write to ACH Alert s image specifications) Financial Institutions may also provide custom Image retrieval specifications for ACH Alert to write to the FI s image provider. E. CLIENT SETTINGS File Format Delimited Flat File Record Delimiter Pipe Null Record Indicator Blank record (nothing between pipes) File Name PRO-CHEX_ClientSettings.dat Column Name Data Type Max Digits Required? Description Client Code Character 100 Yes Unique identifier for the Client and will be used to relate accounts to a Client. Presentment Type Character 1 Yes E =Exceptions A = All Payee Positive Pay Character 1 Yes N=No Y=Yes F. ACCOUNTS File Format Delimited Flat File Record Delimiter Pipe Null Record Indicator Blank record (nothing between pipes) File Name PRO-CHEX_AccountLoad.dat Page 15 of 32

16 Column Name Data Type Max Digits Required? Description Client Code Character 100 Yes Unique identifier for the Client and will be used to relate accounts to a Client. Account # Character 17 Yes Account Name Character 30 Yes Bank Code Character 8 No Routing # Character 9 See Description Required only if FI uses more than one routing number. Alternate Billing Account Character 17 No Required only if FI wants to bill an account other than the account enrolled Alternate Billing Routing # Character 9 No Required only if FI wants to bill a routing# other than the routing# enrolled Setting Character 1 Yes P = Pay R=Return Notification Level Character 1 Yes A = Account T = Transaction G. CLIENT USER ACCOUNT MAPPING File Format Delimited Flat File Record Delimiter Pipe Null Record Indicator Blank record (nothing between pipes) File Name PRO-CHEX_ClientUserAccounts.dat Column Name Data Type Max Digits Required? Description Client Code Character 100 Yes Unique identifier for the Client and will be used to relate accounts to a Client. Account # Character 17 Yes User Name Character 30 Yes if Standard Security SSO ID Character 50 Yes, if SSO H. CLIENT USER ACCESS RIGHTS File Format Delimited Flat File Record Delimiter Pipe Null Record Indicator Blank record (nothing between pipes) File Name PRO-CHEX_UserAccessRights.dat Page 16 of 32

17 Column Name Client Code User Name SSO ID Access Right: Transaction History Access Right: Change Transaction Status Access Right: Load Issuance File Access Right: Manage Issuance File Templates Access Right: Manual Issue File Access Right: View Issuance File Status Data Type Characte r Characte r Characte r Characte r Characte r Characte r Characte r Characte r Characte r Max Digits Required? Description 100 Yes Unique identifier for the Client and will be used to relate accounts to a Client. 30 Yes, if Standard Security 50 Yes, if SSO 1 Yes Y = Yes N = No 1 Yes Y = Yes N = No 1 Yes Y = Yes N = No 1 Yes Y = Yes N = No 1 Yes Y = Yes N = No 1 Yes Y = Yes N = No II. Training ACH Alert s project manager can provide an agenda for each type of training. An example of the training services provided is outlined below. A. PRO-CHEX TRAINING AGENDA I. General Discuss purpose of PRO-CHEX Discuss how PRO-CHEX will integrate into process flow Review User Documentation for FI & Clients II. Process Flow PRO-CHEX compares every incoming check to issue items submitted by a Client. Transactions trigger an ALERT to the Client, requiring action to: Pay or Return a check Adjust serial number and amount if Pay & Adjust configuration elected Page 17 of 32

18 III. Sample Files and File Format Specifications The following sample files and format specifications are currently supported by ACH Alert: A. SUPPORTED PAYMENT FILES: ACH Alert s standard payment file sample: ACH Alert Standard Payment File Format specifications: Page 18 of 32

19 Catalyst Payment File sample: Catalyst File Format specifications: Page 19 of 32

20 FIS Horizon Export Payment File sample: FIS Horizon Export File Format specifications: Page 20 of 32

21 FiServ DNA Payment File sample: FiServ DNA File Format specifications: Page 21 of 32

22 B. SUPPORTED EXCEPTION FILES: ACH Alert s Basic Exception File sample: ACH Alert Basic Exception File Format specifications: Page 22 of 32

23 Finastra Phoenix Core Exception File sample: Finastra Phoenix Core Exception File Format specifications: Page 23 of 32

24 C. SUPPORTED ISSUANCE FILES: ACH Alert s Basic Issuance File sample: ACH Alert Basic Issuance File Format specifications: Page 24 of 32

25 FIS Horizon Export Issuance File sample: FIS Horizon Export Issuance File Format specifications: Page 25 of 32

26 Finastra Phoenix Core Issuance File sample: Finastra Phoenix Core Issuance File Format specifications: Page 26 of 32

27 ACH Alert s Basic Outstanding Issued Items Custom Extract File sample: ACH Alert Basic Outstanding Issued Items Custom Extract File Format specifications: Page 27 of 32

28 FIS Horizon Export Outstanding Issued Items Custom Extract File sample: FIS Horizon Export Outstanding Issued Items Custom Extract File Format specifications: Page 28 of 32

29 Finastra Phoenix Core Outstanding Issued Items Custom Extract File sample: Finastra Phoenix Core Outstanding Issued Items Custom Extract File format specifications: Page 29 of 32

30 D. SUPPORTED DISPOSITION FILES: Standard Disposition File 001 Standard Disposition File 002 Standard Disposition File 003 Page 30 of 32

31 III. Appendix Appendix A: Fraud Prevention HQ Implementation & Operational Guide Appendix B: Fraud Prevention HQ Guide for FI Users Appendix C: Fraud Prevention HQ Access Guide for Client Users Appendix D: Fraud Prevention HQ Guide for Client Admin Users Appendix E: Fraud Prevention HQ Guide for Client Users Appendix F: PRO-CHEX Guide for FI Users Appendix G: PRO-CHEX Guide for Client Users Appendix H: FIIT Implementation & Operational Guide and User Guide Appendix I: FIIT Installation Appendix J: FIIT Installing Java 8 and the Cryptographic Extensions Page 31 of 32

32 IV. Exhibits Exhibit 1: PRO-CHEX Implementation Questionnaire Exhibit 2: PRO-CHEX Branding Message Questionnaire Exhibit 3: PRO-CHEX Import Template Exhibit 4: Federal Reserve Bank Supplemental MICR File Exhibit 5: PRO-CHEX Video Questionnaire Page 32 of 32