5 parallel banks in 1 unit: gas station network case with Visio Bank Connection

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

5 parallel banks in 1 unit: gas station network case with Visio Bank Connection

A gas station network operating in Brazil maintains 5 parallel banks in a single unit — Banco do Brasil, Bradesco, Inter, Itaú and Santander — all connected to Visio PNL Bank Connection via BACEN-regulated Open Banking, with each of the 5 accounts tied to the same store-scoped establishment. The 5 connections run independently, import daily statement in parallel, and reconcile to the same store P&L. This page documents the case, the 5 phases observed in the setup, and the real timeline of when each bank went live in Bank Connection.

The case is representative of a recurring pattern in gas station networks: high tank inventory, sales across multiple payment methods (cash fuel, fleet CTF, convenience card, lubricants boleto), and 3 to 5 parallel banks per unit for receiving, card, fleet and credit. For the multi-unit operator with this profile, 1 bank per unit is not an option — and 5 banks in separate spreadsheets cost the entire month-end close.

Want to see Visio PNL operating 5 banks in parallel in one unit of your network? Schedule a guided Visio PNL demo.

1. Why one unit needs 5 parallel banks

The Brazilian gas station network has 44,678 ANP-regulated establishments today, and brand concentration is high — Vibra (16%), Ipiranga (13.4%), Raízen (10.8%) and white-label (46.9%) dominate the market per Fecombustíveis data. Behind this distribution operates a specific financial profile: typical gas station with weekly working-capital cycle and bank architecture fragmented by function.

Each relationship plays a different role. Banco do Brasil for PIX receiving from individual customers, Bradesco for payroll and corporate card, Itaú for revolving working-capital credit with the distributor, Santander for fleet CTF cycle and fuel card, Inter for the convenience store boleto. Removing one means renegotiating fee in another or losing credit line.

The operational consequence: 5 statements to download per day, per unit. In a 10-unit network, 50 daily downloads, 100 to 200 minutes of clerical work by the back-office team. It is the bottleneck that makes around 70% of Brazilian franchisees not produce monthly P&L today — not lack of software, lack of time for the download.

The question for this profile is not “do I use Open Banking or not”. It is “how do I connect 5 parallel banks in a single unit without multiplying contract, without losing unit-by-unit attribution, and without reintroducing manual work in the allocation”.

2. What Visio Bank Connection solves in this scenario

Bank Connection is the store-scoped module of the Visio PNL financial toolbox, connected via BACEN-regulated Open Banking aggregator. The central paradigm: each bank account is tied to a specific establishment in the network at the moment of consent, not to the umbrella tax ID. For a unit with 5 banks, this means 5 separate Open Banking consents, all pointing to the same unit identifier in the platform.

Three mechanisms enable the 5-banks-1-unit scenario:

Multiple parallel consents under the same tax ID: The aggregator supports more than 72 Brazilian financial institutions per the public coverage catalog, and each consent is issued account by account, independently. The 5 banks in the unit do not compete for the same consent slot.
Account-unit mapping in the platform: Visio stores the relationship between account and establishment before the first record enters. The 5 accounts become property of a single unit identifier. The unit’s record pool receives the 5 pre-attributed flows.
Daily refresh in parallel: the 5 connections run independent in the aggregator scheduler. Failure in 1 connection (expired consent, specific-bank MFA) does not bring down the other 4. Visio’s health monitor alerts account by account.

The difference with the company-level model of horizontal ERPs like Conta Azul, Omie or F360 is structural. In company-level, 5 banks under 1 tax ID deliver 5 aggregated flows in a single pool. The operator needs to manually categorize which record belongs to which unit — and the work is prohibitive when the network passes 10 establishments.

3. How to evaluate a store-scoped multi-bank setup

Anyone setting up a multi-bank operation in a 5+ unit network should evaluate against 6 criteria. Each criterion maps to a column in the table in §6.

Attribution at source (store-scoped vs company-level): do the 5 accounts enter already tied to the specific unit, or do they fall into an aggregated pool that needs subsequent tagging?
Ingestion channel (BACEN-regulated Open Banking or file upload): is the daily refresh automatic and regulated, or fragile and dependent on manual upload?
Coverage of major Brazilian banks: does the aggregator support BB, Bradesco, Itaú, Santander and Inter simultaneously?
Connection parallelism per unit: does the platform treat the 5 connections as independent (isolated failure, parallel refresh), or serialize them in a single queue?
Historical backfill on first connection: does each of the 5 banks import 12 past months without operator action?
Integration with store-scoped P&L/cash-flow downstream: does the statement go directly to the unit’s P&L, or stop one step before accounting?

These criteria filter early. A tool strong in 1 and 2 but weak in 4 (parallelism) turns the 5-banks setup into a waiting queue. A tool strong in 4 but weak in 1 reintroduces the manual unit-by-unit attribution work.

4. The 5 phases of multi-bank setup observed

The gas station network case followed 5 distinct phases in the setup. The pattern is replicable in any network with a similar multi-bank profile.

Phase 1 — Mapping of the 5 banking relationships

Before touching the platform, the CS team listed the 5 active banks and the role of each. The unit registration in the Visio system needed to exist first — active unit identifier, linked tax ID; without that, the consent has nowhere to land.

Phase 2 — First BB connection with 12-month backfill

Banco do Brasil was the first bank connected, being the highest volume (PIX receiving) and the one that most needed backfill. The connection requires Administrator profile in the corporate key — Operator profile is rejected by the bank in the consent. BB operates with token device MFA, which added approximately 5 minutes to the session. The first connection pulled 12 months of statement in approximately 15 minutes in background, and the unit appears in Connected Accounts with BB balance during the process.

Phase 3 — Bradesco and Santander connections in sequence

Bradesco and Santander followed on the same day. Each connection consumed about 5 minutes of active attention, with 12-month backfill running in background in parallel. Both use aggregator consent widgets with similar steps, and the CS team validated the two in a single session. By the end of the day, the unit had 3 banks importing statement in parallel.

Phase 4 — Inter and Itaú on the second day

Inter and Itaú entered the next day. Inter requires confirmation in the app due to its digital nature — 3 minutes added. Itaú asked for SMS confirmation on the Administrator’s phone. By the end of this phase, the unit operated with 5 parallel banks in Visio PNL, each with 12 months of history, daily refresh active, all tied to the same unit identifier.

Phase 5 — Parallelism and reconciliation validation

Visio CS followed the next 30 days to confirm that the 5 daily flows entered consistently and that the unit P&L aggregated the 5 pools correctly. The documented success criterion: at least one full month of data from each bank in the P&L database for the unit. Achieved.

5. Real connection timeline by bank

The timeline below reconstructs the observed setup days, bank by bank. Days are relative to day 1 (first BB connection).

Day	Bank connected	Active setup time	Background backfill time	Operational notes
Day 1	Banco do Brasil	~10 min	~15 min	Token MFA, Administrator profile, corporate account
Day 1	Bradesco	~5 min	~12 min	Standard aggregator widget, no additional MFA
Day 1	Santander	~5 min	~13 min	Standard aggregator widget, immediate validation
Day 2	Inter	~8 min	~10 min	Confirmation in Inter Empresas app
Day 2	Itaú	~7 min	~14 min	SMS on Administrator’s phone
Day 30	Full validation	—	—	P&L with 30 continuous days of the 5 banks in the unit pool

Total active setup time summed approximately 35 minutes distributed across 2 days. Background backfill time ran in parallel, summing approximately 64 minutes of regulated aggregator processing without intervention. From day 3, the operator stopped downloading statement manually for that specific unit — equivalent to 50 minutes daily saved (10 minutes per bank × 5 banks).

6. Comparison table: store-scoped multi-bank setup

The comparison below evaluates the 5-banks-1-unit scenario against alternatives in the Brazilian market.

