Assisted CBS and IBS assessment: a finance guide

Assisted CBS and IBS assessment is a model in which electronic tax documents and their events feed a government platform that presents liabilities, credits, payments, and adjustments for Brazil's new consumption taxes. Companies no longer build the entire assessment from scratch, but remain responsible for reviewing data, recording events, explaining differences, and correcting inconsistencies.

The change turns a month-end obligation into a continuous process. If an invoice starts incorrectly or an event is not recorded, the discrepancy reaches assessment. Preparation means connecting master data, documents, events, open items, payments, and evidence.

In 2026, the environment is designed for adaptation and testing. The CBS Platform Manual states that real documents are loaded for processing while payments, refunds, and other effects are simulated without financial validity during the test year. This makes it possible to test processes with real data, but it does not justify inventing dates, stages, or obligations beyond those officially published.

Assisted assessment versus taxpayer-declared assessment

In a traditional taxpayer-declared assessment, taxpayers gather documents, apply rules, calculate amounts, and submit their declaration. The tax authority receives the reported result and may compare it with other databases. The company controls the initial assembly of the view.

In assisted assessment, the tax administration presents a pre-calculated view based on the documents and events it received. This view can include liabilities shown in transactions, credits related to purchases, credit and debit notes, cancellations, returns, adjustments, payments used, balances, and refund requests.

The operating difference matters. Work does not disappear, but moves:

• previously, much of the effort involved compiling and declaring;
• in the assisted model, more effort goes into source quality, reconciliation, and exception handling;
• in both models, the company must maintain controls, documentation, and responsibility for its position.

"Assisted" does not mean automatic or accepted without review. The platform works with the data available to it. The company must verify whether the tax representation matches the actual transaction and follow applicable official procedures when there is a difference. This article addresses operational preparation and does not replace tax advice for a specific company or transaction.

The document and event lifecycle

Assessment should be understood as a chain, not as an isolated screen:

1. A business need creates a sales order or purchase order.
2. Item, service, customer, supplier, and legal-entity master data guide document issuance.
3. The company issues or receives an electronic tax document.
4. The authorizing system sends information to the tax environment.
5. The ERP records billing, receipt, inventory, and the financial open item.
6. Later events, such as cancellation, return, adjustment, or payment, update the transaction.
7. The platform presents liabilities and credits based on available data.
8. The taxpayer compares the assisted view with internal systems, handles exceptions, and preserves evidence.

Every event should carry identifiers that lead back to the original document. When a return exists in inventory but is not linked to the invoice and open item, tax and finance see different stories. The design must also support reprocessing and identify earlier documents affected by a correction.

Liabilities and credits from an operating perspective

The team should explain each amount's origin without turning reconciliation into specific tax advice:

• liabilities should link to the issued document, transaction, period, and later events;
• credits should link to the received document, purchase record, supplier, and status shown by the platform;
• adjustments should have a reason, approval, reference, and evidence;
• payments, offsets, balances, and refunds should be reconciled with the official view available.

Eligibility, timing, and treatment of each credit depend on the law and rules applicable to the case. When the platform and ERP differ, the safe workflow is to classify the cause, gather documentation, and route the decision to the tax owner. Forcing systems to match without understanding the source is not a sound control.

Master data: the first control layer

Product, service, supplier, customer, legal-entity, and transaction-nature master data support the process from document issuance. A master-data program should define an owner, source, required fields, validations, change approval, and history.

Test tax ID and entity consistency across systems, links from an item or service to its order and document, critical fields, duplicates, and effective dates. Every change should record its author, date, request, and potentially affected transactions.

Reconciliation layers

Comparing only monthly totals can hide problems. Use layers:

1. Document integrity: confirms count, key, issuer, recipient, date, and value across the authorizing environment, tax repository, and ERP.

2. Lines and events: compares line items, references, cancellations, returns, credit and debit notes, and other related events.

3. Finance: links the document to the open item, due date, settlement, payment, and bank statement when applicable.

4. Tax: compares liabilities, credits, adjustments, and statuses between internal calculation and the assisted view.

5. Accounting and management reporting: verifies that reconciled totals reach the accounts, cost objects, entities, and reports used at close.

Each layer should produce exceptions with identifiers, amount, probable cause, age, owner, and next action.

Daily, weekly, and monthly routines

Daily, monitor rejections, missing documents, unlinked events, and integration failures. Prioritize items that could affect several later steps.

Weekly, review the queue by cause and owner, address aging items, analyze recurring master-data issues, and inspect end-to-end samples. Tax, finance, procurement, billing, and technology should discuss blockers that depend on more than one department.

Monthly, perform complete reconciliations, explain changes, confirm the treatment of significant exceptions, and close the evidence trail. Update validations, master data, or integrations to prevent repetition.

Responsibility matrix

A practical matrix can assign roles as follows:

• billing: issuance quality and correction of rejections;
• procurement and receiving: links among order, receipt, item, and document;
• tax: tax criteria, assessment review, and decisions on discrepancies;
• accounts payable and receivable: open items, settlements, and document association;
• treasury: payment confirmation and bank reconciliation;
• accounting: accounting impact and close consistency;
• data and technology: integrations, monitoring, access, and reprocessing;
• internal controls: control design, sampling, and evidence retention.

