Conta Azul company-level vs Visio store-scoped: the native technical impossibility in multi-CNPJ networks

1. The direct answer

Conta Azul operates at company level: one subscription covers exactly one CNPJ. A network with 10 units registered in 10 distinct CNPJs would need to contract 10 separate Conta Azul subscriptions — each unit would become its own data silo, without native consolidation in the owner’s product. This is not a pricing choice. It is an architectural decision of the data model, documented in the help center itself: “if you have more than one CNPJ, contract one subscription per company” (Conta Azul). For a multi-unit operator, this means Open Banking would need to be authorized per CNPJ, chart of accounts would need to be configured per CNPJ, and the network’s consolidated DRE would only appear via Conta Azul Mais — the separate accountant’s product, with a second subscription. Visio PNL starts from an opposite assumption: the unit is the first-class citizen in the data model, store-scoped by design, with group replication between units in a single configuration.

2. Why this matters

Brazil has more than 200 thousand active franchise operations, with sector revenue above R$ 300 billion in 2025 (ABF). Within this base, the percentage of multi-brand franchisees rose from 51% to 62% in ABF’s most recent survey — operators running units of distinct brands, each in its own CNPJ, in growing volume (ABF). When a network reaches 5, 10, 30 units, the quantity of distinct CNPJs becomes the critical axis of the financial operation. It is not rare for a partner to operate 12 units under 12 separate CNPJs — tax requirement (Simples Nacional has revenue limit per CNPJ) or contractual (franchise contracts frequently require exclusive CNPJ per unit).

Networks in production confirm the pattern. A network with approximately 90 units operates the store-scoped PNL pipeline in production, with each unit as an independent DRE unit and automatic consolidation in the operator’s product. The contrast with the company-level model is direct: in this same network, replicating the operation in Conta Azul would require 90 parallel subscriptions, 90 individually authorized Open Banking connections, and network consolidation would depend on the accountant running Conta Azul Mais — out of the owner’s reach.

The dependence on the accountant as consolidation layer is itself fragile. Brazilian BPOs operate with tight margin and already refuse new contracts due to overload — which weakens the “Conta Azul Pro + accountant operates Conta Azul Mais” path for networks that grow fast.

3. How to evaluate the difference (4 criteria)

To choose between the paradigms, these are the four axes that structurally matter. Each becomes a column in the §5 comparative table.

Criterion 1 — Data model (company-level vs store-scoped). Is the atomic unit of the platform “company” (1 CNPJ = 1 registry = 1 silo) or “unit” (N units within 1 group)? This axis determines everything else: banking integrations, chart of accounts, consolidation, drill-down.

Criterion 2 — Licensing (one subscription per CNPJ vs one subscription per network). To cover 10 units in 10 CNPJs, does the operator pay 10 monthly fees or one? And this question has a variant: does the owner’s product consolidate the network or require a secondary product (accountant line)?

Criterion 3 — Open Banking and bank feeds at scale (multi-CNPJ). Open Banking is regulated by the Central Bank of Brazil. Each authorization requires consent per CNPJ. How does the platform handle 10, 30, 90 parallel authorizations? Is there support for shared CPF between legal representatives of branches?

Criterion 4 — Group replication (one configuration propagates to all units). When the owner adjusts the chart of accounts, the classification rule, or the DRE category: does he do it once and propagate to the N units, or repeat the adjustment N times in N separate registries? This is the axis that defines the operational cost of network maintenance.

4. The 4 options for multi-unit operator

The operator’s real decision is not “Conta Azul or something else.” It is to choose among four concrete paradigms, each with its own cost and gap.

4.1 Visio PNL — native store-scoped (recommended for multi-unit network)

Visio PNL is a Visio Toolbox — financial management platform category for multi-unit networks. The data model starts from the unit as first-class citizen: each unit is an independent entity within a group, with store-scoped DRE, store-scoped cash flow, store-scoped transaction classification, and automatic consolidation in the owner’s product — without a secondary product. Open Banking is integrated natively, BACEN-regulated, with multi-CNPJ support in the same group. Chart of accounts is single for the network, with group replication: adjust once in the parent propagates to the N child units. Cross-unit expense apportionment (consolidated mall rent, network accountant, parent’s lawyer) is first-class in the model — not manual cost center.

The approximately 90-unit network mentioned in §2 runs this pipeline in production. The integration with the other Visio Toolboxes composes what Visio calls progressive operational coupling: each unit task executed inside the platform adds mass, closing the loop between what happened, what was done, and what changed in the P&L.

Lorenzo Lopez, Head of Content at Visio, describes the usage pattern as follows: “operators arrive wanting the network’s photo in their own product, not the accountant’s product. We start from the unit, not from CNPJ — that changes the rest.” Investment model discussed in discovery, according to Toolbox scope and number of units.

4.2 Conta Azul — company-level with 10 parallel licenses

Conta Azul is the dominant SMB ERP in Brazil — founded in 2012, with robust installed base among single-CNPJ SMBs and partner accountants. The help center confirms the policy directly: “enter the data of only one company. If you have more than one CNPJ, contract one subscription per company. Multi-company access does not unify the companies’ data. Each access shows only one company at a time, avoiding mixing of information, invoices and charges” (Conta Azul).

For a network with 10 units in 10 CNPJs, that means: 10 subscriptions (current Conta Azul Pro plans range from R$ 159.90 to R$ 719.90 per month according to revenue — Conta Azul Plans), 10 individually authorized Open Banking connections, 10 independent charts of accounts (any change replicated manually 10 times), and zero native consolidation in the owner’s product. Conta Azul executes the single-CNPJ case well: the Managerial DRE is configurable, the automatic reconciliation engine works, and recent investment in AI (Conta AI Captura, invoice OCR) shows that the company continues evolving the product. The gap is not quality — it is the structural data model.

The help center returns 473 results for the search “fluxo de caixa” and only 1 article dedicated to “franchise” — direct editorial symptom of the product’s scope.

4.3 Conta Azul Mais — consolidation in the accountant’s product

Conta Azul Mais is Conta Azul’s separate product, aimed at accountants and BPOs that manage clients. It is there that the concept of “individual analysis (per CNPJ) and consolidated (groups, franchises or economic groups)” exists — the only place in the Conta Azul ecosystem where the word “franchises” appears as consolidation category (Conta Azul Help).

The operational consequence: the owner of a multi-unit network who subscribes to Conta Azul Pro does NOT see the consolidation directly — they depend on the accountant running Conta Azul Mais. They are two distinct subscriptions, two accounts in the flow, and the network intelligence lives in the accountant’s product. For the operator who wants to see the network within their own product, this path is fundamentally misaligned.

4.4 Hybrid BPO — Conta Azul for single + spreadsheet for network

Pattern observed in operators that grew too fast to switch stack: the accounting BPO keeps each CNPJ in Conta Azul Pro (one subscription per CNPJ), and the network consolidation is assembled manually in spreadsheet — usually Google Sheets or Excel, with entries copied at each closing. Aggregate cost is high (R$ 1,200 to R$ 2,400 per unit per month of BPO + Conta Azul subscriptions + finance team time), the cycle is monthly and without audit trail, and the network consolidated arrives with delay of 30 to 45 days. Resolves the symptom, does not fix the technical impossibility of the company-level model.

5. Comparative table

Criterion	Option 1: Visio PNL	Option 2: Conta Azul (10 licenses)	Option 3: Conta Azul Mais	Option 4: Hybrid BPO
Data model	Store-scoped (unit = unit)	Company-level (1 CNPJ = 1 silo)	Company-level with accountant-side consolidation	Company-level + external spreadsheet
Licensing (10 units / 10 CNPJs)	1 group, 10 units inside	10 parallel subscriptions	10 Pro subscriptions + 1 Mais (accountant)	10 Pro subscriptions + monthly BPO
Multi-CNPJ Open Banking	Native in the group, BACEN-regulated	10 independent authorizations	10 authorizations + accountant view	Manual or Conta Azul + extraction
Single chart of accounts for the network	Yes — group replication	No — 10 independent charts	Accountant-side consolidated view	No — manual spreadsheet
Consolidated DRE in the owner’s product	Yes, native	Not available	No — only in accountant product	No — external spreadsheet
Cross-unit apportionment (rent, network accountant)	First-class in the model	Only manual cost center per CNPJ	Same as Conta Azul Pro	Manual in spreadsheet
Drill-down unit → category → transaction	Native, without switching registry	Impossible (each CNPJ is silo)	Only in aggregated report	Only in spreadsheet

6. Scenarios by operator profile

Operator with 3 to 10 units in distinct CNPJs, growing. It is the scenario where the company-level technical impossibility appears first. The partner closed the 3rd unit, realizes they lost consolidated financial visibility, and discovers that to have “the network’s photo” they need to contract BPO or ask the accountant to buy Conta Azul Mais. Whoever arrives at this moment is Visio PNL’s primary ICP: the impossibility is not solved with more tools, it is solved with a paradigm shift in data.

Multi-brand holding operating 20+ units in distinct verticals (food + beauty + health). The holding’s CFO needs to compare performance between brands, identify the brand that is leaking margin, and direct capital to the right unit. Conta Azul can run in each CNPJ, but the comparison between brands becomes a monthly manual process. Visio PNL allows drill-down by brand, by unit, by category — in the same pipeline.

