Search Results iby_intermediary_accts

The IBY_INTERMEDIARY_ACCTS table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical component of the Oracle Payments module (IBY), which facilitates payment processing across financial transactions. This table stores intermediary bank account details, acting as a bridge between the payer and payee accounts, particularly in scenarios involving complex payment routing, such as cross-border transactions or multi-tiered banking relationships. Below is a detailed analysis of its structure, purpose, and integration within Oracle EBS. ### **Purpose and Functional Role** The IBY_INTERMEDIARY_ACCTS table is designed to hold metadata about intermediary financial institutions involved in payment workflows. Intermediary accounts are often required when payments must pass through one or more banks before reaching the beneficiary (e.g., correspondent banking in international transfers). This table ensures that Oracle Payments can dynamically route transactions through the correct intermediary institutions, adhering to banking protocols like SWIFT or SEPA. ### **Key Columns and Structure** The table includes columns to capture essential intermediary account attributes: - INTERMEDIARY_ACCOUNT_ID: Primary key, uniquely identifying each intermediary account record. - INTERMEDIARY_BANK_ID: Foreign key linking to IBY_EXTERNAL_PAYEES_ALL or CE_BANK_ACCT_USES_ALL, referencing the intermediary bank’s details. - ACCOUNT_NUMBER: The intermediary’s bank account number. - CURRENCY_CODE: The currency in which the intermediary account operates (ISO format). - ROUTING_NUMBER/SWIFT_CODE: Identifiers for routing payments (e.g., BIC for SWIFT networks). - START_DATE/END_DATE: Defines the validity period of the intermediary account mapping. - CREATED_BY/LAST_UPDATED_BY: Audit columns tracking record creation/modification. ### **Integration with Oracle EBS Modules** 1. **Oracle Payments (IBY)**: The table is queried during payment instruction generation to append intermediary account details to payment files (e.g., XML for SEPA, NACHA for ACH). 2. **Cash Management (CE)**: Validates intermediary accounts against bank master data (CE_BANKS_B and CE_BANK_ACCOUNTS). 3. **Accounts Payable (AP)**: References intermediary accounts when processing international invoices or complex disbursements. 4. **Multi-Org Access Control (MOAC)**: Supports ORG_ID to enforce data segregation in multi-org environments. ### **Configuration and Usage** - **Setup**: Intermediary accounts are configured via Oracle Payments Administrator responsibility, typically under "Payment Administration" > "Bank Accounts." - **Validation**: The IBY_VALIDATE_PUB API validates intermediary account data before committing to the table. - **APIs**: Custom integrations often use IBY_INTERMEDIARY_ACCTS_PUBMIT_PUB to create/update records programmatically. ### **Business Scenarios** 1. **Cross-Border Payments**: For EUR-to-USD transactions, an intermediary bank in Belgium (SWIFT code) may be stored to handle currency conversion. 2. **Layered Banking**: In supply chain finance, a buyer’s bank may route payments via an intermediary to ensure supplier liquidity. 3. **Regulatory Compliance**: Intermediary accounts may be mandated for sanctions screening (e.g., OFAC compliance). ### **Performance and Maintenance** - **Indexing**: The primary key and INTERMEDIARY_BANK_ID are indexed for fast joins with payment instructions. - **Purge Policies**: Obsolete records should be archived using IBY_FD_EXTRACT_UTIL_PUB to maintain performance. ### **Conclusion** The IBY_INTERMEDIARY_ACCTS table is a foundational element in Oracle EBS for enabling compliant, multi-tiered payment processing. Its design ensures flexibility for global banking requirements while integrating seamlessly with core financial modules. Proper configuration and maintenance of this table are essential for organizations leveraging complex payment workflows in Oracle EBS 12.1.1 or 12.2.2.