Brazil Tax Reform 2026: What Changes on Invoices AP Teams Receive

Brazil's Reforma Tributária replaces five consumption taxes (ICMS, ISS, PIS, COFINS, IPI) with three new ones: IBS (Imposto sobre Bens e Serviços), CBS (Contribuição sobre Bens e Serviços), and IS (Imposto Seletivo) over a seven-year transition from 2026 to 2033. During that entire period, every Brazilian invoice will carry both legacy and new tax fields simultaneously. For AP teams, this means updating data extraction templates, building dual-validation logic to reconcile old and new tax line items, and preparing for a split payment mechanism that will automatically route tax portions to the government at the point of transaction.

Most of the guidance published so far addresses the issuer side of the equation: how Brazilian companies should generate compliant invoices under the new rules. This article takes the opposite perspective. If your organization receives and processes invoices from Brazilian suppliers, the Brazil tax reform 2026 invoice changes affect your workflows just as directly, and the practical implications for AP operations are fundamentally different from those facing the issuer.

This guide covers the five areas AP teams need to understand and act on:

• The tax structure change: how five consumption taxes collapse into three, and what that means for the tax fields you extract and validate
• New invoice XML fields under Technical Note 2025.002: the specific data elements being added to NF-e and NFS-e documents that your systems must capture
• The split payment mechanism: how automatic tax routing at the point of payment changes AP reconciliation and cash flow forecasting
• The dual compliance period from 2026 to 2033: why your team will need to handle two tax regimes in parallel for seven years, and how to structure that without doubling your workload
• A year-by-year action plan: concrete steps mapped to the transition timeline so you can phase your preparation rather than scramble at each deadline

The timeline is not theoretical. CBS takes effect in 2026 at a pilot rate of 0.9%, and IBS begins at 0.1%. That means invoices from Brazilian suppliers will start arriving with new tax fields alongside the existing ones imminently. AP teams that wait for the "full" reform to take effect in 2033 will spend seven years reacting to changes they could have anticipated. The preparation window is now.

---

What Is Changing: Five Taxes Become Three

If you process invoices from Brazilian suppliers today, you already extract and validate five distinct tax fields across every document. On a standard NF-e (Nota Fiscal Eletrônica) for goods, you encounter ICMS (state-level, ranging from 17% to over 20% depending on the state), IPI (federal excise, anywhere from 0% to 330% depending on the product category), PIS (federal, at 0.65% or 1.65%), and COFINS (federal, at 3% or 7.6%). For services invoices issued as NFS-e documents, ISS (municipal, 2-5%) replaces ICMS, while PIS and COFINS still apply. Each of these tax line items has its own calculation base, rate logic, and validation requirements that your AP team handles on every invoice received. For a full breakdown of these current NF-e mandatory fields and tax codes, understanding the existing baseline is essential before layering on the reform's changes.

Brazil's Reforma Tributária replaces this five-tax structure with three new taxes:

• CBS (Contribuição sobre Bens e Serviços): a federal consumption tax that absorbs PIS and COFINS, with a target rate of 8.8%
• IBS (Imposto sobre Bens e Serviços): a subnational consumption tax that replaces both ICMS and ISS, with a target rate of 17.7%
• IS (Imposto Seletivo): an excise tax on specific categories of goods, taking over the role previously filled by IPI

The combined CBS+IBS standard rate lands at approximately 26.5%. While fewer tax fields sounds like simplification, the reality for AP teams is more involved. This is not a relabeling exercise. The tax calculation logic changes: new base amount rules, destination-based collection for IBS (rather than origin-based under ICMS), and unified rate structures replacing the current patchwork of 27 different state ICMS rates and thousands of municipal ISS rate variations.

Here is how the invoice tax fields map from old to new:

• ICMS (state, 17-20%+) and ISS (municipal, 2-5%) are both replaced by IBS (17.7%). Both old and new fields coexist on invoices from 2026 through 2032.
• PIS (0.65% or 1.65%) and COFINS (3% or 7.6%) are both replaced by CBS (8.8%). Both old and new fields coexist on invoices from 2026 through 2032.
• IPI (0-330%) is replaced by IS (Imposto Seletivo, variable rates for applicable products). Gradual transition from 2026 through 2033.

