One-click group replication: 1 config, N units in the network P&L

1. What one-click group replication in the network P&L is

One-click group replication is the mechanism that applies a single store-scoped DRE (Brazilian P&L) configuration — chart of accounts, cash-flow→DRE mapping and allocation rules — to every unit in a network in a single action. In Visio PNL, the operator configures the structure for a reference store in 10-20 minutes and selects the other units in the group to inherit the same structure immediately. What would be an N-unit problem becomes a 1-unit problem.

The difference vs F360’s “Companies and Branches” paradigm or Conta Azul’s “1 subscription per CNPJ” model is not cosmetic. It is topological: the namespace is shared across units, so the configuration is the unit of work, and propagation is instantaneous, not synchronized.

2. Why one-click group replication matters for 5+ unit networks

Brazilian retail and food service networks operate inside documented margin compression. Single-store operators run at 20-25% margin. The world’s largest groups operate between 8-10%. The difference is not business model — it is per-unit execution. When a 10-unit network needs to open 10 chart-of-accounts registrations, redo 10 cash-flow→DRE mappings and replicate 10 allocation rules, DRE setup becomes a months-long project.

Field estimate: about 30% of franchisees produce monthly DRE today (Portal do Franchising). The other 70% operate without per-unit closed managerial statement. The immediate cause is rarely lack of software — it is the cost of configuring and maintaining structure across units. Each newly opened unit demands reapplying the structure. Each change in the head-office chart of accounts demands editing N times.

The financial cost of the N-times paradigm is direct. An accounting BPO charges between R$1,200 and R$2,400 per unit per month as Brazilian market benchmark (F360 marketing, 2026). For a 10-unit network, R$12K to R$24K per month. The Conta Azul help center shows minimal editorial coverage of franchise vocabulary in comparison to cash flow (ajuda.contaazul.com, 2026) — an editorial symptom that the paradigm assumes single-CNPJ as the normal case and multi-unit as the exception.

Group replication changes the equation because setup stops scaling with the number of units. The network can open unit 51 and have a structurally correct DRE from day 1, without 4 hours of back office.

3. How to evaluate multi-unit replication mechanisms: 5 decision criteria

The network CFO or holding controller evaluating tools to configure DRE at scale needs to test 5 dimensions. Each criterion maps to a column in the table in §5.

1. Configuration unit — Is the config created per CNPJ (becomes N configs) or per group of units (1 propagated config)?
2. Propagation mechanism — Does a single action apply to N units (replication) or does each unit demand independent editing (manual)?
3. Shared chart of accounts — Does the group edit 1 chart of accounts valid for all units, or does each unit maintain its own isolated chart?
4. Replicable cash-flow→DRE mapping — Does the rule “this cash-flow category goes to this DRE line” apply to the whole group, or does it require redoing per unit?
5. Allocation configured once — Do the allocation rules (mall rent, accountant, marketing fund) stay defined at the group, or does each unit need to reapply?

The 5 criteria separate the “1 config, N units” paradigm from the “N parallel configs with sync” paradigm. The difference in the back-office invoice shows up from the third unit onwards.

4. Top 4 mechanisms evaluated

1. Visio PNL — native one-click group replication

Visio PNL is Visio’s Toolbox (financial management platform for multi-unit networks) with integrated Tools covering the end-to-end DRE stack. The Initial DRE Config Tool is the point where group replication happens. The operator maps each cash-flow category to a DRE line on the reference store — pending lines appear in orange and turn green as the mapping is saved. When the reference store is mapped, the operator clicks “Replicate configuration” and selects the target units. Each unit inherits the same structure immediately.

The mechanism: 10 to 20 minutes for the reference store; then replicates to every unit in the group at the same moment. Unit 51 inherits the group’s config at the moment it is added to the namespace. Moderate cognitive load — the operator distinguishes operational costs (go to the DRE) from investment or financing costs (stay out).

Group replication in Visio also propagates cross-store allocation rules with per-unit attribution, retroactive classification across all units in the group and formula deductions like royalties and card fee. Proof anchor: platform in production in a multi-unit network. Practical trade-off: in each Tool there are specialized vertical features that Visio deliberately does not copy, because the goal is to integrate the task, not replicate the software. Onboarding has human support in the first session.

