FX - INT - 18 FedEx Remittance File To Citibank TSD - v1.3
FX - INT - 18 FedEx Remittance File To Citibank TSD - v1.3
FX - INT - 18 FedEx Remittance File To Citibank TSD - v1.3
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
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
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
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.
● 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.
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
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.
Create a new template (‘MasterCard Remittance File Template’) by uploading the custom eText template
‘XXCorporateCreditCardRemittanceFile.rtf’
Navigation: Setup and Maintenance -> Manage Formats -> Select Type =
‘Disbursement Corporate Credit Card Remittance File’ -> Click on Create button
4. Transmission Configuration
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 “Submit Corporate Card Remittance File” has to be run after the PPR for CCD file is completed.
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”
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
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.
● Access to Corporate Cards setups and ESS jobs are limited to users having the “Card Administrator” role.
● XX
● XX
2.9. Definitions
The lists of all the definitions used in this design document are as follows:
● AP = Accounts Payables
Appendices