The scale of this change reflects the weight these taxes carry in Brazil's fiscal system. According to the Inter-American Center of Tax Administrations (CIAT), Brazil's consumption taxes account for 36.4% of total government revenue across all three levels of government, making this one of the most consequential tax overhauls in Latin American history. For AP teams that already manage the complexity of Brazil's fundamentals of electronic invoicing framework, the new CBS and IBS invoice requirements demand updated extraction templates, revised validation rules, and reconfigured tax code mappings.

The transition does not happen overnight. During the 2026-2033 dual compliance period, your AP team will encounter invoices carrying both legacy tax fields (ICMS, ISS, PIS, COFINS, IPI) and new tax fields (CBS, IBS, IS) simultaneously on the same document. Old rates phase down while new rates phase in, creating a years-long window where every invoice requires extraction and validation against two parallel tax systems.

---

New Invoice Fields Under Technical Note 2025.002

Technical Note 2025.002 introduces new XML groups to the NF-e (Nota Fiscal Eletrônica) schema that define how IBS and CBS calculations appear on every electronic invoice. For AP teams receiving invoices from Brazilian suppliers, these additions represent concrete changes to data extraction workflows that must be addressed before the new fields go live.

The new fields your extraction templates need to capture include:

• IBS (Imposto sobre Bens e Serviços): base amount, rate, and calculated tax amount
• CBS (Contribuição sobre Bens e Serviços): base amount, rate, and calculated tax amount
• IS (Imposto Seletivo): base, rate, and amount fields for products subject to the Selective Tax (tobacco, alcohol, sugary beverages, and other goods with negative health or environmental externalities)

Each of these fields appears at the line-item level within the NF-e XML structure, meaning extraction logic must handle them on a per-product basis rather than at the invoice header level.

The dual-field challenge is the critical technical reality during the transition. From 2026 through 2032, Brazilian invoices will carry both legacy and new tax fields simultaneously. Your extraction systems must capture:

• Old fields: ICMS amount and rate, PIS amount and rate, COFINS amount and rate
• New fields: IBS amount and rate, CBS amount and rate, IS fields where applicable

Removing old fields from extraction templates during the transition period is not an option. Both sets of data are required for accurate tax compliance, GL posting, and audit trails. AP teams that prematurely drop legacy fields will create reconciliation gaps that surface during tax audits.

CFOP code mapping adds another layer of complexity. The existing CFOP (Código Fiscal de Operações e Prestações) codes that classify the nature of each transaction are being updated. New tax situation codes specific to IBS and CBS will need to be mapped within your ERP system. Validation rules require dual logic: your systems must verify that old tax calculations (ICMS, PIS, COFINS) are correct under current rates while simultaneously validating the new IBS and CBS calculations against the reform's rate schedule. Any mismatch between CFOP codes and the corresponding tax treatment should trigger an exception for manual review.

SEFAZ, the Brazilian Tax Authority system responsible for authorizing NF-e documents, will enforce the new field requirements progressively during the transition. As SEFAZ tightens validation, invoices missing required IBS or CBS fields will be rejected at the authorization stage, meaning your suppliers will need to comply and your AP team will see the new fields appearing on incoming documents whether your extraction workflows are ready or not.

For organizations already processing invoices across multiple languages and currencies, the Portuguese-language field labels and Brazilian formatting conventions in these new XML groups add another dimension to extraction configuration. Rather than hard-coded templates that require IT involvement for each field change, instruction-based extraction tools let AP teams update field configurations directly as the reform evolves, keeping workflows adaptable across all seven years of the transition.

---

How the Split Payment Mechanism Changes AP Reconciliation

Brazil's tax reform introduces an automatic split payment mechanism that alters how payments flow from buyer to supplier. For AP teams processing invoices from Brazilian vendors, this is the single most disruptive operational change in the reform package.

