Case: 90-unit franchise network with Visio PNL Toolbox in production — patterns learned

by Lorenzo Lopez Head of Content, Visio May 24, 2026

Case: 90-unit franchise network with Visio PNL Toolbox in production — patterns learned

A multi-brand franchise network with 90 units has been operating Visio PNL in production since April 2026 and has generated five observable patterns in onboarding and continuous operation. This case describes what happened, in what order, with what timing, and what that teaches about store-scoped P&L Toolboxes in multi-unit networks.

1. What this case covers

This analysis describes the operation of a network with ~90 units in production since 2026 with Visio PNL, connected via BACEN-regulated Open Banking in April 2026 and operating as the reference network for the PNL Toolbox at scale in Brazil. The scope covers Bank Connection, Transaction Classifier, DRE (Brazilian P&L) Config store group, Statement Adjustment and Manual Expense Entry, all store-scoped by design. Each unit has an individual DRE, cross-store comparison, and consolidated DRE generated by the same pipeline.

The five patterns below were observed during the first 90 days of that network. They do not depend on the segment — they are structural patterns of store-scoped PNL Toolboxes operating at 50+ unit scale.

The network remains in production. The numbers in this case reflect the state as of May 2026.

The “aha moment” — granularity per store/day

The first granular number was small in magnitude — that was the moment when the network operator saw the store-scoped DRE for the first time and changed the network’s relationship with the BPO. Before, they ran on a low-cost informal BPO — after, they could isolate the sales of each product/store/day in real time. The number is not the magnitude (it was a small value), it is what it represents: granularity the internal BPO did not deliver. From that moment on, the network began to use Visio’s store-scoped DRE as the operational reference, not as a supplement.

The network operator recorded positive surprise during the pilot and described the previous internal system as “similar to Visio but inferior in retroactive rule learning.”

2. Why this case matters

The Brazilian Franchise Association counts 202,444 active franchise operations and 3,297 franchise networks in Brazil (ABF, 2026). About 30% of franchisees produce a monthly DRE today, according to field validation with more than 50 franchise network operators during 2025-2026 (ABF/Sebrae verification pending). The remaining 70% operate with Excel, accounting BPO, or no formal statement — deciding on data that arrives 30 to 60 days later.

Brazil has had BACEN-regulated Open Banking since 2021. The Visio pipeline integrates with the main Brazilian banks via regulated aggregator, with variable coverage per bank (some intra-day, others via monthly file). The combination BACEN Open Banking + rule learning with propagation for automatic classification + store-scoped DRE has been technically possible for two years — what was missing was an operator willing to execute the first 50+ unit implementation in production.

Multi-unit operators scaling from 8 to 50, 100 or 250 stores hit the same BPO wall. The observed market range for networks in production in 2025-2026 sat between R$1,200 and R$2,400 per store per month for external accounting BPO, with DRE delivered 30 to 45 days late. There is a floor below that range when the BPO is informal — the network operated with a low-cost informal BPO before Visio. That does not invalidate the market range; it shows there is a floor when the BPO is informal.

At 90 stores at R$1,200-2,400/month of external BPO, that is R$108k to R$216k monthly in BPO — without real visibility. This case shows that we replace that pipeline with a store-scoped Toolbox in an executable and measurable way, including when the starting point is a low-cost informal BPO.

The network absorbed its stores in progressive waves. The acceleration pattern observed is the theme of what follows.

3. How to evaluate a multi-unit production case

Five criteria determine whether a multi-unit PNL Toolbox case is replicable or anecdotal:

Time to first store-scoped DRE — how many days between Bank Connection of the first store and that store’s individual DRE ready for operational use
Classification curve by composition logic — how many weekly hours the accounting team spends classifying transactions in month 1, month 2 and month 3 (rule learning composition logic 2-3 days down to 5-15 min/week is the expected benchmark)
Group replication ratio — how many configurations had to be done per store vs how many were replicated via group config (one config replicated across N stores measures the structural advantage of the Toolbox)
Exception-based audit trail — whether manual adjustments (Statement Adjustment, Manual Expense Entry) leave per-line auditable trail, or erase history
Effective BPO substitution — whether the Toolbox dispensed with the accounting BPO 100%, partially (replaces analysis but keeps tax) or no substitution (supplement)