For each exception, define who performs the task, who approves it, who must be consulted, and who receives information. Without this matrix, a discrepancy can circulate across departments without a decision.

How to handle discrepancies

The workflow begins with classification. Common causes include a missing document, late event, invalid key, duplication, item-level difference, incorrect master data, integration failure, pending financial settlement, or a tax criterion requiring analysis.

Then:

1. preserve the original evidence;
2. confirm whether the difference is real or timing-related;
3. identify the source system and process;
4. route the case to its owner with a deadline and impact;
5. correct it through the approved procedure, without a silent adjustment;
6. reprocess and validate every affected layer;
7. record the root cause and preventive action.

For example, a purchase appears in the ERP but not in the assisted view. The analyst checks its key, tax ID, date, authorization, ingestion, and period. If the document is wrong, procurement, the supplier, and tax become involved. The case closes when the new position is reconciled and supported.

In another example, a partial return reduces inventory and the open item but is not linked to the original invoice. The queue should display the document, items, amount, and affected systems. Correcting only the accounting balance would leave the cause active.

Controls and evidence

An auditable control states its objective, frequency, population, tolerance, performer, approver, and response to exceptions. Evidence can include a dated report, source file, approval, corrected document, and reprocessing result. Retain parameters and versions, and apply segregation of duties proportionate to risk.

Automation can collect files, validate fields, reconcile keys, and route queues. Decisions that require interpretation remain with the appropriate team, with their basis recorded.

How to use 2026 as a test

Brazil's Federal Revenue Service describes 2026 as a CBS and IBS test year. Under its official guidance for 2026, taxpayers should follow applicable layouts and obligations and, when transition conditions are met, are exempt from payment of the new taxes.

Use the period to validate issuance, integrations, master data, internal calculations, reconciliations, evidence, and training. The absence of a financial effect in the scenarios described by official guidance does not make testing irrelevant. It creates an opportunity to measure failures before they affect credits, payments, and cash.

Do not assume an unpublished schedule. Monitor official sources and adapt the plan to new manuals, layouts, or guidance. Internal test waves are company choices, not official milestones.

A 30, 60, and 90-day preparation plan

First 30 days: inventory documents, events, systems, and owners. Select a high-volume flow, define common keys, establish baseline metrics, and identify master-data and integration gaps.

By day 60: implement reconciliation layers for the pilot flow, create the exception queue, formalize the responsibility matrix, and test reprocessing. Train teams with real cases and document decisions.

By day 90: expand the scope based on risk, automate repetitive checks, perform a simulated close, and review evidence. Turn recurring causes into preventive validations and report results to leadership.

This plan is a suggested internal cadence, not an official tax reform calendar. Adapt it to the company's size, system maturity, and current guidance.

Metrics to monitor

• percentage of documents reconciled without discrepancies;
• integration coverage for documents and events;
• differing liabilities and credits by cause and amount;
• average correction time and maximum age;
• events not linked to their original document;
• rejected, duplicated, or incomplete documents;
• recurrence by master-data field, supplier, customer, or entity;
• difference between internal calculation and assisted view;
• percentage of exceptions with complete evidence;
• volume reopened after correction;
• completion of planned tests and training.

Review both count and materiality. One hundred small differences can reveal a systemic failure, while one significant difference may require immediate priority.

Assisted assessment FAQ

Does the platform replace the tax team?

No. It presents calculations based on the data received. The team remains responsible for quality, review, applicable interpretation, and exception handling.

Is CBS and IBS payment effective in 2026?

The 2026 environment is officially described as a test, and the manual states that financial effects are simulated. Applicable conditions should be confirmed in official guidance and in light of the company's circumstances.

Is assisted assessment the same as a pre-filled return?

The concepts are similar because both use data already received by the tax authority, but the platform's process, events, and procedures follow their own rules. The comparison should not be treated as a legal equivalence.

What is the biggest operating risk?

A document or event that does not reflect the actual transaction. One master-data error can propagate through issuance, credit, payment, accounting, and reconciliation.

Is comparing the monthly total enough?

No. Equal totals can conceal missing documents and offsetting differences. Reconciliation should reach the document, line, event, and amount.

What should be automated first?

Document capture, field validations, key-based matching, amount comparison, and routing of repetitive exceptions. Tax decisions should remain with qualified owners.

How should discrepancies be prioritized?

Consider value, age, affected volume, recurrence risk, close impact, and external dependencies. Define service levels for each class.

Where should a company start?

Select a relevant document type, connect issuance or receipt, ERP, finance, and platform, classify discrepancies, and fix root causes before expanding scope.

Conclusion

Assisted assessment does not eliminate work. It shifts work toward data quality, cross-functional integration, and continuous exception handling. Companies that connect documents, events, ERP systems, payments, and evidence reach close with fewer surprises and a greater ability to explain their numbers.

Abstra helps finance and tax teams capture documents, apply operating rules, reconcile events, and route discrepancies with traceability.

To prepare your operation for CBS and IBS, talk to an expert.