Incoming Shared Archive File Processing
Incoming files with names ending in the following shared archive file extensions are processed as shared archive ECP, ECPF, and ECPI files. The main difference between ECP and ECPF files is the ECPF files contain image view records and the ECP files do not. The ECPI files are similar to ECPF files but contain the images as well.
| End of File Name | Transmission Type |
|---|---|
| .ISIX.ECP | SA_ECP |
| .ISIX.ECPF | SA_ECPF |
| .ISIX.ECPI | SA_ECPI |
The image view records (type 50, type 52, and type 54) present in ECPF files do not contain image data. In particular, the ECPF image view detail field 21.2 (image indicator) is a 0 (zero) (image view not present). The fields in these type 50 and type 52 records adhere to X9.37–2003 Annex E, image record definition for image view not present.
The Gateway Server incoming file route capability now allows routing these files differently. To accommodate this, SA_ECP, SA_ECPF, and SA_ECPI are valid fileType attributes. This allows the bank to send ECP files to one receiving point and process ECPF or ECPI files.
- Business day identifier
- X9.37 file name
- Cash letter identifier
- 3-character capture bank identifier
- 3-character paying bank identifier
- 8 MICR fields
- Capture date (set from this item’s bundle creation date)
- Capture bank sequence number (the item sequence number assigned by the originating institution)
The missing image criteria is modified for items in a shared archive file. Item images in a shared archive ECP or ECPF file are missing when field 10.9, document type indicator in the type 25 record is K (no image provided, no paper provided).