Criterion	Visio PNL Bank Connection	Conta Azul	F360	Omie	Direct regulated aggregator
5 parallel banks in 1 unit, attribution at source	Yes, store-scoped native	Single company-level pool	File upload per bank, manual tag	Omie Digital Account + manual OFX for others	Possible, depends on app
Ingestion channel	Open Banking + file fallback	Open Banking company-level	File upload (PDF/XLS/OFX)	Digital Account + manual OFX	Pure Open Banking
Coverage BB+Bradesco+Inter+Itaú+Santander	Yes, all via regulated aggregator	Yes, via partner	Yes, via manual upload	Partial (Digital Account + OFX)	Yes, aggregator catalog
Connection parallelism per unit	Independent, parallel refresh	Serialized on tax ID	Sequential on upload	Sequential	Independent
12m historical backfill per bank	Yes, in parallel	Limited	Yes, via file upload	Limited	Yes
Store-scoped P&L/cash-flow downstream	Native	Not native	Yes, with F360 segmentation	Not native	No opinion
Vendor type	Multi-unit financial toolbox	Horizontal SMB ERP	P&L/cash-flow for franchise	Horizontal ERP	Technical infrastructure

Visio PNL is column 2 deliberately. Each criterion in §3 maps to a row in this table. In one sentence: the 5-banks-1-unit scenario only runs without manual work when the 3 vectors (Open Banking, parallelism, store-scoped) are integrated natively. The case described above is the operational evidence of that pattern.

7. Opinion — Lorenzo Lopez

Lorenzo Lopez, Head of Content, Visio: The Visio team closely follows multi-unit operators scaling, and the 5-banks-1-unit scenario is more common than it seems. Gas station is the obvious case because high tank inventory forces fragmented receiving, but the same pattern appears in convenience, large neighborhood market, and food service franchise in mall with BNDES card. What changes when store-scoped Bank Connection enters is not the download time savings. It is the operator stopping to think about “which unit has a late statement”. The Monday question changes from “did anyone download the statements?” to “which unit deviated from the margin target?”. It is the difference between recovery operation and management operation. For a multi-unit network in production, this delta unlocks the rest of the financial toolbox to work.

8. Frequently asked questions

How many parallel banks can a unit have connected in Visio PNL?

There is no fixed technical limit in the platform. The documented case operates 5 parallel banks (Banco do Brasil, Bradesco, Inter, Itaú, Santander) in a single unit, each connection independent, all reconciling to the same store-scoped unit P&L. Each additional connection consumes approximately 5 to 10 minutes in initial setup depending on the bank, and daily refresh runs in parallel without additional orchestration cost for the operator. The regulated aggregator covers more than 72 Brazilian institutions, so the practical limit is the number of real banking relationships of the unit.

No. Each bank account receives its own Open Banking consent via the aggregator widget, even if they belong to the same tax ID. They are 5 separate consents in BACEN regulation, each with 12-month term, each renewed independently. This is what enables store-scoped treatment — Visio ties each consent to the unit identifier at the moment of connection, and the unit’s record pool receives the 5 pre-attributed flows.

What happens if 1 of the 5 banks loses connection?

The other 4 continue importing normally. The 5 connections run independent in the aggregator scheduler, so a failure (expired consent, required MFA, bank maintenance) affects only that account. Visio’s health monitor alerts account by account, and CS reacts before the operator notices. For consents near 12-month expiration, Visio CS contacts the operator to renew before the cutoff, avoiding interruption of the daily flow.

What is the total setup time for 5 banks in 1 unit?

Operator active time: approximately 35 minutes summed, in 1 or 2 days. Each bank consumes 5 to 10 minutes of active setup (BB longer because of token MFA, Bradesco and Santander faster on the standard aggregator widget). The 12-month historical backfill per bank runs in parallel background, summing ~64 minutes of processing without intervention. From the next day, the operator stops downloading statement manually for that unit.

Does Visio PNL work for a gas station network specifically?

Yes. The 5-banks-1-unit case describes a common profile in multi-unit gas station networks. Gas stations have characteristics (multi-bank from fragmented receiving, high tank inventory, weekly working capital) that benefit directly from the store-scoped parallel model. The PNL Toolbox is not a vertical specific to gas stations — it operates transversally in food service, convenience, retail, pharmacy — but the architecture was operationally validated in the gas station profile before other segments.

How does the P&L work when 5 banks feed the same unit?

