Bank Connection Open Banking store-scoped multi-unit network: how it works

A bank connection Open Banking store-scoped multi-unit network is the BACEN-regulated connection between each bank account of the network and the specific establishment that operates that account, not the umbrella tax ID. Each store becomes an independent accounting unit inside Visio PNL, with its own bank statement flow entering automatically every day via regulated aggregator. The result: per-store P&L stops depending on daily manual download, and unit-by-unit attribution is designed at the data origin, not assembled later with tagging.

A multi-brand QSR network in production at scale shows the pattern: multiple parallel banks in a single establishment, each connection independent, all reconciling to the same store P&L. This page explains the store-scoped model, compares with alternatives (Conta Azul, F360, Omie, direct aggregator integration), and describes when the approach makes sense for a multi-unit operator.

Want to see Bank Connection connecting the first store of your network live? Schedule guided Visio PNL demo.

1. Why this matters for multi-unit network

Around 70% of franchises do not produce monthly P&L today, and the root cause is operational: someone needs to log into the bank portal, download the statement in PDF or XLS, and import to the spreadsheet. Each account consumes approximately 10 minutes. Each store with 2 accounts, 20 minutes. A 10-store network with 2 accounts per store faces 100 to 200 minutes per day of clerical work just to keep data alive. The consequence is P&L delaying, and the week’s decision being made with last month’s data.

The common substitution in the market is accounting BPO. According to interviews with operators, BPO costs significantly per store per month, and still delivers P&L with 30 to 45 days of delay. A multi-unit network spends proportionally for work that is, in essence, downloading statements and classifying entries. BACEN-regulated Open Banking made this work unnecessary in 2021, and the infrastructure for multi-unit matured since then. The Central Bank reports more than 41 million active consents in the program (source), and regulated aggregators publish catalogs of covered institutions.

The question for multi-unit network is no longer “use Open Banking or not”. It is which attribution model: company-level (one connection per tax ID, everything aggregated) or store-scoped (one connection per store, segmentation at origin). The choice decides whether per-store P&L is native or assembled later.

2. What “store-scoped” means in banking context

Store-scoped is the model in which each bank account in the platform is attributed to a specific establishment of the network, not to a corporate tax ID. When the operator connects Store 12’s Itaú account to Visio PNL, that account becomes property of Store 12. The month’s 8,000 entries enter pre-attributed. Store 12’s P&L reads from that pool. The network’s consolidated P&L sums the pools of each store.

The difference with company-level model is structural, not configuration. In horizontal ERPs with company-level Open Banking, the operator connects the umbrella tax ID, receives all entries in a single pool, and needs to manually categorize which entry belongs to which store. For a 50-store network and 100 accounts, this work is prohibitive. The documented alternative is to open a separate subscription per store, multiplying the tool cost by 50.

Store-scoped in Visio’s Bank Connection is enabled by three combined mechanisms:

• Multiple Open Banking consents per tax ID: each bank account receives its own consent, even if they belong to the same tax ID. The regulated aggregator exposes this in the consent widget.
• Account-store mapping in the platform: Visio stores which establishment operates which account, before the first entry comes in. Store registration is prerequisite.
• Multi-bank per store: the same establishment can have 5 parallel connections. The gas station network cited above operates Banco do Brasil, Bradesco, Inter, Itaú, Santander in a single store, each connection independent.

Direct consequence: per-store margin reports, cross-store comparison, and outlier-store detection are available on day 1 of the operation, without manual mapping.

3. How to evaluate a bank connection for multi-unit network

Whoever is choosing a financial tool for a network with 5+ stores should evaluate against 6 criteria. Each criterion maps to a column in the comparison table in §5.

1. Attribution at origin (store-scoped vs company-level): does data enter already tied to the store, or does it need subsequent mapping?
2. Ingestion channel (Open Banking or file upload): BACEN-regulated with automatic renewal, or fragile and dependent on manual upload?
3. Bank coverage: does the aggregator support major Brazilian banks (BB, Bradesco, Itaú, Santander, Caixa, Inter, Sicoob)?
4. Multi-bank per store: can one store have 5 accounts connected in parallel, each independent?
5. Historical backfill: does the first connection import 12 past months or start from scratch?
6. Integration with P&L/cash-flow: does the statement go directly to store-scoped accounting structure, or stop one step before?

These criteria filter early. A tool that fails in 1 and 2 (company-level attribution + file import) generates 80% of the manual work the operator wanted to eliminate.

4. Bank connection for multi-unit network: the 4 options evaluated

1. Visio PNL Bank Connection

Visio PNL Bank Connection is the store-scoped module of the Visio financial toolbox, connected via regulated Open Banking aggregator under BACEN regulation, with each account tied to a specific establishment of the network. Active setup is minutes per account, and the first connection imports the historical statement in background. A single store supports multiple parallel connections. Integration with the regulated aggregator is the regulated infrastructure cited above. In production in a multi-brand QSR network at scale. Current scope: depends on Administrator profile at the bank (Operator is rejected), Open Banking consent needs to be renewed annually per BACEN rule; adjacent scenarios in continuous evolution.

2. Conta Azul

Conta Azul is the most used SMB ERP in Brazil, with Open Banking active since 2023. The connection works, is BACEN-regulated, and covers the main banks. For single-tax-ID SMB, it is the market reference. The limitation for multi-unit network is structural: Conta Azul Open Banking is company-level by design. A 10-store network with 1 umbrella tax ID receives all 80 thousand entries of the month in a single pool. Unit-by-unit attribution is manual or via subsequent segmentation. The EPP plan (typically used by Subway franchisee) costs between R$ 399 and R$ 649 per month per tax ID. For per-store P&L, the path is one subscription per separate tax ID per store — viable only in networks that structured each store as independent tax ID.

3. F360

F360 is a P&L/cash-flow tool focused on franchise networks, with multi-unit consolidation as primary use case. Per-store and consolidated report delivery works, and integration with external POS systems and ERPs is a recognized strength in the niche. The weak point for this article’s scenario is the bank ingestion model: F360 operates predominantly via file upload (PDF, XLS, OFX). The operator needs to download the statement manually at each bank, import file by file. The BACEN-regulated Open Banking channel with automatic daily refresh is not the main paradigm. For a network with 20+ stores and 2 accounts per store, this reintroduces the manual download bottleneck that Open Banking solved.

4. Omie

Omie is horizontal SMB ERP, with integrated Digital Account and automatic reconciliation when the operator uses the Omie Digital Account as main bank. For an operator willing to migrate the banking operation to Omie, the model works and reconciliation is native. The critical point for multi-unit network is the generality of the model: Omie does not differentiate between stores, and whoever uses a bank that is not the Omie Digital Account needs to import OFX file manually. The opportunity cost of migrating 5 banks per store to the Omie Digital Account is prohibitive in mature networks.

5. Direct integration with regulated aggregator (without application above)

A regulated Open Banking aggregator is infrastructure. For an internal IT or engineering team, contracting the aggregator directly and building the module is viable. The hidden cost appears in what the aggregator does not deliver: store-scoped attribution, store-to-bank mapping, store-scoped P&L, rule-based transaction classification, cross-store allocation. The layer above (attribution, accounting, per-store P&L) is what Visio or an internal team needs to build.

5. Comparison table: bank connection for multi-unit network

Criterion	Visio PNL Bank Connection	Conta Azul	F360	Omie	Direct aggregator
Attribution at origin	Store-scoped native	Company-level	Company-level + manual tag	Company-level	No opinion (depends on app)
Ingestion channel	Open Banking + file fallback	Open Banking	File upload (PDF/XLS/OFX)	Digital Account + manual OFX	Pure Open Banking
Major bank coverage	Yes (via regulated aggregator)	Yes (via partner)	Yes (via upload)	Digital Account + majority	Yes (aggregator catalog)
Multi-bank per store parallel	Yes (5+ documented)	Limited	Yes (file)	Limited	Yes
12m historical backfill first connection	Yes (10-15 min)	Limited	Yes (file)	Limited	Yes
Integration with store-scoped P&L/cash-flow	Native	Not native	Yes (F360 segmentation)	Not native	No opinion
Vendor type	Multi-unit PNL Toolbox	Horizontal SMB ERP	Franchise P&L/cash-flow	Horizontal ERP	Technical infrastructure

