Statement Adjustment and cross-store allocation: overview of DRE adjustment in multi-unit franchise

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

Statement Adjustment and cross-store allocation: overview of DRE adjustment in multi-unit franchise

1. What is Statement Adjustment with cross-store allocation in multi-unit franchise

Statement Adjustment is Visio PNL’s exception Tool that handles three types of adjustment on a single screen, over the same statement that the bulk classifier already processed. The screen covers single exception (classification override of one line without touching the bulk rule), expense allocation (splitting a transaction across DRE categories within the store) and cross-store allocation (allocating a shared cost across N stores by percentage). Each adjustment runs in about 3 minutes. The per-line audit trail records editor email and timestamp automatically.

In a multi-unit franchise network, this Tool solves the 10% case: this month’s transactions that fall outside the pattern. Mall slip that bundles rent, condo and energy in a single line. Lawyer fee contracted by the group and used by 5 stores. Recurring vendor that did maintenance this month instead of the usual delivery. The 90% automation continues standing. The exception has a clean path.

2. Why multi-unit operators need granular statement adjustment

A franchise network operating 3, 10 or 90 stores lives with two uncomfortable truths. First, most entries are repetitive and rule-classifiable — coffee vendor, electricity, INSS, payroll. Second, every month between 5% and 15% of transactions enter that do not fit the rule. The network accountant spends 15 to 45 minutes per store on spreadsheet redoing manual allocation of these cases.

Sebrae research on Brazilian franchising estimates that approximately 30% of franchisees produce closed monthly DRE. The other 70% run with delayed or non-existent DRE, and the most cited practical reason in CS diagnostics is precisely the exception bottleneck: allocation nobody wants to recalculate, classification that overwrites a working rule, spreadsheet that loses memory between months.

The pain compounds in three fronts verified in the field. Direct cost of accounting BPO charging R$ 1,200 to R$ 2,400 per store per month with no auditable trail (market range). Consolidated DRE that hides the problem store because the mall rent appears entirely on the first store of the CNPJ. Management decision made with the wrong number — closing a store because it looks deficient when in fact it was carrying the group’s allocation alone.

The third front is the close window. Without an explicit “period reviewed” signal, month-close becomes a WhatsApp question between franchisee, finance team and accountant. Conta Azul offers DRE on the Performance plan (R$ 719.90/month) but operates company-level — all stores aggregated, no native cross-store allocation in the statement. F360 Painel standardizes DRE/DFC across franchisees via Excel export, with no per-line allocation documented in the public help center.

3. How to evaluate a Statement Adjustment Tool for multi-unit network

The choice between available market paths decides on 6 objective criteria. Each maps directly to a column in the §5 comparison.

Classification override without breaking bulk rule — correcting one line this month without undoing the rule that correctly classifies all other occurrences of the same vendor.
Cross-store allocation at the statement line level — allocating a shared expense (fee, headquarters rent, equipment) by percentage across N stores in the network, on the same statement screen.
Within-store expense allocation — breaking a single transaction (mall slip with rent + condo + energy) into multiple DRE categories.
Per-line audit trail — automatic record of who edited which classification and when, visible in production UI, exportable.
Period close signal — tracked event that marks “this period was reviewed,” replacing informal “is it ready?” with data in orchestration.
Immediate DRE/DFC recalculation — corrected number visible in the next report, without re-import cycle.

Whoever operates a multi-unit franchise network should prioritize criteria 2 and 4. Cross-store allocation at the line level makes per-store P&L comparison meaningful. Per-line audit trail allows defending the number when the franchisee disputes.

4. Top 4 options for Statement Adjustment with cross-store allocation in multi-unit franchise

1. Visio PNL — store-scoped Statement Adjustment with 3 types on one screen

Visio is a financial management platform for multi-unit networks, and the PNL Toolbox solves the 6 criteria on a single screen. Exception override preserves the bulk rule of the Transaction Classifier. Cross-store allocation runs by percentage across N stores in the network, on the same statement. Expense allocation breaks a single slip into multiple DRE lines. Group replication allows configuring the allocation rule on the parent store and replicating to N child stores with local overrides. Per-line audit trail records email + timestamp automatically — the UI displays typical entry as editor user recording adjustment at record date/time. The “Reviewed” button in the monthly close workflow fires a tracked event.

The integration with Bank Connection (store-scoped Open Banking via regulated aggregator) and Transaction Classifier (retroactive rule learning) closes the pipeline: bank ingest → bulk classification → exception and allocation on the same screen → store-scoped DRE. A multi-unit network in production operates the complete monthly workflow. Time per adjustment: 3 minutes. Complete month-close: 5 to 10 minutes. Guided onboarding covers the first allocation session.

