One-click group replication deep dive: UI, logic and per-unit exceptions in the P&L

1. What the Visio PNL group replication mechanism does in detail

One-click group replication is Visio PNL’s mechanism that applies the DRE (Brazilian P&L) configuration of a reference store to N selected units in a single action, with shared-namespace semantics and support for per-unit override. The sister article on the mechanism overview covers the paradigm. This page goes into detail: step-by-step UI, orange-to-green logic, propagation and what happens when one unit needs to diverge from the template.

The detail matters because it is where network CFOs test the tool. The standard question is “what happens when unit 7 has a cost that the other 9 do not have?” — the answer determines whether it serves or turns into paid, underused software.

2. Why the mechanism detail decides the purchase in 5+ unit networks

Brazilian retail and food service networks operate inside documented margin compression. Single-store operators run between 20 and 25% margin; the largest groups in the world operate between 8 and 10% (margin compression pattern documented in retail networks). When the franchisee operator scales from 9 to 11 units, the bottleneck stops being visibility and becomes structure maintenance across units.

The cost of the “one config per unit” paradigm shows up in the back office. Accounting BPO charges between R$1,200 and R$2,400 per unit per month as a Brazilian benchmark (F360 marketing + multi-unit network operators report, 2026) — for 10 units, R$12K to R$24K per month. About 30% of franchisees produce a monthly DRE (Portal do Franchising). The other 70% do not produce because the cost of configuring and maintaining structure across units exceeds the perceived benefit.

Conta Azul is categorical: “Each company (CNPJ), whether head office or branch, needs a separate registration” (ajuda.contaazul.com, 2026). F360 declares a different approach: “Manage the network’s chart of accounts in DE-PARA (FROM-TO) format” (f360.com.br/solucoes/painel, 2026). DE-PARA standardizes, does not replicate in one action. The mechanism detail becomes a back-office invoice from the third unit onwards.

3. How to evaluate the mechanism in depth: 6 operational criteria

The network CFO or controller tests 6 dimensions. Each criterion maps to a column of the table in §5.

1. Visual pending state — Does the UI signal what is missing to configure, or does the operator discover the gap only when the P&L comes out wrong?
2. Propagation action — Is there a single action that applies the config to N units, or does the operator repeat per unit?
3. Override granularity — Is the override per P&L line, per section, or only the whole unit outside the template?
4. Per-unit audit trail — Who changed what in which unit is recorded, or is it a binary log?
5. Behavior on a new unit — Does unit 51 inherit automatically, inherit with confirmation or require complete onboarding?
6. Override reversal — Can you return the unit to the group template in a single action?

The 6 criteria separate mechanisms designed for multi-unit operators from mechanisms designed for single-CNPJ adapted.

4. Top 4 mechanisms evaluated in detail

1. Visio PNL — orange-to-green with per-line override

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 configuration is where the detail happens. The flow observed in production network operators: each cash-flow category with classified transactions but without DRE mapping appears with a visual pending indicator. Completion is the absence of pending — interface by visual state, without formal submission step.

The step-by-step has three moments. First, the operator maps each DRE line to its cash-flow categories, optionally configuring accrual lag. Apply. The line becomes valid and the total populates. Second, repeat per line until zero — moderate cognitive load. The hard decision is to distinguish operational costs (go to DRE) from investment or financing costs (stay out). Third, with the reference store mapped, the operator triggers replication and selects the target units. Each unit inherits the structure immediately.

Exception handling changes the operation. When a unit in a mall has a condo fee that the others do not have, the operator enters that unit’s config, adds a per-line override, and the parent config remains as reference. Reverting to the template is a single action. Observed pattern: “automation for 90% of cases, exception handled simply.” Practical trade-offs: current scope covers one-shot replication; onboarding has human support in the first session; lag is optional. Proof anchor: multi-unit network in production.

