Global ERP Adapter Guide - Credit Transfer - GlobalVersion - Baseline - V2

Implementing J.P.
Morgan Host-to-Host - ERP Adapter

for ISO 20022 [For Oracle ERP Cloud]
Disclaimer
This guide provides an overview of pre-defined ISO XML template developed by J.P. Morgan for use with Oracle®
ERP Cloud software applications (the “J.P. Morgan Host-to-Host – Cloud ERP Adapter”). This guide is confidential
and proprietary to J.P. Morgan and is provided for your general information only. It is subject to change without
notice and is not intended to be legally binding. The J.P. Morgan Host-to-Host – Cloud ERP Adapter described in
this document is subjected to laws and regulations and terms of use. Not all products and services are available in
all locations. Eligibility will be determined by J.P. Morgan Chase Bank, N.A. or its affiliates. Neither J.P. Morgan nor
any of its directors, officers, employees or agents shall incur any responsibility or liability whatsoever to you or any
other parties in respect of the contents of this document or any matters referred to in, or discussed as a result of,
this document. J.P. Morgan makes no representations as to the legal, regulatory, technological, tax or accounting
implications of the matters referred to in this document. It may not be copied, published, disclosed or used, in whole
or in part, for any purpose other than as expressly authorized by J.P. Morgan. Oracle® is the registered trademark
of Oracle and/or its affiliates.
©2020 J.P.Morgan Chase & Co. All rights reserved.
J.P. Morgan Host-to-Host – Cloud ERP Adapter for ISO 20022 Page 1 of 103
Table of Contents
J.P. Morgan Host-to-Host - Cloud ERP Adapter – Introduction .................................................... 5

Overview of Deployment Process .................................................................................................... 6
2.1. Cloud ERP Adapter Setup Process............................................................................................................... 6
2.2. ERP Adapter Resource Roles ....................................................................................................................... 6
Pre-requisites ..................................................................................................................................... 7
3.1. System Requirements ................................................................................................................................... 7
3.2. Technical Resources ..................................................................................................................................... 7
ERP Adapter Deployment ................................................................................................................. 8
4.1. Analyzing & Overriding the default XSL Mapping ......................................................................................... 8
4.2. Importing XSL Template ................................................................................................................................ 8
4.3. Payment Format Setup ............................................................................................................................... 14
4.4. Associating Payment Document to Bank Account ...................................................................................... 16
4.5. Create Payment System Account, Payment Process Profile and Assign Payment Format ....................... 19
4.6. Payment Process Profile ............................................................................................................................. 21
4.7. Create Payment methods............................................................................................................................ 24
4.8. Payment Codes ........................................................................................................................................... 25
Generating ISO 20022 v3 Payment File during Payment Process Request ............................... 28
Appendix........................................................................................................................................... 30
6.1. Global Variables – Default Mapping and Overriding ................................................................................... 30
6.2. Country/Payment Instrument Specific Mapping .......................................................................................... 34
6.3. ERP Adapter – Payment Method & Service Level Code Mapping ............................................................. 38
6.3.1. WHEM ................................................................................................................................................. 38
6.3.2. EMEA .................................................................................................................................................. 39
6.3.3. APAC .................................................................................................................................................. 41
6.3.4. LATAM ................................................................................................................................................ 44
6.4. ERP Adapter – Formatting Payment Reason Codes .................................................................................. 45
6.4.1. WHEM ................................................................................................................................................. 45
6.4.2. EMEA .................................................................................................................................................. 45
6.4.3. APAC .................................................................................................................................................. 46
6.4.4. LATAM ................................................................................................................................................ 48
6.5. ERP Adapter - Formatting Delivery Channel Code ..................................................................................... 49
6.5.1. WHEM ................................................................................................................................................. 49
6.5.2. EMEA .................................................................................................................................................. 50
6.5.3. APAC .................................................................................................................................................. 51
6.5.4. LATAM ................................................................................................................................................ 52
6.6. ERP Adapter - Formatting Bank Instruction Codes..................................................................................... 53
6.7. ERP - Adapter - Field Formatting Requirement - Group Header Level ...................................................... 55
6.7.1. Group Header…Control Fields ................................................................................................................... 55
6.7.2. Group Header…Initiating Party… Name .................................................................................................. 55
6.7.3. Group Header…Initiating Party…Identification….Organization Identification…
Other…Identification (corresponding Scheme Level Code) ................................................................................ 56
6.8. ERP Adapter – Field Formatting Requirement – Payment Information/Batch Level .................................. 58
6.8.1. Payment Information…Payment Method ................................................................................................. 58
6.8.2. Payment Information…Batch Booking..................................................................................................... 59
6.8.3. Payment Type Information…Service Level Code .................................................................................. 60
6.8.4. Payment Type Information…Local Instrument…Proprietary ............................................................. 61
6.8.5. Payment Type Information…Category Purpose…Code ...................................................................... 61
6.8.6. Payment Type Information…Requested Execution Date .................................................................... 62
6.8.7. Debtor…Name ................................................................................................................................................ 62
6.8.8. Debtor…Postal Address .............................................................................................................................. 63
6.8.9. Debtor…Identification…Organization Identification…BIC or BEI ..................................................... 63
6.8.10. Debtor…Identification…Organization Identification…Other…Identification ................................. 64
6.8.11. Debtor Account…Identification…IBAN .................................................................................................... 66
6.8.12. Debtor Account…Identification…Other…Identification ...................................................................... 66
6.8.13. Debtor Account…Type…Proprietary ........................................................................................................ 67
6.8.14. Debtor Account…Currency ......................................................................................................................... 67
6.8.15. Debtor Agent…Financial Institution Id…BIC .......................................................................................... 67
6.8.16. Debtor Agent…Financial Institution Id…Postal Address…Country ................................................. 68
6.9. ERP Adapter - Field Formatting Requirement - Credit Transfer Transaction Information Level................. 69
6.9.1. End to End Identification .................................................................................................................. 69
6.9.2. Service Level…Code ..................................................................................................................................... 70
6.9.3. Local Instrument…Code .............................................................................................................................. 70
6.9.4. Local Instrument…Proprietary ................................................................................................................... 71
6.9.5. Category Purpose…Code ............................................................................................................................ 72
6.9.6. Category Purpose…Proprietary ................................................................................................................. 73
6.9.7. Amount…Instructed Amount & Currency ....................................................................................... 73
6.9.8. Exchange Rate Information…Rate Type .................................................................................................. 73
6.9.9. Charge Bearer .................................................................................................................................... 74
6.9.10. Cheque Instructions…Cheque Type ......................................................................................................... 74
6.9.11. Cheque Instructions…Cheque Number ................................................................................................... 75
6.9.12. Cheque Instructions…Delivery Method…Code ..................................................................................... 75
6.9.13. Cheque Instructions…Delivery Method…proprietary .......................................................................... 75
6.9.14. Cheque Instructions…Maturity Dates ...................................................................................................... 75
6.9.15. Cheque Instructions…Forms Code........................................................................................................... 76
6.9.16. Cheque Instructions…Regional Clearing Zone ..................................................................................... 76
6.9.17. Cheque Instructions…Print Location ....................................................................................................... 77
6.9.18. Ultimate Debtor…Name ................................................................................................................................ 78
6.9.19. Intermediary Agent1 Section............................................................................................................ 78
6.9.20. Creditor Agent…Financial Institution Id…BIC ....................................................................................... 79
6.9.21. Creditor Agent…Financial Institution Id…Clearing System Member Id…Member Id ................... 79
Mapped from Payee Bank – Bank Number or Branch ID based on Variable list. Refer to Global Variables –
Default Mapping and Overriding.............................................................................................................................. 79
6.9.22. Creditor Agent …Financial Institution Id…Name................................................................................... 80
6.9.23. Creditor Agent …Financial Institution Id…Postal Address section .................................................. 80
6.9.24. Creditor …Name ............................................................................................................................................. 80
6.9.25. Creditor…Postal Address ............................................................................................................................ 81
6.9.26. Creditor…Identification…Organization Id…Other…Identification .................................................... 81
6.9.27. Creditor…Country of Residence ................................................................................................................ 83
6.9.28. Creditor…Contact Details…Name ............................................................................................................. 83
6.9.29. Creditor…Contact Details…Email Address ............................................................................................ 84
6.9.30. Creditor Account…Identification…IBAN ................................................................................................. 84
6.9.31. Creditor Account…Identification…Other…Identification .................................................................... 84
6.9.32. Creditor Account…Type…Code................................................................................................................. 85
6.9.33. Creditor Account…Type…Proprietary ..................................................................................................... 86
6.9.34. Ultimate Creditor…Name ............................................................................................................................. 86
6.9.35. Ultimate Creditor…Identification…Other…Identification .................................................................... 87
6.9.36. Instruction for Creditor Agent…Instruction Information ..................................................................... 87
6.9.37. Instruction for Debtor Agent ............................................................................................................ 88
6.9.38. Purpose…Code / Proprietary ...................................................................................................................... 92
6.9.39. Regulatory Reporting…Details…Type ..................................................................................................... 92
6.9.40. Regulatory Reporting…Details…Code ..................................................................................................... 92
6.9.41. Regulatory Reporting…Details…Information ......................................................................................... 93
6.9.42. Tax Section ........................................................................................................................................ 94
6.9.43. Related Remittance Information (First Iteration) ............................................................................ 94
6.9.44. Related Remittance Information (Second Iteration)....................................................................... 95
6.9.45. Remittance Information - Unstructured (Equivalent of Payment Details) ................................... 95
6.9.46. Remittance Information - Structured (First Mapping Iteration - US CQP) ................................... 96
6.9.47. Remittance Information - Structured (Second Mapping Iteration - Denmark ACH).................... 96
6.9.48. Remittance Information - Structured (Third Mapping Iteration - US Auto Dealer Transaction) 96
6.9.49. Remittance Information - Structured (Fourth Mapping Iteration) Invoice Information............... 97
6.9.50. County Specific Localization - Brazil Boleto – Barcode ................................................................ 98
6.9.51. County Specific Localization – Thailand Withholding tax (WHT) ............................................... 100
J.P. Morgan Host-to-Host - Cloud ERP Adapter – Introduction
The J.P. Morgan Host-to-Host - ERP Adapter (“ERP Adapter”) provides clients with an easy-to-use, cost
effective solution to initiate Payments or Direct Debit transactions using industry-standard ISO 20022 formatted
files while minimizing technology development implementation effort at the client’s end.
Oracle ERP Cloud natively supports generation of ISO 20022 formatted files for initiating Payments (ISO XML
pain.001 v3) and Direct Debits (ISO XML pain.008 v2) based on Common Global Implementation - Market
Practice (CGI-MP) guidelines. However, the native/default ISO XML functionality does not fully cater for specific
Payment and Country-level variations (Regulatory, Clearing, Local language and Remittance Advice
requirements to name a few) that Banks and Clearing Houses necessarily require to process these
transactions.
The ERP Adapter builds on XML Publisher Format Template - the standard functionality provided by Oracle
ERP Cloud to meet these requirements need and thus minimizes the development process for clients by
providing an enriched version of the XML Format Template.
Key features of Cloud ERP Adapter are:
• Leverages and built on the baseline of standard Oracle ERP Cloud’s ISO Template “ISO20022CGI.xsl”
• Mapping and data enrichments required for Mandatory, Optional and conditionally determined fields.
• Standard Oracle ERP Cloud’s functionalities such as “Payment Codes Setup” to support transaction data
processing requirement for:
a. Regulatory Purpose Codes

b. Clearing Purpose Codes
c. Instruction for Debtor Agent (Field 72 equivalent in SWIFT MT payment messages)
• Use of Variable-based mapping for certain key output fields to simplify changes required in XSL Mapping
Template wherever needed.
The scope of this guide is to detail the steps required to: (1) deploy the ERP Adapter and (2) to provide some
detail on the overall flow to generate the formatted ISO 20022 Payment files (specifically, pain.001.001.03)
from Oracle ERP Cloud.
Note that all screenshots provided in this document are for reference purposes only and may vary depending
on the client’s specific Oracle ERP Cloud version and/or configuration.
Overview of Deployment Process
2.1. Cloud ERP Adapter Setup Process
Cloud ERP Adapter can be used to generate ISO 20022 pain.001.001.03 in five steps as mentioned
below.
2.2. ERP Adapter Resource Roles

Depending on Countries and Payments Instruments in scope, implementation resources with different
expertise and roles are required for a seamless and efficient ERP Adapter deployment.
Note:
“1” indicates expected efficiency in the steps as compared to conventional implementation.
Pre-requisites
3.1. System Requirements
• ERP Adapter is compatible with Oracle Cloud Application R13 onwards.
• System should have multilingual capabilities to support payment types required in local language
• Pre-requisite country-specific localization setups should be performed. (Example: Brazil Boleto, Thailand
WHT etc.)
3.2. Technical Resources

Finance Consultant
Responsible for performing the following:
• Analyze default mapping provided as a part of XSL Template and suggest defining Variable source as
well as overriding default mapping
• Create BI Publisher Payment Format using template
“JPMC_IBY_ISO_CT_CORE_CLOUD_GLOBAL_V1.6.2_Formatted.xsl”.
• Create and configure Payment Process Profile.
• Create Bank and Bank Branch setup
• Create Disbursement Bank Account, Payment Document and attach Payment Format/Payment Process
Profile required for payment document
• Configure Payment Methods with Output Format Value Mapping
• Create required Payment Setup Codes as per Country and Payment Instrument Requirements.
Technical Consultant - Developer

Responsible for performing the following:
• Define Variables and XSLT code mapping as per business requirements