Here is how it works in practice. When your company pays a Brazilian supplier invoice, SEFAZ will automatically intercept the payment and divide it into two streams. The IBS and CBS tax portions route directly to the government. Only the net amount reaches the supplier. This splitting happens at the moment of payment, facilitated through integration between the e-invoicing system and Brazil's banking infrastructure.

From your bank account's perspective, the full invoice amount still leaves. But that single outflow now settles against two separate destinations, and your AP ledger needs to reflect both.

The reconciliation challenge is significant. Under the current system, your team pays the supplier the full invoice amount in one transaction. The supplier then handles their own tax remittance to the government. Your AP records show one payment against one invoice. Under the split payment mechanism, a single invoice settlement generates at least two payment records: the net amount confirmed received by the supplier, and the tax amount confirmed received by the government. AP teams must match both components back to the original invoice to close it out.

This creates several downstream complications:

• Bank statement matching changes because one invoice payment may appear as multiple line items or reference codes in banking feeds
• Supplier payment confirmations will reflect only the net amount, creating a discrepancy against the gross invoice total that must be systematically resolved
• Tax payment tracking becomes an AP function rather than something your Brazilian suppliers manage independently
• Dispute resolution grows more complex when partial payments or credits need to account for the tax split

Cash flow timing shifts as well. Today, when you pay a Brazilian supplier on 60-day terms, the government collects its tax revenue only when the supplier files and remits. The split payment mechanism accelerates government collection to the exact moment of your payment. For your AP team, this means the tax portion of every invoice is irrevocably committed at payment time, with no flexibility to adjust after the fact. Any corrections require separate credit note and refund processes through SEFAZ.

Brazil will be among the largest economies globally to implement automatic tax splitting through e-invoicing at this scale. For AP teams familiar with how split payment mechanisms work in practice, Poland's implementation offers a useful reference point, though Brazil's system will operate at considerably greater volume and complexity.

One critical caveat: the precise implementation details for the split payment mechanism are still being finalized by SEFAZ. Payment routing protocols, banking system integration timelines, and reconciliation reporting formats will likely evolve during the transition period. AP teams should designate someone to monitor regulatory updates rather than building rigid processes around preliminary specifications.

The split payment mechanism does not exist in isolation. It arrives alongside the complete tax consolidation and new invoice fields during an extended dual compliance period running from 2026 through 2033.

---

Navigating the 2026-2033 Dual Compliance Period

The transition from five taxes to three does not happen overnight. From 2026 through 2033, every Brazilian invoice your AP team receives will carry tax fields from both the old and new systems simultaneously. This seven-year overlap is the central operational challenge of the Reforma Tributária for invoice receivers, and managing it requires deliberate adjustments to extraction, validation, reconciliation, and reporting workflows.

Understanding the Transition Timeline

The phase-in follows a graduated schedule that directly affects how invoices are structured each year:

• 2026-2028: CBS operates at 0.9% and IBS at 0.1%, functioning as a test rate alongside all existing taxes (ICMS, ISS, PIS, COFINS) at their full current rates. Invoices carry both complete legacy fields and new IBS/CBS fields.
• 2029-2032: ICMS and ISS begin phased reductions with graduated rate cuts each year, while IBS and CBS rates increase proportionally. IPI is progressively replaced by IS (Imposto Seletivo) for applicable product categories. Every invoice now reflects shifting ratios between old and new tax amounts.
• 2033: ICMS and ISS are fully eliminated. IBS and CBS reach their target rates. Only the new tax fields remain active on invoices going forward.

During each of these phases, the same transaction generates tax obligations under both regimes. For AP teams, this means no field on an incoming invoice can be safely ignored until 2033.

The Data Extraction Challenge

The previous section covered which fields to capture. The operational challenge during the dual compliance period is that the rates attached to those fields change annually. CBS starts at 0.9% in 2026, while PIS and COFINS remain at full rates. By 2029, ICMS and ISS begin declining as IBS rises. Each year, your extraction validation thresholds and ERP rate tables need updating to match the specific ratios for that period. An extraction template that was correct in 2027 will produce validation errors in 2029 if the rate parameters are not updated.