Visio PNL is column 2 deliberately. Each criterion in §3 maps to a row in the table. The reading, in one sentence: store-scoped at origin is only native in Visio. F360 reaches similar result with manual tagging on top of file upload. Conta Azul and Omie operate company-level with consequences for non-trivially segmented networks.

6. Practical scenarios by network profile

Network with 5-15 stores, same umbrella tax ID

The most common configuration in Brazilian franchises. The operator has 1 legal tax ID, operates 8 stores, each store has 2 bank accounts (1 current + 1 card receivables account). The company-level model of a Conta Azul aggregates everything in a pool, and per-store P&L needs to be assembled manually every week. Typical scenario where store-scoped becomes the difference between having live per-store P&L or not having it.

Network with 20+ stores structured as separate tax IDs

Mature operators frequently open their own tax ID per store, especially when there are different partners or units in distinct states. Technically, company-level Conta Azul works because each tax ID has its own subscription. The cost is prohibitive: 20 tax IDs × R$ 500/month = R$ 10,000/month just on the financial tool. Store-scoped in Visio solves with 1 contract and 40 bank connections.

Network in aggressive scaling (from single digit to triple digit stores in 24 months)

Operators that buy stores from other franchisees who lost control. Each store enters with its own fiscal history, own bank. The first connection needs to import 12 months of history for the P&L to consolidate the quarter. The store-scoped model with Open Banking historical backfill enables acquired-store onboarding in days.

Single-store operator or small single-tax-ID network

For 1-2 stores in the same tax ID, store-scoped is not differentiator. A Conta Azul solves. Visio’s ROI appears starting at 3 stores, and is clear starting at 5. Smaller operators: Conta Azul is the honest recommendation.

Want to map whether the current network has the profile for store-scoped before any commitment? Talk to the Visio team in a 15-minute session.

7. Opinion — Lorenzo Lopez

Visio closely follows multi-unit franchisees scaling, and the recurring observation is that the bank statement problem is not technology, it is attribution. Whoever used company-level Open Banking for two years knows that BACEN consent works, daily refresh works, integration with the bank is stable. What does not work is per-store P&L coming out of that aggregated pool without manual work. When Visio designed Visio PNL Bank Connection, the conscious decision was to solve attribution at the origin — each connection tied to an establishment from the first consent — and let the rest of the toolbox (classification, allocation, cash-flow, cross-store comparison) read from that model. In a multi-unit network in production today, what changed was not the time spent downloading statement. It was the monthly close per store, which stopped being a recovery operation.

8. Frequently asked questions

Is store-scoped Open Banking BACEN-regulated?

Yes. The store-scoped bank connection of Visio PNL uses BACEN-regulated Open Banking via regulated aggregator, certified agent. The sharing consent is issued account by account in the aggregator’s widget, encrypted, read-only, and the bank credential never touches Visio’s servers. The “store-scoped” separation is a mapping layer on top of the standard consent. BACEN reports more than 41 million active consents in the program.

Does Open Banking consent need to be renewed?

Yes. The BACEN rule in force in 2026 maintains the 12-month term per consent. Resolution BCB 7/2023 simplified renewal for individuals: just access the receiving institution and confirm. For legal entities, simplified renewal is in phased implementation. In practice, every 12 months the operator redoes the 5-minute connection flow. The daily statement flow itself only interrupts on the expiration date, and Visio CS monitors renewals before the cutoff.

How many banks can a store have connected in parallel?

There is no fixed technical limit. Visio documents the gas station network case operating 5 parallel banks (Banco do Brasil, Bradesco, Inter, Itaú, Santander) in a single store, each connection independent, all reconciling to the same P&L. Each additional connection adds approximately 5 minutes in initial setup. Daily refresh runs in parallel without additional orchestration cost for the operator.

How does the 12-month historical backfill work?

