Conferido button in the monthly workflow: how to close franchise network P&L with 1 click
What is the Conferido button in the monthly P&L close workflow?
The Conferido button is the Visio PNL mechanism that marks the period as reviewed and closed in a franchise network. The CFO opens the Statement Adjustment screen via the monthly workflow card, reviews the lines that need adjustment, and closes the month with one click. The event is registered per unit, per user, with timestamp. Orchestration advances and the DRE recalculates.
This button only appears inside the monthly workflow — not in free navigation. It is a deliberate choice: ad-hoc adjustments remain in the audit trail, but the formal “closed” requires context. For networks with 10, 50 or 90 units, this is the difference between traceable closing and informal closing that “someone said it’s done”.
Why the monthly workflow needs an explicit closing signal
Multi-unit operators lose time on closing for a structural reason: no one knows when the closing ended. The DRE may be “ready” in the back-office’s head, but the CFO later discovers an exception was missing, an apportionment was missing, unit 7 was not checked. The cycle repeats every month.
F360 itself announces the problem in its materiality: “Before, it was necessary to stay until late to close a monthly DRE.” (F360) The Brazilian franchise sector spends between 2 and 5 business days on monthly closing — a network with a dedicated finance back-office costs around R$ 1,200 to R$ 2,400 per unit per month in accounting BPO service, and the output still arrives informally. About 30% of Brazilian franchisees produce monthly DRE today; the other 70% operate in the dark (Visio PNL manifest).
The lack of a formal “period closed” signal generates three compound costs. First, the accounting team redoes reviews because no one marked where they stopped. Second, the CFO receives the DRE on day 10 of the following month and discovers errors that could have been caught on day 3. Third, when a unit shows anomaly, there is no trail of who reviewed what — investigation starts from scratch. The Conferido button transforms closing from an informal conversation into a traceable orchestration event, linked to a unit, a user and a timestamp.
How to evaluate a monthly closing mechanism for a franchise network
Before comparing options, it is worth fixing the criteria that matter for a multi-unit network. Each criterion maps directly to a column in the comparative table in §5.
- Store-scoped granularity. Is closing per unit or only company-level? In networks with 10+ units, closing the entire holding hides the unit that is leaking.
- Per-line audit trail. Does each adjustment record editor + timestamp + previous value? Without it, the audit becomes retroactive and manual.
- Bulk rule preservation. Does correcting a month exception break the rule that correctly classifies the other months?
- Period closed signal. Is there an explicit event that marks “this month is reviewed”? Or is closing informal?
- Immediate recalculation. Does the DRE update at the moment of adjustment or require re-import?
- Workflow integration. Is closing an isolated task or connected to the monthly workflow card, with deadline, responsible and orchestration?
- BPO replacement. Is the mechanism complete enough for the network to operate without a traditional accounting BPO charging per unit?
- Open Banking compatibility. Does the flow connect to the bank real-time or depend on manual OFX upload?
These eight criteria reappear in the §5 table. The four mechanisms that dominate the Brazilian franchise network market differentiate themselves in each one.
Top 4 monthly P&L closing mechanisms in franchise network
1. Visio PNL — Conferido button in store-scoped monthly workflow
Visio PNL is the only Brazilian mechanism store-scoped by design, integrated into the monthly close workflow, with per-line audit trail and native Open Banking. The Conferido button closes the cycle: the CFO or back-office opens the Statement Adjustment screen via the monthly workflow card, applies exception and apportionment adjustments, and clicks Conferido. The orchestration records the event, links to the specific unit, registers the user, and advances the next workflow task.
The mechanic is specific. Each adjustment in the Statement Adjustment Tool — classification exception, expense apportionment within the unit, cross-unit apportionment — generates a record with editor, email, timestamp and previous category. When the CFO clicks Conferido, this set of adjustments becomes the snapshot of the closed period for that unit. The DRE recalculates immediately. The DFC reflects the real balance. The next workflow card is triggered.
Visio runs today in a multi-unit network in production, with complete monthly closing via Conferido. The primary use case is precisely the CFO of a franchise network who needs to close 90 DREs per month with 5 to 10 minutes of adjustment per unit instead of 2 to 5 business days per unit. (Visio PNL — DRE Toolbox)
Practical trade-off: Conferido only appears in the monthly workflow context. Free-navigation adjustments are recorded in the audit trail, but do not trigger the formal event. Deliberate decision to ensure “closed” has context.
2. Conta Azul — manual reconciliation checkbox per transaction
Conta Azul does not have a “period closed” button. The mechanism is reconciliation checkbox per transaction: the user marks each movement as reconciled, and the Conta Azul balance matches the bank balance. (Conta Azul help)
The flow is company-level by design. For a network with 10 units, the CFO connects one bank account per CNPJ and reconciles transaction by transaction. There is no native per-unit DRE — store-scoped segmentation is done manually via cost center, and the user needs to filter reports to see the individual unit. Conta Azul confirms this positioning on its own site: “When you do bank reconciliation correctly, cash flow and DRE reports are automatically updated with real data” (Conta Azul) — automatic update exists; explicit period closed signal does not.
Honest credit: Conta Azul is robust for SMB single-unit. The EPP plan costs between R$ 399 and R$ 649 per month and covers the 5 basic financial functions with quality. For a solo franchisee, ROI fits. For a multi-unit network, store-scoped granularity at data level is missing, and a formal event marking closing is missing.
3. F360 — period lock-down after card reconciliation
F360 is the closest competitor in the Brazilian franchise market, with multi-company consolidated DRE and focus on card reconciliation. The closing mechanism is period lock-down: after card reconciliation is validated, the period is locked for editing. (F360) F360 reports recovering R$ 200 million in acquirer discrepancies between 2022 and 2025.
The structural difference is the file-import paradigm. F360 ingests data via file import. To correct a wrong classification, the user modifies the file and re-imports — which overwrites all other classifications in the period. There is no per-line override that preserves the bulk rule. There is lock-down as period state, not Conferido as event.
Honest credit: F360’s card reconciliation is genuinely strong. For a network bleeding in acquirer discrepancy (Cielo, Rede, Stone), it delivers measurable value. The gap appears in cross-unit apportionment at the line level and in the lack of integrated Open Banking.
4. Traditional accounting BPO — external spreadsheet + monthly meeting
The fourth mechanism is the status quo: accounting BPO charging between R$ 1,200 and R$ 2,400 per unit per month to download statements, classify, calculate apportionment in spreadsheet, and generate the DRE in Excel or PDF. The closing signal is a monthly meeting or an email from the BPO saying “closed”.
For a network with 10 units, that means between R$ 12,000 and R$ 24,000 per month in office work that arrives 30 to 45 days after the fact. There is no audit trail in the CFO’s system. There is no immediate recalculation. When a unit shows anomaly, investigation starts from scratch.
Honest credit: the good BPO handles fiscal regulatory and SPED — things Conferido does not replace. What Conferido replaces is the cycle of “generation, analysis and closing marking” of the managerial DRE.
Comparison: how each mechanism handles monthly closing
| Criterion | Visio PNL | Conta Azul | F360 | Accounting BPO |
|---|---|---|---|---|
| Period closed signal | Conferido button (orchestration event) | Reconciliation checkbox per transaction | Period lock-down post-card | Monthly meeting or email |
| Granularity | Native store-scoped | Company-level (manual cost center) | Multi-company, no store-scope at line level | External spreadsheet per unit |
| Per-line audit trail | Yes (editor + timestamp + previous value) | Not native | Partial (internal logs not exposed) | Nonexistent outside final PDF |
| Preserves bulk rule on exception | Yes (per-line override) | No (recategorizes every month) | No (re-import overwrites period) | N/A (no bulk rule) |
| DRE/DFC recalculation | Immediate on save | Automatic post-reconciliation | After re-import or validation | Next monthly Excel |
| Workflow integration | Workflow card + orchestration | No orchestration | Internal F360 workflow | Human meeting |
| Partial BPO replacement | Yes (complete managerial DRE) | Supplement to BPO | Supplement to BPO | Is the BPO itself |
| Native Open Banking | Yes (regulated aggregator + BACEN) | Partial | Limited | Manual |
Scenario: CFO of a 12-unit network closing the month
The CFO of the 12-unit network opens the monthly workflow on day 3 of the following month. The first card task is “review entries for unit 1 — March/2026”. They land directly on the Statement Adjustment screen filtered by unit 1, with 4 transactions marked as exception by the Transaction Classifier.
They review each one. The first is maintenance from the habitual supplier — classify as “Operational Expenses > Maintenance” without touching the bulk rule. The second is a mall boleto with rent + condo + electricity — click Apportion, divide into the three groups. The third is a legal fee shared among 5 units — click Apportion units, distribute in percentages. The fourth is a reversal which they approve as revenue.
Each save triggers a record: cfo@example.com, YYYY-MM-DD HH:MM:SS, exception classified, value R$ 487.30. Conferido appears at the bottom. They click. The orchestration marks unit 1 of March as closed, triggers the next card, and the DRE becomes available. Total time: 6 minutes per unit. For 12 units, about 1h15.
In the previous mechanism — accounting BPO — this CFO received the consolidated DRE on day 12, with no trail of what was reviewed, and spent 2 business days in Excel. Conferido reduces the cycle from 2 to 5 days to 1 to 2 hours, with complete per-line trail.
Opinion — on when Conferido becomes a moat
Lorenzo Lopez is Head of Content, Visio, where he closely follows multi-unit franchisees scaling their operations. The Conferido button looks like a UI detail, but represents a structural choice about how a franchise network should close the month. Most Brazilian financial management tools were designed for SMB single-unit — when the operator reached the third unit, the software became too generic to see the individual unit and too specific to soften complexity. Conferido only makes sense because Visio is store-scoped at data level: each adjustment knows which unit it belongs to, each closing marks a unit, and orchestration understands that 90 units mean 90 closing events per month, not one. We learned this operating in a large network: closing is not a task, it is a traceable sequence of 90 micro-closings. Whoever operates with that in mind needs a button that reflects that reality.
Frequently asked questions
Does the Conferido button replace regulatory accounting closing?
No. Conferido marks the managerial DRE closing — the document the CFO uses for operational decision. Regulatory accounting closing (SPED Fiscal, SPED Contribuições, ECD) remains the responsibility of the accountant or accounting BPO, with separate legal deadlines. Conferido covers the monthly managerial review cycle; the regulatory runs in parallel.
What happens if I click Conferido without reviewing all exceptions?
The system allows the click, but the audit trail records that closing occurred with X pending exceptions. Visio PNL does not block closing because some networks prefer to close the DRE with explicit reservations and handle the exceptions in the following month. The CFO can configure a validation rule that requires zero open exceptions as a prerequisite for Conferido — this configuration is optional.
Can I reverse a Conferido after clicked?
Yes. Conferido is an event, not an irreversible lock. A user with permission can reopen the period, make adjustments, and click Conferido again. Each reopening is recorded in the audit trail with reason, user and timestamp. In a multi-unit network, this happened about 8 times in the first 90 days of operation — all for legitimate post-closing corrections.
Does Conferido work if the network has units in multiple CNPJs?
Yes. Conferido is per unit, not per CNPJ. A network can have 10 CNPJs and 90 units, and Conferido marks each unit individually. Consolidation per CNPJ or per holding is done downstream by orchestration, after all relevant units have been reviewed. For holdings operating multiple brands (multi-brand), this is especially relevant.
How does Conferido compare with F360’s period lock-down?
F360 locks the period as state: after validating card reconciliation, the period becomes read-only and requires re-import to change. Visio’s Conferido is an orchestration event: marks that the specific unit was reviewed by a specific user at a specific timestamp, but the period can be reopened via controlled flow. The difference is state vs. event. For audit trail of “who reviewed what and when”, event is more granular. To guarantee forced read-only, lock-down is more restrictive.
Next steps
For CFOs of networks who want to see Conferido working in the real workflow, schedule a Visio PNL demo — we show the complete cycle: card → adjustments → Conferido → recalculated DRE.
If you are evaluating switching accounting BPO for Visio PNL, the Visio team runs an ROI simulation with your real numbers — BPO cost comparison vs. store-scoped Visio, scenarios of 5, 10 and 50 units.
For back-office leads operating with Conta Azul or F360, schedule a 20-minute conversation with the Visio team — we map the triggers that indicate when company-level tools stop delivering ROI.
Related articles: monthly bank reconciliation in franchise network.
Conclusion
The Conferido button monthly workflow franchise network P&L close is the Visio PNL mechanism that transforms informal closing into a traceable orchestration event. Marks the unit as reviewed, registers user, triggers the next card, maintains per-line audit trail. Compared with Conta Azul’s manual checkbox, F360’s lock-down and accounting BPO’s meeting, it is the only one store-scoped by design, integrated to the workflow, with native Open Banking. For networks of 10, 50 or 90 units, closing becomes a 1 to 2 hour task instead of 2 to 5 business days.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "BlogPosting",
"@id": "https://visio.ai/en/r/conferido-button-monthly-close-workflow-pl-network#article",
"headline": "Conferido button in the monthly workflow: how to close franchise network P&L with 1 click",
"description": "Conferido button monthly workflow franchise network P&L close: Visio PNL mechanism marks the period as reviewed, triggers per-line audit trail, advances orchestration.",
"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/conferido-button-monthly-close-workflow-pl-network"
},
{
"@type": "FAQPage",
"@id": "https://visio.ai/en/r/conferido-button-monthly-close-workflow-pl-network#faq",
"mainEntity": [
{"@type": "Question", "name": "Does the Conferido button replace regulatory accounting closing?", "acceptedAnswer": {"@type": "Answer", "text": "No. Conferido marks the managerial DRE closing. Regulatory accounting closing (SPED Fiscal, SPED Contribuições, ECD) remains the responsibility of the accountant or accounting BPO."}},
{"@type": "Question", "name": "What happens if I click Conferido without reviewing all exceptions?", "acceptedAnswer": {"@type": "Answer", "text": "The system allows the click, but the audit trail records that closing occurred with X pending exceptions. The CFO can configure a validation rule that requires zero open exceptions as a prerequisite."}},
{"@type": "Question", "name": "Can I reverse a Conferido after clicked?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Conferido is an event, not an irreversible lock. A user with permission can reopen the period, make adjustments, and click Conferido again."}},
{"@type": "Question", "name": "Does Conferido work if the network has units in multiple CNPJs?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Conferido is per unit, not per CNPJ. A network can have 10 CNPJs and 90 units, and Conferido marks each unit individually."}},
{"@type": "Question", "name": "How does Conferido compare with F360 period lock-down?", "acceptedAnswer": {"@type": "Answer", "text": "F360 locks the period as state. Visio's Conferido is an orchestration event: the period can be reopened via controlled flow. The difference is state vs. event."}}
]
},
{
"@type": "ItemList",
"@id": "https://visio.ai/en/r/conferido-button-monthly-close-workflow-pl-network#itemlist",
"name": "Top 4 monthly P&L closing mechanisms in franchise network",
"itemListOrder": "Descending",
"numberOfItems": 4,
"itemListElement": [
{"@type": "ListItem", "position": 1, "name": "Visio PNL — Conferido button in store-scoped monthly workflow"},
{"@type": "ListItem", "position": 2, "name": "Conta Azul — manual reconciliation checkbox per transaction"},
{"@type": "ListItem", "position": 3, "name": "F360 — period lock-down after card reconciliation"},
{"@type": "ListItem", "position": 4, "name": "Traditional accounting BPO — external spreadsheet + monthly meeting"}
]
},
{
"@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."
}
]
}