Bulk CNPJ Generator

Multiple CNPJs for B2B CRM, NFe sandbox and BI dashboards

A multi-CNPJ generator outputs dozens of valid Cadastro Nacional da Pessoa Jurídica numbers per click — same modulo-11 check as CPF, but applied over 12 base digits split into radical (8) + branch suffix (4). The standard lote tool already covers the basic workflow; this page focuses on the B2B angles: populating CRM pipelines, exercising NFe homologation environments, modelling realistic CNAE distributions, and preparing for the 2026 alphanumeric migration.

B2B CRM and pipeline mocks

B2B CRMs (Salesforce, RD Station, HubSpot, Pipedrive) routinely demand 10,000-row pipelines for sales-ops rehearsals — but exporting real client data violates the LGPD. A multi-CNPJ generator fills the gap: pair each company with a Faker company name and a synthetic industry code and you have a realistic pipeline without legal exposure. Most CRMs do not validate the CNPJ against the Receita Federal base, so any algorithmically valid number imports cleanly.

Beware of accidental real CNPJs in cloud validators

A pure random generator can coincidentally land on a real company — public APIs like brasilapi.com.br/api/cnpj/v1/14572624000110 will then return live RFB data (razão social, address, CNAE). If your QA pipeline calls a cloud validator and asserts "not found", this will flake. Two defences: (1) use the reserved prefix 00.000.000 family which the RFB never assigns; (2) keep a deny-list of confirmed-real numbers you have already encountered.

NFe sandbox and SEFAZ homologation

Each state SEFAZ maintains a homologation environment with its own list of test CNPJs (typically published in the technical manual). Algorithmically valid generated numbers are usually accepted as emitente in homologation when paired with the matching IE-test, but production endpoints reject anything that the RFB base does not recognise. Use the generator for load test on your own internal NFe pipeline (XML signing, schema validation, queue throughput) before swapping to the SEFAZ-provided list for real protocol round-trips.

CNAE distribution for realistic BI mocks

• CNAE 47 (Comércio varejista) — ~40% of active companies; over-represent in any retail-facing dashboard.
• CNAE 56 (Alimentação) — ~10%, dense in metropolitan regions.
• CNAE 62 (Tech / TI) — ~3% nationally but concentrated in SP capital, Recife, Florianópolis.
• CNAE 86 (Saúde) — ~5%; important for healthtech dashboards.

Headquarters + branches (matriz + filiais)

A common B2B scenario is one corporate group with one HQ and several branches sharing the same 8-digit radical. Encoding: HQ uses suffix 0001, the first branch 0002, second 0003, and so on, each followed by a fresh pair of check digits. To model this, generate one radical then iterate the suffix counter — every branch has the same razão social but distinct billing addresses, which matters for tax-rule QA.

2026 alphanumeric CNPJ — heads up

The Receita Federal published IN 2.229/2024 introducing alphanumeric CNPJs starting July 2026. The radical and suffix become base-36 (digits + uppercase letters A-Z); only the two final check digits stay numeric. This generator currently emits the legacy numeric format — once the new rules go into effect, you will need to switch to the /gerador-cnpj-alfanumerico page to stay compatible. Existing CNPJs remain valid; only new registrations from 2026 onwards can be alphanumeric.

FAQ

Does it emit HQ plus branches in one batch? Some toolkits include a "matriz + N filiais" mode that locks the radical and walks the suffix. The basic generator gives independent numbers; chain a small wrapper if you need the grouped output.

Can the output be sent to a SEFAZ homologation endpoint? Yes — homologation accepts any algorithmically valid CNPJ as a test emitente. Production endpoints reject anything not on file at the RFB.

Should I migrate the generator to alphanumeric now? Not until the rule takes effect in July 2026. Until then, NFe and Sintegra systems still expect the numeric form, and emitting letters early would break downstream validators.

Are state inscriptions (IE) generated together? No — IE follows per-state algorithms (44 variants in total) and is generated by a separate tool. Pair the two outputs by row index when you need the full fiscal identity.