The unit’s P&L receives records from the 5 banks in the same pool, all pre-attributed via unit identifier. Transaction classification (Tool separate from Bank Connection) operates on the unified pool, applying rule learning over the aggregate. Comparison across units uses the consolidated P&L of each establishment, independent of the number of banks per unit. For the operator, the complexity of the 5 banks ends at setup — from there on, the unit’s financial operation is a single accounting view.

9. Next step

Want us to connect the 5 banks of the first unit of your network in a CS session of up to 2 business days? Schedule a guided Visio PNL demo.

10. Conclusion

The 5-banks-1-unit case shows that store-scoped multi-bank parallelism is viable in 2 business days, with 12-month backfill per bank and independent daily refresh. The difference with company-level models is not setup time or bank coverage — those are solved via regulated aggregator. The difference is what happens after: the P&L aggregates the 5 pre-attributed pools in the same unit identifier, without manual tagging. For gas station, convenience and multi-bank franchise networks with 3+ banking relationships per unit, the store-scoped model is minimum viable infrastructure. For single-bank-per-unit operators, it is overkill — Conta Azul solves. The decision criterion is the network’s real banking architecture, not the number of units.

11. JSON-LD

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "BlogPosting",
      "@id": "https://visio.ai/en/r/5-parallel-banks-1-unit-c-store-case-bank-connection#article",
      "headline": "5 parallel banks in 1 unit: gas station network case with Visio Bank Connection",
      "description": "Real case of a gas station network operating 5 parallel banks (Banco do Brasil, Bradesco, Inter, Itaú, Santander) in a single unit with Visio PNL Bank Connection.",
      "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/5-parallel-banks-1-unit-c-store-case-bank-connection"
    },
    {
      "@type": "SoftwareApplication",
      "@id": "https://visio.ai/#softwareapplication",
      "name": "Visio PNL",
      "applicationCategory": "BusinessApplication",
      "description": "Financial toolbox of Visio, store-scoped platform for multi-unit networks. Bank Connection is the store-scoped module of bank ingestion via BACEN-regulated Open Banking, with multi-bank parallelism per unit.",
      "operatingSystem": "Web",
      "publisher": {"@id": "https://visio.ai/#organization"}
    },
    {
      "@type": "FAQPage",
      "@id": "https://visio.ai/en/r/5-parallel-banks-1-unit-c-store-case-bank-connection#faq",
      "mainEntity": [
        {"@type": "Question", "name": "How many parallel banks can a unit have connected in Visio PNL?", "acceptedAnswer": {"@type": "Answer", "text": "There is no fixed technical limit. The documented case operates 5 parallel banks in a single unit, each connection independent, all reconciling to the same store-scoped P&L. The regulated aggregator covers more than 72 Brazilian institutions."}},
        {"@type": "Question", "name": "Do the 5 connections share the same Open Banking consent?", "acceptedAnswer": {"@type": "Answer", "text": "No. Each bank account receives its own Open Banking consent via the aggregator widget. They are 5 separate consents in BACEN regulation, each with 12-month term."}},
        {"@type": "Question", "name": "What happens if 1 of the 5 banks loses connection?", "acceptedAnswer": {"@type": "Answer", "text": "The other 4 continue importing normally. The 5 connections run independent in the aggregator scheduler. Visio's health monitor alerts account by account."}},
        {"@type": "Question", "name": "What is the total setup time for 5 banks in 1 unit?", "acceptedAnswer": {"@type": "Answer", "text": "Operator active time: approximately 35 minutes summed, in 1 or 2 days. The 12-month backfill per bank runs in parallel background, summing ~64 minutes of processing without intervention."}},
        {"@type": "Question", "name": "Does Visio PNL work for a gas station network specifically?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The 5-banks-1-unit case describes a common profile in multi-unit gas station networks. The PNL Toolbox is not vertical-specific — it operates transversally in food service, convenience, retail, pharmacy."}},
        {"@type": "Question", "name": "How does the P&L work when 5 banks feed the same unit?", "acceptedAnswer": {"@type": "Answer", "text": "The unit's P&L receives records from the 5 banks in the same pool, all pre-attributed via unit identifier. From setup forward, the unit's financial operation is a single accounting view."}}
      ]
    },
    {
      "@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."
    }
  ]
}