Automatic Bank Statement File Import for Cash Management Cloud To

Service (Doc ID 2109691.1) Bottom

In this Document

Goal
Solution
References

APPLIES TO:

Oracle Fusion Cash Management - Version 11.1.8.0.0 and later

Oracle Fusion Cash Management Cloud Service - Version 11.1.8.0.0 and later
Information in this document applies to any platform.

GOAL

 This document details the setup needed to automate the process of bank statement file import
into Fusion Cash Management.

SOLUTION

 Fusion Cash Management has integration with Fusion Payments to take advantage of
payment transmission configuration feature to automate the bank statement file import
process. The processes leverages the payments transmission feature to connect to bank and
download the bank statement file for subsequent processing and loading in to Cash
Management.  

Here are detailed steps to setup automatic bank statement file import:

1. Setup Payment System - Payment system represents the financial institute or bank in
Fusion Payments

Navigation: Setup and Maintenance ----> Manage Payment System

Create a payment system with details as shown below:

2. Setup Payment Transmission Configuration -  Transmission Configuration contains the

connectivity details for the financial institute or bank. This connectivity information is
provided by the bank. Fusion Payments supports following protocols for connecting and
retrieving a file from bank server:

 Secure File Transfer Retrieval Protocol for Static File Names (SFTP_GET)  -
 Bank will provide the SFTP server details including SFTP server host/ip, port,
credential details. Before using this protocol, you will need to log a service request
with Oracle Support and provide SFTP connectivity details. Support will follow the
process outlined in "Bank Statement File Download Using SFTP GET Protocol (Doc
ID 2243918.1)" to enable SFTP connection from the POD to the destination SFTP
server.  Entire process to enable SFTP connectivity takes around a week and possibly
longer if using non-standard SFTP port (any port other than 22)

Important Note: Starting from R13, customers will have the ability to process bank
statements files with dynamic name. For that purpose, user can provide file name with wild
card (‘*’) in the transmission configuration setup. This will allow retrieval of file with any
name that matches to the wildcard pattern. With this change, if a file which was retrieved and
successfully processed then another file with same name will not be retrieved again. This will
ensure that a file is processed only once. See Doc ID 2395131.1 for additional details

Note: If your non-Oracle SFTP server target uses Internet Protocol (IP)-whitelisting as part of
its security scheme, you must ensure that the IP # range for your Oracle Public Cloud data
center will be accepted (i.e. whitelisted) by the target server for SFTP sessions.  For list of
Oracle IP addresses to add to white list for your firewall, please review IP Whitelist for Web
Service Calls Initiated by Oracle Sales Cloud (Doc ID 1903739.1)

 Http(s) GET Request - Bank will provide SSL enabled destination URL for
connecting and retrieving the statement file. This URL can have authentication
enabled. 

HTTPS_GET protocol support https connection. It does not support exchange of any
dynamic tokens.

3. Schedule Process Electronic Bank Statement Request - This ESS process performs the
following tasks:

 Connect to bank and retrieve bank statement file

 Process and load bank statement file into Cash Management

Submit the ESS job as shown below: