Oracle’s April 26 Release: What Transportation Companies Need to Do Now

The Oracle April 2026 release is not a routine patch. For transportation businesses in Brazil, it changes how electronic freight documents are generated, validated, and settled – permanently.

If your business operates in Brazil’s transportation sector, April 26, 2026 is a date that should already be on your project plan. The Oracle April 2026 release introduces significant new functionality to Oracle EBS for Brazilian electronic freight document compliance – specifically, new Events processing and Split Payment capabilities that directly affect how transport invoices are generated, validated, and settled.

This is not a minor update. The Oracle April 2026 release is Oracle’s response to Brazil’s reformed transport invoice compliance framework, which requires transportation companies to manage CBS and IBS tax obligations within their electronic freight documentation. Companies that treat this as a routine patch cycle will find themselves with a very short runway between the release date and the point at which non-compliance attracts real financial consequences.

This blog covers exactly what is changing, what your Oracle EBS team needs to implement, and the common mistakes transportation companies make when they underestimate the scope of the work.

What Is Changing in Oracle’s Transport Invoice Compliance Framework

Brazil’s transport invoice compliance framework has been directly impacted by the country’s broader tax reform under Complementary Law No. 214/2025. The reform replaces the legacy ICMS tax on transport services with the new destination-based IBS (Imposto sobre Bens e Serviços) at state and municipal level, running in parallel with CBS at the federal level. This changes the tax logic, document structure, and payment mechanics for every electronic freight document issued in Brazil.

The Oracle April 2026 release is Oracle’s localisation update that brings Oracle EBS into alignment with these requirements. Until this release, Oracle EBS did not natively support the new CBS/IBS fields, the updated transport invoice XML layouts, the Events framework, or the Split Payment logic required under the reformed compliance model.

Companies affected by this release include:

• Road, rail, air, and waterway freight carriers issuing electronic transport invoices in Brazil
• Shippers and logistics operators who manage freight documentation within Oracle EBS
• Businesses using Oracle EBS for fleet operations or integrated supply chain management in Brazil
• Any company managing transport-related tax obligations across multiple Brazilian states

Changes in Events and Split Payments

The Oracle April 2026 release delivers two major functional additions to Oracle EBS for Brazil transport invoice compliance. Understanding what each one does – and what it requires from your ERP environment – is essential before you begin implementation planning.

1. Transport Invoice Events Framework

Brazil’s updated transport invoice compliance model introduces a formal Events framework that tracks the lifecycle of a freight document beyond its initial issuance. Events include:

• Cancellation events: Formal XML-based cancellation of a transport invoice within the permitted window, with SEFAZ authorisation required
• Correction events (EPEC – Evento Prévio de Emissão em Contingência): Used when the primary SEFAZ authorisation channel is unavailable
• Transport closure events (MDF-e linkage): Linking transport invoices to the electronic freight manifest
• Tax substitution events: Triggered when IBS liability transfers between parties in the supply chain

In Oracle EBS, supporting these events requires module-level reconfiguration to enable event-trigger logic, outbound XML generation for each event type, and real-time integration with SEFAZ’s authorisation web services. This is not achievable through a middleware fix alone – the ERP itself must be updated.

2. Split Payment

Split Payment is described by analysts as one of the most structurally significant aspects of Brazil’s tax reform. Rather than requiring businesses to collect CBS and IBS from customers and remit separately to tax authorities, Split Payment automates the tax diversion at the moment of financial settlement.

Under Split Payment, when a payment is processed – whether via Pix, card, or bank transfer – the system automatically separates the CBS/IBS tax component and directs it to the relevant government accounts in real time. The net commercial amount flows to the supplier. This creates a direct link between the electronic transport invoice, the payment system, and the tax authority’s collection infrastructure.

The Oracle April 2026 release configures three Split Payment operational modes within Oracle EBS:

• Standard B2B: Full CBS/IBS split at the point of payment for business-to-business transactions
• Simplified B2C: A streamlined split for consumer-facing transport transactions
• Acquirer Collection: Tax collected and remitted directly by the payment acquirer (card networks, Pix processors)

