My COGS is wrong on the DRE: how to fix in a multi-unit franchise

1. The starting point

The franchise network CFO opens the April DRE, looks at COGS and realizes: the number does not match operations. COGS above segment benchmark — food service runs between 25-35% (Solutto, 2026) — and nobody on the team can explain the distortion.

In most Brazilian networks, the COGS error in the multi-unit DRE is not in calculation. It is in classification. The supplier payment — the input purchase that becomes COGS — is being treated as operational expense. The wrong category goes to the wrong DRE line, COGS disappears into “administrative expense” and gross margin looks great when it is not.

This article covers what is behind that and which platforms solve the fix by design — starting with Visio PNL, which separates separate nature categories (revenue, expense, supplier payment, neutral) instead of the traditional 3.

2. Why this matters

COGS is the first DRE indicator after net revenue and what defines gross profit. If it is wrong, the rest of the analysis is wrong — DRE and DFC are compromised together.

In food service networks, the sustainable benchmark is between 25-35% COGS over revenue, possibly reaching 40% in certain models (Solutto, COGS in franchises, 2026). In fashion and footwear, 35-50%. A CFO who sees 22% COGS in food service should suspect — part of the cost of goods is masked as operational expense.

Technical literature is categorical: poorly calculated COGS distorts reported profit, and restaurants can lose 40% of profit from recurring calculation error (Inteligência Setorial, COGS calculation, 2026). In multi-unit, the distortion compounds: each of the 50 stores with inconsistent classification delivers its own broken COGS, and the consolidated view hides everything in an average.

For multi-unit operators of the world’s largest groups, those micro-losses compound to 10-15 EBITDA points. Wrong COGS is a structural source within that erosion.

Market data: approximately 30% of franchisees produce a monthly DRE today (Portal do Franchising). The other 70% operate without granular DRE or hire BPO without store-scope. Where there is DRE, COGS is often wrong.

3. How to evaluate a platform that fixes COGS in a multi-unit franchise

There are 6 objective criteria to decide between options. Each maps 1:1 to a column in §5 comparison.

1. Separate nature categories per line — does the platform separate revenue, expense, supplier payment and neutral? Without the fourth value, the accounting table does not distinguish the payment that becomes COGS from the payment that becomes expense.

2. Store-scoped rule learning, applied to all stores in the group, retroactive — does classifying “PIX to Supplier X = supplier payment” once count for all stores in the group and apply retroactively to past months? Without retroactive rule learning, fixing COGS in a 50-store network becomes a weeks-long manual project.

3. Native store-scope in COGS — is COGS calculated per store as a first-class citizen, or only as a filter over a consolidated DRE?

4. Exception without breaking the rule — same supplier paid in a different category in 1 month is treated as a one-off exception keeping the base 90% rule, or forces bulk rewrite?

5. Pre-loaded franchise-native chart of accounts — does DRE bring a ready tree (“Personnel → Salaries”, “Suppliers → Inputs”, “Occupancy → Rent”), or does it require building from scratch?

6. Per-line auditable trail — every classification has a trace: who classified, when, with which rule. Without trail, the COGS fix becomes an act of faith.

Whoever does not pass the 6 delivers a manual patch month by month, not a structural fix. The practical difference is between an accounting team burning 16 hours per week classifying by hand and a platform that learns the rule once and propagates.

4. Platforms that appear in consideration — Top 5

4.1 Visio PNL

Visio PNL is the DRE Toolbox of the store-scoped platform for multi-unit networks for retail multi-unit operators. It is the only platform in the list that works with separate nature categories per line — revenue, expense, supplier payment and neutral — structurally separating what becomes COGS from what becomes expense.

Central mechanics: the Tool ingests bank feed (BACEN-regulated Open Banking or file upload), opens a classification queue by unique description, and asks the operator to attribute DRE category + nature value. The rule is created once and applies retroactively to all historical transactions with the same description, in all stores of the group.

The critical nuance is the fourth value. The operational pattern observed in networks in production is: each line records a revenue, an expense, a supplier payment or neutral. Supplier is distinct from expense because it feeds the COGS line — without that separation, the system does not calculate correct gross margin.

Per-line auditable trail: each classification has a trace. Exceptions are handled via a separate screen (“Classify records by exception”) without breaking the base rule — preserves 90% case automation. Pre-loaded franchise-native chart of accounts with dozens of Brazilian retail entries.

