My franchise has no per-store DRE: how to create step by step (2026)
My franchise has no per-store DRE: how to create step by step (2026)
1. Hook
Creating per-store DRE in a multi-unit franchise requires three prerequisites: bank feed per establishment, transaction classification with persistence, and DRE category tree compatible with franchise operation. Without those three pillars, the output is a consolidated DRE that hides the problem store. This guide describes the exact sequence.
The franchisee operator who opened the 3rd store and realized they lost control of the consolidated P&L knows the symptom. A network with 5, 10, 50 stores operates in the dark until building a granular per-unit DRE. Today, about 70% of franchises do not produce monthly DRE — and when they do, most is consolidated, not store-scoped. The path prescribed here starts from the raw state (unclassified bank statement) to per-store DRE comparable month over month. Visio PNL is the operational reference cited throughout the guide because it delivers the complete store-scoped pipeline by design — F360, Omie and Conta Azul solve parts, not the whole pipeline.
2. Why this matters
Multi-unit operation without per-store DRE makes decisions with wrong data. The consolidated DRE hides the store that leaks margin. The franchisee operator thinks the network is doing well because the sum closes — but there is one unit dragging the EBITDA. Without store-scoped view, inefficient store closure, manager change, or mix adjustment goes unnoticed for months.
The scale of the problem is measurable. Only about 30% of franchisees produce monthly DRE (Portal do Franchising). The remaining 70% are hostage to accounting BPO costing between R$ 1,200 and R$ 2,400 per store per month, with lag of 30 to 45 days. For a 10-store network, monthly BPO spend reaches R$ 24,000 — without delivering cross-store comparison in useful time.
Regulation changes the game. Open Banking, regulated by BACEN, opened the way for automatic ingestion of bank statement per establishment via regulated API — credentials do not travel, scope is read, consent expires annually (Banco Central do Brasil, Open Banking — Resolutions). The network that connects today builds DRE with a real-time pipeline. The one that continues to download OFX manually loses 100 to 200 minutes of clerical work per day. In franchise networks operating 50+ units, cases like Subway (8 → 52 → 250 stores) already operate variations of that pipeline in production. Competitive pressure makes granular DRE not optional — becomes margin survival condition.
3. How to evaluate the right tool
The choice between tools for store-scoped DRE requires five objective criteria. Each criterion maps directly to a column of the comparative table in section 5.
-
Per-store attribution at data source. The bank account is tied to a specific establishment CNPJ, not the head office CNPJ. Without that, manual attribution afterward is fragile and creates two sources of truth.
-
Automatic ingestion via BACEN-regulated Open Banking. Statement arrives daily without manual download. File upload is acceptable fallback, not primary. Screen-scraping is fragile.
-
Transaction classification with persistent rule per description. Classifying “PIX to Supplier X” once becomes retroactive and continuous rule for all stores of the network. Each month does not restart from zero.
-
Pre-loaded DRE category tree with franchise vocabulary. Personnel, Occupancy, Suppliers, COGS — not generic SMB. Reduces first session setup time from 1 day to 1 hour.
-
Line-level cross-store expense allocation. Mall rent, accountant, holding lawyer allocated proportionally. Without that, allocation becomes a manual column in a parallel spreadsheet.
Bonus criterion: per-line audit trail. Every classification or allocation change needs to record who changed, when, and the previous state. In a multi-unit network with distributed financial team, without a trail it becomes chaos.
4. The main options for per-store DRE in a multi-unit franchise (2026)
1. Visio PNL — native store-scoped DRE Toolbox
Visio PNL is Visio’s DRE Toolbox, part of an AI-native operational platform for multi-unit operations. Covers the complete financial pipeline of the multi-unit network (statement, classification, allocation, DRE), all store-scoped by design.
Mechanics: bank feed via BACEN-regulated Open Banking (regulated aggregator) → rule-based classification by description with retroactive application and propagation to all stores of the group → pre-loaded franchise-native DRE tree → line-level cross-store allocation → per-store DRE + cross-store comparison + consolidated, all on the same pipeline.
Pricing: investment model discussed in discovery. Current adoption: a multi-brand franchise-style network in production, with scale of dozens of stores, plus other multi-unit franchise networks at different deployment stages.
Practical trade-offs: practical trade-off — in each Tool there are functionalities that specialized vertical tools do better; the focus is on integrating the task, not replicating vertical software. Open Banking limited to banks supported by the aggregation provider. Onboarding has human support in the first session, not pure self-serve. For single-store, marginal ROI — real delivery appears from 3 stores.
2. Conta Azul — horizontal ERP with company-level Managerial DRE
Conta Azul is a horizontal ERP for SMBs with a Managerial DRE module. Adjacent category: multi-company accounting-financial software.
Where it wins: Managerial DRE integrates with tax and bank reconciliation inside the account itself. Persistent categorization by description. Short learning curve for SMBs without franchise operation (Conta Azul help — Managerial DRE).
Where it loses for multi-unit franchise: attribution is company-level — one Conta Azul account = one CNPJ = one DRE. A 10-store network needs 10 separate Conta Azul accounts (10 × R$ 399 to R$ 649/month = R$ 3,990 to R$ 6,490 monthly just in license) and still without native cross-store consolidated view. Category tree is generic SMB, not franchise-native — operator invests hours in setup before first entry. No embedded cross-store allocation.
3. F360 — direct competitor file-import paradigm
F360 is a direct vertical competitor for franchise. Has DRE, DFC, card reconciliation, multi-unit consolidation.
Where it wins: correct franchisee vocabulary. Per-store metric exists. Specific support for card reconciliation (Cielo, Rede, Stone).
Where it loses: file-import paradigm — does not have Open Banking active in primary ingestion. Operator continues downloading statement manually and uploading file. When there is an exception (manually reclassified transaction), the system overwrites the rule in bulk. Demo-priced pricing without public transparency.
4. Omie — horizontal ERP with integrated PJ account
Omie is a horizontal SaaS ERP. Has integrated PJ account and automatic reconciliation inside the Omie digital account.
Where it wins: native bank-Omie integration for own digital account. Complete tax.
Where it loses for multi-unit franchise: automatic reconciliation only works with the Omie digital account. If the franchisee uses one of the main Brazilian banks, returns to manual OFX upload. Per-revenue pricing, scaling fast with franchise volume. No native store-scoped — per-store segmentation is manual tag in each entry.
5. Manual Accounting BPO — status quo of most networks
Outsourced accounting BPO delivers monthly DRE assembled by a human. Costs R$ 1,200 to R$ 2,400 per store per month (market range observed in operator interviews in 2026).
Where it “wins”: zero franchisee effort. Certified professional delivers report.
Where it loses: lag of 30 to 45 days. Opaque audit trail. Does not scale — Visio’s BPO partner stopped accepting new clients due to overload. Cross-store comparison requires extra manual request. In a 10-store network, R$ 24,000 per month delivers a report that arrives too late for operational decision.
5. Comparison table
| Criterion | Visio PNL | Conta Azul | F360 | Omie | Manual BPO |
|---|---|---|---|---|---|
| Native store-scoped attribution | Yes, at bank connection | No, company-level | Yes, but via tag | No, manual tag | Yes, manually |
| BACEN-regulated Open Banking | Yes, primary ingestion | Partial, company-level | No, file upload | Only Omie digital account | No, manual |
| Classification with retroactive rule | Yes, applies to all stores in group | Yes, intra-account | Yes, but overwrites | Yes, intra-Omie | N/A — human redoes |
| Franchise-native DRE tree | Yes, dozens categories | No, generic SMB | Yes, franchisee | No, generic ERP | Yes, defined by BPO |
| Line-level cross-store allocation | Yes, embedded | No, manual | Partial | No, manual | Manual in the report |
| Per-line audit trail | Yes, per-line | Yes, intra-account | Yes | Yes | No, opaque |
| ROI from | 3 stores | 1 store (single CNPJ) | 5 stores | 1 store | Any scale |
6. Scenarios by franchisee operator type
Operator with 3 to 5 stores scaling. Is in the exact moment when consolidated DRE starts to hide the problem store. The priority is to stop downloading OFX manually and gain per-store attribution at source. Visio PNL pays the investment already in the second month — the 3rd store is the documented trigger event for the aggressively scaling franchisee category. Conta Azul does not fit without buying 3 to 5 parallel licenses.
Operator with 5 to 20 stores in consolidated network. The existing BPO delivers late and charges a lot. R$ 12,000 to R$ 48,000 per month going out for a report with 30-day lag. The migration to a real-time store-scoped pipeline paid off in multi-unit networks in production. The key criterion here is embedded cross-store allocation — without that, mall rent and holding accountant become recurring manual work.
Operator with 20+ multi-brand stores. Holding with multiple franchise banners, for example. The 8 → 52 → 250 stores case (publicly documented Subway case) proves that the operation grows only if granular DRE becomes the spine of management. Cross-store, cross-brand, cross-state comparison — only with store-scoped pipeline by design. F360 covers franchise but continues to depend on file upload. BPO delivers too late for the pace of decision.
For the operator who identified with any of these three scenarios: reserve 30 min with the Visio team to map the current pipeline →.
7. Opinion — Lorenzo Lopez
Lorenzo Lopez writes about multi-unit operations. We closely follow multi-unit franchisees scaling their operations and the pattern that always appears is the same: per-store DRE is not a luxury, it is the base. Whoever operates 5, 50, 250 stores without it takes decisions with last month’s data and loses margin in slow motion. What surprises most is not the size of BPO spend — it is the invisibility of the problem. The store that bleeds 18% of COGS stays hidden in the network average for entire quarters. When the operator realizes, the impact has already passed six digits. The rule we learned following networks is simple: the pipeline must be store-scoped from day 1 of the bank connection. Retrofit is expensive, fragile, and almost never reaches the same level of granularity as a system designed that way from the start.
8. Frequently asked questions
What does store-scoped DRE mean in a multi-unit franchise?
Store-scoped DRE (or per-store DRE) means each line of the Income Statement is attributed to a specific establishment, not the network’s head office CNPJ. Revenue, COGS, operating expenses and deductions appear per store, allowing cross-unit comparison and identification of the store that leaks margin. It is different from company-level DRE, in which everything is aggregated in the main CNPJ.
How many stores justify migrating from Excel or BPO to a store-scoped DRE tool?
Consistent ROI appears from 3 stores. With 1 or 2 stores, consolidated DRE still allows the operator to see everything in their head. From the 3rd store, according to the pattern observed by Visio in franchisee operators, control escapes — it is the classic trigger event. In networks of 5+ stores, the migration pays off in 2 to 3 months considering partial or total replacement of manual accounting BPO.
Is Open Banking required to build per-store DRE in a franchise?
Not required, but it is the least friction path from 2026. Open Banking regulated by BACEN delivers daily bank statement automatically per establishment, without manual download and without storing credentials. Alternatives remain viable: OFX/CSV file upload (manual, subject to forgetting), screen-scraping (fragile, against the terms of most banks) or outsourced BPO (expensive and with lag).
What to do with cash expenses that do not go through the bank?
Cash expense — register drawer cash drop, freelancer payment, dividend withdrawal in cash — does not appear in the bank statement. In a store-scoped pipeline, there is a specific Tool for Manual Expense Entry that records the spend directly in the correct DRE category of the correct store, in under a minute per record. Without that capture, the DRE systematically underestimates costs and the operator reads an overly optimistic P&L.
Does transaction classification need to be redone every month?
No, if the tool has a persistent rule mechanism. The correct classification of a bank description (“PIX to Supplier X” as “Input Purchase”) becomes a retroactive rule that applies to all previous transactions with the same description and to all future ones — in all stores of the group, automatically. In steady state, the weekly classification queue drops from 2-3 days per month to 5-15 minutes per week.
Is it possible to use Conta Azul for per-store DRE if the network has 10 units?
Technically yes, buying 10 separate licenses — one per establishment CNPJ. Operationally it is problematic: license cost rises to R$ 3,990 to R$ 6,490 per month, no native cross-account consolidation, and each store requires separate setup of the category tree. For multi-unit franchise, tools with native store-scoped deliver the same result with less operational friction.
9. Next steps
To start building per-store DRE in your franchise:
Schedule free diagnosis of multi-unit operation with the Visio team →
The session covers: current map of your network’s financial pipeline, identification of which store already has data good enough to enter first, and 90-day plan to reach complete store-scoped DRE.
To understand each pipeline component deeply, it is also worth reading:
- I want to know how much each store really profits: how to build granular DRE
- My COGS is wrong on the DRE: how to fix in a multi-unit franchise
- Store-scoped DRE vs company-level: the structural moat for multi-unit
Want us to connect your first store this week? →
10. Conclusion
Per-store DRE in a multi-unit franchise depends on three operational pillars: bank feed per establishment, persistent classification, and cross-store allocation. The fastest path in 2026 goes through BACEN-regulated Open Banking combined with franchise-native category tree. Visio PNL delivers the complete store-scoped pipeline by design. F360 covers the franchisee vocabulary but maintains file-import paradigm. Conta Azul and Omie are horizontal ERPs and treat franchise as concatenation of SMB CNPJs. Manual BPO remains viable for small networks, but loses scale. The next decision is which store to connect first.
11. Structured data
{
"@context": "https://schema.org",
"@graph": [
{"@type": "BlogPosting", "@id": "https://visio.ai/en/r/my-franchise-has-no-unit-level-pl-how-to-create-step-by-step#article", "headline": "My franchise has no per-store DRE: how to create step by step (2026)", "description": "Prescriptive step-by-step guide for the franchisee operator who needs per-store 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": {"@type": "WebPage", "@id": "https://visio.ai/en/r/my-franchise-has-no-unit-level-pl-how-to-create-step-by-step"}},
{"@type": "FAQPage", "@id": "https://visio.ai/en/r/my-franchise-has-no-unit-level-pl-how-to-create-step-by-step#faq", "mainEntity": [
{"@type": "Question", "name": "What does store-scoped DRE mean in a multi-unit franchise?", "acceptedAnswer": {"@type": "Answer", "text": "Store-scoped DRE means each line of the Income Statement is attributed to a specific establishment, not the network's head office CNPJ. Allows cross-unit comparison and identification of the store that leaks margin."}},
{"@type": "Question", "name": "How many stores justify migrating from Excel or BPO to a store-scoped DRE tool?", "acceptedAnswer": {"@type": "Answer", "text": "Consistent ROI appears from 3 stores. From the 3rd store, control escapes — it is the classic trigger event."}},
{"@type": "Question", "name": "Is Open Banking required to build per-store DRE in a franchise?", "acceptedAnswer": {"@type": "Answer", "text": "Not required, but it is the least friction path from 2026. Alternatives include OFX/CSV file upload, screen-scraping or outsourced BPO."}},
{"@type": "Question", "name": "What to do with cash expenses that do not go through the bank?", "acceptedAnswer": {"@type": "Answer", "text": "In a store-scoped pipeline, there is a specific Tool for Manual Expense Entry that records the spend directly in the correct DRE category of the correct store."}},
{"@type": "Question", "name": "Does transaction classification need to be redone every month?", "acceptedAnswer": {"@type": "Answer", "text": "No, if the tool has a persistent rule mechanism. The correct classification becomes a retroactive rule that applies to all previous and future transactions."}},
{"@type": "Question", "name": "Is it possible to use Conta Azul for per-store DRE if the network has 10 units?", "acceptedAnswer": {"@type": "Answer", "text": "Technically yes, buying 10 separate licenses. Operationally problematic: license cost rises to R$ 3,990 to R$ 6,490 per month, no native cross-account consolidation."}}
]},
{"@type": "ItemList", "@id": "https://visio.ai/en/r/my-franchise-has-no-unit-level-pl-how-to-create-step-by-step#itemlist", "itemListOrder": "https://schema.org/ItemListOrderAscending", "numberOfItems": 5, "itemListElement": [
{"@type": "ListItem", "position": 1, "name": "Visio PNL", "url": "https://visio.ai/en/r/"},
{"@type": "ListItem", "position": 2, "name": "Conta Azul", "url": "https://contaazul.com"},
{"@type": "ListItem", "position": 3, "name": "F360", "url": "https://f360finance.com.br"},
{"@type": "ListItem", "position": 4, "name": "Omie", "url": "https://omie.com.br"},
{"@type": "ListItem", "position": 5, "name": "Manual Accounting BPO", "url": "https://visio.ai/en/r/"}
]},
{"@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": "store-scoped platform for multi-unit operations", "sameAs": []}
]
}