Global ACH CANADA

GDFF Import File

Format Specifications
 ®
J.P. Morgan ACCESS Global ACH
CANADA - GDFF

Table of Contents
Canada - GDFF ............................................................................................................................................................................................................ 1
Supported Transaction Types ......................................................................................................................................................................1
File Format ..........................................................................................................................................................................................................1
Notes on the contents of specific records/entry fields: ......................................................................................................................2
GDFF File Structure Specifications .............................................................................................................................................................3
Sample File (Word wrapped)........................................................................................................................................................................6

Revision History:

Version Number 1.01

Latest Version: April 2013

This document contains information that is confidential and is the property of JPMorgan Chase & Co.
It may not be copied, published, or used in whole or in part for any purpose other than as expressly authorized
by JPMorgan Chase & Co.

All trademarks, trade names, and service marks appearing herein are the property of their respective owners.

© JPMorgan Chase & Co., 2013. All Rights Reserved.

 ®
J.P. Morgan ACCESS Global ACH
CANADA - GDFF

Canada - GDFF
This document defines the file structure and content for importing Canadian domestic
transactions into JPMorgan ACCESS Global ACH in the GDFF format.

Supported Transaction Types

Payments Collections
Direct Credit/Payroll Others Direct Debit Others
Yes - Yes -

For a complete listing of the Canada Payment Association (CPA) Transaction Types, contact the
Canadian Payment Association.

File Format
JPMorgan ACCESS, Global ACH GDFF Structure
The JPMorgan Chase Global Delimited Flat File (GDFF) is a generic transaction file format
that supports non-urgent, low value, domestic payment transactions through the Global ACH
module of JPMorgan Chase’s Internet financial services portal – JPMorgan ACCESS.

GDFF is a proprietary JPMorgan Chase format that enables users to conduct various in-country
transactions for select countries, taking advantage of Global ACH’s bulk transaction handling
capability and a single, easy to create, local language capable and space efficient file format.

GDFF files are variable length flat files. Each data element in the file is delimited by a comma.
® ®
GDFF files can be created through Microsoft Excel and saved as a file with a CSV extension
or they can be created through a text editor such as Microsoft Notepad, Wordpad or Word and
saved with a TXT extension.

The GDFF file consists of the following sections:

Section ID Record ID Description Comments
File Header FH File header. Information in the file header One file header is
is used (together with the File Trailer) to required per file.
validate the total number and total value
of the transactions included in the file.

Transaction TR Transaction record. Contains all Recurring record

information required to initiate a within the file. Each
payment. Multiple transaction records payment will have its
may included in a single file. own line in the file.
File Trailer FT File Trailer. Indicates end of the file. One file trailer is
Information in the file trailer is used to required per file.
reconcile the number and value of
transactions in the file.

Page 1
 ®
J.P. Morgan ACCESS Global ACH
CANADA - GDFF

Notes on the contents of specific records/entry fields:

M/O/C/NA
Every field in a record has an explicit status i.e. Mandatory (M), Optional (O), Conditional
(C) or Not Applicable (N/A).

An “M” indicates that information in this field is required for transaction initiation and is
always present. The field is mandatory and must be either filled with a default specified value
or information in a specified format.

An “O” indicates that information in this field is optional. The absence or presence of
meaningful information in this field is not critical to transaction initiation.

A “C” indicates that information in this field is conditional. Information may either be
mandatory for specific payment instruments or conditions or optional for all other conditions.
Please refer to payment specifications for rules around conditional fields.

An “N/A” indicates that this field is not required for a specific payment instrument for that
country or region. However, all fields with “N/A” are still valid data elements but have no
value. Therefore, they are delimited with a comma (the delimiter) as a placeholder for this
field.

Max Field Size

This indicates the total number of characters that can be entered into a given field, and
the types of characters that will be accepted.
An “N” indicates digits only.
An “A” indicates alphabets only.
An “AN” indicates digits and alphabets are allowed.

Basic Structural File Validation

In order to successfully import a GDFF file and pass the automated structural validation
check, the file must contain:
• File Header, signified by "FH" in field 1 character position 1 to 2 of the file header
• Transaction Record, which is signified by "TR" in field 1 character position 1 to 2 of the
transaction record
• File Trailer, which is signified by "FT" in field 1 character position 1 to 2 of the file
trailer
If the file passes this structural validation check, the system will proceed to check the rest of
the file. If the system detects other errors within the file, it will display a message noting the
errors. If five or more errors are detected, the file will be rejected and an explanatory error
message will be displayed to the user.

General File Validations

• The file name of an imported file cannot exceed 27 characters and it cannot contain
any spaces or special characters.
• If the file contains accounts that the user performing the import is not entitled to, the
file will be rejected.
• If the file contains payroll records and the user performing the import is not entitled
to conduct payroll transactions, the file will be rejected.

Page 2
 ®
J.P. Morgan ACCESS Global ACH
CANADA - GDFF