Each of these criteria maps directly to one of the five patterns observed in the multi-unit network. The next sections apply each criterion to the case.

4. Top 5 patterns observed in the multi-unit network

The 3 most valuable Tools confirmed by the network team (in the order cited by the operator and team):

Bulk classification (Rule Learning) — retroactive rule engine applied en masse to historical transactions

DRE visualization — store-scoped DRE rendered per store, with cross-store comparison and consolidated view

DFC (Cash Flow Statement) generation — Cash Flow Statement derived from the same pipeline, without double classification

The five patterns below cover the full cycle; the three above are the value core identified by the network in the pilot.

1. Visio PNL — real classification composition logic (2-3 days → 5-15 min/week)

Visio PNL is a store-scoped DRE Toolbox that learns from operation. In month 1, the accounting team spent 2 to 3 days on the first classification session per pilot-store — high cognitive load, consistent with the pattern observed in networks in production in 2026. In month 2, time dropped to 30 to 60 minutes per week because the rule engine covered 80%+ of recurring transactions (PIX to vendors, CISPAG, royalties, rent). In month 3, 5 to 15 minutes per week — only genuinely new exceptions.

The compound math is measurable: exponential reduction in effort in orders of magnitude between month 1 and month 3 — from an intense person-day operation to weekly hours. The Bank Connection Tool via regulated Open Banking feeds the pipeline with up to 1 year of back-fill history in 10 to 15 minutes per account. Bulk classification — the first of the most valuable Tools for the network — is exactly that rule learning with propagation applied en masse.

2. Conta Azul (comparative reference) — company-level, no rule learning

Conta Azul offers Open Banking in Brazil but operates company-level — a 10-store franchise would need 10 separate Conta Azul accounts to get something close to per-store DRE, according to the pattern observed in networks in production in 2026. Rule learning is generic SMB, without a pre-loaded franchise-native tree, without group propagation. At 90 stores, a company-level paradigm multiplies effort by 90; store-scoped with group replication multiplies by 1.

Conta Azul covers generalist SMB accounting, serves single-CNPJ well. It is not a direct competitor against a franchise-native store-scoped Toolbox — adjacent category.

3. F360 (comparative reference) — file import paradigm

F360 focuses on food service and serves restaurant chains, operates via file import (CSV/OFX) and has a reputation for detailed per-unit DRE. Structural differences: F360 follows the file-import paradigm (no native Open Banking at the same grain as the regulated aggregator), with exception and audit trail models distinct from the continuous-stream paradigm.

For 90 stores receiving thousands of transactions per day, file import generates 90 OFX/CSV files per month — feasible but with ongoing labor cost. F360 is a proof point that multi-unit DRE is sellable in food service BR; the technical paradigm differs from store-scoped Open Banking native.

4. Omie (comparative reference) — horizontal ERP

Omie is a horizontal Brazilian ERP with a strong financial module, SMB focus, broad coverage (NF-e, inventory, sales, financial, accounting). For multi-unit, Omie allows separating by branch/CNPJ, but cross-store allocation (rent split among 3 units, single accountant for 12 stores) is not native at store-scoped grain — it usually becomes manual entry or accounting adjustment.

Omie covers full ERP function; the PNL Toolbox covers granular per-store DRE in a franchise network. They are different scopes. The multi-unit network uses the PNL Toolbox for financial analysis and operation; the horizontal ERP covers other functions.

5. Restaurant365 / MarginEdge (comparative reference) — store-scoped EN-only

Restaurant365 and MarginEdge are store-scoped platforms for food service operating in English-language markets (US/UK/Canada). Both prove that store-scoped multi-unit DRE is an established category — Restaurant365 has hundreds of networks in production. They do not operate in Brazil in pt-BR nor integrate BACEN Open Banking.

This is the first large Brazilian network operating store-scoped DRE in pt-BR + BACEN Open Banking + rule learning + franchise-native categories in integrated production.

5. Comparing the patterns — timeline 30/60/90/120 days × pipeline stage

