## (BRA) Setting Up Electronic Banking

This chapter provides an overview of electronic banking and user-defined codes for electronic banking and discusses how to:

- Set up the monthly late fee rate (juros de mora).

- Set up bank layouts using the Dynamic Formatter.

See Also

Setting Up UDCs for Electronic Banking for Brazil

### Understanding Electronic Banking

Companies in Brazil often use banks to facilitate the electronic transfer of payments and receipts between suppliers and customers. For payments to suppliers, you electronically send data to the bank as a flat file. You might send the file using the internet, or by using magnetic tape or other electronic media. The bank processes the data and then sends back to you data that describes the transactions processed by the bank.

For receipts, banks collect funds from the customers to pay for goods and services that the customers obtained from you. You can create a flat file with information about the customer and send it to the bank. The bank processes this information and contacts the customers with the amount that they owe to you. The customers send this money to the bank, and the bank sends you information about the transaction.

Because banks in Brazil do not use a common table layout for the transmission of data, the JD Edwards EnterpriseOne system provides a Dynamic Formatter application that lets you create the bank layouts that you need. The procedures that are contained in the Electronic Banking section of this guide describe how to use the Dynamic Formatter application. When you use the Dynamic Formatter application, you specify the bank layout in which the system processes outbound and inbound flat files.

You use the bank layouts that you set up in the Dynamic Formatter application to work with inbound and outbound automatic receipts.

### Setting Up the Monthly Late Fee Rate

You must set up a version of the Generic Message/Rates Records program (P00191) with System Code 76. Record Type JM. The UDC 76/JM is hard-coded into the business function that creates the Brazil A/R tag file record.

The rate is the Brazilian Monthly Late Fee Rate (Juros de Mora) used by the bank for late payments and is based on a 30-day month.

### Setting Up Bank Layouts Using the Dynamic Formatter

This section provides an overview of bank layouts and bank layout attributes, lists prerequisites, and discusses how to:

- Set up the layout master.

- Set up transaction types and line types.

- Set up layout details.

- Specify the layout for transaction types.

- Specify the layout for a payment instrument.

- Create bank cross-references for attributes.

#### Understanding Bank Layouts

A bank layout is a set of specifications comprising attributes. You create bank layouts by using the Dynamic Formatter Layout Setup program (P76B471). You use the bank layouts for processing electronic files for inbound and outbound payments and receipts. After you create a bank layout, you define the record types that the layout uses for inbound and outbound processes, and then you define the attributes and the position of the attributes for each inbound and outbound record type.

Banks in Brazil often use different layouts for different payment instruments. You should create a bank layout for each payment instrument for each bank with which you work.

After you create bank layouts, you must set up bank information for electronic banking. To set up bank information, perform these actions:

1. Define the bank layouts that you want to use for automatic payments and automatic receipts.

2. Specify the payment instrument for each transaction type.

3. Create a cross-reference for attributes that relates the value which the JD Edwards EnterpriseOne system uses for an attribute to the value that the bank uses.

4. Set up next numbers that the system uses when you generate the flat file.

#### Understanding Bank Layout Attributes

A bank layout is a set of specifications comprising attributes. Before you can use a bank layout to send electronic data to the banks, you must assign attributes to a layout that you create. Attributes define specific data and the format of the data. The attributes that you can use are defined in the Dynamic Formatter Attributes UDC table (76B/F1).

The two types of attributes are:

Attribute | Description
System | Values that begin with an S. These values are constants. For example, S0002 is the attribute for blanks and S0003 is the attribute for zeros. You define the value of S0001 when you specify layout details.
Application | Values that begin with a Z. These values are defined by each transaction. For example, attribute Z0009 is the company name. The value of the Z0009 attribute changes, depending on the company for which the transaction occurs.

The system retrieves the information for the attribute depending on:

- Whether the process is inbound or outbound.

- The line type that you specify when you set up the Layout Master.

You use the Dynamic Formatter Layout Setup program (P76B471) to create a record for each transaction/line type combination that you need for a bank layout.

For example, you might set up these transaction/line type combinations for each bank that you work with:

- Inbound/Header

- Inbound/Detail

- Inbound/Trailer

- Outbound/Header

- Outbound/Header Detail

- Outbound/Detail

- Outbound/Trailer

- Outbound/Trailer Detail

  See Setting Up Transaction Types and Line Types.

You must specify the bank layout that you want the system to use for each transaction type for each bank with which you work. When you specify the bank layout, you also identify where the system creates the text file for outbound transactions, where the system stores the file for inbound transactions, and where the application searches for information about the payment instrument.

For inbound transactions, the system searches for information about the payment instrument in the record type that you specify. For example, if you specify Header as the record type, the system searches the lines in the layout that contain header information to identify the payment instrument that is contained in the flat file.

See Specifying the Layout for Transaction Types.

For some attributes, the information that the system retrieves is also determined by whether the attribute is used for automatic receipt or automatic payment processing.

Automatic Payment Process, Inbound, Line Type 1 (File Header)

This table shows examples of the attributes that you might use for inbound transactions with line type 1 (file header):