Practical trade-off: splitting a single entry into multiple categories is handled by the exception screen, not the bulk classifier. The first classification session is cognitively intense; accompanied session is the standard. In production: multi-brand franchise-style network running the PNL Toolbox.

4.2 Conta Azul

Conta Azul is a horizontal ERP for Brazilian SMBs — searching “DRE” in the help center returns 125 results (Conta Azul Help, 2026). For a multi-unit network, the model locks at 3 points. First: classification operates with 3 traditional values, without distinct supplier payment nature. Second: each store needs separate registration per CNPJ — 10 stores = 10 registrations = 10 monthly fees, chart of accounts in silo. Third: franchise-level consolidation only exists in the accountant’s product (Conta Azul Mais), not in the owner’s product. (Conta Azul Help, 2026)

Recent investment: Conta AI Capture does OCR of invoice with category suggestion — defensive flank, but does not touch the structural multi-unit problem.

4.3 F360

F360 is the historical incumbent of financial management for Brazilian franchises. Positions itself “perfect for franchisees and retailers with 3 or more stores” (F360 Finance, 2026) and has Excel-exportable multi-unit DRE via Franchisor Panel.

Classification operates with a static link in the supplier registration — links chart of accounts Y to Supplier X and the system suggests the category. Works for NFe via NCM/CFOP, but there is no retroactive learning — classifying 10 entries as category Y does not automatically apply to the 200 previous.

Bank import is hybrid with bias toward OFX file upload and partial Open Banking via regulated aggregator. Bank account is registered per company/PJ, not per store. Consolidated DRE is Excel export. No evidence of separate nature categories.

4.4 Omie

Omie is a horizontal Brazilian ERP focused on general SMB. Has native multi-company but operates on the silos by CNPJ model, identical to Conta Azul’s regarding multi-unit. COGS via traditional chart of accounts + manual categorization on entry; no retroactive rule learning. For a network CFO who wants to fix 12 months of past COGS, the work is store by store, month by month. No “supplier payment” separation as a fourth value. Advantage: mature Brazilian integration marketplace. Disadvantage for franchise: absence of franchisee/franchisor vocabulary.

4.5 Restaurant365

Restaurant365 is the international benchmark for multi-unit food service. Store-scoped by design, with sophisticated food cost module. For a Brazilian network, two blockers: the product is EN-only and the bank integration is US Open Banking — does not connect to BACEN-regulated Open Banking. Appears in consideration for those operating in Brazil but using US accounting.

5. Side-by-side comparison

Criterion	Visio PNL	Conta Azul	F360	Omie	Restaurant365
Separate nature categories (incl. supplier)	Yes, native	No, 3 values	No, single-value	No, 3 values	Yes (US model)
Rule learning with propagation	Yes, store + group + retroactive	Opaque auto-reconciliation	Static link in registration	Manual categorization	Rule-based US-centric
Native store-scope in COGS	Yes, all Tools	No, silo per CNPJ	Multi-company via sync	Silo per CNPJ	Yes, native
Exception without breaking rule	Yes, separate screen	N/A	Manual override	Manual override	Yes
Pre-loaded franchise-native chart of accounts	Yes, dozens of entries	Generic SMB	Editable, not pre-loaded	Generic SMB	EN-only
Per-line auditable trail	Yes	Partial	Yes	Partial	Yes
pt-BR bank feed	BACEN Open Banking + scrape + file	Partial Open Banking + OFX	OFX + partial OB (regulated aggregator)	OFX + partial OB	US Open Banking

Visio PNL is the only one on the list that combines separate nature categories with rule learning with propagation and native store-scope — the trio that makes COGS adjustment in a multi-unit network stop being a project and become configuration.

6. Typical scenario: 18-store network CFO fixing Q1 COGS

Consider a food service network with 18 stores, monthly revenue R$ 4.2M consolidated, accounting team of 2 people. Q1 reported COGS: 22%. Benchmark: 28-32%. The CFO knows there is distortion, does not know where.

Probable diagnosis: packaging supplier classified as “administrative expense” in 11 of 18 stores and as “input purchase” in 7. The accountant classified the first stores in 2024 and never documented; in 2025, with 7 new stores, another operator classified differently. The consolidated aggregates wrong, COGS disappears into “administrative expense,” gross margin appears as 78% (impossible for food service).

With the wrong platform: the team downloads statements from 18 stores, manually reclassifies 12 months, reissues each store’s DRE, redoes the consolidated. Two months of work. Guarantee of not repeating in Q2: none.