Each mode requires specific ERP tax logic, payment integration configuration, and invoice field mapping within Oracle EBS. The cash flow implications are also material: because tax is diverted at payment rather than remitted in a subsequent period, companies need to recalibrate their working capital planning.

Implementation Timeline: What Your ERP Team Needs to Plan For

The Oracle April 2026 release drops on a fixed date. The window between release and the point at which non-compliant transport invoices attract regulatory enforcement is not generous. Based on ITC’s experience with Oracle EBS Brazil implementations, here is a realistic view of what the implementation timeline looks like for a prepared organisation vs. one that waits.

Note: Companies that begin ERP readiness work before the Oracle April 2026 release can compress this timeline significantly. Companies that wait until after the release to start planning typically require 10–14 weeks to go live – a window that extends well into enforcement territory.

Common Pitfalls for Transportation Companies Aligning Oracle EBS

ITC works with Oracle EBS customers across Brazil’s transportation sector regularly. These are the five mistakes we see most often when companies begin their Oracle April 2026 release implementation without adequate preparation.

How ITC Supports Transport Invoice Compliance End-to-End

ITC’s approach to the Oracle April 2026 release begins before the release date and covers every stage from initial ERP gap assessment through to post-go-live monitoring. As a system compliance partner – not a tax advisor – ITC’s role is to ensure Oracle EBS is correctly configured, patched, and integrated to support the requirements your tax advisor has confirmed apply to your business.

 ITC’s positioning: ITC is a system compliance partner, not a tax advisor. All CBS/IBS tax interpretations, rate determinations, and exemption decisions should be made in consultation with your qualified tax advisor. ITC implements what your tax advisor determines – correctly, on time, and within your Oracle EBS environment.

Frequently Asked Questions (FAQs)

1. What exactly is the Oracle April 2026 release and why does it matter for transport companies?
   The Oracle April 2026 release is Oracle’s Brazil localisation update that brings Oracle EBS into compliance with the reformed electronic transport invoice framework – specifically, the new Events processing requirements and the Split Payment system introduced by Brazil’s tax reform. Without this update applied and configured, Oracle EBS cannot generate, validate, or settle transport invoices in accordance with the new CBS/IBS requirements.
2. Does the Oracle April 2026 release affect companies outside the transport sector?
   The Events and Split Payment functionality in the Oracle April 2026 release is particularly critical for transport invoice issuers. However, Split Payment as a broader mechanism applies across all CBS/IBS-eligible transactions from 2027 onwards – so companies in other sectors should also be tracking Oracle’s localisation roadmap, even if April 26 is not their immediate milestone.
3. Can our tax partner or fiscal middleware handle the Oracle April 2026 release changes without touching Oracle EBS?
   No. The Events framework and Split Payment configuration required by the Oracle April 2026 release must be implemented within Oracle EBS itself – in the tax modules, payment integration layer, and fiscal classification setup. A middleware layer can assist with outbound XML generation, but it cannot substitute for ERP-side module reconfiguration.
4. How long does implementation realistically take after Oracle drops the update on April 26?
   For a well-prepared organisation – one that has already completed an ERP gap assessment and prepared its test environment – implementation from release to production go-live typically takes 6–8 weeks. For organisations starting from scratch after April 26, expect 10–14 weeks. The pre-release preparation window is therefore critical.
5. What is CNPJ-level segregation, and why does it matter?
   Brazil treats each CNPJ (Cadastro Nacional da Pessoa Jurídica) registration as a distinct fiscal identity. Oracle EBS must be configured to calculate, report, and remit CBS/IBS separately for each CNPJ in your organisation. Companies with multiple legal entities or operating units in Brazil that use consolidated ERP configurations will fail the CGIBS audit validation. The Oracle April 2026 release includes CNPJ-level segregation support – but it requires deliberate configuration, not just patch application.
6. Does ITC provide tax advice as part of the Oracle April 2026 release implementation?
   No. ITC is a system compliance partner, not a tax advisor. Our role is to assess your Oracle EBS environment, identify the implementation gaps, and deliver the patching, module reconfiguration, and tax logic integration required to support your transport invoice compliance. All CBS/IBS rate determinations, exemption decisions, and tax interpretations should come from your qualified tax advisor.