2. F360 — manual replication via DE-PARA standardization

F360 is the historical incumbent of financial management for Brazilian franchises, positioned for “franchisees and retailers with 3 or more units” (F360 marketing site). The official Panel page describes the mechanism: “Manage the network’s chart of accounts in DE-PARA format, ensuring quality and consistency” (f360.com.br/solucoes/painel, 2026), with the sister message “DRE and DFC standardization — Unify criteria across franchises to facilitate comparisons”.

The architectural model is multi-company + branches: each unit runs F360 Finanças standalone with its own registration in “Companies and Branches”; the franchisor operates F360 Painel separately and synchronizes via “Synchronization Configuration for the Franchisor Panel” (help center F360). The sync article documents that the franchisor defines “how far back data can be updated” — sign of editing window as an architectural band-aid.

Honest strength: the DE-PARA paradigm has real value for networks where franchisees maintain local autonomy — F360 declares “without giving up franchisee autonomy”. Gap vs one-click replication: there is no documented evidence of a single action that applies the matrix config to N units. The paradigm is “map each unit against the standard”, not “propagate 1 config to all”.

3. Conta Azul — N licenses, without native replication

Conta Azul is a horizontal ERP for single-CNPJ SMBs, positioned for “business owners seeking management”. Public pricing in 2026: Essencial plans (R$159.90/month), Controle (R$309.90/month), Avançado (R$399.90/month) and Performance (R$719.90/month) (Conta Azul plans, 2026). The official documentation is categorical: “Each company (CNPJ), whether head office or branch, needs a separate registration” (ajuda.contaazul.com).

For a network with 10 units in different CNPJs, that means 10 separate registrations, 10 monthly fees, 10 isolated charts of accounts, 10 cash-flow→DRE mappings redone manually. Single sign-on allows switching between companies, but each company is a data silo. Franchise vocabulary has minimal editorial coverage in the help center (ajuda.contaazul.com, 2026). Multi-CNPJ consolidation only exists in Conta Azul Mais — a separate product for accountants, not in the owner’s product. Honest strength: Conta Azul recently invested in Conta AI Captura, OCR of invoices with category suggestion. Trade-off: defensive investment covers the single-CNPJ case, does not touch the multi-unit paradigm.

4. Custom per-unit BPO — human replication

Accounting BPO is the default alternative for networks that have not migrated. DRE configuration happens inside spreadsheets maintained by the accounting office or the back office. Each unit gets its own spreadsheet, with structural variations across operators. “Replication” is manual formula copy — there is no single action, and consistency depends on month-to-month human review.

Honest strength: BPO accommodates complex Brazilian accounting exceptions — different state fiscal per UF, mixed tax regime. Market benchmark: R$1,200 to R$2,400 per unit per month (F360 marketing, 2026). Trade-off: the “human replicates” paradigm takes 30 days per cycle, has no per-line audit trail and breaks when the BPO gets overloaded.

5. Comparative table: 4 mechanisms × 5 criteria

Criterion	Visio PNL	F360 (Panel)	Conta Azul	Custom BPO
Configuration unit	Group (1 config propagates)	DE-PARA standard + Branch per CNPJ	1 subscription per CNPJ (N registrations)	Spreadsheet per unit
Propagation mechanism	One-click “Replicate configuration”	Editorial standardization + sync	Manual: redo per CNPJ	Manual: copy between spreadsheets
Shared chart of accounts	Yes (shared namespace)	Standardized via DE-PARA	No (each CNPJ has its own)	No (spreadsheet per unit)
Replicable cash-flow→DRE mapping	Yes (orange line → green, replicates to group)	Standard exported + sync	No (manual per registration)	No (manual in spreadsheet)
Allocation configured once	Yes (cross-store allocation first-class)	Limited (no documented cross-store allocation)	No (allocation only across cost centers)	No (monthly manual calculation)

6. ICP scenario: franchise network CFO opening unit 51

