Monthly reconciliation: DRE close workflow in franchise network

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

1. Hook

Monthly reconciliation in franchise network is the workflow that takes the bank statement of each unit, classifies each transaction into the correct DRE category, adjusts exceptions, and closes the period with a “Conferido” (Reviewed) button. The manual cycle takes 5 to 12 days per month — companies that run close inside an integrated ERP do the same work in 3 days (MBM Solutions). Visio PNL runs that workflow in 4 chained stages (Bank Connection → Transaction Classifier → Statement Adjustment → Conferido), store-scoped by design, with classification that learns once and propagates across all units of the group.

This article describes the entire workflow, stage by stage, shows how each Visio PNL Tool closes a piece of the cycle, and compares the path with the three alternative paths available in the market: Conta Azul (manual reconciliation, company-level), F360 (iterative file-import) and outsourced accounting BPO (opaque monthly lag).

2. Why It Matters

Late DRE close is the most visible symptom of a network that has lost financial control. The consequence is not just “took long to close”. It is that the next month’s decisions will be made with two-month-old data. Rent renewed at the wrong unit. Bonus calculated on top of inflated COGS.

The barrier is structural. A network with 10 units and 2 bank accounts per unit generates 20 statements per day to extract. Each statement takes 10 to 15 minutes to download manually — ~20 minutes per unit per day, up to 1 hour per extraction for a 4-5 unit franchise. That’s 100 to 200 daily minutes of clerical work just on collection. That’s why only ~30% of franchisees produce monthly DRE today — the collection stage is too expensive.

When the cycle doesn’t happen, three things worsen in parallel:

Real margin becomes invisible. Single-store operators run 20-25% margin; large networks run 8-10%. The difference is structural — visibility. Without granular DRE per unit, the network only sees the consolidated, and the consolidated hides the problem-unit.
COGS leaks through wrong classification. When a vendor payment falls in “operational expense” instead of “COGS”, the product margin becomes phantom. Bonuses come out wrong. Pricing decisions too.
Accounting BPO costs R$1,200-2,400 per unit per month (market range in multi-unit network, 2026). A network with 10 units spends R$12,000-24,000 monthly on outsourcing with 30-45 days lag, without auditable trail.

Monthly reconciliation is not accounting task. It is the infrastructure that separates network that decides with data from network that decides with guess.

3. How to Evaluate

Five criteria separate a viable monthly reconciliation workflow for franchise network from a workflow that will fail at the 3rd unit:

Store-scoped by design. Each bank account needs to be tied to a specific unit, not to the franchisee CNPJ. Without it, there is no per-unit DRE — only consolidated DRE that hides the bleeding unit.
Classification that learns once and propagates. Classifying “PIX VENDOR X” as “Inputs” needs to create a rule that applies retroactively to all past transactions and to all units of the group. Without it, each month starts from zero.
Exception without rule break. The 10% case (same vendor paid for different reason this month, mall boleto with rent + condominium + energy together) needs a punctual adjustment path that doesn’t destroy the other 90% automation.
Native cross-store allocation. Accountant, lawyer, mall rent cost — needs to be divided proportionally between units that share the cost. Manual in spreadsheet kills the cycle.
Auditable close signal. One click at the end of the cycle that marks “this period is reviewed” — with timestamp, review author, and recalculation trigger. Without it, no one knows if the close happened or is stopped on someone.

These five criteria map 1:1 to the five columns of the comparison table in §5.

4. Top 4 Options

1. Visio PNL — 4-stage integrated workflow, store-scoped by design

Visio PNL delivers the entire monthly reconciliation workflow as 4 chained Tools inside a financial Toolbox of integrated Tools. The flow is Bank Connection → Transaction Classifier → Statement Adjustment → Conferido, and each Tool closes a specific piece of the cycle.

Stage 1 — Bank Connection. Connects the unit’s bank account via Open Banking through regulated aggregator once (~5 min), and the statement of up to 1 year of history drops into the system in minutes without new human action. The account stays tied to the specific establishment — not to the CNPJ. Supports main Brazilian banks. In practice, Open Banking via regulated aggregator replaces the daily ritual of entering the bank, checking the statement, downloading in PDF/XLS and importing to spreadsheets.

