Friday, October 2, 2026

Easy way to default Disbursement Bank Account on Payments

Sometimes the most useful Oracle Fusion functionality is the one that's been sitting quietly in the application for years, waiting for the right business requirement.Recently, while working with a client, we encountered a requirement to automatically default the disbursement bank account during the payment process based on the Business Unit and, in some cases, the Balancing Segment Value (BSV) associated with the transaction. Instead of building a custom solution, we explored Oracle Payments and rediscovered the ORA_IBY_DEFAULT_BANK_ACCOUNT lookup.

Interestingly, this functionality has existed in Oracle Fusion for quite some time, but many implementations never leverage it because a single legal entity often operates with one primary payment bank account. As organizations grow and introduce multiple legal entities, business units, and cash management strategies, the need for intelligent bank account selection becomes much more relevant.

Consider the following scenario- not exact but similar :)

Business Unit

BSV

Bank Name

US Operation

100

BoA

Canada Operation

200

RBC

UK Operation

300

HSBC

The client wanted Oracle Fusion Payments to automatically select the correct disbursement bank account during payment processing based on the originating Business Unit or Balancing Segment.

Without automatic defaulting, payment administrators would have to manually choose the correct bank account during each payment run, increasing both effort and risk of error.

Though challenging, I did extensive research just to find one hidden functionality of Oracle Fusion ORA_IBY_DEFAULT_BANK_ACCOUNT is a lookup used within Oracle Payments to determine the default disbursement bank account for supplier payments. It allows Oracle Payments to evaluate transaction attributes and derive an appropriate internal bank account during payment processing.Common selection criteria may include Business Unit, Legal Entity,  Payment Method, Process Profile, BSVThe result is a more automated and controlled payment process. Payment i.e. ORA_IBY_DEFAULT_BANK_ACCOUNTAssume that the client has a specific requirement i.e. Invocies from Business Unit A needs to be paid from Bank Account A, Business Unit B needs to be paid from Bank Account B and so on.During Payment Process when Payment process is created – Oracle evaluates the lookup rules and identifies the Business Unit and Defaults the Bank Account associated with it from the lookup. Sounds Fun Right!! Similarly, when client wants to drive bank account selection based on BSV Oracle Payments can be configured to derive a value representing the balancing segment and use that value during bank account determination.

However as easy this functionality sounds- there are some challenges i.e. what happens if my Invoice has multiple Balancing segments (Intercompany Invoice,etc.) Oracle Payments ultimately selects a single disbursement bank account for a payment.

Because of this, organizations should establish a business rule such as:

-          1.) Use the primary BSV 2.) Use the highest dollar amount BSV 3.) Restrict Invoices to Single BSV 4.) Default based on BU rather than BSV. This decision should be made during solution design to avoid ambiguity during payment processing.

Benefits of this solution include Improved Automation, Better Controls, Simplified Payment Processing and Scalabiltiy.

 Lets look at the configurations for the same:

 Navigation:

 Setup and MaintenanceàFinancialsàPayments->Manage Disbursement Lookups

Search for the lookup ORA_IBY_DEFAULT_BANK_ACCOUNT and populate the values

Lookup Code and Meaning—Balancing Segment Value

Description: Bank Account

 

Create your payment process Template

Ensure Disbursement Account is blank

 

This requirement was a great reminder that Oracle Fusion often provides the framework needed to solve a business problem without resorting to extensive customizations.

In our client's case, the ability to default disbursement bank accounts based on Business Unit and Balancing Segment was already available through Oracle Payments. The functionality had technically existed all along, but because previous implementations relied on a single operating bank account, it was never utilized.

As organizations expand and banking structures become more sophisticated, revisiting features like ORA_IBY_DEFAULT_BANK_ACCOUNT can unlock automation, strengthen controls, and significantly improve the payment process with minimal configuration effort.

 

You can find more information on this functionality using Oracle Notes:

https://docs.oracle.com/en/cloud/saas/financials/26c/fappp/automatic-population-of-bank-accounts-by-company-codes.html#Multiple-Ledgers-Use-Different-Company-Codes

No comments:

Accounting Hub Transformation Rules: Where the Magic Really Happens in Oracle Fusion Accounting Hub (Part 3)

  In the first two blogs of this series, I covered what Oracle Fusion Accounting Hub is and how transactions flow from source systems into S...