Value | Description | Description 2 | Explanation
Z0001 | Company Person/Corp Code | F0101 - TAXC | The value for the Person/Corporation Code field in the F0101 table for the address book number that appears in the F0010 table. If PO Unique Payment is activated in the company constants, the system uses the Parent Address Number Person/Corporation Code.
Z0002 | Company Tax ID | F0101 - TAX | The value for the Tax ID field in the F0101 table for the address book number that appears in the F0010 table. If PO Unique Payment is activated in the company constants, the system uses the Parent Address Number Tax ID.
Z0003 | Company Bank Agency | F0030 - TNST | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the system parses information from the G/L bank account defined in the payment group and pulls the value before the separator (/) in the Bank Transit Number field in the Bank Transit Master table (F0030). For the Receipt process, the system parses information from the G/L bank account defined in the processing options and pulls the value before the separator (/) in the Bank Transit Number field in the F0030 table.
Z0004 | Company Bank Account Number | F0030 - CBNK | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the system parses information from the G/L bank account defined in the payment group and pulls the value in the Bank Account Number field in the F0030 table. For the Receipt process, the system parses information from the G/L bank account defined in the processing options and pulls the value in the Bank Account Number field in the F0030 table.
Z0005 | Company Bank Agency Digit | F0030 - TNST | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the system parses information from the G/L bank account defined in the payment group and pulls the value before the separator (-) in the Bank Transit Number field in the Bank Transit Master table (F0030). For the Receipt process, the system parses information from the G/L bank account defined in the processing options and pulls the value before the separator (-) in the Bank Transit Number field in the F0030 table.
Z0006 | Company Bank Account Digit | F0030 - CHKD | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the system parses information from the G/L bank account defined in the payment group and pulls the value in the Control Digit field in the F0030 table. For the Receipt process, the system parses information from the G/L bank account defined in the processing options and pulls the value in the Control Digit field in the F0030 table.
Z0007 | Company Bank Agency Number + Digit | F0030 - TNST | The values for attributes Z0003 and Z0005; they are separated by a dash (-).
Z0008 | Company Bank Account Number + Digit | F0030 - CBNK + CHKD | The values for attributes Z0004 and Z0006; they are separated by a dash (-).
Z0009 | Company Name | F0101 - ALPH | The address book number in the F0010 table. If PO Unique Payment is activated in the company constants, the system uses the Parent Address Number Alpha Name.
Z0010 | Formatted File Date Created | UBE B9800100 - Get Audit Info | The date from the Get Audit Information field in the UBE.
Z0011 | Formatted File Time Created | UBE B9800100 - Get Audit Info | The Time from the Get Audit Information field in the UBE.
Z0012 | Company Bank Number | F0030 - TNST | The system parses information from the G/L bank account defined in the payment group and uses the first 3 digits in the Bank Number field in the F0030 table.
Z0013 | Company Bank Name | F0030 - DL01 | The system parses information from the G/L bank account defined in the payment group and uses the first 3 digits in the Bank Account Number field in the F0030 table and the value in the Description field from the Bank Codes UDC table (76/BC).
Z0014 | Payment Instrument | F0411 - PYIN |
Z0015 | Company Street Name | F0101 - ADD1 | The value for the Address 1 field in the F0101 table for the address book number that appears in the F0010 table. If PO Unique Payment is activated in company constants, the system uses the Parent Address Number Address 1.
Z0016 | Company Street Number | NONE |
Z0017 | Company Street Complement | NONE |
Z0018 | Company City | F0101 - CTY1 | The value for the City field in the F0101 table for the address book number that appears in the F0010 table. If PO Unique Payment is activated in company constants, the system uses the Parent Address Number City.
Z0019 | Company Postal Code - No Mask | F0101 - ADDZ | The value for the Postal Code field in the F0101 table for the address book number that appears in the F0010 table. If PO Unique Payment is activated in company constants, the system uses the Parent Address Number Postal Code. The system uses the value in the Postal Code field without the separator (-).
Z0020 | Company State Code | F0101 - ADDS | The value for the State field in the F0101 table for the address book number that appears in the F0010 table. If PO Unique Payment is activated in company constants, the system uses the Parent Address Number State.
Z0022 | Formatted File Line Count | UBE R76B047E Variable | This UBE counts the number of lines created inside the flat file.
Z0057 | Company Postal Code with Mask | F0101 - ADDZ | The value for the Postal Code field from the F0101 table for the address book number that appears in the F0010 table. If PO Unique Payment is activated in company constants, the system uses the Parent Address Number Postal Code. The attribute uses the value in the Postal Code field with the separator (-).
Z0058 | Payment Group Next Number | UBE R76B047ES NN 04/06 | This UBE generates a unique identifier for the flat file and assigns a next number from 04/06 for each file.
Z0060 | Company Bank Swift Code (Conv.) | F0030 - SWFT | The bank accord/agreement number for the bank as defined in the Dynamic Formatter G/L Bank Account File Numbers table (F76B477) for the BRPAGEL transaction type and the specified G/L bank account.
Z0065 | File Formatter Line Type | UBE R76B047ER Variable |

Automatic Payment Process, Inbound, Line Type 2 (Detail)

This table shows examples of the attributes that you might use for inbound transactions with line type 2 (detail):

Value | Description | Description 2 | Explanation
Z0023 | Payment Group Sequence | UBE R76B047E Variable | The sequence number from the F04572 table, which is required to identify the payment in the return process in the client use code.
Z0025 | Payee Bank Number | F04572 - BNST | The first three digits from the Bank Transit Number field in the F04572 table.
Z0026 | Payee Bank Agency No | F04572 - BNST | The numbers before the separator (/) from the Bank Transit Number field in the F04572 table.
Z0027 | Payee Bank Account Number | F04572 - CBNK | The value for the Bank Account Number field in the F04572 table.
Z0028 | Payee Bank Agency Digit | F04572 - BNST | The value for the numbers before the separator in the Bank Transit Number field in the F04572 table.
Z0029 | Payee Bank Account Digit | F04572 - CBNK | The value from the Control Digit field in the F04572 table.
Z0030 | Payee Bank Agency Number + Digit | F04572 - BNST | The values for the Z0026 and Z0028 attributes, separated by a dash (-).
Z0031 | Payee Bank Account Number + Digit | F04572 - CBNK | The values for the Z0027 and Z0029 attributes, separated by a dash (-).
Z0032 | Payee Name | F0101 - ALPH | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value for the Alpha Name field in the F0101 table for the address book number that appears in the Payee Number field in the F04572 table. For the Receipt process, the value for the Alpha Name field in the F0101 table for the address book number that appears in the Address Number field in the F03B11 table.
Z0034 | Payment Date | F04572 - DGJ | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value for the G/L Date field in the A/P Payment Processing - Summary table (F04572). For the Receipt process, the value for the Payment Date field in the F04572 table.
Z0035 | Payment Amount | F04572 - PAAP | The value for the Payment Amount field in the F04572 table.
Z0042 | Payee Person Corporation Code | F0101 - TAXC | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value for the Person Corporation Code in the F0101 table for the address book number that appears in the Payee Address Number field in the F04572 table. You must create a bank cross-reference. For the Receipt process, the value for the Person Corporation Code in the F0101 table for the address book number that appears in the Address Number field in the F03B11 table.
Z0043 | Payee Tax ID | F0101 - TAX | The data for the attributes varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value from the Tax ID field in the F0101 table for the address book number that appears in the Payee Address Number field in the F04572 table. For the Receipt process, the value for the Tax ID field in the F0101 table for the address book number that appears in the Address Number field in the F03B11 table.
Z0044 | Bar Code - Payee Bank Number | R76B0411 - BBRCD | Parses the bank code from the Bar Code field in the F76B04BC table for the first voucher found in F04573 table.
Z0045 | Bar Code - Currency Code | R76B0411 - BBRCD | For the first voucher in the F04573 table, pulls the currency code from the Bar Code field in the F76B04BC table.
Z0046 | Bar Code - Control Digit | R76B0411 - BBRCD | Parses the currency code from the Bar Code field in the F76B04BC table for the first voucher found in the F04573 table.
Z0047 | Bar Code - Payment Amount | R76B0411 - BBRCD | Parses the payment amount from the Bar Code field in the F76B04BC table for the first voucher found in the F04573 table.
Z0048 | Bar Code - Bar Code All | R76B0411 - BBRCD | The system identifies the first voucher in the F04573 table. It then locates that voucher in the F76B04BC table and writes the value from the Bar Code field to the layout.
Z0049 | Due Date | F04572 - DGJ | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value from the G/L Date field in the F04572 table. For the Receipt process, the value from the Due Date field in the F03B11 table.
Z0050 | Open Amount | F04572 - PAAP+ADSA | The sum of the values of the Payment Amount and Discount Amount fields in the F04572 table.
Z0051 | Discount Taken | F04572 - ADSA | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value from the Discount Amount field in the F04572 table. For the Receipt process, the value from the Discount Amount field in the F03B11 table.
Z0052 | Abatement Amount | Zero |
Z0053 | Discount + Rebate Amount | F04572 - ADSA | The value from the Discount Amount field in the F04572 table (F04572).
Z0054 | Fee Amount | Zero |
Z0055 | Rebate Amount | Zero |
Z0056 | Fee + Fee 2 Amount | Zero |
Z0059 | Bank Agency Digit + Account Digit | F0030 - TNST + CNBK |
Z0061 | Payee Address Book No | F04572 - AN8 | For the Payment process, the value from the Payee Address Number field in the F04572 table. This information is required to identify payment in the return process in the client use code.
Z0062 | Payment Sequence | UBE R76B047ES Variable | This UBE identifies the sequence of the number of payments for a payment group in the F04572 table.
Z0064 | Bar Code - Free Value | R76B0411 - BBRCD | The value from the Bar Code field in the F76B04BC table, for the first voucher founded in the F04573 table.
Z0065 | File Formatter Line Type | UBE R76B047ER Variable |

Automatic Payment Process, Inbound, Line Type 3 (Additional Header)

This table shows an example of the attribute that you might use for inbound transactions with line type 3 (additional header):

Value | Description | Description 2 | Explanation
Z0063 | Line sequence in Segment | UBE R76B047ES Variable | For each segment in a line sequence, this UBE resets the counter to zero.

