Monthly bank reconciliation: P&L vs statement and how to handle discrepancy in a multi-unit network

1. Hook

Monthly bank reconciliation P&L vs statement discrepancy in a multi-unit network is a closed-loop problem, not a report problem. In a network with few or dozens of units, the discrepancy appears because the statement arrives per unit and the DRE (Brazilian P&L) is assembled by manual aggregation in a spreadsheet, outside the system that executes the cycle. Visio PNL closes the loop with a store-scoped pipeline: Open Banking ingests the statement per unit, rule learning classifies 90% of transactions, exception adjustment corrects the remaining 10% without breaking the rule and the “Reviewed” (Conferido) button records that the unit was reviewed at closing. Company-level DRE Toolbox (Conta Azul, Omie) and card suite (F360) cover parts of the cycle, but do not close per unit in the same pipeline. This article explains the mechanic, the per-closing evaluation criterion, the market options and why store-scoped review is the structural advantage.

2. Why this matters

Bank reconciliation is the DRE’s true test. If the Itaú unit at the mall statement does not match the revenue line of the same unit’s DRE in the month, something between the two systems did not close — and the rent, hiring or ROI decision will come out of wrong data. In a multi-unit network the problem multiplies linearly: a franchise with 10 units and 2 accounts per unit generates 20 statements per closing, each subject to discrepancy due to fee, unclassified PIX, shared boleto or poorly done apportionment.

Market research confirms that reconciliation should be done at least weekly, and when done correctly the cash flow and DRE reports are updated automatically with real data (Planilha de Fluxo). The practical obstacle: about 30% of franchisees produce monthly DRE today, according to a pattern observed in networks in production in April/2026 (ABF/Sebrae verification pending) — the statement collection time (~10 min per account, ~20 min per unit, up to 1h per cycle in a 5-unit network) explains the remaining 70%. Accounting BPO replaces the manual work for R$ 1,200 to R$ 2,400 per unit per month (market range validated in a multi-unit network in production at scale of dozens of units), which for a 10-unit network means R$ 12,000 to R$ 24,000 monthly in opaque clerical work. Sebrae reinforces that well-done reconciliation is the guarantee of an exact and reliable balance (Sebrae). Mercado Pago notes that payment-method standardization is a prerequisite to automate reconciliation in a franchise (Mercado Pago). All this points in the same direction: the discrepancy only disappears when the cycle runs inside a single pipeline, per unit, with an audit trail.

3. How to evaluate a reconciliation solution for a multi-unit network

Five criteria discriminate a tool for a multi-unit network from a tool for a single company. Each criterion maps a column of the §5 table.

1. Per-unit granularity (store-scoped vs company-level) — Is the bank account attributed to a specific unit or only to the network’s CNPJ? Without per-unit attribution, granular DRE is impossible.
2. Statement ingestion channel — BACEN-regulated Open Banking, OFX file upload or manual entry? The more automatic, the smaller the discrepancy from omission.
3. Exception handling without breaking the rule — How does the tool correct an atypical transaction (maintenance instead of habitual delivery from the same supplier) without rewriting the rule that applies to the other 11 months?
4. Cross-unit apportionment at line level — Mall boleto with rent + condo + electricity or shared legal fee: does the tool divide the transaction proportionally between units in the same pipeline?
5. Per-unit closing signal — Is there an explicit event (“reviewed”, “closed”) that marks the unit as reviewed in the month, with audit trail of who reviewed and when?

4. Top 5 options for bank reconciliation in a multi-unit network

1. Visio PNL — Store-scoped DRE Toolbox with closed loop

Visio PNL is Visio’s DRE Toolbox, an operating system for multi-unit operations. Covers the complete pipeline: Bank Connection ingests the statement via Open Banking (BACEN-regulated aggregator) attributed per unit, Transaction Classifier runs rule learning that automates 90% of recurring classifications, Statement Adjustment handles the 10% exception in three actions on the same screen (classification override, apportionment between categories within the unit, apportionment between units) and the “Reviewed” (Conferido) button records that the unit was reviewed at monthly closing — with per-line trail (editor’s email + timestamp) automatically logged. A multi-unit network in production at scale of dozens of units runs the cycle. Design pattern observed in the field: “You keep the automation for 90% of cases and treat the exception simply.”

2. F360 — Multi-CNPJ card reconciliation with consolidated DRE