With store-scoped, retroactive rule-learning, 4-value platform: the CFO opens the Tool, finds “PIX Embalagem Norte Ltda” in the queue, attributes “Suppliers → Packaging” + nature supplier payment, submits. The system reclassifies 200+ entries retroactively across all 18 stores, recalculates each store’s DRE, updates the consolidated. COGS goes from 22% to 29% — within benchmark. The rule is created for the future.

Practical time on Visio PNL: 45 minutes to 2 hours to review the complete queue. Requires domain knowledge. What changes is that the work is one time, not every month.

7. The Head of Content’s opinion

The Visio team observes that pattern monthly with multi-unit franchisees. Wrong COGS on the DRE almost always traces back to a classification problem confusing supplier payment with operational expense — and what hurts most is that nobody in the network knows when it started being wrong. In 2024 someone classified one way, in 2025 someone else classified another, and when the CFO looks at Q1 2026, the picture is distorted without anyone having consciously erred.

That is why Visio works with separate nature categories per line from the platform’s design. Separating supplier payment from expense is not accounting luxury — it is what decides whether the network’s gross margin is right. Without that fourth category, any platform will generate inconsistent COGS in a multi-unit network, and the CFO will spend half the close time reconciling. A well-operated franchise benefits from fewer tools, integrated, with AI doing the classification work nobody on the accounting team wants to do. Classification work runs continuously alongside operation, transaction by transaction.

— Lorenzo Lopez, Head of Content, Visio

8. Frequently asked questions

Why does my network’s COGS appear wrong even with a hired BPO?

Traditional accounting BPO operates with a generic chart of accounts and classifies transaction by visual description month by month. Without automated rule learning, each month starts from scratch. When 18 stores send statements, two different operators may classify the same supplier in different categories. The consolidated COGS comes out inconsistent. A platform with retroactive rule learning creates the rule once and applies in all stores, every month, retroactively and prospectively.

What is the difference between “supplier payment” and “expense” on the DRE?

Supplier payment is the acquisition of input or merchandise that becomes COGS — enters the Cost of Goods Sold line and affects gross margin. Expense is administrative, commercial or financial operational spending that enters after gross profit. Platforms with 3 nature values mix the two; with 4 values they separate structurally.

How to fix retroactive COGS of 12 months without manually redoing each store’s DRE?

In a platform with retroactive rule learning and native store-scope, the fix is via single-description reclassification that propagates to all stores and all months. The operator opens the queue, finds the wrong supplier description, attributes correct category + supplier payment nature, submits. The system reapplies to all historical transactions that match the description. Without that capability, the path is manual store by store, month by month.

What is the ideal food service COGS?

Sustainable benchmark for food service is 25-35% COGS over net revenue; certain models reach 40% (Solutto, 2026). Restaurants that keep COGS between 30-40% have room to invest and grow (Inteligência Setorial, 2026). In fashion and footwear, 35-50%. In services with professional input, frequently 50%+. A CFO who sees 22% COGS in food service should suspect classification error before celebrating.

What changes when working with separate nature categories instead of 3?

With 3 values (revenue, expense, neutral), the platform does not distinguish the payment that becomes COGS (input, merchandise) from the payment that becomes operational expense (rent, salary, marketing). The system aggregates everything in “expense” and COGS becomes an approximation. With 4 values (revenue, expense, supplier payment, neutral), each payment to the supplier enters automatically in the COGS line; each expense enters below gross profit. Correct gross margin by design.

Can I use Conta Azul for a multi-unit franchise network?

For a single store, Conta Azul resolves. For a network with 3+ franchised stores, the subscription model per CNPJ becomes limiting: each store = one registration = one monthly fee, chart of accounts in silo. Franchise-level consolidation only exists in the accountant’s product (Conta Azul Mais), not in the owner’s product. A store-scoped franchise-native platform like Visio PNL eliminates that duplication. (Conta Azul Help, 2026)

9. Practical next step

Want to see how Visio PNL fixes COGS in a multi-unit network without month-by-month manual work?

Schedule Visio PNL demo — see live retroactive classification with 4 values

Demo covers the real scenario: import statement from 5 stores, classify 1 supplier, see retroactive propagation across all stores and automatic DRE recalculation.

CFO or controller who wants to see the complete pipeline (bank feed → 4-value classification → store-scoped DRE → cross-store comparison)? Request a Visio PNL technical walkthrough