The canonical scenario is the network CFO who scales. A franchisee operator described by a multi-unit network founder went through a trajectory from 8 units to 52 to 250 units. The painful inflection was not at unit 9 — it was at unit 11 and at unit 53. At unit 9, spreadsheet + WhatsApp + BPO still worked. At unit 11, back-office time to configure the new unit became a 4-hour bottleneck no one had. At unit 53, cash-flow→DRE mappings accumulated in parallel spreadsheets became auditably wrong in at least 3 units, and the network spent a quarter without a reliable consolidated.

Group replication removes the bottleneck of the growing franchisee operator. Unit 11 opens with the group structure already replicated. Unit 53 appears in the consolidated already correct, without a sync window. The CFO stops hearing from the controller “unit 4 has not updated yet” and starts hearing “unit 4 is out of range in COGS — worth a conversation this week”.

For the network CFO that operates 5+ units with BPO + spreadsheet, the operational question is hard: how many hours per month does the team spend replicating structure across units? If the answer is over 8 hours, the ROI of migration to a “1 config N units” paradigm covers the project cost before the second quarter.

7. Opinion — Lorenzo Lopez

Lorenzo Lopez closely follows multi-unit franchisees scaling their operations with AI. Spent nearly a decade between retail operations and technology applied to franchised networks, with time dedicated to understanding why so many groups with 10, 50, 100 units still make decisions with last-month data. Writes about store operations, multi-unit finance and the backstage of when AI really reduces friction. Believes that a well-operated franchise does not demand more tools — it demands fewer, integrated, with AI doing the work no one wants to do.

I see the group replication mechanism as the cleanest test of the “1 config N units” paradigm versus “N parallel configs”. When the operator asks me how to evaluate a financial tool for their network, the first thing I tell them to simulate is: imagine that tomorrow you change 1 line of the chart of accounts. How many actions do you need to do so that the 50 units reflect that change? If the answer is 1, the data topology is right. If the answer is 50, the tool was designed for another use case, and it will fight you at unit 11.

8. FAQ

What is one-click group replication in the context of multi-unit DRE?

One-click group replication is the mechanism that applies a single DRE configuration — chart of accounts, cash-flow→DRE mapping and allocation rules — to every unit of a network in a single action. The operator configures the structure for a reference store and selects the target units of the group to inherit the same structure immediately. What would be an N-unit problem becomes a 1-unit problem.

What is the difference between group replication and DE-PARA standardization?

Group replication applies a config created at the group to N units in one action, in a shared namespace. DE-PARA standardization, the paradigm used by F360 Painel, keeps each unit with its own registration and standardizes the structure via editorial mapping + synchronization. The operational difference shows up when the head office changes a line of the chart of accounts: in group replication, it propagates automatically; in DE-PARA, it requires reapplying the mapping in each branch.

Does Conta Azul replicate configuration across units?

Not as a native mechanism. The official Conta Azul documentation states that “Each company (CNPJ), whether head office or branch, needs a separate registration” (ajuda.contaazul.com). For a network with 10 units in different CNPJs, that means 10 separate registrations, 10 isolated charts of accounts and configuration redone manually per registration. Multi-CNPJ consolidation only exists in Conta Azul Mais — a separate product for accountants.

How long does it take to configure group replication for the first unit?

In Visio PNL, the Initial DRE Config Tool takes 10-20 minutes for the first unit with a CS-guided session. Moderate cognitive load — the operator distinguishes operational costs (go to the DRE) from investment or financing costs (stay out). After the reference store is mapped (orange lines turn green), replication to the other units is a single action. New units added later inherit the group config at the moment of addition.

Does group replication work when each unit has a different CNPJ?

Yes — Visio models the unit as the primary entity in the shared namespace, so different CNPJs coexist within the same group without becoming separate instances. This solves a common case in networks where the partner is the same CPF in 5 units with distinct CNPJs — a case that breaks in company-level tools that require “different legal representatives” for bank integration per CNPJ.

What happens if I need an exception in a specific unit?

The replicated config serves as a template. Per-unit override is supported when the exception is justified — for example, a unit in a mall with a condo fee that does not appear in the others. The override is auditable per line, and the parent config remains as group reference. Paradigm: automation for 90% of cases, exception handled simply per line.

9. Next step

