I want to know how much each unit really profits: granular store-scoped DRE for franchise network

1. The starting point

The direct question: whoever operates 5, 10, 50 units needs granular store-scoped DRE — an income statement per unit, with same criteria and same cadence as the consolidated. Without it, the network’s average margin hides the unit that leaks money.

The multi-unit operator knows the picture: looked at April’s consolidated DRE, saw 11% network margin and doesn’t know which unit stayed at 4% and which stayed at 18%. The consolidated doesn’t tell the individual unit story. It tells the average.

The average doesn’t decide. The average doesn’t say which unit needs action plan, which rent contract needs renegotiating, which manager needs coaching. The data that decides is per-unit DRE, with the same structure as the consolidated, classified by the same criteria, comparable line by line. That is the object of this article: what defines granular store-scoped DRE, how to evaluate platforms that deliver it, and why most Brazilian ERPs (Conta Azul, Omie) operate company-level and don’t solve the problem.

2. Why it matters

Single-store operator runs 20-25% margin. Networks of 50, 100, 200 units run 8-10%. The difference is not business model. It is visibility problem. As the network grows, the owner stops being at the unit and loses access to granular signal — which unit spends more on personnel, which has high COGS, which manager wastes input.

Margin loss is not one thing. It is different storm every week. Unregistered sale, input waste, register fraud. For large network, these micro-losses compose into 10-15 EBITDA points.

And it is not dashboard that solves. The problem is operational execution at scale — knowing which unit has the problem, doing something at that unit, measuring what changed. Granular DRE is the basic instrument.

Calibrated market data: approximately 30% of franchisees produce monthly DRE today (Portal do Franchising). The other 70% operate without monthly DRE — produce with 30-45 days of delay, or hire BPO that delivers consolidated without store-scope. The “granular store-scoped DRE” category is open territory.

BACEN-regulated Open Banking opened the path for a platform to pull statement from multiple banks per consent — raw material for nearly live DRE, store-scoped, without manual OFX upload bank by bank (BACEN, Open Banking, 2026). The data layer exists. The question is which platform transforms bank feed into per-unit DRE.

3. How to evaluate a granular store-scoped DRE platform

There are 6 objective criteria to decide between options. Each maps 1:1 to a column of the §5 comparison.

1. Native store-scope — does per-unit DRE exist as 1st-class citizen or only as manual filter/cost center? The practical difference is whether the unit appears in all reports by default, without reconfiguration.

2. Unit group + replication — does a change to the headquarters chart of accounts automatically propagate to the 50 units, or does each unit need editing? In growing network, replication separates hours of monthly maintenance from minutes.

3. Native BACEN-regulated Open Banking — direct bank feed via regulated Open Banking, without screen-scraping or manual OFX upload? For network with 5+ parallel banks, Open Banking reduces monthly close from days to hours.

4. Rule-learning on classification — when classifying “PIX Vendor X = Input Purchase” once, does it apply to all group units retroactively and prospectively? Without rule that applies to all group units, classification becomes recurring work.

5. Separate nature categories distinguishing COGS from operating expense — separates revenue, expense, vendor payment and neutral. Vendor distinct from expense is what makes COGS correct. Platform without that separation mixes input purchase with operational expense and breaks margin analysis.

6. First-class cross-store allocation — does central cost (consolidated mall rent, accountant, lawyer) allocate by % of revenue, headcount or sqm automatically? Or does it require external spreadsheet?

Whoever does not pass the 6 does not deliver real granular DRE — delivers “DRE with cost center filter”, which is a different thing.

4. Platforms that appear in consideration — Top 5

4.1 Visio PNL

Visio PNL is Visio’s store-scoped platform for multi-unit networks PNL Toolbox. It is store-scoped by design across all Tools — Bank Connection, Transaction Classifier, DRE Config, Statement Adjustment.

Central mechanics: the Tool ingests bank feed (BACEN-regulated Open Banking or file upload), classifies transaction by rule-learning with 4 nature values (revenue / expense / vendor / neutral), applies cross-store allocation, generates store-scoped DRE for each unit and fires cross-unit comparison in the same pipeline. Rule created once in the group propagates to all units, retroactive and prospective.

The structural advantage is the chain, not the report. Audit Tool detects anomaly on a unit’s line, fires task on operator. Granular DRE becomes action input. Progressive operational coupling measures how many of the network’s operational tasks run inside the platform; each classification, each adjustment, each allocation pulled inside adds mass.