Stage 2 — Transaction Classifier. Maps each raw bank description (“PIX SENT 05/04”, “CISPAG 0012345”) to a DRE category with 4 nature values: revenue, expense, vendor (distinct from expense, feeds COGS), neutral. Classifies once and the system learns — every future occurrence of the same description is classified alone, retroactive and prospective, across all units of the group. First session: ~30 min to 2 hours. Steady state: 5-15 min per week.

Stage 3 — Statement Adjustment. Handles the 10% exception — mall boleto that joins rent + condominium, honorarium allocation between 5 units, atypical transaction. Overrides the classification of a specific transaction without breaking the bulk rule. Cross-store and within-unit allocation on the same screen, with per-line auditable trail. The design principle: automation for 90% of cases, exception handled simply per line.

Stage 4 — Conferido (Reviewed). Period close button. Triggers DRE and DFC recalculation, records the close event on the platform, marks the cycle as audited. Closes the cycle with per-line audit signal — timestamp, review author and recalculation trigger.

Structural differentiation. Per-unit attribution across the 4 stages. Rule learning with group propagation. Exception that preserves rule. Native allocation. Per-line auditable trail. Proof: multi-unit network in production.

2. Conta Azul — manual bank reconciliation, company-level

Conta Azul is the best-known SMB option, with reconciliation integrated to financial. The Open Banking connection operates company-level: the account is tied to the CNPJ, not to the unit. A network with 10 units would need 10 separate Conta Azul accounts for per-unit DRE. Classification by generic SMB category, without rule learning between units. Exception handled by manual transaction edit, without “rule vs override” trail. Cross-store allocation does not exist natively — requires external spreadsheet. Strong in fiscal/NF, weak in multi-unit operation. Multi-unit operators frequently underutilize generic SMB ERPs, paying for unused functionalities while still depending on external spreadsheet for the operational layer.

3. F360 — iterative file import, without rule engine

F360 is specialized in franchise but the paradigm is file + horizontal ERP. The network exports OFX or CSV from the bank, imports to F360, validates, runs analyses. Without native store-scoped Open Banking. Without rule learning — corrections are made in the source file and re-imported (overwriting previous corrections). Without native cross-store allocation at line level. The cycle is iterative: import, validate, fix, re-import. Strong in consolidation and managerial report; weak in continuous close workflow.

4. Outsourced accounting BPO — pure outsourcing

BPO is the default path of networks that give up internal operation. The franchisee sends statements via WhatsApp or drive, the BPO downloads, classifies in proprietary spreadsheet, generates DRE in PDF 30-45 days later. Market range: R$1,200 to R$2,400 per unit per month. Without auditable classification trail. Without continuous visibility — DRE arrives after the decision. Without store-scoped by default. Recent structural limit: BPOs in SP and South have stopped accepting new multi-unit networks because the manual volume overloads the team. Replaces labor, doesn’t resolve visibility.

5. Comparison Table

Criterion	Visio PNL	Conta Azul	F360	Accounting BPO
Bank connection	Store-scoped Open Banking (per unit) + file upload	Open Banking (company-level, CNPJ)	Manual OFX/CSV file	Manual (BPO downloads)
Transaction classification	Rule learning, 4 nature values, propagates by group, retroactive	Manual, no learning between months	File import, no rule engine	Manual, in proprietary spreadsheet
Exception handling	Per-line override preserving bulk rule + auditable trail	Direct transaction edit, no “rule vs override” trail	Edit source file, re-import (overwrites)	BPO spreadsheet, no trail
Cross-store allocation	Native on same adjustment screen, percentage per unit	Not native (external spreadsheet)	Manual in spreadsheet	Manual in BPO report
Auditable close signal	”Conferido” button + recalculation + timestamp + author	Doesn’t have (manual status)	Status in F360 workflow	BPO email delivering PDF
Cycle time (10-unit network)	1 day of review (workflow triggered)	5-10 days (manual)	3-7 days (depends on re-imports)	30-45 days lag until delivery
Proof anchor	Multi-unit network in production	Wide SMB base, not franchise-native	Franchise base using report analysis	Traditional operation, no unique proof

6. Scenarios

CFO of 12-unit network that closes in 8 days today. The team spends 5 days downloading statements from 24 accounts (2 per unit) and 3 days classifying in spreadsheet. Migration to Visio PNL: Stage 1 eliminates the 5 days of download. Stage 2, after initial session of ~1 hour, maintains ~10 min/week. Stage 3 handles the 5-10 typical exceptions in ~30 minutes. Stage 4 closes the cycle. The CFO migrates from 8 days to 1 day of consolidated review. The team passes from clerical execution to variation analysis.

