Step 4 Statement Adjustment: exceptions, apportionment and Reviewed in monthly closing

Step 4 of Visio PNL onboarding

Step 4 statement adjustment exceptions onboarding workflow PNL is the step that handles the 10% of transactions that do not fit in the Transaction Classifier’s bulk rule. Happens after Bank Connection (step 1), Transaction Classifier (step 2) and Initial DRE Config (step 3), closing the 4-step pipeline of Visio’s PNL Toolbox. In a single screen, the multi-unit operator overrides the category of an atypical transaction, apportions an expense between multiple DRE categories or allocates a shared cost between multiple units — without breaking the rule that automates the other 90% of the month. About 3 minutes per adjustment; 5 to 10 minutes for full monthly review; one click on the Reviewed button closes the cycle.

Without this step, the 10% pollute the DRE forever. A wrongly classified transaction in January remains wrong in February, March and April, because the classifier operates by description and does not know the exception. A mall rent that came in a single boleto with condo and electricity disappears in the wrong P&L line. A lawyer fee paid by one unit, but owed by the five in the group, distorts the comparative margin. The network with dozens of units in production only runs clean monthly closing because step 4 handles each exception without rewriting the classifier.

Why this step exists (and why the file-import paradigm fails here)

About 90% of transactions in franchise network repeat month to month — same supplier, same description, same chart of accounts. The other 10% do not repeat. The habitual supplier did maintenance instead of delivery. The mall administration sent single boleto bundling rent + condo + electricity. The accountant apportioned fee between five units. Each of these lines needs individual treatment — and none fits in the rule that serves the other 90%.

File-import tools (F360 and SMB ERPs) handle exception with the wrong paradigm. To correct a line, the operator exports the file, edits the category and reimports — and the reimport overwrites all the period’s classification. Result: either the error passes, or 90% of the work is redone to fix 10%. Cortex Intelligence’s analysis on COGS reinforces that non-COGS operating expenses (rent, marketing, salaries) need independent classification — exactly the friction point in network with shopping mall.

Cross-unit apportionment has regulatory weight. Migalhas’ article on mall expense apportionment cites Civil Code article 1,336 (“in proportion to ideal fractions”) and the Tenancy Law (Law 8,245/91, article 23, XII) as legal basis for the Coefficient of Expense Apportionment (CRD). When shared cost falls 100% on one unit, its margin disappears, the others inflate, and the decision about which unit to close or expand becomes guess. The accounting mapping of DRE Group described by Bluesoft makes explicit that each account needs to be attributed to a P&L line to enter the calculation — poorly handled exception disappears from the right group and appears in the wrong one.

How to evaluate an exception handling and apportionment tool in DRE closing

Not every statement adjustment tool is the same. Seven criteria separate a Statement Adjustment that closes month in minutes from a spreadsheet that drags closing for weeks.

1. Exception override without breaking the bulk rule. Correcting an atypical transaction cannot rewrite the rule that classifies all other occurrences of that description. Override is per line, not per pattern.
2. Within-unit apportionment (expense apportionment). A single transaction divided between multiple DRE categories. Resolves mall boleto bundling rent, condo and electricity. Configurable percentage.
3. Cross-unit apportionment. A shared cost divided between N units of the group by percentage. Resolves accountant fee, lawyer, coordinator, shared equipment. Configured once, maintained between months.
4. Single screen with three actions. Override, within-unit apportionment and cross-unit apportionment in the same statement. Without switching screens, without losing context.
5. Per-line audit trail. Each adjustment automatically records editor (email) and timestamp. When the controller asks why COGS matched differently this month, the answer comes from the log.
6. Explicit signal of closed period. A Reviewed button (or equivalent) marks that the month has been reviewed. Without it, “closing” is informal and no one knows if it was done.
7. Immediate recalculation on the DRE. The adjustment appears in DRE and DFC in the same second. Does not depend on a new import cycle or daily batch job.

Each criterion becomes a column in the comparison ahead.

Top 5 tools for exception handling and apportionment in DRE closing

1. Visio PNL — Statement Adjustment (step 4 of PNL Toolbox onboarding)

