Multiple Line Transaction String Handling Rules are not evaluating and matching invoices to receipts
Summary:
Multiple Transaction String Handling rules configured within an AutoMatch Rule Set are not being evaluated as expected during receipt-to-transaction matching in Oracle Fusion Receivables. When multiple rules are configured, receipts fail to match corresponding AR transactions even though the transformed values should result in a valid match. Testing indicates the functionality works when only a single Transaction String Handling rule is configured.
Content (please ensure you mask any confidential information):
Please review attached screenshot showing the issue: 4-0002478986.docx
Link: https://analysiscenter.oraclecorp.com/?contextType=SR&contextId=4-0002478986&collectionId=5484905
Environment is using Oracle Fusion Receivables AutoMatch functionality with Transaction String Handling rules configured to remove leading characters from transaction numbers during receipt matching.