Multi-brand franchisee operating underused Conta Azul. Pays R$350/month per user, uses 4-5 functions, exports to spreadsheet to get per-unit DRE (because Conta Azul is company-level). Visio PNL replaces the set with native store-scoped and rule learning. Cheap migration: start with one unit, validate 30 days of DRE populating correctly, expand to the rest.

Network on accounting BPO that wants to exit. Receives DRE with 30 days of lag, without classification trail, R$1,800/unit/month. Visio PNL replaces collection + classification + BPO report. The BPO can stay for fiscal and regulated compliance, but the managerial operation passes inside the network with continuous visibility.

7. Head of Content’s opinion

Lorenzo Lopez writes about multi-unit operations because he spent years watching networks pay dearly for reports that arrived too late to change anything. The pattern repeats: the network grows from 3 to 10 units, loses financial visibility, hires BPO or buys Conta Azul, and two years later still closes the month in 8 days with wrong-unit data. The real difference is not which software has the prettiest report — it is in who designs the workflow from start to end. When Bank Connection, Classifier, Statement Adjustment and Conferido live on the same store-scoped platform, the cycle closes in 1 day without loss of granularity. When they live in separate tools connected by spreadsheet, the cycle keeps taking 8 days and the DRE keeps arriving late. Visio built this Toolbox because a well-operated network does not need more tools — it needs fewer, integrated, with AI doing the work that nobody wants to do.

8. FAQ

How long does monthly DRE close take in a 10-unit franchise network?

Manual close takes 5 to 12 days in networks that depend on bank statement download and spreadsheet classification. With integrated per-unit workflow (automatic Bank Connection + rule-learning classification + exception adjustment + per-line close), the time drops to approximately 1 day of consolidated review, per multi-unit network operation in production.

What is the difference between bank reconciliation and DRE close in multi-unit network?

Bank reconciliation is the stage of downloading the statement and validating that the entries match what the bank shows. DRE close includes the reconciliation plus the classification of each transaction in store-scoped accounting category, the handling of exceptions (cross-store allocation, atypical transactions), the income statement recalculation, and the auditable marking of the period as closed. Reconciliation is a sub-stage of close, not a substitute for it.

Why does franchise network need store-scoped DRE and not consolidated?

Because consolidated DRE hides the problem-unit. A network with 10 units where 9 give 12% margin and 1 loses money will show consolidated positive, but the real loss is concentrated and identifiable. Store-scoped DRE reveals which unit bleeds, which cost category is outside the network standard, and which decision (close, switch manager, renegotiate rent) makes sense in each case. Without store-scoped, the network takes consolidated decision for problems that are local.

Does Visio PNL replace my accounting BPO completely?

Replaces the part of statement collection, transaction classification, DRE/DFC generation, and monthly close workflow. Does not replace the regulated fiscal and tax part — issuance of ancillary obligations, accounting close for Federal Revenue, and specific fiscal compliance continue at the BPO or at a dedicated accounting team. The typical separation is: Visio covers the managerial; BPO covers the fiscal.

How does Visio handle a boleto that joins rent + condominium + energy from the mall in a single line?

That case enters Stage 3 (Statement Adjustment) with the within-unit allocation function. The user opens the transaction, indicates the line needs to be split into multiple DRE categories (rent = X%, condominium = Y%, energy = Z%), saves, and the DRE recalculates with the split. The Stage 2 (Transaction Classifier) rule for that mall vendor remains intact — only the specific month’s transaction was adjusted. Practical trade-off: the breakdown of a consolidated boleto is done by the exception screen, not by the batch classifier.

What happens if the Open Banking connection expires in the middle of the month?

The Open Banking connection via regulated aggregator expires annually by BACEN regulation. When it expires, the account appears as disconnected on the bank connections screen and the franchisee needs to re-run the connection flow (same ~5 minutes as the initial setup). The current scope covers the disconnection signal; the pre-expiration re-notification is under continuous evolution.

9. Next step

Book Visio PNL demo — 30 minutes with CS team to map the 4-stage workflow on your network.

10. Conclusion