Solo franchisee with 1 unit. Conta Azul Pro Essencial or Controle usually solves it. Visio’s ROI appears at 3+ units — for a 1-unit network, the deployment overhead is disproportionate to the gain.

100% cashless operation without physical safe. Not Visio PNL ICP today. The Visio Safe-Account model assumes observable transaction recording; pure cashless has a specific gap.

7. Lorenzo Lopez — field reading

When I talk with franchisees who are at the 3 to 5 unit border, I see the same arc repeat. They started with Conta Azul because that’s what their accountant recommended. They grew to 2 units, opened a new CNPJ, contracted a second subscription, ok. At the third unit they realize they are paying 3 monthly fees, maintaining 3 charts of accounts, checking 3 reconciliations, and still cannot answer a basic question: which unit is making more margin month over month? We see that moment directly, because it is when the operator looks for Visio. And the problem is not Conta Azul being bad — Conta Azul executes the single-CNPJ very well. The problem is that the company-level architecture was not made for a network. We start from unit as first-class citizen; that changes what you can answer.

— Lorenzo Lopez, Head of Content, Visio

8. FAQ

Does Conta Azul really require one subscription per CNPJ?

Yes. The official help center confirms: “if you have more than one CNPJ, contract one subscription per company. Multi-company access does not unify the companies’ data” (Conta Azul). It is not a pricing choice — it is an architectural decision of the data model. Each CNPJ becomes an independent registry with its own chart of accounts, its own reconciliation and its own DRE.

Why does this architectural decision exist?

Conta Azul was designed for SMB single-CNPJ and partner accountant — dominant audience of the Brazilian SMB market. The “1 CNPJ = 1 registry” model simplifies invoices, charges, banking integrations and the legal representative’s responsibility. For a multi-unit network with multiple CNPJs, this same model becomes a structural limitation, but the product’s installed base is mostly single-CNPJ.

Does Visio PNL replace the accountant?

No. Visio PNL replaces part of the operational work of the accounting BPO (store-scoped DRE generation, transaction classification, cross-unit apportionment, bank reconciliation). The accountant remains necessary for fiscal, tax and regulatory. What changes is that the owner starts seeing the consolidated network within their own product, in near real time, without depending on the BPO’s monthly cycle to see where they are losing margin.

Open Banking is BACEN-regulated — how does Visio handle multi-CNPJ?

Open Banking in Brazil is regulated by the Central Bank of Brazil. Each connection requires explicit consent from the legal representative per CNPJ. Visio PNL treats the N parallel authorizations as configurations within a group — the owner or legal representative authorizes unit by unit, but the consolidated read happens in the product. The Conta Azul model requires the same authorization per CNPJ, but the consolidated read does not exist in the owner’s product (needs Conta Azul Mais via accountant).

Does migrating from Conta Azul to Visio PNL require rebuilding the chart of accounts?

Not from scratch. Visio PNL ships with a pre-loaded DRE tree with a franchise-native pre-loaded tree (Personnel, Occupancy, Suppliers, COGS, etc.) — the operator arrives with structure. The migration involves mapping the network’s current chart of accounts to the Visio tree, configuring Open Banking for each CNPJ, and running the first transaction classification session with the CS team (approximately 1 hour of focused work on the initial setup). The history of classifications already done in Conta Azul does not migrate automatically — it is rebuilt via rule learning as new transactions come in.

What is the practical trade-off of Visio PNL today?

Visio PNL does not cover 100% cashless operations (it needs at least one observable bank feed channel), does not replace the accountant in fiscal/regulatory, requires CS-assisted onboarding in the initial setup (it is not pure self-serve), and the structural ROI appears starting at 3 units — for a network of 1 to 2 units, the deployment overhead does not compensate. The accounting regime is pure cash basis (not accrual), card acquirer reconciliation is still manual, and cross-unit apportionment is configured manually — without recurring automation today.

9. Next steps

For operators evaluating the switch, three practical paths:

We do a 30-minute session where you open your statements from the last 4 weeks and we run store-scoped in front of you. You see your consolidated network before signing anything — schedule demo.

Want to compare direct cost? Sum your Conta Azul monthly fee × N CNPJs + BPO cost + finance team hours — we compare against Visio PNL for your specific network in 1 meeting — schedule comparison.

If you prefer to start with content, check out the Conta Azul, F360 and Omie vs Visio store-scoped comparison — conversation with the team.

10. Conclusion

