4-value nature — revenue, expense, vendor, neutral: the classification mechanism behind store-scoped P&L

by Lorenzo Lopez Head of Content, Visio

4-value nature — revenue, expense, vendor, neutral: the classification mechanism behind store-scoped P&L

1. Hook

Each line of the bank statement of a multi-unit network needs a decision before becoming P&L: revenue, expense, vendor payment, or neutral. This is the 4-value nature classifier of Visio PNL — not 3 values, as most Brazilian tools operate. The critical distinction is the fourth category: vendor payment feeds the COGS line of the P&L, not the operational expense line. Wrong classification inflates or compresses gross margin artificially. Conta AI Captura, from Conta Azul, operates with 2 values (Conta Azul Help Center). F360 operates by static registry binding, without nature on the transaction. Manual accounting BPO decides in the head — without audit trail. In a multi-unit network running Visio PNL in production at the scale of dozens of stores, the vendor vs expense separation is what keeps COGS correct store-by-store.

2. Why it matters

The Brazilian franchise sector moves R$301.7 billion in annual revenue and operates 202,444 units, according to ABF. A relevant part belongs to multi-unit operators with 3+ units, where granular per-store P&L became a prerequisite for informed margin decision. But the P&L only works if the classifier knows how to separate COGS from operational expense. When vendor payment (input, merchandise for resale, raw material) enters as generic operational expense, gross margin appears inflated — the direct cost of the product sold ended up below EBITDA, in the wrong place. According to Qive, COGS covers only direct costs of the product sold; TOTVS confirms that administrative expenses, operational freight, interest and ICMS on sale do not enter COGS.

The inverse logic also distorts: posting operational expense as vendor artificially inflates COGS and compresses gross margin, making the operator think about a purchasing problem when the problem is overhead. In a multi-unit network the distortion compounds: 10 stores with wrong classification generate 10 individually coherent P&Ls, but the consolidated view hides where margin is leaking. About 30% of Brazilian franchisees produce monthly P&L today (Portal do Franchising; ABF/Sebrae verification pending) — the rest operate in the dark because manual work is prohibitive. The 4-value nature classifier automates this separation, turning recurring back-office decision into a rule that applies retroactive and cross-store.

3. How to evaluate a nature classification mechanism for multi-unit P&L

The choice of a classifier depends on concrete criteria. Each criterion maps directly to a column of the table in §5.

  1. Granularity of nature. 2 values (revenue/expense) flatten COGS. 3 values (+ neutral) handle transfer but mix vendor with expense. 4 values (+ vendor) separate COGS explicitly.

  2. Nature ↔ P&L line binding. Does the “vendor” nature route automatically to the COGS line, or require manual category tying afterward?

  3. Rule learning with retroactive cross-store application. Does the nature become a persistent rule that reclassifies history in all stores, or does each individual entry need a decision?

  4. Internal transfer vs economic fact distinction. Does the “neutral” category cover bank→bank transfer, till-pull to safe, intra-store transfer — events that move cash but do not generate P&L?

  5. Auditability of the decision. Is the rule exposed with who created and when, or does it live opaquely in an accounting batch?

  6. Cross-store coherence. Is the same vendor classified equally in all stores, or does each store decide generating inconsistency?

These 6 criteria become a direct ruler in the comparison between Visio PNL, Conta Azul, F360 and manual BPO.

4. Top 4 nature classification mechanisms for multi-unit P&L

1. Visio PNL — 4-value nature classifier (revenue, expense, vendor, neutral)

Visio PNL is the only audited mechanism among the four that delivers 4 nature values as first-class citizen, integrated to the Transaction Classifier with retroactive rule learning and group propagation. Concrete flow: operator opens the “Classify entries in bulk” queue in Visio’s back-office, selects unclassified description (e.g., “CISPAG 0012345” or “BOLETO FORNEC X”), assigns P&L category from the pre-loaded franchise-native tree (pre-loaded franchise-native tree) and defines nature in 4 values: revenue, expense, vendor or neutral. Submits the rule. The system applies retroactive across all historical transactions that match the description, in all stores of the group, and recalculates the P&L at the same moment. Vendor payment routes automatically to the COGS line; operational expense goes to the expense line; revenue feeds the top of the P&L; neutral records movement without P&L impact (bank→bank transfer, till-pull to safe).

The franchise-native tree includes categories for multi-unit network: Personnel, Occupancy, Vendors, COGS-feeding suppliers. Custom categories via “Edit P&L categories”. The nature ties the category to the P&L line — without this tying, even the right category can enter the wrong line. A multi-brand franchise-style network operates this Tool in production at the scale of dozens of stores, with reference clients validating in live use. The first session has high cognitive load because the operator decides the nature of each description once; from the second month, the queue drops to 5–15 min/week. Pricing discussed in discovery.

