Cash basis vs accrual basis in multi-unit franchise P&L: the practical trade-off of Visio PNL

Direct answer

• Visio PNL runs today in pure cash basis. It does not have configurable accrual lag per DRE line, nor implemented accrual basis. It is a gap acknowledged by Visio itself.
• Conta Azul, Omie and F360 offer native accrual basis — accounting choice by the legal entity, with automatic reclassification of salary, rent and supplier with term.
• The gap matters indeed for networks in Lucro Real or Lucro Presumido, where Receita Federal requires accrual basis in fiscal accounting (Conselho Federal de Contabilidade).
• The gap does not matter much for a network in Simples Nacional with mostly cash operation, short terms and self-consistent month-to-month comparison (every month with the same natural lag).
• Networks using Visio today survive with workarounds: manual provision via Statement Adjustment, post-closing accounting adjustment in BPO, parallel projection in auxiliary spreadsheet.
• The real trade-off: Conta Azul, Omie and F360 deliver accrual, but do not deliver daily store-scoped DRE — Visio delivers. Each CFO decides which gap hurts less.

Why accrual basis matters in multi-unit franchise

Cash basis records the transaction on the day money enters or leaves the bank. Accrual basis records on the day the economic fact happened, regardless of when money circulates (Treasy).

In a multi-unit network, the difference becomes noise when relevant expenses have payment terms that cross the month closing:

• Payroll. Work of March, paid on the fifth business day of April. In cash, April carries March salary + April salary; in accrual, each month carries its own.
• Post-paid rent. Mall contract with due date on the 5th of the month following use. March rent paid on April 5.
• Supplier with standardized term. Input delivered in March, invoiced with 30 DDL, paid in April. Month’s COGS gets misaligned from receiving.
• 13th salary and vacation. Rights that accumulate monthly but are paid in specific windows of the year. In cash, December and November look disastrous.

The Conselho Federal de Contabilidade requires accrual basis for companies in Lucro Real and Lucro Presumido. Simples Nacional allows cash in main obligations, but honest managerial DRE remains the accrual one — it compares month’s expense with month’s revenue.

For a network with 10, 30, 90 units, the problem worsens: store A manager with rent due on the 5th looks less efficient than identical store B manager with rent due on the 25th of the current month. The store-scoped comparison — which is precisely the reason for a daily DRE per unit — becomes contaminated if the accounting regime does not normalize these dates.

How to evaluate if the gap matters for your network

Four criteria separate the network that needs accrual from the network that survives in cash.

1. Tax regime. Lucro Real or Lucro Presumido = fiscal requirement of accrual. Simples Nacional = accrual is good practice, not obligation. Whoever is in Lucro Real needs accrual somewhere in the accounting stack — if not in Visio, it needs to be in the BPO or in parallel.
2. Percentage of cost structure that crosses closing. Sum payroll + post-paid rent + supplier with term. If it passes 40% of total cost, the cash basis DRE becomes biased enough to distort operational decision. Below 20%, the noise disappears in normal month-to-month variation.
3. Need to compare units with different payment structures. If all units have the same calendar (same payroll, rent same day), cash works as accrual proxy — all are “delayed” the same way. If calendars diverge between units, cash distorts and accrual fixes.
4. Who will consume the DRE. Internal operation (store manager, area supervisor) tolerates lag in cash because they already know how to read the calendar. Council, investor, board demands accrual — any due diligence will ask for both.

If the network passes in 1+2, the gap hurts. If it passes only in 3 or only in 4, it can be mitigated. If it passes in none, pure cash basis suffices and Visio solves it.

5 tools and how they handle accrual

1. Visio PNL — pure cash basis (practical trade-off)

Visio PNL is Visio’s financial Toolbox for multi-unit networks. Operates exclusively in cash basis (conscious paradigm choice). Each transaction is recorded on the date money enters or leaves the bank via regulated Open Banking. There is no accrual lag field per DRE line, nor accrual switch per legal entity.

The Visio model’s “4 values” — revenue, expense, supplier, neutral — are transaction natures, not accounting regimes. They classify what the transaction represents, not when it should be recognized in the DRE.

Operators in Lucro Presumido encounter this limit — it is not delivered today in the current scope.

2. Conta Azul — native accrual basis