• Overriding default mapping to meet customized / specific business requirements
ERP Adapter Deployment
4.1. Analyzing & Overriding the default XSL Mapping
The first step in the deployment process of the ERP Adapter is to analyze the default mapping provided as a
part of the Adapter to ensure the consistency among the source fields and the XSL Template mapping. The
primary purpose of this exercise is to:
A. Define Variables in XSL Template based on Country and Payment Method requirements
The ERP Adapter XSL mapping uses a Variable based mapping approach to simplify the mapping changes
needed in the XSL Template. Wherever possible, Oracle ERP Cloud’s standard fields are used to derive
the information needed in the output. However, there are cases where Variables without any source
mapping are used in case there are no standard fields available in Oracle ERP Cloud to supply the required
information.
Additionally, Variables are used to turn On / Off specific parts of the ERP Adapter mapping which needs to
be setup depending on the ISO 20022 output requirement.
B. Identify and override the XSL mapping if required. Refer to the Appendix section for detailed XSL mapping
in the ERP Adapter to identify the source mapping at ISO field level.
4.2. Importing XSL Template
Once XSL Template is finalized, next step is to import XSL into Oracle Cloud BIP server. User responsible for
importing XSL template should have below roles provisioned in Oracle ERP Cloud instance.
• Application Administrator
• Application Developer
• Application Implementation Administrator
• Application Implementation Consultant
• Application Implementation Manager
Steps to import XSL template in Oracle Cloud BIP server
1. From the Oracle Cloud Homepage, navigate to Tools  Reports And Analytics
2. Select “Browse Catalog” to open reporting repository
3. In new window edit URL from “/analytics/saw.dll?catalog” to “/xmlpserver/servlet/catalog” to open

“Reporting Tool”
4. Select “Catalog” to avail the list of available reports
5. Navigate to Shared Folders  Financials  Payments to find “Disbursement Payment File Formats” report
6. To create a copy of “Disbursement Payment File Formats” report, click on More  Customize
7. A copy of “Disbursement Payment File Formats” report will be created in the “Custom” folder Shared
Folders  Custom  Financials  Payments
8. Navigate back to “Analytic Reporting Tool” by replacing URL from “/xmlpserver” to “/analytics”
9. Select “Catalog”
10. Navigate to Shared Folders  Custom  Financials  Payments and click on “Edit” option to upload
template
11. List of templates attached to report can be viewed, click on “Add New Layout” to upload new template
12. In order to upload prepared XSL template, specify necessary details, Upload and Save
a. Layout Name - JPMC Cloud ISO Retrofit Template (Example)

b. Template File - To browse the prepared XSL file
c. Type - XSL Stylesheet (HTML/XML/Text)
d. Locale – English
13. Select “View as list” to change view from Thumbnails to listed view
14. Change default file format to “XML” and click on save, template is successfully uploaded
4.3. Payment Format Setup
Steps to setup Payment Format

1. Select “Setup and Maintenance” from main menu
2. Select “Taskbar” ta avail “Search” option, click on “Search”
3. Search “Manage Formats” and select “Manage Formats” listed under “Name”
4. From dropdown menu of “Select type” select “Disbursement Payment File Formats” and click on “Create”
5. Provide necessary details in new tab, select “Save and Close” to create the Payment format
a. Name - JPMC Cloud ISO Retrofit Template (Example)

b. Code - JPMCCloudISORetrofitTemp (Example)
c. Type - Disbursement Payment File Formats (pre-defined)
d. Message Direction - Outbound (pre-defined)
e. Transformation Program Type - BI Publisher (pre-defined)
f. BI Publisher Template – From dropdown menu select file that was defined in 4.2 “Importing XSL
Template”
4.4. Associating Payment Document to Bank Account
1. Navigate to search menu same as first step of 4.3 “Payment Format setup”, search “Manage Bank
Accounts” and select “Manage Bank Accounts” listed under “Name”
2. Enter Bank name in “Account Name” then select “Search” to avail list of Bank accounts. Select required
Bank Account listed under “Account Name” and then select “Edit”
3. Select “+” to enter details under “Create Payment Document”
4. Provide necessary details, select “OK” and “Save”
a. Payment Document - CT ISO US USO

b. Paper Stock Type - Blank Stock (Pre-defined)
c. Number of Lines per Remittance Stub - (Leave blank)
d. Number of Setup Documents - (Leave blank)
e. Format - Choose the format that was defined in section 4.3 “Payment Format setup”
f. Payment Document Category - (Leave blank)
g. First Available Document Number - 1 (Example)
h. Last Available Document number - (Leave blank)
5. Double check to make sure that document is populated under “Payment Document”
4.5. Create Payment System Account, Payment Process Profile and Assign Payment Format
Steps to create Payment System Account

1. Select “Setup and Maintenance” in Oracle Cloud Homepage
2. Select “Taskbar” ta avail “Search” option, click on “Search”
3. Search and select “Manage Payment systems” similar to first step of 4.3 “Payment Format Setup” and click
on “+”
4. Provide necessary details and select “+” to add “Name”, “Code” and “Data Type”, select “Save and Close”
to complete Payment System creation process
4.6. Payment Process Profile
Payment Process Profile is a payment attribute assigned to documents payable, which specifies handling of
documents payable, payments, and payment instructions by Oracle Payments. It also includes several
information including specifications for payment instruction formatting and transmission.
Steps to create Payment Process Profile and Assign Payment Instruction Format to Payment Process
Profile
1. Sign in as a Setup User in Oracle Cloud application, search and select “Manage Payment Process Profiles”
similar to first step of 4.3 “Payment Format Setup”
2.
2. Provide necessary details to create Payment Process Profile
a. Name - JPMC Cloud ISO Retrofit PPP (Example)

b. Code - JPMCCloudISORetrofitPPP (Example)
c. From Date - Date will be set by default
d. Payment File Format - JPMC Cloud ISO Retrofit Template (Example)
e. Processing Type - Electronic
f. Payment Confirmation Point - When the payment file is transmitted
g. Select the “Usage Rules” tab and select option “All” for Payment Methods, Disbursement Bank Accounts,
Business Units and Currencies
Note:
Select “Specify” option to limit the use of this profile to payments that have specific payment methods,
disbursement bank accounts, business units or currencies.
3. Under “Payment System” tab select payment system that was created earlier in “Payment System Account”
section
4. Under “Payment” tab select “Bank charge bearer”, “Delivery channel”, “Payment reason”, “Ultimate Debtor”
by using check box in “Document Grouping Rules” section
5. Under “Payment File” tab select “Group by Business Unit”, “First party legal entity” and “Disbursement bank
account” by using check box in “Creation Rules” section
6. Under “Grouping” tab select “Payment Date”, “Service Level and Delivery Channel”, “Disbursement Bank
Account”, “Category Purpose”, “Ultimate Debtor”, “Settlement Priority” and “Charge Bearer” by using the
check box in “Transaction Grouping Rules” section
7. Select “Save and Close” option available on top right corner of the page to complete procedure.
4.7. Create Payment methods
1. Navigate to search menu same as first step of 4.3 “Payment Format setup”, search “Manage Payment
Methods” and select “Manage Bank Accounts” from the list
2. Select “+” to create new payment method
3. Provide necessary details, “Save and Close” to save the provided details to create new payment method
a. Name - JPMC Global HV TRF (Example)

b. Code - JPGBL_HV_TRF (Example)
c. Description - JPMC Global HV TRF (Example)
d. Alias - TRF (Example)
e. From date - Date will be set by default
4.8. Payment Codes
Oracle ERP Cloud provides four different types of Payment Codes

1. Payment Reason Code
2. Delivery Channel Code
3. Bank Instruction Code
4. Service Level Code
Code creation process for all four codes are elaborated below:
Payment Reason Code:
1. Navigate to search menu same as first step of 4.3 “Payment Format setup”, search “Manage Payment Codes”
and select “Manage Bank Codes” from the list
2. Click on “+" to create new Payment Code, select “Payment Reason Code” from drop down menu of “Type”
and provide necessary details such as “Name”, “Code”, “Type”, “Alias” and “From Date”
3. Select “Save and Close” to save provided details
Delivery Channel Code:
1. Click on “+" to create new Payment Code, select “Delivery Channel Code” from drop down menu of “Type”
Bank Instruction Code:
1. Click on “+" to create new Payment Code, select “Bank Instruction Code” from drop down menu of “Type”
Service Level Code:
1. Click on “+" to create new Payment Code, select “Service Level Code” from drop down menu of “Type” and
provide necessary details such as “Name”, “Code”, “Type”, “Alias” and “From Date”
Generating ISO 20022 v3 Payment File during Payment Process Request
1. Once ERP Adapter is deployed successfully, Oracle Cloud ERP is ready to generate ISO 20022 payment file
as a part of Payment Process Profile. While most of the Payment Process Request configuration remains
same, user needs to specify an additional parameter in order to associate ERP Adapter with the file
generation process
2. Below example shows how to submit a Single Request under Payment Process Request
3. Select “Payables” from Oracle Cloud homepage
4. Select “Taskbar” to avail “Submit Payment Process Request” option, select “Submit Payment Process
Request” listed under “Payments”
5. Provide necessary details under “Submit Payment Process Request” and “Selection Criteria” section
then select “Payment and Processing Option”
6. Provide details under “Payment and Processing Option” section then select “Submit” to complete
“Payment Process Request”
7. Once Payment Process Request task is completed, ISO XML 20022 file will be generated and saved in
defined location
Appendix
6.1. Global Variables – Default Mapping and Overriding
1. Enabling Split Remittance Delivery Information
Depending on service subscription, Variable “SplitRemDlyInfo” can be used to suppress Split Remittance
Delivery information section. Split Remittance Delivery Section (Related Remittance Information group in ISO
XML 20022 message) is primarily used to provide information related to advices delivery attributes such as Email
IDs / Fax Number, Format (PDF / Human Readable etc).
By default, Variable is setup as “Y” indicating that ERP Adapter Template will include Related Remittance
Information group in output file. Setting up Variable as “N” disables the mapping.
2. Enabling Structured Invoice Section
Depending on service subscription and requirement, Variable “StrdInvchk” can be used to suppress Structured
Invoice section. Structured Invoice section primarily includes invoice level details under payment. Some Payment
Instruments such as US Corporate Quick Pay, US Auto Dealer Transaction and Denmark ACH mandatorily
requires this section and switching off this flag will not influence output of Structured Invoice section for these
Payment Instruments.
By Default, Variable is setup as “Y” indicating that ERP Adapter Template will include Structured Invoice section
in output. Setting up Variable as “N” disables mapping.
3. End to End identification
Depending on reconciliation requirements, there may be a need to generate End to End Identification (Transaction
Reference Number) which includes the Entity ID and Year of Payment to make it unique across multiple entities
and fiscal years.
ERP Adapter Template uses the Variable “endtoend” to indicate the formatting of End to End Identification. By
Default, the Variable is setup as “N”.
If Variable is defined as “N” then the output format will be “Payment Reference Number”.
If Variable is defined as “Y” then the output format will be “Payment Reference Number + Last 4 characters of
Legal Entity Internal ID + Year of Payment Date (format – “YY”)”.
4. Creditor Agent  Financial Institution  Member Identification (For Electronic Transfers)
Bank ID, Branch ID or both (Bank ID and Branch ID) will be mapped to either Member Id or Branch ID or both
based on list of Destination bank Country maintained as variable in the Template. Based on the requirements,
the list can be modified and provide ability to maintained different list for different set of Service Level Code and
output requirement.
The variable follows a naming convention where, first 4 characters represents service level code followed by the
mapping procedure where –
BankCdToMMBID – Represents Bank Code will be mapped to Member ID
BankCdBranchNuToMMBID – Represents both Bank Code and Branch Code will be concatenated and mapped to Member ID
BranchNuToMMBID – Represents Branch Number will be mapped to Member ID
BranchNuToBranchId – Represents Branch Number will be mapped to Branch ID field
Default Variable list provided in the XSL Template is as below –
For Service Level Code – NURG
NURGBankCdToMMBID - HK, JP, NZ, KR, TW, TH, MX, SA, CH, ZA, BR, CZ, DK, SE, NO
NURGBankCdBranchNuToMMBID - AU, SG
NURGBranchNuToBranchId - HK, JP, NZ, TW, TH, BR
For Service Level Code – URGP - X-Border Wires
URGPXBordBankCdToMMBID - KR, MX, SA, CH, ZA, CZ, DK, SE, NO
URGPXBordBankCdBranchNuToMMBID - HK, JP, NZ, TW, TH, BR
For Service Level Code – URGP for Domestic Wires
URGPDOMBankCdToMMBID - JP, SA, CH, BR, KR, MX, ZA
URGPDOMBankCdBranchNuToMMBID - AU, TW, HK, NZ, SG, TH
URGPDOMBranchNuToBranchId - JP, BR
For Service Level Code – BKTR
BKTRBankCdToMMBID - MX, BR
BKTRBranchNuToMMBID - US
BKTRBranchNuToBranchId – BR
Variable declaration in template based on country mapping.
Oracle Source:
5. “For Further Credit to (FFC)” scenario
In case of “For Further Credit to (FFC)” scenario, there may be a need to provide final beneficiary’s account
number in “Unstructured/Payment” details. ERP Adapter uses Variable “FFCACCOUNT” to provide flexibility
to define source mapping as per business need. By default, Variable is not mapped.
6.2. Country/Payment Instrument Specific Mapping
1. US Single Use Account – Single Authorization/Multiple Authorization Indicator
ERP Adapter Template uses the Variable “SUAAuthInd” to indicate “US Single Use Account”. In Delivery
channel code meaning field may be defined as “SUA SINGLE” or “SUA MULTIPLE”. If Single Authorization is
selected, variable is assigned as “YES” else if Multiple Authorization is selected variable is assigned as “NO”.
2. US Single Use Account – SUA Pool ID
Variable “SUAPoolId” is used to capture US Single Use Account Pool Id. Oracle Source for this field is alias field
in Delivery channel code and derived based on the below code.
Oracle Source
3. Malaysia NBPS – Creditor Identification
For Malaysia NBPS, Biller Code needs to be provided for payments to be successfully processed. ERP Adapter
sources “Creditor Identification information” from “Payee Legal Entity Registration Number” using Variable
“MYNBPSCRDID”.
4. Taiwan - Creditor Identification
For Taiwan TCH Payments - Receiver Uniform Id needs to be provided for the payments to be successfully
processed. ERP Adapter sources “Creditor Identification information” from “Payee Legal Entity Registration
Number” using Variable “TWGIRCRDID”.
5. Brazil, Chile, Mexico and Argentina - Creditor Identification
For Mexico, Brazil, Chile and Argentina - certain Payment Instruments needs to be provided for payments to be
successfully processed. ERP Adapter sources “Creditor Identification information” from Payee “Tax Registration
Number” using Variable “MXTRFCRDID”, “BRTRFCRDID”, “CLTRFCRDID” and “ARTRFCRDID”, for Mexico,
Brazil, Chile and Argentina respectively.
6. Forms Code for US and Canada Checks
For US and Canada Checks, in case if “Forms Code” are required to be provided in ISO XML to identify unique
account number/signature combinations at printer, Variable “FormsCd” can be used to define an Oracle source
where information is populated. By default, Variable is not mapped.
7. Regional Clearing Zone for APAC Cheques
ERP Adapter uses Variable based approach to define a source or default regional Clearing zone for APAC Paper
Instruments. By default, Variables are not mapped. It is created for the purpose of defining source for Regional
Clearing Zone depending on Country and Instrument specific requirement.
8. Indonesia – Regulatory Reporting Details Type (Creditor Type)
ERP Adapter uses Variable “rrdetyp” to define a source or default Beneficiary Type such as Individual,
Corporation/Company or Government for Indonesia ACH/GIR Payments. By default, Variables is mapped as
“corporation”.
9. Brazil Boleto – Bar Code
Brazil Boleto requires Bar Code to be provided in ISO XML output for payments to be successfully processed.
ERP Adapter uses Variable “BoletoBR” to define an Oracle Cloud ERP source where information is populated.
Refer 6.11 for detailed Brazil Boleto Bar Code setup.
10. Denmark ACH – GIK/FIK Reference number
Denmark ACH requires GIK/FIK reference numbers to be provided in Creditor Reference field under Structured
Invoice section of ISO XML. ERP Adapter uses Variable “DKGIKFIKREF” to define an Oracle source where
information is populated. By default, the Variable is not mapped.
11. US - Auto Dealer Transactions
ERP Adapter uses Variables “AutoDealerVT”, “AutoDealerIV” and “AutoDealerIT” to provide various details
related to Auto Dealer Transactions. Depending on Oracle fields where respective information is populated,
Variable Source needs to be mapped in ERP Adapter Template. Information needs to be provided as -
a. AutoDealerVT - VIN followed by a "*" then Model Year followed by Description