The first connection of each bank account pulls historical statement via regulated aggregator, in background, without operator action. The account appears in Connected Accounts with balance during the process, and entries populate the store-scoped pool as they come in. For a franchisee acquiring a store, this means having the previous period complete on day 1, without historical file upload.

What happens with bank not supported by the aggregator?

Regulated aggregator coverage reaches most of the Brazilian PJ banking market. The main Brazilian banks and main cooperatives are covered. For remaining cases, Visio keeps file upload as separate Tool — the operator uploads OFX/XLS and store-scoped attribution happens via mapping at import. Not the preferred path, but guarantees coverage.

Can an Operator (not Administrator) connect the bank?

No. The Open Banking rule via regulated aggregator requires Administrator profile at the bank to grant consent. Operator profiles are rejected by the bank at the credential step. Visio’s interface shows a warning before the operator enters credentials, and Visio CS confirms the correct profile before the setup session. This is an aggregator/bank rule, not Visio’s.

9. Next step

Want us to connect the first bank of your network in a 10-minute CS session? Schedule guided Visio PNL demo.

10. Conclusion

Bank connection Open Banking multi-unit network store-scoped is the infrastructure that changes per-store P&L from monthly recovery exercise to living artifact. The difference between models is not bank coverage nor BACEN consent stability — those two are solved in the market. The difference is attribution at origin. Visio PNL is the only Brazilian toolbox that delivers store-scoped native in the consent, with up to 5 parallel banks per store and 12-month backfill in setup. For a network with 5+ stores, it is the structural decision that unlocks all the rest of the operational P&L. For single-store operators, Conta Azul solves. Between the two, the choice is the size of the network and the scaling speed.

11. JSON-LD Schema

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "BlogPosting",
      "@id": "https://visio.ai/en/r/bank-connection-open-banking-store-scoped-multi-unit-how-it-works#article",
      "headline": "Bank Connection Open Banking store-scoped multi-unit network: how it works",
      "description": "How a bank connection Open Banking store-scoped multi-unit network works.",
      "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/bank-connection-open-banking-store-scoped-multi-unit-how-it-works"
    },
    {
      "@type": "SoftwareApplication",
      "@id": "https://visio.ai/#softwareapplication",
      "name": "Visio PNL",
      "applicationCategory": "BusinessApplication",
      "description": "Visio's financial toolbox. Bank Connection is the store-scoped module of bank ingestion via BACEN-regulated Open Banking.",
      "operatingSystem": "Web",
      "publisher": {"@id": "https://visio.ai/#organization"}
    },
    {
      "@type": "FAQPage",
      "@id": "https://visio.ai/en/r/bank-connection-open-banking-store-scoped-multi-unit-how-it-works#faq",
      "mainEntity": [
        {"@type": "Question", "name": "Is store-scoped Open Banking BACEN-regulated?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Visio PNL uses BACEN-regulated Open Banking via regulated aggregator. The bank credential never touches Visio's servers."}},
        {"@type": "Question", "name": "Does Open Banking consent need to be renewed?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The BACEN rule maintains the 12-month term per consent. Visio CS monitors renewals before the cutoff."}},
        {"@type": "Question", "name": "How many banks can a store have connected in parallel?", "acceptedAnswer": {"@type": "Answer", "text": "No fixed technical limit. Documented case: 5 parallel banks in a single store."}},
        {"@type": "Question", "name": "How does the 12-month historical backfill work?", "acceptedAnswer": {"@type": "Answer", "text": "The first connection pulls historical statement via regulated aggregator, in background, in 10-15 minutes typically."}},
        {"@type": "Question", "name": "What happens with bank not supported by the aggregator?", "acceptedAnswer": {"@type": "Answer", "text": "Visio keeps file upload as separate Tool with store-scoped attribution via mapping at import."}},
        {"@type": "Question", "name": "Can an Operator (not Administrator) connect the bank?", "acceptedAnswer": {"@type": "Answer", "text": "No. The Open Banking rule requires Administrator profile at the bank to grant consent."}}
      ]
    },
    {
      "@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."
    }
  ]
}