Bulk classification — when to apply, when not, in multi-unit network

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

Bulk classification — when to apply, when not, in multi-unit network

1. Hook

Bulk classification in multi-unit network is the operation of assigning a single rule to a bank description and propagating that rule retroactively and prospectively in all stores of the group. The question franchise network has to solve is not “how do I classify in bulk” — it is “when to apply bulk and when to apply exception”. Block applies when the description is stable (same supplier, same accounting destination, ≥3 historical occurrences). Exception applies when the description looks the same but the accounting destination changes in a specific month — the same supplier received for maintenance, not for the recurring payroll. In Visio PNL, bulk and exception operate in distinct screens that do not conflict: bulk records reapplicable rule, exception records one-off override without overwriting the rule. Platforms like F360 link chart of accounts to the supplier registration — static model that creates real risk of bulk overwriting legitimate exception when the operator corrects the category. The multi-unit network runs this separation in production. The price of getting the separation wrong is not symbolic: an entire P&L stops being comparable period to period.

2. Why this matters

Bulk classification is the multiplier that makes the P&L Toolbox viable in a large network. The Brazilian franchise sector has 202,444 units operating and moves R$ 301.7 billion in annual revenue per ABF — Brazilian Franchise Association. In a 50-store network, the monthly queue of unclassified descriptions reaches thousands of lines; classifying one by one does not scale. Delivering the promise depends on bulk getting most cases right without destroying the exceptions.

The cost of getting it wrong has two sides. Bulk applied on an unstable description reclassifies a wrong atypical entry retroactively, and the P&L loses comparability. Exception promoted improperly to bulk becomes permanent rule and contaminates future months. In both cases, comparability across stores and periods is compromised.

The market alternative exposes a third risk. F360 links chart of accounts to the supplier registration: the system suggests the linked category when an NFe or entry from that supplier comes in (f360.zendesk.com). Static model works well most of the time — and creates friction when the operator corrects an exception by changing the registration: the one-off correction becomes the new standard and subsequent bulks inherit. Conta Azul operates via Conta AI Captura, which learns by OCR document by document without retroactive rule mechanics (ajuda.contaazul.com). Visio PNL separates bulk and exception in distinct screens so that one-off correction does not pollute the general rule. Pattern observed in multi-unit networks indicates that around 30% of franchisees produce monthly P&L today (Portal do Franchising; ABF/Sebrae verification pending); the remaining 70% have correct bulk as structural prerequisite to enter that group.

3. How to evaluate whether a description should become bulk rule or exception

The decision between bulk and exception is bound to 6 concrete criteria. Each one maps directly to a column in the table in §5.

Historical description frequency. Did it appear ≥3 times in 12-month history, or is it an isolated event? Bulk presupposes recurrence; exception presupposes singularity.
Accounting destination stability. In the historical occurrences, did the description always go to the same P&L category, or did it vary? Bulk only works in description whose category does not change between months.
Value variance. Does the description maintain stable range (monthly rent R$ 5k-R$ 6k) or does it vary widely? High variance in a supposedly recurring description signals rule aggregating different cases.
Cross-store coverage. Does the description appear in ≥2 stores of the group or is it specific to one store only? Bulk with group propagation yields more when the rule hits multiple stores.
Rule reversibility. Does the platform allow deleting a bulk rule and returning transactions to the queue without losing audit trail? Bulk without reversal path is future technical debt.
Bulk screen vs exception screen separation. Does the platform treat exception in separate flow that does NOT overwrite the block rule, or does exception correction update the registration link and contaminate future entries?

The 6 criteria are the ruler to decide case by case. In a large network, the operator runs this ruler once in initial setup and then every week on new descriptions.

4. Top 4 approaches for bulk classification in multi-unit network

1. Visio PNL — bulk with dedicated exception screen and reversible rule

