Upload Payables Collection Documents Data

The process starts once the supplier sends a collection document against which payment has to be made.

This process is used to import collection documents from the bank, as initiated by the supplier. If the import validation errors option is set to NO, then the collection lines are auto-matched with the transaction installments. If it's set as YES, then based on the action set, either the primary or the reference data is changed, or the import lines are rejected and the bank is informed.

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 Payables Collection Documents 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.

• Don't change the order of the columns in the template.

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

Settings That Affect Payables Collection Documents Data Upload Interface

The template consists of two sheets:

• Instructions and CSV Generation

• Payables Collection Documents

You can enter data in the Payables Collection Documents sheet per the guidelines in this table:

Field Name	Comments
FILE_CONTROL	Bank control file name received from the bank.
ENTRY_SEQUENTIAL_NUMBER	Entry sequential number on an imported bank collection document.
DOCUMENT_NUMBER	Collection Document number on an imported bank collection document.
DOCUMENT_DATE	Date on an imported bank collection document.
CNAB_CODE	No longer used.
DUE_DATE	Due date on an imported bank collection document.
AMOUNT	Total amount of associated installments on an imported bank collection document.
ARREARS_DATE	Use the same date as in DOCUMENT_DATE.
ARREARS_CODE	Use 1.
ARREARS_INTEREST	Use 1.
DRAWEE _NAME	Registered Payer name on an imported bank collection document.
DRAWEE_BANK_CODE	Payer bank code on an imported bank collection document.
DRAWEE_BANK_NAME	Payer bank name on an imported bank collection document.
DRAWEE_BRANCH_CODE	Payer bank branch code on an imported bank collection document.
DRAWEE_ACCOUNT_NUMBER	Payer account number on an imported bank collection document.
DRAWEE_INSCRIPTION_TYPE	Payer inscription type on an imported bank collection document.
DRAWEE_INSCRIPTION_NUMBER	Payer Taxpayer Id on an imported bank collection document.
TRANSFEROR_NAME	The Supplier name of a bank collection document.
TRANSFEROR_BANK_CODE	Bank code of the supplier on an imported bank collection document.
TRANSFEROR_BRANCH_CODE	Branch code of the supplier on an imported bank collection document.
TRANSFEROR_ACCOUNT_NUMBER	Account number of the supplier on an imported bank collection document.
TRANSFEROR_INSCRIPTION_TYPE	Inscription type of the supplier site on an imported bank collection document.
TRANSFEROR_INSCRIPTION_NUMBER	Taxpayer ID of the supplier site on an imported bank collection document.
ACCOUNTING_BALANCING_SEGMENT	No longer used.
SET_OF_BOOKS_ID	No longer used.
ORG_ID	Indicates the identifier of the business unit associated to the row.
BARCODE_TYPE_CODE	Type of barcode used for a Brazilian Payables collection document.
BARCODE	The numeric representation of barcode number (manual) or the barcode number (scanned).
ELECTRONIC_FORMAT_FLAG	Electronic bank collection indicator.

How Payables Collection Documents Data Upload Interface Is Processed

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.