b. AutoDealerIV - Invoice Number
c. AutoDealerIT - Dealer Number
Respective values are mapped in Structured…Referred Document Information…Number with appropriate

qualifier in Structured… Referred Document Information…Type…Code or Proprietary…Code field (VT, IV
or IT).
6.3. ERP Adapter – Payment Method & Service Level Code Mapping
Mentioned below is the detailed information for region wise “Payment Instruments” - “Payment Method” - “Service
Level Code” mapping.
Important – As Oracle Standard setup do not provide for differentiating amongst different types of paper
instruments such as Corporate Cheques, Bank Cheques and FCY Drafts, ERP Adapter Template follows a
workaround of using Service Level Code to identify cheque types
6.3.1. WHEM
Payment Instruments Input ISO XML 20022 Output
Service ISO
Instrument Payment Payment Check
Country Level Service
Description Method Method Type
Code Level Code
Canada GACH Credit TRF NURG TRF NURG
BKTR /
Canada Wire Transfer TRF TRF BKTR / URGP
URGP
Canada Checks CHK CHK
US Book Wire TRF URGP TRF URGP
US CHIPS Wire TRF URGP TRF URGP
US FED Wire TRF URGP TRF URGP
US Wire Auto FX TRF URGP TRF URGP
US ACH CCD Credit TRF NURG TRF NURG
ACH CCD+ Child
US TRF NURG TRF NURG
Support Credit
US ACH CCD+ Credit TRF NURG TRF NURG
ACH CCD+ Credit
Auto Dealer
Transactions - Dealer
Buyback
ACH CCD+ Tax
Credit
US ACH CTX Credit TRF NURG TRF NURG
ACH IAT Credit (No
Cross-Border)
US ACH PPD Credit TRF NURG TRF NURG
US ACH PPD+ Credit TRF NURG TRF NURG
US Corporate Quick Pay TRF NURG TRF NURG
SUA (Single Use
US SUA TRF NURG
Account)
US Checks CHK CHK
Wire Draft (Including
US CHK DRFT CHK DRFT
Auto FX)
6.3.2. EMEA
ISO
Service
Instrument Payment Payment Service Check
Country Level
Description Method Method Level Type
Code
Code
Austria Wire Transfer TRF URGP TRF URGP
Belgium Wire Transfer TRF URGP TRF URGP
Czech
Wire Transfer TRF URGP TRF URGP
Republic
Czech
Czech ACH Credit TRF NURG TRF NURG
Republic
Denmark Wire Transfer TRF URGP TRF URGP
Denmark ACH
Denmark TRF NURG TRF NURG
Credit FIK Type 75
Denmark ACH
Denmark Credit GIK Type 01 TRF NURG TRF NURG
and FIK Type 73
Denmark ACH
Credit GIK Type 04
and 15 and FIK
Type 71
Denmark UDUS
Type 356
Wire Transfer Base
EMEA TRF URGP TRF URGP
Template
EMEA SEPA Credit TRF SEPA TRF SEPA
Book Wire (Not
EMEA available for Cross- TRF BKTR TRF BKTR
Border payments)
EMEA EMEA Draft CHK DRFT CHK DRFT
Estonia Wire Transfer TRF URGP TRF URGP
Finland Wire Transfer TRF URGP TRF URGP
France Wire Transfer TRF URGP TRF URGP
Germany Wire Transfer TRF URGP TRF URGP
Hungary Wire Transfer TRF URGP TRF URGP
Hungary ACH
Hungary TRF NURG TRF NURG
Credit
Ireland Wire Transfer TRF URGP TRF URGP
Italy Wire Transfer TRF URGP TRF URGP
Latvia Wire Transfer TRF URGP TRF URGP
Lithuania Wire Transfer TRF URGP TRF URGP
Netherland
s
Wire Transfer -
Norway TRF URGP TRF URGP
From London
Norway Norway ACH Credit TRF NURG TRF NURG
Norway Norway GIRO CHK DRFT CHK DRFT
ISO
Service
Country Level
Code
Code
Poland Wire Transfer TRF URGP TRF URGP
Poland Poland ACH Credit TRF NURG TRF NURG
Poland ACH SSBE
Poland (Social Security) TRF NURG TRF NURG
JPM Current State
Poland ACH Tax
Poland TRF NURG TRF NURG
JPM Current State
Saudi
SADAD Payments TRF URGP TRF URGP
Arabia
Saudi
Arabia
Saudi Saudi Arabia
TRF NURG TRF NURG
Arabia Salary Payments
Saudi Saudi Arabia -
TRF BKTR TRF BKTR
Arabia Book Transfer
South Africa Wire Transfer TRF URGP TRF URGP
South Africa (ZA)
South Africa TRF NURG TRF NURG
Low Value Credit
Spain Wire Transfer TRF URGP TRF URGP
Sweden Wire Transfer TRF URGP TRF URGP
Sweden Bankgiro
Sweden TRF NURG TRF NURG
and Plusgiro Credit
Sweden Payment
Sweden TRF NURG TRF NURG
to Account
Switzerland Wire Transfer TRF URGP TRF URGP
Switzerland ACH
Switzerland TRF NURG TRF NURG
Credit
Switzerland
Switzerland PostFinance Red TRF NURG TRF NURG
Slip (827)
Switzerland
Switzerland Orange Slip (826) TRF URGP TRF URGP
[Type 1]
UK Faster
UK TRF URNS TRF URNS
Payments Credit
UK Wire Transfer TRF URGP TRF URGP
UK ACH Credit
UK TRF NURG TRF NURG
(BACS)
UK ACH Credit
UK (BACS) to Roll TRF NURG TRF NURG
Number
6.3.3. APAC
ISO
Service
Country Level
Code
Code
Australia Cross Border - TLX TRF URGP TRF URGP
Australia Local Wire - LOC TRF URGP TRF URGP
Australia ACH - GIR TRF NURG TRF NURG
Australia ACH - GIR BPAY TRF NURG TRF NURG
Australia Book Transfer - IAT TRF BKTR TRF BKTR
Australia Bank Cheques - ATK CHK BCHQ CHK BCHQ
Corporate Cheques -
Australia CHK CCHQ CHK CCHQ
CHK
Foreign Currency Draft
Australia CHK DRFT CHK DRFT
- DFT
China Cross Border - TLX TRF URGP TRF URGP
Local Wire - HVPS -
China TRF URGP TRF URGP
GIR
China ACH - BEPS - GIR TRF NURG TRF NURG
Book Transfer - IAT
(For Non-CNY Txns
China TRF BKTR TRF BKTR
only. For CNY - use
GIR)
Hong Kong Cross Border - TLX TRF URGP TRF URGP
Hong Kong Local Wire - LOC TRF URGP TRF URGP
Local Wire X currency -
Hong Kong TRF URGP TRF URGP
TLX
Hong Kong ACH - GIR TRF NURG TRF NURG
Hong Kong Book Transfer - IAT TRF BKTR TRF BKTR
Bank Cheques - ATK -
Hong Kong For CNY Manager’s CHK BCHQ CHK BCHQ
Cheque, use “DFT”
Corporate Cheques -
Hong Kong CHK CCHQ CHK CCHQ
CHK
Hong Kong CHK DRFT CHK DRFT
- DFT
India Cross Border - TLX TRF URGP TRF URGP
India Local Wire - LOC TRF URGP TRF URGP
India NEFT/NACH - GIR TRF NURG TRF NURG
India Book Transfer - IAT TRF BKTR TRF BKTR
India Bank Cheques - ATK CHK BCHQ CHK BCHQ
Corporate Cheques -
India CHK CCHQ CHK CCHQ
CHK
India - DFT CHK DRFT CHK DRFT
ISO
Service
Country Level
Code
Code
Indonesia Cross Border - TLX TRF URGP TRF URGP
Indonesia Local Wire - LOC TRF URGP TRF URGP
Indonesia ACH - GIR TRF NURG TRF NURG
Indonesia Book Transfer - IAT TRF BKTR TRF BKTR
Indonesia Bank Cheques - ATK CHK BCHQ CHK BCHQ
Corporate Cheques -
Indonesia CHK CCHQ CHK CCHQ
CHK
Indonesia - DFT CHK DRFT CHK DRFT
Japan Cross Border - TLX TRF URGP TRF URGP
Local Wire - LOC
Zengin using Phonetic
Japan Language / Pre- TRF URGP TRF URGP
Registration Code &
FXYCS payments
ACH - Multibank
Payment - (Local
Japan TRF NURG TRF NURG
Language/Vendor
Registration Code)
ACH - Zengin using
Local Language or
Japan Vendor Registration TRF NURG TRF NURG
Code (For Phonetic
Language, use LOC)
Japan Book Transfer - IAT TRF BKTR TRF BKTR
Malaysia Cross Border - TLX TRF URGP TRF URGP
Malaysia Local Wire - LOC TRF URGP TRF URGP
ACH - GIR NBPS
Malaysia (National Bill Payment TRF NURG TRF NURG
Scheme)
Malaysia ACH - GIR TRF NURG TRF NURG
Malaysia Book Transfer - IAT TRF BKTR TRF BKTR
Malaysia Bank Cheques - ATK CHK BCHQ CHK BCHQ
Corporate Cheques -
Malaysia CHK CCHQ CHK CCHQ
CHK
Malaysia CHK DRFT CHK DRFT
- DFT
New
Cross Border - TLX TRF URGP TRF URGP
Zealand
New
Local Wire - LOC TRF URGP TRF URGP
Zealand
New
ACH - GIR TRF NURG TRF NURG
Zealand
New
Book Transfer - IAT TRF BKTR TRF BKTR
Zealand
ISO
Service
Country Level
Code
Code
New
Bank Cheques - ATK CHK BCHQ CHK BCHQ
Zealand
New Foreign Currency Draft
CHK BCHQ CHK DRFT
Zealand - DFT
Philippines Cross Border - TLX TRF URGP TRF URGP
Philippines Local Wire - LOC TRF URGP TRF URGP
Local Wire X currency
Philippines TRF URGP TRF URGP
- TLX
Philippines ACH - GIR TRF NURG TRF NURG
Philippines Book Transfer - IAT TRF BKTR TRF BKTR
Philippines Bank Cheques - ATK CHK BCHQ CHK BCHQ
Corporate Cheques -
Philippines CHK CCHQ CHK CCHQ
CHK
Philippines CHK DRFT CHK DRFT
- DFT
Singapore Cross Border - TLX TRF URGP TRF URGP
Singapore Local Wire - LOC TRF URGP TRF URGP
Singapore ACH - GIR TRF NURG TRF NURG
Singapore Book Transfer - IAT TRF BKTR TRF BKTR
Singapore Bank Cheques - ATK CHK BCHQ CHK BCHQ
Corporate Cheques -
Singapore CHK CCHQ CHK CCHQ
CHK
Singapore CHK DRFT CHK DRFT
- DFT
South
Local Wire - LOC TRF URGP TRF URGP
Korea
South
Cross Border - TLX TRF URGP TRF URGP
Korea
South
ACH - GIR TRF NURG TRF NURG
Korea
South
Book Transfer - IAT TRF BKTR TRF BKTR
Korea
Cross Border - TLX -
Taiwan and In-Country non- TRF URGP TRF URGP
TWD Payments
Taiwan Local Wire - FIS - GIR TRF URGP TRF URGP
Taiwan ACH - GIR TRF NURG TRF NURG
Taiwan Book Transfer - IAT TRF BKTR TRF BKTR
Taiwan Bank Cheques - ATK CHK BCHQ CHK BCHQ
Corporate Cheques -
Taiwan CHK CCHQ CHK CCHQ
CHK
Taiwan CHK DRFT CHK DRFT
- DFT
Thailand Cross Border - TLX TRF URGP TRF URGP
Thailand Local Wire - LOC TRF URGP TRF URGP
ISO
Service
Country Level
Code
Code
Thailand ACH - GIR TRF NURG TRF NURG
Thailand Book Transfer - IAT TRF BKTR TRF BKTR
Thailand Bank Cheques - ATK CHK BCHQ CHK BCHQ
Corporate Cheques -
Thailand CHK CCHQ CHK CCHQ
CHK
Thailand CHK DRFT CHK DRFT
- DFT
Vietnam Cross Border - TLX TRF URGP TRF URGP
Local Wire X currency
Vietnam TRF URGP TRF URGP
- TLX
Vietnam ACH - GIR TRF NURG TRF NURG
Vietnam Book Transfer - IAT TRF BKTR TRF BKTR
6.3.4. LATAM
ISO
Service
Country Level
Code
Code
Argentina Wires TRF URGP TRF URGP
Argentina Book Transfer TRF BKTR TRF BKTR
Brazil Wire (TED) TRF URGP TRF URGP
Brazil DOC TRF NURG TRF NURG
Boleto (No Tax or
TRF NURG TRF NURG
Brazil Utility Payments)
Brazil Book Transfer TRF BKTR TRF BKTR
Brazil Bank Check - TLX CHK BCHQ CHK BCHQ
Wire and Book
Chile TRF URGP TRF URGP
Transfer
Mexico Wire (SPEI) TRF URGP TRF URGP
Mexico CECOBAN TRF NURG TRF NURG
Mexico Book Transfer TRF BKTR TRF BKTR
6.4. ERP Adapter – Formatting Payment Reason Codes
• Payment reason codes are generally country-specific identifiers provided by a country's government or
central bank. These codes provide "payment system" or bank with additional details about reason for
payment for regulatory reporting purposes. The purpose of providing Payment Reason Codes required by a
country's payment system or central bank is to specify the reason for payment.
• Depending on Country and Payment Instrument business requirement, Payment Reason Code in “Alias”
needs to be provided as applicable. ERP Adapter Template automatically prioritizes and maps Payment
Reason Code “Alias” Value to either Code or Proprietary field based on the mapping defined.
6.4.1. WHEM
Instrument ISO Structural

