Introduction
In today’s fast-evolving financial ecosystem, large enterprises and shared service centers depend on ERP platforms like Oracle Fusion Cloud to automate and simplify vendor payment processes. However, while initiating payments is only the first step, ensuring that those payments are successfully received and processed by banks is equally critical.
This is where payment acknowledgements play a vital role — offering transparency, minimizing risk, and driving operational efficiency. With the help of ISO 20022-based acknowledgements in Oracle Fusion, finance teams now gain near real-time visibility into payment statuses. This feature bridges the communication gap between ERP systems and banks, helping organizations mitigate operational risks and achieve faster, more accurate cash flow management.
Pre-requisites: If you’re reading this, we’ll assume you already speak a bit of the H2H (Host-to-Host) language in Oracle Fusion. That means you’re familiar with the essentials — things like Transmission Configurations, Payment System Accounts, file formats, and Payment Process Profiles.
Oh, and one more thing, make sure your bank speaks ISO 20022 too! You’ll need their support for both payment and acknowledgement files to make the magic happen.
The Evolution of Payment Confirmation in ERP: From Manual Pain to Automated Precision
| Aspect | Life Before ISO Acknowledgements (Manual Pain Points) | The ISO Acknowledgement Feature (A Game Changer) | Why Acknowledgements are Crucial in ERP (Core Value) |
| Confirmation Method | Manual/Delayed: Relying on bank portals, custom middleware (SOA/OIC), or checking end-of-day bank statements. | Automated/Real-Time: Automated upload and parsing of ISO 20022 acknowledgement files. | Instant Verification: Provides confirmation of payment file receipt and detailed processing status from the bank. |
| Key Challenge / Benefit | High Operational Overhead: Required significant manual intervention and custom, bank-specific integrations. | Streamlined Efficiency: Eliminates the need for custom OIC/API workarounds, offering a seeded solution in Oracle Fusion (since Release 23D). | Error & Cash Flow Certainty: Gives immediate visibility of rejections/errors, crucial for accurate cash flow reporting and vendor satisfaction. |
| Visibility & Speed | No Real-Time Insight: Payment status was often delayed until the next business day or through manual checks. | Real-Time Status Updates: Updates payment status directly within the ERP dashboard for immediate insight. | Enhanced Control & Transparency: Offers a higher degree of control and transparency over the entire financial operations cycle. |
| Error Handling | Delayed Detection: Errors or rejections were often found hours or days later. | Automatic Resolution: Features auto-voiding of rejected payments and automatic handling of linked invoices. | Seamless Reconciliation: Greatly improves the reconciliation process and minimizes manual errors. |
| Audit & Control | Lack of Auditability: Exception handling was complex and difficult to track consistently. | Enhanced Traceability: Provides robust audit trails, ensuring every step of the payment cycle is accounted for. | Solid Foundation: Enhances control, transparency, and the reliability of financial operations and auditing. |
ISO 20022 Disbursement Acknowledgement Levels
| Acknowledgment Level | What it Confirms (Oracle Docs) | Consulting Considerations |
| L0 (File Level) | Bank confirms receipt and file syntax is correct. | A successful L0 means nothing about the money movement. Silence after L0 is a potential “silent failure”. |
| L1 (Payment Level) | Bank confirms transactions passed technical/business validation. | Partial Rejection requires immediate AP action. If the rejected invoice is auto-voided, the AP team must handle the accounting consequences of the voided payment and the subsequent re-invoicing/re-payment cycle. |
| L2 (Clearing Status) | List of final rejections after the clearing process. | Critical for reconciliation and treasury, but not all banks provide L2—confirm during testing.
L2 confirmations are especially useful for Cash Management Reconciliation, since they validate whether funds were settled.
|
Enabling ISO Acknowledgements in Oracle Fusion: Setup Guide
Prerequisites for ISO 20022 Acknowledgement Integration in Oracle Fusion
- Secure file transmission with the bank must be established (SFTP, SWIFTNet, or another secure channel).
- The H2H setup must be working for outbound payments and inbound bank files.
- Bank must support ISO 20022 format for payment and acknowledgement files.
Step-by-Step Configuration:
- Manage Payment Systems
- Search for and edit the seeded “ISO20022 Payment System”
- Note down the configuration settings
- Add the required settings to the payment system used for sending payment files, such as:
- Automatic Retrieval Interval (e.g., 30 mins)
- Auto-Voiding Option (Yes/No): If set to Yes, the system will automatically void payments that have a rejection status in the acknowledgement file.
- Acknowledgement Format
- Transmission Configuration (SFTP/HTTPS/UCM)
- Voiding Invoice Action (None / Hold / Cancel)
- Email Notifications toggle
- Payment File Register Format for audit tracking
- Click Save and Accounts. Then we can observe the setting added in the previous step on this page. Input the details as per the requirement as shown below.
- Save & Link to Payment Process Profile
- Ensure the same payment system is selected in the process profile that handles file transmission
Monitoring & Retrieving Acknowledgements
Once a payment is transmitted, it appears under Manage Payment Files as shown below.
Acknowledgements can be retrieved using:
- The Retrieve Disbursement Acknowledgements task
- Manual triggers from the payment files screen
On successful retrieval, the system:
- Updates the payment status
- Reflects acknowledgement details
- Initiates invoice handling based on setup
If acknowledgements cannot be retrieved due to errors or bank-side delays, Force Acknowledgement can be used. However, this should be a last resort to avoid reconciliation mismatches.
Implementation Challenges
| Challenge | Recommendation |
| Bank Interpretation Variations | ISO 20022 is flexible; banks may interpret formats differently. Thoroughly coordinate with the bank and test acknowledgements during SIT/UAT. |
| Auto-Void Strategy | Decide early between ‘Hold’ (faster re-initiation) and ‘Cancel’ (better GL separation but complex re-creation if posted).
|
| Retrieval Performance | Start with 30-minute intervals and adjust based on volume; consider real-time only for high-value urgent payments. |
Conclusion
The introduction of ISO 20022 Acknowledgement Processing in Oracle Fusion Release 23D marks a pivotal enhancement for finance teams and consultants. It eliminates the dependency on custom integrations and manual tracking by enabling secure, real-time, and automated reconciliation between ERP and banks.
This feature not only simplifies payment configuration but also drives operational efficiency, enhances audit capabilities, and reduces reconciliation cycle times — all critical to a modern ERP-driven finance ecosystem.
By embracing this feature, organizations can step confidently into the future of intelligent, integrated, and automated payments.
Akhil has 4 years of experience as an Oracle Fusion Finance Consultant, specializing in Accounts Payable, Cash Management, Fixed Assets, and General Ledger modules. He has strong expertise in implementing and supporting end-to-end finance solutions that optimize processes and improve financial accuracy.
Recent Posts
Categories
Design OfficeLatest News
Website Launch And 3 Lessons From Chandrayan-3
January 16, 2024
Real Time Visibility In Supply Chain
January 16, 2024