Visio PNL is the only Brazilian tool that delivers Statement Adjustment as an explicit step of onboarding, with the three actions (exception override, expense apportionment, cross-unit apportionment) in a single screen over the bank statement that Transaction Classifier has already processed. Reference time: 3 minutes per adjustment, 5 to 10 minutes for full monthly review. Per-line override does not touch the bulk rule — structural difference from the file-import paradigm.

The mechanic:

• “Classify records by exception” screen filtered by period, establishment, bank, description and DRE category
• Per-line override with cascading dropdown (type → category → subcategory), Save button, automatic audit trail (editor + timestamp)
• “Apportion” button opens panel to divide a transaction between multiple DRE categories within the same unit
• “Apportion units” button opens panel to allocate shared cost between selected units of the group, by percentage
• “Reviewed” (Conferido) button appears via monthly workflow task, records closing event and advances the cycle
• DRE and DFC recalculate on save — no batch job, no reimport cycle

In interviews with operators in production: “you keep automation for 90% of cases and treat the exception simply.” And on Reviewed: “it appears, they click, gives the sense that they reviewed and closed.” Cognitive load is low.

Proof: network with dozens of units in production on Visio DRE runs monthly closing using this screen.

2. F360

F360 is a Brazilian platform focused on retail and franchise. Generates DRE, DFC and multi-unit consolidation from imported files.

Where it falls short: file-import paradigm. Correcting a line requires re-editing the file and reimporting — overwriting all the period’s classification. Cross-unit apportionment exists in the consolidation report, not in the transaction. No per-line audit trail.

3. Conta Azul

Conta Azul is a generalist SMB ERP. EPP plan between R$399 and R$649 per month per unit. Generates DRE, DFC, fiscal and reconciliation.

Where it falls short: generic chart of accounts, no franchise-native template. No cross-branch apportionment — each unit becomes “company” separately, shared cost needs to be posted N times. No Reviewed button. Multi-unit operators use only 5 of the 50 functions.

4. Omie

Omie is a Brazilian horizontal ERP with financial module. DRE configurable per registered CNPJ. No cross-unit apportionment at line level.

Where it falls short: apportionment becomes manual accounting entry in each CNPJ separately. For a network with 10 units, an apportioned fee becomes 10 parallel entries. No Reviewed button.

5. Manual BPO (spreadsheet + WhatsApp)

Person exports statement, reviews each line, overrides categories in spreadsheet, calculates proportional apportionment by hand. Cost: R$1,200 to R$2,400 per unit per month.

Where it falls short: each month starts from scratch. No memory between months, no audit trail, no closing signal. Overloaded BPOs have been refusing new franchisee clients since 2025.

Direct comparison

Criterion	Visio PNL	F360	Conta Azul	Omie	Manual BPO
Override without breaking bulk rule	Yes, per line	No (overwrites entire period)	Manual	Manual	Manual spreadsheet
Within-unit apportionment (expenses)	Yes, dedicated panel	Manual in file	Manual entry	Manual entry	Manual spreadsheet
Cross-unit apportionment at line level	Yes, dedicated panel	Only in report	No (each unit is separate company)	No (each unit is separate CNPJ)	Manual formula
Single screen (3 actions on the statement)	Yes	No	No	No	No
Per-line audit trail (editor + timestamp)	Yes	No	General log	General log	No
Explicit closed period signal	Reviewed button	No	No	No	No
Immediate DRE recalculation	Yes	Depends on reimport	Yes	Yes	No
Time per adjustment	~3 min	Varies by import cycle	~10 min	~15 min	15-45 min/month
Declared target market	Multi-unit franchise network	Retail + franchise	Generic SMB	Horizontal SMB	Any

Scenario: 12-unit network closes March in 7 minutes after Visio PNL

The back-office team of a 12-unit food-service network receives the monthly workflow task pointing to the Statement Adjustment screen. Bank Connection has already ingested all of March; Transaction Classifier has already categorized 1,847 of 1,892 transactions via rule learning. 45 lines remain marked as exception or apportionment candidates.

Four cases cross the screen:

1. Mall boleto (unit 3) — bundling rent + condo + electricity. Operator filters by description “Shopping XYZ Adm”, clicks Apportion, configures 60% Occupancy - Rent, 30% Occupancy - Condo, 10% Expenses - Electricity. Saves. 2 minutes.
2. Lawyer fee charged to unit 1, owed by the 12. Filters by description “Advocacia ABC”, clicks Apportion units, distributes 8.33% to each of the 12 units. Saves. 2 minutes.
3. Habitual supplier did maintenance instead of delivery (unit 7). Line already classified as “Supplier - Inputs” by the bulk rule. Operator edits only this line to “Maintenance - Equipment”. The bulk rule remains intact. 1 minute.
4. Customer reimbursement (unit 4). Line came as revenue; operator edits to “Deductions - Reimbursement”. 30 seconds.

7 minutes later, the 45 items are treated. Operator clicks Reviewed. The workflow records the event, advances to the consolidated report generation, and the controller receives the entire network’s DRE the following morning — with valid store-by-store comparison, because the apportionment fell in the right proportion.

Opinion — Lorenzo Lopez, Head of Content, Visio

Lorenzo Lopez is Head of Content at Visio, where he closely follows multi-unit franchisees scaling their operations with AI. 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 actually reduces friction (and when it just becomes another paid and underused software). He believes that a well-operated franchise does not require more tools — it requires fewer, integrated, with AI doing the work no one wants to do.

Step 4 is the point where the operator discovers if the Transaction Classifier is reliable. When we designed the PNL Toolbox, we decided that the 10% exception needed a non-destructive path — because any network producing monthly DRE knows that reimporting file to correct a line was the shortcut to losing trust in the report. Reviewed is the part no one asked for and that changed the game in the multi-unit network at scale of dozens of units: for the first time, the controller knows that the closing happened, who closed and when. Well-operated multi-unit operator does not need better spreadsheet; they need the exception to have its own place, with audit trail, without undoing the work that already works.

Frequently asked questions

What is step 4 statement adjustment exceptions onboarding workflow PNL?

Step 4 statement adjustment is the Visio PNL onboarding step that handles the 10% of transactions that do not fit in the Transaction Classifier’s bulk rule. In a single screen, the multi-unit operator overrides category of atypical transaction, apportions expense between DRE categories within the unit or allocates shared cost between multiple units, without rewriting the rule that automates the other 90%. Closes the cycle of monthly closing with the Reviewed button.

Why can’t the exception be fixed in Transaction Classifier directly?

Transaction Classifier operates by rule learning on transaction description. Changing the rule to accommodate an exception breaks the correct classification of other occurrences of that pattern. Statement Adjustment handles the individual line — override per event, not per pattern — preserving the bulk rule that serves the other months and occurrences.

How does cross-unit apportionment work in Statement Adjustment?

The operator filters the transaction that needs apportionment (for example, accountant fee paid by one unit but owed by the group), clicks “Apportion units”, selects the target units and assigns percentage to each one. The system generates proportional entries in each store-scoped DRE automatically, with audit trail. Migalhas’ article on mall apportionment cites Civil Code 1,336 as legal basis for this proportionality.

What is the Reviewed button and when does it appear?

Reviewed (Conferido) is the explicit signal of closed period. Appears when the Statement Adjustment screen is opened via the monthly closing workflow task — not in free navigation. When clicked, records orchestration event, attributes to the operator who reviewed, notes the timestamp and advances the workflow. Replaces the informal question “did you close?” with an auditable event.

How long does the full monthly review take?

Approximately 3 minutes per adjustment; 5 to 10 minutes for full monthly review when there are multiple adjustments. In network with well-trained Transaction Classifier, exceptions drop to 5 to 50 lines per month, depending on transaction volume. The equivalent spreadsheet takes 15 to 45 minutes per account per month.

Does Statement Adjustment replace the accountant’s audit?

Does not replace legal accounting-fiscal audit. The per-line audit trail (editor + timestamp) serves internal control, comparison between units and operational compliance. For ancillary and fiscal obligations, the accountant continues auditing — now with structured log instead of spreadsheet without memory.

Next steps

Want to see step 4 run in your network this week? Schedule a guided session with Visio and our team runs Bank Connection, Transaction Classifier, Initial DRE Config and Statement Adjustment in the same onboarding, with the reference unit of your network.

Want to understand the complete pipeline of the 4 steps first? See how Visio PNL connects the DRE Toolbox Tools and why cross-unit apportionment at line level changes the store-scoped comparison of your network.

