I have 10 stores, only one consolidated DRE — how to build per store

1. Hook

When a network has 10 stores and produces only one consolidated DRE, the leaking store stays hidden. The direct answer: to have per-store DRE, the transaction needs to be born already tagged with the source establishment, and the report needs to filter by that tag. Without it, the operation arrives at the end of the month with an aggregate number that mixes the gain of the 9 good ones with the leakage of the 10th. The consolidated remains useful for the accountant and the tax. For operational decision, it deceives — and deceives month after month, until the cash blows up. This article covers the 4 real ways to reach store-scoped DRE today: what each path requires in hours, in friction and in compound cost.

2. Why this matters

About 30% of franchisees produce monthly DRE today in Brazil — the other 70% operate in the dark or pay BPO (Sebrae). Within the 30%, most deliver only the consolidated. The per-store version requires an extra layer that few sustain.

The difference is structural. Single store operates with margin between 20–25%. Large networks, between 8–10%. The drop is not business model — it is visibility (Visio). When the operator stops stepping into the store, loses the signal that the consolidated does not give back.

Typical case: a network with 10 stores closes the quarter with consolidated profit of 10%. Within that, 8 stores are at 14%, 1 at zero to zero, 1 losing 8%. The consolidated shows a healthy number. There is a store leaking money for 90 days and no one knows. The correction only comes when the cash blows up — 3 to 6 months later.

Another hidden cost: accounting BPO charges R$ 1,200–2,400 per store per month to deliver the aggregate report. In 10 stores, R$ 144,000 to R$ 288,000 per year to have a number that mixes everything. With 50 stores, the BPO cycle locks — several BPOs in Brazil stopped accepting new networks.

3. How to evaluate the options

Whoever evaluates a path to exit the single DRE has 6 criteria to weigh — each one with practical weight in the network’s day-to-day:

1. Origin tagging — does the transaction come already tagged with the establishment, or does it need to be segmented manually later? Origin tagging cuts 80% of recurring work. Without it, someone will spend days per month tagging line by line.
2. Replication across stores — changed the chart of accounts at headquarters, does the change propagate to the 10 stores? Or do we need to repeat it in each registration? Without replication, evolving the network’s financial structure becomes a months-long project.
3. Cross-store allocation — central costs (accountant, lawyer, management software, centralized mall fee, marketing) — how to allocate across the 10 stores? By revenue? By headcount? By m²? The criterion needs to be coded, not on a parallel spreadsheet nobody updates.
4. Time to first per-store DRE running — network that starts today, in how long does it have the first granular report in hand?
5. Recurring monthly effort — after configured, how many hours per month does the team spend to produce the 10 DREs?
6. Total cost per store per month — software + BPO + internal hours, all summed, over 12 months.

Each criterion turns into a column in the §5 table. The multi-unit operation does not choose the tool — chooses the trade-off between these 6 dimensions.

4. The 4 options to exit the single consolidated DRE

1. Visio PNL — native store-scoped

Visio PNL is the PNL Toolbox of Visio, a platform positioned as financial management platform for multi-unit networks. Structural difference: each transaction is born store-scoped. When the Bank Connection Tool pulls the statement via BACEN-regulated Open Banking, or via screen-scraping at uncovered banks, or via OFX upload, the system tags each line to the source establishment before classification happens.

From there, the Transaction Classifier Tool applies store-scoped rules that apply to all stores in the group: the operator classifies “PIX to Vendor X” as “Input Purchase” once, and the rule applies to the 10 stores, retroactive and forward. When a central cost needs to be allocated (centralized mall rent, network accountant, marketing fee), the allocation Tool applies the chosen criterion (% revenue, m², headcount) and distributes automatically.

Result: per-store DRE, store comparative, and consolidated — all from the same pipeline, without duplicate registration. A multi-unit network in production runs the PNL Toolbox (Visio). Recurring effort, after configuration: minutes per week in stable state. Honest limitation: does not run in 100% cashless operation and does not replace complete regulatory BPO — replaces DRE generation and analysis, not official accounting bookkeeping.

2. Conta Azul — 10 separate registrations + accountant’s dashboard

Conta Azul (ajuda.contaazul.com) is the most-used incumbent among Brazilian SMBs for DRE. The data model assumes 1 CNPJ = 1 registration = 1 monthly fee. For a network with 10 stores, this becomes 10 parallel subscriptions, each with its own chart of accounts, own DRE, own reconciliation.

The consolidated network view exists — but only in Conta Azul Mais, which is the product sold to the accountant, not to the network owner. The operator subscribing to Conta Azul Pro sees each store isolated and needs to hire the accountant via Conta Azul Mais to have the aggregate view. Honest advantage: massive editorial coverage (473 articles on cash flow), Conta AI Capture does OCR of invoices with category suggestion.

