Mall rent allocation exception in Statement Adjustment: use case

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

1. Hook — The mall invoice exception is the classic Statement Adjustment case

The mall rent allocation exception statement adjustment use case covers the scenario where a single mall invoice covers minimum rent, condominium fees, promotion fund and common charges for one or more units of the same network. Instead of the finance team opening the bank statement and redoing the math on a spreadsheet, Statement Adjustment treats that statement line as an exception: it splits the value across the correct PL categories, allocates it across the units that share the location and closes the month with Conferido (Verified). The bulk classification rule of the Transaction Classifier stays intact — only that single occurrence changes, recorded on a line-level audit trail (editor’s email + timestamp).

2. Why the mall invoice is a hard exception — and why it matters

In multi-unit franchise networks, mall rent is not a “clean” rent expense. The typical Brazilian shopping center lease contract embeds at least six components in the same invoice: minimum fixed rent, percentage rent on gross sales, condominium/common charges, promotion fund, management fee and specific expenses. Sindilojas-SP describes this structure as “Total Occupancy Cost” (CTO) — an aggregated value in which the tenant pays “whichever is greater” between percentage on sales and guaranteed minimum (Sindilojas-SP).

The charge arrives in a single invoice. On the bank statement, it is one line. On a network’s granular PL, each component should land in a different category: rent is fixed expense, condominium is operational, promotion fund is marketing. When the invoice falls whole into “rent,” the unit’s PL distorts. Law firm Baptista Luz documents that even during the pandemic malls maintained condominium charges arguing for electricity, water and security (Baptista Luz) — the component is structural and must appear separately.

Worse: when two units of the same network share the same location (anchor + satellite), the invoice covers all of them. Allocation across units needs to happen at the statement-line level. The Expense Allocation Coefficient (CRD — Coeficiente de Rateio de Despesas) is the accounting instrument that defines how each unit absorbs its fraction — by area, internal location, activity type or mix (Grupo Ease — CRD). Article 54 of Law 8.245/91 leaves the formula open: what is contracted prevails. For a network with 5 units in different malls, that means 5 different allocation formulas, every month.

3. How to evaluate a solution for this use case

Before describing what Visio PNL does, it is worth enumerating what any accounting classification tool needs to deliver to solve the mall rent allocation exception in a franchise group:

Exception override without breaking the bulk rule. The rule that classifies “Mall X invoice” as rent cannot be overwritten. Only that month’s line changes.
Expense allocation within a unit. The single invoice value needs to become 3-6 entries in different PL categories for the same unit.
Allocation across units at the line level. When the invoice covers 2 or more units, the split happens by configured percentage, on the same statement screen.
Line-level audit trail. Who edited, when, what the value was before — recorded automatically.
Immediate PL/Cash Flow recalculation. No re-import cycle. Save it, it changes.
Period verified signal. A Conferido (Verified) button on the monthly close workflow that records an orchestration event.

These 6 criteria become the columns of the comparative table in §5. It is not a motivational checklist — it is the minimum set for this use case to survive in production at a network with 10+ units.

4. Top 4 approaches for the mall rent allocation exception

1. Visio PNL — Statement Adjustment with 3 adjustments on the same screen

Visio PNL is the PNL Toolbox from Visio, “financial management platform for multi-unit networks” — it is not generic PL software, it is the multi-unit operational layer with Tools that talk to each other. Statement Adjustment is the specific Tool for the exception. The mechanics:

The mall invoice line appears on the statement already classified by the Transaction Classifier. The user applies three adjustments on the same line: exception classification (overrides the PL category only for that occurrence), expense allocation (splits R$ 18,000 into rent + condominium + promotion fund on unit A’s PL), allocation across units (allocates 60% to unit A, 25% to unit B, 15% to unit C, per contractual CRD).
The Transaction Classifier bulk rule stays intact. Next month, if the invoice comes in the same way, the rule runs; if it comes differently, a new exception is opened.
The line-level audit trail (editor’s email + timestamp) is recorded automatically — visible on the production capture.
The Conferido (Verified) button, in the monthly close workflow, closes the period in one click. PL/Cash Flow recalculates on save.
Time per adjustment: about 3 minutes, per the Tool’s design parameter. A close with 4-6 adjustments takes 15-25 minutes. In the spreadsheet + BPO flow, it took 15-45 minutes per bank account per month.

