Make Payments - Import Payments - Field Descriptions and Business Rules

When you send an EFT 80 Byte Payment file to TD, using the Import Payments function, TD will:

Complete some Import File Validations to ensure that the file can be processed.
Process the Imported EFT 80 Byte Payment file and add the payments to your Workspace; assuming that the File Validations were successful.

Import File Validations

Once an Import file has been successfully uploaded to TD, TD will validate the file to ensure that it can be processed. The file will be rejected and an error message will be displayed if any of these validations fail:

The file is a valid EFT 80 Byte file (e.g. every line is 80 characters and has a CRLF)
The Originator ID contained in field 2 of the Files Header Record at position 2-11 is an Originator ID to which you have been granted access.
The Payment Type contained in field 3 of the Header record position 12 (will be either 'C' for credits or 'D' for debits) is supported by the Originator ID.
The Total number of detailed records equals the Total Number of Payments in the Trailer record field 2, position 2-9.
The Total number of Payments in Trailer record field 2 does not exceed the number of payments allowed for the Originator.
The Total of detailed records field 7, position 71-80, equals the Trailer record field 3, position 10-23.
The Payment Due Date contained in field 5 of the Header, and the due dates in field 3 of the Detailed records pass the following validation based on the Payment Type in field 3 and the Due Date Check value assigned to the Originator.

For Credits
If the Originator's 'Due Date Check' is "2" then
The Due Date must be >= current business day + 2 Business Days.

If the Originator's 'Due Date Check' is "1" then
The Due Date must be >= current business day + 1 Business Days

If the Originator's 'Due Date Check' is "0" then
The Due Date must be >= current business day + 0 Business Days

If the Originator's 'Due Date Check' is "N/A" then
The Due Date must be >= current business day - 30 Calendar Days

For Debits
The Due Date must be >= current business day - 173 Calendar Days

For both Credits and Debits
The Due Date must be <= current business day + 35 calendar days.

Processing the Imported EFT 80 Byte Payment File

Description

Once an Import file has been successfully uploaded to TD, and passed the Import File Validations, TD will extract the payments from the file and create new Payments within the EFT service. Once the payments are created a Payments (Summary Record) will be added to your Make Payments - Workspace.

The following table identifies how the file and payments are mapped into the WBB-Service.

Summary Record	Assigned WBB Value	Assigned value from File
Summary Record	Assigned WBB Value	Record Type	Field	Position
Originator ID		H	2	2-11
Due Date Note: Only assigned this value if all of the payments are using this due date. If there are mixed due dates then the summary record will be assigned a value of 'MIXED'.		H	5	16-21
Payment Type		H	3	12
# of Payments		T	2	2-9
Total Amount		T	3	10-23
Company Name	The Company Name assigned to the Originator at the time the file was imported.
Company Short Name	The Company Short Name assigned to the Originator at the time the file was imported.
Return Account	The Return Account assigned to the Originator at the time the file was imported.
Last Modified By	Your USERID.
Group	'IMPORT'
Frequency	'No Frequency Assigned'
Payment Type		H	3	12
Rate	'No Rate Assigned'
Due Date		D	3	25-30
Due Date (If the Detailed record was empty)		H	5	16-21
Amount		D	7	71-80
Name		D	2	2-24
User Field 1	Blank / Null
User Field 2	Blank / Null
Reference	If value in File is blank then the system will generate a reference number for the payment. The same global counter, which is used for Templates and One-Time Payments, will be used. The reference number generated by the counter will be prefixed by "IP" to signify that this is an Imported Payment.	D	4	31-49
Bank		D	5	50-53
Transit		D	5	54-58
Account Number		D	6
Group	'IMPORT'
Frequency	'No Frequency Assigned'