FX - INT - 18 FedEx Remittance File To Citibank TSD - v1.3

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 15

FedEx

Oracle Cloud
Implementation
Technical Design
Document

FX_INT_18: Remittance
Advice File to Citibank
(Outbound)

March 2018

Release 13.0
Technical Design Document – Remittance File to Citibank (Outbound) 1
Authors

Name E-mail: Position


Sumanth Shenoy Tonse sumanth.s.tonse@pwc.com Senior Associate

Versions
Date Document Version Document Revision Document Author
Description
3/21/2018 1.0 Initial Version Sumanth S Tonse
4/09/2018 1.1 Added assumption on Sumanth S Tonse
Tokenized Card number.
18/06/2018 1.3 Added ESS Job details Sumanth S Tonse

Approvers
Approval Date Approved Version Approver Role Approver
PwC - Engagement Lead Ranga Subramanian

Technical Design Document – Remittance File to Citibank (Outbound) 2


Table of contents

Background 4
1.1. Scope 4
1.2. Business benefits 4
1.3. Intended audiences 4
Technical design 5
2.1. Business requirements 5
2.2. Approach 5
2.3. Setups 5
2.4. Flow diagram 9
2.5. Assumptions 10
2.6. Security requirements 10
2.7. Report/Log output 10
2.8. Error message handling and reprocessing 11
2.9. Definitions 11
Test Scenarios 12
Open and Closed Issues 13
Appendices 14

Technical Design Document – Remittance File to Citibank (Outbound) 3


Background

FedEx is currently in the process of implementing Oracle Cloud financial applications. As a part of this initiative,
some business process improvements are considered to enhance productivity and improve process controls.

This document describes the technical design to generate and interface Remittance Advice files from Oracle Cloud
to Citibank.

Payment intimation from FedEx to the disbursement bank (Bank of America) is made at once for different
expenses/ card transactions depending upon the payment schedule. Based on this intimation, Bank of America
pays Citibank in lump sum and not per card account. For Citibank to mark the individual card transactions as
paid, it has to be intimated with the individual transaction details that are paid.

1.1. Scope
The scope of this document is limited to the creation of Remittance Advice files with requisite format in Oracle
Cloud and its transmission to Citibank.

1.2. Business benefits


The following are some of the key business benefits that are expected to be realized out of this interface:

● To enable Citibank to mark the right card account as paid, a Remittance Advice file is prepared in Oracle
Cloud. This file contains card account information, along with the payment details. Once generated, this
file is transmitted to the Citibank server as an automated process. This provides Citibank the requisite
information to mark the relevant corporate card accounts as paid.

1.3. Intended audiences


The intended audiences for this document include the project process team, functional team, technical team and
testing team members.

Technical Design Document – Remittance File to Citibank (Outbound) 4


Technical design
This section contains all the information related to building the interface for the business requirements stated
below.

2.1. Business requirements


The list of business requirements covered in this design are:

● Generation of Remittance Advice file in Oracle Cloud.

● Interface of Remittance Advice file from Oracle Cloud to Citibank.

2.2. Approach
The agreed high-level approach for this interface is as follows:

● BI Report – ‘Disbursement Corporate Credit Card Remittance Formats’ is customized and a custom eText
template is prepared as per Citibank’s Global Combi-Pay (GCP) format.

● Payment Format – ‘MasterCard Remittance Format’ is setup with type as “Disbursement Corporate Credit
Card Remittance File” and associated with the custom eText BI template prepared before.

● Payment Transmission – ‘Citibank Transmission’ configuration is setup with Citibank destination server
details.

● ESS Job – ‘Submit Corporate Card Remittance File’ is scheduled to run ‘MasterCard Remittance Format’.
This job processes the payments made through Payment Process Request (PPR) and generates the
Remittance Advice file in Global Combi-Pay format. Transmission Configuration is defaulted to the
‘Citibank Transmission’.

2.3. Setups
1. BI Template
The standard Oracle BI Template for “Disbursement Corporate Credit Card Remittance Formats” –
CorporateCreditCardRemittanceFile.rtf is downloaded from BI Publisher. This template is available in the
BI Publisher folder (/Shared Folders/Financials/Payments).

This RTF template is modified to adhere to the format in Citibank’s Global Combi-Pay (GCP) layout. This
amended template is renamed as XXCorporateCreditCardRemittanceFile.rtf

Citibank’s Global Combi-Pay layout

Technical Design Document – Remittance File to Citibank (Outbound) 5


Global-CombiPayb1
1-Layout_FINALb1-20160114.xlsx

Customized RTF template - XXCorporateCreditCardRemittanceFile.rtf

XXCorporateCreditC
ardRemittanceFile.rtf

2. BI Report
Navigate to: ‘/Shared Folders/Financials/Payments’

This is a standard, un-customized report and has to be enabled for customization. To enable
customization, right click on the report and click on ‘Customize’.

Now, the same report can be viewed in a custom folder (‘/Shared Folders/Custom/Financials/Payments’)
and is customizable.

Technical Design Document – Remittance File to Citibank (Outbound) 6


Click on the ‘Edit’ option in the ‘Disbursement Corporate Credit Card Remittance Formats’ report.

Create a new template (‘MasterCard Remittance File Template’) by uploading the custom eText template
‘XXCorporateCreditCardRemittanceFile.rtf’