Automatic Payment Process, Inbound, Line Type 5 (Additional Trailer)

This table shows an example of the attribute that you might use for inbound transactions with line type 4 (additional trailer):

Value | Description | Description 2 | Explanation
Z0063 | Line sequence in Segment | UBE R76B047ES Variable | For each segment in a line sequence, this UBE resets the counter to zero.

Automatic Payment Process, Inbound, Line Type 9 (File Trailer)

This table shows an example of the attribute that you might use for inbound transactions with line type 9 (file trailer):

Value | Description | Description 2 | Explanation
Z0041 | Total Payment Amount | UBE R76B047E Variable | This UBE sums all of the payments in the file.

Automatic Payment Process, Outbound, Line Type 1 (File Header)

This table shows examples of the attributes that you might use for outbound transactions with line type 1 (file header):

Value | Description | Description 2 | Explanation
Z0014 | Payment Instrument | F0411 - PYIN |
Z0065 | File Formatter Line Type | UBE R76B047ER Variable |

Automatic Payment Process, Outbound, Line Type 2 (Detail)

This table shows examples of the attributes that you might use for outbound transactions with line type 2 (detail):

Value | Description | Description 2 | Explanation
Z0014 | Payment Instrument | F0411 - PYIN |
Z0021 | Bank Return Message | Bank |
Z0023 | Payment Group Sequence | UBE R76B047E Variable | The sequence number from the F04572 table, which is required to identify the payment in the return process in the client use code.
Z0024 | Bank Return Code | Band |
Z0034 | Payment Date | F04572 - DGJ | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value for the G/L Date field in the F04572 table. For the Receipt process, the value for the Payment Date field in the F04572 table.
Z0035 | Payment Amount | F04572 - PAAP | The value for the Payment Amount field in the A/P Payment Processing - Summary table (F04572).
Z0051 | Discount Taken | F04572 - ADSA | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value from the Discount Amount field in the F04572 table. For the Receipt process, the value from the Discount Amount field in the F03B11 table.
Z0061 | Payee Address Book No | F04572 - AN8 | For the Payment process, the value from the Payee Address Number field in the F04572 table. This information is required to identify payment in return process in client use code.
Z0065 | File Formatter Line Type | UBE R76B047ER Variable |

Automatic Payment Process, Outbound, Line Type 3 (Additional File Header)

This table shows examples of the attributes that you might use for outbound transactions with line type 3 (additional file header):

Value | Description | Description 2 | Explanation
Z0014 | Payment Instrument | F0411 - PYIN |
Z0065 | File Formatter Line Type | UBE R76B047ER Variable |

Automatic Payment Process, Outbound, Line Type 5 (Additional File Trailer)

This table shows an example of the attribute that you might use for outbound transactions with line type 5 (additional file trailer):

Value | Description | Description 2 | Explanation
Z0065 | File Formatter Line Type | UBE R76B047ER Variable |

Automatic Payment Process, Outbound, Line Type 9 (File Trailer)

This table shows an example of the attribute that you might use for outbound transactions with line type 9 (file trailer):

Value | Description | Description 2 | Explanation
Z0065 | File Formatter Line Type | UBE R76B047ER Variable |

Automatic Receipts Process, Inbound, Line Type 1 (File Header)

This table shows examples of the attributes that you might use for inbound transactions with line type 1 (file header):

Value | Description | Description 2 | Explanation
Z0009 | Company Name | F0101 - ALPH | The address book number in the F0010 table. If PO Unique Payment is activated in the company constants, the system uses the Parent Address Number Alpha Name.
Z0010 | Formatted File Date Created | UBE B9800100 - Get Audit Info | The date from the Get Audit Information field in the UBE.
Z0012 | Company Bank Number | F0030 - TNST | The system parses information from the G/L bank account defined in the payment group and uses the first 3 digits in the Bank Number field in the F0030 table.
Z0013 | Company Bank Name | F0030 - DL01 | The system parses information from the G/L bank account defined in the payment group and uses the first 3 digits in the Bank Account Number field in the F0030 table and the value in the Description field from the Bank Codes UDC table (76/BC).
Z0022 | Formatted File Line Count | UBE R76B047E Variable | This UBE counts the number of lines created inside the flat file.
Z0058 | Payment Group Next Number | UBE R76B047ES NN 04/06 | This UBE generates a unique identifier for the flat file and assigns a next number from 04/06 for each file.
Z0060 | Company Bank Swift Code (Conv.) | F0030 - SWFT | The bank accord/agreement number for the bank as defined in the F76B477 table for the BRPAGEL transaction type and the specified G/L bank account.
Z0065 | File Formatter Line Type | UBE R76B047ER Variable |

Automatic Receipts Process, Inbound, Line Type 2 (Detail)

This table shows examples of the attributes that you might use for inbound transactions with line type 2 (detail):

