What importers, resellers, and e-commerce operations must decide, execute, and document in the implementation of IBS and CBS.
The first rupture caused by the Consumption Tax Reform is not necessarily in the price or the rate. It is in the ability to correctly issue the tax document and keep the operation moving.
Each purchase, import, sale, return, or cancellation will start to feed the calculation of IBS and CBS debits and credits. In the regular regime, taxed outflows will generate debits, while eligible acquisitions and imports may give rise to credits, provided that the legal and documentary conditions are met. The difference between these values will define, separately for IBS and CBS, the balance to be paid or the credit balance.
This change removes the tax from the isolated moment of the fiscal closing. The quality of the data now influences price, margin, working capital, inventory, supplier selection, financial reconciliation, and continuity of billing.
The electronic invoice is no longer just the record of the transaction
Supplementary Law No. 214/2025 grants declaratory character to the information contained in the electronic tax document. The IBS and CBS values recorded in the document may produce tax effects even before any inconsistency is noticed by the board of directors.
The risk can arise in two ways.
When the document is rejected, the problem is immediately visible: billing, shipping, transport, integration with marketplaces, and delivery can be interrupted.
When the document is authorized with incorrect information, the sale continues, but the exposure remains silent. Inadequate classification, tax base, destination, or tax treatment can distort debits, compromise credits, alter margins, and accumulate discrepancies for tax assessment.
Therefore, adaptation is not limited to filling out new fields. It is necessary to ensure that the data originates correctly, circulates between systems, is finalized in the tax document, and returns to the operation without breaking the commercial flow.
In e-commerce, the error traverses the entire journey
In operations integrated with ERP, tax engines, marketplaces, payment methods, WMS, carriers, and import systems, the electronic invoice is only the visible part of a more extensive chain.
The same product cannot present inconsistent NCM, unit, origin, purpose, or description across different systems. Likewise, CST-IBS/CBS and cClassTrib must not be applied automatically by a generic rule, without linkage to the product, the operation, the benefit, or the corresponding purpose.
It is also not enough for the XML to be authorized. The company must verify whether the key returned to the order, whether the inventory was released, whether the transport document was correctly linked, whether the finance department reconciled the operation, and whether cancellations, returns, exchanges, and warranties produced consistent tax, accounting, and operational effects.
The system is not ready when it can issue an invoice. It is ready when the entire operation is closed.
Four decisions transform an obligation into a secure operation
The first step is to correct the master data. SKU, description, unit, NCM, origin, purpose, kits, parts, and packaging must be standardized across all systems involved.
Next, the company must approve its parameterization matrix. The definition of CST-IBS/CBS, cClassTrib, base, applicable tax rates, reductions, deferrals, credits, and specific treatments must contain identified premises, foundation, and those responsible for approval.
The third stage is to test real end-to-end journeys. Sales, receipt, cancellation, return, exchange, warranty, assistance, import, entry, transfer, and unavailability situations must be reproduced in a controlled environment, with preservation of the corresponding documents and records.
Finally, the board of directors must formalize the decision to enter production. Pending issues must be classified as prohibitive, mitigable, or residual. Implementation can only be considered controlled when there is a tested contingency, defined responsibles, a deadline for correction, and monitoring.
Evidence is part of compliance
Meetings, supplier presentations, or generic statements that “the system is adequate” do not prove readiness.
The implementation dossier must allow for the reconstruction of the business decision. To do this, it must gather, among other elements, the tax and master data matrix, the technical versions used, the tested XMLs, authorization protocols, logs, rejection records, root cause, corrections, retests, reconciliation, contingency procedures, and minutes of the entry into production.
Responsibility also cannot remain diffuse. The management authorizes the risk and defines resources; the tax, accounting, and legal departments approve the premises; technology implements and preserves records; and operations prove that the actual flow remains functional.
Five answers for the board of directors
Before declaring that the company is ready, the administration must be able to respond objectively:
1. Was the implemented technical version identified and confirmed in the environment used?
2. Were the master data and tax matrix formally approved?
3. Did the critical journeys work end-to-end, including in finance and after-sales?
4. Was the contingency tested and is there a defined channel for incident handling?
5. Do the residual pending issues have mitigation, a responsible party, and a deadline?
A negative answer prevents the affirmation of full readiness. The implementation may be controlled or restricted, but the limitation and the corresponding risk must be formally registered.
The business decision
The implementation of IBS and CBS requires more than a technological update. It requires governance capable of connecting tax classification, document, contract, operation, evidence, and financial consequence.
In the new system, documentary compliance preserves billing, credit, and cash flow.
Informative material based on the version finalized on July 29, 2026. Technical documentation and operational schedule remain subject to subsequent acts and versions. Before any implementation decision, the norms, Technical Notes, schemas, tables, and rules effectively in force in the authorizing environment used by the company must be verified.
This content does not substitute specific analysis of the operation.