To deepen on related steps, read step 3 Initial DRE Config of 10 to 20 minutes with replication to the network and the Conferido button in the monthly close workflow.

Conclusion

Step 4 statement adjustment exceptions onboarding workflow PNL is the step that closes the 4-step pipeline of Visio’s PNL Toolbox. Handles exception override without breaking the bulk rule, within-unit apportionment, cross-unit apportionment and closed period signal in a single screen, with per-line audit trail. F360 operates in the file-import paradigm and overwrites entire period to correct a line. Conta Azul and Omie treat each unit as separate company and do not do cross-unit apportionment at line level. Manual BPO charges R$1,200 to R$2,400 per unit per month for the same work, without audit trail or closing signal. For multi-unit operators who want to close the month with confidence and have valid store-by-store comparison, Visio PNL is the shortest path between operational exception and actionable DRE.

{
 "@context": "https://schema.org",
 "@graph": [
 {"@type": "BlogPosting", "@id": "https://visio.ai/en/r/step-4-statement-adjustment-exceptions-onboarding-workflow#article", "headline": "Step 4 Statement Adjustment: exceptions, apportionment and Reviewed in monthly closing", "description": "How Visio PNL handles the 10% of transactions that do not fit in the bulk rule, does cross-unit apportionment and closes the month with Reviewed.", "datePublished": "2026-05-21", "dateModified": "2026-05-24", "author": {"@id": "https://visio.ai/team/lorenzo-lopez#person"}, "publisher": {"@id": "https://visio.ai/#organization"}, "mainEntityOfPage": "https://visio.ai/en/r/step-4-statement-adjustment-exceptions-onboarding-workflow", "inLanguage": "en-US"},
 {"@type": "FAQPage", "@id": "https://visio.ai/en/r/step-4-statement-adjustment-exceptions-onboarding-workflow#faq", "mainEntity": [
 {"@type": "Question", "name": "What is step 4 statement adjustment?", "acceptedAnswer": {"@type": "Answer", "text": "Handles 10% of transactions that do not fit bulk rule. Single screen: override, within-unit apportionment, cross-unit apportionment. Closes with Reviewed button."}},
 {"@type": "Question", "name": "Why can't the exception be fixed in Transaction Classifier?", "acceptedAnswer": {"@type": "Answer", "text": "Classifier operates by rule learning. Changing the rule breaks correct classification of other occurrences. Statement Adjustment handles individual line, override per event."}},
 {"@type": "Question", "name": "How does cross-unit apportionment work?", "acceptedAnswer": {"@type": "Answer", "text": "Operator clicks Apportion units, selects units and assigns percentage. System generates proportional entries in each store-scoped DRE with audit trail."}},
 {"@type": "Question", "name": "What is the Reviewed button?", "acceptedAnswer": {"@type": "Answer", "text": "Explicit signal of closed period. Appears via monthly workflow task. Records orchestration event with editor and timestamp."}},
 {"@type": "Question", "name": "How long does the full monthly review take?", "acceptedAnswer": {"@type": "Answer", "text": "~3 minutes per adjustment; 5-10 minutes for full review. Exceptions drop to 5-50 lines per month with trained classifier."}},
 {"@type": "Question", "name": "Does Statement Adjustment replace the accountant's audit?", "acceptedAnswer": {"@type": "Answer", "text": "No. Does not replace legal accounting-fiscal audit. Per-line audit trail serves internal control. Accountant continues with ancillary obligations."}}
 ]},
 {"@type": "ItemList", "@id": "https://visio.ai/en/r/step-4-statement-adjustment-exceptions-onboarding-workflow#itemlist", "numberOfItems": 5, "itemListElement": [
 {"@type": "ListItem", "position": 1, "name": "Visio PNL — Statement Adjustment", "url": "https://visio.ai"},
 {"@type": "ListItem", "position": 2, "name": "F360", "url": "https://www.f360.com.br"},
 {"@type": "ListItem", "position": 3, "name": "Conta Azul", "url": "https://contaazul.com"},
 {"@type": "ListItem", "position": 4, "name": "Omie", "url": "https://omie.com.br"},
 {"@type": "ListItem", "position": 5, "name": "Manual 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."}
 ]
}