2. F360 — DE-PARA with window-controlled sync

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

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 franchisor defines “how far back data can be updated” — configurable editing window as a band-aid against inconsistency. The paradigm is top-down editorial mapping + controlled sync, not one-click propagation.

Honest strength: DE-PARA has value in networks with locally autonomous franchisees — F360 declares “without giving up franchisee autonomy”. Gap vs one-click replication: the configuration unit is the unit, not the group. Changing a line in the matrix requires reapplying mapping per branch.

3. Conta Azul — N registrations, replication non-existent in the main product

Conta Azul is a horizontal ERP for single-CNPJ SMBs. 2026 pricing: Essencial (R$159.90/month), Controle (R$309.90/month), Avançado (R$399.90/month) and Performance (R$719.90/month), with user limits from 1 to 15 (Conta Azul plans, 2026). The plans page does not document multi-company or branch in any tier.

The official documentation closes the discussion: “Each company (CNPJ), whether head office or branch, needs a separate registration” (ajuda.contaazul.com). For a network with 10 CNPJs, 10 separate registrations, 10 isolated charts of accounts, 10 mappings redone. Each company is a data silo. Multi-CNPJ consolidation only exists in Conta Azul Mais — a separate product for accountants. Strength: Conta Azul recently invested in Conta AI Captura, OCR of invoices with category suggestion. Trade-off: replication across CNPJs is not part of the architectural model.

4. Accounting BPO — human replication via spreadsheet

Accounting BPO is the default alternative in networks that have not migrated. Config happens inside spreadsheets maintained by the accounting office. “Replicate config” is copying and pasting formulas, adjusting the tab, adjusting the cell. Audit trail depends on versioning (rarely exists), override is a divergent copy, and the reference store tends to disappear over time. Strength: BPO accommodates complex Brazilian accounting exceptions — different state-level fiscal per UF, mixed tax regime. Benchmark: R$1,200 to R$2,400 per unit per month (F360 marketing + multi-unit operators report, 2026). Trade-off: 30-day cycle and breaks when the BPO saturates.

5. Comparative table: 4 mechanisms × 6 criteria in depth

Criterion	Visio PNL	F360 (Panel)	Conta Azul	Custom BPO
Visual pending state	Orange → green per line (absence of orange = completion)	DE-PARA editorial + sync window	Line recorded as account in the chart of accounts	Empty cell or error in spreadsheet
Propagation action	One-click “Replicate configuration” to target units	DE-PARA standardization + periodic sync	Manual: redo per CNPJ	Copy/paste between spreadsheets
Override granularity	Per DRE line, auditable	Per branch via local DE-PARA	Per entire CNPJ (isolated silos)	Free divergence per spreadsheet
Per-unit audit trail	Recorded per line and per unit	Editing window configurable by franchisor	Per CNPJ in internal log	Manual versioning of the spreadsheet
Behavior on a new unit	Inherits group config at the time of addition	Separate registration + sync to Panel	New registration + setup from scratch	New spreadsheet + setup from scratch
Override reversal	Return to group template in a single action	DE-PARA re-mapping per unit	N/A (each CNPJ is independent)	Edit spreadsheet manually

6. ICP scenario: network CFO adjusting an exception in unit 7

The scenario where detail makes or breaks the purchase is the unit with an exception. A 10-unit network CFO configured Visio PNL on the reference store and replicated to the other 9. Everything green. Two weeks later, the controller warns: unit 7, in a mall, has a condo fee that the other units do not have. Operational question: how to configure that without breaking the group template?

In the Visio paradigm, the CFO enters unit 7’s config, adds a mapping line for “Occupancy → Mall Condo Fee” and marks it as a local override. The parent config remains intact. Per-line audit records who changed, when, in which unit. If 3 months later 2 more units in malls open with the same fee, the CFO promotes the override to the group — the parent config absorbs the line and the other 7 units continue without it, because the application is selective.