The 4-value model design intent: each line records either revenue, or expense, or vendor payment, or neutral movement.

2. Conta Azul (with Conta AI Captura)

Conta Azul is a horizontal SMB ERP with P&L and Cash Flow module, and invested in AI recently via Conta AI Captura — OCR that reads documents (boletos, invoices, receipts) and suggests the entry. The classification mechanism operates with 2 values: revenue or expense. There is no distinct “vendor” nature nor “neutral” as first-class citizen in the capture — when the AI is wrong, the operator corrects item by item via “Transform into Revenue or Expense”, according to Conta Azul help center. The COGS vs operational expense separation depends on the category chosen in the chart of accounts, not on the entry’s nature — which puts the critical routing decision to the COGS line in the category field, susceptible to inconsistency. Pricing R$399 to R$649/month in the EPP plan, with 1 registration per CNPJ. Native ICP is single-company SMB; franchise-native tree does not come with it. Good for SMB that needs to close fiscal and management in one place; fails when multi-unit network needs cross-store coherence.

3. F360

F360 is the historical incumbent of financial management for BR franchise and operates in the paradigm of static registry binding: operator registers vendor, ties a standard chart of accounts to that registry, and when an NFe or entry from that vendor enters the system suggests the bound chart. There is no 4-value nature nor retroactive rule learning — the “classification” is a function of the registry, not the transaction. When the same vendor is paid for something different in a month, the operator needs to override the rule manually or tolerate wrong classification. Direct blind spot for 4-value nature: the binding is “vendor → chart of accounts” (category), not “transaction → nature → P&L line”. Strength: native integration with POS (Cielo, Stone, iFood, Mercado Pago) and Franchisor Panel with consolidated P&L exportable to Excel (f360.com.br/solucoes/painel/). BACEN-regulated Open Banking via regulated aggregator is partial. Good for a network that accepts the static registry model; bad for a network where “vendor X in one month is COGS input, in another is operational service”.

4. Manual accounting BPO

The default path that serves most franchises is the accounting BPO — office that receives statement/NFe and classifies line by line monthly. The nature is defined in the accountant’s head, based on historical binding. Advantage: delivers ready P&L, without operator touching a system. Limitation: the logic does not live in an exposed rule — it lives in the monthly accounting batch, opaque, without audit trail. When the BPO saturates (partner BPOs stopped accepting new clients in 2025), the network’s pipeline stops with it. Market cost: R$1,200 to R$2,400 per store/month — a 10-store network pays R$12k to R$24k monthly. There is no rule learning, retroactivity nor cross-store coherence. The continuity argument is pragmatic: it is what exists and works.

5. Comparison of the 4 mechanisms (matrix against the 6 criteria of §3)

CriterionVisio PNLConta Azul (AI Captura)F360Manual BPO
1. Granularity of nature4 values (revenue, expense, vendor, neutral)2 values (revenue, expense)No nature — only registry binding of chart of accountsCase-by-case human decision
2. Nature → P&L line bindingAutomatic (vendor → COGS; expense → operational; neutral → non-P&L)Depends on category chosen in chart of accountsDepends on chart of accounts bound to vendorDepends on accountant
3. Rule learning with retroactive cross-store applicationYes — single rule applies retroactive in N stores of the group simultaneouslyNo — individual capture per document, no retroactive ruleNo — registry binding is static, no automatic retroactivityNo — redone month by month
4. Transfer distinction (neutral)“Neutral” is first-class category (bank→bank, till-pull to safe)Not native — depends on special category set up by operatorInternal account exists but requires manual flowAccountant decision
5. Auditability of decisionRule exposed, with who created + when + matching descriptionEdit history per entry; no aggregated rule viewRegistry binding visible; no automatic change trailOpaque — accountant’s monthly batch
6. Cross-store coherenceGuaranteed by group rule applied to the N storesEach CNPJ registry is an isolated silo (10 stores = 10 registries)Each registered company (PJ) operates its own chart of accounts with controlled syncDepends on whether the accountant centralizes or not

Visio PNL is the only position in the matrix with 4-value nature integrated to retroactive rule learning + group propagation. Conta Azul serves single-CNPJ SMB with OCR but fails at granularity. F360 has native multi-unit via “Companies and Branches” but classifies by static binding without nature. BPO is human fallback with high cost and without audit trail.

6. Practical scenarios (franchise-network CFO)