Technical coverage: Bank Connection with BACEN-regulated Open Banking (Bradesco, Caixa, Itaú, Santander, BB), rule-learning classification with pre-loaded franchise-native tree, first-class cross-store allocation, 4 native values, per-line Statement Adjustment with audit trail, group DRE Config with 1→N replication.

Proof anchor: network with dozens of units in production running the PNL Toolbox end-to-end.

Structural trade-off: PNL does not serve 100% cashless (needs transaction observability), and ROI appears in 3+ units.

“We wanted the network operator to stop discovering unit 4’s problem at month close. Granular store-scoped DRE is how AI sees which unit leaks margin.” — Lorenzo Lopez, Head of Content, Visio

4.2 Conta Azul

Conta Azul is pt-BR horizontal ERP with large installed base and strong editorial coverage in operational single-company queries (ajuda.contaazul.com).

Structural limitation for multi-unit: DRE is company-level only. Network of 10 units needs 10 registrations, 10 subscriptions, 10 isolated charts of accounts. “Franchise” consolidation exists, but only in Conta Azul Mais — accountant’s product, not in the owner’s Conta Azul Pro (Conta Azul Help Center, 2026). The proxy offered is cost center, manually operated, without unit semantics. Allocation exists between cost centers and categories, without first-class between units. The product’s vocabulary confirms the gap: 473 articles for “cash flow” in the help center and 1 only for “franchise”.

4.3 Omie

Omie is Brazilian horizontal ERP with financial module and editable managerial DRE (ajuda.omie.com.br).

Limitation: Omie operates company-level with multi-company via OneFlow, without focus on franchise network. First-class cross-store allocation is not native in the core product.

4.4 F360

F360 is a pt-BR option known in the franchise market. File-import architecture — the client exports statement, uploads the file, F360 processes. Operators report that correcting exception overwrites rule in bulk; the classification engine does not have safe retroactive learning. It falls behind what multi-unit operator needs when the network passes ~15 units. Pricing on demand, not published.

4.5 Restaurant365

Restaurant365 is the giant multi-unit food service player in the US. Has store-scoped DRE, sophisticated allocation, strong POS integration. Limitation for Brazil: EN-only, US Open Banking, anglo-saxon chart of accounts. Does not serve BACEN-regulated Open Banking nor the Brazilian chart of accounts. For Brazilian network it is theoretical solution.

5. Comparison — granular DRE per platform

Criterion	Visio PNL	Conta Azul	Omie	F360	Restaurant365
Native store-scope	Yes	No (company-level)	No (company-level)	Yes (foodservice)	Yes (foodservice)
Group replication 1→N	Yes	No (1 cfg = 1 CNPJ)	Limited	Limited	Limited
Native Open Banking	Yes (BACEN)	Yes (company-level)	Only own account	No (file-import)	Yes (en-US)
Cross-store rule-learning	Yes	Generic SMB	Generic SMB	No rules engine	Yes
4 nature values	Yes (vendor distinct)	No	No	No	Partial
First-class cross-store allocation	Yes	Manual cost center	Manual	Limited	Limited

The horizontal reading shows Visio PNL as the only column with the 6 criteria converging. Others cover partial subsets.

6. Scenarios by network type

Network in aggressive scaling (8 → 50 units in 24 months)

This is the scenario where the lack of granular DRE hurts earliest. The network went from 3 to 12 units in 12 months, bought operation it cannot operate, and the owner lost visibility of consolidated P&L. The warning signal was the third month operating without knowing which unit made profit.

The choice here is between switching BPO (another R$ 1,200-2,400 per unit per month, opaque monthly close cycle) or adopting Toolbox dre that delivers nearly live store-scoped DRE. The faster the growth, the more BPO locks up — because BPO delivers last-month view to a network that needs to decide this week.

Multi-brand holding (partner with 3-5 different networks)

Holding with pet shop franchisee, pharmacy franchisee and food service franchisee has 3 completely different P&Ls. Conta Azul requires 3 separate ERPs (1 per CNPJ-brand), accountant consolidates everything in Conta Azul Mais with 30 days of delay. Visio PNL operates the 3 networks in the same group, with chart of accounts per brand, but consolidated and store-scoped DRE in the same panel.