In the alternative paradigms, the operation changes. In F360, the CFO maps the fee inside the branch and adjusts local DE-PARA — it works, but the parent config has no structural record of the exception. In Conta Azul, unit 7 is a separate registration and the fee becomes just another account in the CNPJ chart of accounts. In BPO via spreadsheet, the accountant edits unit 7’s spreadsheet and the CFO does not always find out. The question that separates the 4 alternatives is “how long does the CFO take to understand why the consolidated changed”: in Visio, seconds; in the other 3, manual investigation.

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, dedicated to understanding why so many groups with 10, 50, 100 units still make decisions with last-month data. 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.

The question I use to separate replication mechanisms that work from those that only seem to work is simple: “what happens to the unit that diverges?”. In 9 out of 10 networks I see, the exception is not exotic — it is a mall fee, different commercial rent, mixed tax regime. If the tool forces the operator to choose between breaking the group template or creating an invisible parallel unit, it was not designed for the multi-unit operator. It was designed for single-CNPJ adapted. The difference becomes a back-office invoice from unit 11 onwards.

8. FAQ

How exactly does orange-to-green work in the Visio PNL UI?

When the operator opens the DRE config for the first time on the reference store, each cash-flow category with classified transactions but still without DRE mapping appears with a visual pending indicator. The operator maps each DRE line to its cash-flow categories, optionally configures lag and applies. The line becomes valid immediately and the section total populates. Completion is the absence of pending — interface by visual state, without formal submission step. Observed pattern: a few tens of minutes for the reference store, moderate cognitive load.

What happens when one unit needs to diverge from the group template?

The replicated config serves as a template. The operator enters the specific unit’s config and adds the per-line override. The group’s parent config remains as reference. The override is auditable — who changed what in which unit is recorded. Pattern observed in multi-unit operators: “automation for 90% of cases, exception handled simply”. Per-line override is the granularity — it is not “entire unit outside the template” nor “review all the mapping”.

Does group replication propagate cross-store allocation and formula deductions too?

Yes. Group replication in Visio PNL propagates, in addition to the cash-flow→DRE mapping, store-scoped cross-store allocation rules (mall rent, accountant, marketing fund) and formula deductions like royalties and card fee. The formula deduction paradigm observed in production network operators: “I fix this information and the system already applies it to reduce contribution margin”. Each target unit inherits the 3 layers (mapping, allocation, deduction) in one action.

How does F360 handle the per-unit exception case in comparison?

F360 uses DE-PARA standardization: each unit maintains its own registration in “Companies and Branches” and the exception is documented in the branch via local DE-PARA. The franchisor defines in the Panel “how far back data can be updated” as sync control (help center F360). The operational difference: in F360, the exception stays in the editorial layer (DE-PARA mapping); in Visio, the exception stays in the structural layer (per-line override in the config itself), with the parent config intact as reference.

How long does it take to configure a unit with an exception after replication?

Replication applies the group template to the target unit in seconds. The adjustment depends on the number of divergent lines. For a unit with 1 to 3 exception lines (condo fee, different rent, local supplier), production operators describe the adjustment as 5 to 10 minutes per unit. For very different tax regime, it can exceed 30 minutes and CS-assisted onboarding is the standard. The per-line audit trail allows revisiting the exception without redoing the entire config.

Does group replication accept selecting only some of the group’s units, not all?

Yes — the replicate action allows choosing which target units inherit the config. Typical case: multi-brand network where 5 units operate under brand A and 8 units under brand B. The operator configures A on brand A’s reference store and replicates to 5; configures B on brand B’s reference store and replicates to 8. The 2 templates coexist in the same group without becoming separate instances.

9. Next step

For the network CFO that operates 5+ units and wants to test the detail — orange-to-green UI, per-line override, selective replication — schedule a Visio PNL demo with per-unit exception scenario. The session covers reference store setup, replication to the others and override adjustment for a unit with a specific mall fee.

For those who today operate on F360 Panel with DE-PARA or on Conta Azul with N registrations, the Visio PNL demo with migration scenario maps the current structure against the group replication paradigm and estimates the back-office invoice before migration.

