Appendix > Appendix > Format Requirements for Importing Transactions > Accounts Receivable File Format Requirements > External File Format Requirements for the AR Transaction Header
External File Format Requirements for the AR Transaction Header
The table below contains the external file format requirements for the AR Transaction Header.
Required fields are noted with an asterisk (*).
Field Order1
 
Field Description
Maximum Field Length2
 
Character Position (Fixed Length Format)3
 
Data Type
1
* Header Identifier (H)
1
1
Char-Caps
2
* Customer Number
50
2
Char-Caps
3
* Source Document
50
52
Char-Caps
4
* Transaction Date4
 
10
102
Date
5
* Transaction Code (2,3,4,5,6,7,9)
6
112
Char-Caps
6
Description
50
118
Character
7
Terms Code
6
168
Char-Caps
8
Transaction Amount
17
174
Numeric
9
Electronic (EFT)
(1=Yes, 0=No)5
 
1
191
Numeric
10
Bank Account Code
6
192
Char-Caps
 
* End of Record
2
198
 
1 This number is for reference purposes only and will not appear in the actual text file.

2 If the file format is tab or semi-colon delimited, any characters over the specified length will be cut off at the length limit.
If the file format is fixed length (column position) each field must be the exact length shown in the Maximum Field Length column. It cannot be longer or shorter.

3 If the field doesn’t start in the character position specified, it will create an error and potentially prohibit the transaction from being imported.

4 If the Transaction Date is invalid, an error will be printed on the Import Error Report. If the Transaction Date is left blank, it will be imported as zeros.

5 A blank entry in the Electronic (EFT) field will be treated the same as a “0” (No). If AR is not integrated to BR then the Bank Account Code field in the Import File will instead be the 3-character EFT Account Code.

Published date: 12/03/2021