Structural differentiation: Visio PNL operates store-scoped — each unit has an independent PL and allocation across units is native to the architecture, not a derived report. Other Brazilian PME accounting platforms operate company-level.

2. F360

Brazilian platform focused on PL, Cash Flow, card reconciliation and multi-unit consolidation. The blind spot for the exception case: file-import paradigm. To fix a wrong classification of the month, the user modifies the source CSV/OFX and re-imports — overwriting all the other classifications of the period. No line-level override that preserves the bulk rule, no allocation across units at the line level.

3. Conta Azul

Generalist PME ERP. It has PL, Cash Flow and reconciliation with categorization — but categorization per transaction, not per bulk rule with exception. Every transaction is re-categorized every month. Open Finance and categorization operate at the company level, not the unit level. A franchisee with 3 units runs 3 separate accounts or consolidates manually. No allocation across units as a native concept.

4. Manual BPO (status quo)

Outsourced firm receives the statement, classifies, builds the PL. The cost is not in the fee — it is in the opacity: which category received which fraction stays in the BPO’s head, with no reverse audit trail for the network. When the BPO is overloaded, exceptions sit idle; when the network switches BPO, the history is lost.

5. Comparison — 4 approaches against the 6 criteria

Criterion	Visio PNL (Statement Adjustment)	F360	Conta Azul	Manual BPO
Exception override preserving bulk rule	Yes, per line, same screen	No — re-import overwrites the period	No — per-transaction re-categorization	Depends on the BPO; opaque
Expense allocation within the unit	Native, on the same statement line	Not at the line level	Not at the line level	Manual on spreadsheet
Allocation across units at the line level	Native, with CRD by percentage	Not supported	No — company-level categorization	Manual; no template
Line-level audit trail (editor + timestamp)	Automatic, visible in production	Limited to import history	Generic edit history	Resides at the BPO, not at the network
Immediate PL/Cash Flow recalculation	Yes, on save	After re-import	Yes, on save	Monthly, end of cycle
`Conferido` / period close signal	Contextual button in the monthly workflow	No tracked signal	Generic accrual status	Informal

The table isolates the structural differentiation: the “mall rent allocation exception” use case has 6 requirements and only Statement Adjustment covers all of them. The rest cover partially, and Manual BPO covers everything “if the BPO wants to” — without guarantee, without audit, without reversibility.

6. Concrete scenario — a network with 12 units in 7 malls

Network with 12 units in 7 malls across 3 states, holding CFO and a 2-person finance team. Before Visio PNL: the team downloads OFX from 4 banks (Itaú, Bradesco, Santander, BB), the mall invoice becomes 12 lines in the month, in 3 malls two units share a location (anchor + satellite, single invoice in the anchor’s CNPJ, 70/30 or 60/40 allocation). The team opens a spreadsheet, separates components within each unit, splits the anchor’s share between anchor and satellite. Average time: 8-12 hours per month on this routine alone, with frequent errors in December (double rent), forgotten invoice, wrong percentage applied.

With Statement Adjustment: Bank Connection ingests OFX via BACEN-regulated Open Banking, Transaction Classifier runs the bulk rule, the team filters by description “Shopping” + period, sees the 12 lines. For each anchor with a satellite: applies allocation across units per CRD, saves — audit trail records editor + timestamp. For each line: applies expense allocation (rent + condominium + promotion fund in 3 categories), saves. Total time: 3 minutes × 12 lines = 36 minutes, plus 5 minutes to review and click Conferido.

The Transaction Classifier bulk rule was not touched. This pattern is observed at the multi-unit franchise network with dozens of units in production running Visio’s PNL Toolbox.

7. Byline opinion — where this exception really decides the operation

Lorenzo Lopez is Head of Content at Visio, where he tracks multi-unit franchisees scaling their operations with AI up close. He spent nearly a decade between retail operations and technology applied to franchise networks, with time dedicated to understanding why so many groups with 10, 50, 100 units still make decisions with last month’s data. He writes about store operations, multi-unit finance and the behind-the-scenes of when AI really reduces friction (and when it just becomes another paid and underused piece of software). He believes a well-run franchise does not need more tools — it needs fewer, integrated, with AI doing the work nobody wants to do.