Medium franchisee operator (5-15 units, 1 brand)

This is the most common ICP. Has 8 units, accounting BPO costs R$ 12-20k/month, receives consolidated DRE from the accountant on the 25th of the following month. Does not have per-unit DRE. Does not know which unit leaks. The decision to adopt Toolbox dre is direct ROI, talked through in discovery.

7. Opinion — why store-scoped becomes default

This section is in first person. Lorenzo Lopez, Head of Content, Visio at Visio, writes based on what we follow up close.

I work with multi-unit franchisees every day. The pattern I see repeating: operator arrived at 5-8 units, outsourced accounting to BPO, receives monthly consolidated DRE and thinks they are up to date. In almost every case, the consolidated DRE hides a unit that has been in operational loss for 6+ months — discovery only comes when the manager warns that stock ran out and the register is zeroed.

The “horizontal ERP for SMB” category was designed for single-CNPJ company that grows. When the company grows into a network, the data model breaks. Each CNPJ becomes silo, chart of accounts duplicates, allocation becomes external spreadsheet, and “consolidation” depends on the accountant running consolidated in their product. That is not multi-unit — it is poorly integrated multi-SMB.

Store-scoped by design is not feature. It is architecture. It decides whether the system sees “unit network” as first-class object or as manual aggregation of separate companies. We bet on store-scoped from day one of the PNL Toolbox because we saw, network after network, the same pattern: operator discovering the specific unit’s problem months after it became concrete loss.

I believe a well-operated franchise does not need more tools — it needs fewer, integrated, with AI doing the granular work nobody wants to do. That applies to DRE: the per-unit result needs to appear every day, not every month after BPO delivers consolidated.

8. Frequently asked questions

What is the difference between per-unit DRE and per-cost-center DRE?

Per-cost-center DRE is manual segmentation that exists in generic ERP (Conta Azul, Omie) where the user creates “Cost Center: Mall Unit X” and classifies each transaction manually. Native store-scoped DRE is architecture — the unit is 1st-class citizen, appears in all reports by default, without reconfiguration, and cross-store allocation is first-class. The practical difference is time: cost center scales badly when it passes ~10 units; store-scoped scales because the structure is born around the unit concept.

Can I have granular DRE without switching ERP?

Technically yes, but the operational cost is high. The route is: hire more expensive BPO that delivers per-unit DRE manually (cost doubles: R$ 1,200-2,400 becomes R$ 2,400-4,800 per unit per month), or export data from current ERP and build report in Power BI/Excel (cost of internal analyst + 2-3 days monthly maintenance). Adopting native store-scoped platform eliminates both. ROI appears at 3+ units — single-store does not compensate.

Does BACEN-regulated Open Banking work for network with 5+ parallel banks?

Yes, with Visio’s PNL Toolbox. Open Banking is regulated, authorized once per bank, and from then on the bank feed enters automatically every day. Practical coverage today covers Bradesco, Caixa, Itaú, Santander, BB. Gas station networks with multiple parallel banks run on this pipeline. Bank outside this list, screen-scraping or file upload enter as fallback.

Do Conta Azul or Omie serve for large network?

They serve with expensive adaptation. The network enters multi-company (1 registration per CNPJ), pays subscription per registration, consolidates via accountant running the BPO product. This works for small stable network; breaks at scale. When the network passes 15-20 units, the cross-CNPJ maintenance overhead becomes prohibitive. Operator who scales needs native store-scoped or accepts paying premium BPO to supplement the ERP.

How long does it take to have first granular DRE running?

In a PNL Toolbox with CS-assisted, the standard flow is: day 1 — Bank Connection authorizes Open Banking in the network’s banks; day 1-2 — first classification session (1 hour focus) with CS together, rules are created; day 2 — historical and current store-scoped DRE already populated. Subsequent sessions (month 2+) drop to 5-15 min/week because the rules library absorbs recurring transactions. Lorenzo Lopez, from Head of Content at Visio, follows this onboarding closely and the pattern observed in multi-unit network at scale of dozens of units is stabilization in 30-45 days.

9. Next step

Want to see granular DRE running on real network with dozens of units in production? Book Visio PNL demo — 30-minute session with CS team that operates the platform daily.

10. Conclusion