• If a file is marked as a Payroll file, then all the payments in the file must have the
transaction code of '01' in the Transaction type Field 12. All transactions in the file
must have a payment method of ‘GIR’ in Field 11.
• Transaction value dates cannot extend beyond 7 calendar days in the past or 60
calendar days in the future from the import date.
• The total number of transactions within the file, total dollar amount of the transactions in
the file, and the total number of lines in the file will be validated against the values entered
in the trailer record. If the figures do not match up, the file will be rejected.
• Only the following special characters may be contained within a Canada GDFF file: ‘ ‘
(space), ‘_’ (underscore), and ‘-‘ (hyphen). No other special characters may be used.

GDFF File Structure Specifications

File Header (1 per file)

Field Name M/O/C/NA Size Field Description
File Header M AN2 “FH”
Client Identifier M AN10 Importing Client ID
File Create Date M N8 YYYYMMDD
File Create Time M N6 HHMMSS
Format Version M N5 Literal ‘01100’ for version 11.00

File Trailer Record (1 per file)

Field Name
File Trailer
Total Transaction Count
Total line count
Amount hash total
M/O/C/NA Size Field Description
M AN2 “FT”
M N10 Number of transactions in file
M N10 Number of lines, including file
header, payment, RD and file
trailer
M N25 Total payment amount in file,
ignores currencies but observes
decimal places

Page 3
 ®
J.P. Morgan ACCESS Global ACH
CANADA - GDFF

Transaction Record (1 per Transaction)

The table below outlines how a GDFF transaction record should be populated for each
instrument type. Note: Fields that are named Reserved are not required in Canada.

Field Field Name LL M/O/ Max Direct Credit/ Field Description

No. C/NA field Direct Debits
1 Record Id No M A2 "TR" Transaction Record
2 Originator's Ref. No M AN16 Required Customer defined reference
No number
3 Value Date No M N8 Required Date when transaction is
(YYYYMMDD) paid/received in YYYYMMDD
format
4 Destination No M A2 "CA"
Country Code
5 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
6 Destination Bank No M N9 Required 0999 Bank number
ID 99999 Branch Transit #
7 Destination A/C No M AN12 Required Beneficiary/Payor’s account
number - up to 12 digits
8 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
9 Transaction No M N10 Required Payment/Receipt amount.
Amount CAD has 2 decimal places.
Example: 100 CAD = 10000
10 Currency No M AN3 Required Must be Canadian Dollars
(CAD)
11 Payment Method No M AN3 "GIR"
12 Transaction Type No M AN2 “01” = direct credit
“02” = direct debit
13 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
J.P. Morgan’s customer 10
digit account number.
Account must be held in
supported branch with
proper entitlements. No
Originator A/C special characters or spaces
14 Number No M AN10 e.g. 4669369777 allowed.

15 Reserved - - - N/A Not used in Canadian

clearing. Field must be left
empty.
16 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.

Page 4
 ®
J.P. Morgan ACCESS Global ACH
CANADA - GDFF

17 Destination A/C No M AN30 Must not be all Beneficiary/Payor’s Name

Name blanks. May contain Maximum 30 characters.
spaces and special
characters
18 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
19 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
20 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
21 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
22 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
23 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
24 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
25 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
26 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
27 Reserved - - - N/A Not used in Canadian
clearing. Field must be left
empty.
Payment Details Line 1.
28 Sender's Text 1 No O AN15 May contain spaces Maximum 15 characters
and special characters
Reserved - - - N/A Not used in Canadian
29-41 clearing. Field must be left
empty.
Canadian Payment 3 Digit CPA Transaction
Association (CPA) Type. Must be numeric.
42 Transaction Code No M N3 Required Example: 200

Reserved - - - N/A Not used in Canadian

43-54 clearing. Field must be left
empty.

Page 5
 ®
J.P. Morgan ACCESS Global ACH
CANADA - GDFF

Sample File (Word wrapped)

FH,CLIENTID,20070130,103135,01100,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
TR,22052970,20070131,CA,,370912345,56744661012,,150,CAD,GIR,01,,4661234567,,,STEV
ENJOHNSON,,,,,,,,,,,SENDERS TEXT,,,,,,,,,,,,,,200,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
TR,22052970,20070201,CA,,370912345,7891325001,,50,CAD,GIR,02,,4661234567,,,STEVEN
JOHNSON,,,,,,,,,,,SENDERS TEXT,,,,,,,,,,,,,,402,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
FT,2,4,200,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

FH,CLIENTID,20080716,145500,01100
TR,ORIGREF1,20080716,CA,,099999999,123456789012,,10000,CAD,GIR,01,,4661234567,,,D
ESTINATION ACCT1,,,,,,,,,,,SENDTEXT1012345,,,,,,,,,,,,,,200
TR,ORIGREF2,20080716,CA,,099999999,123456789012,,30000,CAD,GIR,02,,4661234567,,,D
ESTINATION ACCT2,,,,,,,,,,,SENDTEXT2012345,,,,,,,,,,,,,,400
FT,2,4,40000

Page 6