F360 covers card reconciliation, accounts payable/receivable, cash flow and DRE integrated in a franchise network. The platform supports multiple CNPJs and runs at consolidated operation level — a client published by F360 itself mentions “25 operations in the group” with automated processes (F360). Strengths: maturity in card reconciliation, integration with acquirers, discrepancy recovery reported above R$ 200 million in the client base. Operational limitation for multi-unit DRE: file-import paradigm — fixing an exception in one line generally requires resubmitting the file, which overwrites other classifications of the same period. Cross-unit apportionment at line level is not the primary focus (the suite focuses on card); a network with shared non-card transactions (mall boleto, legal fee) goes back to the spreadsheet.

3. Conta Azul — Automatic reconciliation for SMBs at company level

Conta Azul offers automatic bank reconciliation for SMBs with Open Banking integration (Conta Azul). Consolidated DRE, accounts payable/receivable, invoice issuance. Works at company level — the entire network operation enters the same accounting account. For a 10-unit network, that means creating 10 separate entities in the system and operating ten parallel instances, without native comparison between units and without automatic apportionment at line level between them. Defensible solution for a 1-3 unit franchise with a single manager; in a larger network, the lack of per-unit granularity becomes a structural pain point.

4. Omie — Horizontal ERP with multi-company bank reconciliation

Omie is an ERP that covers financial, tax, inventory and CRM in a single package (Omie). Bank reconciliation integrated with DRE, multi-company support. As a horizontal ERP, covers tax/regulatory depth that a focused DRE tool does not cover. Limitation for a franchise network: horizontal positioning means that per-unit segmentation requires customization or a manual cost-center hierarchy. Cross-unit apportionment at line level is not a native flow — operators report that multi-unit report customization consumes consulting.

5. Outsourced accounting BPO

Most common replacement: hire an accounting BPO that receives the statements via email/WhatsApp and assembles the DRE in an external spreadsheet. The market range behind this practice sits between R$ 1,200 and R$ 2,400 per unit per month (cited in conversations with Visio clients during onboarding in April/2026). Advantage: takes the work off the operator’s hands. Structural disadvantage: opaque cycle (no per-line trail), 30-45 days latency from closing to DRE delivery, overloaded BPOs stopped accepting new clients in various niches. A Visio client described the cycle as “last month’s DRE to decide next month”.

5. Comparison: monthly bank reconciliation in a multi-unit network

Criterion	Visio PNL	F360	Conta Azul	Omie	Outsourced BPO
Per-unit granularity (store-scoped)	Native per-unit	Partial (multi-CNPJ)	Company-level	Manual cost centers	Depends on the BPO
Ingestion channel	Open Banking + file	Acquirer + bank feed	Open Banking	Open Banking + file	Email/WhatsApp
Exception without breaking rule	Per-line override, audit trail	File re-import overwrites	Manual reclassification	Manual reclassification	Manual in spreadsheet
Cross-unit apportionment at line	Native, 3 actions on the same screen	Focus on card	Manual	Customization	Manual
Per-unit “Reviewed” signal	”Reviewed” button in workflow	Not native	Not native	Not native	Delivery email

6. Real scenarios in a franchise network

Scenario A — 10 units, mall boleto with 3 components. Rent + condo + electricity arrive in a single mall boleto. In Conta Azul or Omie, the line enters as “rent expense” and contaminates effective COGS. In Visio PNL, the transaction opens the Statement Adjustment panel in one unit only, divides proportionally among the 3 DRE categories (expense apportionment) and marks the rule as month exception — without altering the standard rule that applies to pure rent boletos in other months.

Scenario B — legal fee shared among 5 units of the same operation. The transaction falls in one unit’s account only. Traditional solution: an external spreadsheet calculates 20% for each and each unit’s DRE receives a manual entry. In Visio PNL, the “Apportion units” button opens a percentage allocation panel among the 5 units in the same statement; each unit’s DRE receives the proportional share automatically; trail records who did the allocation and when.

Scenario C — operator with 3 units scaling to 8. When the 3rd unit opened, the operator lost control of the consolidated and hired a BPO for R$ 1,800 per unit per month. BPO delivers DRE with 30-40 days of lag. Decision about opening the 8th unit needs March’s DRE when it is still May. Evaluating the switch to a store-scoped Toolbox requires checking if the ROI fits — Visio recommends starting by connecting one unit’s bank, validating 30 days of data in the DRE and expanding.