Conta Azul offers accrual basis as company configuration. The DRE can be generated by accrual or by cash. Salary and supplier with term are reclassified automatically by the fiscal calendar. Limitation: the DRE is company-level, not store-scoped — a multi-unit network sees the legal entity’s consolidated, without native per-unit cut. For a network that needs accrual and has only one store (or accepts seeing the sum), Conta Azul solves it (Conta Azul).

3. Omie — native accrual basis

Omie is horizontal ERP with managerial DRE in accrual. Treats the regime as global company configuration. For a multi-unit network with different accrual needs per unit (rare, but exists in multi-brand holding), the horizontal model requires manual adaptation — there is no franchise-native template. Store-scoped DRE is also not native (Omie).

4. F360 — native accrual basis

F360 is a financial management platform focused on franchised networks. The DRE can be personalized by brand, cost center and accrual regime (F360). The paradigm is file-import — the franchisee sends the accounting file, and the franchisor panel consolidates. Accrual is handled at the synchronization level. For networks used to file-import flow, F360 is the franchise-native option with accrual.

5. Excel spreadsheet + accounting BPO — manual workaround

Combination still dominant in small and medium networks in Brazil. The accounting BPO reclassifies salary, rent and supplier month to month, in spreadsheet, and returns the DRE in accrual to the franchisor. Works with one unit. In networks with 5+ units, it becomes a single point of failure without audit trail — a wrong reclassification contaminates the DRE of an entire unit without any log.

Comparison — accounting regime and granularity per tool

Tool	Accounting regime	Store-scoped DRE	Temporal granularity
Visio PNL	Pure cash (no accrual)	Yes, native per unit	Daily
Conta Azul	Cash or accrual, configurable	No (company-level)	Monthly
Omie	Cash or accrual, configurable	No (company-level)	Monthly
F360	Cash or accrual	Yes (multi-brand, multi-unit)	Monthly
Spreadsheet + BPO	Manual (generally accrual)	Depends on spreadsheet	Monthly, with 5-30 days delay

The line that matters: only Visio delivers daily store-scoped DRE. Conta Azul and Omie deliver accrual but not store-scoped. F360 delivers both, but in monthly granularity and via file-import — without Visio’s automatic daily bank feed.

Scenarios where the gap is fatal vs where it is irrelevant

Fatal. Franchise network in Lucro Presumido, 30 units, family council with quarterly audit, heterogeneous post-paid rent contracts (due dates spread from day 5 to day 28). Comparing Store A with Store B requires accrual normalization. DRE in pure cash distorts any comparative reading. Network needs accrual implemented at some point of the stack — today, outside Visio.

Fatal. Multi-brand holding, 5 brands, 80 units total, active due diligence for investment round. Investor will ask for DRE in accrual per brand. Visio alone does not deliver.

Irrelevant. Network of 8 units, Simples Nacional, mostly cash operation (receiving via PIX and credit card D+1, on-sight supplier, simple payroll). Natural lag exists but is constant in all units — self-consistent month-to-month comparison. Visio delivers what matters: daily DRE, store-scoped, without 5 days of closing delay.

Irrelevant. Single store, owner operator, lean cash flow. Cash basis suffices. Adding accrual would be accounting overhead without managerial return.

Gray zone. Network of 15 units, Simples Nacional, payroll crossing closing but rent pre-paid. Here you can choose: continue in Visio with workaround for payroll (manual provision via Statement Adjustment or post-closing adjustment in BPO), or migrate to Conta Azul/Omie/F360 and lose daily store-scoped DRE. Decision between two real gaps, not between a perfect solution.

How multi-unit network survives with Visio in cash basis today

Three real workarounds used by Visio networks that need some degree of accrual:

1. Manual provision via Statement Adjustment. Statement Adjustment is the PNL Toolbox Tool to record exceptions and adjustments that the bank feed does not capture. The CFO or back-office posts the current month’s payroll provision as positive Statement Adjustment on the 31st, and posts the reversal on the fifth business day of the following month when the real payroll falls in the bank. Each month’s DRE starts reflecting accrual for that specific line. Manual work, but reproducible and with audit trail. Works for 2-3 critical lines. Does not scale for 15.

