What changed in 2026 and why your system needs a review now
Complementary Law 214/2025 set the consumption tax reform in motion, and 2026 is the test year: invoices must calculate and report IBS (0.1%) and CBS (0.9%), still without payment for companies that meet the ancillary obligations. Technical Note 2025.002 changed the NF-e and NFC-e layout with new groups and fields (cClassTrib, IBS/CBS CST, cIndOp, pDevTrib, totals and return references), mandatory for the regular regime since 3 August 2026; since then, an invoice without IBS and CBS is rejected. Version 1.51 of the note goes to production on 5 October 2026. NFS-e became a national standard, and micro and small Simples companies issue only through the National Issuer since 1 September 2026. In September, Simples companies choose between the standard and the hybrid model, effective in 2027. And split payment, regulated by Decree 12,955/2026, starts in 2027, optional and business-to-business.
If your ERP, e-commerce, POS or issuer has not been updated for any of this, the question is not whether there will be a problem, but when. A rejected invoice stops the sale; a catalogue without tax classification produces wrong invoices; NFS-e in the old layout stops being accepted; a payment without operation identification cannot enter split payment. JBKR Web assesses the current system, lists what must change by obligation and by date, and adapts it in parts without stopping operations. Read the full article with the checklist in Insights.
What JBKR has already done for the tax reform
We updated clients' NF-e and NFC-e issuers to NT 2025.002, with the IBS and CBS groups, cClassTrib in the product catalogue, the specific CST, the operation indicator and the new totals, including the ERP we have kept in production since 2009. We migrated NFS-e issuance from municipal web services to the national standard, with DPS and NBS code. We reviewed payment flows with Mercado Pago, Pix and boleto so they carry the operation identification split payment requires. And we handled what comes with it: digital certificates, LGPD and gov.br integration.
Every adaptation ships tested in the homologation environment, with a log of the rejections handled and monitoring under the monthly plans, because the legislation keeps changing until 2033 and the system has to keep up.
What is systems integration and when does my company need it?
Systems integration means making different software exchange data automatically: the e-commerce sends orders to the ERP, the ERP issues the invoice, the logistics system receives the delivery, all without manual typing. Signs your company needs it: staff retyping information between screens, duplicate records, stock errors and reports assembled from spreadsheets.
JBKR Web maps the current data flow, identifies the rework points and proposes the integrations with the best return, starting with the ones that save the most manual hours or prevent the most errors.
Do you integrate NF-e, NFS-e and NFC-e issuance?
Yes, tax integrations are one of JBKR Web's specialities. The client's system starts issuing NF-e (goods), NFS-e (services) and NFC-e (consumer) automatically, talking to SEFAZ and municipal web services or to issuing providers. The founder has maintained since 2009 an ERP that issues NF-e over web services in production.
This applies to new and legacy systems alike: it is common for an old ERP that works well to need only its tax module updated for a new layout version. In those cases the integration avoids replacing the whole system.
How do payment and bank integrations work?
Payments join the same data flow: JBKR has implemented Mercado Pago transparent checkout in an SMM dashboard, a payment-provider integration in a .NET Core platform with Angular and MongoDB, Juno reconciliation in the OMO Lavanderia app (Unilever) and a Banco do Brasil bank integration in an ERP.
The rule is the same for Pix, cards and boleto: the payment confirms the order in the system, the system issues the invoice and reconciliation happens without spreadsheets. Every integration ships with transaction logging and error handling, because providers fail and operations cannot stop.
How do you integrate a legacy system that has no API?
First answer: it is almost always possible. When there is no API, JBKR Web evaluates alternatives in order of safety: controlled direct database reads, file import/export routines, an intermediate web service built on top of the system, or interface automation as a last resort.
The company's experience maintaining legacy systems in PHP, Java, .NET/C# and classic ASP is the differentiator here: understanding old code makes it possible to choose the integration point that does not break what already works.
Frequently asked questions
Does my system need to issue IBS and CBS on invoices in 2026?
Yes. Since 3 August 2026, SEFAZ rejects NF-e and NFC-e from regular-regime companies (Lucro Real and Presumido) without the IBS and CBS groups of NT 2025.002 (cClassTrib, CST, cIndOp and totals). In 2026 the rates are test rates (0.1% IBS and 0.9% CBS) and payment is waived for companies that meet the ancillary obligations, but the invoice must go out right. Simples Nacional and MEI join in 2027. JBKR Web adapts the ERP, e-commerce or issuer to the technical note and tests it in the homologation environment before switching over.
What is split payment and what changes in my system?
Split payment is the separation and collection of IBS and CBS at the moment the payment settles (Pix, boleto, transfers and, later, cards). It was regulated by Decree 12,955/2026 and starts in 2027, optional and business-to-business. For it to work, the order, the invoice and the payment must carry the same operation identification and the same tax amounts, from checkout to reconciliation. JBKR Web reviews the financial flow of e-commerces, marketplaces and platforms with Mercado Pago, Pix and boleto for that requirement.
I am under Simples Nacional. Do I need to change anything?
In September 2026 the company chooses, with its accountant, between standard Simples (IBS and CBS inside the DAS) and hybrid Simples (IBS and CBS assessed separately, with full credit for business customers), effective 1 January 2027. In the hybrid model the system must calculate and highlight both taxes as a Lucro Presumido company would. In addition, micro and small service providers issue NFS-e exclusively through the National Issuer since 1 September 2026, with DPS and NBS code. JBKR Web migrates the issuer and updates the records.
What is systems integration and when is it necessary?
It means making different software exchange data automatically: the e-commerce sends orders to the ERP, the ERP issues the invoice without typing. It is necessary when the team retypes information between systems, when there are duplicate records and stock errors, or when reports require merging spreadsheets by hand.
Does JBKR Web integrate Brazilian electronic invoicing (NF-e, NFS-e, NFC-e)?
Yes. JBKR Web builds integrations for NF-e (goods), NFS-e (services) and NFC-e (consumer) issuance, connecting the client's system to SEFAZ and municipal web services or to issuing providers. The founder has maintained since 2009 an ERP that issues NF-e over web services in production.
Do you integrate payment providers and banks?
Yes. Delivered projects include Mercado Pago transparent checkout in an SMM dashboard, a payment-provider integration in a .NET Core platform with Angular and MongoDB, Juno reconciliation for a Unilever app and a Banco do Brasil bank integration in an ERP. Pix, cards and boleto follow the same flow.
Can you integrate an old system that has no API?
Yes, almost always. When there is no API, JBKR Web evaluates direct database reads, file import/export, an intermediate web service or interface automation. Experience with legacy systems in PHP, Java, .NET and classic ASP helps pick the path that does not break what already works.
How much does a systems-integration project cost?
It depends on the systems involved, whether documented APIs exist and the business rules. Integrations with defined scope are contracted as fixed-scope projects. One-off work uses the On-Demand plan (from BRL 250/hour, estimate before the work starts); continuous evolution and support use the monthly plans: Care from BRL 1,125/month and Expert from BRL 2,050/month. Every proposal is written and itemized.
How is an integration maintained once it is live?
Integrations depend on external systems that change: APIs are updated, tax layouts get new versions, certificates expire. JBKR Web's monthly plans include monitoring, fixes and adaptation to those changes, keeping the data exchange working over time.