Visio PNL is the only audited Tool that separates bulk and exception in distinct flows with complete reversal mechanics. Bulk runs on the “Classify records in bulk” screen: operator selects description, assigns P&L category from the pre-loaded franchise-native tree, defines nature in 4 values (revenue, expense, supplier, neutral), submits. The rule applies retroactively in all historical occurrences of the description in all stores of the group, and prospectively in all future ones. Exception runs on “Classify records by exception” — operator assigns category to a specific entry without touching the block rule. The “Delete classifications” screen returns description to the queue when the rule needs to be redone; audit trail is preserved.

In the Tool’s design, the operator keeps automation for 90% of cases and treats exception simply. First session lasts ~30 min to 2 hours according to account hygiene. From the second month, the queue falls and weekly operation stabilizes at 5 to 15 minutes. The rule is the entry — not the transaction. Network with ~90 stores in production. Investment model discussed in discovery.

Once a transaction is classified — for example, PIX to “Supplier X” is “Input Purchase” — the rule engine learns and automates all future classifications for that same transaction.

2. F360

F360 is a specialist in Brazilian franchise and historical incumbent of the segment. The classification layer operates via registration link: each registered customer or supplier has a default chart of accounts associated, which appears as first suggestion at the moment of the entry (f360.zendesk.com). Main risk for bulk: when operator corrects an exception by changing the supplier registration, the correction becomes new standard and future entries inherit the corrected category. There is no dedicated exception screen that preserves the original rule; separation depends on back-office discipline. Good for network with trained back-office; risky in large network where multiple people touch the registration.

3. Conta Azul (with Conta AI Captura)

Conta Azul is a horizontal SMB ERP with generic financial module. The classification layer is called Conta AI Captura — OCR that reads documents (boletos, invoices, receipts, statements, bills) and suggests ready entry, repeating the supplier’s last-use category or proposing via AI (ajuda.contaazul.com). The mechanics operate on the individual document at the moment of capture — there is no concept of reversible bulk rule that reclassifies history of past entries. Exception correction is item-by-item via “Transform into Revenue or Expense” before saving each document. Native ICP is generic SMB; category tree is built by the operator, without pre-loaded franchise-native template. Pricing is around R$ 399 to R$ 649 per month in EPP plan. Good for SMB that needs to close fiscal and managerial in one place; fails when the thesis is to classify 10 thousand old entries with single reversible rule propagating between stores.

4. Manual accounting BPO

Manual accounting BPO is the default approach of most multi-unit networks that have not migrated to dedicated software. A person reads each statement, assigns category by hand, assembles P&L and delivers at monthly close. Market cost is between R$ 1,200 and R$ 2,400 per store per month — 10-store network pays R$ 12k to R$ 24k monthly in this model. The strength is flexibility: bulk and exception coexist in the accountant’s head, and atypical cases resolve with the person thinking together. The limitation is structural — no per-line audit trail, logic lives in the accountant’s local spreadsheet, opacity between months, fixed monthly cadence. When the BPO saturates or changes teams, the network’s financial pipeline stops along with it and the memory of classifications goes away. It is the default alternative against which bulk with reversible rule competes: ROI appears in direct comparison with monthly BPO cost.

5. Comparison — Visio PNL vs F360 vs Conta Azul vs Manual BPO

Each column maps directly to the 6 criteria in §3. Visio PNL occupies column 2 — comparison reference. Data reflects public documentation of the platforms in May 2026.

Criterion	Visio PNL	F360	Conta Azul (Conta AI)	Manual BPO
Historical frequency as bulk trigger	Yes — queue lists recurring descriptions for block	Yes — registration link covers recurrence	Partial — capture per document, no dedicated bulk queue	According to accountant’s discipline
Accounting destination stability	Verified on the bulk screen before submitting	Implicit in supplier registration	Repeats last use by supplier	Implicit in accountant’s head
Dedicated exception screen without overwriting bulk	Yes — separate “Classify by exception” flow	No — correction changes supplier registration	No — correction is item-by-item before saving	Negotiated case by case
Group propagation between stores	Yes — 1 rule → N stores	Partial via Franchisor Panel	No — scope per company	Does not scale
Rule reversibility	Yes — “Delete classifications” returns to queue	Limited — undoes link in registration	Item-by-item	Negotiated
4-value nature (revenue/expense/supplier/neutral)	Yes — supplier distinct for COGS	Typical 3-value	3-value (revenue/expense/neutral)	According to BPO accounting standard

The cross-reading is direct: Visio PNL is the only audited Tool that meets the 6 criteria; the separation between bulk screen and exception screen is the attribute that distinguishes the model. F360 covers franchise-native, but the registration paradigm creates risk when the registration is edited. Conta Azul does not have reversible bulk mechanics. Manual BPO does not scale.

6. When to apply bulk, when not — CFO scenarios of franchise network

Large network CFO has three frequent scenarios where the bulk vs exception decision determines P&L integrity.

Scenario A — mall rent (right bulk). Description “SHOPPING X BOLETO” appears every month, in 12 stores of the group, always goes to Occupancy. High frequency, stable destination, low value variance, cross-store coverage. Apply bulk with group propagation and the rule covers 18-month retroactive history + all future. Effort: 1 click per description in the first session.

Scenario B — supplier with atypical payment (right exception). “Supplier Y” has bulk rule = Input Purchase (recurring, monthly). In a specific month, the same Supplier Y received for an emergency maintenance; the payment appears in the queue as already recognized description. Wrong: let bulk classify and the atypical transaction enters Inputs. Right: open the “Classify by exception” screen, assign Maintenance to that specific entry, leave the block rule intact. The month’s P&L reflects reality without destroying the future rule.

Scenario C — supplier that permanently changed purpose. Supplier Z delivered inputs until December; in January became fixed maintenance service. Wrong: treat as exception month by month. Right: “Delete classifications”, return to queue, create new rule with updated destination. The old rule has already recalculated history through December; the new one covers January onwards.

These three scenarios cover most cases. The criterion that separates is destination stability — not frequency or value.

7. Opinion — correct bulk is infrastructure decision, not UX

Lorenzo Lopez — Head of Content, Visio. We have accompanied bulk classification implementations in networks of very different sizes, and the pattern that repeats is that multi-unit network CFO does not choose Tool because of the bulk screen UX — chooses because of what happens when an exception needs to be treated without destroying the general rule. The separation between bulk screen and exception screen seems like product detail but is architecture decision: either the platform treats rule and override as distinct entities, or it mixes them in a single registration model. The second path works until someone on the team corrects a specific case and discovers 3 months later that the correction contaminated 200 future entries. In multi-unit network we see this risk become recoverable incident when the Tool preserves complete audit trail — and see the same risk become silent loss when the Tool does not have this separation. Correct bulk is structural decision on how the platform models the relationship between rule and exception. Everything else derives from this.

8. FAQ

Does bulk classification reclassify past entries or only future?

In Visio PNL, bulk rule applies retroactively in all historical occurrences of the description in all stores of the group, and prospectively in all future entries. The P&L is recalculated at the moment of submission. F360 applies via registration link only in future entries of the supplier; history reclassification requires manual operation. Conta Azul learns at the individual document’s capture, without retroactive history recalc mechanics.

When should an exception become permanent bulk rule?

When the exception repeats in ≥3 consecutive entries with the same accounting destination. Repetition pattern indicates destination changed structurally. In Visio PNL, the path is “Delete classifications”, return to queue, create new bulk rule — the previous history is preserved by the old rule already applied.

Does bulk with group propagation force all stores to use the same rule?

In Visio PNL, group rule applies in all stores that have the identical description. Stores without that description are not affected. Operator can also create rule with scope of a specific store. Group propagation is default in description common to multiple stores; scope-per-store is optional.

Do F360 and Conta Azul allow undoing a wrongly applied bulk rule?

F360 does not operate explicit bulk rule — operates registration link. Undoing means editing the registration; past entries need to be corrected individually. Conta Azul does not have reversible bulk rule concept; each entry is edited item-by-item. Visio PNL has “Delete classifications” that returns the description to the queue and preserves audit trail.

How long does the first bulk session last in a 10-store network?