Country ISO Output Field Output Requirement
Description Sequence
ACH CCD+ Identifier for Child Support.
US Child Support Purpose…Code 02.17.21.01 Purpose Code to be
Credit populated as "BECH"
Identifier for Tax Payment.
ACH CCD+ Tax
US Purpose…Code 02.17.21.01 Purpose Code to be
Credit
populated as "TAXS"
Category
Auto Dealer Provide the value as "Auto
US Purpose… 02.17.02.04.02
Transaction Dealer Transaction"
Proprietary
4 Characters Transaction
Any (not
Any ACH (not Purpose… Code 02.17.21.01 / Type Purpose Code. If not
covered
covered above) /Proprietary 02.17.02.04.02 provided, defaulted to
above)
"OTHR"
6.4.2. EMEA

Type Purpose Code. If not
EMEA SEPA Credit Purpose…Code 02.17.21.01
provided, defaulted to
"OTHR"
Category 4 Characters Purpose Code
Poland ACH Tax 02.17.02.04.01
Purpose… Code as "TAXS"
Any (not
Any ACH (not Purpose… Code 02.17.21.01 / Type Purpose Code. If not
covered
covered above) /Proprietary 02.17.02.04.02 provided, defaulted to
above)
"OTHR"
6.4.3. APAC

Transaction Type Purpose
Purpose…Code/ 02.17.21.01 /
Australia ACH - GIR Code. If not provided,
Proprietary 02.17.21.02
defaulted to "OTHR"
ACH - BEPS - Purpose…Code/ 02.17.21.01 /
China Code. If not provided,
GIR Proprietary 02.17.21.02
defaulted to "OTHR"
Hong Kong ACH - GIR Purpose…Code 02.17.21.01
"OTHR"
Category 4 Characters Purpose
India Local Wire - LOC 02.17.02.04.01
Purpose…Code Code
NEFT/NACH -
India Purpose…Code 02.17.21.01 provided, defaulted to
GIR
"OTHR". Do not provide for
NACH.
Indonesia ACH - GIR Purpose…Code 02.17.21.01
"OTHR"
Regulatory Purpose Code.
Output formatted as
Book Transfer - Instruction for "/REG/BIDATA, (Country
Indonesia 02.17.20
IAT Debtor Agent Code), (Category),
(Relationship), (Purpose
Code) "
Output formatted as
Cross Border - Instruction for "/REG/BIDATA, (Country
Indonesia 02.17.20
TLX Debtor Agent Code), (Category),
(Relationship), (Purpose
Code) "
Japan ACH - Zengin Purpose…Code 02.17.21.01
"OTHR"
Regulatory
Malaysia ACH - GIR Reporting…Details 02.17.22.03.04 Regulatory Purpose Code
…Code
Regulatory
Bank's Cheque -
Malaysia Reporting…Details 02.17.22.03.04 Regulatory Purpose Code
ATK
…Code
Book Transfer - Instruction for
Malaysia 02.17.20 Output Formatted as
IAT Debtor Agent
"/REG/(Purpose Code)"
Regulatory
Corporate
Cheques - CHK
…Code
Cross Border - Instruction for
Malaysia 02.17.20 Output Formatted as
TLX Debtor Agent
Regulatory
Foreign Currency
Draft - DFT
…Code
New Type Purpose Code. If not
ACH - GIR Purpose…Code 02.17.21.01
Zealand provided, defaulted to
"OTHR"
Philippines ACH - GIR Purpose…Code 02.17.21.01
"OTHR"
Bank's Cheque - Purpose…
Philippines 02.17.21.02 Regulatory Purpose Code
ATK Proprietary
Philippines 02.17.20 Output Formatted as
IAT Debtor Agent
Corporate
Philippines Purpose…Code 02.17.21.01 Regulatory Purpose Code
Cheques - CHK
Philippines 02.17.20 Output Formatted as
TLX Debtor Agent "/REG/(Purpose Code)"
Singapore ACH - GIR Purpose…Code 02.17.21.01
"OTHR"
South Type Purpose Code. If not
ACH - GIR Purpose…Code 02.17.21.01
Korea provided, defaulted to
"OTHR"
3 Characters / 4
Characters Transaction
Taiwan ACH - GIR Type Purpose Code. If not
"OTHR"
Taiwan 02.17.20 Output Formatted as
IAT Debtor Agent
Taiwan 02.17.20 Output Formatted as
TLX Debtor Agent
Thailand ACH - GIR Code. If not provided,
defaulted to "OTHR"

Thailand 02.17.20 Output Formatted as
IAT Debtor Agent
"/REG/TH/(Purpose Code)"

Thailand 02.17.20 Output Formatted as
TLX Debtor Agent
"/REG/TH/(Purpose Code)"
Vietnam ACH - GIR Code. If not provided,
defaulted to "OTHR"
6.4.4. LATAM

Purpose… Code/ 02.17.21.01 / Type Purpose Code. If not
Any ACH
Proprietary 02.17.02.04.02 provided, defaulted to
"OTHR"
6.5. ERP Adapter - Formatting Delivery Channel Code
• Delivery channels are instructions that tell the bank how to make the payment to the payee. A default delivery
channel value can be set on the supplier, supplier address, or supplier site. A value automatically populates
from the lowest of these levels to the invoice in Oracle Fusion Payables. On the invoice, it's displayed with
the "installments" and can be manually overridden there.
• When an installment is paid, the delivery channel is copied from the "document payable" to the payment when
payment documents have the same delivery channel. If you select delivery channel as a grouping rule on the
profile, all documents that share the same delivery channel are grouped into a payment.
• Depending on Country and Payment Instrument requirement, Delivery Channel “Alias” value needs to be
provided as applicable. Refer to J.P. Morgan ISO Client Guides for the list of allowed Purpose Codes.
• ERP Adapter Template maps Delivery Channel “Alias” to either Local Instrument or Cheque Instruction
section of ISO XML based on the mapping defined.
6.5.1. WHEM
Cheque Instruction... Provide Delivery Channel
Canada Checks Delivery Method… 02.17.06.04.02 Format value as the
Proprietary delivery method code
Cheque Instruction... Provide Delivery Channel
US Checks Delivery Method… 02.17.06.04.02 Format value as the
Proprietary delivery method code
Corporate Quick Local Instrument… Provide Delivery Channel
US 02.17.02.03.02
Pay Proprietary Format value as "CQP"
Single Use Local Instrument… Provide Merchant Category
US 02.06.03.02
Account (SUA) Proprietary Code group
US ACH CCD Local Instrument… Provide Delivery Channel
US Credit 02.17.02.03.01
Code Format value as "CCD"
US ACH CCD+
Local Instrument… Provide Delivery Channel
US Child Support 02.17.02.03.01
Credit
US ACH CCD+ Local Instrument… Provide Delivery Channel
US Credit 02.17.02.03.01
US ACH CCD+
Credit Local Instrument… Provide Delivery Channel
US 02.17.02.03.01
Auto Dealer - Code Format value as "CCD"
Dealer Buyback
US ACH CCD+ Local Instrument… Provide Delivery Channel
US Tax Credit 02.17.02.03.01
US ACH CTX Local Instrument… Provide Delivery Channel
US Credit 02.17.02.03.01
Code Format value as "CTX"
US ACH IAT
US Credit (No Cross- 02.17.02.03.01
Code Format value as "IAT"
Border)
US ACH PPD Local Instrument… Provide Delivery Channel
US Credit 02.17.02.03.01
Code Format value as "PPD"
US ACH PPD+ Local Instrument… Provide Delivery Channel
US Credit 02.17.02.03.01
Code Format value as "PPD"
6.5.2. EMEA
Structured…Creditor
ACH Credit FIK Reference 02.17.25.02.03 Provide Delivery Channel
Denmark
Type 75 Information… .02 Format value as "75"
Reference
Structured…Creditor
ACH Credit GIK
Reference 02.17.25.02.03 Provide Delivery Channel
Denmark Type 01 and
Information… .02 Format value as "01" or "73"
FIK Type 73
Reference
ACH Credit GIK Structured…Creditor
Provide Delivery Channel
Type 04 and 15 Reference 02.17.25.02.03
Denmark Format value as "04" or "15"
and FIK Type Information… .02
or "71"
71 Reference
Low Value Local Instrument…
South Africa 02.17.02.03.01 Format value as
Credit Code
"CCD" / “PPD”
Orange Slip Local Instrument… Provide Delivery Channel
Switzerland 02.17.02.03.02
(826) [Type 1] Proprietary Format value as "CH01"
6.5.3. APAC
Bank Cheques - Cheque Instruction...
Australia 02.17.06.04.01 Format value as the
ATK Delivery Method…Code
delivery method code
Corporate Cheque Instruction...
Australia 02.17.06.04.01 Format value as the
Cheques - CHK Delivery Method…Code
Foreign Provide Delivery Channel
Cheque Instruction...
Australia Currency Draft - 02.17.06.04.01 Format value as the
Delivery Method…Code
DFT delivery method code
Hong Kong 02.17.06.04.01 Format value as the
Hong Kong 02.17.06.04.01 Format value as the
Hong Kong Currency Draft - 02.17.06.04.01 Format value as the
India 02.17.06.04.01 Format value as the
India 02.17.06.04.01 Format value as the
India Currency Draft - 02.17.06.04.01 Format value as the
NEFT/NACH - Local
India 02.17.02.03.01 Format value as "ECS". Do
GIR Instrument…Code
not provide for NEFT.
Indonesia 02.17.06.04.01 Format value as the
Indonesia 02.17.06.04.01 Format value as the
Indonesia Currency Draft - 02.17.06.04.01 Format value as the
Malaysia 02.17.06.04.01 Format value as the
ATK Delivery Method…Code delivery method code
Malaysia 02.17.06.04.01 Format value as the
Malaysia Currency Draft - 02.17.06.04.01 Format value as the
GIR NBPS
(National Bill Local Instrument… Provide Delivery Channel
Malaysia 02.17.02.03.02
Payment Proprietary Format value as "NBPS"
Scheme)
ISO
Instrument
Country ISO Output Field Structural Output Requirement
Description
Sequence
New Bank Cheques - Cheque Instruction...
02.17.06.04.01 Format value as the
Zealand ATK Delivery Method…Code
New Cheque Instruction...
Currency Draft - 02.17.06.04.01 Format value as the
Zealand Delivery Method…Code
Philippines 02.17.06.04.01 Format value as the
Philippines 02.17.06.04.01 Format value as the
Cheques - CHK Delivery Method…Code delivery method code
Philippines Currency Draft - 02.17.06.04.01 Format value as the
Singapore 02.17.06.04.01 Format value as the
Singapore 02.17.06.04.01 Format value as the
Singapore Currency Draft - 02.17.06.04.01 Format value as the
South Cheque Instruction... Provide Delivery Channel
Local Wire - LOC 02.17.02.03.01
Korea Delivery Method…Code Format value as "BOKW"
Taiwan 02.17.06.04.01 Format value as the
ATK Delivery Method…Code delivery method code
Taiwan 02.17.06.04.01 Format value as the
Taiwan Currency Draft - 02.17.06.04.01 Format value as the
Thailand 02.17.06.04.01 Format value as the
Thailand 02.17.06.04.01 Format value as the
Thailand Currency Draft - 02.17.06.04.01 Format value as the
6.5.4. LATAM
Brazil Boleto 02.17.02.03.02
Proprietary Format value as "81"
6.6. ERP Adapter - Formatting Bank Instruction Codes
Bank instruction codes are values that contain instructions that must be passed to a bank or financial institution
at payment file level. Up to two bank instructions can be entered on a "Payment Process Profile". When Payment
Process Profile is used during creation of a payment file, bank instruction values are copied directly to it. If
payment format specifies use of bank instructions, values are passed to the bank in header level of payment file.
A. For Indonesia, several regulatory information like Bank instruction code must be provided for Cross border
transaction in ISO field Instruction for Debtor Agent.
Mapping requirement for “Instruction for Debtor Agent” -