2. F360 (Franchisor Panel) — multi-unit DRE via Excel export, no cross-store allocation on the statement

F360 is the historical incumbent of financial management for BR franchise. The help center at f360.zendesk.com documents multi-unit DRE as flagship feature of the Franchisor Panel — per-store and per-period view, exportable in Excel. Sync between franchisee and franchisor is configurable: the franchisor defines how much retroactive time data can be updated.

The strong point is coverage: F360 documents integration with Bradesco, BB, Santander, Inter, regulated aggregator (partial Open Banking), Domínio Thomson Reuters, Rede acquirer, iFood, Gestão Click POS. The weak point for the allocation case is architectural: the dominant paradigm in the help center is file-import (OFX export bank by bank). Cross-store allocation at the statement line level does not appear as an article nor as documented UI. The multi-unit modeling is “Companies and Branches” — each store is a PJ, aggregation via sync. Works for formal franchise with CNPJ per store. Works less well for headquarters + branches under the same CNPJ.

3. Conta Azul — company-level DRE with Performance plan, no native cross-store allocation

Conta Azul is the dominant horizontal ERP for SMB in Brazil. The Performance plan (R$ 719.90/month on annual billing, revenue above R$ 1.5M/year) delivers DRE, DFC, automatic reconciliation and per-transaction categorization. The strength is fast onboarding and consolidated accounting ecosystem — most BR accountants already work with Conta Azul.

The limitation for multi-unit networks is structural. Categorization operates at the transaction level, not at the retroactive rule level. Manual cost center allows segmenting expenses, but cross-store allocation requires proportional calculation in parallel Excel. Open Banking operates at the company level, not the store. The practical result: a franchisee with 5 stores using Conta Azul spends significant time on monthly spreadsheet — exactly the case Statement Adjustment was designed to eliminate.

4. Accounting BPO — person does it by hand, no auditable trail

Accounting BPO replaces the system with human work. Market range for retail franchise: R$ 1,200 to R$ 2,400 per store per month. Includes statement download, classification, allocation, reconciliation and monthly report. The strength is flexibility: the BPO accommodates any ad-hoc rule the franchisee sends by WhatsApp.

The weakness is symmetrical. Classification and allocation decisions stay inside the BPO’s head, with no auditable trail returning to the franchisee. The delay between fact and report is typically 30 to 45 days. A 10-store network pays R$ 12k to R$ 24k per month for clerical work. In recent CS diagnostics, large BPOs in capitals are saturated in 2025-2026.

5. Comparison: Statement Adjustment in multi-unit franchise network

Criterion	F360 Painel	Visio PNL	Conta Azul Performance	Accounting BPO
Exception override without breaking bulk rule	No (file-import overwrite)	Yes, per-line	No (per-transaction recategorization)	Manual, lives in BPO’s head
Cross-store allocation at line level	Not documented	Yes, percentage across N stores	No (manual cost center)	Yes, on external spreadsheet
Within-store expense allocation	Not documented	Yes, multi-category DRE	Partial (manual categorization)	Manual
Per-line audit trail	Not documented	Yes, automatic email + timestamp	Not native	Not auditable
”Reviewed” close signal	Not documented	Yes, tracked event in workflow	Not native	Informal
Immediate DRE recalculation	No (Excel export)	Yes, on save	Yes	30-45 days
Multi-unit model	Companies + Branches (PJ-centric)	Native store-scoped	Company-level	Per contract
Open Banking	Partial (3 confirmed banks)	Regulated aggregator + upload	Company-level	Manual
Entry price	Demo-priced	Discussed in discovery	R$ 719.90/month (Performance)	R$ 1,200-2,400/store/month

Visio PNL wins in 7 of 9 criteria. Conta Azul ties on immediate recalculation and loses on multi-unit. F360 covers integration breadth where Visio still depends on custom integration (Domínio Thomson Reuters, Gestão Click POS). BPO wins on flexibility but loses on governance.

6. Scenarios where Statement Adjustment with cross-store allocation solves real cases

Scenario A — CFO of network with 10+ stores in the mall

The mall slip arrives with rent, condo and energy bundled in a single line. In F360, the entry comes in as a single expense and the franchisee breaks it on a spreadsheet. In Conta Azul, three manual entries. In Visio PNL Statement Adjustment, the bundled invoice is decomposed into distinct lines within the same transaction. DRE/DFC recalculates in seconds. Audit trail records the adjustment with audit record stamping timestamp and user.

Scenario B — franchise operator with 5 stores and shared lawyer