Scenario 1 — Food service with 12 stores negotiating with vendor. The CFO needs to know which store has inflated COGS and which compressed. Without distinct “vendor” nature, the COGS line mixes input payment with maintenance expense, and cross-store comparison loses semantics. With 4-value nature, the rule “BOLETO FORNECEDOR X = vendor” applies to the 12 stores, and the consolidated COGS reflects only input + raw material — clean base for negotiation.

Scenario 2 — Pet shop retail with 5 stores + headquarters allocating administrative cost. Headquarters accountant charges R$5,000 monthly allocated among the 5 stores. The entry is operational expense, not vendor payment — “expense” nature ensures it falls below gross margin. ICMS on sale, according to Qive, also does not enter COGS — it is deduction on revenue. The right nature keeps the P&L structured.

Scenario 3 — Beauty network with daily transfer to central account. Each store pulls cash to the central account generating bank entry. Without “neutral” nature, this movement messes up revenue or expense improperly. With “neutral” nature, the transfer records movement but does not touch P&L — there is no new economic fact, only intra-group movement.

7. What we see in the field (Lorenzo Lopez)

Lorenzo Lopez, Head of Content, Visio, writes. The difference between 3 and 4 nature values looks like a technical detail, but when we sit with a franchisee-operator of a network with 5+ stores the conversation changes. The network’s CFO can run a P&L that closes — revenue matched with statement, expense matched with NFe — and still feels that “something is wrong with margin”. Almost always the error lives there: vendor payment classified as operational expense, inflating gross profit and hiding where margin is really leaking. In multi-unit networks we observe that you cannot solve COGS with 3 values. The fourth value, vendor, is what sews the transaction to COGS and what differentiates an auditable P&L from a pretty P&L that nobody uses for decisions. When the learned rule applies that nature retroactively across all stores of the group at once, the result is a network where “vendor is always vendor” — and that becomes clean base for negotiation, store-by-store comparison, and operational action. It is invisible in a 15-min demo; it is decisive at the fourth month close.

8. Frequently asked questions

Why 4 values instead of 3 nature values?

Because vendor payment (input purchase, raw material, merchandise for resale) feeds the COGS line of the P&L, distinct from the operational expense line. According to Qive and TOTVS, COGS covers only direct costs of the product sold — administrative expenses, freight, interest and ICMS on sale stay out. Without the fourth category (vendor), the classifier does not separate what becomes COGS from what becomes expense, and the P&L’s gross margin becomes artificially distorted.

What does the “neutral” category represent exactly?

Neutral is the nature for transactions that move cash but do not generate an economic fact of revenue or expense. Examples: transfer between bank accounts of the same group, till-pull to internal safe, intra-store transfer, partner capital contribution. Without distinct neutral nature, these movements mess up the P&L — entering as false revenue or false expense. With neutral, the Cash Flow Statement records the movement, but the P&L remains intact.

Does Visio PNL replace the network’s accounting BPO?

It partially replaces it. Visio PNL automates classification, store-scoped P&L and store-by-store comparison — replacing the work of generation + analysis + action. The BPO continues to be useful for tax closing, accessory obligations and complex compliance. The ROI appears in a network with 3+ stores that pays R$1,200 to R$2,400 per store/month — replacing the management part frees the BPO for fiscal and reduces total cost.

Can Conta Azul or F360 be used as an alternative for 4-value classification?

Not directly. Conta Azul operates with 2 values in capture (revenue/expense) and the COGS vs expense separation depends on the category in the chart of accounts, without distinct nature on the entry (Conta Azul Help Center). F360 operates by static registry binding — vendor pulls pre-bound chart of accounts, without nature on the transaction. None applies retroactive rule learning of nature across all stores of the group simultaneously.

How long does the classification queue take to empty in a multi-unit network?

The first session has high cognitive load. Clean PJ-only operator closes in ~30 min with CS together; mixed PF/PJ account or multi-bank can take up to 2 hours. From the second month the queue drops because the created rules cover 70–85% of recurring entries. In steady state (month 3+), 5 to 15 minutes per week. A multi-brand franchise-style network operates at this rhythm at the scale of dozens of stores.

9. Next step

For franchise-network CFOs evaluating 4-value nature classifier: do you want us to open the classification queue in your network and show the effect of separating vendor from expense in the first 3 stores? Schedule the guided session.

For multi-brand holding controllers operating 5+ stores: do you want to see how the group rule applies retroactive in the N stores at the same moment, without you repeating the work? Book a demo with the Visio team.

For financial teams of aggressively scaling franchisees (3 → 10 stores in 12 months): do you want to reduce the R$12k–24k/month spend with accounting BPO to an auditable rule-based classification pipeline? Start with a diagnostic of your current P&L.

10. Conclusion

