Postal Address Validation for Cross-Border Payments

To support Cross-Border Payments and Reporting Plus (CBPR+) postal address requirements for ISO 20022 payments, Oracle Payments delivers new predefined CBPR+ payment templates, formats, validations, and payment process profiles for B2B bank partners Bank of America, J.P. Morgan, and PNC Bank.

When customers use these delivered CBPR+ B2B payment artifacts, Oracle Payments validates that the required payment parties have the required postal address information before the payments are generated.

The required postal address fields are:

  • Town or city name and
  • Country code 

The following are the predefined payment formats and payment process profiles:

Bank Partner Payment Format Payment Process Profile
J.P. Morgan JPMC ISO20022 CGI CBPR Format JPMC ISO20022 CGI CBPR
J.P. Morgan JPMC ISO20022 CGI V2 CBPR Format JPMC ISO20022 CGI V2 CBPR
J.P. Morgan JPMC ISO20022 SEPA CBPR Format JPMC ISO20022 SEPA CBPR
PNC Bank PNC ISO20022 CGI CBPR Format PNC ISO20022 CGI CBPR
Bank of America BOFA ISO20022 CGI CBPR Format BOFA ISO20022 CGI CBPR
Bank of America BOFA ISO20022 SEPA CBPR Format BOFA ISO20022 SEPA CBPR

The following predefined validations are added to the new predefined CBPR+ payment formats for B2B bank partners:

  • Payee Address City is Required for Cross-Border Payments 
  • Payee Bank Branch City is Required for Cross-Border Payments 
  • Payee Intermediary Bank 1 City is Required for Cross-Border Payments 
  • Ultimate Payee City is Required for Cross-Border Payments 
  • Payer City is Required for Cross-Border Payments 
  • Ultimate Payer City is Required for Cross-Border Payments 
  • Payer Bank Branch City is Required for Cross-Border Payments

Country code is always available when defining the address. However, city may be optional or not required in the address setup. Therefore, predefined validations are added only for the city.

The new predefined CBPR+ payment formats also support the ISO 20022 <AdrLine> XML tag for up to two address lines, where applicable. Customers using copied or customized templates should review whether equivalent <AdrLine> support is needed in their custom templates.

Validation applies when the payment parties are in different countries, or when the payment service level is URGP, BKTR, or URNS.

For integrated B2B bank partners, Oracle delivers the complete setup, including predefined CBPR+ payment templates, formats, validations, and payment process profiles.

For generic ISO 20022 usage, Oracle delivers the CBPR+ changes in the ISO 20022 CGI 2019 CBPR, ISO 20022 SEPA 2019 CBPR templates and predefined validations. However, payment formats and payment process profiles aren’t seeded for these generic templates.

Business benefits include:

  • Compliance and Risk Reduction: Meets Cross-Border Payments and Reporting Plus (CBPR+) requirement; reduces rejects and repair cases caused by unstructured address data.
  • Operational Efficiency: Improves straight-through processing and minimizes manual interventions.
  • Data Quality and Governance: Enforces consistent structured address capture with auditable validations and controls.

Steps to enable and configure

  • B2B bank partners Bank of America, J.P. Morgan, and PNC Bank don't need to do anything to enable this feature.
  • Customers using generic, copied, or customized ISO 20022 formats must review and create or update their own payment formats, payment process profiles and attach validations at format level as needed.

Tips and considerations

  • To use the delivered CBPR+ validation for integrated B2B bank partners, customers must use the new predefined CBPR+ payment process profiles.
  • Existing customers who use earlier payment process profiles, or customized templates should review their setup and update their payment process request templates, payment process profiles, payment formats, and templates as needed to use the delivered CBPR+ artifacts or equivalent custom changes.
  • Before processing CBPR+ payments, customers should review and update postal address information for all applicable payment parties. Ensure that town or city name and country code are populated for the relevant parties, including payer, payee, intermediary bank, ultimate payer, ultimate payee, payer bank branch, and payee bank branch.
  • Validations run automatically during payment generation.
  • Payments that fail validation can’t proceed until the missing information is provided.
  • If Stop Payments for Review is selected, payments that fail address validation appear on the Resolve Payment Validation Errors page with the corresponding validation errors.
  • To resolve address validation errors:
    1. Navigate to the Resolve Payment Validation Errors page.
    2. Review the error details to identify the missing address fields.
    3. Update the postal address for the identified payment parties with the required data.
    4. Resume the payment for processing after all errors are resolved.

Access requirements

No new access requirements.