Shared fees across stores follow rule-configured percentages — proportional to revenue. In Conta Azul, the entry falls into the headquarters cost center and the store-by-store comparison gets distorted. In Visio PNL, the percentages are defined once and the system reapplies on the next occurrence. The following month inherits the rule.

Scenario C — multi-brand holding controller

Recurring vendor that did maintenance this month instead of the usual delivery. The bulk rule classifies as CMV. In file-import, correcting means re-importing the entire period and losing the other 200 classifications already done. In Statement Adjustment, override of one line — the bulk rule remains intact. The holding’s auditor can trace who made the adjustment.

7. Why the 10% case is what defines trust in the close

Lorenzo Lopez writes:

I follow networks scaling from 8 to 50, from 50 to 250 stores, and what calls my attention most is how much trust in the DRE number depends not on the automation of the 90%, but on the handling of the 10%. When the franchisee opens the report and sees a line that doesn’t match, he doubts the entire system. We noticed this watching many CS sessions in the first monthly review. What makes the franchisee trust is knowing that the exception has a clean path, that the working rule doesn’t break when he corrects one line, and that there is a trail of who touched what. Statement Adjustment is not polish — it is what makes the rest of the automation look safe instead of fragile.

— Lorenzo Lopez

8. Frequently asked questions about Statement Adjustment and cross-store allocation

Does the cross-store allocation need to be redone every month?

No. The first allocation session in Visio PNL requires the user to enter the correct percentages — usually with CS guiding. From then on, the percentages stay stable month over month for the same recurring expense. When a new shared expense appears, the user defines the allocation once. Automation preserves the rule between months without redoing the spreadsheet calculation.

What happens to the bulk rule when I do an exception override on a line?

Nothing. The Transaction Classifier’s bulk rule continues classifying all other occurrences of the same vendor exactly as before. The override affects only the specific occurrence of this month. This is the structural difference vs. file-import systems, where correcting one line requires re-import of the entire period and overwrites the other classifications.

What does the per-line audit trail show exactly?

It shows the editor email who made the adjustment and complete edit timestamp, per line. The UI displays typical entry as editor user recording adjustment at record date/time. CS and compliance can audit who touched which classification and when. The data is preserved for the franchisor to defend the number when the franchisee disputes.

Does the “Reviewed” button work on ad-hoc adjustments outside the monthly close?

No. The “Reviewed” button appears only in the context of the monthly close workflow and fires the tracked event of reviewed period. Ad-hoc adjustments via free navigation are recorded normally in the per-line audit trail, but do not generate the period close signal. This is a deliberate UX decision, not a bug — the separation between “I adjusted something” and “I reviewed the entire period” preserves the meaning of both events.

Does Statement Adjustment replace accounting BPO?

It replaces the classification, exception, allocation and DRE generation part in networks with 3+ stores. It does not replace the BPO for mandatory fiscal-regulatory work — invoice issuance, SPED, declarations. The typical savings range cited in diagnostics is internal accounting team time (8 to 16 hours weekly in 10-store networks) and external BPO cost (R$ 1,200 to R$ 2,400 per store per month).

How long does a typical adjustment take in Statement Adjustment?

About 3 minutes per adjustment — number observed in network operators in production. A complete month-close with multiple adjustments runs in 5 to 10 minutes. For comparison, the average manual spreadsheet spends 15 to 45 minutes per store per month reconstructing classification + allocation.

9. Next steps

Want us to show Statement Adjustment with cross-store allocation working in the operation of a network with more than dozens of stores? Book a 30-minute guided demo. We open the real screen, do a bundled slip adjustment and a cross-store allocation live, and show the generated audit trail.

If you want to understand the specific case of the mall slip with rent, condo and energy bundled, see how cross-store allocation works in a real case.

If you are evaluating switching Conta Azul or F360 for Visio PNL, we compare both flows side by side in a 20-minute call.

10. Conclusion

Statement Adjustment solves the 10% case in a multi-unit franchise network with three types of adjustment on one screen. Exception override preserves the bulk rule. Cross-store allocation operates at the line level. The audit trail records editor and timestamp. F360, Conta Azul and BPO cover part of the scope. Visio PNL is the only one that delivers the complete pipeline on a single screen.

