Split payment: cash and working capital impact

Split payment is the mechanism that separates CBS and IBS when a transaction settles. Instead of receiving the full sale amount and paying tax later, the supplier receives the net amount while the tax portion goes to Brazil's Federal Revenue Service and the IBS Management Committee.

The change brings the tax document, payment, and assessment closer together. It also changes an important finance assumption: part of the money that temporarily sits in cash between collection and the tax due date will no longer be available.

This article explains the operating impact without confusing it with the 2026 test phase. Under the Federal Revenue Service's 2026 guidance, CBS and IBS disclosure is informational in 2026 and does not create effective payment of the new taxes when ancillary obligations are met.

The 2026 tests are not the final implementation

In 2026, the priority is adapting documents, master data, rules, and systems to the test environment. Companies can validate information without treating disclosure as a cash outflow. Future implementation depends on regulation, infrastructure, and payment-method participation. Do not turn project assumptions into official dates. Test coexisting channels and use the period to find data, integration, and reconciliation gaps.

What split payment means under Brazil's tax reform

Split payment links settlement of the tax liability to settlement of the transaction. When the customer pays, the flow separates:

• the net amount due to the supplier;
• CBS due to the federal government;
• IBS due to states and municipalities;
• adjustments supported by the applicable calculation model.

Complementary Law 214/2025 established the mechanism. Implementation is gradual and depends on regulation, infrastructure, and participating payment arrangements. Companies should not assume every transaction will move to the same model at once.

Operating models companies should consider

Without anticipating official decisions, companies can test three operating scenarios:

1. Segregation calculated in the payment flow: transaction data makes it possible to identify the tax portion during settlement, and the supplier receives the net amount.
2. Segregation based on transmitted information: the amount to separate follows references originating in the document or company system, requiring validation between the tax calculation and payment.
3. Settlement with a later adjustment: differences, cancellations, or incomplete data create adjustments that must return to accounts receivable, treasury, and tax assessment.

These scenarios do not state which model will apply to each method or when. Cards, boletos, Pix, and transfers may have different timing and identifiers. Architecture should support coexisting flows.

How split payment may affect cash flow

Today, many companies receive the gross sale amount and hold the tax portion until its payment date. Tax is not revenue, but the interval creates temporary liquidity.

With segregation, the supplier receives less available cash at settlement. The effect may include:

• a lower daily operating balance;
• greater working-capital needs;
• changes to investment and redemption schedules;
• more sensitivity to customer delays;
• a need to revise credit limits and minimum cash.

Businesses with thin margins, strong seasonality, or a long financial cycle may feel more pressure. Measure exposure alongside the cash conversion cycle, financial liquidity, and the treasury forecast.

Numerical examples without assuming tax rates

Consider a BRL 100,000 sale and, solely for an internal simulation, assume that BRL 20,000 is segregated. This figure is not a statutory rate. In the current process, BRL 100,000 may reach the account before taxes are paid. In the simulated scenario, BRL 80,000 is available at settlement and BRL 20,000 follows the tax flow. The economic cost of tax already existed; timing is what changes.

If the company held BRL 30,000 and had BRL 90,000 in payments that day, the gross flow would close at BRL 40,000. The segregated scenario would close at BRL 20,000. Additional liquidity would be BRL 20,000 with no revenue change. Simulate by settlement date, channel, entity, and payment method because monthly averages hide the daily trough.

If the business used this interval to pay suppliers, payroll, or other obligations, it will need to replace that liquidity through:

• faster collection;
• supplier term negotiation;
• a liquidity reserve;
• lower inventory;
• a working-capital facility.

Analysis should be weekly and segmented by channel and payment method, not limited to a monthly average.

End-to-end flow

A controlled process begins before the bank:

1. Order and tax document: master data and identifiers link the transaction, billing, and taxes.
2. Collection: accounts receivable associates document, installment, due date, and method.
3. Payment: the customer pays through the selected channel.
4. Settlement: the arrangement processes payment and, when applicable, directs portions under current rules.
5. Return and clearing: the provider reports gross, net, date, fees, and references; the ERP clears the receivable.
6. Reconciliation and exceptions: calculated, segregated, and adjusted amounts are compared; partial payments, cancellations, and refunds enter a queue.

Each stage should preserve an identifier or reliable cross-reference. Similar amounts do not prove that two events belong to the same transaction.

Impact by business model

Retail, e-commerce, and marketplaces: volume, several methods, cancellations, and transfers require transaction-level reconciliation and separation of own amounts, third-party amounts, fees, and taxes.

Recurring services: installments, credits, and grouped payments require links among accounting period, document, and settlement.

B2B and manufacturing: long terms and partial payments require monitoring by installment and legal entity.

Seasonal, thin-margin, or refund-heavy businesses: combine hypothetical segregation, customer delays, concentrated due dates, and later adjustments.

What changes in financial and tax reconciliation

Split payment creates a four-way reconciliation:

1. tax document issued;
2. amount charged to the customer;
3. net amount received;
4. CBS and IBS segregated.

Without connected references, the difference between billing and collection may look like delinquency, a fee, or a bank error. The process must preserve transaction IDs, tax events, adjustments, cancellations, and refunds.

Automated bank reconciliation should connect with the ERP, tax documents, and assessment. Finding a credit on the bank statement is not enough; finance must explain gross, net, and tax amounts.

