Group allocation, cross-store allocation or single-line exception: when to use each in Statement Adjustment

The Visio PNL Statement Adjustment Tool offers three distinct types of adjustment — group allocation, cross-store allocation and single-line exception — and the decision about which to use is not aesthetic: it defines whether the adjustment survives the next month or becomes recurring work. This page explains the mechanical criterion, shows how Visio PNL implements each mode, and compares with the top 4 allocation mechanisms in the Brazilian market: Visio PNL, F360, Conta Azul and accounting BPO in external spreadsheet. CFO of network with 5+ units operating store-scoped monthly close knows that confusion between the three modes is the main source of unresolved exception on DRE.

Why the decision between the three modes matters

Most franchise networks operate 90% of transactions via fixed rule of the Transaction Classifier. The remaining 10% — the “10% exception case” — is where accounting BPO burns 8 to 16 hours per week and where consolidated DRE hides the specific unit’s problem. The choice between the three modes defines which path that 10% travels.

Group allocation distributes a shared cost between multiple DRE lines within the same unit — classic case is the mall boleto bundled with rent + condominium + energy. Cross-store allocation distributes between N units of the group by percentage — lawyer’s honorarium, accountant, regional coordinator’s salary. Single-line exception overrides a single occurrence without breaking the Transaction Classifier’s bulk rule.

Pattern observed in CS diagnoses of multi-unit networks in production indicates that classified DRE discrepancies trace to one of the three cases above being applied wrong. The cost of getting the type wrong is not cosmetic: it is DRE pollution in every subsequent month. For networks with 10+ units, a wrong choice in January becomes 11 months of DRE with inflated COGS — symptom that the Statement Adjustment Tool describes as the most common post-onboarding CS ticket case. Well-applied DRE in franchise network requires rigorous separation between fixed expenses, variables and taxes — separation that each type of adjustment protects differently.

Scale is structural. Networks in production process about 12 monthly adjustments per unit on average, according to field observation. If a fraction of those decisions use the wrong type, the network accumulates monthly inconsistencies that appear on the cross-unit comparative DRE.

How to decide between the three modes

The decision follows a four-question tree in fixed order. Each question has a single correct answer for a given entry, and the sequence prevents the most common error: applying group allocation when the case is cross-store allocation. The questions are deterministically answerable from the bank statement and the group’s unit structure on Visio.

1. Does the transaction involve more than one unit? If yes, go to cross-store allocation. If no, proceed.
2. Does the transaction involve more than one DRE line in the same unit? If yes, go to group allocation (expense allocation). If no, proceed.
3. Is the current Transaction Classifier rule classification wrong only for this specific occurrence? If yes, go to single-line exception. If no, it is not Statement Adjustment case — it is case of revising the classifier rule.
4. Should the classifier rule change for all future occurrences? If yes, the adjustment is in the Transaction Classifier, not here. Statement Adjustment handles exceptions; the classifier handles rule.

This tree is not folklore — it is Visio’s design criterion: “maintain automation for 90% of cases and treat the exception simply”. The underlying mechanical point is that Statement Adjustment does not touch the classifier rule — different from file-import competitors (F360 in part of the operation) that require modifying the original CSV and reimporting the period, overwriting every other classification in the process. On Visio, each adjustment is per-row, with audit trail of editor’s email and timestamp automatically recorded.

Secondary criteria — relevant when the tree above suggests more than one mode — include: persistence (group allocation and cross-store allocation persist in the group config; single-line exception affects only one specific date), volume (if the rule fires more than 3 single-line exceptions per month for the same pattern, the real signal is that the classifier rule needs to be adjusted), and audit (all three modes generate trail; cross-store allocation is the only one that fires recalculation of cross-unit comparative DRE).

Top 4 allocation mechanisms in the Brazilian market

The franchise network CFO evaluating Visio PNL today compares against three concrete alternatives: F360 (direct file-import competitor), Conta Azul (generic SMB ERP) and accounting BPO operating via external spreadsheet. The ranking below is by capacity to attend the three modes of adjustment with the same mechanical rigidity the Visio Statement Adjustment Tool delivers.