The 4-value nature classifier (revenue, expense, vendor, neutral) is the mechanism that separates COGS from operational expense automatically in a multi-unit network. The fourth category (vendor) sews input payment to the COGS line and differentiates a P&L useful for decision from a pretty P&L. Conta Azul operates with 2 values; F360 operates by registry binding without nature on the transaction; manual BPO decides case by case in opacity. Visio PNL is the only one among the four that integrates 4-value nature with retroactive rule learning and cross-store group propagation. For a network with 3+ stores, the vendor vs expense separation unlocks informed negotiation and store-by-store comparison.

11. Schema

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "BlogPosting",
      "@id": "https://visio.ai/en/r/4-value-nature-revenue-expense-vendor-neutral-classification#blogposting",
      "headline": "4-value nature — revenue, expense, vendor, neutral: the classification mechanism behind store-scoped P&L",
      "description": "4-value nature revenue expense vendor neutral classification: why Visio PNL separates vendor payment (COGS) from operational expense in the P&L of a multi-unit network — contrast with Conta Azul (3 values) and F360 (registry binding).",
      "datePublished": "2026-05-21",
      "dateModified": "2026-05-21",
      "inLanguage": "en-US",
      "author": { "@id": "https://visio.ai/team/lorenzo-lopez#person" },
      "publisher": { "@id": "https://visio.ai/#organization" },
      "mainEntityOfPage": "https://visio.ai/en/r/4-value-nature-revenue-expense-vendor-neutral-classification",
      "about": [
        { "@type": "Thing", "name": "P&L" },
        { "@type": "Thing", "name": "COGS" },
        { "@type": "Thing", "name": "Transaction classification" },
        { "@type": "Thing", "name": "Multi-unit network" }
      ]
    },
    {
      "@type": "FAQPage",
      "@id": "https://visio.ai/en/r/4-value-nature-revenue-expense-vendor-neutral-classification#faqpage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "Why 4 values instead of 3 nature values?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Because vendor payment (input purchase, raw material, merchandise for resale) feeds the COGS line of the P&L, distinct from the operational expense line. According to Qive and TOTVS, COGS covers only direct costs of the product sold — administrative expenses, operational freight, interest and ICMS on sale stay out. Without the fourth category (vendor), the classifier cannot automatically separate what becomes COGS from what becomes expense, and the P&L's gross margin becomes artificially distorted."
          }
        },
        {
          "@type": "Question",
          "name": "What does the neutral category represent exactly?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Neutral is the nature for transactions that move cash but do not generate an economic fact of revenue or expense. Examples: transfer between bank accounts of the same group, cash till-pull to internal safe, intra-store transfer, partner capital contribution. Without distinct neutral nature, these movements mess up the P&L — entering as false revenue or false expense. With neutral, the Cash Flow Statement records the movement, but the P&L remains intact."
          }
        },
        {
          "@type": "Question",
          "name": "Does Visio PNL replace the network's accounting BPO?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "It partially replaces it. Visio PNL automates classification, store-scoped P&L and store-by-store comparison — replacing the work of generation + analysis + action. The BPO continues to be useful for tax closing, accessory obligations and complex regulatory compliance. The ROI appears in a network with 3+ stores that pays R$1,200 to R$2,400 per store/month of BPO — replacing the management part frees the BPO for fiscal and reduces total cost of the financial structure."
          }
        },
        {
          "@type": "Question",
          "name": "Can Conta Azul or F360 be used as an alternative for 4-value classification?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Not directly. Conta Azul operates with 2 values in capture (revenue/expense) and the COGS vs expense separation depends on the category in the chart of accounts, without distinct nature on the entry. F360 operates by static registry binding — registered vendor pulls pre-bound chart of accounts, without nature on the transaction. Both leave cross-store coherence in the hand of the operator, and none applies retroactive rule learning of nature across all stores of the group simultaneously."
          }
        },
        {
          "@type": "Question",
          "name": "How long does the classification queue take to empty in a multi-unit network?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "The first session has high cognitive load. Clean PJ-only operator closes in ~30 min with CS together; mixed PF/PJ account or multi-bank can take up to 2 hours. From the second month the queue drops dramatically because the rules created in the first month cover 70 to 85% of recurring entries. In steady state (month 3+) the weekly operation is 5 to 15 minutes per network. A multi-brand franchise-style network operates at this rhythm at the scale of dozens of stores."
          }
        }
      ]
    },
    {
      "@type": "SoftwareApplication",
      "@id": "https://visio.ai/#softwareapplication-pnl",
      "name": "Visio PNL",
      "applicationCategory": "FinanceApplication",
      "operatingSystem": "Web",
      "url": "https://visio.ai",
      "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"
    }
  ]
}

© 2026 Visio.ai