What is Technical Note 2026.009 and why it matters now
Published in September 2026, Technical Note 2026.009, version 1.00, is one of those changes that seem small on paper but directly affect the return invoice issuance flow at thousands of Brazilian companies. (cite index="1-3">Published in September 2026, version 1.00 of Technical Note 2026.009 changes a validation rule of the Electronic Invoice (NF-e), model 55, expanding acceptance of CFOP 1.949 and 2.949 in the situations provided for by the rule itself. The good news for those who manage tax systems: (cite index="1-5">the update does not change the NF-e layout or the XML schemas.
Which rule changes, exactly
(cite index="20-1">Technical Note 2026.009 specifically changes validation rule I08-140 – Rejection 327: Invalid CFOP for an Invoice with the purpose of merchandise return, located in Group I – Products and Services of the NF-e. This rule has existed for a long time and receives periodic adjustments to keep up with new tax scenarios, including some related to the Consumption Tax Reform.
The reason for the change is practical: (cite index="20-2">the change was necessary because not all existing outbound CFOPs have corresponding return CFOPs. (cite index="21-1">Validation rule I08-140 now accepts CFOPs 1.949 and 2.949 in cases of sales returns and returns due to refusal or non-location of the recipient.
Technically, the change is concentrated in Exception 1 of the rule: (cite index="39-7">the change is concentrated in Exception 1 of I08-140, removing the restriction that linked CFOPs 1.949 and 2.949 exclusively to sales returns. It's worth reinforcing that this is not a general release: (cite index="20-8">NT 2026.009 specifically addresses the operations covered by rule I08-140, while the other NF-e validations continue to be applied normally.
Why Rejection 327 was a recurring problem
Those who work in tax routines know well the headache caused by Rejection 327. It occurs whenever the invoice has the purpose of return, but the CFOP entered does not correspond to that specific purpose. The problem is that, for several outbound operations — especially those outside the standard sales flow, such as returns due to recipient refusal or cases where the recipient is not found — there simply wasn't a specific corresponding return CFOP in the national table. This held up tax documents and forced tax departments to resort to alternative solutions, often manual, to avoid stalling operations.
Implementation schedule
(cite index="20-9">The schedule for version 1.00 states implementation by September 17, 2026, for both the test environment and the production environment. This means the window for reviewing systems is short: only a few business days remain from today. (cite index="28-5">To avoid holding up tax documents, the fix requires immediate implementation in the authorizing environments.
What to review in issuing systems before the 17th
For IT and tax teams that maintain ERPs, integrations, and proprietary issuers, the technical recommendation is clear: (cite index="20-6">the main points to review are creating tests for the finNFe = 4 and finNFe = 5 scenarios, validating the tpNFCredito = 03 and 06 cases, and running regression tests involving Rejection 327.
An additional point of attention for those who have their own pre-validation rules, even before sending the XML to SEFAZ: (cite index="39-8">NT 2026.009 deserves attention in applications that perform tax validations before transmitting the NF-e. If the tax system has its own rules for checking CFOPs before sending the document, it's important to assess whether these validations reproduce the previous restriction of rule I08-140.
It's also worth observing the behavior in Credit Note scenarios, created under the scope of the Tax Reform: (cite index="39-5,39-6">as a result, issuing systems began applying the return CFOP validation in these specific Credit Note scenarios as well, and NT 2026.009 does not change this scope of application of the rule.
Context: another fine-tuning adjustment in the middle of a year of transition
NT 2026.009 arrives at a time of intense movement in Brazilian tax layouts due to the Consumption Tax Reform. Just in the past few weeks, the National NF-e Portal has addressed topics such as the postponement of the Signature and Authorization Provider (PAA) to October, new item-level return referencing rules (rule VC02-14, effective September 1), and the schedule for IBS/CBS fields for Simples Nacional. For tax and IT teams, this reinforces the need to continuously monitor the technical note calendar, not just around major milestone dates like August or October.
Companies that operate ERPs well integrated with the SEFAZ environment tend to feel less impact from this kind of adjustment, since updates to validation rules are automatically absorbed by the technology provider, without requiring manual intervention from the tax team for every technical note.
This content is for informational purposes only and does not replace guidance from your accounting team, which should always be consulted to validate the specific tax classification for your company.
Want to make sure your ERP is already prepared for the upcoming Tax Reform technical notes? Talk to Edoo.
NT 2026.009: SEFAZ Releases CFOP 1.949 and 2.949 for Merchandise Returns and Ends Rejection 327 by 09/17