Oracle Fusion 26A · Transaction Controls

Oracle Transaction Controls 26A Release Intelligence

5 feature changes for Oracle Transaction Controls in 26A — affecting transaction-level risk detection and continuous controls. Analyze release impact, regression risks, affected components and recommended validations.

Analyze Transaction Controls Impact Request Demo
1 High
0 Med-High
3 Medium
1 Low
9 pages
6 APIs
26A Transaction Controls Command Center
LIVE · FEB 2026
Total Features
5
High Severity
1
Affected Pages
9
Affected APIs
6
High1
Med-High0
Medium3
Low1
RELEASE OVERVIEW

What Changed in Oracle Transaction Controls 26A

Oracle Fusion 26A (February 2026) delivers 5 feature changes for Oracle Transaction Controls — covering process logic, accounting rules, integration payloads, security policies and reporting outputs. 1 are marked HIGH severity and require prioritised regression validation before production cutover.

Total Changes
5
High Severity
1
Pages Affected
9
APIs Affected
6

Oracle Transaction Controls 26A Feature Changes

Every Transaction Controls change Oracle shipped in 26A, with severity, affected components, and recommended validations. Combines initial 26A release notes with the latest 26A patch updates.

Enhanced Transaction Control Rule Processing

MEDIUM
Type: Enhancement Optional Opt In

Transaction Control rules now leverage improved rule evaluation engine with optimized performance for high-volume ERP transactions across AP, AR, and Procurement flows Improves speed and accuracy of compliance enforcement in high-volume financial transactions

Pages: Transaction Controls Setup PageRisk Management Dashboard
APIs: REST APIs for Risk Rules (Risk Management Services)
ESS Jobs: ESS: Risk Rule Evaluation Job
Config: Transaction Control RulesCondition SetsRule Sets
Processes: Financial posting controlsupplier transaction validationinvoice hold rules
Test Cases: Validate rule execution timingtest rule trigger on AP invoice creationtest procurement transaction restriction scenarios
Data Objects: FND_TRANSACTION_CONTROLS

Redwood UI Alignment for Controls Setup

LOW
Type: UI Enhancement Opt In Required (UI)

Transaction Controls configuration pages updated to Redwood UI framework for improved usability and simplified rule definition experience Improves usability and reduces configuration complexity for compliance teams

Pages: Transaction Controls SetupRisk Management Workbench
APIs: Risk Management Setup REST APIs
ESS Jobs: ESS: Setup Migration Job
Config: Control Framework Configuration
Processes: Setup of transaction controlsrole-based access configuration
Test Cases: Validate Redwood setup pages load correctlycreate/update/delete control rulesverify role access behavior
Data Objects: FND_RISK_CONTROL_SETUP

Expanded Control Coverage Across Procurement & Payables

HIGH
Type: Enhancement No Opt In Required

Transaction Controls extended to additional validation points in Procurement (PO creation, supplier onboarding) and Payables (invoice validation enhancements) Strengthens financial compliance and reduces fraud/leakage risk in procurement-to-pay process

Pages: ProcurementPayablesRisk Management Pages
APIs: Procurement REST APIsPayables Invoice APIs
ESS Jobs: ESS: Invoice ValidationPO Validation Jobs
Config: Procurement ControlsPayables Controls
Processes: PO approval restrictionsupplier validation blockinvoice hold enforcement
Test Cases: Test PO creation with restricted suppliervalidate invoice hold triggerstest supplier onboarding block rules
Data Objects: PO_HEADERS_ALLAP_INVOICES_ALL (logical mapping)

AI-Assisted Risk Pattern Detection (Controls Insight)

MEDIUM
Type: New Feature Opt In Required (AI features)

AI-driven anomaly detection introduced to highlight unusual transaction patterns that may require additional transaction control rules Helps proactively identify risk gaps before they become compliance issues

Pages: Risk Insights Dashboard
APIs: Risk Analytics REST APIs
ESS Jobs: ESS: Risk Insight Analysis Job
Config: Control Monitoring Dashboard
Processes: Detect duplicate invoicesabnormal supplier activityhigh-risk transactions
Test Cases: Validate anomaly detection accuracysimulate duplicate invoice patternsverify flagged controls
Data Objects: FND_RISK_ANALYTICS

Performance Optimization for Large Rule Sets

MEDIUM
Type: Technical Improvement No Opt In Required

Improved caching and evaluation logic for environments with large number of transaction control rules Ensures scalability for enterprise-grade compliance rule implementations