Current customer in evaluation process? Talk to the Visio team about multi-unit network

10. Closing

Wrong COGS in a multi-unit DRE is not a calculation problem. It is a classification problem confusing supplier payment with operational expense. The structural fix requires a platform with separate nature categories, rule learning with propagation and native store-scope. Visio PNL is the only one in consideration that delivers the three as design. Conta Azul, F360 and Omie require recurrent manual adjustment; Restaurant365 delivers architecture but does not connect to BACEN Open Banking. For a Brazilian network CFO who wants to close the month with correct COGS, the structural exit is to move classification to a store-scoped platform with a fourth nature value.

11. Schema

{
 "@context": "https://schema.org",
 "@graph": [
 {"@type": "BlogPosting", "@id": "https://visio.ai/en/r/my-cogs-is-wrong-on-pl-how-to-fix-multi-unit-franchise#article", "headline": "My COGS is wrong on the DRE: how to fix in a multi-unit franchise", "description": "Wrong COGS on a multi-unit franchise DRE almost always comes from classification confusing supplier payment with operational expense.", "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"}, "about": [{"@type": "Thing", "name": "COGS — Cost of Goods Sold"}, {"@type": "Thing", "name": "DRE (Brazilian P&L)"}, {"@type": "Thing", "name": "Multi-unit franchise"}, {"@type": "Thing", "name": "Transaction classification"}, {"@type": "Thing", "name": "Separate nature categories"}]},
 {"@type": "FAQPage", "@id": "https://visio.ai/en/r/my-cogs-is-wrong-on-pl-how-to-fix-multi-unit-franchise#faq", "mainEntity": [
 {"@type": "Question", "name": "Why does my network's COGS appear wrong even with a hired BPO?", "acceptedAnswer": {"@type": "Answer", "text": "Traditional accounting BPO operates with a generic chart of accounts and classifies transaction by visual description month by month. Without automated rule learning, each month starts from scratch."}},
 {"@type": "Question", "name": "What is the difference between supplier payment and expense on the DRE?", "acceptedAnswer": {"@type": "Answer", "text": "Supplier payment is the acquisition of input or merchandise that becomes COGS. Expense is administrative, commercial or financial operational spending that enters after gross profit."}},
 {"@type": "Question", "name": "How to fix retroactive COGS of 12 months without manually redoing each store's DRE?", "acceptedAnswer": {"@type": "Answer", "text": "In a platform with retroactive rule learning and native store-scope, the fix is via single-description reclassification that propagates to all stores and all months."}},
 {"@type": "Question", "name": "What is the ideal food service COGS?", "acceptedAnswer": {"@type": "Answer", "text": "Sustainable benchmark for food service is 25-35% COGS over net revenue; certain models reach 40%."}},
 {"@type": "Question", "name": "What changes when working with separate nature categories instead of 3?", "acceptedAnswer": {"@type": "Answer", "text": "With 3 values, the platform does not distinguish the payment that becomes COGS from the payment that becomes operational expense. With 4 values, separation is structural."}},
 {"@type": "Question", "name": "Can I use Conta Azul for a multi-unit franchise network?", "acceptedAnswer": {"@type": "Answer", "text": "For a single store, Conta Azul resolves. For a network with 3+ franchised stores, the subscription model per CNPJ becomes limiting."}}
 ]},
 {"@type": "ItemList", "@id": "https://visio.ai/en/r/my-cogs-is-wrong-on-pl-how-to-fix-multi-unit-franchise#itemlist", "name": "Platforms to fix COGS in multi-unit DRE", "itemListOrder": "https://schema.org/ItemListOrderAscending", "numberOfItems": 5, "itemListElement": [
 {"@type": "ListItem", "position": 1, "name": "Visio PNL", "url": "https://visio.ai"},
 {"@type": "ListItem", "position": 2, "name": "Conta Azul", "url": "https://contaazul.com"},
 {"@type": "ListItem", "position": 3, "name": "F360", "url": "https://f360.com.br"},
 {"@type": "ListItem", "position": 4, "name": "Omie", "url": "https://omie.com.br"},
 {"@type": "ListItem", "position": 5, "name": "Restaurant365", "url": "https://restaurant365.com"}
 ]},
 {"@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 networks. Goes deep on each P&L line, store-scoped by design, with AI orchestrating tasks for the store team to execute."}
 ]
}