/REG/BIDATA, (Country Code), (Category), (Relationship), (Purpose Code) where
a. /REG/BIDATA - Predefined
b. Country Code - Beneficiary Country Code - Payee/Address/Country
c. Category - Variable “bnkinstr1” (Mapped from Bank Instruction 1) - Allowed values -
• "A0" - Individual
• "B0" - Government
• "C1" - Banks - Reporting bank
• "C2" - Banks - Branch/Head Office abroad
• "C9" - Banks - other
• "D0" - Non-bank financial institutions
• "E0" - Company
• “Z9” – Others
d. Relationship - Variable “bnkinstr1” (Mapped from Bank Instruction 1) - Allowed values - “P” for
Parent Company, “T” for Subsidiary Company, “G” for Group and “N” for Non-affiliated
e. Purpose Code - “1XXX”. Variable - “pmtrsncode” (Mapped from Payment Reason Code) Refer to
J.P. Morgan ISO Client Guides for list of allowed purpose code
• Bank Instruction 1:
• Payment Reason Code:
B. Other Originating / Destination Country Specific Requirements (where ISO Service Level code is
URGP or BKTR) - For–
o Bank Instruction 1 (if not used elsewhere) and/or Bank Instruction 2 can be used to pass on the
information to J.P. Morgan. Information supplied in Instruction for Debtor Agent is mapped to Tag 72
of the MT message. Refer to J.P. Morgan ISO Client Guides for list of allowed/required values
Example - For Japan Cross-Border, declaration for /NNKNI/ needs to be provided using bnkinstr1
to indicate that the Payment is not related to North Korea and/or Iran
6.7. ERP - Adapter - Field Formatting Requirement - Group Header Level
6.7.1. Group Header…Control Fields
ISO Message Item ERP Adapter Source Mapping

Message Root
GroupHeader
MessageIdentification PaymentInstructionInfo/InstructionReferenceNumber
CreationDateTime substring(PaymentInstructionInfo/InstructionCreationDate , 1,
string-
length(PaymentInstructionInfo/InstructionCreationDate)-6)
NumberOfTransactions InstructionTotals/PaymentCount
ControlSum format-number(InstructionTotals/TotalPaymentAmount/Value,
'##0.00')
6.7.2. Group Header…Initiating Party… Name
• Applicable - All Countries
• Oracle Source –
 First Priority - “ISO20022_IP_NAME”
 Second Priority - “CGI_INITIATING_PARTY_NAME”
 Last Priority – “Legal Entity Name”
6.7.3. Group Header…Initiating Party…Identification….Organization Identification…
Other…Identification (corresponding Scheme Level Code)
First Iteration
• Oracle Source - Populated with the value “BANK” in case if BANK_IDENTIFIER maintained under
Payment System Account is “BANK” (Used where Initiating Party is a Bank)
Second Iteration
• Applicable – All Countries
• Oracle Source – “ISO2022_IP_OTHERID" maintained under “Payment Instruction Info/Payment System
Account/Account Settings”. Corresponding Scheme Level Code is populated as “BANK” (Used for Ack
Routing Solution)
Third Iteration
• Oracle Source - If available use “CGI_INITIATING_PARTY_OTHRID” maintained under Payment System
Account else use last four characters of InstructionGroup/Payer/LegalEntityInternalID. Corresponding
Scheme Level Code is populated as “BANK” (Used for Ack Routing Solution – Alternate to second iteration)
Fourth Iteration
• Applicable - US Single User Account (SUA)
• Oracle Source - SUA_ORG_ID maintained under Payment System Account if available. Corresponding
Scheme Level Code is populated as “CUST” (Used to provide SUA Organization ID for US Single Use
Transactions)
6.8. ERP Adapter – Field Formatting Requirement – Payment Information/Batch Level
6.8.1. Payment Information…Payment Method

• Oracle Source - Payment Method – Format Value
• Important – Refer section 6.3 “ERP Adapter – Payment Method – Service Level Code” for Country and
Instrument-wise detail for value that needs to be populated in the Payment Method Format Value field
• Formatting – Refer 4.8 Manage Payment Method for “Payment Method/Service Level Code Format
Values”
6.8.2. Payment Information…Batch Booking
• Applicable – All Countries. Not used by J.P. Morgan for processing

• Oracle Source - Batch Booking Flag at Payment Process Profile. Make sure to update as “N” to return
value as “False”, default value when not selected is “True”
6.8.3. Payment Type Information…Service Level Code
• Applicable - Service Level Code at supplier site level is used

• Oracle Source – Supplier  Site  Payment Attribute  Payment Delivery  Service Level
Code
6.8.4. Payment Type Information…Local Instrument…Proprietary
• Applicable - Delivery channel code at supplier site level is used.

• Oracle Source - Supplier  Site  Payment Attribute  Payment Delivery  Delivery Channel
Code
6.8.5. Payment Type Information…Category Purpose…Code
• Applicable - Payment reason code at supplier site level is used.

• Oracle Source - Supplier  Site  Payment Attribute  Payment Specification  Payment
Reason Code
6.8.6. Payment Type Information…Requested Execution Date

• Oracle Source - System Date or Payment Date depending on conditions
• Condition 1 - For APAC Corporate Cheques, If Payment Date is greater than system date, populate
system date (Payment Date is populated in another ISO field)
• Condition 2 - For APAC Corporate Cheques, If Payment Date is NOT greater than system date, populate
Payment Date
• Condition 3 - For all other Countries and Payment types, populate Payment Date
6.8.7. Debtor…Name

• Oracle Source - Debtor Name maintained under Payment System Account else Payer Name
6.8.8. Debtor…Postal Address

• Oracle Source - Payer Address
• Formatting -
• Street Name - Payer/Address/AddressLine1

• Postal Code - Payer/Address/PostalCode
• Town Name - Payer/Address/City
• Country Sub-division - Payer/Address/County + Payer/Address/State + Payer/Address/Province
• Country - Payer/Address/Country
6.8.9. Debtor…Identification…Organization Identification…BIC or BEI
• Applicable - US ACH IAT Credit

• Oracle Source - DEBTOR_ID_BIC maintained under Payment System Account. Other….Identification
is automatically populated as “BANK”
6.8.10. Debtor…Identification…Organization Identification…Other…Identification
• Applicable - Multiple Countries and Payment Types

• Condition 1 - India NACH (User Number allotted by NPCI)
Oracle Source - Account Level EFT Number if available else Bank Branch Level
EFT Number
• Condition 2 - Taiwan TCH - Originator Uniform Identification
EFT Number. Scheme Name code is automatically mapped as “CHID”
• Condition 3 - US ACH (Service Level Code is NURG or URNS) - Company ID. Scheme Name
Proprietary is automatically mapped as “JPMCOID”. Not applicable for SUA and CQP.
EFT Number
• Condition 4 - Poland ACH (Service Level Code is NURG) - Company ID. Scheme Name
Proprietary is automatically mapped as “JPMCOID”
EFT Number
• Condition 5 - Other Countries (Service Level Code is NURG or SEPA or URNS) - Company ID.
Scheme Name Proprietary is automatically mapped as “JPMCOID”
EFT Number
• Condition 6 - Poland ACH (Service Level Code is NURG and Tax Registration Number is
available) - Payer's NIP (Unique Taxpayer Reference). Scheme Name Code is automatically
mapped as “TAXID”
Oracle Source - Payer Tax Registration Number
Account Level EFT Number
Branch Level EFT Number
Tax Registration Number
6.8.11. Debtor Account…Identification…IBAN
• Applicable - All Countries (Except US Single Use Account payments)

• Oracle Source - Payer Bank IBAN
6.8.12. Debtor Account…Identification…Other…Identification

• Oracle Source - Payer Bank Account Number (except US Single Use Account payments) and Account
Level EFT Number (for US Single Use Account)
• Payer Bank Account Number:
• Account Level EFT Number (SUA Pool ID) - Variable - “SUAPoolId” mapped to
BankAccount/EFTUserNumber/AccountLevelEFTNumber
6.8.13. Debtor Account…Type…Proprietary
• Applicable - US Single Use Account

• Oracle Source – ERP Adapter Template uses the Variable “SUAAuthInd” to indicate “US Single Use
Account”. In Delivery channel code meaning field may be defined as “SUA SINGLE” or “SUA
MULTIPLE”. If Single Authorization is selected, variable is assigned as “YES” else if Multiple
Authorization is selected variable is assigned as “NO”.
6.8.14. Debtor Account…Currency

• Oracle Source – Payer Bank Account Currency Code
6.8.15. Debtor Agent…Financial Institution Id…BIC

• Oracle Source - Payer Bank Account Swift Code
6.8.16. Debtor Agent…Financial Institution Id…Postal Address…Country

• Oracle Source - Payer Bank Account Country Code
6.9. ERP Adapter - Field Formatting Requirement - Credit Transfer Transaction Information
Level
6.9.1. End to End Identification

• Formatting - Payment Reference Number or
Payment Reference Number + Last 4 characters of Legal Entity Internal ID + Year of Payment Date
• Oracle Source - Payment Reference Number / Legal Entity Internal Id / Year of Payment Date
• Variables –
“leintid” = InstructionGrouping/Payer/LegalEntityInternalID
“year” = substring(PaymentDate,3,4)
“endtoend” = Flag to trigger Legal Entity Internal Id and Year of Payment concatenation.
Default = “N”
If the flag “endtoend” = “Y” then “Payment Reference Number + Last 4 characters of Legal Entity Internal ID
+ Year (YY) of Payment Date” else Payment Reference Number
Variable in XSL Map –
6.9.2. Service Level…Code

