Service excellence continuing investments

Our ongoing investment in service excellence has a focus on overall usability, resiliency, performance, and security. This work is based on monitoring performance trends, reviewing common use patterns, analyzing service requests, and participating in many discussions with customers.

Usability:

Credit to Cash - Receivables Invoice Processing:

  • You can now use Waybill Number (WAYBILL_NUMBER) as an optional AutoInvoice grouping attribute. When you include Waybill Number in a grouping rule and assign that rule to a transaction source, AutoInvoice groups interface lines with the same waybill number value into the same customer invoice. This helps align invoices with shipment documents and supports reconciliation by waybill number. This feature is automatically available and no opt-in is required.

How to use this feature:

1. Navigate to Manage AutoInvoice Grouping Rules.
2. Create or edit a grouping rule.
3. Select WAYBILL_NUMBER in the optional grouping attributes.
4. Assign the grouping rule to the required transaction source.
5. Run Import AutoInvoice.

What this feature does:

  • Groups interface lines into a single invoice when the waybill number value matches and the other grouping attributes also match.
  • Prevents lines with different waybill number values from being grouped on the same invoice when Waybill Number is part of the grouping rule.
  • Does not change existing AutoInvoice behavior when Waybill Number is not included in the grouping rule.

Credit to Cash - Receivables Invoice Processing:

  • Use the Exclude from Revenue Management Processing option on standard memo lines to control whether standard memo line transaction lines created through AutoInvoice are sent to Revenue Management. Currently, lines associated with memo line types other than Line are by default excluded from both tax calculation and Revenue Management processing, while lines associated with a memo line of type Line are eligible for both. By setting this option to Yes, you can use a standard memo line of type Line, for example, to exclude non-revenue charge amounts from Revenue Management processing, while the remaining transaction lines follow standard Receivables processing. When a transaction line references a memo line with this option enabled, Receivables doesn't populate the Revenue Management eligibility attributes. As a result, the line continues through tax calculation, accounting, and General Ledger posting, but isn't extracted by Revenue Management.

Steps to Enable:

      1. Navigate to Manage Standard Memo Lines.

      2. Create or edit a memo line of type Line.

     3. Set Exclude from Revenue Management Processing to Yes and Save.

     4. Use this memo line for transaction lines with non-revenue charge amounts.

Record to Report - Accounting Processing:

  • Enhanced Journal Summarization for Direct Transfer enables each Create Accounting sub-process to use the General Ledger Transfer Processing Unit Size when summarizing and transferring journals to General Ledger. Previously, when Direct Transfer was enabled and Create Accounting was submitted with Transfer to General Ledger set to Yes, the system used the Create Accounting Processing Unit Size and ignored the General Ledger Transfer Processing Unit Size.

This feature provides a higher degree of journal summarization and reduces the number of General Ledger journals while retaining the processing efficiency and architectural benefits of directly transferring accounting entries to General Ledger. When the Autonomous and Elastic Scaling for Create Accounting feature is enabled along with Direct Transfer, the number of General Ledger journal batches can increase significantly. Performance improvement should be the key consideration while enabling Autonomous and Elastic Scaling for Create Accounting along with Enhanced Journal Summarization for Direct Transfer.

This  feature can be enabled by adding lookup code XLA_37404860 under lookup type ORA_ERP_CONTROLLED_CONFIG on the Manage Standard Lookups page.

Performance:

Record to Report - Accounting Processing:

  • Autonomous scaling for Create Accounting enables the system to automatically determine and apply the optimal number of workers, or subprocesses, for each process execution based on transaction data characteristics and available system resources. Retain the default number of workers in Manage Subledger Accounting Options. The system intelligently scales resources for each accounting process submission based on transaction volumes, data characteristics, and system resource availability. It automatically adjusts the number of workers between runs to improve processing throughput. Existing processing unit sizes remain applicable, and scaling also applies to General Ledger transfer when Direct Transfer is enabled. This feature Eliminates ongoing manual tuning, improves performance across varying workloads, and reduces administrative overhead.

This feature is enabled by default for new customers from Release 26A. Existing customers can enable it by adding lookup code XLA_36852861 under lookup type ORA_ERP_CONTROLLED_CONFIG on the Manage Standard Lookups page.

Enhancement:

Procure to Pay - Payables Invoice Processing:

  • The Validate Payables Invoices process includes an optional enhancement that automatically enables parallel invoice validation for large requests submitted with a single worker. When this feature is enabled, the application evaluates the number of invoices and available scheduler resources. If sufficient capacity is available, invoice validation is distributed across multiple workers to improve performance. Customers who do not enable this feature continue to use the existing single-worker processing behavior. By processing large invoice validation requests in parallel, this enhancement can significantly reduce validation time, improve overall processing throughput, and minimize the duration that invoice records remain locked. This helps downstream Payables processes begin sooner and reduces processing delays. If parallel processing resources are unavailable, the process automatically falls back to the existing single-worker behavior. A configurable threshold continues to govern when single-worker processing is used to prevent excessively long-running jobs.

    This  feature can be enabled by adding lookup code AP_39066381 under  the ORA_ERP_CONTROLLED_CONFIG lookup type using the Manage Standard Lookups task.

Regional Compliance & Reporting - Local Compliance & Reporting:

  • JPK VAT File Updates for Poland 2026 Electronic Invoicing Changes: To support Poland’s 2026 electronic-invoicing and JPK_V7M reporting requirements, organizations must report the KSeF number for sales and purchase invoices where available. When an invoice doesn’t have a KSeF number, organizations must report the applicable transaction classification.

The 26C update introduced global descriptive flexfields at the Payables and Receivables transaction-header level for these non-KSeF classifications:

  • OFF for invoices issued during a KSeF system failure that don’t yet have a KSeF number.
  • BFK for paper or electronic invoices issued outside KSeF by taxpayers exempt from using the system.
  • DI for documents other than invoices, including invoices issued in Offline24 mode.

The 26D enhancement extends this support to taxable sales and purchase journals. For internal journal transactions identified with the WEW or RO attributes, the application defaults the non-KSeF indicator to DI. This defaulting helps ensure that taxable sales and purchase journal transactions, which generally represent documents other than invoices, are included correctly in the JPK_V7M tax registers.

Steps to enable and configure

  • Refer to the individual items above for the required setup details.