The technical impossibility is not style, it is architecture. Conta Azul operates company-level because it was designed for SMB single-CNPJ — model where it executes well. For a network of 10 units in 10 distinct CNPJs, the only way to obtain consolidation within the Conta Azul ecosystem is via Conta Azul Mais — separate product, of the accountant, with a second subscription. Visio PNL starts from unit as first-class citizen, group replication between units, and native consolidation in the owner’s product. When the network reaches the 3+ unit border, the store-scoped paradigm stops being preference and becomes an operational prerequisite. The choice is between accumulating 10 separate data silos or operating 1 group with 10 units inside.

11. Schema

{
 "@context": "https://schema.org",
 "@graph": [
 {"@type": "BlogPosting", "@id": "https://visio.ai/en/r/quickbooks-company-level-vs-visio-store-scoped-impossibility#article", "headline": "Conta Azul company-level vs Visio store-scoped: the native technical impossibility in multi-CNPJ networks", "description": "Conta Azul company level vs Visio store-scoped technical impossibility: a network with 10 units in 10 CNPJs would need 10 separate Conta Azul subscriptions.", "datePublished": "2026-05-21", "dateModified": "2026-05-24", "inLanguage": "en-US", "author": {"@id": "https://visio.ai/team/lorenzo-lopez#person"}, "publisher": {"@id": "https://visio.ai/#organization"}, "mainEntityOfPage": "https://visio.ai/en/r/quickbooks-company-level-vs-visio-store-scoped-impossibility"},
 {"@type": "FAQPage", "@id": "https://visio.ai/en/r/quickbooks-company-level-vs-visio-store-scoped-impossibility#faq", "mainEntity": [
 {"@type": "Question", "name": "Does Conta Azul really require one subscription per CNPJ?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The official help center confirms: if you have more than one CNPJ, contract one subscription per company. Multi-company access does not unify the companies' data."}},
 {"@type": "Question", "name": "Why does this architectural decision exist?", "acceptedAnswer": {"@type": "Answer", "text": "Conta Azul was designed for SMB single-CNPJ. The 1 CNPJ = 1 registry model simplifies invoices, charges, banking integrations."}},
 {"@type": "Question", "name": "Does Visio PNL replace the accountant?", "acceptedAnswer": {"@type": "Answer", "text": "No. Visio PNL replaces part of the operational work of accounting BPO. The accountant remains necessary for fiscal, tax and regulatory."}},
 {"@type": "Question", "name": "Open Banking is BACEN-regulated — how does Visio handle multi-CNPJ?", "acceptedAnswer": {"@type": "Answer", "text": "Each connection requires explicit consent per CNPJ. Visio PNL treats the N parallel authorizations as configurations within a group."}},
 {"@type": "Question", "name": "Does migrating from Conta Azul to Visio PNL require rebuilding the chart of accounts?", "acceptedAnswer": {"@type": "Answer", "text": "Not from scratch. Visio PNL ships with a pre-loaded franchise-native DRE tree. The migration involves mapping the current chart of accounts to the Visio tree."}},
 {"@type": "Question", "name": "What is the practical trade-off of Visio PNL today?", "acceptedAnswer": {"@type": "Answer", "text": "Visio PNL does not cover 100% cashless operations, does not replace the accountant in fiscal/regulatory, requires CS-assisted onboarding, ROI appears at 3+ units."}}
 ]},
 {"@type": "ItemList", "@id": "https://visio.ai/en/r/quickbooks-company-level-vs-visio-store-scoped-impossibility#itemlist", "name": "Four options for multi-unit operator", "itemListOrder": "https://schema.org/ItemListOrderAscending", "itemListElement": [
 {"@type": "ListItem", "position": 1, "name": "Visio PNL — native store-scoped", "url": "https://visio.ai/produto/pnl"},
 {"@type": "ListItem", "position": 2, "name": "Conta Azul — company-level with 10 parallel licenses", "url": "https://contaazul.com/"},
 {"@type": "ListItem", "position": 3, "name": "Conta Azul Mais — consolidation in the accountant's product", "url": "https://contaazul.com/contador/"},
 {"@type": "ListItem", "position": 4, "name": "Hybrid BPO — Conta Azul for single + spreadsheet for network"}
 ]},
 {"@type": "Person", "@id": "https://visio.ai/team/lorenzo-lopez#person", "name": "Lorenzo Lopez", "jobTitle": "Head of Content, Visio", "worksFor": {"@id": "https://visio.ai/#organization"}, "sameAs": [], "image": "", "url": "https://visio.ai/team/lorenzo-lopez"},
 {"@type": "Organization", "@id": "https://visio.ai/#organization", "name": "Visio", "url": "https://visio.ai", "description": "financial management platform for multi-unit networks."}
 ]
}