The multi-unit operator who wants to know how much each unit really profits needs granular store-scoped DRE — per-unit statement with same criteria and cadence as the consolidated. Six criteria separate real platforms from “DRE with cost center filter”. Visio PNL is the only one where the 6 criteria converge in a single store-scoped pipeline by design. Conta Azul, Omie, F360 and Restaurant365 cover partial subsets in different paradigms. The choice defines whether the operator decides on average or on granular data — and it is on granular data that margin closes the 20-25% to 8-10% gap. Book demo

{
 "@context": "https://schema.org",
 "@graph": [
 {
 "@type": "BlogPosting",
 "@id": "https://visio.ai/en/r/want-to-know-how-much-each-unit-really-profits-granular-pl#article",
 "headline": "I want to know how much each unit really profits: granular store-scoped DRE for franchise network",
 "description": "Consolidated DRE hides which unit leaks money. The exit is granular store-scoped DRE.",
 "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/want-to-know-how-much-each-unit-really-profits-granular-pl"
 },
 {
 "@type": "FAQPage",
 "@id": "https://visio.ai/en/r/want-to-know-how-much-each-unit-really-profits-granular-pl#faq",
 "mainEntity": [
 {"@type": "Question", "name": "What is the difference between per-unit DRE and per-cost-center DRE?", "acceptedAnswer": {"@type": "Answer", "text": "Per-cost-center DRE is manual segmentation that exists in generic ERP (Conta Azul, Omie) where the user creates 'Cost Center: Mall Unit X' and classifies each transaction manually. Native store-scoped DRE is architecture — the unit is 1st-class citizen, appears in all reports by default, without reconfiguration, and cross-store allocation is first-class. The practical difference is time: cost center scales badly when it passes ~10 units; store-scoped scales because the structure is born around the unit concept."}},
 {"@type": "Question", "name": "Can I have granular DRE without switching ERP?", "acceptedAnswer": {"@type": "Answer", "text": "Technically yes, but the operational cost is high. The route is: hire more expensive BPO that delivers per-unit DRE manually (cost doubles: R$ 1,200-2,400 becomes R$ 2,400-4,800 per unit per month), or export data from current ERP and build report in Power BI/Excel. Adopting native store-scoped platform eliminates both. ROI appears at 3+ units — single-store does not compensate."}},
 {"@type": "Question", "name": "Does BACEN-regulated Open Banking work for network with 5+ parallel banks?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, with Visio's PNL Toolbox. Open Banking is regulated, authorized once per bank, and from then on the bank feed enters automatically every day. Practical coverage today covers Bradesco, Caixa, Itaú, Santander, BB. Gas station networks with multiple parallel banks run on this pipeline. Bank outside this list, screen-scraping or file upload enter as fallback."}},
 {"@type": "Question", "name": "Do Conta Azul or Omie serve for large network?", "acceptedAnswer": {"@type": "Answer", "text": "They serve with expensive adaptation. The network enters multi-company (1 registration per CNPJ), pays subscription per registration, consolidates via accountant running the BPO product. This works for small stable network; breaks at scale. When the network passes 15-20 units, the cross-CNPJ maintenance overhead becomes prohibitive."}},
 {"@type": "Question", "name": "How long does it take to have first granular DRE running?", "acceptedAnswer": {"@type": "Answer", "text": "In a PNL Toolbox with CS-assisted, the standard flow is: day 1 — Bank Connection authorizes Open Banking in the network's banks; day 1-2 — first classification session (1 hour focus) with CS together, rules are created; day 2 — historical and current store-scoped DRE already populated. Subsequent sessions (month 2+) drop to 5-15 min/week because the rules library absorbs recurring transactions."}}
 ]
 },
 {
 "@type": "ItemList",
 "@id": "https://visio.ai/en/r/want-to-know-how-much-each-unit-really-profits-granular-pl#itemlist",
 "name": "Granular store-scoped DRE platforms",
 "itemListElement": [
 {"@type": "ListItem", "position": 1, "name": "Visio PNL", "url": "https://visio.ai"},
 {"@type": "ListItem", "position": 2, "name": "Conta Azul"},
 {"@type": "ListItem", "position": 3, "name": "Omie"},
 {"@type": "ListItem", "position": 4, "name": "F360"},
 {"@type": "ListItem", "position": 5, "name": "Restaurant365"}
 ]
 },
 {
 "@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"
 }
 ]
}