NF-e keeps layout 4.00.
Reform arrives through Technical Notes.

What changes within the same layout

The MOC 7.00, Annex I, field A02 identifies layout version 4.00. The number 7.00 belongs to the taxpayer guidance manual. NT 2025.002 v1.51, introduction and layout section addresses changes for IBS, CBS and the Selective Tax. Keep these identifiers separate in the delivery inventory.

Tax groups and classification fields, including CST and cClassTrib, must be connected to the actual transaction. A field being available does not establish that the tax applies to a particular sale. Ask the Brazilian team to connect the business facts, the approved tax position, the expected calculation and the transmitted fields, with the relevant conditions and exceptions.

This guide concerns adaptation and acceptance. Detailed tags and rules belong to the NF-e layout and NT 2025.002 guide in Portuguese; code selection and maintenance are addressed in the cClassTrib classification guide in Portuguese. These technical references can support the local team without duplicating their scope in the HQ project brief.

Separate three calendars in the programme

The ADCT, Articles 125–129, introduced by Constitutional Amendment 132/2023, provides the transition: a 2026 stage; CBS and Selective Tax from 2027; ICMS/ISS reductions during 2029–2032; and abolition of those two taxes in 2033. These are not a single XML rejection or ERP delivery deadline. Article 125, paragraph 4, links possible relief from collection to ancillary obligations and complementary legislation.

For each flow, record the document type, taxpayer regime, transaction, validation rule, test or production environment, published version and application date. NF-e, NFC-e, NFS-e and CT-e should not automatically inherit the same milestone. The wider business transition belongs to the Brazilian Tax Reform guide.

At the review date, 14/09/2026, the official SVRS catalogue listed NT 2025.002 v1.51 and subsequent changes, including NT 2026.009 v1.00. Before deployment, the project must check the current package applicable to its transactions. A version cited in an executive guide cannot replace that release check.

Why authorization does not close the tax review

In their 6 August 2026 clarification, RFB and CGIBS explained that postponing validation and rejection rules did not suspend the duty to report CBS/IBS information. The measure aimed to preserve billing continuity. Read its scope alongside the acts and rules for the relevant document; it does not establish that every field is optional throughout the year.

A hypothetical example: a sale produces an accepted XML, but the master data used in the calculation corresponds to a different transaction. The protocol demonstrates authorization; it does not determine whether the tax classification was appropriate. The useful test compares documented business facts, the approved tax position and the values actually transmitted and posted.

Articles 132, I, and 147 of CGIBS Resolution 6/2026 preserve that distinction and the responsibility of the issuer for accuracy. The example does not presume an automatic penalty, credit loss or correction procedure: those consequences depend on the facts and applicable rules.

Allocate deliverables between HQ and local teams

The budget should follow the inventory: establishments, document types, transactions, tax regimes, interfaces and custom code. A reviewable statement of work identifies these assumptions, the environments to be used and the owner of each type of discrepancy. Price and duration should follow that assessment, rather than the commercial name of the ERP.

The TaxUp team can translate tax positions into verifiable requirements and assess the evidence produced. The integrator executes the contracted technical changes. This is a governance recommendation, not a legal requirement to buy independent validation or a certification of compliance. HQ should agree how unresolved interpretations and technical defects reach the decision maker.

For an English-language SAP decision path, begin with the Brazil Tax Reform and SAP executive guide, continue with the GRC NFe-to-DRC transition, and use the independent SAP tax validation service page to frame scope, evidence and acceptance.

For SAP environments, the next decision is covered in the SAP architecture and sequencing guide in Portuguese. The detailed scenario workbook remains with the ERP and SaaS tax testing guide in Portuguese. Platform choices should be assessed against demonstrated capabilities and business requirements.

Connect configuration to documented acceptance

Begin with the flows that affect issuance, incoming documents and accounting records. For each scenario, retain the input data, selected rule, expected result, XML, response and postings. Include relevant exceptions, such as returns or cancellations, where they occur in the business. Explain coverage in terms of risk and operations.

After fixing a defect, reproduce the scenario and check affected processes. Distinguish a technical failure, inappropriate master data and a disputed tax interpretation. Counting completed tests does not demonstrate coverage. An unresolved issue affecting billing needs an owner and an explicit decision before the change.

Bookkeeping and reporting require their own inventory of obligations, acts, manuals and versions. A new fiscal document is not a sufficient basis for removing an existing reporting obligation from the project. Tax compliance work connects issuance, records, reconciliation and review of the rules relevant to the company. Ask for a clear account of what has and has not been tested.

Prepare a reviewable scope before commissioning work

The expected review output is a requirements and scenario matrix, explained discrepancies and acceptance criteria. The proposal should identify covered documents, exclusions, dependencies on the integrator and decisions retained by the client. Share only necessary information through the agreed protected channel.

This factual review has a cutoff of 14/09/2026. A new Technical Note, act, tax regime or issuer release may require scenarios to be reopened. The technical starting point is the official NF-e/SVRS catalogue; legal conclusions require the applicable provisions. A company-specific review closes the questions an executive guide cannot settle for its actual operations.