A company registration form can work for years and fail when a new customer arrives. With Brazil’s alphanumeric CNPJ, numeric-only input is no longer a safe assumption for systems receiving business identifiers.
The change has reached Brazilian registration
Receita Federal reported the first alphanumeric CNPJ on July 31, 2026. Existing numeric identifiers remain valid. The format keeps 14 positions: letters and numbers may appear in the first 12; the final two check digits remain numeric. CNPJ is Brazil’s legal-entity registration identifier.
Receita Federal — Primeiro CNPJ alfanumérico ↗Receita Federal — Projeto CNPJ Alfanumérico ↗Coaf — Adequação ao formato alfanumérico ↗Changing the input mask is not enough
Our review approach follows the identifier end to end. A form may accept letters while an integration silently strips them. A spreadsheet may convert the identifier to a number before sending it to CRM.
Map the journey through entry, validation, storage, lookup, export and the receiving system. Ask the team to show the value before and after each transformation. This evidence helps locate the failure instead of blaming the “new CNPJ” in general.
Six areas for the assessment
This implementation checklist should be adapted to your architecture. The Receita Federal project is the reference for the format and validation materials.
- Entry: check keyboard settings, masks, paste behavior and errors.
- Validation: review rules rejecting letters or using only the old algorithm.
- Storage: treat the identifier as text and preserve leading zeros.
- Search: apply consistent punctuation and uppercase normalization.
- Files: test imports, exports and staff templates.
- Integrations: check API contracts and partner responses.
A test across the operation
For acceptance testing, use an official test case and follow a complete journey: register a company, create an opportunity and test order, export it and look it up in the integrated system. Do not invent an identifier to represent a real company.
Repeat the journey with existing numeric identifiers in your test environment. Compare transmitted values, messages and record links. Accept both journeys so that supporting the new format does not break existing registrations.
Assign owners and acceptance criteria
We suggest an owner for each entry point and integration. Record versions, scenarios, results and open issues. If a partner cannot yet accept the format, staff need a documented handling process, rather than stripping letters to force transmission.
At RAQO, this work starts with the actual data flow. The objective is consistent company records across processes. Format validation is not a substitute for an official registration lookup and does not independently establish a business’s status.
Frequently asked questions
Will my existing CNPJ be replaced?
Receita Federal states that existing CNPJs remain valid without a change to their identifier.
Is accepting letters in the form sufficient?
No. The identifier must also be validated, stored, searched and transmitted correctly throughout the workflow.
Official sources
Receita Federal — Primeiro CNPJ alfanumérico ↗Receita Federal — Projeto CNPJ Alfanumérico ↗Coaf — Adequação ao formato alfanumérico ↗Accessed November 2, 2026. Project checklists and examples in this article are RAQO editorial proposals.
