The new alphanumeric CNPJ is no longer just theory
Since last Monday, the change that had been announced by the Federal Revenue Service (Receita Federal) since 2024 has moved off the drawing board. Starting at 7 a.m. on July 27, 2026 (Monday), the systems for the Alphanumeric CNPJ went into production. This means that, from now on, new registrations in the National Registry of Legal Entities (CNPJ) may be issued with letters mixed with numbers — and your company is probably already receiving (or will soon receive) registrations from customers, suppliers, or partners in this new format.
For those working in tax, accounting, and IT, the message is direct: this is no longer "a change that will happen." It's a change that is already happening, and issuance systems, ERPs, and banking integrations need to be prepared so they don't reject documents or improperly block registrations.
Where this change comes from
Normative Instruction RFB No. 2,229/2024, published in the Official Federal Gazette (Diário Oficial da União) on October 16, 2024, established the transition from the traditional numeric CNPJ format to an alphanumeric system. The justification is structural: the exponential growth in the number of companies registered in Brazil, which already exceeds the mark of 60 million active establishments, is exhausting the possible combinations in the current purely numeric format.
What the new number structure looks like
The CNPJ still has 14 positions and the same visual mask everyone already knows. The first 12 positions may contain uppercase letters (A-Z) and numbers (0-9); the final 2 check digits remain numeric only, keeping the XX.XXX.XXX/XXXX-XX mask and the total of 14 characters. The check digit calculation still follows modulo 11 logic, but with an important adaptation: the modulo 11 formula continues to be used, with alphanumeric values replaced by the decimal value corresponding to their ASCII code, so that A=17, B=18, C=19, and so on.
It's important to make this clear to the entire team, including those who deal with customers: existing CNPJs will remain valid and will continue to function normally, with no need for any changes. The new format only applies to new registrations and to branches opened from now on.
Fiscal documents have accepted the new format for weeks now
One point that often goes unnoticed: the electronic fiscal document environment was already ready for the alphanumeric CNPJ even before the Federal Revenue Service itself started issuing the new numbers. ENCAT Technical Note 2025.001 confirmed that the SEFAZ testing environment would accept alphanumeric CNPJs starting April 6, 2026, and the production environment starting July 6, 2026. In other words, NF-e, NFC-e, CT-e, and other electronic documents have already been validating the new standard in the live environment since the beginning of the month.
In practice, this changes the routine for registering business partners: electronic fiscal documents need to accept both formats, numeric and alphanumeric, and any internally written CNPJ validation rule — in spreadsheets, integrations, or registration screens — that still rejects letters will start blocking legitimate partners.
Technical checklist for the coming days
A few areas deserve immediate attention from the tax and IT teams:
Review all CNPJ validation routines (regex, masks, check digit functions) in in-house systems, reconciliation spreadsheets, and integrations with banks, marketplaces, and payment gateways, making sure they accept letters in the first 12 positions.
Test registrations with fictitious CNPJs in the new format before repeating the process with real data. Serpro made check digit validation code available in Java, Python, and TypeScript, along with a document detailing the calculation, and the Federal Revenue Service also provided an official free simulator for system development, testing, and certification.
Confirm with the tax team that customer and supplier registrations pending updates won't cause NF-e/NFC-e rejections due to an "invalid" CNPJ when, in fact, the number is correct and simply follows the new standard.
An operational relief: the Federal Revenue Service will not charge any fee for updating existing CNPJs or for new registrations — the only costs involved will be those the company itself incurs to update its internal technology systems. And for those who use the CNPJ in day-to-day financial operations, it's worth remembering that the use of the CNPJ as a PIX key will remain unchanged.
Why this matters now, and not just "down the road"
The CNPJ change arrives during the same period when the Tax Reform timeline already demands redoubled attention to IBS, CBS, and the Selective Tax in fiscal documents. Ignoring the need to update CNPJ validation routines can cause the same kind of headache as a poorly applied fiscal technical note: document rejection, billing delays, and rework to fix registrations that, technically, were never wrong.
This content is for informational purposes only and does not replace guidance from your accounting firm or a professional specialized in taxes, who should assess your company's specific circumstances in light of the new rules.
If your team wants to get through this transition with your ERP already adjusted and without any rejection surprises, talk to Edoo.
Alphanumeric CNPJ is now in production: what your tax and IT teams need to adjust now