Pages: Backend Processing (No UI change)
APIs: Internal Risk Engine APIs
ESS Jobs: ESS: Rule Compilation Job
Config: Rule Set Optimization Configuration
Processes: Large-scale rule execution in enterprise ERP setups
Test Cases: Stress test with 1000+ rulesvalidate execution time reductiontest concurrent transactions
Data Objects: FND_TRANSACTION_CONTROL_CACHE

Affected Components Across Transaction Controls 26A

Deduplicated inventory of Transaction Controls components impacted by the 26A release (initial + patch). Use these lists as your regression scope baseline.

Affected Pages

9
Backend Processing (No UI change) Payables Procurement Risk Insights Dashboard Risk Management Dashboard Risk Management Pages Risk Management Workbench Transaction Controls Setup Transaction Controls Setup Page

Affected APIs

6
Internal Risk Engine APIs Payables Invoice APIs Procurement REST APIs REST APIs for Risk Rules (Risk Management Services) Risk Analytics REST APIs Risk Management Setup REST APIs

Affected ESS Jobs

6
ESS: Invoice Validation ESS: Risk Insight Analysis Job ESS: Risk Rule Evaluation Job ESS: Rule Compilation Job ESS: Setup Migration Job PO Validation Jobs

Affected Config Objects

8
Condition Sets Control Framework Configuration Control Monitoring Dashboard Payables Controls Procurement Controls Rule Set Optimization Configuration Rule Sets Transaction Control Rules

Affected Business Processes

12
Detect duplicate invoices Financial posting control Large-scale rule execution in enterprise ERP setups PO approval restriction Setup of transaction controls abnormal supplier activity high-risk transactions invoice hold enforcement invoice hold rules role-based access configuration supplier transaction validation supplier validation block

Recommended Test Cases

15
Stress test with 1000+ rules Test PO creation with restricted supplier Validate Redwood setup pages load correctly Validate anomaly detection accuracy Validate rule execution timing create/update/delete control rules simulate duplicate invoice patterns test concurrent transactions test procurement transaction restriction scenarios test rule trigger on AP invoice creation test supplier onboarding block rules validate execution time reduction validate invoice hold triggers verify flagged controls verify role access behavior

Other Oracle 26A Modules

Continue your 26A release readiness across other Oracle modules.

26A Cash Management Changes
View Analysis
26A Costing Changes
View Analysis
26A Demand Management Changes
View Analysis
26A ERP & AI Agents Changes
View Analysis
Back to 26A Hub

Oracle Transaction Controls 26A FAQs

Common questions from teams preparing for Oracle Transaction Controls 26A.

What changed in Oracle Transaction Controls 26A?
Oracle Fusion 26A (February 2026) introduces 5 feature changes for Oracle Transaction Controls, with 1 flagged HIGH severity by Oracle. Changes touch business processes including Detect duplicate invoices, Financial posting control, Large-scale rule execution in enterprise ERP setups, PO approval restriction and surface on pages such as Backend Processing (No UI change), Payables, Procurement.
How many high-risk changes does Oracle Transaction Controls 26A have?
Oracle marks 1 of the 5 changes as HIGH, 0 as MEDIUM-HIGH, 3 as MEDIUM and 1 as LOW. High-severity items in Transaction Controls typically require comprehensive regression validation before production cutover because they touch core transactional, security or accounting logic.
Which APIs are affected by Oracle Transaction Controls 26A?
Affected APIs include Internal Risk Engine APIs, Payables Invoice APIs, Procurement REST APIs, REST APIs for Risk Rules (Risk Management Services), Risk Analytics REST APIs. Custom integrations consuming these endpoints should be validated against the 26A schema and behavioural deltas during your test pod cycle.
What test cases should run for Oracle Transaction Controls 26A?
SyntraFlow recommends validating Stress test with 1000+ rules, Test PO creation with restricted supplier, Validate Redwood setup pages load correctly, Validate anomaly detection accuracy, Validate rule execution timing. The release-aware test pack is auto-composed by SyntraFlow Release Intelligence based on the 26A impact analysis on your specific tenant.
How does Oracle Transaction Controls 26A differ from 26B?
26A landed February 2026 and 26B follows in May 2026. The 26A Transaction Controls changes establish the baseline that 26B builds on. Validating 26A first ensures a smoother 26B upgrade. Use SyntraFlow Release Intelligence to compare both quarters.

Prepare Oracle Transaction Controls for 26A

Get a tenant-specific 26A Transaction Controls impact assessment and ship targeted regression coverage.

Request Assessment Analyze Transaction Controls Environment