Upload Receivables Bank Returns Data

On receiving collection instructions, the bank collects the amounts and returns information in an electronic format. Those details are imported into the application through this process.

This process validates each record against the related collection documents, supplier, customer, and the related setup. For records that are invalid, the details appear in an ADFdi spreadsheet 'Correct Bank Returns' and it allows to make the required corrections and import the corrected records. After all the records in a bank return file are successfully validated, the Bank Return process can be initiated to generate return collection document updates and receipts, and if applicable, adjustments for interest and discounts. In cases where the calculated interest is different from the received interest, debit memos can be automatically generated or the differences be written off (depending on defined tolerance limits). Receipts are applied to the original installments that were selected in a collection document.

To access the template, complete these steps:

1. Navigate to the File-Based Data Import for Oracle Financials Cloud guide.

2. In the Table of Contents, click File-Based Data Imports.

3. Click Receivables Bank Returns Data Upload Interface.

4. In the File Links section, click the link to the Excel template.

Follow these guidelines when preparing your data in the worksheet:

• Enter the required information for each column. Refer to the tool tips on each column header for detailed instructions.

• Do not change the order of the columns in the template.

• You can hide or skip the columns you do not use, but do not delete them.

Settings That Affect the Receivables Bank Returns Data Upload Interface

The template consists of two sheets:

• Instructions and CSV Generation

• Receivables Bank Returns

You can enter data in the Receivables Bank Returns sheet per the guidelines in this table:

Field Name	Comments
FILE_CONTROL	Bank Control File number received from Bank
ENTRY SEQUENTIAL NUMBER	Register sequence number on electronic file received from the bank.
REGISTER_TYPE	Identifier for header, detail and trailer records in electronic file received from the bank.
TRADE_NOTE_AMOUNT	Amount due remaining on collection document received from the bank.
FILE_GENERATION_NUMBER	Oracle internal use only.
COMPANY_CODE	Company code provided by the bank at the time of contract for services associated with the remittance and return of a collection document.
COMPANY_NAME	Company name of the first party associated with the company code provided by the bank.
GENERATION_DATE	Date on which the interface records were generated. Date Format: MM/DD/YYYY
REMITTANCE_CODE	Bank remittance code in electronic file from the original line sent by the company.
BANK_NUMBER	Unique numeric identifier for a bank.
BANK_OCCURRENCE_CODE	Occurrence code returned by the bank related to a bank occurrence.
OCCURRENCE_DATE	Correction date for a bank occurrence received from the bank. Date Format: MM/DD/YYYY
INSCRIPTION_NUMBER	Company registration number in electronic file received from the bank.
COMPANY_USE	Collection document unique identifier for matching purposes.
OUR_NUMBER	Collection document identifier generated by the bank or the company responsible for the collection document printing.
PORTFOLIO_CODE	Portfolio code in electronic file received from the bank.
YOUR_NUMBER	Collection document number related to the document given by the company.
DUE_DATE	Due date for a collection document received from the bank. Date Format: MM/DD/YYYY
COLLECTOR_BANK_NUMBER	Numeric identifier for collecting bank.
COLLECTOR_BRANCH_NUMBER	Numeric identifier for collecting bank branch.
TRADE_NOTE_TYPE	Oracle internal use only.
BANK_CHARGE_AMOUNT	No longer used.
ABATEMENT_AMOUNT	Abatement amount for a bank collection document received from the bank.
DISCOUNT_AMOUNT	Discount amount for a bank collection document received from the bank.
CREDIT_AMOUNT	Credit amount for a collection document received from the bank.
INTEREST_AMOUNT_RECEIVED	Paid interest amount for a collection document received from the bank.
CUSTOMER_NAME	Customer name on a collection document received from the bank.
RETURN_INFO	Return information comment on a bank occurrence on a collection document received from the bank.
BANK_USE	Operation identifier by bank on electronic file received from the bank.

How Receivables Bank Returns Data Upload Interface Is Processed

The Brazil Bank Return Files Import and Validation flow starts with users receiving Customer Payments Banks Processing Return files with the respective formats. You have to implement a custom process to execute a conversion to the Oracle Financials Cloud Import format and generate a .csv file based on that format. This file must be transmitted to Oracle Cloud UCM. The Load and Import process and the Validate process are executed.

Load the Data into the Interface Tables

1. After you finish preparing the data in the parent and child sheets, click the Generate CSV File button. The process generates both a CSV file and a ZIP file.

2. Load the data using the Load Interface File for Import process:

   1. Sign in to the Oracle Public Cloud SFTP server.

   2. Transfer the ZIP file to the SFTP server location.

   3. Sign in to Oracle Fusion Cloud Applications.

   4. Navigate to Scheduled Processes.

   5. Select Load Interface File for Import.

   6. Select the process indicated in the Overview section to load the CSV file to the interface tables.

   7. Review the results of the process.

   8. If necessary, correct any errors in the CSV file and rerun the Load Interface File for Import process.

3. Correct load errors:

   1. If the load of the CSV file fails on any row, the Load Interface File for Import process ends in error and the Load File to Interface child process ends in either warning or error.

   2. All rows that were loaded from the CSV file are deleted including the ones that loaded successfully. This lets you edit the problematic data in the spreadsheet and resubmit without having to separate the successful rows from the rows that need modification.

   3. Review the log and output files of the Load File to Interface child process for information about the data that caused the failure.

   4. Correct the data in the template you used.

   5. Repeat steps 1 and 2 of this section: Generate the CSV file and load the data using the Load Interface File for Import process.

   6. Repeat all of these steps until all data is loaded successfully.