Value | Description | Description 2 | Explanation
Z0003 | Company Bank Agency | F0030 - TNST | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the system parses information from the G/L bank account defined in the payment group and pulls the value before the separator (/) in the Bank Transit Number field in the Bank Transit Master table (F0030). For the Receipt process, the system parses information from the G/L bank account defined in the processing options and pulls the value before the separator (/) in the Bank Transit Number field in the F0030 table.
Z0004 | Company Bank Account Number | F0030 - CBNK | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the system parses information from the G/L bank account defined in the payment group and pulls the value in the Bank Account Number field in the F0030 table. For the Receipt process, the system parses information from the G/L bank account defined in the processing options and pulls the value in the Bank Account Number field in the F0030 table.
Z0005 | Company Bank Agency Digit | F0030 - TNST | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the system parses information from the G/L bank account defined in the payment group and pulls the value before the separator (-) in the Bank Transit Number field in the F0030 table. For the Receipt process, the system parses information from the G/L bank account defined in the processing options and pulls the value before the separator (-) in the Bank Transit Number field in the F0030 table.
Z0006 | Company Bank Account Digit | F0030 - CHKD | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the system parses information from the G/L bank account defined in the payment group and pulls the value in the Control Digit field in the F0030 table. For the Receipt process, the system parses information from the G/L bank account defined in the processing options and pulls the value in the Control Digit field in the F0030 table.
Z0007 | Company Bank Agency Number + Digit | F0030 - TNST | The values for attributes Z0003 and Z0005: they are separated by a dash (-).
Z0008 | Company Bank Account Number + Digit | F0030 - CBNK + CHKD | The values for attributes Z0004 and Z0006; they are separated by a dash (-).
Z0032 | Payee Name | F0101 - ALPH | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value for the Alpha Name field in the F0101 table for the address book number that appears in the Payee Number field in the F04572 table. For the Receipt process, the value for the Alpha Name field in the F0101 table for the address book number that appears in the Address Number field in the F03B11 table.
Z0035 | Payment Amount | F04572 - PAAP | The value for the Payment Amount field in the F04572 table.
Z0042 | Payee Person Corporation Code | F0101 - TAXC | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value for the Person Corporation Code in the F0101 table for the address book number that appears in the Payee Address Number field in the F04572 table. You must create a bank cross-reference. For the Receipt process, the value for the Person Corporation Code in the F0101 table for the address book number that appears in the Address Number field in the F03B11 table.
Z0043 | Payee Tax ID | F0101 - TAX | The data for the attributes varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value from the Tax ID field in the F0101 table for the address book number that appears in the Payee Address Number field in the F04572 table. For the Receipt process, the value for the Tax ID field in the F0101 table for the address book number that appears in the Address Number field in the F03B11 table.
Z0049 | Due Date | F04572 - DGJ | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value from the G/L Date field in the F04572 table. For the Receipt process, the value from the Due Date field in the F03B11 table.
Z0051 | Discount Taken | F04572 - ADSA | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value from the Discount Amount field in the F04572 table. For the Receipt process, the value from the Discount Amount field in the F03B11 table.
Z0055 | Rebate Amount | Zero |
Z0067 | Bank Duplicata Number | F7603B1 - BBDN | The value for the attribute varies, depending on the processing options: If the processing option is set to Bank (1), the value will be 00000000000. If the processing option for Boleto Emitter is set to Company (2), the attribute value is determined as follows: If a value exists in the Bank Duplicata Number field in the F7603B1 table, the attribute value is the value in the field. If the Bank Duplicata Number field is blank, the attribute value is the Bank Duplicata next number for the BRCOBES transaction in the F76B477 table.
Z0068 | Document Number | F7603B1- BBDN | The value in the Invoice Number field in the F03B11 table.
Z0069 | Invoice Date | F03B11 - DIVJ | The value in the Invoice Date field in the F03B11 table.
Z0070 | Client Use Code |  |
Z0071 | Bank Send Code | F7603B1 - BSCB | The value for the attribute varies, depending on the processing options for R76B03ZS: If the Bank processing option has a value, that value is used. If the Bank processing option does not have a value, 01 is used.
Z0073 | Protest Instructions Code |  | The value in the Protest Instructions Code field in the F7603B1 table.
Z0074 | Protest Instructions |  | The value in the Protest Instructions Days field in the F7603B1 table.
Z0075 | Amount Fee by Day |  | The value in the Daily Late Fee Amount field in the F7603B1 table.
Z0076 | Due Date AR | F03B11 - DDJ | The value in the Discount Due Date field in the F03B11 table.
Z0077 | Payee Line 1 | F0116 - ADD1 | The value for the attribute varies, depending on the processing options: If the Customer Address option is blank, uses the value for the Address 1 field in the F0101 table for the address book number that appears in the Address Number field in the F03B11 table. If the Customer Address option is set to 1, uses the value in the Send Invoice To field in the F03012 table.
Z0078 | Customer Postal Code | 3 digit | The value for the attribute varies, depending on the processing options: If the Customer Address option is blank, uses the first five digits of the Postal Code field in the F0101 table for the address book number that appears in the Address Number field in the F03B11 table. If the Customer Address option is set to 1, uses the value in the Send Invoice To field in the F03012 table.
Z0079 | Customer Postal Code | 5 digit | The value for the attribute varies, depending on the processing options: If the Customer Address option is blank, uses the last three digits of the Postal Code field in the F0101 table for the address book number that appears in the Address Number field in the F03B11 table. If the Customer Address option is set to 1, uses the value in the Send Invoice To field in the F03012 table.
Z0080 | Message Code |  | The value in the Message Code field in the F7603B1 table.
Z0081 | Message Description |  | The value in the message code attachment for the Message Code field in the F7603B1 table.
Z0085 | Discount Available by Day |  | The value in the Discount Avaliable/30 field in the F03B11 table.
Z0086 | Boleto Creation |  | The value in the Boleto Emitter option for the R76B03ZS processing options.
Z0087 | Payment Group Control Number | F7603B1 - HDC | The value in the Carteira Number option for the R76B03ZS processing options.

