EFT Processing formats include several sections:
[] - Unique ID of the File format in Square brackets
- description of the bank layout
Note: Render=API - Do not change this line
File format includes several sections:
1. Extra field declaration, including validations, label and help tips
-
BSB or sort code name - customised for the bank layout
-
BSB or sort code size - customised for the bank layout
-
Account name - customised for the bank layout
-
Account size - customised for the bank layout
-
Up to 10 extra fields on the Bank file
-
Up to 50 extra fields on the Vendor file
2. Row Declaration
Each row type can have multiple lines with a number at the end to indicate the sequence. DetailAP1 and DetailAP2 .
-
The definition of the header row(s) - general header for all transactions or an A/P specific header
-
The definition of the detail row(s) - general detail for all transactions or an A/P specific detail
-
The definition of the footer row(s) - general footer for all transactions or an A/P specific detail
-
Rows can include fields from the Company, Bank, Vendor, Payment and Applied Invoices records. For details, refer to Field Names in EFT File Formats
HeaderAP="A000000001[OriginatorIdNumber:%10C][FileCreationNumber:%04D]..”
DetailAP = "C[RecordCount:%09D][OriginatorIdNumber:%-10C]460..”
FooterAP = "Z[RecordCount:%09D][[TransactionTotalInCents:%014D] ..”
Validation examples:
BSBSize is the size of the BSB field. This can either be one number, which means the BSB is a fixed size, or two numbers in the format min:max.
AccountSize is the size of the Account Number field. This can either be one number, which means the Account Number is a fixed size, or two numbers in the format min:max.
Note: The Size is used for data validation.
Making a field required
Use ! in front of a field name. EFT will check if the field has a value.
Example: [!DestAccountNumber] means that the Vendor Bank Account field cannot be blank when creating the EFT File.