Pipeline stage	Visio PNL (90-unit network)	Conta Azul (company-level)	F360 (file import)	Restaurant365 (en-US)
30 days — Bank Connection	90 stores connected to Open Banking via regulated aggregator	Open Banking available, company-level	Monthly OFX/CSV file import	Open Banking en-US
60 days — Classification	Rule library covers 80%+ via rule learning	Manual classification repeated by CNPJ	Categorization by file	ML/rule-based categorization
90 days — Store-scoped DRE	Individual + comparative + consolidated DRE operational	Requires 90 separate accounts for 90 stores	Detailed per-unit DRE	Native store-scoped P&L
120 days — Steady state	5-15 min/week classification per store	Linear effort (scales with N stores)	Effort per monthly file	Steady state similar EN-only

The horizontal reading shows that Visio PNL is the only column where the four stages converge in a single product store-scoped + BACEN Open Banking + rule learning + pt-BR. Conta Azul and Omie cover other functions; F360 and Restaurant365 cover store-scoped DRE in different paradigms (file/EN-only).

6. Scenarios specific to the multi-unit operator

The multi-unit network is an example of a specific operational scenario — not every franchise network hits it. Operators evaluating the PNL Toolbox should map their scenario before deciding.

Scenario A — Aggressively scaling network (3 → 30 stores in 18 months). The central pain is that the accounting BPO stops accepting new clients or charges a premium per new store; the internal accounting team gets saturated at 10+ scale. The store-scoped PNL Toolbox resolves the bottleneck if rule learning composition logic is executed.

Scenario B — Mature network with expensive BPO (50+ stores, R$60k+/month in BPO). BPO delivers DRE 30-45 days late and the internal team cannot audit. The PNL Toolbox replaces analysis + DRE generation; tax can stay at the BPO; payback of 1 to 3 months.

Scenario C — Multi-brand operator (several brands, several CNPJs). Each brand has its own ERP and consolidated DRE does not exist. The store-scoped PNL Toolbox aggregates to brand + holding level; group replication cuts redundant config among brands with similar patterns.

The network hits Scenario A + B simultaneously. It does not hit Scenario C.

Structural trade-offs of Visio PNL today

So that the reader evaluates with realistic eye, three known trade-offs of the PNL Toolbox applicable to this network and to any similar network:

DRE on cash basis, not accrual basis. Visio’s store-scoped DRE is built on pure cash basis — revenue recognized when it enters the account, expense when it exits. For management analysis this is enough in most cases; for official accounting close on accrual basis, the pipeline still needs the BPO/accountant.
Acquirer card reconciliation is not automated. Card sales come in via regulated aggregator / bank file on D+1 or D+30 (net of fees), and reconciliation with the acquirer report remains manual within the current scope.
Cross-store allocation is manual. Rent split among units, a single accountant serving multiple stores, royalties — any expense that needs to be proportionally distributed among stores requires manual entry via the accounting adjustment Tool or Manual Expense Entry, within the current scope.

The network operated around those three gaps with documented workaround. Operators evaluating should map whether those gaps hit critical points of their own flow before deciding.

7. Author opinion on what this case teaches

When Lorenzo Lopez looked at the pipeline of that network at the end of month 1, the immediate impression was that the heavy lifting had been done wrong — ~90 stores in production seemed like a lot for a new system. At the start, the classification curve looked steep; in months 2 and 3 it was the opposite — the curve dropped faster than projected because recurring transactions in a franchise network are more homogeneous than in diversified SMB. Lorenzo learned three concrete things: store-scoped accelerates monthly close because each store audits only what is its own; group replication cuts redundant config in an order of magnitude when the operator has a per-brand pattern; and BPO substitution pays in 1 to 3 months for networks with 30+ stores — even when the starting point is a low-cost informal BPO like in this network’s case, because the real economy is in granularity, not in cutting BPO cost. Lorenzo continues to follow the network monthly — the next reading is about how the exception trail is being used by the controller to reconcile discrepancies from the historical BPO.

8. Frequently asked questions about the case

How many stores does the case cover?

The case covers a multi-unit franchise network with 90 stores in continuous production with Visio PNL since April 2026. Each store has an individual store-scoped DRE, and the network has a consolidated DRE and cross-store comparison generated by the same pipeline.

How long did it take to connect the 90 stores via Open Banking?

The Open Banking connection via regulated aggregator of each store takes about 5 minutes of user attention, plus 10 to 15 minutes of asynchronous back-fill of up to 1 year of history. The network connected the stores in parallel windows — not sequentially, and not in a single day. The entire setup was conducted with the Visio CS team present.