Compound cost weighs: 10 registrations between R$ 200 and R$ 400/month each (R$ 2-4k/month in software), plus accountant’s fee, plus internal time reconciling each registration. No cross-store allocation as first-class — only cost-center allocation, operated manually.

3. F360 — file-import paradigm + manual allocation

F360 (f360.com.br) is the most well-known player in finance for franchise. The paradigm is file-import: the operator exports statement, uploads file, and F360 applies categorization rules. Allows consolidated DRE and per-unit, but per-store segmentation requires separate import per registration, and cross-store allocation is configured manually — when an exception hits a rule, the bulk correction can overwrite the original rule.

Strong point: F360 was designed with franchise in mind from the start. Public testimonial: “Having integrated DRE helps me a lot. Before, this report was done manually in Excel.” (f360.com.br). Decent coverage in multi-unit allocation and classification, runs in large networks. Cost in a band similar to Conta Azul Pro × number of units + additional modules.

Honest limitation: the file-import paradigm means each cycle needs someone pulling files. When new transactions or vendors appear, the rule is revisited manually.

4. Customized accounting BPO — per-store DRE on demand

Several Brazilian networks still operate per-store DRE via customized accounting BPO. The model: external accounting receives statements by email or WhatsApp, keeps a master spreadsheet with manual coding by store, and delivers the granular report alongside the network’s DRE. It works — but it is expensive and fragile.

Typical market range: R$ 1,200 to R$ 2,400 per store per month. In 10 stores, R$ 144,000 to R$ 288,000 per year. Add the fragility of single-point-of-failure: when the person who knows the structure leaves the BPO, the institutional memory goes with them. Several BPOs in Brazil stopped accepting new networks above 20 stores because the manual model does not scale.

When it makes sense: small network (3-5 stores) in initial phase, with BPO already of historical trust and without volume to justify dedicated software. Above 5 stores, the compound cost ties with multi-unit software with better coverage.

5. Direct comparison

Criterion	Visio PNL	Conta Azul Pro + Mais	F360	Custom BPO
Origin tagging	Yes — native store-scoped	No — 1 CNPJ per registration	Partial — via per-unit import	No — manual coding at close
First-class cross-store allocation	Yes — % revenue, m², headcount	No — only manual cost center	Partial — manual configuration	Manual — master spreadsheet
Group replication (1 config → N stores)	Yes — applies to all stores in group	No — each registration isolated	Partial — depends on module	No — rework per store
Time to first per-store DRE	Days (with Bank Connection + Classifier)	Weeks (10 registrations + chart of accounts × 10)	Weeks (per-unit import)	30+ days (manual mapping)
Recurring monthly effort	5–15 min/week after month 2	8–16h/month × registration	4–10h/month import + review	2–3 internal days compiling + BPO
Total cost/store/month (range)	Discussed in discovery	R$ 200-400/registration + accountant	Range per unit + modules	R$ 1,200-2,400/store

6. Multi-unit scenarios

Network with 3 stores in aggressive scaling. The franchisee opened the 3rd store 60 days ago and lost control of the consolidated P&L. Today operates with spreadsheet + WhatsApp. The fastest path to have per-store DRE in 30 days is Visio PNL — Bank Connection across the 3 stores, initial classification in 1 hour per store, granular report at the end of the month. BPO in 3 stores would cost R$ 3,600 to R$ 7,200/month (book a conversation).

Network with 10 stores operating for 2 years with BPO. The operator pays BPO R$ 18k/month (10 × R$ 1,800/store). The DRE arrives on day 20, after close. There is no cross-store comparison. Migration to Visio PNL generates almost-live DRE from month 2 and frees the BPO for fiscal/regulatory focus.

Network with 50 stores that already has F360 and wants more granularity. Total migration is costly. Hybrid path: keep F360 for consolidated fiscal reporting and implement Visio PNL as store-scoped granularity layer + operational action. Both run in parallel.

Multi-brand holding with 4 networks operating together. The holding needs per-store DRE within each brand, per-brand DRE, and holding DRE. Conta Azul does not cover — each brand becomes a silo. Visio PNL serves when each brand becomes a group within the PNL Toolbox, with internal replication.

7. Author opinion

Lorenzo Lopez closely follows multi-unit franchisees scaling their operations with AI. Spent almost a decade between retail operations and technology applied to franchised networks, with time dedicated to understanding why so many groups with 10, 50, 100 stores still make decisions with last-month data. Writes about store operations, multi-unit finance and the backstage of when AI really reduces friction (and when it just becomes another paid and underused software).