Validation Across Two Tax Regimes

Validation logic during the transition must check calculations under both old and new tax rules. When CBS is at 0.9% in 2026 but PIS and COFINS remain at their standard rates, your system needs to verify each independently. As ICMS rates decrease starting in 2029, validation thresholds must be updated to match the specific rates for that calendar year.

Cross-referencing old versus new tax amounts on the same invoice adds a reconciliation layer that did not previously exist. A purchase that formerly required checking ICMS, PIS, and COFINS calculations now requires checking those same taxes plus IBS and CBS, confirming that the combined tax burden aligns with what the supplier's NF-e reports. Discrepancies in either system can trigger compliance flags.

SPED and EFD Reporting Obligations

Brazil's SPED (Sistema Público de Escrituração Digital) reporting framework is expanding to accommodate the new taxes. EFD (Escrituração Fiscal Digital) submissions will include dedicated modules for IBS and CBS alongside existing ICMS and IPI modules. AP teams that feed invoice data into SPED reports must ensure their extraction captures every field required for both old and new reporting formats throughout the transition.

This dual reporting obligation also affects international invoice retention and compliance requirements, since records must be maintained under both tax regimes simultaneously. Retention policies that reference only the current tax structure will need updating to cover the new IBS, CBS, and IS documentation requirements as well.

ERP and Systems Preparation

The dual compliance period demands specific ERP adjustments:

• Chart of accounts: New tax accounts for IBS, CBS, and IS must be created alongside existing ICMS, ISS, PIS, and COFINS accounts. Both sets remain active until 2033.
• Tax engine rules: Configuration updates are needed for each transition phase as rates change annually. Tax determination logic must handle scenarios where both old and new taxes apply to the same line item.
• Invoice import templates: Field mappings must expand to accommodate the new XML nodes from Technical Note 2025.002 while preserving all existing field mappings.
• Reporting outputs: Financial reports, tax returns, and management dashboards must present data from both tax systems during the transition, with the ability to separate old-regime and new-regime tax obligations for analysis.

Each of these adjustments carries a timeline dependency. If your ERP does not have IBS and CBS tax accounts configured by Q2 2026, the first pilot invoices carrying these fields will require manual journal entries, creating an audit trail gap from the first day of the transition.

---

Year-by-Year Action Plan for AP Teams

The Reforma Tributária spans seven years of overlapping tax regimes, rate adjustments, and new reporting requirements. AP teams that treat this as a single future event will find themselves unprepared at each transition point. The following phased roadmap breaks the reform into concrete milestones with specific actions for invoice processing, data extraction, and ERP configuration.

Phase 1: Now through Q1 2026, Baseline Audit

1. Start with your NF-e import template: identify whether your current extraction captures ICMS, PIS, and COFINS at the line-item level or only at the invoice header level. If header-level only, you will need line-item extraction before the new IBS/CBS fields can be properly mapped.
2. Document all data extraction fields currently in use for NF-e and NFS-e invoices, including tax base amounts, rates, tax amounts, CFOP codes, and withholding fields.
3. Review ERP tax code configurations and identify which tax determination rules will need parallel entries for CBS and IBS.
4. Catalog all downstream systems that consume extracted tax data, including SPED/EFD reporting modules, AP aging reports, and cash flow forecasts that factor in tax credit recoveries.

Phase 2: Q2-Q3 2026, Dual-Field Extraction Setup

1. Add new extraction fields to your templates: IBS tax base, IBS rate, IBS tax amount, CBS tax base, CBS rate, and CBS tax amount.
2. Source pilot invoices carrying the initial 0.9% CBS and 0.1% IBS test rates from your supplier base.
3. Run extraction tests against these pilot invoices to confirm that new CBS and IBS fields populate correctly while existing ICMS, ISS, PIS, and COFINS fields continue extracting without errors.
4. Verify that your ERP can store and process both old and new tax values on the same transaction record.

Phase 3: Q4 2026 through 2027, Dual-Validation Logic