• Oracle Source - Refer ERP Adapter - Payment Method & Service Level Code Mapping section for
additional details on setup and maintenance of Service Level Codes.
6.9.3. Local Instrument…Code
• Applicable - US ACH, South Africa Low Value Credit, India NACH, South Korea Domestic Wires in
KRW
• Oracle Source - Delivery Channel Code Format Value. Refer ERP Adapter - Formatting Delivery
Channel Code section for Additional details
• Variable -
Variable Name Template Mapping
Dlvrchnlcode` DocumentPayable/DeliveryChannel/FormatValue[1]"
if available else DeliveryChannel/FormatValue
• Formatting -
• US ACH - “CCD”, “CTX”, “PPD”, “IAT”, ”SUA”
• For South Africa Low Value Credit - “CCD”, “PPD”
• For India NACH - “ECS”
• For Korea Domestic Wires - “BOKW”
6.9.4. Local Instrument…Proprietary
• Applicable - US CQP, Malaysia NBPS, Brazil Boleto

• Oracle Source - Delivery Channel Code Format Value
• Variable -
dlvrchnlcode DocumentPayable/DeliveryChannel/FormatValue[1]"
• Formatting -
• For US CQP - “CQP”
• For Malaysia NBPS - “NBPS”
• For Brazil Boleto - “81”
6.9.5. Category Purpose…Code
• Applicable - India Domestic Wires, Poland ACH Tax, Czech Republic Domestic Wires
• Oracle Source - Payment Reason Code Format Value
• Variable -
pmtrsncode DocumentPayable/PaymentReason/FormatValue[1]"
if available else PaymentReason/FormatValue
• Formatting - India Domestic Wires -

• "CASH" - Cash Management Transfer
• "CORT" - Trade Settlement Payment
• "DIVI" - Dividend
• "GOVT" - Government Payment
• "HEDG" - Hedging
• "INTC" - Intra Company Payment
• "INTE" - Interest
• "LOAN" - Loan
• "PENS" - Pension Payment
• "SALA" - Salary Payment
• "SECU" - Securities
• "SSBE" - Social Security Benefit
• "SUPP" - Supplier Payment
• "TAXS" -Tax Payment
• "TRAD" - Trade
• "TREA" - Treasury Payment
• "VATX" - Value Added Tax Payment
• "WHLD" - With Holding
• Formatting - Poland ACH Tax - If Payment Reason Code - Format Value Mapping is “TAXS”,
Category Purpose Code is mapped as “TAXS”
6.9.6. Category Purpose…Proprietary
• Applicable - US Auto Dealer Transaction

• Variable -
pmtrsncode DocumentPayable/PaymentReason/FormatValue[1]"
if available else PaymentReason/FormatValue
• Formatting - If Payment Reason Code - Format Value mapping is “AUTO DEALER TRANSACTION”,
Category Purpose - Proprietary is mapped as “Auto Dealer Transaction”
6.9.7. Amount…Instructed Amount & Currency

• Oracle Source - Payment Amount Value and Payment Amount Currency Code
6.9.8. Exchange Rate Information…Rate Type
• Applicable - US Wire and Drafts Auto FX

• Oracle Source – Not Available
• Variable – USExchDff – Not Mapped.
• Formatting -
Rate Sheet Number - /CFR/nn where “nn” is the Rate Sheet Number or /CFR/MMDDYYYY where
“MMDDYYYY” is the date of rate sheet. If provided, Rate Type is populated as “AGRD”
6.9.9. Charge Bearer
• Applicable - All Countries (Except Paper based instruments - Corporate Cheques, Bank Cheques and
Foreign Currency Drafts)
• Oracle Source - Supplier  Site  Payment Attribute  Payment Specification  Bank Charge
Bearer Code
• Variable -
chargbrcode DocumentPayable/BankCharges/BankChargeBearer/FormatValue[1]" if
available else BankCharges/BankChargeBearer/Code
• Formatting -
• If source value is PAYEE then charge bearer is considered as “CRED”
• If source value is PAYER then charge bearer is considered as “DEBT”
• If source value is SHARED then charge bearer is considered as “SHAR”
• By default charge bearer is considered as “CHAR”
6.9.10. Cheque Instructions…Cheque Type
• Applicable - All Countries where ISO Payment Method is CHK

• Oracle Source – Service Level Code
• Variable -
chqtp1 PaymentMethod/PaymentMethodFormatValue
• Formatting -
• If source value is CCHQ then Cheque type is “CCHQ”
• If source value is DRFT then Cheque type is “DRFT”
• If source value is BCHQ then Cheque type is “BCHQ”
6.9.11. Cheque Instructions…Cheque Number
• Applicable - US and Canada Checks, India Corporate Cheques

• Oracle Source - Payment Number - Cheque Number
6.9.12. Cheque Instructions…Delivery Method…Code
• Applicable - All Countries where ISO Payment Method is CHK. Primarily used for APAC countries
• Oracle Source - Delivery Channel Format Value
• Variable -
• Formatting - Four Characters ISO Delivery Method Code, e.g. CRDB, PUDB etc. Refer to J.P. Morgan
ISO Client Guides for list of allowed Delivery Methods for the Country and Check type.
6.9.13. Cheque Instructions…Delivery Method…proprietary
• Applicable - All Countries where ISO Payment Method is CHK. Primarily used for US and Canada
Checks
• Oracle Source - Delivery Channel Format Value
• Variable –
• Formatting - If Format value mapping is not one of ISO external Code values (e.g. CRDB, MLCD etc),
Delivery Method is populated in proprietary field.
6.9.14. Cheque Instructions…Maturity Dates
• Applicable - All APAC Countries where ISO Check Type is Corporate Cheque (CCHQ)
• Oracle Source - Payment Date
6.9.15. Cheque Instructions…Forms Code
• Applicable - US and Canada where Forms Code is provided

• Oracle Source - Open ended mapping using Variable “FormsCd”
• Requirement - Forms Code needed to identify unique account number/signature combinations at the
printer. Depending on field where information is stored, Variable needs to be mapped appropriately.
Alternatively, if only one value is required to be populated, it can be defined directly in XSL Template.
6.9.16. Cheque Instructions…Regional Clearing Zone
• Applicable - All Countries where ISO Payment Method is CHK

• Oracle Source - Descriptive Flex Field / Variable Default / Payee City
• Variable -
printloc Map to an appropriate Oracle Cloud source field
PrtlctnDff Map to an appropriate Oracle Cloud source field

RgnlClrnZnDff Map to an appropriate Oracle Cloud source field
<XX><YYYY>PAYABLE Use this format to declare variables, where <XX> is the Payer Bank
country code, <YYYY> is the ISO Check Type. For example, to default the
Regional Clearing Zone for Singapore Corporate Cheque, use the variable
“SGCCHQPAYABLE”
• All defaulting variables are empty by default in XSL mapping.

• Refer to J.P.Morgan ISO Client Guide or Implementation Manager for list of allowed values for Regional
Clearing Zone by Country / Check Type.
• Formatting -
a. Where Payer Country Code = “IN”
• If Print Location (variable – “printloc”) is Mumbai / Devenahalli / Paranur / New Delhi / Bangalore
/ Delhi / Chennai / Gurgaon / Gurugram / Bengaluru
• Variable “Printloc” may be any location in India. Example: Mumbai/Bengalure/Chennai
• If Payee Address City is same as Print location (Variable – “printloc”) then output is “JPM PAP”
• If ISO Check Type is CCHQ, then output is “MSP PAP”
• If ISO Check Type is BCHQ, then output is “PARDD”
• For other Print Locations (variable – “printloc”)
• If ISO Check Type is CCHQ, then output as “MSP PAP”
• If ISO Check Type is BCHQ, then output as “PARDD”
• If ISO Check Type is DRFT, then
• Variable – “RgnlClrnZnDff” if available else
• Default value provided in Variable – “INDRFTPAYABLE” at XSL Map level
b. For other Countries
• Variable - “RgnlClrnZnDff” if available else
• Default value provided in Variable - “<XX><YYYY>PAYABLE” at XSL Mapping level where
<XX> is the Payer Bank country code, <YYYY> is the ISO Check Type. For example, to default
the Regional Clearing Zone for Singapore Corporate Cheque, use the Variable
“SGCCHQPAYABLE”. All defaulting Variables are empty by default in the XSL mapping.
• By default, there is no mapping in XSL template for this variable.
6.9.17. Cheque Instructions…Print Location

• Applicable - India where ISO Payment Method is CHK
• Oracle Source - Descriptive Flex Field
• Variable -
PrtlctnDff Map to an appropriate Oracle Cloud ERP source

field
• Refer to J.P.Morgan ISO Client Guide or Implementation Manager for list of allowed values for Print
Location for India.
• Formatting -
• If variable “PrtlctnDff” has value then it is considered else default value is “MUMBAI”
6.9.18. Ultimate Debtor…Name
• Applicable - All Countries (If Payer Legal Entity Name is different than Document Payer Legal Entity
name)
• Oracle Source - Document Payer Legal Entity Name. Organization Unit Legal Entity Name under which
Invoice is booked if different from Payer Entity.
6.9.19. Intermediary Agent1 Section
• Applicable - All Countries for Cross Border Transfers where Intermediary Agent 1 is present
• Oracle Source - Intermediate Bank Account 1 Details Section
ISO XML 20022 Field Oracle Source from Intermediate Bank Account 1
IntermediaryAgent1
FinancialInstitutionIdentification
BIC BIC
ClearingSystemMemberIdentification
MemberIdentification Bank Code
Name Bank Name
PostalAddress
TownName City
Country Country
AddressLine IBAN
1. If Branch Number is present but Bank Account number is
not present then “Branch Number ” + <Branch Number>
2. If both Branch Number and Bank Account number is

AddressLine present then “Branch Number ” & <Branch Number> & "
" & “Account “ + <Account Number>
3. If Branch Number is not present and Bank Account

number is present then “Account “ + <Account Number>
6.9.20. Creditor Agent…Financial Institution Id…BIC
• Applicable - All Countries where Payee Bank Swift Code and Country is available (Except US SUA
and CQP)
• Oracle Source - Payee Bank Account Swift Code
6.9.21. Creditor Agent…Financial Institution Id…Clearing System Member Id…Member Id
• Applicable - All Countries with ISO Payment Method as TRF and Payee Bank Country available (Except
US SUA and CQP)
• Oracle Source - Payee Bank Account - Bank Number and / or Branch Number
• Variable -
MmbIdG Mapped from Payee Bank – Bank Number or Branch ID based on Variable list. Refer
to Global Variables – Default Mapping and Overriding
Important -
Country specific Bank Routing Code, e.g. Sort Code, ABA, BSP Code etc. are required in this field depending
on country specific requirements. In case if information is stored in different field, Variable source mapping
needs to be changed accordingly.
6.9.22. Creditor Agent …Financial Institution Id…Name
• Applicable - All Countries where Payee Bank Country is available (Except US SUA and CQP)
• Oracle Source - Payee Bank Account Bank Name
6.9.23. Creditor Agent …Financial Institution Id…Postal Address section
• Applicable - All Countries where Payee Bank Country is available (Except US SUA and CQP)
• Oracle Source - Payee Bank Account Address section
ISO XML 20022 Field Oracle Source from Supplier Bank Details
CreditorAgent
FinancialInstitutionIdentification
PostalAddress
StreetName Bank Address Line 1
PostCode Bank Address Postal Code
TownName Bank Address City
CountrySubDivision Bank Address County, State and Province
Country Bank Address Country
6.9.24. Creditor …Name
• Applicable - All Countries, some countries require local language Beneficiary Name in this field. Refer
to J.P. Morgan ISO Client Guides for local Language requirements
• The creditor name must be provided in local language for few countries. Refer to J.P. Morgan ISO Client
Guides for local Language requirements
• Oracle Source - Payee Name
6.9.25. Creditor…Postal Address
• Applicable - All Countries. Some countries require local language Beneficiary Name in this field. Refer
to J.P. Morgan ISO Client Guides for local language requirements
• Oracle Source - Payee Address
• Formatting -
ISO XML 20022 Field Oracle Source from Supplier Bank Details
Creditor
PostalAddress
StreetName Payee Address Line 1 (Except Norway ACH)
PostCode Payee Address Postal Code
TownName Payee Address City (Except Norway ACH)
CountrySubDivision Payee Address County, State and Province (Which includes US
and CanadaChecks)
Country Payee Address Country
AddressLine Payee Address Line 1 - Norway NURG Only
AddressLine Payee Address City - Norway NURG Only
AddressLine Populated as "South Africa" - South Africa NURG only
6.9.26. Creditor…Identification…Organization Id…Other…Identification
• Applicable - Malaysia GIR & NBPS, Taiwan TCH, Brazil, Mexico, Chile
• Oracle Source -
• Payee Legal Entity Registration Number for Malaysia NBPS and Taiwan
• Payee Bank Address Country for Malaysia GIR
• Payee Tax Registration Number for Brazil and Mexico
• Variable -
MYNBPSCRDID Payee/LegalEntityRegistrationNumber
CdtrIdDff Map to an appropriate Oracle Cloud source field
TWGIRCRDID Payee/LegalEntityRegistrationNumber
BRTRFCRDID Payee/TaxRegistrationNumber
CLTRFCRDID Payee/TaxRegistrationNumber
MXTRFCRDID Payee/TaxRegistrationNumber
• Formatting -
• For Malaysia NBPS - Provide Biller Code in Payee Legal Entity Registration Number
• For Malaysia GIR (Non NBPS) - Provide “RESIDENT/NON-RESIDENT” indicator in variable
“CdtrIdDff”. Scheme Name automatically mapped as “RESIDENT”. If no value available in
Variable, indicator is mapped as “R” indicating the Payee is a resident of Malaysia in case if
Payee Bank Country equals Payer Bank Country (Malaysia), else mapped as “N”
• For Taiwan TCH Payments - Provide Receiver Uniform Id in Payee Legal Entity Registration
Number. Scheme Name automatically mapped as “CUST”
• For Brazil and Mexico - Tax Registration Number, Scheme Name automatically mapped as
“TXID”
6.9.27. Creditor…Country of Residence
• Applicable - Indonesia GIR

• Oracle Source - Map to an appropriate Oracle Cloud ERP source field
• Variable -
CtryOfResDff Map to an appropriate Oracle Cloud source field
• Formatting -
If value provided in Variable - “CtryOfResDff” equals “RESIDENT” or “Resident”, map output as “ID”
else “XX”. If no value provided in Variable, map Payee Address Country
• Important – If information is stored in fields other than XSL Template mapping, it can be overridden by
modifying source of respective variable
6.9.28. Creditor…Contact Details…Name
• Applicable - GIR (NURG) - China, Japan, Korea, Thailand

• GIR (URGP) - Taiwan (FIS)
• ATK - Taiwan, Thailand
• CHK - Hong Kong, Taiwan, Thailand
• Oracle Source - Payee Alternate Name
• Variable -
<XX><YYY><ZZZZ>” This variable is a flag to turn on mapping of Payee Alternate Name to

Contact Details Name. <XX> is the Payer Bank Country Code, <YYY> is
the ISO Payment Method and <ZZZZ> is the ISO Service Level Code or
ISO Check Type. For example, Taiwan corporate cheque uses Variable
named “TWCHKCCHQ” and Thailand GIR uses variable named
“THTRFNURG”
6.9.29. Creditor…Contact Details…Email Address
• Applicable - US Single Use Account and Corporate Quick Pay

• Oracle Source - Payee Email Address under Contact Locators
6.9.30. Creditor Account…Identification…IBAN
• Applicable - Applicable where ISO Payment Method is TRF (Except US SUA and CQP) and when Payee
Bank Account IBAN Number is provided
• Oracle Source - Payee Bank Account IBAN Number
6.9.31. Creditor Account…Identification…Other…Identification
• Applicable - Applicable where ISO Payment Method is TRF (Except US SUA and CQP)
• Oracle Source - Payee Bank Account User Entered Bank Account Number
6.9.32. Creditor Account…Type…Code
• Applicable - India GIR, US ACH, South Africa Low Value Credit

• Oracle Source - Payee Bank Account Type Name
• Formatting –
 India GIR
Derive Account type Code based on Payee Account type Name where
• For India GIR payments, Payee Account Type - SAVING / SAVINGS / SVGS is mapped as “SVGS”,
• CHECKING/CURRENT/OTHER/OTHERS/OTHR is mapped as “CACC”, CASH CREDIT/CASH is
mapped as “CASH” ,
• LOAN is mapped as “LOAN” , NON-RESIDENT is mapped as “NREX” and OVERDRAFT as
“ODFT”
 US ACH
Derive Account type Code based on Payee Account type Name where
• For US ACH payments, Payee Account Type - SAVING / SAVINGS / SVGS is mapped as “SVGS”
and
• CASH CREDIT / CASH is mapped as “CASH”
 South Africa Low Value Credit

Derive Account type Code based on Payee Account type
• For South Africa Low Value Credit payments, Payee Account Type - SAVING / SAVINGS / SVGS is
mapped as “SVGS” and CASH CREDIT / CASH is mapped as “CASH”
6.9.33. Creditor Account…Type…Proprietary
• Applicable - Japan GIR, Hong Kong GIR / FPS

• Oracle Source - Payee Bank Account Type Name
• Formatting -
 Japan GIR
Derive Account Type Proprietary based on Payee Account type Name where
• For Japan GIR Payments, Payee Account type Name SAVING / SAVINGS / SVGS is mapped as
“01” ,
UNKNOWN is mapped as “09” and CHECKING / DDA / CURRENT / CACC / is mapped as “02”
6.9.34. Ultimate Creditor…Name
• Applicable - For wires, where Trading Party Internal ID is different than Payee Internal ID (Remit to
supplier - FFC cases) and (Service Level Code is “NURG” and Country is Singapore) or (Service Level
Code is “URGP”/”BKTR”/”SEPA”) or TH WHT Actual Supplier Name is present
• Oracle Source - Trading Partner Name / TH WHT Alternate Supplier Id
• Variable - Current Version of Oracle Cloud ERP does not support Thailand WHT. A new variable
“Actualsuplrnmdff” is provided which can be used when Thailand WHT is available.
• Formatting -
• FFC cases - If Trading Party Internal Id is different than Payee Internal Id (Remit to Supplier),
map Trading Partner Name to Ultimate Creditor Name
6.9.35. Ultimate Creditor…Identification…Other…Identification
• Applicable - For Wires where Trading Party Internal Id is different than Payee Internal Id (Remit to
supplier)
• Oracle Source - No Default mapping. Open ended Variable
• Variable - FFCACCOUNT
• Formatting -
• Depending on where the information for “For Further Credit to” Account number is stored, the
Variable needs to be mapped to the source accordingly. There information provided here in will
be mapped to Tag 70 of MT messages in the Formatting of /FFC/<Ultimate Creditor Name>
ACCOUNT <FFCACCOUNT>
6.9.36. Instruction for Creditor Agent…Instruction Information
• Applicable - All Countries where service Level code is URGP or BKTR

• Oracle Source - No default mapping
• Variable – InstrForCdtrAgtFormatting -
• Some Beneficiary bank may require specific instruction to be passed on. Variable
“InstrForCdtrAgt” can be used to map Oracle Source to Instruction for Creditor Agent…Instruction
Information ISO node.
6.9.37. Instruction for Debtor Agent
• Applicable - Where (ISO Payment Method = TRF and ISO Service Level code is URGP or BKTR), US
Drafts, Brazil Boleto
• Oracle Source - Payment Reason Code, Bank Instruction 1, Bank Instruction 2, Payee Bank Country
Code, US Exchange Rate Variable, Brazil Boleto Bar Code reserve field
• Variable -
pmtrsncode DocumentPayable/PaymentReason/FormatValue[1]" if available else

PaymentReason/FormatValue
bnkinstr1 /OutboundPaymentInstruction/PaymentInstructionInfo/BankInstruction[1]/Meaning
if available else BankInstruction[1]/Meaning
bnkinstr2 /OutboundPaymentInstruction/PaymentInstructionInfo/BankInstruction[2]/Meaning
if available else BankInstruction[2]/Meaning
bnkinstr3 “/ACC/BENE TEL ” & Payee/ContactInfo/ContactLocators[1]/PhoneNumber

BoletoBR DocumentPayable/BrazilExtend/JLBR_BAR_CODE
USExchDff Used to provide auto FX Rate sheet. Currently not mapped
• Formatting - As multiple fields are required to be mapped to a single field in ISO XML, the ERP Adapter
maps the information in a block of 35 characters in the following priority -
 Priority 1 (Originating Country side Regulatory/Clearing Requirements) -

• For Indonesia where ISO Service Level code is URGP or BKTR, and, both Bank Instruction 1
and Payment Reason Code are provided -
o Mapping requirement for “Instruction for Debtor Agent” -
/REG/BIDATA, (Country Code), (Category), (Relationship), (Purpose Code) where
• /REG/BIDATA - Prefix
• Country Code - Beneficiary Country Code
• Category - Allowed values -
• "A0" - Individual
• "B0" - Government
• "C1" - Banks - Reporting bank
• "C2" - Banks - Branch/Head Office abroad
• "C9" - Banks - other
• "D0" - Non-bank financial institutions
• "E0" - Company
• "Z9" - Others
• Relationship - Allowed values - “P” for Parent Company, “T” for Subsidiary Company, “G” for Group and
“N” for Non-affiliated
• Purpose Code - “1XXX”. Refer to J.P. Morgan ISO Client Guides for the list of allowed purpose code
• The ERP Adapter Mapping -
• /REG/BIDATA - Prefixed
• ISO Country Code - Payee/Address/Country
• Category & Relationship - Variable – “bnkinstr1”
• Purpose Code - Variable - “pmtrsncode”
• For Malaysia (where ISO Service Level code is URGP or BKTR and Payment Reason Code is provided)
• Mapping requirement for “Instruction for Debtor Agent” - /REG/(Payment Reason Format Value
and Payment Reason Meaning) where
• /REG/ - Prefixed
• Purpose Code - Refer to J.P. Morgan ISO Client Guides for the list of allowed purpose
code
• Purpose Code - Variables – “pmtrsncode” and “pmtrsndesc”
• For Philippines and Taiwan (where ISO Service Level code is URGP or BKTR and Payment Reason
Code is provided)
• Mapping requirement for “Instruction for Debtor Agent” - /REG/(Purpose Code) where
• Purpose Code - Refer to J.P. Morgan ISO Client Guides for the list of allowed purpose
code
• Purpose Code - Variable – “pmtrsncode”
• For Thailand (where ISO Service Level Code is URGP or BKTR and Payment Reason Code is provided)
-
• Mapping requirement for “Instruction for Debtor Agent” - /REG/TH/(Purpose Code) where
• /REG/TH/ - Prefixed
• Purpose Code - Refer to J.P. Morgan ISO Client Guides for the list of allowed purpose code
• /REG/TH/ - Prefixed
• Purpose Code - Variable – “pmtrsncode”
• For US (where FX Rate sheet details are provided for Check Type is DRFT or ISO Service Level
code is URGP or BKTR
• Rate Sheet Number - /CFR/nn where “nn” is Rate Sheet Number or /CFR/MMDDYYYY where
“MMDDYYYY” is the date of rate sheet
• If there is value provided in the rate sheet, Exchange Rate Information - Rate Type is populated
as “AGRD”
• For Brazil Boleto (where ISO Service Level Code is NURG and Delivery Channel code is 81) -
• Variable “BoletoBR” is reserved for Brazil Boleto Bar Code.
• Perform Brazil localization setup in Oracle Cloud ERP instance to enable Brazil Boleto Bar Code
• Refer to 6.11 for detailed Brazil Boleto Bar Code setup.
 Priority 2 (Bank Instruction 1 where ISO Service Level code is URGP or BKTR)
• For Originating Country Specific Requirements that are not covered in Priority 1 above - Bank
Instruction 1 can be used to pass on information to J.P. Morgan. Information supplied in
Instruction for Debtor Agent is mapped to Tag 72 of MT message. Refer to J.P. Morgan ISO
Client Guides for the list of allowed/required values.
• Destination Country Specific Requirements / Instruction to Destination Bank - Bank Instruction 1
can be used to pass on the information to the receiving bank. Information supplied in Instruction
for Debtor Agent is mapped to Tag 72 of the MT message. Refer to J.P. Morgan ISO Client
Guides / Global Payments Guide for the list of allowed/required values.
• Important - Not applicable where Payer Bank country is Indonesia, ISO Service Level code is
URGP or BKTR, and, both Bank Instruction 1 and Payment Reason Code are provided as Bank
Instruction 1 is used to provide Originating Country (Indonesia) specific requirement.
 Priority 3 (Bank Instruction 2 where ISO Service Level code is URGP or BKTR ) –
• Destination Country Specific Requirements / Instruction to Destination Bank - Bank Instruction 2

can be used to pass on the information to receiving bank. Information supplied in Instruction for
Debtor Agent is mapped to Tag 72 of the MT message. Refer to J.P. Morgan ISO Client Guides
/ Global Payments Guide for the list of allowed/required values.
 Priority 4 (Bank Instruction Details where ISO Service Level code is URGP or BKTR ) –
• Primarily used for Cross Border Transfers where Destination countries requires Beneficiary
Contact information to be passed on mandatorily.
• ERP Adapter Template maps Bank Instruction details at Supplier Site level to Instruction for
Debtor Agent is mapped to Tag 72 equivalent of MT message. Field may be used to provide
supplier specific information such as Tax IDs, Beneficiary specific IDs required by the destination
Country to process the transactions.
 Priority 5 (Beneficiary Contact number where ISO Service Level code is URGP) –
• Primarily used for Cross Border Transfers where Destination countries requires Beneficiary
Contact information to be passed on mandatorily. ERP Adapter Template maps Payee Contact
number by default to Tag 72 equivalent field with a prefix of “/ACC/BENE TEL “
6.9.38. Purpose…Code / Proprietary
• Applicable - APAC Countries - ACH / GIR, Philippines - Corporate Check and Bank Check, US CCD,
EMEA SEPA
• Variable -

• Formatting -
• Provide ISO Purpose Code in Payment Reason Code Format Value as applicable. Refer to J.P.
Morgan ISO Client Guides for the list of allowed Purpose Codes.
6.9.39. Regulatory Reporting…Details…Type
• Applicable - Indonesia GIR

• Oracle Source - No Default mapping in XSL Template
• Variable - rrdetyp
• Formatting -
• Based on the value provided in the source, XSL mapping outputs the desired code as below -
Individual-1, Corporation-2, Company-2, Government-3
6.9.40. Regulatory Reporting…Details…Code
• Applicable - Norway Cross Border Regulatory VR Code, Malaysia GIR, ATK, CHK & DFT Regulatory
Reporting Code
• Variable -

• Formatting -
• Norway -
• Provide Regulatory Reporting VR Code
• Malaysia-
• Provide Regulatory Purpose Code in Payment Reason Format Value as applicable. Refer to
J.P. Morgan ISO Client Guides for the list of allowed Purpose Codes.
6.9.41. Regulatory Reporting…Details…Information
• Applicable - All Countries Wires where ISO service level code is URGP
• Oracle Source - Payment Text Message (3rd iteration, first two are reserved for Payment details)
• Formatting -
• Provide Regulatory information in Payment Text Message 3 as applicable.
6.9.42. Tax Section
• Applicable - Mexico and TH Withholding Tax

• Oracle Source -
• For Mexico - Tax…Record…Type & Tax…Record…Tax Amount…Total Amount
• If any invoices covered under payment has VAT amount (Tax Type Code contains “VAT”) greater
than 0, Sum of all such VAT amount is mapped to the Total Amount field under Tax section. Tax
Type Code is populated as “VATX”. Information is not available for Thailand WHT in current
version of Oracle Cloud ERP.
6.9.43. Related Remittance Information (First Iteration)
• First iteration of Related Remittance Information section is used to send a copy of the Split Remittance
advice to the Payer Email Address maintained under the contact information section of Oracle Cloud
ERP.
• Applicable - All Countries with Split Remittance Functionality where Split Remittance Delivery
information Variable (SplitRemDlyInfo) at Template Level is Set to “Y”
• Oracle Source -
• Payer/ContactInfo/ContactLocators[1]/EmailAddress
• Payee/Name
• Payee/Address/Country
• Formatting -
• Remittance Id is Defaulted to “PDF/”
• Remittance Location Method is Defaulted to “EMAL”
• Remittance Location Address is mapped as Payer/ContactInfo/ContactLocators/EmailAddress
• Remittance Location Postal Address -
• Name is mapped as Payee/Name
• Country is mapped as Payee/Address/Country
6.9.44. Related Remittance Information (Second Iteration)
• Applicable - All Countries with Split Remittance Functionality where Split Remittance Delivery
information flag ($SplitRemDlyInfo) at Template Level is Set to “Y”
• Payee/RemitAdviceEmail
• Payee/Name
• Payee/Address/Country
• Payee/RemitAdviceDeliveryMethod
• Formatting -
• If RemitAdviceDeliveryMethod is “EMAIL” or Blank and Payee/RemitAdviceEmail is available
• Remittance Id is Defaulted to “PDF/”
• Remittance Location Method is Defaulted to “EMAL”
• Remittance Location Address is mapped as Payee/RemitAdviceEmail
• Remittance Location Postal Address -
• Name is mapped as Payee/Name
• Country is mapped as Payee/Address/Country
6.9.45. Remittance Information - Unstructured (Equivalent of Payment Details)

• Oracle Source - Trading Partner details (For Further Credit to cases), Payment Text Message 1 & 2,
Payment Details Formula created and assigned at Payment Process Profile Level. Depending on the
priority, different information is mapped to Unstructured node is ISO XML upto 140 characters in total.
• Priority 1 - “For Further Credit to” cases - Applicable in case if Payee is different from Trading partner
(for Service Level Code different than URGP and BKTR)
• Priority 2 - “For Further Credit to” cases - Applicable in case if Payee is different from Trading partner
(for Service Level Code NURG, URNS and SEPA) and Variable “FFCACCOUNT” is provided. Mapped
as “ACCOUNT” & <FFCACCOUNT>.
• Priority 3 - Payment Text Message 1 and Payment Text Message 2
6.9.46. Remittance Information - Structured (First Mapping Iteration - US CQP)
• Applicable - US Corporate Quick Pay

• Oracle Source - DocumentPayable/DocumentDescription[1] (first Invoice Document) using Variable
“DocDescrptn”
6.9.47. Remittance Information - Structured (Second Mapping Iteration - Denmark ACH)
• Applicable - Denmark ACH

• Oracle Source - Delivery Channel Code and Variable “DKGIKFIKREF”
• Formatting -
• If Delivery channel code is “01” or “73” - Mapped as Delivery Channel Code & “/”.
• If Delivery channel code is different from “01” or “73” - Mapped as Delivery Channel Code & “/”
& $DKGIKFIKREF (where $DKGIKFIKREF needs to be mapped to an Oracle Field where FIK /
GIK Reference number is populated)
6.9.48. Remittance Information - Structured (Third Mapping Iteration - US Auto Dealer

Transaction)
• Applicable - US Auto Dealer Transactions

• Oracle Source - Mapped using Variables “AutoDealerVT”, “AutoDealerIV” and “AutoDealerIT”
• Formatting -
• Depending on Oracle fields where respective information is populated, Variable Source needs to
be mapped in the Template respectively where there information needs to be provided as -
• “AutoDealerVT” - VIN followed by a "*" then the Model Year followed by Description
• “AutoDealerIV” - Invoice Number
• “AutoDealerIT” - Dealer Number
• Respective values are mapped in Structured…Referred Document Information…Number with
appropriate qualifier in Structured… Referred Document Information…Type…Code or
Proprietary…Code field (VT, IV or IT)
6.9.49. Remittance Information - Structured (Fourth Mapping Iteration) Invoice Information
• Applicable - All Countries where Structured Invoice flag - StrdInvchk is maintained as “Y” at ERP
Adapter Template level (Except US Corporate Quick Pay and Auto Dealer Transaction).
ISO Message Item The ERP Adapter Source Mapping

Strd One Occurrence for each Invoice Document under the Payment
ReferredDocumentInformation
Type
CodeOrProprietary
Code If TotalDocumentAmount/Value > 0 then "CINV" else "CREN"
Number DocumentNumber/ReferenceNumber
RelatedDate DocumentDate
ReferredDocumentAmount
If sum of ITEMS > 0 then
DuePayableAmount translate(format-number(sum(DocumentPayableLine[LineType/Code
= 'ITEM']/LineGrossAmount/Value), '##0.00'), '-', '')
DiscountTaken/Amount/Currency/Code
DiscountAppliedAmount format-number(DiscountTaken/Amount/Value, '##0.00')
If sum of ITEMS < 0 then
CreditNoteAmount translate(format-number(sum(DocumentPayableLine[LineType/Code
= 'ITEM']/LineGrossAmount/Value), '##0.00'), '-', '')
TotalDocumentTaxAmount/Currency/Code and
TaxAmount sum(DocumentPayableLine[LineType/Code =
'TAX']/LineGrossAmount/Value
RemittedAmount PaymentAmount/Currency/Code and PaymentAmount/Value
CreditorReferenceInformation Applicable for US CTX where PO Number is available
Type
CodeOrProprietary
Code
Proprietary Default - “PO”
Issuer
Reference PO Number
CreditorReferenceInformation Applicable for US SUA where PO Number is available
Type
CodeOrProprietary
Code Default - “PUOR”
Proprietary
Issuer
Reference PO Number
CreditorReferenceInformation Applicable for all transaction except US CTX and SUA
Type
CodeOrProprietary
Code Default - “SCOR”
Proprietary
Issuer
DocumentNumber/UniqueRemittanceIdentifier/Number if available
Reference
else DocumentNumber/ReferenceNumber
sum(DocumentPayableLine[(not(LineType/Code = 'TAX') and
AdditionalRemittanceInformation not(LineType/Code = 'ITEM'))]/LineGrossAmount/Value)
& DocumentDescription
6.9.50. County Specific Localization - Brazil Boleto – Barcode
• Brazil Boleto requires Bar Code to be provided in ISO XML output for Payments to be successfully
processed. ERP Adapter uses Variable “BoletoBR” for the ability to define an Oracle Cloud ERP source
where information is populated.
• To generate the Bar Code, Perform necessary localization setups for Brazil.
• Create a custom role with associated Payables Management for Brazil hierarchy role.
• Add custom role to user.
• Custom Role
• Navigate to “Tools” in Oracle Cloud Homepage, Select “Security Console”, Select “Create Role”
under “Roles”
• Localization setup for Brazil Boleto includes following steps:
• Perform required payables configuration to enable interest invoice creation.

• Define common configuration options for Payments and procurement for Brazil business unit.
• Define Work schedule for Brazil.
• Associate Work schedule for Calendar profile.
• Define local holidays for Brazil.
• Use Localization system options to configure Payable Bank Transfer functionality.
• Create Payment format for Brazil.
• Create Payment method for Brazil. Ensure the Payment Method Additional Information is
changed From “Electronic” to “Collection Document”.
• Create a Payment Process Profile for Brazil.
• Perform Collection Document Update Codes.
• Define various controls used by Payable Bank Transfer functionality at supplier level, which
takes precedence over same setup at system option level.
• Define various controls used by the Payable Bank Transfer Functionality at supplier site level,
which takes precedence over same setup at supplier level.
• Define Collection Document Processing Controls at invoice level, which takes precedence over
all other levels.
• Import Collection document manually or automatically by using “Validate and Import Collection
Document” process.
• Open collection document to match invoice manually or automatically.
• Run Payment Process Request to generate the output XML.
• Once necessary localization setups are completed, “Collection Documents for Brazil” menu appears in
payments window Taskbar.
• Refer to oracle Doc ID 2347415.1 (ManagingPayablesCollectionDocumentsforBrazil.pdf) for further help

to perform Brazil localization setup.
6.9.51. County Specific Localization – Thailand Withholding tax (WHT)
• The Below Configurations should be performed for Thailand withholding tax certificate generation.
• Thailand Opt In should be enabled for withholding tax certificate numbering rule and reports.
• Navigation: Navigator –> Setup and Maintenance -> Setup: Financials -> Change Feature Opt
In
• Click pencil for Financials feature followed by pencil for Regional Localization feature.
• Add Thailand and click ‘Save and Close’.
• A new privilege "Process Tax Transactions and Reports for Thailand' should be added to the
existing duty role 'APAC Financial Reporting' for Thailand programs and reports.
• ’APAC Financial Reporting' is not assigned to any job role. Therefore, to use the Thailand feature,
you must assign the duty role to a relevant job role, such as Tax Manager.
• Create address format for Thailand from Manage Address Formats.
• The created address format can be used for Thailand first party (Legal reporting Unit) and third
party sites (Supplier and customer).
• Branch Number should be associated with first party or third party sites for Thailand WHT reports.
• User should create the Tax Reporting Type and codes from Manage Tax Reporting Types.
• If Legal Reporting Unit (First party) or third party site (Third party) does not have the branch
number tax reporting code, then first party or third party will be retrieved as HQ for WHT reports.
• If one Legal Reporting Unit match with multiple branch numbers, then please setup the Legal
Reporting Unit name = report required Legal Reporting Unit name + Branch number (5 digits),
and match with branch numbers (tax reporting code) one by one. WHT reports will not display
the last 5 digits if last 5 digits = matched branch number (tax reporting code).
• Tax Registration Number should be defined for Legal Reporting Unit and Third-Party Site. This
ensures the WHT reports can retrieve the first party tax registration number and third party tax
registration number correctly from invoice header.
• Make sure withholding tax registration number should be same as VAT tax registration number.
• Ensure WHT regime \ Tax \ Tax Status \ Tax Jurisdiction \Tax Rate \Tax are configured in order
to enable WHT.
• Associate the tax reporting type and codes to product category and then enter the product
category into invoice line.
• Enter the basic information for Revenue Type and then click ‘Save and Close’.
• Associate the child node with revenue type tax reporting type and code.
• Sender ID \ Large Business Tax Administration Office \ Branch Type should be associated with
first party for Thailand WHT reports. User should create the Tax Reporting Types and Codes
based on the required words.
• Create for Large Business Tax Administration Office
• Associate the first party with WHT report required tax reporting type and code.
• Create an invoice by entering the appropriate First-Party Tax Registration Number in invoice
header Accounting page and make payment using Payment process profile.
• WHT rate should be associated with PND Type tax reporting code and entered in the AP invoice
tax line.
• Product Category should be associated with Revenue Type tax reporting code and entered in
the AP invoice line.
• Withholding Tax calculation point should be Payment and GDF Condition should be entered in
payment.
• Payments should be posted to ledger.
• Submit the job Withholding Tax Certificate Report for Thailand to generate the withholding tax
certificate.
• Once the job is completed successfully, view the output.
-END OF DOCUMENT-

Global ERP Adapter Guide - Credit Transfer - GlobalVersion - Baseline - V2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Global ERP Adapter Guide - Credit Transfer - GlobalVersion - Baseline - V2

Uploaded by

Copyright:

Available Formats

Implementing J.P.

Morgan Host-to-Host - ERP Adapter

J.P. Morgan Host-to-Host - Cloud ERP Adapter – Introduction .................................................... 5

Key features of Cloud ERP Adapter are:

a. Regulatory Purpose Codes

2.2. ERP Adapter Resource Roles

3.2. Technical Resources

Technical Consultant - Developer

• Define Variables and XSLT code mapping as per business requirements

4.2. Importing XSL Template

2. Select “Browse Catalog” to open reporting repository

3. In new window edit URL from “/analytics/saw.dll?catalog” to “/xmlpserver/servlet/catalog” to open

a. Layout Name - JPMC Cloud ISO Retrofit Template (Example)

Steps to setup Payment Format

2. Select “Taskbar” ta avail “Search” option, click on “Search”

a. Name - JPMC Cloud ISO Retrofit Template (Example)

4. Provide necessary details, select “OK” and “Save”

a. Payment Document - CT ISO US USO

Steps to create Payment System Account

2. Select “Taskbar” ta avail “Search” option, click on “Search”

a. Name - JPMC Cloud ISO Retrofit PPP (Example)

2. Select “+” to create new payment method

a. Name - JPMC Global HV TRF (Example)

Oracle ERP Cloud provides four different types of Payment Codes

Payment Reason Code:

Bank Instruction Code:

3. Select “Payables” from Oracle Cloud homepage

1. Enabling Split Remittance Delivery Information

2. Enabling Structured Invoice Section

4. Creditor Agent  Financial Institution  Member Identification (For Electronic Transfers)

BankCdToMMBID – Represents Bank Code will be mapped to Member ID

BranchNuToMMBID – Represents Branch Number will be mapped to Member ID

BranchNuToBranchId – Represents Branch Number will be mapped to Branch ID field

Default Variable list provided in the XSL Template is as below –

For Service Level Code – NURG

NURGBranchNuToBranchId - HK, JP, NZ, TW, TH, BR

URGPXBordBankCdToMMBID - KR, MX, SA, CH, ZA, CZ, DK, SE, NO

URGPXBordBankCdBranchNuToMMBID - HK, JP, NZ, TW, TH, BR

For Service Level Code – URGP for Domestic Wires

URGPDOMBankCdToMMBID - JP, SA, CH, BR, KR, MX, ZA

URGPDOMBankCdBranchNuToMMBID - AU, TW, HK, NZ, SG, TH

For Service Level Code – BKTR

Variable declaration in template based on country mapping.

1. US Single Use Account – Single Authorization/Multiple Authorization Indicator

2. US Single Use Account – SUA Pool ID

4. Taiwan - Creditor Identification

5. Brazil, Chile, Mexico and Argentina - Creditor Identification

7. Regional Clearing Zone for APAC Cheques

8. Indonesia – Regulatory Reporting Details Type (Creditor Type)

10. Denmark ACH – GIK/FIK Reference number

11. US - Auto Dealer Transactions

a. AutoDealerVT - VIN followed by a "*" then Model Year followed by Description

Respective values are mapped in Structured…Referred Document Information…Number with appropriate

Instrument ISO Structural

Instrument ISO Structural

Instrument ISO Structural

Regulatory Purpose Code.

Regulatory Purpose Code.

Instrument ISO Structural

Mapping requirement for “Instruction for Debtor Agent” -

6.7.1. Group Header…Control Fields

ISO Message Item ERP Adapter Source Mapping

6.8. ERP Adapter – Field Formatting Requirement – Payment Information/Batch Level