EFT Payments Upload File Layout

EFT Payments Import File Layout

The EFT Payments Import function enables users to import information to create One Time EFT Payments or EFT Payments from Templates.

All mandatory information must be available to create a payment. If the payment is to be created using a template, information from the template will be used along with information from the import file to create the payment. If a payment is to be created as a one-time EFT payment, all mandatory information must be available in the import file.

Note: For fixed length files, all fields must be included with the exact length and format indicated in the definition column.

One Time EFT Payment Import

Field name	Description	Definition	Mandatory (Y/N)
Type	1. Must be ‘EO’. Only upper case allowed.	Char (2)	Y
Payment Group	1. Must be a Payment Group that you have previously set up on the EFT Payments service. Access to the corresponding SD Agreement Number should be available to the group. 2. Agreement number and charge back account mapped to payment group are validated.	Char (20)	Y
Due Date	1. The format of the due date must be MM/DD/YYYY. 2. Payments can be backdated up to 170 calendar days for debits and 30 calendar days for credits. 3. Payments can be future dated up to 60 calendar days. 4. Defaults to current date when not available in the file.	Char (10)	N
Institution	1. Must be numeric. 2. Must be a valid institution in the BENE BANK table.	Char (3)	Y
Transit	1. Must be numeric. 2. Must be a valid institution in the BENE BANK table.	Char (5)	Y
Account	1. Must be numeric.	Char (12)	Y
Amount	1. Must be numeric. Comma and dollar sign are allowed. 2. Must be > 0 3. Should not exceed the value set up in BANK SERVICE.	Decimal (15,2)	Y
Payment Type	1. Must be Credit or Debit. 2. Validated against user’s access to payables/receivables. 3. Validated against payable/receivable account mapped to payment group.	Char (6)	Y
Payee/Payor Name		Char (30)	Y
Address 1		Char (35)	N
Address 2		Char (35)	N
City		Char (20)	N
Province		Char (32)	N
Postal Code		Char (10)	N
Country	1. Validated against country table.	Char (32)	N
Cross Ref. Number		Char (19)	Y
CPA Code	1. Must be numeric. 2. Must exist in the CPA code list available in the system.	Char (3)	Y
Sundry Information		Char (15)	N
Contact		Char (35)	N
Phone		Char (20)	N
Email		Char (64)	N
Fax		Char (20)	N
Additional Info.		Char (140)	N

EFT Payments from Templates Import

Field name	Description	Definition	Mandatory (Y/N)
Type	1. Must be ‘ET’. Only upper case allowed.	Char (2)	Y
Template ID	1. Any other characters. 2. Must be a template that you have previously set up and access to the corresponding agreement number must be available to the group. 3. Agreement number and charge back account mapped to payment group are validated. 4. Validation against user’s access to payables/receivables based on payment type.	Char (30)	Y
Due Date	1. The format of due date must be MM/DD/YYYY. 2. Payments can be backdated up to 170 calendar days for debits and 30 calendar days for credits. 3. Payments can be future dated up to 60 calendar days. 4. If blank, will default to current date.	Char (10)	N
Amount	1. Must be numeric. Comma and dollar sign are allowed. 2. Must be > 0. 3. Should not exceed the valued set up in BANK SERVICE. 4. Amount should not be provided in the file if an amount has already been defined in the payment template.	Decimal (15,2)	N
CPA Code	1. Must be numeric. 2. Must exist in the CPA code list available in the system.	Char (3)	Y
Sundry Information		Char (15)	N
Additional Info.		Char (140)	N

EFT Payments Import File Layout

EFT Payments from Templates Import

Related Topics