29 Apr What does the Tax Reform mean for JD Edwards?

While public debate swirls around tax rates and legislative timetables, the IT and Tax teams that operate Oracle JD Edwards EnterpriseOne are faced with a more specific question: which system parameters, fields and routines need to be changed and in what timeframe?

What changes with the Tax Reform is not a single event. It progresses in stages, each with new requirements that the ERP needs to be absorbed and validated before going into production.

This article details the technical changes brought about by the Release 26 and the three new requirements arriving in 2026, as well as the two paths available to adapt the system.

How does the Tax Reform transition timetable work?

O new tax model replaces five taxes - PIS, COFINS, IPI, ICMS and ISS - by Dual VAT, CBS (Contribution on Goods and Services, of federal competence) and IBS (Tax on Goods and Services, of state and municipal competence). Added to these is the IS (Selective Tax), levied on products considered harmful to health or the environment.

The period from 2026 to 2032 is mandatory coexistence between the two regimes. Legacy taxes reduce progressively while CBS and IBS grow at the same rate and the JDE will need to calculate, record and reconcile the two sets on the same operations simultaneously, with no room for accounting inconsistencies.

For ERP, This calendar translates into consecutive waves of technical demands. The initial phase was activated in January 2026, with CBS at 0.9% and IBS at 0.1% highlighted on invoices. The next wave, scheduled for 2026, makes the requirements for Credit Notes, Debit Notes and Fiscal Events mandatory.

What technically changes in JDE tax processing?

The biggest structural change is in the way the tax is determined.

In the previous model, JDE calculated taxes using a combination of CFOP, UF of origin and destination and tax regime.

With the Reformation, Oracle introduced a new selection criteria processed to calculate the new taxes, where the Tax Classification and CST for each of the new taxes is defined by Nature of Operation, Recipient Profile and Item Type.

This new engine automatically determines the logic to be used for calculating CBS, IBS and IS and needs to be parameterized independently of the legacy rules, which remain in force during the coexistence period.

The second significant change is in the layout of the NF-e XML. The new CBS and IBS fields are calculated and highlighted in the tax document, but in 2026 they will not make up the financial value of the operation - the so-called “outside” calculation logic.

Technically, this means that the system maintains two sets of values in parallel. To ensure that these two sets do not generate overlapping accounting entries, it is necessary to set up specific Accounting Classes for CBS and IBS, separate from the existing accounting classes for PIS, COFINS and ICMS.

The third change affects financial reconciliation: the split payment.

When fully implemented, this mechanism requires that no time of settlement of a security, The system automatically segregates the tax portion and directs it to government accounts, giving the supplier only the net amount.

The JDE's automatic payment routines - in particular the Creation of the Payment Group - will need to be reconfigured to support this segregation by transaction, with a direct impact on payment instruments and the bank reconciliation.

There is also a one-off but far-reaching technical change planned for July 2026: the CNPJ will no longer be exclusively numerical and now accepts alphanumeric characters.

All JDE routines that validate or format the CNPJ, including customized objects that interact with the General Registry (Address Book), will need to be revised to support the new format, at the risk of system errors in registrations and issuing invoices.

What are the new requirements for Credit, Debit and Event Notes?

The initial phase resolved the calculation and highlighting of IBS and CBS in standard operations. The three requirements in the following table are not yet covered in most active JDE environments and will become mandatory in the next stage of the Reform.

Table: New tax requirements in JD Edwards for 2026 - comparison between the current behavior of the system and the requirements of the new tax model.

The critical technical element in all three requirements is the referential integrity between the original tax document and the documents that complement or adjust it.

The JDE must guarantee traceability at data level, not just in the XML reference field, but in the tax tables that record IBS/CBS credits and debits.

The tax authorities use this information to fill in the tax forms via Assisted Calculation. In other words, any discrepancy in the document chain is, in practice, equivalent to an unused credit.

How to update JD Edwards 9.2 for the Tax Reform?

Oracle provides tax functionalities for Brazil via ESUs (Electronic Software Updates).

For the initial phase of the Reform, four baseline ESUs are a prerequisite:

• JN20946, which covers Localization Brazil's infrastructure;
• JN21082, responsible for the calculation engine and business rules;
• JN20168, with improvements in invoice processing;
• JN20429, with updates on supplies and stock.

Companies that have not yet installed this set operate with an incomplete base, even for the requirements already in force since January 2026.

For the new requirements - Credit Notes, Debit Notes and Fiscal Events - Oracle expects to release the update in July 2026.

The process, however, it's not just about installing this new update. Environments with customizations in objects that interact with Localization Brazil, such as XML generation routines, tax accounting, SPED reports, require impact analysis before applying each ESU.

The complete cycle of installation, testing in a quality environment, validation of the new requirements and homologation with SEFAZ rarely ends in less than two months in medium and large operations. Planning after the ESU has been released is therefore planning after the deadline.

MPL offers the specialized service configuration and validation for companies in the version 9.2application of ESUs with compatibility analysis with existing objects, parameterization of the new requirements - Credit and Debit Notes and Events - and compliance tests in a controlled environment before migration to production, without overwriting customizations in use.

How can I adapt JD Edwards if my company uses an older version?

Oracle does not provide ESUs of Tax Reform for versions prior to 9.2. Companies operating on legacy versions do not have a native upgrade path, but the tax obligation remains in full.

The tax authorities do not recognize the ERP as justification for non-conformity. Thus, Credit and Debit Notes issued outside the standard of the new model are rejected by SEFAZ, and Unrecorded Events generate divergences in the tax history that directly affect the use of IBS and CBS credits.

Extensive customizations, modified object dependencies or environment restrictions can also prevent the update from being installed even in companies that are formally on version 9.2. In these cases, the path is the same: development specific to the client's context.

For this scenario, the MPL develops and configures solutions customized with the same functional coverage as the standard update. Everything is integrated into the existing architecture, without requiring a version migration as a precondition. The solution respects already customized objects and ongoing operational processes.

There are more than 18 tax adjustment projects and a direct relationship with the Oracle board to deal with cases that are not answered in the standard documentation.

Technical compliance doesn't wait for the law to expire

The Tax Reform imposes on JD Edwards a responsibility that goes beyond reading the rules: requires data integrity at each layer of the ERP, The new system will include all the necessary steps, from the parameterization of the calculation engine to the traceability of complementary tax documents. Credit Notes, Debit Notes and Fiscal Events are the next requirement, and the time between the release of the updates and obligation compliance does not support last-minute configuration processes.

Those on version 9.2 have Oracle update scheduled for July and need to start planning now. Those with a legacy version, or with a technical impediment to installing the ESU, need specific development, the implementation and validation cycle of which also requires advance notice.