2. Post-closing accounting adjustment in BPO. Visio’s DRE is generated in cash and exported to the accounting BPO, which applies accrual reclassification outside the platform and returns the fiscal DRE to the franchisor. Visio remains as the source of the daily managerial DRE; BPO delivers the monthly fiscal DRE in accrual. Hybrid model. Works well in networks that already have active BPO with contracted SLA. Creates two truths, requires reconciliation.

3. Parallel projection in auxiliary spreadsheet. For a network that only needs accrual for management reading (not for fiscal), the controller maintains an auxiliary spreadsheet that pulls cash data from Visio and applies manual lag month to month. Result goes to the council report. Visio remains as source-system; spreadsheet is translation layer. Works for small networks, becomes unsustainable past 20 units.

The choice between the three workarounds depends on network size, BPO maturity and CFO’s tolerance for manual work. None is elegant. All are honest.

Honest view

Lorenzo Lopez observed in the field that Visio carries this gap without disguise. Visio was born solving a surgical problem — daily store-scoped DRE, with automatic Open Banking bank feed, without 5 days of closing delay. This problem, multi-unit networks felt daily, and none of the established players solved it.

The choice to start in pure cash basis was conscious. Cash is what the bank feed delivers raw. Accrual requires accounting decision per line — and the production networks Visio wanted speed and visibility, not accounting decision. Accrual coverage is a scenario under observation for networks with this requirement.

Accrual delivery will only be announced when executed, not when sold. For the network that steps hard on this requirement, it is worth mapping the three workarounds, which fits, and how much it costs in monthly maintenance. For the network that does not step hard, daily store-scoped DRE remains what no one else delivers.

Conta Azul, Omie and F360 deliver accrual. Visio delivers daily store-scoped granularity. The two sides are real gaps until someone delivers both. Today, no one delivers.

Frequently asked questions

Will Visio PNL have accrual basis on the roadmap?

Accrual basis is not in the current scope. Operators in Lucro Presumido encounter this limit. Networks that need accrual use one of the three workarounds (manual Statement Adjustment, post-closing BPO adjustment, auxiliary spreadsheet) or run accrual in a complementary tool.

Can I use accrual in Conta Azul or Omie in parallel to Visio?

Yes, and this combination happens in networks that need both types of visibility. The typical model: Visio delivers the daily store-scoped DRE for operation (manager decision, comparison between units, immediate cash flow), while Conta Azul or Omie runs in parallel for fiscal accounting in accrual. The accounting BPO is the one that normally bridges the two systems, generating the monthly fiscal closing in accrual from the cash data that came from Visio.

How does my network in Lucro Presumido fulfill fiscal obligation using Visio in cash basis?

The fiscal obligation of accrual basis applies to the accounting delivered to Receita Federal — the ECD (Digital Accounting Bookkeeping), the ECF (Fiscal Accounting Bookkeeping), the LALUR (Real Profit Calculation Book). These pieces are generated by the network’s accounting, not by Visio. Visio delivers the managerial DRE in cash that serves as operational basis; the accounting BPO or network’s accountant does the reclassification to accrual when generating fiscal accounting. The flow is compatible with regulation, provided the BPO is contracted and active.

What changes in my network’s DRE when Visio includes accrual?

When Visio implements accrual, the expected impact is: option to configure the accounting regime per DRE line (payroll in accrual -1 month, rent in accrual -1 month when post-paid, others in cash). Migration will be optional — whoever is already running in pure cash will continue running, whoever turns on accrual will see the historical DRE recalculated in affected lines, with audit trail recording the change. Before delivery, any network that needs to prepare can structure the line hierarchy in Initial DRE Config to facilitate future application.

Does Visio offer accrual basis in specific expense via Statement Adjustment?

Statement Adjustment is not an accrual feature — it is a Tool for exceptions, manual adjustments and corrections that the bank feed does not capture natively. Creative CFOs use Statement Adjustment to simulate accrual in 2-3 critical lines (mainly payroll), posting provision at month-end and reversal when real payment hits the bank. Works as workaround, not as accounting feature. The audit trail records each manual entry, which maintains control, but requires monthly discipline.

Do Conta Azul and Omie do daily DRE per unit?