3. Disbursement Corporate Credit Card Remittance File format

Navigation: Setup and Maintenance -> Manage Formats -> Select Type =
‘Disbursement Corporate Credit Card Remittance File’ -> Click on Create button

Create custom disbursement format using the following details:

Upload Rules : MasterCard Remittance Format

Technical Design Document – Remittance File to Citibank (Outbound) 7


Code : XXIBY_CDF_REMITTANCE
BI Publisher Template : MasterCard Remittance File Template

4. Transmission Configuration

Navigation: Setup and Maintenance -> Manage Transmission Configurations ->


Select Protocol = ‘Secure File Transfer Protocol for Static File Names’ -> Click on
Create button

Configuration : CitiBank SFTP Transmission – CitiSFT


Protocol : Secure File Transfer Protocol for Static File Names
FTP Server IP Address : 192.193.218.29 (UAT Virtual IP from CitiBank)
FTP Account User Name : fedexts (CitiSFT user name)
FTP Account Password : (CitiSFT password)
Remote File Directory :/
Sent File Name : FX_GCPI_FedEx_125_&REQUESTID_T

Technical Design Document – Remittance File to Citibank (Outbound) 8


2.4. Flow diagram
Integration with Citibank

The inbound CDF3 Corporate Cards transactions interface is a separate component and not part of scope of
Remittance Advice file to Citibank interface.

ESS Job Execution


The process to generate and transmit the Remittance Advice files is a manual activity. This is undertaken after the
completion of CCD electronic payments file Payment Process Request.

ESS Job “Submit Corporate Card Remittance File” has to be run after the PPR for CCD file is completed.

The ESS Job has below parameters:

1. Payment File : Select the PPR document number for the particular CCD file which has
to be remitted.
2. Format : Default to “MasterCard Remittance Format”
3. File Sequence Number : Provide a value that populates CCRemittanceFileSequenceNumber tag
4. File Version Number : Provide a value that populates CCRemittanceFileVersionNumber tag
5. Transmission Configuration : Default to “CitiBank SFTP Transmission – CitiSFT”

Technical Design Document – Remittance File to Citibank (Outbound) 9


The ESS job generates a remittance advice file and transmits the file to CitiSFT location with the file name
FX_GCPI_FedEx_125_<REQUESTID>_T.

CitiSFT Virtual IP details are given below:

Production External VIPs


192.193.218.30
199.67.137.221

UAT External VIP


192.193.218.29
192.193.173.119

2.5. Assumptions
The list of all the assumptions based on which the interface has been developed are as follows:

Sl.No Assumptions

1 Employee details from Oracle are available with Citibank and Oracle Person number (FedEx ID) will be

Technical Design Document – Remittance File to Citibank (Outbound) 10


available in <EmployeeID> tag in the CDF file

2 CitiSFT virtual IPs are whitelisted and firewall rules allow traffic to CitiSFT environment

3 Citibank should send tokenized card numbers in CDF3 inbound file. The same tokenized number will be
sent back to Citibank in GCP format Remittance Advice file in “Card Acct Number” / D2 field.

2.6. Security requirements


The list of all the security requirements for this interface are as follows:

● Access to Corporate Cards setups and ESS jobs are limited to users having the “Card Administrator” role.

2.7. Report/Log output


The output will be driven through the standardized reporting structure and will include:

● XX

The report output will appear as follows:

● XX

The log will include:

● Detailed error messages of each failed report

2.8. Error message handling and reprocessing


The following table captures the commonly encountered error scenarios and also highlights the action taken to
reprocess the error records:

Sl.No. Error Message Cause Action


1
2

2.9. Definitions
The lists of all the definitions used in this design document are as follows:

● AP = Accounts Payables

Technical Design Document – Remittance File to Citibank (Outbound) 11


● CM = Cash Management

● MFT = Managed File Transfer

● SFTP = Secure File Transfer Protocol

● ESS = Enterprise Scheduler Service

● PPR = Payment Process Request

● GCP = Global Combi-Pay

Technical Design Document – Remittance File to Citibank (Outbound) 12


Test Scenarios
Step Test Case Expected Result Data

Technical Design Document – Remittance File to Citibank (Outbound) 13


Open and Closed Issues
Sl.N Issue Issue Open Date Disposition Closed Date
o Owner
1 What is the Rivers Clarke Use the same 28-March-2018
destination for (Citibank) CitiSFT location.
Remittance Advice
File?
2 If multiple remittance Rivers Clarke Citibank will check 28-March-2018
files are generated on a (Citibank) only the file prefix.
single day, the file You can
names will be the concatenate the
same. How can we SeqNbr / Time
avoid the original file Stamp as suffix to
from being replaced? the file Name
3 Since we are receiving Rivers Clarke We cannot accept 28-March-2018
masked card numbers (Citibank) Account Number
with only the last 4 as you have
digits exposed, Oracle indicated below. 
generates Card We must either
Number with receive the full
Employee ID and Account Number
unmasked characters or we can also
of Card Number from utilize
CDF file Tokenization as
indicated in H8

Appendices

Technical Design Document – Remittance File to Citibank (Outbound) 14


Technical Design Document – Remittance File to Citibank (Outbound) 15

You might also like