Bank Draft Formats
Bank draft formats can be used for subscriber payments, subscriber refunds, account direct deposits, and account withdrawals. The formats described in this section will be the same regardless of how they’re used. Several bank draft formats are supported; they are listed in the following table.
ACH
The ACH (Automated Clearing House) bank draft format is used by most U.S. banks. The ACH format will be used if the electronic file format in the Bank record is set to “ACH”.
The ACH file is fixed-length and will be located in /dti/exchange/cm/secure. It can be used for:
Subscriber payments—The file will have the same name as the batch, with the following exception. When the Business Rule Should customer service payments create separate payment batches by publication? is answered “Yes,” and the Business Rule For one-time bank draft payments, should a new batch be created daily? is answered “No,” the file name for Customer Service batches will have the first character of the batch id replaced with the first character of the company short name (when not blank) or the first character of the company ID from Company setup. For example, if the batch name is “CS13072201” and the company short name is “Times,” the file name would be “TS13072201.”
Subscriber refunds—The file will have the same name as the batch.
Account direct deposits—The file will be named
depositMMDDYY-xxx.d.
ACH Bank Draft Format
File Header
1
“1” (record type code)
2
“01” (priority code)
1
Not used
9
Automated clearing house from BANK (immediate destination)
10
Immediate origin from BANK, or if this is blank, client number from BANK (immediate origin)
6
Run date (YYMMDD format) (file creation date)
4
Run time (HHMM format; military) (file creation time)
1
“A” (file ID modifier)
3
“094” (record size)
2
“10” (blocking factor)
1
“1” (format code)
23
Bank description from Bank setup (immediate destination name)
23
Company short name from Company setup (immediate origin name)
8
Not used (reference code)
Batch Header
1
“5” (record type code)
3
“225” for payments, “220” for refunds and direct deposits (service class code)
15
Company short name from Company setup (company name)
20
Not used (company discretionary data)
10
Client number from Bank setup (company identification)
3
“WEB” for web payments; “PPD” for all other entries (standard entry class code)
10
Short description from data entry screen (company entry description)
6
Run date (YYMMDD format) (company descriptive date)
6
Run date (YYMMDD format) (effective entry date)
3
Not used (settlement date (Julian format))
1
“1” (originator status code)
8
Originating DFI from Bank setup; or, if this is blank, automated clearing house from Bank setup (originating depository financial institution (DFI) identification)
7
“0000001” (batch number)
Detail Record
1
“6” (record type code)
2
(transaction code) • For payments: “27” for checking account, “28” for prenotification, “37” for savings account. • For refunds and account direct deposits: “22” for checking account, “32” for savings account. • For account direct deposit prenotification: “23” for checking account, “33” for savings account.
8
First 8 digits of the subscriber or account bank number (receiving DFI identification)
1
Last digit of subscriber or account bank number (check digit)
17
Subscriber or account bank account number (DFI account number)
10
Payment/refund/direct deposit amount, including tip (no decimal point) (amount)
15
Subscriber or account ID (individual identification number)
22
Subscriber or account name (individual name)
2
“S” followed by a space for web payments; blank for all other entries (discretionary data; payment type code)
1
“0” (addenda record indicator)
15
First 8 characters of the automated clearing house from Bank setup, followed by a unique number (trace number = DFI # + unique #)
Batch Control
1
“8” (record type code)
3
“225” for payments, “220” for refunds or direct deposits (service class code)
6
Total number of detail records (entry/addenda count)
10
Entry hash number
12
Total amount of payments; zeros for a refund or direct deposit batch (total debit entry dollar amount)
12
Total amount of refunds or direct deposits; zeros for a payment batch (total credit entry dollar amount)
10
Client number from Bank setup (company identification)
19
Not used (message authentication code)
6
Not used (reserved)
8
First 8 characters of the automated clearing house from Bank setup (Originating DFI identification)
7
“0000001” (batch number)
File Control
1
“9” (record type code)
6
“000001” (batch count)
6
Total of all lines divided by ten and rounded (block count)
8
Total number of detail records (entry/addenda count)
10
Entry hash number
12
Total amount of payments; zeros for a refund or direct deposit batch (total debit entry dollar amount in file)
12
Total amount of refunds or direct deposits; zeros for a payment batch (total credit entry dollar amount in file)
39
Not used (reserved)
Note: ACH bank draft files will always have a number of records that is divisible by 10. When necessary, filler records will be added to the end of the file in order to round up to the nearest 10. For example, if a file has 32 records, 8 filler records will be added, to make a total of 40 records in the file.
RBC
The RBC (Royal Bank of Canada) bank draft format is used by many banks in Canada. The RBC format will be used if the electronic file format in the Bank record is set to “RBC”.
The RBC file is fixed-length and will be located in /dti/exchange/cm/secure. It can be used for:
Subscriber payments—The file will have the same name as the batch.
Subscriber refunds—The file will have the same name as the batch.
Account direct deposits—The file will be named
depositMMDDYY-xxx.d.
RBC Bank Draft Format
Header
6
“000001” (file header begins)
1
“A” (header record)
3
“HDR” (transaction code)
10
Newspaper bank account number
30
Newspaper company name
4
File creation number
7
File creation date (Julian format)
3
“CAD” (currency type)
1
“1” (input type)
15
Not used
Header Count
6
000002 (header count)
65
Not used
1
“N” (client level optional)
8
Not used
Detail Record
6
Record count (detail record begins)
1
“D” for payments; “C” for direct deposits (payment type)
3
“450” for payments; “200” for direct deposits (transaction code)
10
Newspaper bank account number
1
Not used
19
Subscriber or account ID
1
“1” (payment number)
1
Not used
1
“0” (filler)
8
Bank number of the subscriber or account
18
Bank account number of the subscriber or account
1
Not used
10
Payment or deposit amount, including tip
Detail Count
6
Payment record count
7
Transaction date (Julian format)
30
Name of the subscriber or account (last, first)
1
“E” (language code)
1
Not used
15
Short description
11
Not used
1
“N” (optional records indicator)
8
Not used
Trailer
6
Trailer count (file trailer begins)
1
“Z” (record type)
3
“TRL” (transaction code)
10
Newspaper bank account number
20
Not used (must be zeros)
6
Number of payments or deposits
14
Total amount (no decimal point)
20
Not used (must be zeros)
Trailer Count
6
Trailer record count
74
Not used
HSBC
The HSBC file is fixed-length and will be located in /dti/exchange/cm/secure. It can be used for:
Subscriber auto payments
Account bank draft payments
Account direct deposits
HSBC Bank Draft Format
Header
1
1
Record type (“A”)
9
02-10
Record sequence / count
10
11-20
EFT Originator ID—a 10-digit unique ID provided by HSBC
4
21-24
File creation number. Identifier of this EFT file. Each file must contain a file creation number that is greater than that of previously transmitted files.
6
25-30
File creation date. Format CYYDDD: C = 0 (no change in turn of century), YY = year, DDD = Julian date (e.g., Dec. 15 is 350).
5
31-35
HSBC institution ID; always “01600”
20
36-55
Blank
3
56-58
Currency code: CAD (Canadian dollar) or USD (US dollar)
1406
59+
Blank
Detail Debit/Credit Record The detail records define information for each transaction in the EFT file.
1
1
Record type (“C” - credit payment or “D” - debit payment)
9
02-10
Record sequence / count. Increment by 1 from same field in header record.
10
11-20
EFT Originator ID. Must be the same as the EFT Originator in the header record.
4
21-24
File creation number. Must be the same as the file creation number in the header record.
Segment 1
3
25-27
CPA transaction code.
10
28-37
Amount of EFT transaction.
1
38
Due date century. 0 (no change in turn of century)
2
39-40
Due date year. 2008 = 08.
3
41-43
Due date day. Julian.
4
44-47
Financial institution bank number, format 0999
5
48-52
Financial institution branch number, format 99999
12
53-64
Participant account number. Must be left-justified; do not zero fill. Significant digits only.
22
65-86
Item trace number; all “0”
3
87-89
Stored trans type; all “0”
15
90-104
Short name. Your company’s name for participant statements. Do not enter zeros in this field.
30
105-134
Transaction payee / payor name. Mandatory.
30
135-164
Long name. Your company’s name for participant statements.
10
165-174
EFT originator ID. Must be the same as the EFT originator ID in the header record.
19
175-193
Transaction origination Xref. Optional.
9
194-202
Transaction return financial institution.
12
203-214
Transaction return account.
15
215-229
Originator’s sundry info. May remain blank.
22
230-251
Stored trace number. Blank.
2
252-253
Settlement code. Blank.
11
254-264
Invalid data element. All “0”.
Detail records may include 6 segments or transactions. Segments 2-6 have the same format at Segment 1 (described above)
265-504
Segment 2
505-744
Segment 3
745-984
Segment 4
985-1224
Segment 5
1225-1464
Segment 6
Trailer Record (must be the last record of the EFT file)
1
1
Record type; “Z”
02-Oct
9
Record sequence / count. Increment by 1 from same field in previous record.
Nov-20
10
EFT Originator ID. Must be the same as the EFT Originator ID in the header record.
21-24
4
File creation number. Must be the same as the file creation number in the header record.
25-38
14
Amount of debit payment transactions (type D). Right-justified with leading zeros.
39-46
8
Total number of debit payment transactions (type D). Right-justified with leading zeros.
47-60
14
Amount of credit payment transactions (type C). Right-justified with leading zeros.
61-68
8
Total number of credit payment transactions (type C). Right-justified with leading zeros.
69-82
14
Number of Err Corr “E”. Should be “0”.
83-90
8
Value of Err Corr “E”. Should be “0”.
91-104
14
Number of Err Corr “F”. Should be “0”.
105-112
8
Value of Err Corr “F”. Should be “0”.
113+
1352
Filler.
CIBC
The CIBC (Canadian Imperial Bank of Commerce) bank draft format is used in Canada. The CIBC format will be used if the electronic file format in the Bank record is set to “CIBC”.
The CIBC file is fixed-length and will be located in /dti/exchange/cm/secure. It can be used for:
Subscriber payments—The file will have the same name as the batch.
Subscriber refunds—The file will have the same name as the batch.
Account direct deposits—The file will be named
depositMMDDYY-xxx.d.Account withdrawals—The file will be named
paymentMMDDYY-xxx.
CIBC Bank Draft Format
File Header
1
1
“1” (file header record begins)
2
02-03
Spaces
5
04-08
Receiving data center (from Bank setup)
5
09-13
Spaces
10
14-23
Originator number (client number from Bank setup)
6
24-29
File creation date (format MMDDYY)
4
30-33
File creation number
1
34
Spaces
4
35-38
Bank number (from Bank setup)
5
39-43
Branch number (from Bank setup)
12
44-55
Bank account number (from Bank setup)
2
56-57
Spaces
15
58-72
Company Name
1
73
Space
3
74-76
Currency indicator (“CAD” = Canadian dollar, “USD” = US dollar)
4
77-80
Spaces
Batch Header
1
1
“5” (batch header record begins)
46
02-47
Spaces
3
48-50
“450” (transaction type)
10
51-60
Descriptive statement (short description entered at run time)
6
61-66
Export date
14
67-80
Spaces
Detail Record
1
1
“6” (detail record begins)
1
2
Credit/debit indicator. “C” direct deposits, “D” for account withdrawals and subscriber bank drafts.
1
3
Space
4
04-07
Bank number of the subscriber or account
5
08-12
Branch number of the subscriber or account
12
13-24
Bank account number of the subscriber or account
5
25-29
Spaces
10
30-39
Payment amount (last two positions are cents)
13
40-52
Cross-reference number (payment sequence number)
22
53-74
Name of the subscriber or account
6
75-80
Spaces
Batch Trailer
1
1
“7” (batch trailer record begins)
3
02-04
“450” (transaction type)
6
05-10
Batch record count
10
11-20
“9999999999” (hash total)
20
21-40
Spaces
12
41-52
Batch payment total (last two positions are cents)
28
53-80
Spaces
File Trailer
1
1
“9” (file trailer record begins)
6
02-07
Batch count
6
08-13
Record count
67
14-80
Spaces
BACS
The BACS (Bankers Automated Clearing Services) bank draft format is used by many banks in the United Kingdom. The BACS format will be used if the electronic file format in the Bank record is set to “BACS”.
The BACS file is fixed-length and will be located in /dti/exchange/cm/secure. It can be used for:
Subscriber payments—The file will have the same name as the batch.
Subscriber refunds—The file will have the same name as the batch.
Account direct deposits—The file will be named
depositMMDDYY-xxx.d.Account withdrawals—The file will be named
paymentMMDDYY-xxx.
BACS Format
Destination Sort Code
9(6)
Sort code assigned with the subscriber or account payment
Destination Account Number
9(8)
Account number assigned with the subscriber or account payment
Destination Account Type
9(1)
Value=”0”
Transaction Code
9(2)
Value=”01” for initial payment or direct debit Value=”0N” for pre-notifications Value=”99” for refunds or payments to account Value=”19” for final collection Value=”17” for all other payments or direct debits
Originating Sort Code
9(6)
The sort code defined in Bank setup
Originating Account Number
9(8)
The bank account number defined in Bank setup
Free Format
X(4)
Space filled
Amount
9(11)
No decimal point, with leading zeros
Originating Account Name
X(18)
The newspaper’s account name defined in Bank setup (left justified)
Reference
X(18)
Subscription or account ID
Destination Account Name
X(18)
First and last name of the subscriber or account (left justified)
EdgCapture
The EdgCapture bank draft format is a fixed-length format and will be located in /dti/exchange/cm/secure. Business Rules determine if bank draft payments are included in the EdgCapture credit card export.
The EdgCapture file will be named “edgcapture[type][productID].[date][sequence#]”, where:
[type] will be “ar” for auto renew payments, “ot” for one-time payments, or “ref” for refunds.
[date] will be the batch date in DDMMYYYY format.
[sequence#] will be the number of times the EdgCapture export has been run on that day.
The EdgCapture format is used for account and subscriber credit card payments, subscriber refunds, and subscriber bank draft payments. It is described on Account Credit Card Payment Formats | EdgCapture.
Edgil
The Edgil bank draft format is a fixed-length format and will be located in /dti/exchange/cm/secure. Business Rules determine if bank draft payments are included in the Edgil credit card export.
The Edgil format can be used for subscriber payments and refunds—The file will be named edgilar.[date][sequence#] for auto-renews, or edgilot.[date][sequence#] for one-time bank drafts.
[date] is the batch date in DDMMYYYY format, and [sequence#] is the number of times the Edgil export has been run on that date. If more than 9,999 records are being exported, multiple Edgil files will be created, using the same naming convention but with suffixes of 1, 2, 3, and so on.
Edgil Bank Draft Format
Control Record
1
H (Control record begins)
8
System date in DDMMYYYY format
1
Merchant ID (from Business Rules)
1
Filler (spaces)
2
Sequence number (number of Edgil exports so far on this date)
1
OEP ID (from Business Rules)
1
1 (held transaction option)
65
Filler (spaces)
Detail Record
1
1 (Detail record begins)
4
Transaction sequence (the order of the payment in the file)
2
SA (transaction code—SA = “sale”)
1
OEP ID (from Business Rules)
1
Merchant ID (from Business Rules)
8
System date in DDMMYYYY format
2
Sequence number (from the Control record)
4
Transaction sequence (the order of the payment in the file)
2
Filler (spaces)
24
Subscriber or account bank account number
6
Credit card expiration date (spaces)
7
Payment amount, including cents, format 9999999
8
Authorization code (spaces)
2
Card holder state (spaces)
8
Filler (spaces)
Detail Record 2
1
2 (Detail record 2 begins)
4
Transaction sequence (the order of the payment in the file)
19
Subscriber or account first name plus last name
1
Oct 35 (GS-1)
19
Subscriber or account address, line 1
1
Oct 35 (GS-2)
20
Subscriber or account address, line 2
9
Subscriber or account Zip code plus Zip extension
6
Filler (spaces)
Detail Record 3
1
3 (Detail record 3 begins)
4
Transaction sequence (the order of the payment in the file)
15
Subscriber or account primary phone number, format (999)999-9999, plus 2 spaces
15
Account number of subscription or account
12
Subscriber or account city
10
Account number of subscription or account
4
ID of user who entered payments
5
Subscription or account payment batch ID
4
Payment sequence (the order of the payment in the batch)
10
Filler (spaces)
Detail Record 4
1
4 (Detail record 4 begins)
4
Transaction sequence (the order of the payment in the file)
75
Filler (spaces)
Detail Record 5
1
5 (Detail record 5 begins)
4
Transaction sequence (the order of the payment in the file)
9
Subscriber or account bank number
1
B if auto renew payment, otherwise A
1
A if client type entered with payment is “personal” or blank, B if client type is “business”
64
Filler (spaces)
Trailer Record
1
T (Trailer record begins)
4
Total number of detail records in batch (detail 1 + 2 + 3 + 4 + 5)
9
Total amount of all payments in batch
66
Filler (spaces)
Intell-A-Check
The Intell-A-Check bank draft format is a fixed-length format and will be located in /dti/exchange/cm/secure. Business Rules determine if bank draft payments should be exported using Intell-A-Check.
The Intell-A-Check format can be used for subscriber payments and refunds. The file will be named icheck[batchID].txt.
Intell-A-Check Bank Draft Format
Check Date
MM/DD/YYYY
Payment date
Check Number
9(10)
Check number
ABA
9(9)
Subscriber or account bank number
Account Number
9(20)
Subscriber or account bank account number
Amount
9.99 (17.2)
Amount
Memo
X(40)
Blank
Name1
X(35)
First name
Name2
X(35)
Last name
Street
X(40)
Street name
City
X(25)
City
State
X(2)
State
Zip
X(5)
Zip code
Date Posted
MM/DD/YYYY
Payment date
Requester
X(16)
Requester ID defined within bank setup
MICR Alignment
X(1)
Value=”R”
Check PayTo Name
X(40)
Populated by the setting of the Business Rule, If interfacing bank draft payments to Intell-A-Check, what text should be exported in the ‘Check Pay To Name’ field?
Confirm Letter Request
Y/N
Value=”N”
Transaction Type
X(4)
Blank
Customer ID
X(32)
Subscription or account ID
Reference Code
X(32)
Blank
Fee
9.99 (3.2)
Blank
Record Number (ID)
X(8)
Blank
Bank Name
X(50)
Blank
Bank City
X(30)
Blank
Bank State
X(2)
Blank
User Name
X(16)
User ID from subscription or account payment
Printed
Y/N
Value=”N”
Confirm Letter Printed
Y/N
Value=”N”
Phone
9(10)
Phone number
Status
X(8)
Blank
Group ID
X(2)
Blank
SSN
9(9)
Blank
Drivers License
X(24)
Blank
Drivers License State
X(2)
Blank
DOB
MM/DD/YYYY
Blank
Check Type
X(1)
Value=”P” for personal or “B” for business
Verify Required
Y/N
Value=”N”
Verify Status
Y/N
Value=”N”
Verify Time
MM/DD/YYYY HH:MM:SS
Blank
Verify Response Status
Y/N
Blank
Verify Text
X(32)
Blank
Verify Code
X(16)
Blank
ACH Entry Class
X(3)
“WEB” if payment was made via the web; otherwise Blank
Settled
Y/N
Blank
Date Settled
MM/DD/YYYY
Blank
PrintToPaper
Y/N
Value=”N”
UDK1
X(8)
Blank
UDK2
X(16)
Blank
UDK3
X(32)
Blank
Location ID
X(4)
Blank
Split Number
9(2)
Blank
Split Amount
9.99 (17.2)
Blank
Split Account Number
9(24)
Blank
Saving Account
Y/N
Value=”N” for checking and “Y” for savings
Verification Station ID
X(16)
Blank
MICR
X(40)
Blank
Surcharge
9.99 (3.2)
Blank
Additional Principle
9.99 (7.2)
Blank
Fee Printed
Y/N
Value=”N”
Fee Date Printed
MM/DD/YYYY
Blank
Batch ID
X(8)
Blank
Batch Sequence Number
9(6)
Blank
Batch Lot Number
9(6)
Blank
Credit
Y/N
Value=”N”
Date Printed
MM/DD/YYYY
Blank
Frozen
Y/N
Value=”N”
Last updated