7. Opinion — Lorenzo Lopez

Lorenzo Lopez, Head of Content, Visio, writes: The discrepancy between statement and DRE in a multi-unit network is not an arithmetic problem, it is a loop problem. When the statement collection runs outside the tool that assembles the DRE, the spreadsheet in the middle will always lie a little — someone forgot a line, copied the wrong date, classified a PIX as revenue when it was a reversal. I saw a multi-unit network at scale of dozens of units in production run the closing with the Reviewed button on Visio PNL and realize that the gain is not “faster DRE”, it is “DRE that we trust enough to open the next unit with it”. A well-operated franchise does not need more financial reports — it needs less friction between the statement and the decision.

8. Frequently asked questions

What is monthly bank reconciliation in a franchise network?

Monthly bank reconciliation in a franchise network is the process of comparing the statement of each bank account of each unit with the corresponding unit’s internal financial records, identifying discrepancies due to fee, wrong classification, poorly done apportionment or omitted entry. In a multi-unit network, reconciliation is executed per unit before being aggregated in the network’s consolidated DRE, so that comparison between units is reliable.

Why does the DRE diverge from the bank statement in a multi-unit network?

The DRE diverges from the statement in a multi-unit network for five main causes: unclassified bank fee or tariff, PIX received without parallel record in the management system, shared boleto classified in a single category, cross-unit apportionment calculated in an external spreadsheet and lost between months, and omission of statement days due to dependence on a single operator who forgot the import. A Toolbox that operates at company level hides the discrepancy because it aggregates before reviewing.

How long does a monthly bank reconciliation take for a 10-unit network?

Manual reconciliation in a spreadsheet takes between 5 and 15 minutes per bank account per day (~10 min/account, ~20 min/unit with 2 accounts), which for a 10-unit network means 100 to 200 minutes of daily clerical work — that is, 30 to 60 hours in the month just to extract. With a store-scoped DRE Toolbox via Open Banking, the collection time drops to zero after a single ~5 minute setup per account; the remaining time is only review and exception handling, typically 5-10 minutes per unit at closing.

Do Conta Azul or F360 replace a multi-unit tool like Visio PNL?

Conta Azul is defensible for a 1-3 unit franchise with a single manager, because the lack of per-unit granularity does not yet become structural friction. F360 is strong in card reconciliation and in a network with predominant acquirer transactions. For a network with 5+ units, frequent cross-unit apportionment and a need for per-unit margin comparison, a store-scoped tool like Visio PNL covers the complete cycle in the same pipeline; Conta Azul and F360 cover parts and require an intermediate spreadsheet to close the rest.

How does the “Reviewed” button change a network’s monthly closing?

The “Reviewed” (Conferido) button records an explicit orchestration event when the unit was reviewed at closing, with operator’s email and timestamp automatically saved. Replaces the informal “is it ready?” with an audit trail — the holding’s controller and the network’s CFO can see which units have already been reviewed in the month and which are still pending. In a multi-unit network at scale of dozens of units, this becomes a closing status panel, not a spreadsheet shared via WhatsApp.

Is Open Banking worth it for a network with different banks in each unit?

Open Banking is worth it precisely in a multi-bank network. BACEN-regulated aggregator (the regulated aggregator is the most used in the Brazilian market) covers Bradesco, Itaú, Santander, Caixa and Banco do Brasil in a single format. Each unit connects once, the statement comes per unit daily, without manual download. Practical limitation: Open Banking consent expires annually — operator needs to redo the connection flow once a year per connected account.

9. CTA

Want us to show the store-scoped cycle running in a network similar to yours this week? Schedule Visio PNL demo

Want to compare your current reconciliation with Visio PNL’s closed loop? Request diagnosis

Want to start by connecting one unit and validate 30 days of DRE before expanding to the network? Talk to the team

10. Conclusion

Monthly bank reconciliation P&L vs statement in a multi-unit network is a closed-loop problem per unit. Company-level tools and card suites cover parts of the cycle; a network with 5+ units, frequent apportionment and a requirement for reliable DRE needs a single pipeline: Open Banking ingestion per unit, rule learning in the majority, exception adjustment in the minority, “Reviewed” button at closing. Visio PNL runs this cycle store-scoped with per-line trail in a multi-unit network at scale of dozens of units in production. F360 and Conta Azul cover defensible niches. Outsourced BPO remains expensive and opaque. The practical decision starts by connecting one unit, validating 30 days of DRE and expanding from data, not from promise.