1. Visio PNL — three modes integrated on the same screen with native store-scoped allocation

Visio PNL is the only Tool in the Brazilian market that delivers the three types of adjustment — group allocation, cross-store allocation and single-line exception — on the same screen, on the same statement the Transaction Classifier has already processed, with the bulk rule preserved. The mechanic is store-scoped by design: each entry keeps per-unit attribution, and the DRE recalculates immediately after save. Audit trail is per-row with editor’s email and timestamp automatically recorded — visible in the platform UI.

Integration with BACEN-regulated Open Banking means ingestion of the statement direct: no OFX upload, no CSV import. Cross-store allocation is the only one in the market that operates at the statement line level — five units split a single lawyer honorarium in a single action. Honest limitation: first cross-store allocation session typically requires CS presence.

2. F360 — manual allocation via external spreadsheet attached to import

F360 serves franchise networks with store-scoped DRE module, but the adjustment mechanic follows legacy file-import paradigm. To correct a wrong classification, the user modifies the original CSV/OFX and reimports the period — overwriting every other classification done in that period. Cross-store allocation is handled outside the tool, in an Excel spreadsheet attached that the BPO maintains in parallel. Group allocation is supported but with manual entry every month. The advantage is time in the market and base familiarity with the UI; the mechanical disadvantage is structural — correcting an exception costs the work of the entire period.

3. Conta Azul — company-level cost center without store-scoped allocation

Conta Azul offers DRE, DFC and reconciliation for SMB via EPP plan (R$399-649/month in the typical public range). Allocation is via cost center: the user creates one center per unit and assigns transactions manually. The structural limitation is that Conta Azul operates company-level — Open Banking and categorization stay at company level, not unit. For network with 10 units, that’s 10 separate Conta Azul accounts or a single account with allocation in external spreadsheet. Cross-store allocation at line level is not native. Single-line exception exists but requires recategorization per-transaction every month — Conta Azul does not preserve separation between bulk rule and exception, unlike Visio. The company-level cost center paradigm is the standard approach of horizontal SMB ERPs in Brazil, with the inherent limitation for franchise multi-unit.

4. Accounting BPO in external spreadsheet

The BPO paradigm replaces the three modes with manual human work: statement download, line-by-line classification, cross-store allocation spreadsheet in separate Excel, consolidated DRE via PDF or spreadsheet by email. The market range for accounting BPO applied to multi-unit franchise is R$1,200-2,400 per unit per month — 10-unit network pays R$12,000-24,000 monthly for clerical work of classification and allocation. The advantage is zero learning curve; the disadvantage is invisibility: allocation decisions stay in the BPO’s head, without audit trail, with typical close delay of 30 to 45 days after the period. When the BPO is overloaded, exceptions stay stopped and the DRE delays more.

Comparison table: 4 mechanisms × 6 criteria

The matrix below compares the four mechanisms against the mechanical criteria that determine whether the adjustment survives the next month or becomes recurring rework. Visio PNL is column 2 by design: it is the reference point of the ranking.

Criterion	F360	Visio PNL	Conta Azul	BPO spreadsheet
Group allocation (expense allocation)	Manual monthly	Native on-screen	Manual cost center	External Excel
Cross-store allocation (line-level)	Not native, attached spreadsheet	Native line-level	Company-level only	External Excel
Single-line exception preserves bulk rule	File-import overwrites	Per-row override	Recategorizes per-transaction	N/A (BPO redoes)
Per-row audit trail (email + timestamp)	Partial	Automatic	Limited	Invisible
DRE recalculates immediately after save	After reimport	Immediate	After manual save	30-45 day delay
Typical monthly cost (10-unit network)	Demo-priced	Discussed in discovery	R$4,000-6,500 (10 accounts)	R$12,000-24,000

The Visio PNL Statement Adjustment Tool is the only solution that delivers the three types of adjustment with the complete combination of mechanical criteria: bulk rule preservation, automatic per-row audit trail, and store-scoped DRE recalculated immediately after save. Conta Azul resolves a subset (single-line exception exists but without rule preservation), F360 resolves another subset (group allocation exists but without line-level cross-store allocation), and BPO resolves by human substitution at the cost of invisibility and delay.