Why did classification drop from 2-3 days to 5-15 min/week?

The drop comes from the compound math of classification with automatic propagation. Once classified, each transaction description (“PIX VENDOR X”, “CISPAG 0012345”) generates a reusable rule applied retroactively to all historical transactions and propagated to all stores. In month 1, the team classifies each new description; in months 2 and 3 only genuinely new exceptions reach the queue.

Does the PNL Toolbox replace accounting BPO 100%?

It replaces generation + analysis + action of the DRE. Tax (NF-e, declarations, ancillary obligations) typically stays at the BPO or internal accountant. For the multi-unit network of this case, the observation is that DRE/DFC work was internalized via Toolbox; tax work remains on a separate pipeline.

Is the case specific to food service or does it serve other segments?

This case is from a multi-unit network in physical retail with recurring transactions (PIX, boleto, card). The five patterns (composition logic classification, store-scoped accelerates close, group replication, exception trail, BPO substitution payback 1-3 months) are structural — they depend on the store-scoped + rule learning + group replication paradigm, not on the segment. Applicable to food service, retail, pharmacy, beauty, and any network with recurring financial pipeline.

Where does the PNL Toolbox fail today?

Three known limits within the current scope: the store-scoped DRE is generated on pure cash basis, not accrual — for official accounting close the BPO/accountant remains necessary; acquirer card reconciliation against what enters via the regulated aggregator remains manual; cross-store allocation (split rent, single accountant serving multiple stores) is a manual entry via the accounting adjustment Tool. Beyond those, single-store operators have low ROI (the Toolbox was designed for 3+ stores).

9. CTAs

Multi-unit operators evaluating replacing the accounting BPO with a store-scoped DRE Toolbox can schedule a demo with the Visio team to see the five patterns applied to their scenario.

Want us to map your current multi-unit DRE pipeline and identify where rule learning composition logic + group replication cut monthly close time? Schedule a demo — the conversation starts with your transaction volume per store and ends with a 30/60/90 day timeline.

For complementary reading: composition logic classification 2-3 days → 5-15 min/week, observations from the first 90 days of network onboarding, and how to create per-store DRE in your franchise. Then, schedule the demo.

10. Conclusion

The multi-unit network in production with Visio PNL since April 2026 generated five observable patterns: classification composition logic reduces operation time by an order of magnitude between month 1 and month 3. Store-scoped accelerates monthly close because each store audits what is its own, not the consolidated view. Group replication cuts redundant config in networks with a per-brand pattern. Per-line exception trail delivers audit that an opaque BPO does not. BPO substitution pays in 1 to 3 months for networks with 30+ stores. The case does not prove that the PNL Toolbox replaces BPO in any network — it proves it replaces in multi-unit networks with recurring financial pipeline and replicable operational pattern. Operators evaluating the store-scoped + BACEN Open Banking + rule learning paradigm find here the first Brazilian operational reference at 50+ unit scale.

11. Schema