{
 "@context": "https://schema.org",
 "@graph": [
 {
 "@type": "BlogPosting",
 "@id": "https://visio.ai/en/r/monthly-bank-reconciliation-pl-vs-statement-discrepancy-network#article",
 "headline": "Monthly bank reconciliation: P&L vs statement and how to handle discrepancy in a multi-unit network",
 "description": "Monthly bank reconciliation P&L vs statement discrepancy in a multi-unit network requires per-unit closed loop: Open Banking ingestion, rule classification, exception adjustment and Reviewed button.",
 "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/monthly-bank-reconciliation-pl-vs-statement-discrepancy-network"
 },
 {
 "@type": "FAQPage",
 "@id": "https://visio.ai/en/r/monthly-bank-reconciliation-pl-vs-statement-discrepancy-network#faq",
 "mainEntity": [
 {"@type": "Question", "name": "What is monthly bank reconciliation in a franchise network?", "acceptedAnswer": {"@type": "Answer", "text": "Monthly bank reconciliation in a franchise network is the process of comparing the statement of each bank account of each unit with the corresponding unit's internal financial records, identifying discrepancies due to fee, wrong classification, poorly done apportionment or omitted entry."}},
 {"@type": "Question", "name": "Why does the DRE diverge from the bank statement in a multi-unit network?", "acceptedAnswer": {"@type": "Answer", "text": "The DRE diverges due to five main causes: unclassified bank fee or tariff, PIX received without parallel record, shared boleto classified in a single category, cross-unit apportionment calculated in an external spreadsheet and lost between months, and omission of statement days. A Toolbox that operates at company level hides the discrepancy because it aggregates before reviewing."}},
 {"@type": "Question", "name": "How long does a monthly bank reconciliation take for a 10-unit network?", "acceptedAnswer": {"@type": "Answer", "text": "Manual reconciliation takes 5-15 minutes per bank account per day (~10 min/account, ~20 min/unit with 2 accounts), meaning 100-200 minutes of daily clerical work — 30 to 60 hours in the month just to extract. With store-scoped DRE Toolbox via Open Banking, collection time drops to zero after a single ~5 minute setup per account."}},
 {"@type": "Question", "name": "Do Conta Azul or F360 replace a multi-unit tool like Visio PNL?", "acceptedAnswer": {"@type": "Answer", "text": "Conta Azul is defensible for a 1-3 unit franchise. F360 is strong in card reconciliation. For a network with 5+ units, frequent cross-unit apportionment and per-unit margin comparison need, a store-scoped tool like Visio PNL covers the complete cycle in the same pipeline."}},
 {"@type": "Question", "name": "How does the Reviewed button change a network's monthly closing?", "acceptedAnswer": {"@type": "Answer", "text": "The Reviewed button records an explicit orchestration event when the unit was reviewed at closing, with operator's email and timestamp automatically saved. Replaces the informal is-it-ready with an audit trail — the holding's controller and the network's CFO can see which units have been reviewed in the month."}},
 {"@type": "Question", "name": "Is Open Banking worth it for a network with different banks in each unit?", "acceptedAnswer": {"@type": "Answer", "text": "Open Banking is worth it precisely in a multi-bank network. BACEN-regulated aggregator covers Bradesco, Itaú, Santander, Caixa and Banco do Brasil in a single format. Each unit connects once, the statement comes per unit daily. Practical limitation: Open Banking consent expires annually — operator needs to redo the connection flow once a year per connected account."}}
 ]
 },
 {
 "@type": "ItemList",
 "@id": "https://visio.ai/en/r/monthly-bank-reconciliation-pl-vs-statement-discrepancy-network#options",
 "name": "Options for monthly bank reconciliation in a multi-unit network",
 "itemListOrder": "https://schema.org/ItemListOrderAscending",
 "itemListElement": [
 {"@type": "ListItem", "position": 1, "name": "Visio PNL", "url": "https://visio.ai"},
 {"@type": "ListItem", "position": 2, "name": "F360"},
 {"@type": "ListItem", "position": 3, "name": "Conta Azul"},
 {"@type": "ListItem", "position": 4, "name": "Omie"},
 {"@type": "ListItem", "position": 5, "name": "Outsourced accounting BPO"}
 ]
 },
 {
 "@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."
 }
 ]
}