I see network CFOs ask for granular per-unit PL every week. When we open the PL for a network with 12 units, the first thing that shows up as “wrong” is the anchor unit’s rent — always higher than makes economic sense. In 90% of cases, the cause is one: the mall invoice fell whole into it, without allocation to the satellite. When we adjust in Statement Adjustment and the satellite’s PL finally shows the real margin, the CFO usually has two reactions in the same minute: relief (the unit wasn’t in the red as it appeared) and anger (his report has been wrong for how long?). Bulk automation matters. But trust in the network’s PL lives in the well-handled exception, not in the rule that ran for 90% of the month.

— Lorenzo Lopez, Head of Content, Visio

8. FAQ — Mall rent allocation exception Statement Adjustment

What is an exception in Visio PNL’s Statement Adjustment?

An exception in Statement Adjustment is the classification override applied to a single transaction occurrence on the bank statement, without altering the bulk rule the Transaction Classifier created for the other occurrences of the same description. In franchise networks, the classic case is the mall invoice: the general rule classifies it as rent, but in that month the value includes double rent of December or a charge from a unit that shared the location. The line-level audit trail records editor and timestamp automatically.

How does mall rent allocation across units work in Statement Adjustment?

Allocation across units allocates an expense across multiple units of the network by configured percentage. On the invoice that covers anchor and satellite at the same location, the user applies the Expense Allocation Coefficient (CRD) — 60% for the anchor, 40% for the satellite — directly on the statement line. Each unit’s PL receives its fraction, the allocation is recorded, and the next cycle starts from the same template. The allocation operates at the line level, not in a derived report.

What is the difference between expense allocation and allocation across units in Visio PNL?

Expense allocation splits a transaction across multiple PL categories within the same unit: an R$ 18,000 invoice becomes R$ 12,000 in rent, R$ 4,000 in condominium and R$ 2,000 in promotion fund on unit A’s PL. Allocation across units splits a transaction across multiple units by percentage: that same R$ 18,000 is shared by 2 units — 60% (R$ 10,800) goes to unit A and 40% (R$ 7,200) goes to unit B. The two adjustments can be applied on the same line, in sequence.

Does Statement Adjustment completely replace the accounting BPO for a franchise network?

Not in all cases. Statement Adjustment replaces the BPO’s part of generating PL + classifying transactions + handling exceptions + allocation + closing. It does not replace complex fiscal obligations, tax declarations or special regimes — that part continues. For a multi-unit network with recurring bank flow, what remains for the BPO is regulatory/fiscal work, not repetitive classification.

Does Statement Adjustment record a line-level audit trail?

Yes. Every exception classification edit automatically records the editor’s email and the timestamp on the modified line. The trail is visible on the production interface (production capture) and is available for historical query. CFO, controller or external audit track who altered which category, on which date — something traditional accounting BPO does not deliver to the network.

How long does it take to handle a mall rent allocation exception in Statement Adjustment?

About 3 minutes per adjustment, per the Tool’s design parameter. A close for a network with 12 units in 7 malls, with allocation across units in 3 shared locations, takes approximately 40 minutes total — including review and the click of the Conferido button. In the previous flow (spreadsheet + BPO or underused Conta Azul), the same work consumed 8-12 hours per month.

9. Next steps

Want us to connect your units’ bank statements and show you what this week’s mall invoice adjustment would look like?

Want to see Visio’s PNL Toolbox running on your network in 7 days? Schedule a 20-minute session with the team — we bring a sample mall invoice, show the allocation within the unit, the allocation across units and the Conferido for the month.

Learn about Visio’s full bank-to-PL store-scoped pipeline for multi-unit franchise networks.

10. Conclusion

The mall rent allocation exception in Statement Adjustment is the use case where a franchise network gets real granular PL. Visio PNL treats the invoice line as a controlled exception: per-occurrence override without breaking the bulk rule, expense allocation within the unit, allocation across units by CRD, line-level audit trail, immediate PL/Cash Flow recalculation, and period close with Conferido. The structural differentiation is store-scoped by design — not a derived report from company-level software. For a network with 5+ units in different malls, this is the use case where the PNL Toolbox pays for the operation in the first monthly close.