Automatic Receipts Process, Outbound, Line Type 1 (File Header)

This table shows examples of the attributes that you might use for outbound transactions with line type 1 (file header):

Value | Description | Description 2 | Explanation
Z0010 | Formatted File Date Created | UBE B9800100 - Get Audit Info | Date from file creation.
Z0058 | Payment Group Next Number | UBE R76B047ES NN 04/06 | This UBE generates a unique identifier for the flat file and assigns a next number from 04/06 for each file.
Z0037 | Bank Return Payment Date | Bank | G/L Date, used as G/L Date of receipt
Z0067 | Bank Duplicata Number | F7603B1 - BBDN | The value for the attribute varies, depending on the processing options: If the processing option is set to Bank (1), the value will be 00000000000. If the processing option for Boleto Emitter is set to Company (2), the attribute value is determined as follows: If a value exists in the Bank Duplicata Number field in the F7603B1 table, the attribute value is the value in the field. If the Bank Duplicata Number field is blank, the attribute value is the Bank Duplicata next number for the BRCOBES transaction in the F76477 table.

Automatic Receipts Process, Outbound, Line Type 2 (Detail)

This table shows examples of the attributes that you might use for outbound transactions with line type 2 (detail):

Value | Description | Description 2 | Explanation
Z0003 | Company Bank Agency | F0030 - TNST | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the system parses information from the G/L bank account defined in the payment group and pulls the value before the separator (/) in the Bank Transit Number field in the F0030 table. For the Receipt process, the system parses information from the G/L bank account defined in the processing options and pulls the value before the separator (/) in the Bank Transit Number field in the F0030 table.
Z0004 | Company Bank Account Number | F0030 - CBNK | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the system parses information from the G/L bank account defined in the payment group and pulls the value in the Bank Account Number field in the F0030 table. For the Receipt process, the system parses information from the G/L bank account defined in the processing options and pulls the value in the Bank Account Number field in the F0030 table.
Z0005 | Company Bank Agency Digit | F0030 - TNST | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the system parses information from the G/L bank account defined in the payment group and pulls the value before the separator (-) in the Bank Transit Number field in the F0030 table. For the Receipt process, the system parses information from the G/L bank account defined in the processing options and pulls the value before the separator (-) in the Bank Transit Number field in the F0030 table.
Z0024 | Bank Return Code | Bank | The bank return code from bank file. The value in this field is written to the Receipts field in the Electronic Receipts Input table (F03B13Z1) when the special handling code in the Record Type UDC (76/RC) is set to 1. You must set up a bank cross-reference.
Z0034 | Payment Date | F04572 - DGJ | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value for the G/L Date field in the F04572 table. For the Receipt process, the value for the Payment Date field in the F04572 table.
Z0035 | Receipt Amount | F04572 - PAAP | For all banks except bank 041 (Banrisul), the total amount received, including the fee amount. For Banrisul, the receipt amount does not include the fee amount.
Z0051 | Discount Taken | F04572 - ADSA | The data for the attribute varies, depending on whether you are using the Payment or Receipt process: For the Payment process, the value from the Discount Amount field in the F04572 table. For the Receipt process, the value from the Discount Amount field in the F03B11 table.
Z0052 | Abatement Amount | Zero |
Z0054 | Fee Amount | Zero | The fee amount that the system uses is determined by the processing options for the Process Return A/R Bank Tape Diskette - Dynamic Formatter process (R76B03ZR). Fee Invoice Creation processing option: Blank: The amount is ignored. 1: The system creates an RF invoice with the amount of the fee paid. 2: The system creates an RF invoice with a calculated fee amount that is based on the daily late fee amount on table F76B03B1. Fee Process processing option: Blank: The system performs receipt first on the original invoice and then applies the difference to the fee invoice. 1: The system performs receipt first on the fee invoice, and then applies the difference to the original invoice.
Z0065 | File Formatter Line Type | UBE R76B047ER Variable |
Z0067 | Bank Duplicata Number | F7603B1 - BBDN | The value for the attribute varies, depending on the processing options: If the processing option is set to Bank (1), the value will be 00000000000. If the processing option for Boleto Emitter is set to Company (2), the attribute value is determined as follows: If a value exists in the Bank Duplicata Number field in the F7603B1 table, the attribute value is the value in the field. If the Bank Duplicata Number field is blank, the attribute value is the Bank Duplicata next number for the BRCOBES transaction in the F76B477 table.
Z0070 | Client Use Code |  | The identifier sent during the outbound process and returned during the inbound process. The Client Use Code is a concatenation of the Document Company + Document Type + Document Number, Pay Item/suffix, and Address Number in the Customer Ledger table (F03B11). This is the first process to find an invoice. If this field is blank, the system uses the Bank Duplicata Number. This is the first process to find an invoice. If this field is blank, the system uses the Bank Duplicata Number.