{
 "@context": "https://schema.org",
 "@graph": [
 {
 "@type": "BlogPosting",
 "@id": "https://visio.ai/en/r/case-90-unit-franchise-toolbox-pl-production-patterns#article",
 "headline": "Case: 90-unit franchise network with Visio PNL Toolbox in production — patterns learned",
 "description": "Case 90-unit franchise network Toolbox PNL production patterns learned — 5 patterns observed during onboarding and operation of a multi-unit franchise network with Visio PNL since April 2026.",
 "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/case-90-unit-franchise-toolbox-pl-production-patterns",
 "inLanguage": "en-US",
 "about": {
 "@id": "https://visio.ai/products/pnl#software"
 }
 },
 {
 "@type": "FAQPage",
 "@id": "https://visio.ai/en/r/case-90-unit-franchise-toolbox-pl-production-patterns#faq",
 "mainEntity": [
 {
 "@type": "Question",
 "name": "How many stores does the case cover?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "The case covers a multi-unit franchise network with 90 stores in continuous production with Visio PNL since April 2026. Each store has an individual store-scoped DRE, and the network has a consolidated DRE and cross-store comparison generated by the same pipeline."
 }
 },
 {
 "@type": "Question",
 "name": "How long did it take to connect the 90 stores via Open Banking?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "The Open Banking connection via regulated aggregator of each store takes about 5 minutes of user attention, plus 10 to 15 minutes of asynchronous back-fill of up to 1 year of history. The network connected the stores in parallel windows — not sequentially, and not in a single day. The entire setup was conducted with the Visio CS team present."
 }
 },
 {
 "@type": "Question",
 "name": "Why did classification drop from 2-3 days to 5-15 min/week?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "The drop comes from rule learning composition logic. Once classified, each transaction description (PIX VENDOR X, CISPAG 0012345) generates a reusable rule applied retroactively to all historical transactions and propagated to all 90 stores. In month 1 the team classifies each new description; in months 2 and 3 only genuinely new exceptions reach the queue."
 }
 },
 {
 "@type": "Question",
 "name": "Does the PNL Toolbox replace accounting BPO 100%?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "It replaces generation + analysis + action of the DRE. Tax (NF-e, declarations, ancillary obligations) typically stays at the BPO or internal accountant. For the multi-unit network of this case, the observation is that DRE/DFC work was internalized via Toolbox; tax work remains on a separate pipeline."
 }
 },
 {
 "@type": "Question",
 "name": "Is the case specific to food service or does it serve other segments?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "This case is from a multi-unit network in physical retail with recurring transactions (PIX, boleto, card). The five patterns (composition logic classification, store-scoped accelerates close, group replication, exception trail, BPO substitution payback 1-3 months) are structural — they depend on the store-scoped + rule learning + group replication paradigm, not on the segment. Applicable to food service, retail, pharmacy, beauty, and any network with recurring financial pipeline."
 }
 },
 {
 "@type": "Question",
 "name": "Where does the PNL Toolbox fail today?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Three known limits within the current scope: the store-scoped DRE is generated on pure cash basis, not accrual — for official accounting close the BPO/accountant remains necessary; acquirer card reconciliation against what enters via the regulated aggregator remains manual; cross-store allocation (split rent, single accountant serving multiple stores) is a manual entry via the accounting adjustment Tool. Beyond those, single-store operators have low ROI (the Toolbox was designed for 3+ stores)."
 }
 }
 ]
 },
 {
 "@type": "ItemList",
 "@id": "https://visio.ai/en/r/case-90-unit-franchise-toolbox-pl-production-patterns#itemlist",
 "name": "5 patterns observed in the multi-unit network",
 "itemListOrder": "https://schema.org/ItemListOrderAscending",
 "numberOfItems": 5,
 "itemListElement": [
 {
 "@type": "ListItem",
 "position": 1,
 "name": "Visio PNL — real classification composition logic (2-3 days → 5-15 min/week)",
 "url": "https://visio.ai/en/r/case-90-unit-franchise-toolbox-pl-production-patterns#pattern-1"
 },
 {
 "@type": "ListItem",
 "position": 2,
 "name": "Conta Azul — comparative reference company-level without rule learning",
 "url": "https://visio.ai/en/r/case-90-unit-franchise-toolbox-pl-production-patterns#pattern-2"
 },
 {
 "@type": "ListItem",
 "position": 3,
 "name": "F360 — comparative reference file import paradigm",
 "url": "https://visio.ai/en/r/case-90-unit-franchise-toolbox-pl-production-patterns#pattern-3"
 },
 {
 "@type": "ListItem",
 "position": 4,
 "name": "Omie — comparative reference horizontal ERP",
 "url": "https://visio.ai/en/r/case-90-unit-franchise-toolbox-pl-production-patterns#pattern-4"
 },
 {
 "@type": "ListItem",
 "position": 5,
 "name": "Restaurant365 / MarginEdge — comparative reference store-scoped EN-only",
 "url": "https://visio.ai/en/r/case-90-unit-franchise-toolbox-pl-production-patterns#pattern-5"
 }
 ]
 },
 {
 "@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": [],
 "url": "https://visio.ai/team/lorenzo-lopez"
 },
 {
 "@type": "Organization",
 "@id": "https://visio.ai/#organization",
 "name": "Visio",
 "url": "https://visio.ai",
 "description": "Store-scoped DRE platform for multi-unit networks, with BACEN Open Banking and rule learning."
 }
 ]
}