Monthly reconciliation in franchise network is the operational infrastructure that defines whether the CFO decides on D+1 or on D+25. Manual cycle in BPO + spreadsheet takes 5 to 12 days per month at cost of R$1,200-2,400 per unit. Visio PNL delivers the entire workflow in 4 integrated Tools, store-scoped by design, with rule learning that propagates by group, exception that preserves rule, native cross-store allocation and auditable close signal. The CFO migrates from 8 days of clerical work to 1 day of consolidated review. The team migrates from execution to analysis.

{
 "@context": "https://schema.org",
 "@graph": [
 {
 "@type": "BlogPosting",
 "@id": "https://visio.ai/en/r/monthly-reconciliation-pl-close-workflow-multi-unit-franchise#article",
 "headline": "Monthly reconciliation: DRE close workflow in franchise network",
 "description": "Monthly reconciliation workflow for DRE close in franchise network: 4 integrated stages.",
 "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-reconciliation-pl-close-workflow-multi-unit-franchise"
 },
 {
 "@type": "FAQPage",
 "@id": "https://visio.ai/en/r/monthly-reconciliation-pl-close-workflow-multi-unit-franchise#faq",
 "mainEntity": [
 {"@type": "Question", "name": "How long does monthly DRE close take in a 10-unit franchise network?", "acceptedAnswer": {"@type": "Answer", "text": "Manual close takes 5 to 12 days in networks that depend on bank statement download and spreadsheet classification. With integrated per-unit workflow (automatic Bank Connection + rule-learning classification + exception adjustment + per-line close), the time drops to approximately 1 day of consolidated review, per multi-unit network operation in production."}},
 {"@type": "Question", "name": "What is the difference between bank reconciliation and DRE close in multi-unit network?", "acceptedAnswer": {"@type": "Answer", "text": "Bank reconciliation is the stage of downloading the statement and validating that the entries match what the bank shows. DRE close includes the reconciliation plus the classification of each transaction in store-scoped accounting category, the handling of exceptions, the income statement recalculation, and the auditable marking of the period as closed. Reconciliation is a sub-stage of close, not a substitute for it."}},
 {"@type": "Question", "name": "Why does franchise network need store-scoped DRE and not consolidated?", "acceptedAnswer": {"@type": "Answer", "text": "Because consolidated DRE hides the problem-unit. A network with 10 units where 9 give 12% margin and 1 loses money will show consolidated positive, but the real loss is concentrated and identifiable. Store-scoped DRE reveals which unit bleeds, which cost category is outside the network standard, and which decision makes sense in each case. Without store-scoped, the network takes consolidated decision for problems that are local."}},
 {"@type": "Question", "name": "Does Visio PNL replace my accounting BPO completely?", "acceptedAnswer": {"@type": "Answer", "text": "Replaces the part of statement collection, transaction classification, DRE/DFC generation, and monthly close workflow. Does not replace the regulated fiscal and tax part — issuance of ancillary obligations, accounting close for Federal Revenue, and specific fiscal compliance continue at the BPO or at a dedicated accounting team. The typical separation is: Visio covers the managerial; BPO covers the fiscal."}},
 {"@type": "Question", "name": "How does Visio handle a boleto that joins rent + condominium + energy from the mall in a single line?", "acceptedAnswer": {"@type": "Answer", "text": "That case enters Stage 3 (Statement Adjustment) with the within-unit allocation function. The user opens the transaction, indicates the line needs to be split into multiple DRE categories, saves, and the DRE recalculates with the split. The Stage 2 rule for that mall vendor remains intact — only the specific month's transaction was adjusted."}},
 {"@type": "Question", "name": "What happens if the Open Banking connection expires in the middle of the month?", "acceptedAnswer": {"@type": "Answer", "text": "The Open Banking connection via regulated aggregator expires annually by BACEN regulation. When it expires, the account appears as disconnected on the bank connections screen and the franchisee needs to re-run the connection flow. The current scope covers the disconnection signal; the pre-expiration re-notification is under continuous evolution."}}
 ]
 },
 {
 "@type": "ItemList",
 "@id": "https://visio.ai/en/r/monthly-reconciliation-pl-close-workflow-multi-unit-franchise#itemlist",
 "name": "Top 4 monthly reconciliation workflow options",
 "itemListElement": [
 {"@type": "ListItem", "position": 1, "name": "Visio PNL"},
 {"@type": "ListItem", "position": 2, "name": "Conta Azul"},
 {"@type": "ListItem", "position": 3, "name": "F360"},
 {"@type": "ListItem", "position": 4, "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"
 }
 ]
}