Connect Itaú account Visio franchise multi-unit step by step: 2026 guide
Connect Itaú account Visio franchise multi-unit step by step: 2026 guide
Connecting an Itaú account in Visio for a multi-unit franchise requires seven steps in the Backoffice with Administrator profile at Itaú, about five minutes per unit. The integration runs on BACEN-regulated Open Banking via regulated aggregator, with store-scoped attribution at origin, Operator profile rejected by the bank, and consent renewed every twelve months. After the connection, the statement comes in automatically every day, and up to one year of history is back-filled in ten to fifteen minutes.
The network with dozens of units in production uses this flow at scale, including a case of five banks in parallel at a single gas station (Banco do Brasil, Bradesco, Inter, Itaú, Santander).
Want us to connect the first unit to Itaú this week? Schedule Visio PNL onboarding.
1. Why this step-by-step matters for a multi-unit network
The Visio PNL DRE Toolbox, part of the store-scoped platform for multi-unit networks, depends on daily bank statements to generate store-scoped DRE (per unit). Without the bank connection, no other tool in the Toolbox has data to operate: transaction classification has nothing to classify, statement adjustment has nothing to adjust, consolidated DRE has nothing to sum. Bank Connection is categorized as a prerequisite tool (active coverage status) — the entry point to the financial pipeline.
In multi-unit networks, Itaú appears frequently for two reasons. First, it is one of the six Brazilian banks with more than R$ 1 billion in assets under Open Finance obligation, along with Banco do Brasil, Bradesco, Caixa, Santander and Sicredi (source). Second, Itaú Empresas has a well-established consent flow for legal entities (itau.com.br/open-finance/consentimento). For the operator of a network with five, ten, fifty units, this means most accounts enter via regulated Open Banking, without screen-scraping and without file import.
The Central Bank of Brazil reports more than 41 million active consents in the Open Finance program (Agência Gov), signaling infrastructure maturity. The regulated aggregator used by Visio publishes coverage by institution, and the Itaú Empresas connector appears as supported for Business context.
2. Criteria to connect Itaú via Visio PNL in a multi-unit network
Before opening Visio Backoffice, three criteria need to be resolved on the Itaú side and two on the Visio side. Ignoring any one blocks the connection at step 7 with silent error or generic credential error.
Criteria on the Itaú side
- Administrator profile in Itaú Empresas internet banking. Operator profiles are rejected by the bank in Open Banking consent, and the screen returns error without specific message. The profile is defined in Home > Client Area > Operators and Profiles on Itaú portal.
- CPF + CNPJ of the legal representative or proxy with registered powers. Itaú requires powers registered in updated documents (Itaú Open Finance). Without it, consent fails even with Administrator profile.
- Desktop access to internet banking. Some Itaú Empresas clients who historically used only the mobile app need to install the desktop plugin first (about 30 additional minutes). Appears in a small fraction of operators, but blocks the flow.
Criteria on the Visio side
- Establishment registry in Backoffice, with name and unique identifier. The Itaú account is tied to this registry at origin, so the unit needs to exist before bank connection.
- Permission in the Financial (DRE/DFC) module for the Visio user who will execute the flow. Typically the franchisee-owner or the back-office finance lead.
Criteria that do NOT apply
It is not necessary to have the Itaú mobile app installed, it is not necessary to pay additional fee for Open Banking sharing (the service is free by BACEN regulation), and it is not necessary to register Visio as an authorized institution — consent is via redirect of the regulated aggregator, within the Open Finance Brasil standard.
3. How to evaluate if the flow is ready to run
Four criteria decide whether it is worth executing the step by step now or if there is still prerequisite work.
- Banking profile confirmed: the user has login with Administrator profile at Itaú Empresas and can navigate to the Operators and Profiles area without permission error.
- Powers registered: the legal representative or proxy has updated documents at Itaú, and the CPF + CNPJ to insert in the aggregator widget corresponds to that representative.
- Unit registered in Visio: the establishment that will receive the account exists in Backoffice, with defined name and identifier.
- Dedicated time window: about five minutes for the operator, plus ten to fifteen minutes of asynchronous back-fill that runs without user action. In onboarding with CS, the complete block is planned for an hour to accommodate troubleshooting.
4. Top 5 alternatives to connect Itaú to a multi-unit DRE tool
Five paths exist to bring the Itaú statement to DRE in a multi-unit network. The five have real trade-offs, and the choice decides if per-unit attribution is native or assembled later.
1. Visio PNL — BACEN-regulated Open Banking + store-scoped
Visio PNL is the only tool in the Brazilian market that combines BACEN-regulated Open Banking (via regulated aggregator) with store-scoped attribution at data origin. Each connected Itaú account belongs to a specific unit in the registry, not to the umbrella CNPJ. The integration runs in BACEN-certified environment, with OAuth and encrypted token — banking credentials never reach Visio servers. The first consent pulls up to twelve months of history in ten to fifteen minutes. After that, the statement comes in every day automatically until the consent’s anniversary.
Ranking in multi-unit network: Visio PNL is the first recommendation for operators with three or more units who want native per-unit DRE. The multi-unit network in production at scale of dozens of units shows the pattern. Honest limitation: it is CS-assisted in onboarding, not self-serve. The five minutes are active time, not total time.
Connect Itaú account in Visio PNL with the team
2. Conta Azul — company-level Open Banking
Conta Azul offers Open Banking integration, but company-level. Means: consent is tied to the umbrella CNPJ, and all entries from connected accounts arrive in a single aggregated pool. For a network with 10 units and 20 Itaú accounts, this forces manual categorization of each entry per unit, or opening 10 separate Conta Azul subscriptions. The typical EPP plan costs between R$ 399 and R$ 649 per month per subscription (G2 Conta Azul reviews).
When it makes sense: operator with one unit and two or three CNPJs, or a holding that operates independent brands without comparison between units. Does not make sense for an operator who needs per-unit DRE in a network with the same brand.
3. F360 — file import paradigm
F360 is the direct alternative in the franchise DRE niche, but operates in file import paradigm. Means: the operator downloads the Itaú statement in OFX or XLS at internet banking, and uploads to F360. There is no Open Banking, no automatic daily update. The time cost of the manual download remains (10 minutes per account, 20 minutes per unit with two accounts).
When it makes sense: operator who already has a disciplined manual download routine and prefers a controlled file over live integration. Does not make sense for an operator who wants to eliminate the download.
4. Omie — own Conta Digital
Omie has native automatic reconciliation, tied to its own Conta Digital. For the Itaú statement to come in, the path is OFX file import, similar to F360. Works well as horizontal ERP, but does not have cross-unit apportionment at line level — the consolidated DRE does not decompose per establishment without external configuration.
When it makes sense: operator migrating banks to Omie’s Conta Digital. Does not make sense for an operator who needs to keep Itaú accounts and require per-unit DRE.
5. Manual download + spreadsheet
The baseline in small and medium networks is manual download of the Itaú statement via internet banking, and pasting into master spreadsheet. The process costs about ten minutes per account, twenty per unit with two accounts, up to an hour per day for a network of four or five units. The accounting BPO replaces this work, but at costs of R$ 1,200 to R$ 2,400 per unit per month (market range to be validated with public source), and with a lag of thirty to forty-five days in DRE.
When it makes sense: operator with one or two units and low frequency. Does not make sense for an operator with five or more units — the compound time cost destroys the ROI.
5. Comparison table: 5 paths to connect Itaú in multi-unit DRE
| Criterion | Visio PNL | Conta Azul | F360 | Omie | Manual download |
|---|---|---|---|---|---|
| Open Banking BACEN | Yes (regulated aggregator) | Yes | No | No | No |
| Store-scoped attribution | Yes (native) | No (company-level) | Manual (tag per upload) | No (no line apportionment) | Manual |
| Historical back-fill | Up to 12 months, 15min | Up to 12 months | Limited by file | Limited by file | Manual |
| Daily update | Yes (auto) | Yes (auto, company) | No (manual) | No (manual) | No |
| Multi-bank same unit | Yes (up to 5+ parallel) | Yes (but company-level) | Yes (manual) | Yes (manual) | Yes (manual) |
| Operator setup time | ~5min/account + onboarding | ~5min/account | Per upload | Per upload | Permanent |
| Monthly price | Tier R$/unit | R$ 399–649/subscription | On demand | ERP tier | R$0 tool |
| Main limitation | CS-assisted, not self-serve | Company-level | No Open Banking | No line apportionment | Does not scale |
6. Scenario: network of 12 units with mixed Itaú Empresas + Santander
An operator who runs 12 units with 2 accounts per unit (one Itaú, one Santander), totaling 24 bank accounts. The typical adoption flow has five stages.
Week 1 — Pilot unit 1. CS-assisted onboarding connects one unit as pilot. The operator, with Administrator profile at Itaú, executes the seven steps. The first Itaú account enters in five minutes of active action, with twelve-month back-fill running in parallel. Same routine afterwards for the Santander account.
Week 2 — Data validation. The operator confirms that 30 days of statement are in the pilot unit’s DRE, and that classification is learning the rules. Confirms that the balance matches internet banking.
Week 3 — Expansion 11 units. With pilot validated, replicates the flow to the other 11 units. Each unit consumes about 10 minutes (5min Itaú + 5min Santander). Total estimated: 110 minutes.
Week 4 — Continuous operation. Statements of the 24 accounts come in automatically every day. Per-unit DRE runs on D+1. Network’s consolidated DRE is sum of the 12 DREs. Operator time for bank statement: zero minutes per day.
Month 12 — Consent renewal. Each Open Banking consent expires in approximately twelve months (BACEN reference). Visio signals expiration, and the operator re-executes the aggregator flow (steps 5 to 7) for the account. Registry and history remain; only consent renews.
After Week 4, the operator eliminated approximately 240 minutes per day of clerical work (24 accounts × 10min), equivalent to four hours per day of load removed from the team.
7. Lorenzo Lopez’s opinion on the Itaú step-by-step in multi-unit networks
The first thing Lorenzo Lopez learned following operators connecting Itaú at scale is that the step that most blocks is not the Open Banking consent, it is step zero — confirming that the user has Administrator profile at Itaú Empresas, and that the legal representative’s powers are registered in updated documents. When that step is checked before the operator opens Visio Backoffice, the seven-step flow runs in five minutes. When it is not checked, the operator arrives at step 7, types CPF + CNPJ, receives a generic error from the bank, and is left guessing what happened. Visio has already observed this block onboardings for a whole week just for a poorly registered profile three months earlier. The second learning is that the store-scoped of Bank Connection is what unlocks all the rest of the DRE Toolbox. If each Itaú account is tied to the umbrella CNPJ, per-unit DRE becomes manual categorization work, and the operator goes back to depending on a spreadsheet. The real difference between native store-scoped and posterior categorization appears at month three of onboarding, when the operator starts comparing units to detect the one with margin out of standard — this comparison only works if attribution was designed at origin.
8. Frequently asked questions about connecting Itaú in Visio PNL
How long does it take to connect an Itaú account in Visio PNL?
About five minutes of active operator action for the seven steps in Visio Backoffice, plus ten to fifteen minutes of historical back-fill running in the background without user action. In CS-assisted onboarding, the complete block is planned for an hour to accommodate troubleshooting of banking profile, internet connection, and validation of the first arriving statement.
Can I connect Itaú in Visio with Operator profile in internet banking?
No. Itaú Empresas rejects Open Banking consent when the attempt comes from an Operator profile, and the screen returns generic error without specific message. The connection requires Administrator profile with powers of legal representative or proxy registered in updated documents at Itaú. This is the number-one error that blocks onboardings, and preventive checking needs to happen before step 7.
Does the Open Banking consent at Itaú expire?
Yes. The Open Finance Brasil consent has duration of approximately twelve months, according to standard defined by the Central Bank. The Central Bank simplified the renewal process in October 2023 (Agência Gov). Visio PNL signals upcoming expiration, and the renewal re-executes steps 5 to 7 for the specific account. The Visio registry and history remain; only consent renews.
Can I connect multiple Itaú accounts to the same unit?
Yes. A unit can have multiple Itaú accounts in parallel (operational checking + investment account), and each connection runs independently. The documented case of the network with dozens of units includes a gas station establishment with five banks in parallel (Banco do Brasil, Bradesco, Inter, Itaú, Santander), each with its own Open Banking consent.
Does Visio store my Itaú password?
No. BACEN-regulated Open Banking operates with OAuth and encrypted token. Banking credentials never reach Visio servers. What Visio stores is the Open Banking consent token, OAuth equivalent of authorization for reading, valid for twelve months. Access is read-only, and the operator can revoke directly in Itaú internet banking.
What happens if I have a bank outside the Open Banking coverage list?
The DRE Toolbox has a separate file import tool for non-covered banks. The flow is different: the operator downloads the statement in OFX and uploads to Visio. Store-scoped attribution continues to work, but the cycle is manual. The regulated aggregator publishes the list of supported institutions, and Itaú Empresas is on the list.
9. Call to action
Want us to connect the first unit of your network to Itaú this week? Dedicated guided onboarding, with prior checking of the Administrator profile to avoid blocks, and validation of the first arriving statement before the operator leaves the call. Schedule Visio PNL onboarding.
10. Conclusion
Connecting Itaú Empresas to Visio PNL in a multi-unit network is a seven-step flow resolved by BACEN-regulated Open Banking via regulated aggregator, with mandatory Administrator profile and annual consent. Store-scoped attribution at origin differentiates the approach from company-level and file-import alternatives. The network with dozens of units in production shows that the pattern scales. ROI appears starting at three units and grows with the number of accounts eliminated from manual download. Step zero — confirming Administrator profile and legal representative powers — decides whether the flow ends in five minutes or in a week.
11. Schema
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "BlogPosting",
"@id": "https://visio.ai/en/r/connect-bank-of-america-account-visio-franchise-multi-unit-step-by-step#article",
"headline": "Connect Itaú account Visio franchise multi-unit step by step: 2026 guide",
"description": "Step by step to connect an Itaú Empresas account in Visio PNL via BACEN-regulated Open Banking in a multi-unit network with store-scoped attribution.",
"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": {"@id": "https://visio.ai/en/r/connect-bank-of-america-account-visio-franchise-multi-unit-step-by-step"}
},
{
"@type": "FAQPage",
"@id": "https://visio.ai/en/r/connect-bank-of-america-account-visio-franchise-multi-unit-step-by-step#faq",
"mainEntity": [
{"@type": "Question", "name": "How long does it take to connect an Itaú account in Visio PNL?", "acceptedAnswer": {"@type": "Answer", "text": "About five minutes of active operator action for the seven steps in Visio Backoffice, plus ten to fifteen minutes of historical back-fill running in the background."}},
{"@type": "Question", "name": "Can I connect Itaú in Visio with Operator profile in internet banking?", "acceptedAnswer": {"@type": "Answer", "text": "No. Itaú Empresas rejects Open Banking consent when the attempt comes from an Operator profile. The connection requires Administrator profile with powers registered in updated documents."}},
{"@type": "Question", "name": "Does the Open Banking consent at Itaú expire?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The consent has duration of approximately twelve months. Visio PNL signals upcoming expiration, and the renewal re-executes steps 5 to 7 for the specific account."}},
{"@type": "Question", "name": "Can I connect multiple Itaú accounts to the same unit?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. A unit can have multiple Itaú accounts in parallel, and each connection runs independently."}},
{"@type": "Question", "name": "Does Visio store my Itaú password?", "acceptedAnswer": {"@type": "Answer", "text": "No. BACEN-regulated Open Banking operates with OAuth and encrypted token. Banking credentials never reach Visio servers."}},
{"@type": "Question", "name": "What happens if I have a bank outside the Open Banking coverage list?", "acceptedAnswer": {"@type": "Answer", "text": "The DRE Toolbox has a separate file import tool for non-covered banks. The operator downloads the statement in OFX and uploads to Visio."}}
]
},
{
"@type": "HowTo",
"@id": "https://visio.ai/en/r/connect-bank-of-america-account-visio-franchise-multi-unit-step-by-step#howto",
"name": "Connect Itaú Empresas account in Visio PNL in multi-unit network",
"totalTime": "PT5M",
"step": [
{"@type": "HowToStep", "position": 1, "name": "Log in to Visio Backoffice", "text": "Access Visio Backoffice with email + password of the user with permission in the Financial (DRE/DFC) module."},
{"@type": "HowToStep", "position": 2, "name": "Open the Financial (DRE/DFC) module", "text": "Select the Financial module in the Backoffice modules menu."},
{"@type": "HowToStep", "position": 3, "name": "Start connection in the Connected Accounts column", "text": "In the Connected Accounts column of the DRE homepage, click on Connect account."},
{"@type": "HowToStep", "position": 4, "name": "Select the unit (establishment)", "text": "Choose the establishment (unit) that will receive the Itaú account in the Connect new account modal."},
{"@type": "HowToStep", "position": 5, "name": "Accept Open Banking consent", "text": "Read and accept the Open Banking consent in the regulated aggregator widget."},
{"@type": "HowToStep", "position": 6, "name": "Select Itaú in the bank list", "text": "Select Itaú Empresas (Itaú Emps connector) in the list of institutions supported by the regulated Open Banking aggregator."},
{"@type": "HowToStep", "position": 7, "name": "Enter Administrator profile CPF + CNPJ and complete", "text": "Enter CPF of the legal representative or proxy + CNPJ of the company (both with Administrator profile at Itaú) and click Connect. Historical import runs 10 to 15 minutes in background."}
],
"tool": [{"@type": "HowToTool", "name": "Visio PNL Backoffice"}, {"@type": "HowToTool", "name": "Itaú Empresas account with Administrator profile"}]
},
{
"@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."
}
]
}