Automatic Receipts Process, Outbound, Line Type 9 (File Trailer)

This table shows an example of the attribute that you might use for outbound transactions with line type 9 (file trailer):

Value | Description | Description 2 | Explanation
Z0065 | File Formatter Line Type | UBE R76B047ER Variable |

#### Prerequisite

Set up these UDC tables with the values that you want to use in the layouts:

- Bank Codes (76/BC)

- Date Format (00/DF)

- Date Separator (H98/DS)

- Decimal Format (H98/DE)

- Direction Indicator (00/DN)

- Record Type (00/RD)

- Transaction Type (00/TT)

See Setting Up UDCs for Electronic Banking for Brazil.

#### Forms Used to Set Up Bank Formats

Form Name | FormID | Navigation | Usage
Work with Dynamic Formatter Layout Master | W76B471A | Bank Tape Processing (G76B413), Dynamic Formatter Layout Setup. Bank Tape Processing (G76B415), Dynamic Formatter Layout Setup. | Locate bank layouts and select a bank layout for additional setup.
Dynamic Formatter Layout Master Revision | W76B471B | On the Work with Dynamic Formatter Layout Master form, click Add. | Name the bank layout and define the record length of the layout.
Work with Dynamic Formatter Layout Transaction & Line Types | W76B471C | On the Work with Dynamic Formatter Layout Master form, select a bank layout and then select Detail from the Row menu. | Create a record for each transaction/line type combination that you need for a bank layout.
Work with Dynamic Formatter Layout Details | W76B471D | On the Work with Dynamic Formatter Layout Transaction & Line Types form, select the line with which you want to work, and then select Detail from the Row menu. | Assign attributes to each transaction type or line type record in the bank layout. When you assign the attributes, you define on which line of the record the attribute appears and the position within the line that the attribute occupies.
Work with Bank Additional Information for Dynamic Formatter | W76B474A | Bank Tape Processing (G76B413), Bank Information for Dynamic Formatter. Bank Tape Processing (G76B415), Bank Information for Dynamic Formatter. | Locate bank layouts that have been linked to transaction types and select them for further setup.
Bank Additional Information for Dynamic Formatter Revision | W76B474B | On the Work with Bank Additional Information for Dynamic Formatter form, click Add. | Specify the bank layout that you want the system to use for each transaction type for each bank with which you work. When you specify the bank layout, you also identify where the system creates the text file for outbound transactions, where the system stores the file for inbound transactions, and where the application searches for information about the payment instrument.
Work with Bank Layouts for Payment Instrument | W76B474C | On the Work with Bank Additional Information for Dynamic Formatter form, select the line with which you want to work, and then select Layouts for Instr. from the Row menu. | Associate bank layouts with payment instruments.
Work with Bank Attributes X Reference for Dynamic Formatter | W76B474D | On the Work with Bank Additional Information for Dynamic Formatter form, select the line with which you want to work, and then select X Reference from the Row menu. | The values that you set up for the layout attributes in the Dynamic Formatter Attributes UDC table (76B/F1) might not apply for every bank with which you work or for the different payment instruments for each bank. You set up cross-references between the JD Edwards EnterpriseOne values and the banks' values so that the system converts the JD Edwards EnterpriseOne value to each bank's required value on outbound transactions, and converts the bank's value to the JD Edwards EnterpriseOne value on inbound transactions
Work with G/L Bank Account Next Numbers | W76B474E | On the Work with Bank Additional Information for Dynamic Formatter form, select the line that you want to work with, and then select G/L Bank Account NN from the Row menu. | After you create bank layouts, set up the next numbers that the system uses when you generate the text file.

#### Setting Up the Layout Master

Access the Dynamic Formatter Layout Master Revision form.

Layout | Enter a unique identifier to the layout.
Record Length | Enter the number of characters (not bytes) allowed per record. This system uses this value in the creation of a virtual diskette file for a personal computer download.

#### Setting Up Transaction Types and Line Types

Access the Work with Dynamic Formatter Layout Transaction & Line Types form.

Dir Ind (direction indicator) | Enter the direction of the transaction from the Direction UDC table (00/DN). Values are: 1: Inbound 2: Outbound
Sequence Number | Enter the sequence in which the record type will appear in the layout.
Record Type | Enter the type of record associated with the line. You set up values in the Record Type UDC (00/RD). For example, you might set up these record types: 1: Header 2: Detail 3: Header detail 4: Trailer detail 7: Header text 8: Detail text 9: Trailer
Lines by Line Type | Enter the number of lines in the layout that are of a specified record type for the sequence number.

#### Setting Up Layout Details

Access the Work with Dynamic Formatter Layout Details form.

