The End of the "Float": 5 Structural Shifts from Brazil's Split Payment You Can't Ignore

Brazil’s financial logic is about to change, not incrementally, but structurally. For decades, businesses operated on a simple premise: collect the gross amount, park the tax portion in working capital for a few weeks, and remit when the payment slip fell due. From 2026 onwards, that window closes. Under the Split Payment mechanism, the tax is segregated at the moment of financial settlement, before the net amount even reaches the supplier’s account.

Before diving into the specifics, a few definitions worth pinning down:

• Split Payment: a mechanism by which the payment infrastructure automatically separates, at the point of settlement, the tax portion of a transaction and routes it directly to the government.
• Tax float: the interval between receiving the gross value of a sale and the due date of the corresponding tax remittance, a period during which the tax liability sat, interest-free, as working capital in the company’s account.
• DFe (Electronic Fiscal Document): the umbrella term for electronic invoices and related fiscal documents required under Brazilian tax law for commercial transactions.
• PSP (Payment Service Provider): an institution authorised by the Central Bank of Brazil to operate within payment arrangements: banks, fintechs, and acquirers alike.

---

1. Tax Revenue Is Officially No Longer Your Revenue

One of the deepest conceptual shifts in Brazil’s Tax Reform is the formal consolidation of a principle that, in sound accounting practice, was already supposed to hold: the company is a mere collection agent for certain taxes, not their beneficial owner.

CPC 51, replacing CPC 26 in the treatment of revenue recognition, is explicit on this point. The IBS (Tax on Goods and Services) and the CBS (Federal Contribution on Goods and Services) are “taxes charged on top.” They do not belong to the entity. The company routes them in transit; it never holds them as its own. Two practical consequences follow:

• Reduction in the IRPJ and CSLL tax base: because IBS and CBS are excluded from gross revenue, they are also excluded from the calculation base for corporate income taxes.
• Mandatory net accounting: revenue is recognised net of those taxes from the outset, eliminating the distortion that previously inflated balance sheet figures by including tax amounts that were never the company’s to keep.

The technical guidance from the Federal Accounting Council (CFC) and CPC 51 is unambiguous: “Given the nature of taxes charged on top, IBS and CBS amounts do not form part of the revenue recognised by the entity.”

Cleaner financial statements, yes, but also an immediate comparability problem. Any historical analysis of gross revenue that crosses the pre- and post-reform boundary will need explicit adjustment to remain meaningful.

---

2. The End of the Tax Float: A Real Liquidity Shock

The tax float was, in practice, an interest-free credit line extended by the Brazilian state to every business that collected taxes on its behalf. Under the current model, a company receives the full transaction value, retains the tax portion in its account for the duration of the payment cycle (sometimes several weeks) and remits when the DARF (federal tax payment slip) falls due.

Under Split Payment, that interval disappears. The PSP handling the transaction automatically withholds the tax portion at settlement (via Pix, boleto, or card) and routes it to the government. The comparison below maps the shift:

Phase	Before (Current model)	After (Split Payment)
Receipt	Company receives the gross value	Company receives only the net value
Working capital	Tax portion temporarily funds operations	That indirect financing source disappears
Remittance	Active, via payment slip (DARF/GPS)	Automatic at source, by the bank or PSP

The practical implication for SMEs is straightforward: cash flow projections need recalibrating now, not in 2027. Renegotiating supplier payment terms to align outflows with the new net-receipt rhythm is one of the earliest and most concrete adaptation levers available.

---

3. Mandatory Linkage: The Fiscal Document and the Payment Must Talk to Each Other

Technical Note 2026.001 introduces a strict new requirement: a formal link between every Electronic Fiscal Document (DFe) and the corresponding financial transaction that settles it.

Previously, issuing the invoice closed the supplier’s obligation for that leg of the process. Under the new rules, the supplier must ensure the payment system can identify, at settlement, precisely which invoice a given payment is discharging. Three mechanisms are valid for creating that link:

1. Key at the PSP: providing the DFe’s access key when initiating the financial transaction.
2. Transaction data in the DFe: inserting the transaction identifiers (Pix ID or boleto code) into the designated XML fields (pgtoVinc group).
3. Linkage Event (Event 110300): retroactively associating a completed payment with an already-authorised invoice when the link was not established at the origin.

The liability distribution here is worth understanding clearly: the burden of correction falls on the seller, even when the error originates in the bank’s or acquirer’s infrastructure. A keystroke error in a TED transfer key, for instance, is the supplier’s problem to resolve (via Event 110300), or the buyer’s tax credit gets blocked. A blocked credit strains the commercial relationship and damages the buyer’s compliance score, creating real downstream pressure on the supplier who fails to remediate.

---

4. A Two-Tier Precision Architecture: “Super-Intelligent” vs. “Intelligent”

The Split Payment system operates at two levels of technological precision. The distinction matters operationally, because it determines how much of your capital gets temporarily withheld.

Characteristic	Super-Intelligent Split	Intelligent Split
Credit balance query	Real-time, at point of sale	No query at point of sale
Cash flow impact	Withholds only the net tax due	Withholds the full tax amount
Adjustment	Maximum precision at settlement	Excess returned within 3 business days
Payment rails covered	Dynamic Pix, Boleto, Automatic Pix	TED, TEF, Static Pix, Pix by Key

In the Super-Intelligent flow, the system queries the company’s available tax credit balance in real time and withholds only what is actually owed. In the Intelligent flow, no such query occurs: the full tax amount is withheld and any excess is returned within 3 business days.

For high-volume or high-value operations, that 3-day reimbursement window stops being a minor inconvenience and becomes a material liquidity risk. A company with tight payroll or supplier commitments falling within that window can find itself cash-constrained precisely because of an overpayment it is owed back, a perverse outcome built into the architecture rather than the result of any error.

---

5. The Rise of the Nanoempreendedor and Full Tax Exemption

The Tax Reform introduces a new taxpayer category: the Nanoempreendedor, designed to draw the widest base of the economic pyramid into formal activity through an aggressive fiscal benefit.

• Revenue threshold: up to R$ 40,500 per year, exactly 50% of the current MEI (Individual Microentrepreneur) ceiling.
• Full exemption: entirely exempt from CBS and IBS, provided they do not opt into the standard tax regime.

The competitive implication for established SMEs is direct. Service providers currently operating informally now have a clear, formal entry path into the market with near-zero tax costs. In any segment where price is the primary competition axis, that structural cost advantage will compress margins for businesses operating under a standard tax regime.

---

Conclusion: Automation as a Compliance Requirement

The pilot phase begins in April 2026, with production rollout in May and full mandatory adoption in 2027. TEF (Electronic Funds Transfer) arrangements are first in the implementation queue, where urgency is therefore highest.

One technical detail that deserves more attention than it typically receives: the Integration Manual caps batch processing at 1,000 transactions per API request to the Public Platform. For businesses with high transaction volumes, an ERP that lacks atomic processing capability will generate systemic rejections. That is not a theoretical risk; it is a processing constraint that accumulates at scale.

The broader point is that automation has moved from competitive advantage to compliance baseline. Does your business already know how much working capital it will lose the moment tax starts leaving the account before the payment even arrives?

---

Split Payment testing is scheduled from April 2026, with production entry in May 2026 and mandatory adoption in 2027. Figures and thresholds referenced (R$ 40,500 Nanoempreendedor ceiling, 3-business-day reimbursement window, 1,000-transaction API limit) are based on Technical Note 2026.001 and the public Integration Manual available at that date. Verify against the latest regulatory guidance before operational implementation.