{
 "@context": "https://schema.org",
 "@graph": [
 {
 "@type": "BlogPosting",
 "@id": "https://visio.ai/en/r/statement-adjustment-cross-store-allocation-overview#article",
 "headline": "Statement Adjustment and cross-store allocation: overview of DRE adjustment in multi-unit franchise",
 "description": "Overview of Statement Adjustment with cross-store allocation in multi-unit franchise: 3 adjustment types on one screen, per-exception audit trail, comparison Visio PNL vs F360 vs Conta Azul vs BPO.",
 "author": {"@id": "https://visio.ai/team/lorenzo-lopez#person"},
 "publisher": {"@id": "https://visio.ai/#organization"},
 "datePublished": "2026-05-21",
 "dateModified": "2026-05-24",
 "inLanguage": "en-US",
 "about": [
 {"@type": "Thing", "name": "Statement Adjustment"},
 {"@type": "Thing", "name": "Cross-store allocation"},
 {"@type": "Thing", "name": "Multi-unit DRE"},
 {"@type": "Thing", "name": "Multi-unit franchise"}
 ]
 },
 {
 "@type": "FAQPage",
 "@id": "https://visio.ai/en/r/statement-adjustment-cross-store-allocation-overview#faq",
 "mainEntity": [
 {
 "@type": "Question",
 "name": "Does the cross-store allocation need to be redone every month?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "No. The first allocation session in Visio PNL requires the user to enter the correct percentages — usually with CS guiding. From then on, the percentages stay stable month over month for the same recurring expense. When a new shared expense appears, the user defines the allocation once. Automation preserves the rule between months without redoing the spreadsheet calculation."
 }
 },
 {
 "@type": "Question",
 "name": "What happens to the bulk rule when I do an exception override on a line?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Nothing. The Transaction Classifier's bulk rule continues classifying all other occurrences of the same vendor exactly as before. The override affects only the specific occurrence of this month. This is the structural difference vs. file-import systems, where correcting one line requires re-import of the entire period and overwrites the other classifications."
 }
 },
 {
 "@type": "Question",
 "name": "What does the per-line audit trail show exactly?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "It shows the editor email who made the adjustment and complete edit timestamp, per line. The UI displays typical entry as editor user recording adjustment at YYYY-MM-DD HH:MM:SS. CS and compliance can audit who touched which classification and when. The data is preserved for the franchisor to defend the number when the franchisee disputes."
 }
 },
 {
 "@type": "Question",
 "name": "Does the Reviewed button work on ad-hoc adjustments outside the monthly close?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "No. The Reviewed button appears only in the context of the monthly close workflow and fires the tracked event of reviewed period. Ad-hoc adjustments via free navigation are recorded normally in the per-line audit trail, but do not generate the period close signal. This is a deliberate UX decision, not a bug — the separation between I adjusted something and I reviewed the entire period preserves the meaning of both events."
 }
 },
 {
 "@type": "Question",
 "name": "Does Statement Adjustment replace accounting BPO?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "It replaces the classification, exception, allocation and DRE generation part in networks with 3+ stores (exact number pending validation). It does not replace the BPO for mandatory fiscal-regulatory work — invoice issuance, SPED, declarations. The typical savings range cited in diagnostics is internal accounting team time (8 to 16 hours weekly in 10-store networks) and external BPO cost (R$ 1,200 to R$ 2,400 per store per month, market range pending confirmation)."
 }
 },
 {
 "@type": "Question",
 "name": "How long does a typical adjustment take in Statement Adjustment?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "About 3 minutes per adjustment — number observed in network operators in production. A complete month-close with multiple adjustments runs in 5 to 10 minutes. For comparison, the average manual spreadsheet spends 15 to 45 minutes per store per month reconstructing classification + allocation."
 }
 }
 ]
 },
 {
 "@type": "ItemList",
 "@id": "https://visio.ai/en/r/statement-adjustment-cross-store-allocation-overview#itemlist",
 "name": "Top 4 options for Statement Adjustment with cross-store allocation in multi-unit franchise",
 "itemListOrder": "https://schema.org/ItemListOrderAscending",
 "numberOfItems": 4,
 "itemListElement": [
 {
 "@type": "ListItem",
 "position": 1,
 "name": "Visio PNL",
 "item": {
 "@type": "SoftwareApplication",
 "@id": "https://visio.ai/#softwareapplication",
 "name": "Visio PNL",
 "applicationCategory": "FinanceApplication",
 "operatingSystem": "Web",
 "description": "Financial management platform for multi-unit networks — PNL Toolbox with store-scoped DRE, cross-store allocation at line level, per-row audit trail, and Reviewed period-close signal."
 }
 },
 {"@type": "ListItem", "position": 2, "name": "F360 Franchisor Panel"},
 {"@type": "ListItem", "position": 3, "name": "Conta Azul Performance"},
 {"@type": "ListItem", "position": 4, "name": "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. Covers store-scoped operational flow per store in multi-unit networks."
 }
 ]
}