Brazil's Tax Reform (CBS/IBS): Why Allocating Developers Just Became Even More Advantageous for Tech Companies
Brazil's tax reform changes the economics of technology teams: services invoiced by a vendor generate CBS/IBS tax credits, while payroll does not. Learn why developer allocation with Espresso Labs is now a fiscal decision — not just an operational one — for companies and subsidiaries operating in Brazil.

Scope note: everything in this article applies to companies operating in Brazil — Brazilian companies and Brazilian subsidiaries or branches of international groups. If your organization runs engineering, product, or back-office operations through a Brazilian entity, this reform directly affects how your technology spend is taxed.
Brazil's tax reform has stopped being an accountants-only topic and become a CTO topic. Since January 2026, the new CBS and IBS taxes have been appearing on electronic invoices in a test phase, and starting in 2027 they begin effectively replacing five existing taxes (PIS, Cofins, IPI, ICMS, and ISS). For technology companies, this changes two things at once: how your systems need to work and how the math of your operation closes.
In this article, we cover the essentials of the transition and explain why the new tax-credit model makes developer allocation — like the service Espresso Labs provides — a financially smarter alternative than ever for Brazilian operations.
What changes with CBS and IBS, in practical terms
The reform creates a dual VAT: CBS (federal, replacing PIS, Cofins, and IPI) and IBS (state and municipal, replacing ICMS and ISS). Throughout 2026, a 1% test rate applies (0.9% CBS + 0.1% IBS), fully offset against the PIS/Cofins companies already pay — meaning no effective increase in tax burden this year, but immediate compliance obligations: new mandatory fields on electronic invoices, ERP and billing-system adaptations, and correct tax classifications to avoid having invoices rejected.
From 2027 onward, collection becomes effective, with a gradual transition running until 2033. The estimated standard VAT rate lands between 26.5% and 28.6% — significantly above what the services sector pays today under the municipal ISS and the cumulative PIS/Cofins regime.
The core of the new system is full non-cumulativeness: every real of CBS/IBS a company pays when purchasing goods and services becomes an actual financial credit, offsetting the tax due on its own sales.
The asymmetry that changes the decision: invoices generate credits, payroll does not
Here is the detail every technology leader with a Brazilian entity needs to understand: payroll generates no VAT credit. Salaries, social charges, and benefits for an in-house (CLT) team are a "full" cost — there is no CBS/IBS embedded in them to recover.
Services contracted from another company, on the other hand, generate full credits. When you hire allocated developers through a software house, the tax highlighted on the vendor's invoice becomes a credit that reduces the CBS/IBS your Brazilian entity owes on its own revenue.
In practice, this creates a meaningful fiscal asymmetry between two team-composition models:
| In-house team (CLT) | Allocation via software house | |
|---|---|---|
| Consumption-tax treatment | No credit generated | Full CBS/IBS credit |
| Effect on your entity's tax due | No offset | Offsets VAT on your sales |
| Scaling flexibility | Low (hiring/termination cycles) | High (adjust on demand) |
| Labor charges and liabilities | Fully yours | The vendor's |
Before the reform, comparing in-house hiring with allocation was essentially a matter of labor charges and flexibility. With the non-cumulative VAT, a third factor enters: part of what you pay the vendor comes back as a tax credit. For companies under the regular tax regime in Brazil, the effective cost of allocation drops below its nominal cost — something that never happens with payroll.
One important caveat: each company has a different tax framework (regular regime, Simples Nacional, sector-specific reduced rates), and the exact modeling should be done with your tax advisors in Brazil. But the direction is clear: the new system rewards formalized, invoice-based supply chains and offers no equivalent relief for structures heavy on their own payroll. And again — this logic applies to Brazilian entities; it does not extend to teams employed outside Brazil.
The other side of the coin: your systems need to be ready
Beyond the fiscal math, the reform creates an immediate technical demand. Since August 2026, companies under the regular regime can no longer issue electronic fiscal documents without the CBS and IBS fields. And the transition through 2033 means years of running two tax systems in parallel.
That translates into a real engineering backlog:
- ERP and billing-system adaptation for the new fields, rates, and calculation rules — which change year over year during the transition;
- Fiscal integrations querying tax rules in real time, to prevent invoice rejections caused by registration inconsistencies;
- Legacy systems that need updating or replacement — many undocumented, with the original team long gone;
- Pricing and contracts: pricing engines, e-commerce platforms, and SaaS products will need to recalculate prices and display taxes transparently.
Few companies have idle in-house capacity to absorb this volume of work without compromising their product roadmap. It is exactly the scenario where developer allocation solves two problems at once: it delivers the required adaptation and does so through a contracting model the new tax system itself favors.
How allocation with Espresso Labs works
Espresso Labs is a São Paulo-based software house with over 8 years in the market, more than 220 clients served — including companies like Unilever and C&A — and 57+ systems under continuous maintenance. In the allocation model, we provide developers, tech leads, and full squads that work embedded in your team, with the seniority and stacks your project requires.
For international groups, this is also the practical path to reinforce a Brazilian subsidiary's technology capacity without navigating local labor law hiring cycles — while the subsidiary captures the CBS/IBS credits on every invoice.
In the context of the tax reform, that means:
- Speed of adaptation: professionals experienced with fiscal systems, ERPs, and integrations join your project in weeks, not months;
- Elasticity: scale the team up during the adaptation peak (2026–2027) and adjust afterward, with no labor liabilities;
- Fiscal efficiency: all services are invoiced, generating CBS/IBS credits for your Brazilian entity under the regular regime;
- Continuity: beyond the adaptation project, we keep systems running under maintenance SLAs — important in a scenario where fiscal rules will keep changing until 2033.
Conclusion: the reform redraws the build-vs-buy math in Brazil
Brazil's tax reform doesn't just change taxes — it changes the economic logic of how technology teams are assembled in the country. In a system where contracted services generate credits and internal payroll does not, developer allocation stops being merely a flexibility play and becomes a tax-efficiency decision as well.
If your company — or your Brazilian subsidiary — needs to adapt systems to the new fiscal reality, or if you want to revisit your technology team's composition in light of the new rules, talk to Espresso Labs. We help you turn a regulatory obligation into a competitive advantage.
This article is for informational purposes only and does not replace guidance from accounting or tax advisors. The rules described apply exclusively to companies and subsidiaries operating in Brazil. Percentages and deadlines reflect legislation in force as of July 2026 and may be adjusted during the transition period.
Have a similar idea?
Send us a message, we will help you find the best way to bring it to reality