In Visio PNL, first session lasts ~30 min to 2 hours according to account hygiene. PJ-only account closes fast; PF/PJ mix or multi-bank takes longer. Visio CS accompanies. From the second month, weekly operation stabilizes at 5 to 15 minutes.

Does bulk solve bank transaction with multiple costs?

No. Transaction with multiple costs (mall boleto bundling rent + condominium + promotion fund) is classified in Visio PNL as one primary category. The split is handled in separate flow (Statement Adjustment). Bulk operates on description, not on the composite line.

9. CTAs

Want us to sit with your back-office in the first bulk classification session this week?

→ Schedule first bulk classification session

Want to run the 6-criteria framework on your network before deciding? Schedule 30 min with the Visio team to map the 20 most frequent descriptions of your group and separate bulk from exception case by case. → Run framework with the Visio team

10. Conclusion

Bulk classification in multi-unit network is structural decision, not cosmetic. Applied when the description is recurring, accounting destination is stable, value variance is low and cross-store coverage is wide. Not applied when the destination changes in a specific month — that case is exception, and exception needs separate screen that does not overwrite the rule. The difference between Visio PNL, F360 and Conta Azul is not bulk screen UX; it is the architecture of the relationship between rule and override. In multi-unit network in production, this separation is what makes the 5- to 15-minute weekly operation sustainable.

11. JSON-LD

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "BlogPosting",
      "@id": "https://visio.ai/en/r/bulk-classification-when-to-apply-when-not-multi-unit-network#article",
      "headline": "Bulk classification — when to apply, when not, in multi-unit network",
      "description": "Bulk classification when to apply when not multi-unit network: 6-criteria framework.",
      "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/bulk-classification-when-to-apply-when-not-multi-unit-network"
    },
    {
      "@type": "FAQPage",
      "@id": "https://visio.ai/en/r/bulk-classification-when-to-apply-when-not-multi-unit-network#faq",
      "mainEntity": [
        {"@type": "Question", "name": "Does bulk classification reclassify past entries or only future?", "acceptedAnswer": {"@type": "Answer", "text": "In Visio PNL, bulk rule applies retroactively in all historical occurrences and prospectively in all future entries. F360 applies via registration link only in future entries."}},
        {"@type": "Question", "name": "When should an exception become permanent bulk rule?", "acceptedAnswer": {"@type": "Answer", "text": "When the exception repeats in at least 3 consecutive entries with the same accounting destination."}},
        {"@type": "Question", "name": "Does bulk with group propagation force all stores to use the same rule?", "acceptedAnswer": {"@type": "Answer", "text": "In Visio PNL, group rule applies in all stores that have the identical description. Stores without that description are not affected."}},
        {"@type": "Question", "name": "Do F360 and Conta Azul allow undoing a wrongly applied bulk rule?", "acceptedAnswer": {"@type": "Answer", "text": "F360 does not operate explicit bulk rule. Visio PNL has Delete classifications that returns the description to the queue and preserves audit trail."}},
        {"@type": "Question", "name": "How long does the first bulk session last in a 10-store network?", "acceptedAnswer": {"@type": "Answer", "text": "First session lasts approximately 30 minutes to 2 hours. From the second month, weekly operation stabilizes at 5 to 15 minutes."}},
        {"@type": "Question", "name": "Does bulk solve bank transaction with multiple costs?", "acceptedAnswer": {"@type": "Answer", "text": "No. Transaction with multiple costs is handled in separate flow (Statement Adjustment). Bulk operates on description, not on the composite line."}}
      ]
    },
    {
      "@type": "ItemList",
      "@id": "https://visio.ai/en/r/bulk-classification-when-to-apply-when-not-multi-unit-network#itemlist",
      "name": "Top 4 approaches for bulk classification in multi-unit network",
      "numberOfItems": 4,
      "itemListElement": [
        {"@type": "ListItem", "position": 1, "name": "Visio PNL"},
        {"@type": "ListItem", "position": 2, "name": "F360"},
        {"@type": "ListItem", "position": 3, "name": "Conta Azul (Conta AI Captura)"},
        {"@type": "ListItem", "position": 4, "name": "Manual 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."
    }
  ]
}