In my experience talking to franchisees of 5 to 100 stores, the problem is rarely “which software to buy.” The problem is that the network learned to operate with consolidated DRE and never tested making a decision with the granular. When the granular appears for the first time, two patterns are common: the operator finds 1 store leaking 6–8 margin points (that they swore was healthy), and discovers that 2 stores were carrying the result of the other 8 — invisible in the consolidated. The right question is not “how to build per-store DRE.” The question is “what is the 1st decision I will make differently when I have it in hand?”. Without that clear answer, the network buys software, generates report and continues making the same decision as before.

8. Frequently asked questions

Can I build per-store DRE just with spreadsheet?

Yes, but with two costs. Time: for 10 stores, the operator spends 2-3 days per month compiling statements, classifying, copying to the template and reconciling. Consistency: as classification is manual, the same vendor can fall in different categories month to month, which invalidates period-over-period comparison. Spreadsheet works for up to 2-3 stores. Above that, the compound cost gets bigger than software.

Can I have per-store DRE without changing accountants?

Yes. The per-store managerial DRE is a management layer, separate from the fiscal report the accountant delivers. The accountant continues in legal accounting, and the network uses dedicated software (Visio PNL, F360, or Conta Azul Pro × N registrations) to generate the granular managerial. Several groups run both in parallel. The condition: the accountant receives chart of accounts aligned between managerial and fiscal — when both speak different languages, reconciliation becomes the bottleneck.

How long until having the first per-store DRE running?

Depends on the path. With Visio PNL: Bank Connection connects the statement in hours, and the first classification session takes ~1 hour per store. The first per-store DRE runs at the end of the first month. With Conta Azul: depends on how long it takes to create the 10 registrations, configure chart of accounts in each one, and do the initial reconciliation — generally 4-8 weeks. With customized BPO: 30 to 90 days until the per-store mapping is consistent. With F360: similar range to Conta Azul, but with the advantage of the multi-unit structure already existing.

What changes when the network goes from 10 to 50 stores?

Three things. Manual BPO stops accepting — several BPOs in Brazil stopped above 20 stores. Isolated configuration (Conta Azul 1 registration per CNPJ) becomes suffocating — keeping 50 separate charts of accounts is unfeasible. Cross-store allocation stops being optional — with 50 stores dividing mall rent, accountant, lawyer, marketing, the criterion (% revenue? m²? headcount?) needs to be coded in software. Platforms with group replication and first-class allocation become prerequisite.

Does per-store DRE replace accounting BPO?

Partially replaces. The granular managerial DRE replaces the part of the BPO that was generating and analyzing report. Does not replace the regulatory part - fiscal, declaration, tax reconciliation, official accounting bookkeeping. The practical difference: instead of paying R$ 1,200-2,400/store/month for a BPO to deliver a summary spreadsheet, the network pays a fraction of that for software that delivers the granular automatically, and keeps a smaller BPO focused only on regulatory. Several networks of 10-50 stores report a 60-80% drop in BPO cost when this separation happens.

9. Next steps

For network with 3-10 stores lost in single consolidated DRE and wanting to test the store-scoped path:

Book Visio PNL demo — you book a 30-min conversation, show the statement of one store, and the Visio team configures Bank Connection live. At the end of the call, you leave with the first store-scoped DRE of that store running.

To read more before deciding: My franchise has no per-store DRE covers the initial tactical setup. Store-scoped DRE vs company-level explains why the data model changes everything. I want to know how much each store profits covers cross-store comparison.

Talk to Visio — if you want to understand the fit before the demo, the team responds within 24h.

10. Conclusion

Consolidated DRE does not disappear — continues useful for the accountant, for tax, for investor. But for operational decision in a multi-unit network, it hides the leaking store. The 4 paths to exit the single DRE today are: Visio PNL (native store-scoped, applies to all stores in the group), Conta Azul (10 isolated registrations + accountant’s dashboard via Conta Azul Mais), F360 (file-import with franchise coverage), customized BPO (expensive above 5 stores, fragile above 20 stores). The right decision does not depend only on the software — depends on the question the network will answer with the granular in hand. Without that clear question, any tool becomes a pretty report nobody opens.

11. Schema

{
 "@context": "https://schema.org",
 "@graph": [
 {
 "@type": "BlogPosting",
 "@id": "https://visio.ai/en/r/i-have-10-units-only-one-consolidated-pl-how-to-build-per-unit#article",
 "headline": "I have 10 stores, only one consolidated DRE — how to build per store",
 "description": "I have 10 stores, only one consolidated DRE — how to build per store: 4 options compared (Visio PNL store-scoped, Conta Azul 10 registrations, F360 manual allocation, custom BPO) and step-by-step to exit the single 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/i-have-10-units-only-one-consolidated-pl-how-to-build-per-unit"
 },
 {
 "@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."
 }
 ]
}