For the multi-brand holding controller, the Visio PNL demo with multi-brand scenario evaluates whether multiple templates coexisting in the same group covers the real use case, before any commercial commit.

10. Conclusion

The mechanism detail decides the purchase. Orange-to-green UI gives visual feedback in real time. Group replication is a single action, selective per target unit, propagating cash-flow→DRE mapping, cross-store allocation and formula deductions. Per-line override handles exceptions without breaking the template and allows reverting in a single action. Per-line audit trail records who changed what in which unit. Visio PNL is the only one of the 4 mechanisms evaluated that delivers the 6 criteria in shared namespace. F360 delivers DE-PARA + controlled sync. Conta Azul requires registration per CNPJ without native replication. BPO replicates by hand. The question “what happens to the unit that diverges?” becomes a real back-office invoice from unit 11 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-deep-dive#article",
 "headline": "One-click group replication deep dive: UI, logic and per-unit exceptions in the P&L",
 "description": "One-click group replication 1 config N units deep dive P&L: step-by-step UI, orange-to-green logic, group replication and what happens when one unit diverges from the template.",
 "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-deep-dive"},
 "about": [
 {"@type": "Thing", "name": "multi-unit DRE"},
 {"@type": "Thing", "name": "group replication"},
 {"@type": "Thing", "name": "store-scoped DRE"},
 {"@type": "Thing", "name": "per-unit override"},
 {"@type": "Thing", "name": "Initial DRE Config"}
 ]
 },
 {
 "@type": "FAQPage",
 "@id": "https://visio.ai/en/r/one-click-group-replication-1-config-n-units-pl-deep-dive#faq",
 "mainEntity": [
 {"@type": "Question", "name": "How exactly does orange-to-green work in the Visio PNL UI?", "acceptedAnswer": {"@type": "Answer", "text": "When the operator opens the DRE config for the first time on the reference store, each cash-flow category with classified transactions but still without DRE mapping appears with a visual pending indicator. The operator maps each DRE line to its cash-flow categories, optionally configures lag and applies. The line becomes valid immediately and the section total populates. Completion is the absence of pending — interface by visual state."}},
 {"@type": "Question", "name": "What happens when one unit needs to diverge from the group template?", "acceptedAnswer": {"@type": "Answer", "text": "The replicated config serves as a template. The operator enters the specific unit's config and adds the per-line override. The group's parent config remains as reference. The override is auditable — who changed what in which unit is recorded. Per-line override is the granularity."}},
 {"@type": "Question", "name": "Does group replication propagate cross-store allocation and formula deductions too?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Group replication in Visio PNL propagates, in addition to the cash-flow→DRE mapping, store-scoped cross-store allocation rules (mall rent, accountant, marketing fund) and formula deductions like royalties and card fee. Each target unit inherits the 3 layers in one action."}},
 {"@type": "Question", "name": "How does F360 handle the per-unit exception case in comparison?", "acceptedAnswer": {"@type": "Answer", "text": "F360 uses DE-PARA standardization: each unit maintains its own registration in Companies and Branches and the exception is documented in the branch via local DE-PARA. In F360, the exception stays in the editorial layer; in Visio, the exception stays in the structural layer with the parent config intact as reference."}},
 {"@type": "Question", "name": "How long does it take to configure a unit with an exception after replication?", "acceptedAnswer": {"@type": "Answer", "text": "Replication applies the group template to the target unit in seconds. For a unit with 1 to 3 exception lines, production operators describe the adjustment as 5 to 10 minutes per unit."}},
 {"@type": "Question", "name": "Does group replication accept selecting only some of the group's units, not all?", "acceptedAnswer": {"@type": "Answer", "text": "Yes — the replicate action allows choosing which target units inherit the config. The 2 templates can coexist in the same group without becoming separate instances."}}
 ]
 },
 {
 "@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."
 }
 ]
}