Line ID | Displays the system-assigned line ID that uniquely identifies the records in this table. The line ID determines the print order of the records on the stub or register.
Begin Pos. (dynamic formatter begin position) and End Pos. (dynamic formatter end position) | Enter the initial and final positions at which the characters of an attribute appear in the specified line of the flat file. If the attribute might not require all of the character positions defined by the difference between the begin position and the end position, complete the Alpha Filler field with the character that you want to occupy the nonrequired positions.
Attribute | Enter the attribute defined in the Dynamic Formatter UDC table (76B/F1) that occupies the position defined by the difference between the begin position and the end position. Values that begin with an S are constants. Values are: S0001: User-defined value S0002: Blanks S0003: Zeros Values that are defined by each transaction application begin with a Z. These values are hard-coded, but the data associated with the value changes based on data in the table and fields referenced.
Description Alpha | Enter a description for the data items. Enter text in upper and lower case. The system uses this name to search for similar data items. To enter an alpha description, follow these conventions: Dates: Begin all date fields with the word Date. Amounts: Begin all amount fields with the word Amount. Units: Begin all unit, quantity, and volume fields with the word Units. Name: Begin all 30-byte description fields with the word Name. Prompt: Begin any Y/N prompting field with the word Prompt. Address Number: Begin all address numbers (employee, customer, owner) with the word Address Number.
Default Value | Optional default value for this prompt (see Display [Y/N/D]). To use a default value of blanks, enter *BLANK.
Data Type | Enter the style or classification of data, such as numeric, alphabetic, and date. Do not change the data item type if it is used within an existing application. Otherwise, you must regenerate the table and review all business functions that use this data item. Data types include: Character: A single letter, always the size of one. Date: A date. Integer: An integer. Character (Blob): An item that can be translated from EBCDIC (8-bit character code commonly used on IBM mainframes) to ASCII (7-bit character code). Binary (Blob): An item that cannot be translated, appears in machine code, and is found as an executable file under Win.help. Binary: An option that represents two choices. It is usually a combination of the digits 1 and 0 to represent on and off or true and false. String: An item that is always the same size or length. Variable String: An item of variable size. UTime: An item that allows business processes to span several time zones. Identifier: (ID) An item that is used within the program logic for controls. An ID is used to write a C program and reference third-party software that returns a pointer. An API then saves the pointer that references the ID. The parameter that the system passes to the C program is the ID. Numeric: A long integer.
Item Dec (item decimal) | Enter the number of stored positions to the right of the decimal of the data item.
D F (decimal format) | Enter the number of positions to the right of the decimal that you want to use. If you leave this field blank, the system value is used as the default.
Align Left | Select this option to align a group of controls vertically with the left edge of the selected control.
Alpha Filler | Enter the character that the system uses to fill the position defined by the difference between the begin position and end position when the attribute value does not fill the position.
Date Format | Enter the format of a date as it is stored in the database. Values are: MDY: Month, Day, Year (MMDDYY). DMY: Day, Month, Year (DDMMYY). YMD: Year, Month, Day (YYMMDD). EMD: 4-digit Year, Month, Day (YYYYMMDD). If you leave this field blank, the system displays dates based on the settings of the operating system on the workstation. With NT, the regional settings in the Control Panel control the settings for the operating system of the workstation.
Date Sep (date separator) | Enter the character to use when separating the month, day, and year of a given date. If you enter an asterisk (*), the system uses a blank for the date separator. If you leave the field blank, the system uses the system value for the date separator.

#### Specifying the Layout for Transaction Types

Access the Bank Additional Information for Dynamic Formatter Revision form.

Bank Code | Enter the code that specifies the bank to which the system sends the outbound statement. The code that you enter must exist in the Bank Codes (76/BC) UDC table.
Transaction Type | Enter the qualifier used to identify a specific type of transaction.
Direction Indicator | Enter the code that indicates whether the transaction is inbound or outbound.
Path | Enter the path used for client-based menus. The path describes where the application is located on the computer or network. A path includes the drive, folders, and subfolders that contain the application to be executed.
File Extension | Enter the flat file extension that the system appends to the name in the Path field to create the name of the flat file.
Record Type | Specify the type of record associated with the line. You set up values in the Record Type UDC (00/RD). For example, you might set up these record types: 1: Header 2: Detail 3: Header detail 4: Trailer detail 7: Header text 8: Detail text 9: Trailer

#### Specifying the Layout for a Payment Instrument

Access the Work with Bank Layouts for Payment Instrument form.

Pay Inst (payment instrument) | Enter a value that exists in the Payment Instrument (00/PY) UDC table that determines the means by which a payment is issued to a supplier or received from the customer. Examples of payment instruments include check, electronic funds transfer, lockbox, and EDI.
Layout | Enter a unique identifier for the layout.

#### Creating Bank Cross-References for Attributes

Access the Work with Bank Attributes X Reference for Dynamic Formatter form.

Attribute | Enter the attribute defined in the Dynamic Formatter UDC table (76B/F1) that occupies the position defined by the difference between the begin position and the end position. Values that begin with an S are constants. Values are: S0001: User-defined value S0002: Blanks S0003: Zeros Values that are defined by each transaction application begin with a Z. These values are hard-coded, but the data associated with the value changes based on data in the table and fields referenced.
JD Edwards EnterpriseOne Value | Enter the JD Edwards EnterpriseOne value for the attribute that is associated to the bank's value.
Bank Value | Enter the value that the bank uses that you associate with the JD Edwards EnterpriseOne value.