Initial PL Config: Cash Flow to PL mapping with multi-unit overview in franchise
1. Bridges between cash flow and PL in a multi-unit network
Initial PL Config is the Cash Flow to PL mapping step in a multi-unit franchise network. After Bank Connection pulls the statement and Transaction Classifier categorizes in Cash Flow, the PL still stays blank — because it operates on a different accrual basis from Cash Flow’s cash basis (Treasy, 2023). Each Cash Flow cost line needs an explicit decision: does it go to operational PL, or stays out (investment, financing) — understanding that frontier is the difference between Cash Flow and PL in franchise.
In multi-unit networks, that mapping multiplies by N — if each establishment requires its own configuration. Visio PNL does the setup once on the reference-unit (10-20 minutes), replicates to all other units in the group in one action (one-click group replication), and releases the store-scoped PL of each establishment. F360 delivers consolidated PL via Excel export but does not document a configuration step of this grade (F360 Help Center). Conta Azul requires building the chart of accounts from scratch per company, without a preloaded franchise template.
The result for a group of 10 units: 10-20 minutes vs hours of store-by-store configuration.
2. Why this matters for a multi-unit group
Cash Flow and PL are not the same report, and that confusion is expensive. Cash Flow shows real money movement — cash basis. PL shows operational result of the period — accrual basis (Treasy, 2023). A franchisee can close the month with positive Cash Flow and negative PL, or vice versa, depending on how salaries, rent and investments fall in each basis.
Practical rule: approximately 30% of Brazilian franchisees produce monthly PL today. The other 70% run only on bank statement and WhatsApp (Sebrae — franchise formatting). The two dominant reasons are manual bank extraction and manual month-by-month classification. The third friction, less discussed, is configuring the structural PL — deciding what goes in and what stays out.
In a franchise network, this effort multiplies. Each unit needs PL with the same structure for cross-unit comparison to work. If unit A classifies “equipment purchase” as Occupancy Cost and unit B classifies as Investment, the consolidation lies. Structural PL configuration is what guarantees consistency across the entire network.
The sectorized PL — indicated for companies with multiple units, with separate results per unit — is the format that franchise needs (Cora, 2024). And it only works if each unit reports against the same structural skeleton.
Network CFO who ignores this step delivers consolidated PL that hides the problem unit. Each R$ 1,200 to R$ 2,400 per unit/month spent with accounting BPO to solve this became fixed, opaque, and non-replicable structure.
3. How to evaluate an Initial PL Config tool
Five criteria separate franchise-native tool from generic adaptation:
- Preloaded franchise template — does the PL tree already come with Personnel Costs (Salaries, Severance, Charges, Freelancers, Benefits), Occupancy, Suppliers, COGS, or does it require building from scratch.
- Cash Flow to PL line-by-line mapping — explicit UI to decide which Cash Flow categories enter each PL line, with visual confirmation of which are still pending.
- Group replication — one action replicates the configuration of a reference-unit to the other N units in the group, maintaining the same structure.
- Explicit treatment of non-operational — investment, equipment acquisition, financing payment stay outside operational PL, without leaks into costs.
- Optional deferral — deferred accrual (April-paid salary attributed to March PL) available per line for groups operating on accrual basis.
Each criterion maps directly to the corresponding column of §5 table.
4. Top 4 options for Cash Flow to PL mapping in a multi-unit franchise network
1. Visio PNL — store-scoped, native group replication
Visio PNL is Visio.ai’s PL Toolbox, part of the store-scoped platform for multi-unit networks for multi-unit operators. Covers the complete setup: Cash Flow ingest via Open Banking (regulated aggregator, BACEN-regulated) → Transaction Classifier with rule learning → Initial PL Config with Cash Flow to PL mapping and group-scoped replication.
Initial configuration takes 10-20 minutes on the reference-unit. The franchisee opens the PL view, sees every Cash Flow category without mapping marked in orange, clicks line by line, chooses the destination PL category (Personnel → Salaries, Occupancy → Rent, Suppliers → Inputs), confirms. Each orange becomes green. When the reference-unit is 100% green, one action replicates the entire PL structure to each selected unit in the group.
The PL tree comes preloaded with a preloaded franchise-native tree. No building from scratch. Custom categories can be added inline. Royalties (12.5% on 90% of revenue, for example) and card fees enter as formulas in setup — auto-applied every month, without dependency on a specific bank transaction.
In production: a multi-unit network with dozens of units operates store-scoped PL via Visio PNL. Setup done once at the group level, replicated to the 90 units — not 90 separate configurations.
2. F360 — multi-unit consolidated PL via Franchisor Dashboard
F360 is the historical incumbent of financial management for BR franchises. Delivers multi-unit PL via “Franchisor Dashboard” — flagship feature documented as “allows verifying all information related to franchisees and performing extractions in EXCEL” (F360 Help Center, 2024).
Chart of accounts is registered in “Registration Menu → Chart of Accounts,” with manual link between plans and customer/supplier registry. Sync configuration between franchisee and franchisor allows defining a retroactive editing window.
Competitive honesty: F360 delivers real multi-unit PL — it is not a feature gap, it is a UX gap. Setup fragmented across multiple screens (registries, links, syncs). There is no Cash Flow to PL mapping consolidated into a single view, nor one-click replication across units — each establishment is registered in “Companies and Branches” with its own structure. CNPJ-centric model.
Good fit for: network that already has F360 implemented and accounting team trained on the fragmented interface. Known trade-off: slower initial setup, no preloaded franchise template, no atomic replication.
3. Conta Azul — generic PME PL, no franchise template
Conta Azul is a horizontal PME ERP. Delivers PL, Cash Flow, fiscal and reconciliation (Conta Azul). Price R$ 399-649/month EPP plan.
Chart of accounts: the user builds from scratch. No preloaded franchise template, no predefined lines (Personnel Costs, Occupancy, Suppliers). Each registered company makes its own structure. Replication across companies does not exist — because each company is a separate Conta Azul instance.
Competitive honesty: Conta Azul is genuinely good for single-store PME. Fiscal/accounting integration is strong. The gap is structural — Open Banking operates at the company level (not unit), which means a network of 10 units with 10 separate CNPJs would need 10 independent Conta Azul accounts for store-scoped PL. Each with its own manually built chart of accounts.
Good fit for: single-store franchisee or network with single CNPJ headquarters+branches where consolidated PL per company is sufficient.
4. Manual BPO — outsources setup, maintains opacity
Accounting BPO solves PL configuration by delivering the result ready. Market cost: R$ 1,200 to R$ 2,400 per unit per month. A 10-unit network on BPO spends R$ 12,000 to R$ 24,000/month.
The PL structure stays in the BPO’s spreadsheet — invisible to the franchisee. When a new cost category or new unit appears, the franchisee calls, the BPO updates the spreadsheet, and the cycle continues. No internal audit trail, no self-serve, no atomic replication.
Competitive honesty: BPO is genuinely useful when the franchisee wants to outsource the whole (not just PL, but fiscal, accounting, full regulatory). The gap is dependency — overloaded BPO stops accepting new clients, monthly cycle is slow, and PL logic lives in the BPO’s head, not in a replicable system.
Good fit for: franchisee who needs full fiscal/regulatory coverage and not just PL generation + analysis + action.
5. Comparison: multi-unit PL configuration tools
| Criterion | F360 | Visio PNL | Conta Azul | Manual BPO |
|---|---|---|---|---|
| Preloaded franchise template | No — manual link in chart of accounts | Yes — preloaded franchise-native tree | No — user builds from scratch | Bespoke per BPO |
| Cash Flow to PL line-by-line mapping | Fragmented across screens | Yes — single UI, orange → green | Per-entry categorization, no structural mapping | Manual in BPO spreadsheet |
| Group replication (1 config → N units) | Sync per unit separately | Yes — one action replicates to group | No — each company is a separate instance | No — repeats work per unit |
| Explicit treatment of non-operational | Manual in chart-of-accounts registration | Yes — exclusion per line during setup | Manual in classification per entry | BPO decision, opaque |
| Deferral (deferred accrual) | Not documented in help center | Yes — optional per PL line | Manually configurable | Configurable in BPO Excel |
Visio PNL stays in column 2 because that column is the comparison reference. The 5 criteria map 1:1 from §3 evaluation criteria.
6. Multi-unit scenarios: when each tool serves
3-10 unit network scaling. Trigger: franchisee opened the 3rd or 4th unit, lost visibility of consolidated P&L, today operates with Excel + WhatsApp + light BPO. Initial PL Config via Visio PNL serves because setup is proportional to the group, not to the units — see the complete 10-20 min onboarding sequence. Twenty minutes once, atomic replication.
10-50 unit network with active BPO. Trigger: BPO cost passed R$ 15-30k/month, franchisee wants to bring generation/analysis inside while keeping fiscal outsourced. Initial PL Config replaces the structural part of BPO without replacing the whole service — BPO continues delivering fiscal, regulatory and closing. PL runs native store-scoped.
50+ unit network with F360 implemented. Trigger: team already trained on F360, pain is fragmented UX and slow setup for new unit. Migration is not an easy decision — F360 delivers consolidated PL via Excel, which many networks accept. Initial PL Config competes via UX (orange → green), preloaded template, and atomic replication.
Network with headquarters CNPJ+branches (not formal franchise). Trigger: brand operates 5 units all under the same CNPJ, no PJ fragmentation. Conta Azul may be sufficient because company-level PL covers the case. Visio PNL still adds value with store-scoped (separates P&L per unit-branch even within the same CNPJ), but the structural advantage diminishes.
Single-store franchisee. Trigger: 1 unit only. Initial PL Config is overkill — no replication to be done. Light BPO or Conta Azul usually covers.
7. What we see in practice
Lorenzo Lopez is Head of Content at Visio, where he closely tracks 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 really reduces friction (and when it just becomes another paid and underused piece of software). He believes a well-run franchise does not need more tools — it needs fewer, integrated, with AI doing the work nobody wants to do.
The initial PL configuration is where I most see the franchisee abandon the process. Bank Connection is the hook — connects the bank, the money comes in. Classification is work but the result appears. Then the franchisee opens the PL, sees everything orange, loses confidence. In the networks I track, the 20-minute session with CS alongside unlocks. Not for the click — for the judgment. Deciding operational versus investment requires knowledge of the business, not of the software. AI does not solve that yet, and we prefer to say so than to promise nonexistent automation.
8. Frequently asked questions
How long does it take to configure the initial PL in a network with 10 units?
Approximately 10 to 20 minutes on the reference-unit, depending on the cleanliness of the chart of accounts and the franchisee’s knowledge of operational cost versus investment. After that, replication to the other 9 units is one action. The 10-unit group exits with structural PL ready in the same session, against hours or days if each unit is configured separately.
Why does the PL stay blank even after connecting bank and classifying transactions?
Because Cash Flow and PL operate on different accounting bases — cash versus accrual. Cash Flow is ready automatically after classification. PL needs an explicit per-line decision: which Cash Flow categories enter operational (Personnel Costs, Occupancy, Suppliers) and which stay out (investment, financing). Initial PL Config is the step that makes that decision and releases the PL to generate.
Does Initial PL Config replace the accounting BPO of a franchise network?
Replaces the structural part — generation, classification, mapping and replication. Does not replace the fiscal-regulatory part (delivery of accessory obligations, ECF, ECD, formal accounting close). Networks that want to bring P&L inside while keeping fiscal outsourced use Initial PL Config as a complement to BPO. Networks that want to outsource everything continue with full BPO.
How does PL configuration replication to other group units work?
After the reference-unit is 100% configured (zero orange lines), the user clicks the replication action and selects which group units inherit the structure. Each selected unit receives the same PL skeleton at the same moment — same Cash Flow to PL mappings, same exclusions, same royalty and card fee formulas. Cross-store comparison works because each unit reports against the same template.
Can I have customized PL lines beyond the franchise-native template?
Yes. The template comes with preloaded franchise-native tree preloaded covering the standard franchise lines (Personnel, Occupancy, Suppliers, COGS, etc.), but custom categories can be added inline during setup. Custom lines also replicate to all group units when the replication action runs.
9. Want to see this running on your network?
Want us to connect your first unit and turn on the group’s store-scoped PL this week? Book 20 minutes and exit the call with PL configured and replicated. See the demo.
Want to bring P&L inside while keeping BPO on fiscal? We show the parallel setup. Talk to us.
Want to compare with your current stack (F360, Conta Azul, BPO)? We run the parallel and show the delta. Schedule the comparison.
10. Summary
Initial PL Config is the step that unlocks PL after the bank is connected and transactions classified. In a multi-unit network, without this step, PL stays blank despite all infrastructure ready. Visio PNL does the configuration on the reference-unit in 10 to 20 minutes and replicates to N units in one action. F360 delivers consolidated multi-unit PL via Excel but without atomic Cash Flow to PL mapping or group replication. Conta Azul serves single-store PME without franchise template. Manual BPO covers the full outsourced case at R$ 1,200 to R$ 2,400 per unit/month. Multi-unit network CFO who needs consistent, replicable and auditable store-scoped PL has Initial PL Config as the tool of choice.
11. Schema
{
"@context": "https://schema.org",
"@graph": [
{"@type": "BlogPosting", "@id": "https://visio.ai/en/r/initial-pl-config-cash-flow-to-pl-mapping-overview-multi-unit#article", "headline": "Initial PL Config: Cash Flow to PL mapping with multi-unit overview in franchise", "description": "Initial PL Config is the step that maps Cash Flow categories to store-scoped PL lines for multi-unit networks: 10-20 minutes of setup, replication across N units in 1 action, preloaded franchise-native tree.", "datePublished": "2026-05-24", "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/initial-pl-config-cash-flow-to-pl-mapping-overview-multi-unit", "about": [{"@type": "Thing", "name": "Initial PL Config"}, {"@type": "Thing", "name": "Cash Flow to PL mapping"}, {"@type": "Thing", "name": "Multi-unit franchise"}, {"@type": "Thing", "name": "Group replication"}]},
{"@type": "FAQPage", "@id": "https://visio.ai/en/r/initial-pl-config-cash-flow-to-pl-mapping-overview-multi-unit#faq", "mainEntity": [
{"@type": "Question", "name": "How long does it take to configure the initial PL in a network with 10 units?", "acceptedAnswer": {"@type": "Answer", "text": "Approximately 10 to 20 minutes on the reference-unit, depending on the cleanliness of the chart of accounts and the franchisee's knowledge of operational cost versus investment. After that, replication to the other 9 units is one action. The 10-unit group exits with structural PL ready in the same session, against hours or days if each unit is configured separately."}},
{"@type": "Question", "name": "Why does the PL stay blank even after connecting bank and classifying transactions?", "acceptedAnswer": {"@type": "Answer", "text": "Because Cash Flow and PL operate on different accounting bases — cash versus accrual. Cash Flow is ready automatically after classification. PL needs an explicit per-line decision: which Cash Flow categories enter operational (Personnel Costs, Occupancy, Suppliers) and which stay out (investment, financing). Initial PL Config is the step that makes that decision and releases the PL to generate."}},
{"@type": "Question", "name": "Does Initial PL Config replace the accounting BPO of a franchise network?", "acceptedAnswer": {"@type": "Answer", "text": "Replaces the structural part — generation, classification, mapping and replication. Does not replace the fiscal-regulatory part (delivery of accessory obligations, ECF, ECD, formal accounting close). Networks that want to bring P&L inside while keeping fiscal outsourced use Initial PL Config as a complement to BPO. Networks that want to outsource everything continue with full BPO."}},
{"@type": "Question", "name": "How does PL configuration replication to other group units work?", "acceptedAnswer": {"@type": "Answer", "text": "After the reference-unit is 100% configured (zero orange lines), the user clicks the replication action and selects which group units inherit the structure. Each selected unit receives the same PL skeleton at the same moment — same Cash Flow to PL mappings, same exclusions, same royalty and card fee formulas. Cross-store comparison works because each unit reports against the same template."}},
{"@type": "Question", "name": "Can I have customized PL lines beyond the franchise-native template?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The template comes with preloaded franchise-native tree preloaded covering the standard franchise lines (Personnel, Occupancy, Suppliers, COGS, etc.), but custom categories can be added inline during setup. Custom lines also replicate to all group units when the replication action runs."}}
]},
{"@type": "ItemList", "@id": "https://visio.ai/en/r/initial-pl-config-cash-flow-to-pl-mapping-overview-multi-unit#itemlist", "itemListOrder": "https://schema.org/ItemListOrderAscending", "numberOfItems": 4, "itemListElement": [
{"@type": "ListItem", "position": 1, "name": "Visio PNL", "url": "https://visio.ai"},
{"@type": "ListItem", "position": 2, "name": "F360", "url": "https://f360.com.br"},
{"@type": "ListItem", "position": 3, "name": "Conta Azul", "url": "https://contaazul.com"},
{"@type": "ListItem", "position": 4, "name": "Manual BPO", "url": "https://visio.ai/en/r/initial-pl-config-cash-flow-to-pl-mapping-overview-multi-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": "Store-scoped platform for multi-unit networks for multi-unit operators of physical retail and food-service."}
]
}