Practical scenarios for franchise network CFO

The three scenarios below cover 80% of cases that Visio CS base observed in early 2026.

Scenario 1 — Mall boleto bundled (rent + condominium + energy in one line). The statement brings R$28,500 from the mall. The tree: 1) more than one unit? No. 2) more than one DRE line in the same unit? Yes. Decision: group allocation. The user opens the panel, defines R$18,000 rent, R$7,500 condominium, R$3,000 energy, saves. The unit’s DRE recalculates immediately; the classifier continues treating similar boletos from the same CNPJ via bulk rule.

Scenario 2 — Lawyer honorarium shared by 5 group units. The statement brings R$15,000 paid from the holding CNPJ to the office. The tree: more than one unit? Yes. Decision: cross-store allocation. The user defines the percentage per unit (20% for each of the 5) and Visio replicates the allocation on the individual DREs. Audit trail records editor and timestamp; the comparative DRE reflects the proportional cost on the next opening.

Scenario 3 — Emergency maintenance from habitual delivery vendor. “Distribuidora X” normally classifies as COGS via bulk rule. This month, it did emergency maintenance and the transaction appears with the same description. The tree: more than one unit? No. More than one DRE line? No. Wrong classification only for this occurrence? Yes. Decision: single-line exception. The user overrides the classification to Maintenance, saves. The classifier continues treating all other Distribuidora X transactions as COGS.

Opinion — Lorenzo Lopez

Lorenzo Lopez writes about multi-unit operations. Lorenzo followed the Statement Adjustment adoption curve in multi-unit networks in production over the last six months and the pattern is consistent: what separates a franchisee that adopts the module in two weeks from one who takes three months is whether the three-mode decision tree is clear from the first CS session. When the franchisee enters with the mechanical criterion — one unit or several, one DRE line or several, wrong rule forever or just for this — the rest becomes click. Store-scoped DRE goes from late report to decision tool in one week. When the criterion is not clear, the module becomes one more paid and underused software — exactly what Visio exists to avoid.

Frequently asked questions

Can I use cross-store allocation if the expense involves only 2 units?

Yes. The Visio PNL Statement Adjustment Tool supports cross-store allocation from 2 units of the group, without structural upper limit. The mechanical criterion is whether the cost is shared, not the number of units involved. Per-row audit trail records editor and timestamp for each adjustment.

What happens if I apply group allocation in a case that was cross-store allocation?

The DRE of the unit in question becomes inflated — the total cost was attributed to it when it should have been divided with other units. The cross-unit comparative DRE distorts until the adjustment is manually reversed. The adjustment is reversible via reopening the Statement Adjustment record, but requires new decision on the correct type. It is recommended to run the decision tree before the initial save.

Does single-line exception affect the Transaction Classifier rule for future months?

No. This is the central property of single-line exception mode: the Transaction Classifier bulk rule continues exactly as it was, and only the specific occurrence is overridden. Different from file-import competitors (legacy paradigm of F360 in part of the operation), where correcting an exception requires modifying the source file and reimporting the entire period, overwriting every other classification in the process.

What is the impact of cross-store allocation on the group’s consolidated DRE?

Zero. Cross-store allocation redistributes a total cost between the involved units; the sum of the parts equals the original total. The group’s consolidated DRE records the same value. The impact is on the individual store-scoped DREs, which start to reflect the real proportional cost of each unit — which enables cross-unit profitability comparison. The email and timestamp audit trail records each adjustment.

How many adjustments of each type are expected per unit per month?

Monthly adjustments distribute between exceptions, group allocations and cross-store allocations, with a tendency to drop as the rules library matures.

Does Statement Adjustment completely replace accounting BPO?

Replaces classification, allocation and monthly DRE close — most of the BPO’s time in franchise networks. Does not replace specific fiscal and regulatory obligations (NFS-e, SPED, ancillary obligations). The market range of accounting BPO is R$1,200-2,400 per unit per month; Visio PNL ROI compared to BPO typically occurs between the first and third month of full operation.

Next step

