Standard 015 Eng
Standard 015 Eng
STANDARD 015
COMPANION DOCUMENT TO THE ANSI X9.100-187-2008,
“Specifications for Electronic Exchange of Check and Image Data -
Domestic”
PART A – FORWARD PRESENTMENT
PART B – RETURNS
PART C – PROCEDURES SPECIFIC TO ICP IN CANADA
This Standard is copyrighted by the Canadian Payments Association. All rights reserved, including the right of reproduction in whole or in part,
without express written permission by the Canadian Payments Association.
By Publication of this standard, no position is taken with respect to the intellectual property rights of any person or entity. The CPA does not
assume any liability to any person or entity for compliance with this standard, including liability (which is denied) if compliance with the standard
infringes or is alleged to infringe the intellectual property rights of any person or entity.
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
Implemented
Amendments
1. Amendments to Record Type 10 and Record Type 20 to allow cash letters from multiple regions
to be included in one ICP file, and amendments to correct typos. Approved by the Board
February 13, 2014, effective April 7, 2014.
2. Amendments to ICP File Naming Convention to allow files transmitted from server or mainframe
platforms. Approved by the Board December 3, 2015, effective February 2, 2016.
3. Amendments to provide additional information around the file reject reason ‘invalid date’.
Approved by the Board April 7, 2016, effective June 6, 2016.
4. Amendments to provide clarification on the ECE institution. Approved by the Board June 18,
2020, effective, August 17, 2020.
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
Table of Contents
This document is intended to be an industry-specific companion document for the creation of image files
for exchange between CPA member Financial Institutions in Canada. This document is a complement to
the US standard ANSI X9.100-187-2008 “Specifications for Electronic Exchange of Check and Image
Data – Domestic”.
This document is not intended to replace the ANSI X.100-187-2008 standard for image delivery in
Canada. Rather, it is intended to provide clarification and substitutive information for the effective
adoption of ANSI X9.100-187-2008, for image exchange in Canada.
This document strictly provides the details for the Image Captured Payment File as it is proposed for
Inter-Member exchange in Canada. As such, the document makes no other assumptions concerning the
business use of the Image Captured Payments File. For example, business decisions not within the
scope of this document include, but are not limited to:
The decision to create and exchange an Image Captured Payment File, versus continuation of
traditional paper exchange via original paper Items, Clearing Replacement Documents (CRD), or
Return Replacement Documents (RRD).
The choice of application software used to create the Image Captured Payments File.
The choice of application software used ingest, parse, and process the Image Captured Payment
File, including both exchange gateway ‘receive’ systems and systems to create paper CRDs from
electronic files.
The use of an Image Captured Payment File for purposes other than Inter-Member exchange,
including regional capture, branch capture, corporate capture or other depository line-of-business
source capture.
The use of the Image Captured Payment File for image delivery between the U.S. and Canada.
The multiple tables labeled “ANSI X9.100-187-20xx Standard Record Fields Summary” that are used
throughout this document are reproduced with the permission of Accredited Standards Committee ASC
X9, Inc – Financial Industry Standards* from its standard ANS X9.100-187 “Specifications for Electronic
Exchange of Check and Image Data”. The dated version of the standard that applies to this document is
assumed. This document containing extracts from ASC X9 copyrighted materials is being made available
by the Canadian Payments Association (CPA) for general industry use with its Automated Clearing
Settlement System (ACSS) Rules and Standards, with the acknowledgement of ASC X9, Inc.
Copies of all ANSI X9 standards, technical reports or draft standards for trial use can be purchased from
X9 Online. Go to www.x9.org, click on X9 STANDARDS INFORMATION, then on Standards Store.
3 References
The following list of publications is part of the complete set of materials that may be needed for effective
use of this document:
ANSI X9.100-187-2008 “Specifications for Electronic Exchange of Check and Image Data –
Domestic” [Note: The ASC X9 standard referenced in this document represents the most recent
version of the standard at the time this document was originally published. It is the responsibility
of the user of this document to ensure that the most recently published version of the ASC X9
standard is used for reference purposes.]
CPA Rule A10 “Image Rule”
CPA Standard 006 “Specifications for MICR-Encoded Payment Items”
CPA Standard 012 “Image Security Standard”
CPA Standard 013 “Return Replacement Document Design Standard”
CPA Standard 014 “Clearing Replacement Document Design Standard”
Parts A and B of this document provide the technical specifications for the Image Captured Payment File
in Canada, based upon the technical specification for the image exchange file as detailed in the ANSI
X9.100-187-2008 standard.
Each section on each of the record types in the ANSI X9.100-187-2008 standard is specifically addressed
in this document. The sections within Parts A and B are numbered according to the convention and
numbering scheme used in the original ANSI X9.100-187-2008 standard. This facilitates easy reference
between this document and the corresponding section in the original ANSI X9.100-187-2008 standard.
For consistency with the ANSI X9.100-187-2008 standard, the language in the Parts A and B of this
document retains the U.S. spelling conventions, and will be available in English only.
Parts A and B of this document contain one section for each of the record types in the original ANSI
X9.100-187-2008 standard. If a specific record is not relevant for the file in Canada, then the respective
section is still included in this document, but is noted as not being applicable.
The narrative is the description of the specific record type as it appears in the ANSI X9.100-187-2008
standard, with the appropriate modifications and exclusions to tailor and restrict the content to the
requirement for Image Captured Payments in Canada.
The summary table is a copy of the summary data table for the respective record fields from the parent
ANSI X9.100-187-2008 standard. It is reproduced in this document for expedient visual reference. Refer
to Accredited Standards Committee (ASC) X9, Inc. - Permission for Reproduction in section 2.0 of
this document.
In this section, each field within the respective record type is presented in detail. The field descriptors
provide the following information:
Content that is specific to file delivery in Canada. This content takes precedence over the
specification in the ANSI X9.100-187-2008 Standard.
Fields that have significance for general image exchange in the ANSI X9.100-187-2008 Standard,
but have no special overriding content considerations for use in Canada.
Fields that have no special priority business value in either the US or Canada, and may optionally
be used or unused without core business impact.
Fields that have business use that is specific to facilitate exchange, clearing, and settlement via
the Automated Clearing and Settlement System (ACSS) for which additional information is
provided in CPA Rule A10, “Image Rule”.
Each field within each record has an associated data type. The data type provides basic information as to
how that field is used and populated in the parent ANSI X9.100-187-2008 standard, and by comparison
how that same field is used and populated according to this companion document, for use in Image
Captured Payment Exchange in Canada.
o The record field has a creator-defined value that is recognized and acceptable within the
business context of the ANSI X9.100-187-2008 specification.
In the Companion Document specification:
The record field is Mandatory or Conditional;
When present (Mandatory) or if present (Conditional):
o The record field has a creator-defined value, including blanks, that is recognized and
acceptable within the business context of the Companion Document specification.
o The record field has a creator-defined value, including blanks, that has business context
significance to the creator of the record, or to the consumer of the record, or to both.
X9 Annex C > Relationship of Cash Letter Record Type Indicator and Cash Letter Documentation Type
Indicator ......................................................................................................................................... 73
X9 Annex D > Image Record Definition for Image View Not Present .................................................... 73
X9 Annex E > Variable Length Record File ............................................................................................ 73
X9 Annex F > Image Record Definitions ................................................................................................ 73
X9 Annex G > Check Digit Calculation ................................................................................................... 74
X9 Annex H > Examples of Electronic Exchange File Structures .......................................................... 74
X9 Annex I > Image Keys ..................................................................................................................... 75
X9 Annex J > Endorsements ................................................................................................................. 75
X9 Annex K > Differences Between DSTU X9.37 and This Standard ................................................... 76
If Image View records are included in the file, the Check Detail Record shall always follow a Bundle
Header Record (Type 20) or an Image View Data Record (Type 52). If Image View records are omitted
from the file, the Check Detail Record shall always follow a Bundle Header Record (Type 20) or a
Mandatory Check Detail Addendum C Record (Type 28).
The data in Fields 2 through 6, and optionally field 7 for pre-encoded items, represent the various MICR
fields as extracted from the MICR line content of the cheque or other designated payment item. The order
of these fields is the order in which they normally physically appear on the cheque, as referenced in ANSI
X9.100-160-1 for MICR data placement. The data in the fields is created by, or on behalf of, the Direct
Clearer delivering the file, which is the ECE institution. The ECE institution is assumed to be or to
represent the Bank of First Deposit.
X9 Section > 10.4 Payor Bank Routing Number (combined with the following field)
X9 Section > 10.5 Payor Bank Routing Number Check Digit (combined with the
previous field)
Only one Check Detail Addendum A Record is permitted. It is used to identify the return location for the
cheque or payment item. The Check Detail Addendum A record may be present at the discretion of the
delivering Direct Clearer, or the Bank of First Deposit.
The Check Detail Addendum A Record follows its immediately preceding Check Detail Record (Type 25).
The data in the Check Detail Addendum A Record is transferred to the Return Addendum A Record (Type
32) when the item is returned by image. This record may be used to indicate the BOFD, or it may indicate
a third party Return Processing Financial Institution designated to process the Customer Return, if the
item associated with the preceding Check Detail Record (Type 25) is returned.
When the Return Processing Financial Institution indicated in the Check Detail Addendum A Record is
different from the BOFD, the BOFD information shall not be included in the Check Detail Addendum A
Record. In this case, the BOFD information, if known, shall be included in a Check Detail Addendum C
Record (Type 28), and is so indicated by setting the appropriate value in the Endorsing Bank Identifier -
Field 11 of that Check Detail Addendum C Record (Type 28).
One, and only one, truncator flag shall always be set to ‘Y’ per item. This is
inclusive of the Check Detail Addendum A Record (Type 26) and all Check
Detail Addendum C Records (Type 28).
The delivery of an Image Captured Payment file from one Direct Clearer to another can optionally be
completed without the transfer of the Image View records for the items, subject to a special clearing
arrangement.
Within the ANSI X9.100-187-2008 standard, the Check Detail Addendum B Record is intended to be a
mechanism to transfer an electronic image archive locator key for an item that is delivered without image
segments, for which the images can be separately extracted from the Archive store.
This Companion Document does not provide specifications or instructions as to how image access is
provided under such agreements. However, as the Check Detail Addendum B Record is within the base
ANSI X9.100-187-2008 standard, and is intended to assist in archival retrieval for non-image delivery, the
Check Detail Addendum B Record is presented as an optional facilitator for such special clearing
arrangements.
Data in each Check Detail Addendum B Record is transferred to a corresponding Return Addendum C
Record (Type 34) should the item be returned by image.
Standard 015
Page 41
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART A – FORWARD PRESENTMENT
Option 2: Field 2 = 1
One Check Detail Addendum C Record is Mandatory. The Mandatory Check Detail Addendum C Record
shall always be used with a Check Detail Record (Type 25), although others may also be present. The
Mandatory record is used to carry endorsement information identifying the delivering Direct Clearer as the
Financial Institution responsible for the delivery of the file to the exchange. The Mandatory Check Detail
Addendum C Record contains endorsement information that may not be present on the physical item.
If only one Check Detail Addendum C Record is present, then it shall be considered the Mandatory Check
Detail Addendum C Record. If more than one record is present, then the most recent record in
chronological order shall be considered the Mandatory Check Detail Addendum C Record.
Data in each Check Detail Addendum C Record is transferred to a corresponding Return Addendum D
Record (Type 35) should the item be returned by image.
The Direct Clearer identified in the Mandatory Check Detail Addendum C Record may or may not be the
BOFD. The BOFD may be another Financial Institution on whose behalf the Direct Clearer is providing
delivery to the exchange.
Standard 015
Page 43
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART A – FORWARD PRESENTMENT
Values:
In the Mandatory Check Detail Addendum C Record:
This field represents the Direct Clearer Financial Institution that is
responsible for delivery of the file to the clearings exchange.
In any Conditional Check Detail Addendum C Record:
This field represents a Financial Institution that handled the image
item within its automated process. This may be the delivering Direct
Clearer, or it may be a Financial Institution that is other than the
delivering Direct Clearer.
Standard 015
Page 45
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART A – FORWARD PRESENTMENT
For the Mandatory Check Detail Addendum C Record, the value shall be
identical to:
Cash Letter Header Record (Type 10)
Field 05 – Cash Letter Business Date
One, and only one, truncator flag shall always be set to ‘Y’ per item. This is
inclusive of the Check Detail Addendum A Record (Type 26) and all Check
Detail Addendum C Records (Type 28).
The following sections in the ANSI X9.100-187-2008 standard are not included in this Companion
Document. These sections provide the specifications for records that do not provide any business content
to ICP File delivery in Canada.
The electronic delivery of returned image items is not addressed in this Companion Document.
The electronic return by image is addressed in a separate Companion Document.
The Image View Detail Record and the Image View Data Record (Type 52) shall be used together to
convey an image view associated with the related Check Detail Record (Type 25). When an Image View
Detail Record (Type 50) is present, an Image View Data Record (Type 52) shall also be present.
Image segments related to the preceding Check Detail Record (Type 25) shall be ordered in the following
sequence:
1) front bitonal; 2) front greyscale (*optional); 3) back bitonal; 4) back greyscale. (*optional)
* Note: the exchange of greyscale images is optional as outlined in Operational Agreements between
Members.
Front and back image segments shall always be included on the file, unless omitted by a clearing
arrangement. Image segments shall either be included for all items in the file, or shall be omitted for all
items in the file. If image segments are omitted, then Image View Detail Records (Type 50) shall be
omitted from the file. If Image View Detail Records (Type 50) are omitted, then Cash Letter Record Type
Indicator - Field 08 in the Cash Letter Header Record (Type 10) shall have a defined value of ‘E’. Refer to
X9 Section > 12 Check Detail Addendum B Record (Type 27) for additional information on non-image
file transfer.
The image view is normally created by the Direct Clearer that is delivering the file. However, it may be
created by another Financial Institution, and it is then transferred to the Direct Clearer. The data fields
reflect the creator of the image view.
Standard 015
Page 51
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART A – FORWARD PRESENTMENT
The Image View Data Record and the Image View Detail Record (Type 52) shall be used together to
convey an image view associated with the related Check Detail Record (Type 25). When an Image View
Detail Record (Type 50) is present, an Image View Data Record (Type 52) shall also be present.
The Image View Data Record contains sixteen fixed length fields, and three variable length fields which
are optionally used. Only one of the variable length fields, Image Data – Field 19, is actually used and
shall be Mandatory when the Image View Data Record is present. The content of the field is always
variable.
The image view on the file delivered to the exchange is normally created by the delivering Direct Clearer.
An Image View Data Record may be created by another Financial Institution that creates the image
segment, and that Image View Data Record is then transferred to the Direct Clearer for delivery.
However, the data fields in the Image View Data Record that is delivered by the Direct Clearer reflect the
Direct Clearer.
Refer to X9 Section > 21 Image View Detail Record (Type 50) for considerations on the optional
omission of image segments from the file, the inclusion of various image segments on the file, and the
creator of the image segments.
Standard 015
Page 57
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART A – FORWARD PRESENTMENT
The following section in the ANSI X9.100-187-2008 standard is not included in this Companion
Document. The section provides the specifications for a record that does not provide any business
content to ICP File delivery in Canada.
If images are included in the file, the Bundle Control Record shall always follow an Image View Data
Record (Type 52). If images are omitted from the file, the Bundle Control Record shall always follow a
Mandatory Check Detail Addendum C Record (Type 28).
The Bundle Control Record shall be the last record of the bundle. The data in the fields is created by, or
on behalf of, the Direct Clearer delivering the file, which is the ECE institution.
The following sections in the ANSI X9.100-187-2008 standard are not included in this Companion
Document. The sections provide the specifications for records that do not provide any business content to
ICP File delivery in Canada.
The specifications for the field apply only to Check Detail Record (Type 25) – Field 05 ‘On-Us’.
The exchange agreement allows for the optional presence or absence of dash characters in the On-
Us Field, which is at the discretion of the file creator.
ANSI X9.100-187-2008 information does not apply to ICP File delivery in Canada.
Cash Letter Header Record (Type 10) – Field 08 ‘Cash Letter Record Type Indicator’ is restricted
to values ‘E’ and ’I’;
Cash Letter Header Record (Type 10) – Field 09 ‘Cash Letter Documentation Type Indicator’ is
limited to values ‘C’, ‘D’, ‘G’, ‘K’ and ‘L’.
X9 Annex D > Image Record Definition for Image View Not Present
ANSI X9.100-187-2008 information does not apply to ICP File delivery in Canada.
ANSI X9.100-187-2008 information does not apply to ICP File delivery in Canada.
Standard 015
Page 74
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART A – FORWARD PRESENTMENT
The check digit is present in Check Detail Record (Type 25) – Field 05 ‘Payor Bank Routing
Number Check Digit’ only when:
Field 04 ‘ Payor Bank Routing Number’ together with Field 05 ‘Payor Bank Routing
Number Check Digit’ contains a combined 9-character data format ‘AAAABBBBC’,
indicating a US ABA MICR Routing Number for a US currency ABA item.
The minimal structure of the file, based on the record types that are detailed in this document, is as
follows.
ANSI X9.100-187-2008 information does not normally apply to ICP File delivery in Canada.
For non-image file delivery, the description of the Image Archive Locator may be of some limited value.
ANSI X9.100-187-2008 information does not apply to ICP File delivery in Canada.
Standard 015
Page 76
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART A – FORWARD PRESENTMENT
This Companion Document provides detailed descriptions of the following record types:
File Header Record (Type 01)
Cash Letter Header Record (Type 10)
Bundle Header Record (Type 20)
Check Detail Record (Type 25)
Check Detail Addendum A Record (Type 26)
- Conditional record
Check Detail Addendum B Record (Type 27)
- Conditional record
- Possible restricted use for non-image files
Check Detail Addendum C Record (Type 28)
- Single Mandatory record
- Other Conditional record(s)
Image View Detail Record (Type 50)
- Mandatory record unless omitted by clearing arrangement
Image View Data Record (Type 52)
- Mandatory record unless omitted by clearing arrangement
Bundle Control Record (Type 70)
Cash Letter Control Record (Type 90)
File Control Record (Type 99)
Within each of the record types, only specific fields apply, and in some cases, only specific values
for certain record fields apply.
Standard 015
Page 77
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART B – RETURNS
6 PART B – RETURNS
The following sections in the ANSI X9.100-187-2008 standard are not included in this Companion
Document. These sections provide the specifications for records that do not provide any business content
to ICP Return File Delivery in Canada.
If Image View records are included in the file, the Return Record shall always follow a Bundle Header
Record (Type 20) or an Image View Data Record (Type 52). If Image View records are omitted from the
file, the Return Record shall always follow a Bundle Header Record (Type 20) or a Mandatory Return
Addendum D Record (Type 35).
X9 Section > 14.2 Payor Bank Routing Number (combined with the following field)
X9 Section > 14.3 Payor Bank Routing Number Check Digit (combined with the
previous field)
Companion Usage: Mandatory
Companion Data Type: Required
Companion Value: Field 04 combined with Field 05 comprises 9 consecutive characters.
In order to accommodate a ‘dash’ character separator, Field 04 type shall be
defined as:
ANSI X9.100-187-2008
Section 5.2.4 Numericblank/special MICR (NBSM).
Refer to Table 3 for format and content of the combined field values.
For items presented electronically, this may contain a value that is different
from the incoming Check Detail Record (Type 25) Field 04 Payor Bank
Routing Number with Field 05 Check Digit. The paying Financial Institution or
its processing agent, at its discretion, may have replaced, augmented,
modified or corrected the originally received value to meet its proprietary
requirements.
The Return Addendum A Record follows its immediately preceding Return Record (Type 31). The Return
Addendum A Record shall be used to indicate the Financial Institution designated to receive and process
the return of the item associated with the preceding Return Record (Type 31). The Return Processing
Bank may or may not be the BOFD. The Financial Institution that is indicated as the Return Processing
Bank shall be responsible for the proper disposition of the image return upon receipt.
If the Forward item corresponding to this return was originally presented by image and a Check Detail
Addendum A Record (Type 26) was included, then the Return Addendum A Record shall contain the
same information from the corresponding Check Detail Addendum A Record (Type 26).
If the Forward item corresponding to this Return was originally presented by image, but there was no
Check Detail Addendum A Record (Type 26), then a Return Addendum A Record shall be created and
will contain information that is keyed from viewing areas on the Forward presented image.
If the Forward item corresponding to this Return was originally presented as paper, either in the form of
the original paper item or a paper substitution CRD, then the Return Addendum A Record shall be
created and will contain endorsement information that is keyed from viewing the surface of the original
physical item or its image following processing of the item.
Value:
The Routing Transit identifies the Financial Institution to which the
item in the preceding Return Record (Type 31) is being directed as a
return.
The Financial Institution may be:
The BOFD;
A Financial Institution other than the BOFD;
The Direct Clearer that delivered the original item to the
exchange;
A Financial Institution other than the original delivering Direct
Clearer.
Standard 015
Page 109
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART B – RETURNS
Only one Return Addendum B Record is permitted for a Return Record (Type 31). The Return Addendum
B Record shall always follow its immediately preceding Return Addendum A Record (Type 32).
The Return Addendum B Record is used to carry the Auxiliary On-Us MICR Field information that was
included in Check Detail Record (Type 25) for the original Forward presented item, that is now is now
associated with the preceding Return Record (Type 31).
The Forward item corresponding to this Return may have been presented by image, or it may have been
presented as paper, either in the form of the original paper item or a paper substitution CRD. The
Auxiliary On-Us MICR Field on a presented item is normally present, however it may have been absent,
in which case the Mandatory Return Addendum B Record shall still be included.
The delivery of an Image Captured Payment file from one Direct Clearer to another can optionally be
completed without the transfer of the Image View records for the returned items, subject to a special
clearing arrangement.
Within the ANSI X9.100-187-2008 standard, the Return Addendum C Record is intended to be a
mechanism to transfer an electronic image archive locator key for a returned item that is delivered without
image segments, for which the images can be separately extracted from the Archive store.
This Companion Document does not provide specifications or instructions as to how image access is
provided under such agreements. However, as the Return Addendum C Record is within the base ANSI
X9.100-187-2008 standard, and is intended to assist in archival retrieval for non-image delivery, the
Return Addendum C Record is presented as an optional facilitator for such special clearing
arrangements.
If the Forward item corresponding to this return was originally presented by ICP File without Image View
record pairs (Type 50/52), and a Check Detail Addendum B Record (Type 27) was included, then the
Return Addendum C Record shall contain the same information from the corresponding Check Detail
Addendum B Record (Type 27), even if the image segments are included in Image View record pairs
(Type 50/52) with the Return Record (Type 31).
If the Forward item corresponding to this Return was originally presented by ICP File with Image View
record pairs (Type 50/52), and therefore there was no Check Detail Addendum B Record (Type 27), and
the item is being returned by ICP File without Image View record pairs (Type 50/52), then a new Return
Addendum C Record may be included to provide the image archive locator key.
If the Forward item corresponding to this Return was originally presented as paper, either as the original
paper item or a paper substitution CRD, and the item is being returned by ICP File without Image View
record pairs (Type 50/52), then a new Return Addendum C Record may be included to provide the image
archive locator key.
Standard 015
Page 116
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART B – RETURNS
Option 2: Field 2 = 1
The Return Addendum D Record contains thirteen fields. It is one of four addendum type records
available that may be used with the Return Record (Type 31), three of which are Mandatory.
One Return Addendum D Record is Mandatory. A Mandatory Return Addendum D Record shall always
be used with a Return Record (Type 31). Only the Mandatory Check Detail Addendum C Record is
expected with a Return Record (Type 31), although others may be present. The Mandatory record is used
to carry endorsement information identifying the delivering Direct Clearer as the Financial Institution
responsible for the delivery of the file to the exchange.
If only one Return Addendum D Record is present, then it shall be considered the Mandatory Return
Addendum D Record. If more than one record is present, then the most recent record in chronological
order shall be considered the Mandatory Return Addendum D Record.
If the Forward item corresponding to this Return was originally presented by image, then one or more
Check Detail Addendum C Records (Type 28) were included, because at least one Check Detail
Addendum C Record (Type 28) was Mandatory. In this case, a Return Addendum D Record shall be
included for each Check Detail Addendum C Record (Type 28), and each shall contain the same
information from the corresponding Check Detail Addendum C Record (Type 28).
If the Forward item corresponding to this Return was originally presented as paper, either in the form of
the original paper item or a paper substitution CRD, then a Mandatory Return Addendum D Record shall
still be included.
Standard 015
Page 118
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART B – RETURNS
Values:
1) Blank (unused);
2) ‘0’ (did not convert physical document);
3) ‘2’ (original paper converted to image);
4) ‘8’ (undetermined).
Blank
(field unused);
‘0’ or ‘1’
Value transposed from
Check Detail Addendum C Record (Type 28)
Field 11 – Endorsing Bank Identifier;
‘2’
For Mandatory Return Addendum D Record:
Indicates the endorsing Financial Institution is not specifically
identifying itself as the Payor Financial Institution;
‘3’
For Mandatory Return Addendum D Record:
Indicates the endorsing Financial Institution is identifying itself as the
Payor Financial Institution.
The following sections in the ANSI X9.100-187-2008 standard are not included in this Companion
Document. These sections provide the specifications for records that either do not provide any business
content to ICP Return File Delivery in Canada, or provide business value in specific circumstances.
The Image View Detail Record and the Image View Data Record (Type 52) shall be used together to
convey an image view associated with the related Return Record (Type 31). When an Image View Detail
Record (Type 50) is present, an Image View Data Record (Type 52) shall also be present.
Image segments related to the Return Record (Type 31) shall be ordered in the following sequence:
1) front bitonal; 2) front greyscale (*optional); 3) back bitonal; 4) back greyscale. (*optional)
* Note: the exchange of greyscale images is optional as outlined in Operational Agreements between
Members.
Front and back image segments shall always be included on the file, unless omitted by a clearing
arrangement. Image segments shall either be included for all items in the file, or omitted for all items in
the file. If image segments are omitted, then Image View Detail Records (Type 50) shall be omitted from
the file. If Image View Detail Records (Type 50) are omitted, then Cash Letter Record Type Indicator -
Field 08 in the Cash Letter Header Record (Type 10) shall have a defined value of ‘E’. Refer to X9
Section > 17 Return Addendum C Record (Type 34) for additional information on non-image returns
file transfer.
The image view for a returned item corresponding to an image presented Forward item was created by
the Direct Clearer that delivered the original Forward item, or by another Financial Institution that created
the image view and passed it to the forwarding Direct Clearer.
The image view for a returned item corresponding to a Forward item that was presented as an original
cheque or a CRD is created by the Direct Clearer that delivers the returned item.
The Image View Data Record and the Image View Detail Record (Type 52) shall be used together to
convey an image view associated with the related Return Record (Type 31). When an Image View Detail
Record (Type 50) is present, an Image View Data Record (Type 52) shall also be present.
The Image View Data Record contains sixteen fixed length fields, and three variable length fields which
are optionally used. Only one of the variable length fields, Image Data – Field 19, is actually used and
shall be Mandatory when the Image View Data Record is present. The content of the field is always
variable.
The image view for a returned item corresponding to an image presented Forward item was created by
the Direct Clearer that delivered the original Forward item, or by another Financial Institution that created
the image view and passed it to the forwarding Direct Clearer.
The image view for a returned item corresponding to a Forward item that was presented as an original
cheque or a CRD is created by the Direct Clearer that delivers the returned item.
The data fields in the Image View Data Record for the item that is returned by a Direct Clearer reflect the
returning Direct Clearer.
Refer to X9 Section > 21 Image View Detail Record (Type 50) for considerations on the optional
omission of image segments from the file, the inclusion of various image segments on the file, and the
creator of the image segments.
Standard 015
Page 131
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART B – RETURNS
The following section in the ANSI X9.100-187-2008 standard is not included in this Companion
Document. The section provides the specifications for a record that does not provide any business
content to ICP Return File Delivery in Canada.
If images are included in the file, the Bundle Control Record shall always follow an Image View Data
Record (Type 52). If images are omitted from the file, the Bundle Control Record shall always follow a
Mandatory Return Addendum D Record (Type 35).
The Bundle Control Record shall be the last record of the bundle. The data in the fields is created by, or
on behalf of, the Direct Clearer delivering the file, which is the ECE institution.
The following sections in the ANSI X9.100-187-2008 standard are not included in this Companion
Document. The sections provide the specifications for records that do not provide any business content to
ICP Return File Delivery in Canada.
ANSI X9.100-187-2008 information concerning US returns does not apply directly to ICP Return File
delivery in Canada.
For image returns in the Canadian clearings, there can be a maximum of 36 Return Reason codes that
are applied to the Return Record (Type 31) Field 06 – Return Reason.
The values of the Return Reason codes, together with their respective descriptors, in both English and
French, are listed in the CPA Rules and Standards.
The US customer / account Return Reason values as documented in ANSI X9.100-187-2008 do not
directly apply to image returns in the Canadian clearings.
The US Administrative Returns as documented in ANSI X9.100-187-2008 do not directly apply to image
returns in the Canadian clearings.
Items that are returned for administrative reasons, which are errors or conditions associated with the item
itself and not the account from which it is ordered to be paid, cannot be returned by image on an ICP File.
Refer to the CPA Rules and Standards.
Standard 015
Page 150
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART B – RETURNS
ANSI X9.100-187-2008 information partially applies to ICP Return File delivery in Canada.
Cash Letter Header Record (Type 10) – Field 08 ‘Cash Letter Record Type Indicator’ is restricted
to values ‘E’ and ’I’;
Cash Letter Header Record (Type 10) – Field 09 ‘Cash Letter Documentation Type Indicator’ is
limited to values ‘C’, ‘D’, ‘G’, ‘K’ and ‘L’.
X9 Annex D > Image Record Definition for Image View Not Present
ANSI X9.100-187-2008 information does not apply to ICP Return File delivery in Canada.
ANSI X9.100-187-2008 information does not apply to ICP Return File delivery in Canada.
ANSI X9.100-187-2008 information partially applies to ICP Return File delivery in Canada.
The check digit is present in Return Record (Type 31) – Field 03 ‘Payor Bank Routing Number
Check Digit’ only when:
Field 02 ‘Payor Bank Routing Number’ together with Field 03 ‘Payor Bank Routing
Number Check Digit’ contains a combined 9-character data format ‘AAAABBBBC’,
indicating a US ABA MICR Routing Number for a US currency ABA item.
Standard 015
Page 151
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART B – RETURNS
ANSI X9.100-187-2008 information partially applies to ICP Return File delivery in Canada.
The minimal structure of the file, based on the record types that are detailed in this document, is as
follows.
ANSI X9.100-187-2008 information does not normally apply to ICP Return File delivery in Canada.
For non-image returns file delivery, the description of the Image Archive Locator may be of some limited
value.
ANSI X9.100-187-2008 information does not apply to ICP Return File delivery in Canada.
Standard 015
Page 153
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART B – RETURNS
ANSI X9.100-187-2008 information partially applies to ICP Return File delivery in Canada.
This Companion Document provides detailed descriptions of the following record types:
File Header Record (Type 01)
Cash Letter Header Record (Type 10)
Bundle Header Record (Type 20)
Return Record (Type 31)
Return Addendum A Record (Type 32)
- Mandatory record
Return Addendum B Record (Type 33)
- Mandatory record
Return Addendum C Record (Type 34)
- Conditional record
- Possible restricted use for non-image files
Return Addendum D Record (Type 35)
- Single Mandatory record
- Other Conditional record(s)
Image View Detail Record (Type 50)
- Mandatory record unless omitted by clearing arrangement
Image View Data Record (Type 52)
- Mandatory record unless omitted by clearing arrangement
Bundle Control Record (Type 70)
Cash Letter Control Record (Type 90)
File Control Record (Type 99)
Within each of the record types, only specific fields apply, and in some cases, only specific values
for certain record fields apply.
Standard 015
Page 154
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART C – PROCEDURES SPECIFIC TO ICP IN CANADA
7.1 Procedures for the population of ANSI X9.100-187-2008 files for Forward
Presentment & Returns of Eligible ICP Items
The following table is intended to provide industry specific business usage rules for specified fields in
ANSI X9.100-187-2008 files for Inter-Member exchange of ICP Items in Canada. This table should be
read in conjunction with the ANSI X9.100-187-2008 Standard, as well as Parts A & B of this Standard.
Standard 015
Page 156
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART C – PROCEDURES SPECIFIC TO ICP IN CANADA
Procedures for the population of ANSI X9.100-187-2008 files for Forward Presentment &
Returns of Eligible ICP Items
Record Field Business Usage Rule for ICP Files
File Header 04 - Immediate The format is ‘CP00RSNNN’
Record Destination Content as follows
(Type 01) Routing
Number Sub-Field Value Comments
C – Currency ‘0’ = Canadian Indicated the currency of the
Indicator ‘1’ = US Items in the file and the value
shall be identical to Record
Type 01, Field 05.
P – Item Type ‘1’ = Forward Indicates the type of Items in
Presentment the file. The value is
Items expressed as a single digit
and shall be the numerical
equivalent of Record Type
10, Field 02.
00 ‘00’ Fixed value zeroes.
Note: Where the MICR encoding of the Auxiliary On-Us field of an original
paper payment item is not readable by a MICR reader/sorter machine,
Intelligent Character recognition (ICR), or other automated processes, any
unreadable characters shall be replaced by an asterisk (*) in Record Type
25, Field 02.
Check 03 – External Subject to the note below, the population of this field shall be an exact
Detail Processing replica of the printing in the CRD Identifier Code section (position 44) of
Record Code the original payment item.
(Type 25)
Note: Where the MICR encoding of the CRD Identified Code section of an
original paper payment item is not readable by a MICR reader/sorter
machine, Intelligent Character recognition (ICR), or other automated
processes, any unreadable characters shall be replaced by an asterisk (*)
in Record Type 25, Field 03.
Check 04 – Payor Record Type 25, Fields 04 and 05 combined, contain 9 characters.
Detail Bank Routing The format is: NNNNN-FFF
Record Number
(Type 25) ‘NNNNN’ = The five digit number designated by a Member to identify a
05 – Payor Branch.
Bank Routing
Number Check ‘-‘ = the character ‘dash’
Digit ‘FFF’ = The financial institution number allocated by the CPA.
Subject to the note below, the population of this field shall be an exact
replica of the printing in the Transit Number Field (positions 33-43) of the
original payment item.
Standard 015
Page 159
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART C – PROCEDURES SPECIFIC TO ICP IN CANADA
Alternate formats for this field, for use with USD items that contain an ABA
Routing Number is: TTTTAAAAC or TTTT-AAAA
Subject to the note below, the population of this field shall be an exact
replica of the printing on the original payment item.
Note: The ABA routing number is mandatory. Where the MICR encoding
of the ABA routing number is not readable by a MICR reader/sorter
machine, Intelligent Character recognition (ICR), or other automated
processes, the Item would need to be repaired.
Check 06 – On-Us
Detail Subject to the note below, the population of this field shall be an exact
Record replica of the printing in the On-Us Field (positions 14-31) of the original
(Type 25) payment item (i.e. Account/Trans. Code).
The transaction code portion of this field shall be separated from the
account number portion of the field by a forward slash (/). Dashed may be
omitted from the field.
Note: Where the MICR encoding of the On-Us field of an original paper
payment item is not readable by a MICR reader/sorter machine, Intelligent
Character recognition (ICR), or other automated processes, the
corresponding character (s) of Record Type 25, Field 06 shall be replaced
by an asterisk (*).
Check 07 – Item Where the payment type is Canadian, the amount shall not exceed
Detail Amount $25,000,000.00 Unless the item is an Inter-member payment to manage
Record settlement account balances in which case it shall not exceed
(Type 25) $90,000,000.00 If the payment type is USD, the amount shall not exceed
$99,999,999.99
This field indicates the branch and financial institution number of the
negotiating institution branch to which the item should be returned, if
dishonoured.
Check 03 – Endorsing The format is ‘NNNNN-FFF’
Detail Bank Routing
Addendum Number ‘NNNNN’ = The five digit number designated by a Member to identify a
C Record Branch.
(Type 28)
‘-‘ = the character ‘dash’
‘FFF’ = The financial institution number allocated by the CPA.
This field shall contain the branch and financial institution number of the
Direct Clearer which entered this item into the clearing. This field indicates
the Direct Clearers identification of the item in accordance with CPA Rule
A3.
Check 09 – Return This field may not be used, as re-presentment is not permitted.
Detail Reason
Addendum
C Record
(Type 28)
Return 02 – Payor Record Type 31, Fields 02 and 03 combined, contain 9 characters.
Record Bank Routing The format may is: NNNNN-FFF
(Type 31) Number
‘NNNNN’ = The five digit number designated by a Member to identify a
03 – Payor Branch.
Bank Routing
Number Check ‘-‘ = the character ‘dash’
Digit ‘FFF’ = The financial institution number allocated by the CPA.
For items presented electronically, this may be the same as Record Type
25, Field 04 and 05, unless the Drawee institution has replaced, modified
or corrected the originally received value to meet its proprietary
requirements.
Alternate formats for this field, for use for USD items that contain an ABA
Routing Number is: TTTTAAAAC or TTTT-AAAA
Subject to the note below, the population of this field shall be an exact
replica of the printing on the original payment item that is being returned.
Note: The ABA routing number is mandatory. Where the MICR encoding
of the ABA routing number is not readable by a MICR reader/sorter
machine, Intelligent Character recognition (ICR), or other automated
processes, the Item would need to be repaired.
Return 04 – On-Us
Record For items presented electronically, this may be the same as Record Type
(Type 31) 25, Field 06, unless the Drawee institution has replaced, modified or
corrected the originally received value to meet its proprietary
requirements.
The transaction code portion of this field shall be separated from the
account number portion of the field by a forward slash (/). The Dash may
be omitted from the field.
Note: Where the MICR encoding of the On-Us field of the original paper
payment item that is being returned is not readable by a MICR
reader/sorter machine, Intelligent Character recognition (ICR), or other
automated processes, the corresponding character(s) shall be replace by
an asterisk (*).
Return 05 – Item Where the payment type is Canadian, the amount of the return shall not
Record Amount exceed $25,000,000.
(Type 31)
The following file naming convention for ICP Files shall be followed by each Delivering Direct
Clearer:
xxxxxx.ENVE.DdddS.RrrrS.RTC.DYYMMDD.Nxxxxx, where:
RrrrS R:
Fixed letter ‘R’
T:
Collection Type (T)
1 = Forward
3 = Returns
C:
Currency (C)
C = CAD
U = USD
DYYMMDD ACSS/USBE Processing Date The ACSS/USBE date during
which the file was prepared and
sent.
Leading D:
Fixed letter ‘D’
Standard 015
Page 165
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART C – PROCEDURES SPECIFIC TO ICP IN CANADA
xxxxx:
5 digit sequence number
Standard 015
Page 166
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART C – PROCEDURES SPECIFIC TO ICP IN CANADA
The format of an ICP File shall follow what is defined in the ANSI X9.100-187 Standard unless otherwise
noted in this document (Standard 015) and Rule A10. Failure to follow the data and field specifications
could result in a file rejection. In the event that an ICP File is rejected, notification from the Receiving
Direct Clearer should be provided to the Delivering Direct Clearer as soon as it becomes aware that the
file is rejected. The format (e.g. fixed block, text, PDF, etc.) and method of communicating the Rejected
ICP File Notice (e.g. email, FTP, fax, etc.) should be pre-established by the Participants involved in ICP
Exchange.
File Rejection Conditions: Failure to include mandatory information or adhere to the identified standard
file format may result in the rejection of an entire ICP File. When a rejection occurs the Receiving Direct
Clearer may contest the corresponding ACSS/USBE delivery in accordance with Rule A10. In addition,
certain record or item-level exceptions may also result in a rejected ICP File. If the number of such
exceptions within an ICP File exceeds a threshold, (as established by the exchange partners) all the
items within the file may be rejected. These exceptions may occur at the individual record or item level as
per operational agreements. If a field or multiple fields within a record are invalid, that record may be
counted against this file rejection threshold. When this threshold has been exceeded (i.e. the percentage
of invalid records within the file exceeds the file rejection threshold), the entire file may be rejected.
FILE DETAILS
Definitions of values listed in the sample Rejected ICP File Notification report:
1) DATE: Date of file rejection in YYYYMMDD format
2) TIME: Time of file rejection in HH:MM:SS format
3) SENDER: Delivering Direct Clearer (Creator of the ICP File)
4) RECEIVER: Receiving Direct Clearer (Creator of the Reject Notice)
5) FILE TRANSMISSION NAME: as associated with the ICP files delivered in
accordance with Standard 015: Part C – Section 7.2
Standard 015
Page 167
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART C – PROCEDURES SPECIFIC TO ICP IN CANADA
*Note: An invalid date occurs when the date in the ICP file is not equal to the current ACSS or
USBE cycle date, or one day prior to the current ACSS or USBE cycle date.
Standard 015
Page 168
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART C – PROCEDURES SPECIFIC TO ICP IN CANADA
An End-of-Day ICP Transmission Notice for each currency type (CAD and USD) is required from
the Delivering Direct Clearer and should be provided to the Receiving Direct Clearer concurrent
to or immediately following the last ICP File Exchange for the day. The format (e.g. fixed block,
text, PDF, etc.) and method of communicating the EOD Notice (e.g. email, FTP, fax, etc.) should
be pre-established by the Participants involved in ICP Exchange via an operational agreement.
VOLUME/VALUE SUMMARY
FILE DETAILS*
A ‘NIL’ End-of-Day ICP Transmission Notice shall be produced for each currency type (CAN and
USD) when no ICP Files have been exchanged on a particular cycle date. Below is a sample of
this format:
VOLUME/VALUE SUMMARY
Definition of values listed in the End-of-Day ICP Transmission Notice samples above:
1) DATE: Date of EOD transmission in YYYYMMDD format (i.e. Record Type 01 – Field 6)
2) TIME: Time of EOD transmission in HH:MM:SS format (i.e. Record Type 01 – Field 7)
5) REGION: Regional or Bulk Exchange Point - Region associated with Standard 015 Part C Sec 7.2
Positions 9-11 (REG) of the ANSI X9 File Naming Convention.
8) COLLECTION TYPE: FWD, RTN, or F/R to identify whether the EOD Notice is for Forward
Presentment, Returns, or both.
9) CURRENCY: CAD or USD to identify whether the EOD Notice is for Canadian Dollar files, US Dollar
files.
10) SITE: Indicates the logical or physical site from which the delivery of the files takes place. Primary
Site will be 0; Multiple Site processors will use 1-9.
VOLUME/VALUE SUMMARY
11) GRAND TOTAL FWD ITEMS: cumulative total volume of all ICP Items delivered on cycle date
as associated with Record Type 99, Field 04 – Total Item Count for all of the FWD files listed.
12) GRAND TOTAL FWD VALUE$: cumulative total value of all ICP Items delivered on cycle date
as associated with Record Type 99, Field 05 – File Total Amount for all of the FWD files listed.
13) GRAND TOTAL RTN ITEMS: cumulative total volume of all ICP Items returned on cycle date
as associated with Record Type 99, Field 04 – Total Item Count for all of the RTN files listed.
14) GRAND TOTAL RTN VALUE$: cumulative total value of all ICP Items returned on cycle date as
associated with Record Type 99, Field 05 – File Total Amount for all of the RTN files listed.
15) FILE TRANSMISSION NAME: as associated with each of the ICP files delivered in
accordance with Standard 015: Part C – Section 7.2
16) FILE CREATION DATE: as associated to the ANSI Standard X9.100-187 Record Type 01,
Field 06
17) FILE CREATION TIME: as associated to the ANSI Standard X9.100-187 Record Type 01,
Field 07
18) FILE ORIGIN ROUTING NUMBER: as associated to the ANSI Standard X9.100-187 Record
Type 01, Field 05
Standard 015
Page 171
Standard 015 – Companion Document to the ANSI X9.100-187-2008, “Specifications for Electronic
Exchange of Check and Image Data”
PART C – PROCEDURES SPECIFIC TO ICP IN CANADA
19) FILE DEST ROUTING NUMBER: as associated to the ANSI Standard X9.100-187 Record
Type 01, Field 04
20) FILE COLLECTION TYPE: will be ICP1 for Forward Presentment or ICP3 for Returns
21) FILE CURRENCY: will be CAD for Canadian Dollar values or USD for U. S. Dollar values
22) FILE TOTAL DETAIL ITEMS: as associated to ANSI Standard X9.100-187 Record Type 99,
Field 04
23) FILE TOTAL $: as associated to ANSI Standard X9.100-187 Record Type 99, Field 05