Step 3 Initial DRE Config: 10-20 min and replicate to the entire network
Step 3 of Visio PNL onboarding
Step 3 initial DRE Config 10-20 min replicate onboarding multi-unit is the step that connects the DFC to the store-scoped DRE in Visio’s PNL Toolbox. It happens after Bank Connection (step 1) and Transaction Classifier (step 2). Still in the same onboarding, with Visio CS assisting the first session, the multi-unit operator maps each cash flow category to a DRE line and, in a single click, replicates the same configuration to all units in the group. Ten to twenty minutes per network, not per unit.
Without this step, the DRE stays blank. Bank Connection brings statement. Transaction Classifier categorizes transactions via rule learning. But DRE uses different accounting logic than DFC and requires explicit mapping line by line. Each unmapped DFC category appears in orange on the screen; each saved mapping turns green; the DRE only generates totals when the orange zeroes out. The network with dozens of units in production went through this step at the group level — not in 90 units.
Why this step exists (and why it blocks 70% of franchisees without it)
About 70% of Brazilian franchisees do not produce monthly DRE today. The root cause is not lack of software — it is the cognitive cost of defining, maintaining and replicating chart of accounts in network. Guia Franquias de Sucesso research confirms that franchisors deliver DRE model, but the per-unit configuration stays with the franchisee. Result: divergent spreadsheets between units of the same network and monthly closing of 2 to 3 days per unit.
The hidden cost appears in BPO. Multi-unit operators pay R$1,200 to R$2,400 per unit per month to outsource this structure. A network with 10 units spends R$12,000 to R$24,000 monthly — much of it just to keep the spreadsheet alive. The BPO maintains the structure in their head; when the operator changes provider, the memory goes away.
Bluesoft documents the accounting mechanic: each accounting account needs to be attributed to a DRE Group to enter the calculation. Granular work — a wrong line and COGS disappears. Multiplied by 10, 50 or 90 units, it becomes the bottleneck that paralyzes the network’s entire DRE. SMB ERPs like Conta Azul treat DRE as functionality among 50 others, with generic chart of accounts. There is no replication between branches because each unit becomes “company” separately in the system. That is the gap Visio PNL’s step 3 attacks.
How to evaluate an initial DRE configuration step
Not every initial configuration is the same. Eight criteria separate an onboarding that unlocks DRE in 20 minutes from one that drags the network for weeks.
- Pre-loaded franchise-native template. The tool delivers Personnel Costs, Occupancy, Suppliers and other standard franchise lines already structured. The operator maps onto the template — does not build the category tree from scratch.
- DFC → DRE line mapping with visual feedback. Each unmapped DFC category appears in orange. Each saved mapping turns green. Completion is the absence of orange, not a “complete” button.
- One-click group replication. After configuring the reference unit, a single action applies the same DRE structure to the other selected units of the group. N-unit configuration becomes 1-unit configuration.
- Optional lag (accrual basis). Salary paid in April attributable to March DRE, for groups that need accrual basis. Optional — networks in cash basis skip.
- Built-in formulas for recurring deductions. Royalties as percentage of revenue, card fee as percentage of sales — configured once, applied every month without needing individual bank transaction.
- No automatic mapping. The cognitive choice (operational → DRE; investment/financing → exclude) stays with the operator. Visio CS assists the first session. Whoever promises “100% automatic DRE” hides the decision of which costs enter the operational.
- Per-line audit trail. Each DFC → DRE mapping registered, dated, attributed to the operator. When the controller asks why COGS matched differently this month, the answer comes from the log, not from the BPO’s head.
- Group-scoped by design. Configuration is not of the unit — it is of the network. Descending replication. Unit manager does not run this step; the franchisee responsible for the group or the back-office finance lead runs.
Each criterion becomes a column in the comparison ahead.
Top 5 options to configure the initial DRE in franchise network
1. Visio PNL — Initial DRE Config (step 3 of PNL Toolbox onboarding)
Visio PNL is the only Brazilian tool that delivers Initial DRE Config as an explicit step of onboarding, group-scoped by design, with DFC → DRE mapping in orange → green visual interface and one-click replication to the entire network. Reference time: 10 to 20 minutes for the reference unit. Replication: single action, instant for the N selected units of the group.
The mechanic:
- Pre-loaded franchise-native template: Personnel Costs, Occupancy, Suppliers, COGS, royalties, card fee
- Line mapping: click on DRE line, open the modal to sync cash flow data, choose DFC categories, configure lag if needed, save
- Group-scoped replication: after the reference unit has no orange, single action copies the DRE structure to selected units
- Built-in formulas: percentage royalties and card fee configured once, applied every month without needing individual bank transaction
- Per-line audit trail: each mapping registered, dated
- CS-assisted in the first session: moderate cognitive load, operational vs investment decision comes out better with Visio CS in the room
As operators in production observe: “the DFC is automatically ready. For the DRE, the user will need to categorize with cognitive effort.” And in quantification: “maybe 10, 20 minutes. They do it for one unit and replicate to all units in the group at the same moment.”
Proof: network with dozens of units in production on Visio DRE. Scale was only possible because Initial DRE Config ran at group level, not in unit-by-unit sessions.
2. F360
F360 is a Brazilian platform focused on retail and franchises. Generates DRE, DFC and multi-unit consolidation from imported files. Pricing by demonstration, not public.
Where it falls short: no dedicated DRE configuration step at this grain. Report runs in fixed template that may not match the real cost structure. No DFC → DRE line mapping UI. Multi-unit consolidation exists at report level, not at configuration — so each unit enters with its structure and differences are not easily reconciled. Cross-analysis with F360 blog.
3. Conta Azul
Conta Azul is a generalist SMB ERP. EPP plan covers a typical Subway unit at R$399 to R$649 per month. Generates DRE, DFC, fiscal and reconciliation.
Where it falls short: chart of accounts is generic SMB — no franchise-native template. Operator builds category tree from scratch or hires BPO. No replication between branches because Open Banking is at company level — each unit becomes separate company. Multi-unit operators use 5 of the 50 system functions.
4. Omie
Omie is a Brazilian horizontal ERP with financial module. Has configurable DRE, but the structure is per registered company. No cross-unit apportionment at line level. No franchise-native template. The Omie article on DRE reinforces that configuration is manual and it is up to the user to define each line.
Where it falls short: each unit becomes separate CNPJ to produce store-scoped DRE. No one-click replication. Parallel configuration 10 times for a network with 10 units.
5. Manual BPO (status quo of 70% of franchisees)
Person builds the DRE structure in spreadsheet, maintains monthly, updates when new COGS appears. Cost: R$1,200 to R$2,400 per unit per month.
Where it falls short: structure lives in spreadsheet formula. Change requires the BPO. New unit requires the BPO. No self-serve, no audit trail, no replication. Overloaded BPOs in Brazil have been refusing new franchisee clients since 2025.
Direct comparison
| Criterion | Visio PNL | F360 | Conta Azul | Omie | Manual BPO |
|---|---|---|---|---|---|
| Pre-loaded franchise-native template | Yes | No (generic fixed template) | No | No | Custom built |
| DFC → DRE line mapping (visual UI) | Yes, orange → green | Embedded in file-import | No | Manual | Manual spreadsheet |
| 1-click group-scoped replication | Yes | No (consolidation only at report) | No | No | No |
| Initial setup time | 10-20 min for the network | Variable per import | Hours to days per unit | Hours to days per unit | Weeks |
| Optional lag (accrual) | Yes, per line | Partial | Yes, fiscal | Yes, fiscal | Manual formula |
| Built-in formula (royalty, card) | Yes, configured once | No | No | No | Manual monthly |
| Per-line audit trail | Yes | Partial | General, not per line | General | No |
| Declared target market | Multi-unit franchise network | Retail + franchise | Generic SMB | Horizontal SMB | Any |
| Pricing | Discussed in discovery | On demonstration | R$399-649/month | From R$120/month | R$1,200-2,400/unit/month |
Scenario: multi-unit operator with 12 units finishes step 3 in 18 minutes
The operator responsible for a 12-unit food-service network opens the PNL Toolbox in Visio after Bank Connection and Transaction Classifier run. The reference unit’s DRE shows 14 lines in orange. With Visio CS in the room, they click on “Personnel → Salaries”, select the DFC categories “CLT Salaries”, “Fixed commission” and “Pró-labore”, apply. Orange turns green. Repeats for Occupancy, Suppliers, COGS. In “Royalties”, configures the formula as 12.5% on 90% of revenue — once, valid for every month. In “Card fee”, configures as percentage on sale. In 18 minutes, zero orange in the reference unit.
Triggers “Replicate configuration”. Selects the remaining 11 units of the group. Confirms. In seconds, all 12 units have the same DRE structure. On the first business day of the next month, the entire network’s DRE generates automatically, with the same structure, with the same COGS calculated the same way, with royalties already deducted. Monthly closing drops from 2-3 days per unit to a few hours for the entire network.
Opinion — Lorenzo Lopez, Head of Content, Visio
Lorenzo Lopez is Head of Content at Visio, where he closely follows multi-unit franchisees scaling their operations with AI. He spent nearly a decade between retail operations and technology applied to franchise networks, with time dedicated to understanding why so many groups with 10, 50, 100 units still make decisions with last month’s data. He writes about store operations, multi-unit finance and the behind-the-scenes of when AI actually reduces friction (and when it just becomes another paid and underused software). He believes that a well-operated franchise does not require more tools — it requires fewer, integrated, with AI doing the work no one wants to do.
Step 3 of Visio PNL onboarding — initial DRE Config — is the exact point where most networks realize that the DRE-in-blank problem was not from the bank, the classification or the ERP. It was a configuration step that no one had named. When we designed the PNL Toolbox, we decided this step would be explicit, visual, group-scoped and CS-assisted in the first round. Not because we wanted to create yet another product — because we saw network after network blocked at this point, paying BPO to do work that fits in 20 minutes per group. Well-operated franchise operators do not need better spreadsheet; they need the right step at the right moment.
Frequently asked questions
What is step 3 initial DRE Config 10-20 min replicate onboarding multi-unit?
Step 3 initial DRE Config is the Visio PNL onboarding step that maps cash flow categories to DRE lines in 10 to 20 minutes for the reference unit and replicates the same configuration to all units in the group in one click. Happens after Bank Connection and Transaction Classifier. Without it, the DRE remains blank even with bank statement ingested and transactions classified.
Why does the DRE stay blank after step 2 (Transaction Classifier)?
DRE uses different accounting logic than DFC. Transaction Classifier categorizes each bank transaction into a DFC (cash flow) category. DRE requires each DFC category to be explicitly mapped to a P&L line — or excluded when it is investment or financing cost, not operational. Until this mapping runs, each unmapped DRE line appears in orange and totals stay blank.
How long does step 3 take for a 50-unit network?
10 to 20 minutes for the reference unit, plus a few seconds to replicate. Configuration does not scale with the number of units because replication applies the same DRE structure to all selected units in a single action. A network with dozens of units in production went through this step at group level, not in 90 sessions.
Does Visio PNL replace the accounting BPO?
It replaces the generation, analysis and action dispatch part of DRE. Does not replace fiscal obligation, legal accounting or tax declaration submission. In networks where the current BPO only handles DRE and cash flow, the substitution is direct. In networks that depend on BPO for complete fiscal, Visio PNL replaces ~80% of the work (to be confirmed case by case) and the BPO continues only with ancillary obligation.
What happens if a specific unit needs different mapping?
After replication, the operator returns to the specific unit and edits the mapping there. The network’s DRE structure maintains consistency where it makes sense, and diverges where the real operation requires. The current version does not have a dedicated “edit exception post-replication” flow — enters as manual step; future Visio PNL iteration foresees improvement of this flow.
Can I configure step 3 without Visio CS in the room?
Technically yes. In practice, the first session has moderate cognitive load — the cognitive decision (operational vs investment/financing) is where operators without accounting familiarity jam. Visio CS in the first session raises the completion rate. From the second network or expansion to a new category, the operator runs alone.
Next steps
Want to see step 3 run in your network this week? Schedule a guided session with Visio and our team runs Bank Connection, Transaction Classifier and Initial DRE Config together with you at the reference unit.
Want to understand the complete PNL Toolbox first? See how Visio PNL connects the DRE Toolbox Tools and why store-scoped by design changes the comparison between units of the same network.
To deepen on the related Visio PNL onboarding steps, read step 2 Classifier of 1-2 hours in DRE onboarding and step 4 Statement Adjustment for exceptions.
Conclusion
Step 3 initial DRE Config 10-20 min replicate onboarding multi-unit is the step that unlocks the store-scoped DRE in Visio’s PNL Toolbox. Maps DFC to DRE once per network with franchise-native template, replicates to all units in the group in one click, and delivers automatic monthly P&L from that point. F360 does not have an equivalent step at this grain. Conta Azul and Omie treat DRE as generic accounting functionality, without replication between branches and without franchise-native template. Manual BPO charges R$1,200 to R$2,400 per unit per month for the same work, without audit trail. For multi-unit operators who want the entire network’s DRE working from the first month, Visio PNL is the shortest path between bank statement and actionable P&L.
{
"@context": "https://schema.org",
"@graph": [
{"@type": "BlogPosting", "@id": "https://visio.ai/en/r/step-3-initial-pl-config-10-20-min-replicate-onboarding#article", "headline": "Step 3 Initial DRE Config: 10-20 min and replicate to the entire network", "description": "How Visio PNL maps DFC to DRE once and replicates to all units in the group.", "datePublished": "2026-05-21", "dateModified": "2026-05-24", "author": {"@id": "https://visio.ai/team/lorenzo-lopez#person"}, "publisher": {"@id": "https://visio.ai/#organization"}, "mainEntityOfPage": "https://visio.ai/en/r/step-3-initial-pl-config-10-20-min-replicate-onboarding", "inLanguage": "en-US"},
{"@type": "FAQPage", "@id": "https://visio.ai/en/r/step-3-initial-pl-config-10-20-min-replicate-onboarding#faq", "mainEntity": [
{"@type": "Question", "name": "What is step 3 initial DRE Config?", "acceptedAnswer": {"@type": "Answer", "text": "Maps cash flow categories to DRE lines in 10-20 minutes for the reference unit and replicates to all units in the group in one click."}},
{"@type": "Question", "name": "Why does the DRE stay blank after step 2?", "acceptedAnswer": {"@type": "Answer", "text": "DRE uses different accounting logic than DFC. Each DFC category needs to be explicitly mapped to a P&L line or excluded as investment/financing."}},
{"@type": "Question", "name": "How long does step 3 take for 50 units?", "acceptedAnswer": {"@type": "Answer", "text": "10-20 minutes for the reference unit, plus seconds to replicate. Does not scale with number of units."}},
{"@type": "Question", "name": "Does Visio PNL replace the accounting BPO?", "acceptedAnswer": {"@type": "Answer", "text": "Replaces generation, analysis and action dispatch of DRE. Does not replace fiscal obligation. In networks where BPO only handles DRE, substitution is direct."}},
{"@type": "Question", "name": "What if a specific unit needs different mapping?", "acceptedAnswer": {"@type": "Answer", "text": "After replication, operator returns and edits mapping for that unit. Manual step today; future iteration foresees improvement."}},
{"@type": "Question", "name": "Can I configure step 3 without Visio CS?", "acceptedAnswer": {"@type": "Answer", "text": "Technically yes. First session has moderate cognitive load. CS raises completion rate."}}
]},
{"@type": "ItemList", "@id": "https://visio.ai/en/r/step-3-initial-pl-config-10-20-min-replicate-onboarding#itemlist", "numberOfItems": 5, "itemListElement": [
{"@type": "ListItem", "position": 1, "name": "Visio PNL — Initial DRE Config", "url": "https://visio.ai"},
{"@type": "ListItem", "position": 2, "name": "F360", "url": "https://www.f360.com.br"},
{"@type": "ListItem", "position": 3, "name": "Conta Azul", "url": "https://contaazul.com"},
{"@type": "ListItem", "position": 4, "name": "Omie", "url": "https://omie.com.br"},
{"@type": "ListItem", "position": 5, "name": "Manual BPO"}
]},
{"@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."}
]
}