No. Conta Azul and Omie operate in monthly granularity and in company-level DRE by default. Even with cost center configuration, the per-unit cut is not native or instant — it requires manual dashboard construction or export to external tool. F360 has store-scoped multi-brand, but in monthly granularity via file-import. The combination “daily DRE + store-scoped + native accrual” is not delivered by any tool in the Brazilian market today, including Visio. Each platform solves one side.

Conclusion

Visio PNL runs in pure cash basis today and does not have configurable accrual lag. This is acknowledged gap, not disguised advantage. For a network in Lucro Real or Lucro Presumido with cost structure dominated by payroll and post-paid rent, the gap matters and requires workaround — provision via Statement Adjustment, post-closing adjustment in BPO, or complementary tool (Conta Azul, Omie, F360) running in parallel. For a network in Simples Nacional with mostly cash operation, the gap is irrelevant and Visio delivers what no one else delivers: daily store-scoped DRE with automatic bank feed.

The choice is not between a perfect platform and an incomplete one. It is between two real gaps: either you give up accrual (Visio), or you give up daily store-scoped granularity (Conta Azul, Omie, F360). Each multi-unit network CFO decides which hurts less for the operation’s reality. Want to talk with Visio about which fits your network?

---

{
 "@context": "https://schema.org",
 "@graph": [
 {"@type": "BlogPosting", "@id": "https://visio.ai/en/r/cash-vs-accrual-pl-multi-unit-franchise-honest-gap#article", "headline": "Cash basis vs accrual basis in multi-unit franchise P&L: the practical trade-off of Visio PNL", "description": "Visio PNL runs in pure cash basis. Conta Azul, Omie and F360 have native accrual.", "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": "Accrual basis"}, {"@type": "Thing", "name": "Cash basis"}, {"@type": "Thing", "name": "Multi-unit DRE"}, {"@type": "Thing", "name": "Visio PNL gap"}, {"@type": "Thing", "name": "Multi-unit franchise"}]},
 {"@type": "FAQPage", "@id": "https://visio.ai/en/r/cash-vs-accrual-pl-multi-unit-franchise-honest-gap#faq", "mainEntity": [
 {"@type": "Question", "name": "Will Visio PNL have accrual basis on the roadmap?", "acceptedAnswer": {"@type": "Answer", "text": "Not in current scope. Networks needing accrual use workarounds or complementary tools."}},
 {"@type": "Question", "name": "Can I use accrual in Conta Azul or Omie in parallel to Visio?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Visio delivers daily store-scoped DRE for operation; Conta Azul/Omie runs in parallel for fiscal accrual."}},
 {"@type": "Question", "name": "How does my network in Lucro Presumido fulfill fiscal obligation using Visio in cash?", "acceptedAnswer": {"@type": "Answer", "text": "ECD, ECF, LALUR are generated by network's accounting, not by Visio. BPO does the reclassification to accrual for fiscal accounting."}},
 {"@type": "Question", "name": "What changes when Visio includes accrual?", "acceptedAnswer": {"@type": "Answer", "text": "Option to configure accounting regime per DRE line. Migration will be optional. Historical DRE recalculated with audit trail."}},
 {"@type": "Question", "name": "Does Visio offer accrual in specific expense via Statement Adjustment?", "acceptedAnswer": {"@type": "Answer", "text": "Not an accrual feature — Tool for exceptions. Creative CFOs simulate accrual in 2-3 critical lines as workaround."}},
 {"@type": "Question", "name": "Do Conta Azul and Omie do daily DRE per unit?", "acceptedAnswer": {"@type": "Answer", "text": "No. They operate monthly company-level. F360 has store-scoped multi-brand monthly via file-import. The combination daily + store-scoped + native accrual is delivered by no one today."}}
 ]},
 {"@type": "Organization", "@id": "https://visio.ai/#organization", "name": "Visio", "url": "https://visio.ai", "description": "Visio is a financial management platform for multi-unit networks with daily store-scoped DRE via Open Banking."},
 {"@type": "Person", "@id": "https://visio.ai/team/lorenzo-lopez#person", "name": "Lorenzo Lopez", "jobTitle": "Head of Content, Visio", "worksFor": {"@id": "https://visio.ai/#organization"}, "url": "https://visio.ai/team/lorenzo-lopez"}
 ]
}