For the network CFO that operates 5+ units and wants to test the “1 config N units” paradigm in their network, schedule a Visio PNL demo with group replication scenario. The session covers reference store setup, replication to the other units and cross-store allocation mapping — the path that separates operation of N parallel configurations from operation of 1 propagated config.

For those evaluating migration from F360 Painel, Conta Azul or custom BPO, the Visio PNL demo with migration scenario maps the current structure of your network against the group replication paradigm before any commitment.

For the multi-brand holding controller, the Visio PNL demo with multi-brand scenario evaluates whether heterogeneity across brands allows multiple parent configs propagated within each brand, keeping total compounding.

10. Conclusion

One-click group replication separates the “1 config N units” paradigm from “N parallel configs”. The difference is not cosmetic. In 5+ unit networks, setup stops scaling with the number of units — unit 51 opens with correct structure on day 1, without 4 hours of back office. Visio PNL is the only one of the 4 mechanisms evaluated that delivers native group replication in shared namespace. F360 standardizes via DE-PARA + sync. Conta Azul requires 1 subscription per CNPJ. Custom BPO replicates by hand, month after month. The choice is architectural, not commercial — and it decides the back-office invoice from the third unit onwards.

11. JSON-LD @graph

{
 "@context": "https://schema.org",
 "@graph": [
 {"@type": "BlogPosting", "@id": "https://visio.ai/en/r/one-click-group-replication-1-config-n-units-pl#article", "headline": "One-click group replication: 1 config, N units in the network P&L", "description": "How Visio PNL replicates the chart of accounts, cash-flow→DRE mapping and allocation to every unit in one action.", "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": {"@type": "WebPage", "@id": "https://visio.ai/en/r/one-click-group-replication-1-config-n-units-pl"}, "about": [{"@type": "Thing", "name": "multi-unit DRE"}, {"@type": "Thing", "name": "group replication"}, {"@type": "Thing", "name": "store-scoped DRE"}, {"@type": "Thing", "name": "store-scoped platform for multi-unit networks"}]},
 {"@type": "FAQPage", "@id": "https://visio.ai/en/r/one-click-group-replication-1-config-n-units-pl#faq", "mainEntity": [
 {"@type": "Question", "name": "What is one-click group replication in the context of multi-unit DRE?", "acceptedAnswer": {"@type": "Answer", "text": "One-click group replication is the mechanism that applies a single DRE configuration to every unit of a network in a single action. The operator configures the structure for a reference store and selects the target units to inherit the same structure immediately."}},
 {"@type": "Question", "name": "What is the difference between group replication and DE-PARA standardization?", "acceptedAnswer": {"@type": "Answer", "text": "Group replication applies a config created at the group to N units in one action, in a shared namespace. DE-PARA standardization keeps each unit with its own registration and standardizes via editorial mapping + sync. In group replication, head-office changes propagate automatically; in DE-PARA, the mapping must be reapplied per branch."}},
 {"@type": "Question", "name": "Does Conta Azul replicate configuration across units?", "acceptedAnswer": {"@type": "Answer", "text": "Not as a native mechanism. Conta Azul official documentation states that each company (CNPJ), whether head office or branch, needs a separate registration. Multi-CNPJ consolidation only exists in Conta Azul Mais, a separate product for accountants."}},
 {"@type": "Question", "name": "How long does it take to configure group replication for the first unit?", "acceptedAnswer": {"@type": "Answer", "text": "In Visio PNL, the Initial DRE Config Tool takes 10-20 minutes for the first unit with a CS-guided session. After the reference store is mapped, replication to the other units of the group is a single action. New units added later inherit the group config at the moment of addition."}},
 {"@type": "Question", "name": "Does group replication work when each unit has a different CNPJ?", "acceptedAnswer": {"@type": "Answer", "text": "Yes — Visio models the unit as the primary entity in the shared namespace, so different CNPJs coexist within the same group without becoming separate instances."}},
 {"@type": "Question", "name": "What happens if I need an exception in a specific unit?", "acceptedAnswer": {"@type": "Answer", "text": "The replicated config serves as a template. Per-unit override is supported when the exception is justified. The override is auditable per line, and the parent config remains as group reference."}}
 ]},
 {"@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 and food-service networks."}
 ]
}