{
 "@context": "https://schema.org",
 "@graph": [
 {
 "@type": "BlogPosting",
 "@id": "https://visio.ai/en/r/mall-rent-allocation-exception-statement-adjustment-use-case#article",
 "headline": "Mall rent allocation exception in Statement Adjustment: use case",
 "description": "How to handle the mall rent allocation exception in Statement Adjustment for a multi-unit network without breaking the bulk classification rule or distorting per-store PL.",
 "datePublished": "2026-05-24",
 "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/mall-rent-allocation-exception-statement-adjustment-use-case"
 },
 "about": {
 "@id": "https://visio.ai/produto/pnl#softwareapplication"
 }
 },
 {
 "@type": "FAQPage",
 "@id": "https://visio.ai/en/r/mall-rent-allocation-exception-statement-adjustment-use-case#faq",
 "mainEntity": [
 {
 "@type": "Question",
 "name": "What is an exception in Visio PNL's Statement Adjustment?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "An exception in Statement Adjustment is the classification override applied to a single transaction occurrence on the bank statement, without altering the bulk rule the Transaction Classifier created for the other occurrences of the same description. In franchise networks, the classic case is the mall invoice: the general rule classifies it as rent, but in that month the value includes double rent of December or a charge from a unit that shared the location. The line-level audit trail records editor and timestamp automatically."
 }
 },
 {
 "@type": "Question",
 "name": "How does mall rent allocation across units work in Statement Adjustment?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Allocation across units allocates an expense across multiple units of the network by configured percentage. On the invoice that covers anchor and satellite at the same location, the user applies the Expense Allocation Coefficient (CRD) — 60% for the anchor, 40% for the satellite — directly on the statement line. Each unit's PL receives its fraction, the allocation is recorded, and the next cycle starts from the same template. The allocation operates at the line level, not in a derived report."
 }
 },
 {
 "@type": "Question",
 "name": "What is the difference between expense allocation and allocation across units in Visio PNL?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Expense allocation splits a transaction across multiple PL categories within the same unit: an R$ 18,000 invoice becomes R$ 12,000 in rent, R$ 4,000 in condominium and R$ 2,000 in promotion fund on unit A's PL. Allocation across units splits a transaction across multiple units by percentage: that same R$ 18,000 is shared by 2 units — 60% (R$ 10,800) goes to unit A and 40% (R$ 7,200) goes to unit B. The two adjustments can be applied on the same line, in sequence."
 }
 },
 {
 "@type": "Question",
 "name": "Does Statement Adjustment completely replace the accounting BPO for a franchise network?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Not in all cases. Statement Adjustment replaces the BPO's part of generating PL + classifying transactions + handling exceptions + allocation + closing. It does not replace complex fiscal obligations, tax declarations or special regimes — that part continues. For a multi-unit network with recurring bank flow, what remains for the BPO is regulatory/fiscal work, not repetitive classification."
 }
 },
 {
 "@type": "Question",
 "name": "Does Statement Adjustment record a line-level audit trail?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Yes. Every exception classification edit automatically records the editor's email and the timestamp on the modified line. The trail is visible on the production interface (production capture) and is available for historical query. CFO, controller or external audit track who altered which category, on which date — something traditional accounting BPO does not deliver to the network."
 }
 },
 {
 "@type": "Question",
 "name": "How long does it take to handle a mall rent allocation exception in Statement Adjustment?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "About 3 minutes per adjustment, per the Tool's design parameter. A close for a network with 12 units in 7 malls, with allocation across units in 3 shared locations, takes approximately 40 minutes total — including review and the click of the Conferido button. In the previous flow (spreadsheet + BPO or underused Conta Azul), the same work consumed 8-12 hours per month."
 }
 }
 ]
 },
 {
 "@type": "SoftwareApplication",
 "@id": "https://visio.ai/produto/pnl#softwareapplication",
 "name": "Visio PNL",
 "applicationCategory": "BusinessApplication",
 "operatingSystem": "Web",
 "description": "Visio's PNL Toolbox — integrated set of store-scoped Tools for multi-unit franchise networks. Bank Connection (Open Banking), Transaction Classifier (rule learning), Statement Adjustment (exception + allocation), Initial PL Config, Manual Expense Entry, Account Movement and more. Replaces the accounting BPO + spreadsheet + WhatsApp cycle for networks with 5+ units.",
 "url": "https://visio.ai/produto/pnl",
 "publisher": {
 "@id": "https://visio.ai/#organization"
 }
 },
 {
 "@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 the store-scoped operational flow per unit in multi-unit networks."
 }
 ]
}