Minimum controls include totals by document, payment, settlement, and tax; difference reasons; manual approval; change history; and exceptions with a cause, owner, deadline, and evidence.

Required data and integrations

Connect the order, tax document, receivable, payment, settlement, segregated portion, and accounting entry. Preserve identifiers, entity, dates, method, gross, net, taxes, fee, status, and cancellation references.

The ERP, tax engine, accounts receivable, bank, and acquirer need shared keys and states. Define each field's source, reprocessing, and duplicate prevention. In 2026, compare informational values with simulations without recording a nonexistent outflow, and log unlinked transactions.

Metrics to monitor

• percentage of settled value reconciled automatically;
• percentage of transactions with an end-to-end identifier;
• difference between calculated and segregated tax, when applicable;
• count and value of exceptions by reason;
• average time to resolve differences;
• simulated impact on the lowest daily balance and minimum cash;
• incremental working-capital need by scenario;
• unmatched payments, cancellations, and refunds;
• cost and use of short-term facilities;
• test coverage by channel and payment method.

Tax, treasury, and IT responsibilities

Tax validates rules, documents, calculations, and adjustments. Treasury measures liquidity, updates forecasts, sets reserves, and monitors settlement. IT and data maintain integrations, keys, security, monitoring, and reprocessing. Accounts receivable and accounting handle clearing and classification. A business owner coordinates the complete process.

A 30, 60, and 90-day preparation plan

First 30 days: form the cross-functional group, inventory channels, methods, systems, and returns, separate the informational phase from future scenarios, and measure minimum cash.

By day 60: map the flow, standardize identifiers and exceptions, build the 13-week simulation, and define dashboards, owners, and criteria. Hypothetical percentages are not statutory rates.

By day 90: pilot real data in a controlled environment, validate cancellations, refunds, partial payments, and reprocessing. Review minimum cash and contingencies. Produce a prioritized backlog, not a promise of final readiness.

How finance teams can prepare

1. Separate revenue, tax, and available cash

Review reports that treat gross collection as liquidity. Dashboards should distinguish what reached the company from what was segregated.

2. Simulate the effect over 13 weeks

Apply estimated percentages to expected inflows and compare minimum cash before and after segregation. The goal is not to predict the final rate but to measure sensitivity.

3. Map payment methods

Pix, boleto, cards, and transfers may enter different phases and flows. Record volume, settlement time, and available identifiers.

4. Connect tax and treasury

Tax teams validate documents and liabilities. Treasury sees settlement and cash. The design closes only when both teams share the same events.

5. Automate exceptions

Cancellations, partial payments, refunds, and calculation differences should not become side spreadsheets. Create queues with owners, deadlines, and an audit trail.

Readiness checklist

• Does the forecast use gross or tax-net inflows?
• Is exposure known by payment method?
• Does minimum cash reflect lower temporary liquidity?
• Do the ERP, tax document, and bank share identifiers?
• Are cancellation and refund flows defined?
• Do tax and treasury review the same reconciliation?
• Are there alerts for differences between calculated and segregated tax?
• Is there an owner for every field and exception type?
• Does the simulation avoid presenting hypothetical percentages as official rates?
• Does the process clearly distinguish informational testing from an actual cash effect?

Split payment FAQ

Does split payment reduce corporate cash in 2026?

2026 is an adaptation and testing year. When ancillary obligations are met, CBS and IBS are informational and there is no effective collection of the new taxes. Companies should use the period to test systems and simulate future impact.

Does split payment increase the tax burden?

The mechanism changes how and when tax is collected. The tax burden depends on applicable rules; the cash effect comes mainly from reduced liquidity between collection and payment.

How should the gap between billed and received amounts be reconciled?

Reconciliation should separate revenue, segregated tax, fees, and other adjustments. Accounting entries must follow company policy and current regulation.

Will every transaction use split payment?

Implementation is gradual. Models, phases, and participating arrangements depend on regulation and operating infrastructure.

Is there a single date for every payment method?

A single date should not be assumed without official confirmation. Planning should follow regulation and test the coexistence of channels and models during transition.

How can a company simulate impact without knowing the applicable rate?

Use hypothetical ranges only for sensitivity analysis. Present the assumption, segregated amount, minimum balance, and financing need separately. Update the scenario when an official rule applicable to the business is available.

What happens to cancellations and refunds?

They must preserve the reference to the original transaction and follow the treatment established by current rules. Operationally, the company should be able to locate the document, payment, segregation, and adjustment without untracked manual offsets.

What is the main data risk?

Losing the link among the document, receivable, and settlement. A legitimate difference could then be classified as delinquency, a fee, or an error. Consistent identifiers and completeness controls reduce that risk.

Who should lead the project?

Leadership should be shared, with a business owner accountable for the complete process. Tax defines tax requirements, treasury measures liquidity, and IT enables data and integrations.

Conclusion

Split payment turns tax into a settlement event. It strengthens the link between invoice, payment, and assessment, but requires finance to stop treating gross collections as available cash.

Preparation begins with simulation, integration, and reconciliation. In 2026, the goal is to learn from informational disclosure and strengthen data without recording nonexistent payments. For the future, controlled scenarios help size working capital without inventing dates or rates.

Abstra connects banks, ERP systems, tax documents, and rules so teams can monitor gross, net, tax components, and exceptions in one flow.

To assess split-payment impact on your operation, talk to an expert.