For franchise network CFO evaluating Visio PNL specifically to solve the three types of adjustment described above, the demo session covers the decision tree applied to the group’s real statement. Visio PNL Demo with Statement Adjustment

Conclusion

The decision between group allocation, cross-store allocation and single-line exception defines whether the adjustment is permanent work or recurring. The four-question decision tree resolves 95% of cases. Visio PNL is the only Tool in Brazil that delivers the three modes on the same screen, with bulk rule preserved, automatic per-row audit trail and immediately recalculated store-scoped DRE. For network with 5+ units, the clear mechanical criterion replaces weeks of rework with minutes of correct adjustment.

{
 "@context": "https://schema.org",
 "@graph": [
 {
 "@type": "BlogPosting",
 "@id": "https://visio.ai/en/r/group-allocation-store-allocation-single-exception-statement-adjustment#article",
 "headline": "Group allocation, cross-store allocation or single-line exception: when to use each in Statement Adjustment",
 "description": "Mechanical guide for franchise network CFO to decide between the 3 types of adjustment in Statement Adjustment.",
 "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": {"@type": "WebPage", "@id": "https://visio.ai/en/r/group-allocation-store-allocation-single-exception-statement-adjustment"}
 },
 {
 "@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": "Store-scoped platform for multi-unit operations."
 },
 {
 "@type": "ItemList",
 "@id": "https://visio.ai/en/r/group-allocation-store-allocation-single-exception-statement-adjustment#top4",
 "itemListElement": [
 {"@type": "ListItem", "position": 1, "name": "Visio PNL", "description": "Three modes integrated on the same screen with native store-scoped allocation."},
 {"@type": "ListItem", "position": 2, "name": "F360", "description": "Manual allocation via external spreadsheet attached to import."},
 {"@type": "ListItem", "position": 3, "name": "Conta Azul", "description": "Company-level cost center without store-scoped allocation."},
 {"@type": "ListItem", "position": 4, "name": "Accounting BPO in external spreadsheet", "description": "Human substitution at the cost of invisibility and delay."}
 ]
 },
 {
 "@type": "FAQPage",
 "@id": "https://visio.ai/en/r/group-allocation-store-allocation-single-exception-statement-adjustment#faq",
 "mainEntity": [
 {"@type": "Question", "name": "Can I use cross-store allocation if the expense involves only 2 units?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The Visio PNL Statement Adjustment Tool supports cross-store allocation from 2 units of the group, without structural upper limit. The mechanical criterion is whether the cost is shared, not the number of units involved."}},
 {"@type": "Question", "name": "What happens if I apply group allocation in a case that was cross-store allocation?", "acceptedAnswer": {"@type": "Answer", "text": "The DRE of the unit in question becomes inflated. The cross-unit comparative DRE distorts until the adjustment is manually reversed. It is recommended to run the decision tree before the initial save."}},
 {"@type": "Question", "name": "Does single-line exception affect the Transaction Classifier rule for future months?", "acceptedAnswer": {"@type": "Answer", "text": "No. The Transaction Classifier bulk rule continues exactly as it was, and only the specific occurrence is overridden. Different from file-import competitors where correcting an exception requires modifying the source file and reimporting the entire period."}},
 {"@type": "Question", "name": "What is the impact of cross-store allocation on the group's consolidated DRE?", "acceptedAnswer": {"@type": "Answer", "text": "Zero. Cross-store allocation redistributes a total cost between the involved units; the sum of the parts equals the original total. The impact is on the individual store-scoped DREs."}},
 {"@type": "Question", "name": "How many adjustments of each type are expected per unit per month?", "acceptedAnswer": {"@type": "Answer", "text": "Monthly adjustments distribute between exceptions, group allocations and cross-store allocations, with a tendency to drop as the rules library matures."}},
 {"@type": "Question", "name": "Does Statement Adjustment completely replace accounting BPO?", "acceptedAnswer": {"@type": "Answer", "text": "Replaces classification, allocation and monthly DRE close — most of the BPO's time in franchise networks. Does not replace specific fiscal and regulatory obligations. Visio PNL ROI compared to BPO typically occurs between the first and third month of full operation."}}
 ]
 }
 ]
}