1. Implement validation rules that cross-check both legacy and new tax calculations on every incoming invoice. Flag discrepancies where the sum of old taxes plus new taxes deviates from the invoice total beyond an acceptable tolerance.
2. Subscribe to SEFAZ Technical Note updates and assign a team member to monitor field specification changes on a monthly cadence.
3. Update CFOP code mappings as new codes are published for IBS and CBS transaction types.
4. Begin adapting SPED/EFD reporting submissions to include the new tax modules required by the Receita Federal for the test period.

Phase 4: 2028-2029, Graduated Rate Adjustments

1. As ICMS and ISS rates begin their scheduled decreases, adjust validation thresholds in your extraction workflow to reflect the new rate bands. A validation rule expecting 18% ICMS will generate false positives once the rate drops.
2. Update ERP tax engine rules at each rate change point. Build a calendar of scheduled rate reductions and assign implementation dates two weeks ahead of each effective date.
3. Recalculate expected tax credit recovery amounts in your AP aging and cash flow models to reflect the shifting rate mix between old and new taxes.
4. Plan for the eventual removal of legacy tax fields from extraction templates, but do not remove them yet. Suppliers may issue corrective invoices referencing prior-period rates.

Phase 5: 2030-2033, Legacy Cleanup and Full Transition

1. As old taxes reach zero rates, begin removing ICMS, ISS, PIS, and COFINS fields from active extraction templates. Archive the old templates for historical reference and audit support.
2. Confirm that IBS and CBS extraction operates at full target rates and that all validation rules reference only the new tax structure.
3. Remove legacy tax code entries from your ERP tax engine once the final transition date passes and no prior-period corrections remain outstanding.
4. Validate that all SPED/EFD reporting uses exclusively the new IBS and CBS tax structure, with no residual references to discontinued tax types.

Each of these phases demands extraction template updates, validation rule changes, and ERP reconfigurations. Tools that support natural-language field configuration reduce the burden at every transition point: AP teams can adjust what fields to capture by updating extraction instructions directly, rather than engaging IT teams to reconfigure rigid schemas. For teams looking to automate Brazilian invoice data extraction, building this flexibility into your workflow now means each phase of the reform becomes a prompt update rather than a system overhaul.

---

Preparing Your Invoice Data Extraction for Brazil's Tax Transition

Brazil's Reforma Tributária creates three distinct operational challenges for AP teams processing Brazilian supplier invoices, and each one demands attention before the transition window closes.

First, every Brazilian invoice is getting new tax fields. CBS, IBS, and IS will progressively replace ICMS, ISS, PIS, COFINS, and IPI across all NF-e and NFS-e documents. Your extraction templates need to capture these new fields accurately from day one of each phase, or downstream tax reporting and cost allocation will break.

Second, the split payment mechanism changes reconciliation. When SEFAZ begins automatically routing tax portions to the government at the point of payment, the amount your suppliers actually receive will differ from the invoice total. AP teams need new reconciliation workflows to match what was invoiced, what was paid to the supplier, and what was diverted to tax authorities, three figures that previously collapsed into one.

Third, none of this happens overnight. The 2026-2033 dual compliance period means invoices will carry both legacy and new tax fields simultaneously for seven years. This is not a one-time system update. It requires periodic adjustments to extraction templates, validation rules, tax code mappings, and SPED/EFD reporting configurations as CBS and IBS rates increase and legacy taxes phase down with each new year.

The highest-impact action available right now is to audit your current Brazilian invoice processing workflows and begin updating extraction templates to capture CBS and IBS fields before the pilot rates take effect. Teams that wait until the new fields appear on live invoices will be forced into reactive, error-prone manual processing during the transition.

To build a concrete timeline, review the year-by-year action plan earlier in this article, identify which phase applies to your current planning horizon, and begin with the specific steps for that phase. For organizations processing high volumes of Brazilian supplier invoices, evaluating extraction tools that support flexible, instruction-based field configuration will reduce the operational burden across the full transition period. A system where you can define new tax fields through natural-language instructions, rather than waiting on vendor updates or custom development cycles, gives your team the ability to adapt extraction logic as each phase of the reform takes effect.