Tax rollout in SAP: taking the group's tax standard to each new establishment
A tax rollout is the project that takes a tax setup that already works and replicates it, with checks, in a new branch, a new CNPJ (the Brazilian company tax ID), a new state registration, a new plant or a new state, without forcing SAP to change version.
For the tax authority, each establishment is a unit with its own registration, documents and obligations. The work is to make sure the new unit is born equal to the group standard where it must be equal, and different only where the state law says it must be different.
Choose the entry point by your role
Four entries, one per role, straight to the block that answers your question.
01Tax
Map of tax decisions by state (ST, DIFAL, FCP and benefits), real risks with checks and a go-live checklist per unit.
Go to the section02IT and integrator
How SAP represents the tax unit, what changes in the new establishment (CNPJ, state registration, certificate and series) and the six-step method.
Go to the section03Manager
Which project is yours (rollout, migration, expansion or acquisition), who decides at each step and roles with evidence.
Go to the section04Tax reform
CBS and IBS in the rollout: what the new unit inherits.
Go to the sectionTax rollout in project language
In SAP project vocabulary, a rollout is the repeated deployment of a model that has already been built to new units. The tax rollout is the part of that movement that takes care of everything the tax authority sees: registration, electronic documents, tax assessment, ancillary obligations and state rules.
A company can open a branch without changing ERP. It can buy a competitor with its own CNPJ and registrations in other states. It can open a plant in a state where it has never operated. None of these events is a version migration, but all of them require the tax setup in SAP to be reproduced in a new place, and all of them can go wrong in the same way: copying an old setup without reviewing it, or configuring from scratch a rule the group had already solved.
The term tax rollout describes this project for what it is: a project with scope, waves, owners, checks and a closing criterion, and not a registration task that someone does in an afternoon. The difference shows at the unit's first close, when the assessment only matches if the registration, the certificate, the numbering, the state rule and the ancillary obligation are all right at the same time.
What the tax rollout delivers, in one sentence per layer
Registration and identity
The unit's CNPJ, state registration, regime, address, owner, and the SAP record tied to what the tax authority has on file.
Documents and numbering
Accreditation for the electronic documents the unit issues, a valid digital certificate, and series and numbering with no collision.
Assessment and obligations
Tax rules by operation and by state, assessment per establishment, files for SPED (Brazil's digital tax reporting system) and returns with the right data for each unit. See also the page on tax assessment in SAP.
The sister pages detail each layer: tax setup, the tax master data, the electronic tax documents and the ancillary obligations and SPED. Here the focus is the project that ties these layers together in each new unit.
The topic also appears, in summary, as a section inside the page on ECC to S/4HANA migration, where the rollout is the step that comes after the first wave. The difference is the starting point: there the rollout accompanies a version change; here it is the whole project, with or without a change.
The concept of template and rollout comes from SAP project practice, and the tax unit the rollout works on is defined by the ICMS (Brazil's state value-added tax) law.
What to check
- Is there a documented group tax standard with an owner?
- Was the project classified as rollout, migration or adjustment?
- Do the four layers (registration, documents, assessment and obligations) have an owner?
Open the project by classifying the case and naming who answers for the group standard, before any registration. Without that owner, the rollout becomes a sequence of copies.
What to check
- Is there a documented group tax standard with an owner?
- Was the project classified as rollout, migration or adjustment?
- Do the four layers (registration, documents, assessment and obligations) have an owner?
Table of situations: rollout, migration, expansion and acquisition
Not every structure change is a tax rollout, and not every tax rollout is the same size. The table organizes the most common situations to help you choose the right project before defining scope.
| Situation | What changes for tax | Recommended project | Note |
|---|---|---|---|
| New branch with its own CNPJ, in the same state | New establishment: CNPJ, new state registration (IE), accreditation, certificate, series and unit in SAP. | Tax rollout | The group standard exists and should be reused. The state is already known, so the difference is small. |
| New branch in another state | Everything from the previous row plus ST (tax substitution), DIFAL (rate differential), FCP (Poverty Combat Fund), benefits and obligations of the new state. | Tax rollout by state wave | Each state brings its own rules. This is the case where the rule of the wrong state is copied most often. |
| New industrial plant or distribution center | New establishment with inbound, production or transfer flows; IPI (Brazil's federal excise tax) and credit come onto the agenda. | Tax rollout, with process design | There is also a logistics and transfer decision between units of the same owner. |
| Acquisition of a company with its own SAP or another ERP | New CNPJs with history, master data and rules that the group did not choose. | Tax rollout plus cleanup | The first step is to compare what exists with the standard, before bringing it into the group's SAP. |
| Change from ECC to S/4HANA | Technical and tax migration, with waves by unit. | Migration, with rollout as a later step | See the migration page. The rollout comes after the first wave. |
| New state registration in the same UF (federative unit) | It can be a new operation, such as a bonded warehouse or an additional branch, with its own treatment. | One-off tax rollout | Each registration answers for its own obligations. |
| Change of tax regime or corporate reorganization | Changes CNPJ, regime or structure, and not just the unit. | Own adjustment project | It can contain a rollout, but the center is the regime rule. |
| Tax reform: CBS (Brazil's federal consumption tax) and IBS (Brazil's state and city consumption tax) | New taxes for all units at the same time. | Regulatory adjustment | See the tax reform page. The future rollout is born with the new calculation. |
Is there a group standard?
Documented, with an owner, that the unit can inherit.
Same state?
Defines whether the risk is a copy or a swapped rule.
Version change?
If so, the central project is the migration.
Two questions help classify the case. The first: is there a documented group tax standard, with an owner, that the new unit can inherit? If not, the rollout becomes, in practice, the first definition of that standard, and the project needs a prior step. The second: is the new unit in the same state as the previous ones? If so, the main risk is a copy without review. If not, the main risk is a swapped state rule.
When the tax rollout is the right project
When SAP and the group structure already exist and the challenge is to replicate safely. When the challenge is to change version, the project is a migration. When the challenge is to meet a new rule for all units, the project is an adjustment. The three can happen in sequence, and clarity about which one is under way avoids mixed scope.
The page on multi-CNPJ tax governance describes the problem from the side of those who already live with dispersion: units that handle the same obligation in different ways. The tax rollout is the chance not to create the next unit already dispersed.
The classification starts from two legal definitions: the establishment as an autonomous unit and the CNPJ registration per establishment.
What to check
- Is the new unit in the same state as the previous ones?
- Is there an SAP version change in the same period?
- In an acquisition, was what exists compared with the standard before entering the group's SAP?
The establishment as tax unit in Brazil
To understand why the tax rollout is a project, you have to start from the legal fact: in Brazil, the unit the tax authority sees is the establishment, not the group and often not even the whole company.
CNPJ: head office and branch
All entities based in Brazil register in the CNPJ, and so does each of their establishments, before starting activity. The entity can change the registration of a branch to classify it as head office. The possible registration statuses are active, suspended, unfit, closed and null.
ICMS: autonomous establishment
For the ICMS Complementary Law, an establishment is the place where people carry out activities temporarily or permanently, or where goods are stored. Each establishment of the same owner is autonomous, and all those of the same owner answer for the tax debt.
ISS: the service-provider establishment
The ISS (Brazil's municipal services tax) is due, as a rule, at the place of the service-provider establishment, and the law defines that head office, branch, agency, service post or office are irrelevant names: what counts is the economic or professional unit where the service is provided.
What the establishment's autonomy means in practice
Autonomy, here, does not mean that each branch is a separate company. It means that ICMS legislation looks at each establishment as a unit of assessment and registration, and this shows in concrete day-to-day tax matters: document numbering, state registration, accreditation and bookkeeping. The same owner can have dozens of establishments, and the tax authority treats them separately, although liability for the credit is joint among them.
One drafting point deserves attention in a project: the rule on the ICMS taxable event on the outbound movement of goods from a taxpayer's establishment changed wording. The earlier text said that the outbound movement was a taxable event even if the goods went to another establishment of the same owner. The current wording, given by LC 204/2023, speaks only of outbound movement of goods from a taxpayer's establishment, and the compiled text on the Planalto site keeps, next to the old passage, the reference to ADC 49, an action in the Supreme Federal Court (STF). Whoever designs transfers between units in SAP should not presume the treatment: they must confirm, with the company's tax and legal teams, how the rule in force and the state legislation apply to a transfer between establishments of the same owner.
What changes by tax and by obligation
The table shows, tax by tax, which is the tax unit and what that asks of the rollout.
| Tax or obligation | Unit the tax authority considers | What this asks of the rollout | Source |
|---|---|---|---|
| ICMS | Establishment, with its own state registration in the UF where it is located | One IE per establishment, accreditation in the UF and assessment according to state legislation | LC 87/1996, art. 11 §3º; Ajuste SINIEF 07/05, cl. 2ª |
| EFD ICMS IPI (Digital Tax Bookkeeping for ICMS and IPI) (SPED Fiscal) | Taxpayer, mandatory for all establishments located in the UF | Report each establishment of the UF; check how the layout and the generating program handle several IEs | Ajuste SINIEF 02/09, cl. 3ª, §6º |
| EFD-Contribuições (Digital Tax Bookkeeping for PIS and Cofins) (PIS and Cofins) | Individualized establishments inside a single monthly file, centralized by the head office | Data of each branch in the head office file, checking that no unit was left out or duplicated | SPED portal of the Receita; IN RFB 1.252/2012 |
| ECF (Tax and Accounting Bookkeeping) | Bookkeeping centralized by the head office | Consolidation by legal entity, not by branch; the new unit enters the head office data | IN RFB 2.004/2021 |
| ISS and NFS-e (Electronic Service Invoice) | Service-provider establishment, as a rule | Municipal registration of the unit and adoption of the municipality's NFS-e standard | LC 116/2003, arts. 3º and 4º |
| CBS and IBS | Taxpayer identified by a single registry (CNPJ), with the place of operation defined by its own rule | Registration of the new CNPJ in the registries of the new taxes and issuing of an electronic tax document | LC 214/2025, arts. 11, 21, 59 and 60 |
For DCTFWeb (federal tax debts and credits return) and ECD (Digital Accounting Bookkeeping), ask the company's accounting and tax team to confirm, in the applicable act, the level at which each obligation is transmitted before defining the rollout scope.
There is a method lesson in the table: four obligations point to the unit, one points to the head office and two combine the two levels. A rollout that treats everything as if it were per branch fails on EFD-Contribuições and ECF. A rollout that treats everything as consolidated fails on ICMS. That is why the check per unit must know which level each obligation belongs to.
What to check
- Was each obligation classified by level: unit, head office or mixed?
- Was the transfer between establishments validated with tax and legal?
- Was the transmission level of DCTFWeb and ECD confirmed in the applicable act?
The new establishment: CNPJ, IE, accreditation, certificate and series
When a new establishment is born, a sequence of external events must happen before SAP issues the first invoice. Each one has an official source, an owner and a consequence if it fails.
The new establishment sequence, from registration to the first invoice
Unit CNPJ
Registration of the establishment in the CNPJ before activity starts, with an active registration status.
State registration
Registration in the UF's ICMS, which is the registration that accreditation relies on.
Accreditation
Authorization to issue each electronic document, in the UF of registration.
Certificate and series
A digital certificate in force and series and numbering defined for the unit.
Test and first invoice
Issuing in the test environment, checks and only then production, with the unit already in SAP.
Accreditation to issue electronic documents
| Document | What the rule requires | Legal basis |
|---|---|---|
| NF-e (Electronic Invoice) | Prior accreditation in the UF in whose ICMS registry the taxpayer is registered. It can be voluntary, when the taxpayer requests it, or ex officio, when the tax administration does it. | Ajuste SINIEF 07/05, cl. 2ª |
| NFC-e (Electronic Consumer Invoice) | Prior accreditation in the UF of registration. Whoever is accredited for NFC-e is required to use NF-e model 55 in place of old models, unless state legislation says otherwise. | Ajuste SINIEF 19/16, cl. 2ª and §2º |
| CT-e (Electronic Transport Document) | The taxpayer requests accreditation in advance in the UF in whose ICMS registry it is registered. | Ajuste SINIEF 09/07, cl. 4ª |
| MDF-e (Electronic Manifest of Tax Documents) | Legal validity guaranteed by a qualified electronic signature and by the authorization of use from the tax administration of the taxpayer's UF. | Ajuste SINIEF 21/10, cl. 2ª |
Practical consequence: branch in a new state
Because accreditation is by UF of registration, a branch in a new state requires a new accreditation at that SEFAZ(the state tax authority). The procedure, the deadline and the portal are the state's, vary by state treasury office and must be confirmed with it.
Digital certificate per CNPJ
What the rule requires
The NF-e must be signed with a digital signature certified by an entity accredited in the ICP-Brasil (Brazilian Public Key Infrastructure). The certificate must contain the CNPJ or CPF number of any of the taxpayer's establishments: the rule allows the certificate to be from any establishment of the owner.
Decision the rollout must record
Does the group use one certificate per CNPJ, or does it use the one from an establishment to sign documents of others? Internal security policies, expiry management, the certificate type (A1 file or A3 device, depending on what the certificate authority issues) and the SAP environment weigh in the choice.
Series and numbering
Sequential numbering
NF-e numbering is sequential from 1 to 999,999,999, per establishment and per series, and must restart when it reaches the limit. NFC-e follows the same logic.
Uniqueness key
The pair establishment plus series is the uniqueness key, and the SAP setup must reflect this. A duplicate series across establishments is not an error in itself, because the CNPJ is part of the access key.
Where the error is
The error is repeating, within the same establishment, a number already used. Or reusing the range of a deactivated unit without checking what was already authorized.
Ancillary obligations of the new unit
Local task: the unit's state
- Registration, state and municipal returns.
- State EFD ICMS IPI: mandatory for ICMS and IPI taxpayers, and covers all establishments of the taxpayer located in the federative unit.
Consolidation task: the head office
- EFD-Contribuições: a single monthly file from the head office, with the information of each establishment inside the file.
- ECF: reported centrally by the head office.
- Forgetting this task is the reason EFD-Contribuições closes incomplete after a branch opens.
The overall picture of obligations is on the page on ancillary obligations and SPED.
Registration check before switching the unit on
Registration statuses
IN RFB 2.119/2022 provides that the registration status of an entry can be active, suspended, unfit, closed or null, and that the branch can be affected by the status of the head office.
Cascade effect
A unit with an irregular registration status produces cascade effects: certificate, accreditation and issuing can be blocked. The registration check, done at the Receita itself, must be an item of the go-live checklist, and not an assumption.
- Accreditation: treat as a critical-path item of the schedule, because without it SAP, however well configured, cannot authorize the first invoice.
- Certificate: choose a single certificate policy for the group, record who is responsible for each renewal and put the expiry date in a control that tax can see.
- Series: define, before the first invoice, the series policy per unit and per document type (sale, transfer, return, service), document the starting range and forbid manual editing of numbering outside the planned process. In a classic SAP environment, outbound numbering sits at the business place level, see how SAP represents the tax unit.
What to check
- Active CNPJ, IE and accreditation for each document confirmed in the UF.
- Valid digital certificate, with a renewal owner and expiry recorded.
- Series and numbering range documented, with no overlap.
- Unit included in the files centralized by the head office.
How SAP represents the tax unit
On the SAP side, the question is how the real-world tax unit becomes an organizational structure in the system. And what must be created or reviewed so that each establishment gets the treatment the law requires.
Company code, plant and business place
Where it sits
In SAP's Brazilian localization, the classic documentation in the official help describes the business place as an organizational unit situated between the company code and the plant.
What it is for
It is used for the sales and purchase tax report, for the invoice and for the numbering of official documents.
How it is configured
The configuration defines each business place with the invoice data, such as tax numbers and, where ST applies, the ST state registration by tax region. It is assigned to one or more plants, and the numbering of outbound invoices sits at the business place level.
The design of this structure defines what the rollout must create for each new establishment. In project language, the translation is simple:
| Real world | SAP structure (concept) | Rollout question |
|---|---|---|
| Legal entity | Company code | Is the head office CNPJ tied to the right company code? Is there more than one root CNPJ in the group? |
| Establishment, with CNPJ and IE | Business place, with tax numbers | Does each establishment have its own, with CNPJ, IE and ST IE by tax region when there is ST? |
| Physical plant, warehouse, site | Plant | Which plants belong to which business place? One business place can serve more than one plant, and the assignment must be deliberate. |
| Series and numbering | Numbering ranges at the business place | Was the new unit's range defined, documented and tested in the test environment? |
Symptom of an incomplete structure: error 8B060
A public SAP support note describes error message 8B060: the company code CNPJ is not found during billing in the Brazil localization, with reference to the business place and the branch table.
The full resolution is behind a login, in SAP's support portal. The existence of the message makes the point: the tax organizational structure must be complete before the first billing, and a missing record brings the operation down.
The SAP tools that carry the tax
Three SAP solutions appear in Brazilian tax rollouts.
SAP DRC
SAP Document and Reporting Compliance (DRC) is SAP's solution for electronic documents and statutory reports. SAP advises planning the migration of the GRC (SAP Governance, Risk and Compliance) NF-e to outbound and inbound DRC, in an SAP Community post of 13/04/2023.
SAP TDF
SAP Tax Declaration Framework (TDF) generates, among others, EFD ICMS IPI, EFD-Contribuições, EFD-Reinf, ECF and ECD for Brazil.
Tax calculation engine
It can be the SAP standard or an integrated tax engine, such as GUEPARDO Tax, covered in the section on GUEPARDO Tax.
For the rollout, each new unit must be registered in more than one place:
- in SAP's organizational structure;
- in the tax calculation conditions;
- in the electronic document flow;
- in the obligation reports.
If one of these places is left out, the unit works in parts and fails at the integration between them. The page on tax Clean Core shows why the location of each point matters when the environment keeps the core clean.
Setup per establishment in DRC and TDF
The exact way SAP DRC or TDF are configured per establishment depends on the version and the localization package in use. The point is handled in the fit-to-standard phase of the rollout, with the integrator and the environment's tax consultant, who see what is installed. What TDF does and how to run it is in SAP TDF in Brazil.
Create the unit in SAP only after confirming CNPJ, IE and plants, and test billing end to end in the test environment. A single missing record in the tax structure brings the operation down at the first billing.
What to check
- Company code tied to the right CNPJ.
- Business place with CNPJ, IE and ST IE by tax region.
- Plants assigned deliberately.
- End-to-end billing in the test environment.
The map of tax decisions by state: ST, DIFAL, FCP and benefits
Opening operations in a new state means entering a second set of rules. The tax on circulation is state-level, and that is where most of the difference between one unit and its neighbor lives.
Tax substitution: agreement between states and CEST
Agreement between states and the destination rule
Convênio ICMS 142/2018 sets the general rules for tax substitution (ST). In an interstate operation, ST depends on a specific agreement between the federative units involved: the same goods can have ST on one route and not on another.
Whoever withholds follows the legislation of the destination UF. Whoever sells to a new state starts to follow that state's rule for what is withheld, and not the origin's.
CEST and the material master
The CEST (Tax Substitution Specifier Code) has seven digits: two for segment, three for item and two for specification. The goods subject to ST are in the annexes of the convênio, with description, NCM/SH and CEST.
The tax document carries the CEST of each good, even if the operation is not subject to ST. That is why the material needs consistent NCM (Mercosur Common Nomenclature) and CEST, because the CEST is an element of the invoice.
Due date, payment slip and obligations of the substitute
Payment depends on the taxpayer's registration in the destination state. A substitute registered in the destination UF: the ICMS-ST is due on the 9th of the month after the outbound movement. Not registered, or with a suspended registration: it is due at the outbound movement itself, through GNRE (National State Tax Payment Slip) or a document defined by the destination UF.
The substitute also sends obligations to the destination: GIA/ST (tax substitution information and assessment form), the DeSTDA (Tax Substitution, Rate Differential and Advance Payment Return) for Simples taxpayers, or a magnetic file when not required to file EFD.
The list of obligations changes from state to state
The Mato Grosso do Sul SEFAZ announced in July 2020 the waiver of GIA-ST for taxpayers from other UFs required to file EFD, with the information delivered through EFD by the 20th. This does not apply to all states: whoever ships to other states follows the destination's requirement.
The Alagoas SEFAZ keeps a public query of special ST regimes, with the taxpayers that take responsibility for withholding in specific decrees.
DIFAL, FCP and each state's portal
The rule of LC 190/2022
Complementary Law 190/2022 regulated ICMS on interstate operations to final consumers, whether or not taxpayers of the tax. The difference between the internal rate of the destination state and the interstate rate becomes due to the destination. The taxpayer for this difference is the recipient, if a taxpayer, or the sender, if the recipient is not a taxpayer.
States publish on their own portal the applicable legislation, rates, benefits and special regimes and ancillary obligations, with a tool for centralized assessment and issuing of payment slips by federative entity.
In practice: the Goiás portal
In the Goiás SEFAZ portal for the DIFAL of non-taxpayers, a taxpayer from another UF accesses, with the company's digital certificate, the invoices issued to non-taxpayers in Goiás. It lists those with DIFAL and FCP of the destination UF shown, and issues the DARE (State Revenue Collection Document).
When the invoice also carries FCP, the portal generates two slips, one for each revenue. In other words, the new unit that sells to final consumers in another state needs an assessment and payment flow per state, and each flow has its own portal.
The order of the questions for each new state
What is the route?
Origin, destination and customer type: taxpayer or final consumer.
Is there ST?
Goods, NCM and CEST against the agreement between the UFs on the route.
Is there DIFAL or FCP?
Who pays the difference and in which portal.
Is there a benefit?
Granting act and condition of use.
Which obligation?
Returns and files required by the state.
The map of decisions by state
The table organizes the decisions that each new state requires. The values for each state, such as rates and benefits, come from the legislation of the UF itself and go into the state sheet.
| Decision by state | What to decide | Where to confirm it | How SAP carries it |
|---|---|---|---|
| ST: is the good subject on this route? | Goods, NCM and CEST, origin and destination route, specific agreement between the UFs | Convênio ICMS 142/2018, annexes; destination UF legislation | Material master data and tax determination rule, depending on the tax engine |
| Substitute registration in the destination state | Whether the unit needs an ST IE at the destination and what the due date is | Convênio ICMS 142/2018, cl. 14; destination SEFAZ | Registration number per tax region in the establishment record |
| DIFAL and FCP | Who is the taxpayer for the difference, whether there is FCP, how to pay and in which portal | LC 190/2022; destination SEFAZ portal | Calculation per operation and document with DIFAL and FCP fields of the destination UF |
| Tax benefit or special regime | Whether the unit is entitled to one and whether the benefit depends on a state act | State portal (LC 190/2022, art. 24-A) and granting act | Documented exception, with an owner and review date, and not a rule copied from another unit |
| State ancillary obligations | GIA/ST, DeSTDA, state returns and files required from the sender | Convênio ICMS 142/2018, cl. 21; destination SEFAZ | Obligation reports and tax calendar, with the unit and the state in scope |
Build, for each new state, a one-page sheet with these five decisions answered, the link to the state source and the date of the last check. The sheet becomes part of the group standard and prevents the rule of state A from being applied to state B for lack of a document.
The page on tax setup describes what a rule needs in order to be governable, and the rollout is the moment to apply that to the new state.
What to check
- State sheet with the five decisions, the source and the check date.
- Real routes tested against the destination state rule.
- NCM and CEST consistent in the material master.
- State obligations in the unit's tax calendar.
CBS and IBS in the rollout: what the new unit inherits
A rollout done in 2026 happens with two regimes on the horizon: the ICMS and ISS that exist today and the CBS and IBS that come in by stages. The question is what changes, for each new unit, with this coexistence.
The unit is identified by a single registry
Legal entities subject to IBS and CBS register in a registry with a single identification, and the registry of legal entities is the CNPJ. Whoever carries out operations in an economic activity is a taxpayer and must register in the registries of the new taxes.
The place of operation is its own rule
For tangible movable goods, the place of operation is the place of delivery or making available of the good to the recipient. There are specific rules for services, and the wording of the residual item was changed by LC 227/2026. The central point is that the law defines the place of operation by its own criterion, which does not depend on the establishment of origin.
The electronic tax document is mandatory
The taxable person must issue an electronic tax document in operations with goods and services, including exports and imports, and including operations that are immune, exempt or with a zero rate or suspension.
The transition and what it asks of a new unit
In 2026
For taxable events from 1 January to 31 December 2026: IBS at the state rate of 0.1% and CBS at the rate of 0.9%.
From 2027 to 2028
For taxable events from 1 January 2027 to 31 December 2028: IBS at the state rate of 0.05% and at the municipal rate of 0.05%.
Transition milestone, not a cost estimate
These numbers are a milestone of the transition period, not a cost estimate. The full rule of calculation, credit and offsetting is in the law and in the regulation, and the company's reading must be done on the act in force on the project date.
The effect for the rollout
At issuing
A new unit born in 2026 already needs to issue electronic tax documents with the fields of the new taxes, according to the layout technical notes.
In the data structure
Master data, registration and tax determination must support both regimes. The page on CBS/IBS tax reform covers the calendar and the adjustment.
The rollout needs only one guarantee: the group standard the new unit inherits is already reviewed for what is required on the opening date.
A rollout with an old standard is a future adjustment multiplied by the number of units.
A transition detail that depends on the establishment
The rule
LC 227/2026 provides that a taxpayer that holds, at the end of 31 December 2032, stock of goods subject to ICMS ST may take credit for the tax withheld.
The procedure
To do so, it must take an inventory of the goods in each of its establishments and send the inventory and the assessment statement to the UF where the establishment is located and to the IBS Management Committee.
Why it matters to the rollout
The inventory is per establishment. A unit opened before 2032 enters the universe of that inventory, and the traceability of what was withheld, when and by whom becomes worth money. That is why traceability of ICMS-ST per establishment, which looks like a setup detail today, gains weight as credit at the end of the transition.
Make sure, from the rollout onward, that each unit keeps the ST withholding history by document and by item, in the group standard, and not only in reports that are overwritten at each close.
What depends on regulation
Tax benefits, specific regimes and credit depend on regulation, technical notes and each company's specific situation, and the rules in force on the project date apply. For the document fields, the reference is the layout technical note in force on the issuing date.
What to check
- Group standard reviewed for what is required on the opening date.
- Unit registered in the new taxes according to the regulation in force.
- ST withholding history kept by document and by item.
- Document fields according to the technical note in force.
The real risks of the tax rollout: symptom, cause and check
The table lists the most common tax rollout errors in the form the team uses in practice: the risk, the symptom that shows up, the most likely cause and the check that detects it before go-live.
| Risk | Symptom | Probable cause | Check before go-live | Source or area |
|---|---|---|---|---|
| Inherited master data | NCM, origin or CEST different between units for the same item | Copy of master data from an old unit without review | Compare a sample of materials of the new unit with the standard and with the responsible tax person | Tax master data |
| Copied setup | Tax equal to the head office's where the state requires another | Rule copied from a unit in a different state | Check each rule against the state sheet, and not against the unit of origin | Tax setup |
| ST rule of the wrong state | Wrong or missing withholding, invoice rejection, disallowed credit | Agreement between UFs not checked for the route | Run the real operation routes in the test environment and compare with the destination legislation | Convênio ICMS 142/2018, cl. 2ª and 4ª |
| Expired certificate or from the wrong CNPJ | Invoice rejected or stuck at signing | Expiry with no owner; certificate installed in the wrong unit | Expiry control and signing test before go-live | Ajuste SINIEF 07/05, cl. 3ª, IV |
| Duplicate series or numbering | Rejection for duplication, or invoice authorized twice in the same series | Numbering range reused without checking what was already authorized | Query the authorized numbering per establishment and series and lock manual editing | Ajuste SINIEF 07/05, cl. 3ª, II |
| Missing accreditation | First invoice refused by the SEFAZ | Accreditation treated as a last-minute task | Confirm the accreditation of each document in the UF before the go-live date | Ajuste SINIEF 07/05, 09/07, 19/16, 21/10 |
| Branch SPED with head office data | Branch file with CNPJ, IE or balance of another unit | New unit configured with the head office context | Compare the header, IE and totals of the test file with the unit's record | Ajuste SINIEF 02/09, cl. 3ª, §6º |
| Unit missing from the centralized file | EFD-Contribuições without the new branch data | Head office consolidation not reviewed at opening | Check that the unit appears in the single file and in the ECF scope | SPED portal RFB; IN RFB 2.004/2021 |
| Supplier or customer without IE or with the wrong indicator | Tax and withholding inconsistent with the partner | Partner record replicated without the state check | Check partners of the highest value and volume, with the IE and the taxpayer indicator | Tax master data |
| Incomplete business place | CNPJ not found error at billing | Tax organizational structure created halfway | End-to-end billing test with the new unit | SAP Knowledge Base 2516939; SAP help |
| Transfer between units without design | ICMS treatment on transfer different from expected | Rule presumed, without checking the law and the state | Validate the applicable rule with tax and legal before switching on the flow | LC 87/1996, art. 12, I; Convênio ICMS 142/2018, cl. 13 §2º |
| Exception that becomes the standard | One unit's special rule shows up in the next one | Exception with no record, owner or deadline | Record every exception with justification, owner and review date | Project guidance |
The three errors that repeat most
The copy that looks like savings
Copying the neighboring unit's setup is quick, and works until the first different state. The cost shows up as rework in each copied unit. The documented standard costs more at the start and less in total, because fixing the standard fixes all of them.
The deadline that runs over the check
A rollout usually has a commercial opening date. When the date tightens, the check is the first thing to be cut. The result shows at the first close, which is the worst time to find out.
The exception with no owner
Every unit has a legitimate exception. The problem is not the exception, it is the exception with no record: over time, nobody knows whether it still applies.
When the error only shows at the first close, the path is post-go-live stabilization. The goal of a well-run rollout is that post-go-live stabilization is not needed.
Risks with a regulatory basis cite the act in the last column of the table. The acts and documentation behind them:
Choose, for each risk, a check before go-live and a person responsible for the evidence. Risks with no act cited in the last column are method practice and should be calibrated to the company's environment.
What to check
- Each risk has a check and an owner.
- Real routes run in the test environment.
- Certificate, accreditation and numbering checked.
- Exceptions recorded with owner, justification and review date.
The tax rollout in six steps
Six steps, from the group standard to the governance routine, each with a product, a decision-maker and exit evidence.
Group standard
Define what is equal in every unit: rules, master data, certificate policy, series, controls, with an owner and justification per item.
Pilot unit
Validate the standard in one unit, including the first close, before opening the second wave.
Waves
Group units by state or by CNPJ, handling in each wave only what is specific to the state or the unit.
Check per unit
Apply the same check before and after the cutover in each unit, with archived evidence.
First close
Follow the unit's first real tax close, with an escalation criterion defined in advance.
Stabilization and governance
Move the unit to the governance routine, with periodic review of the standard and the exceptions.
The design comes from a concept published on SAP Community's ERP blog channel: in SAP Activate projects with several sites, a template project builds the model and deploys it in the first wave of sites, and a rollout project reuses that model in the following sites. The same publication describes that, in the rollout, the fit-to-standard analysis focuses on local processes and on adjustments to harmonized processes, and that the development environment receives the template before each site.
The six steps are a method recommendation from DFSpro for the tax layer. The company can adapt the order and the names, as long as it keeps the check per unit and the evidence of each step.
What to check
- Each step has a product, a decision-maker and exit evidence.
- The pilot reached the first close before the second wave.
Who decides, what is produced and what proves it is finished
The six steps are most useful when each one answers three questions: what is produced, who decides and what proves it is finished.
| Step | What is produced | Who decides | Closing evidence |
|---|---|---|---|
| 01 Group standard | Catalog of tax rules with purpose and owner, certificate policy, series policy, master data model | Group tax lead, with IT and accounting | Approved standard document, with date and version |
| 02 Pilot unit | Unit with master data, accreditation, certificate and series ready and tested | Tax and IT, with the unit manager | Test invoices authorized and first close checked |
| 03 Waves | Plan by state or CNPJ, with state sheets and accreditation calendar | Project committee, with tax | State sheets approved and accreditations confirmed |
| 04 Check per unit | Single check script run before and after the cutover | Unit tax lead and tax consultancy | Script filled in and archived per unit |
| 05 First close | Unit close, SPED and returns of the first period | Unit tax lead, with accounting | Files validated and divergences handled |
| 06 Stabilization and governance | Routine to review the standard and record exceptions | Group tax lead | Review minutes and updated exception record |
What the unit can change in the standard: four categories
The SAP publication cited above describes five process categories, and the idea is useful for tax because it answers a question almost every rollout faces: what is the local unit free to change? Adapted to the tax context, the categories can be read like this:
| Category in the SAP publication | Meaning in the publication | Suggested tax reading (project guidance) |
|---|---|---|
| Global | Cannot be changed in the local rollout | Master data structure, document keys and certificate policy |
| Standard Complete | Use as delivered, with the option to extend with substructures | Group standard calculation rule, with additional unit fields |
| Standard Partial | Use as delivered, but with locally regulated subprocesses | Calculation with a state-specific part, such as ST and local obligation |
| Harmonized | Standardization recommended, not mandatory today | Internal controls in convergence, still varying between units |
| Local | Process defined by the unit according to local need | Municipal-specific taxation or state benefit |
Governance of deviations is the other idea to use. The publication cites a solution standardization board (Solution Standardization Board) to assess deviations from the template standard. In tax, the equivalent is a small committee, with the group tax lead and IT, that approves or denies the exception before it enters SAP, and records the reason.
Why pilot before wave
A pilot unit is not a less important unit. It is the unit where the cost of error is known and manageable, and the learning applies to the others. The pilot must reach the first tax close, because issuing the first invoice proves the document goes out, and only the close proves that the assessment, the SPED and the obligations close. The page on ECC to S/4HANA migration covers the same principle for the first wave of a version change; in the rollout, it applies to each new unit.
Why group by state or by CNPJ
Waves can be organized by state, when the dominant difference is the ICMS rule, or by CNPJ, when the dominant difference is the corporate structure and registration. Grouping by state reduces the cost of checking the rule once and applying it to several units in that state. Grouping by CNPJ reduces the cost of certificate, accreditation and consolidation. When both dimensions weigh, the plan mixes the two, and the rule of thumb is never to open, in the same wave, more new states than the tax team can check in depth.
The tax clock rules the calendar
A cutover in the middle of the close turns the unit's first SPED into an incident.
Set the opening date in relation to the unit's tax calendar, avoiding the close and obligation delivery windows, and leave a margin between the issuing of the first invoices and the first close, so there is time to fix things. The page on post-go-live stabilization describes the follow-up of the first cycle.
What to check
- Opening date outside the close and obligation delivery window.
- Exceptions committee defined, with the group tax lead and IT.
- Waves organized by state or by CNPJ, with no more new states than the tax team can check.
Tax go-live checklist per unit
A set of verifiable items for each unit that comes in, from registration to cutover.
Registration and identity
- Registration certificate and status of the unit's CNPJ, with an active status.
- Active state registration and registration data equal to SAP's (corporate name, address, regime).
- Municipal registration, when the unit provides services, and adoption of the municipality's NFS-e standard.
- Registration of the establishment in the new taxes, according to the regulation in force on the date.
Electronic documents
- Accreditation for each document the unit will issue (NF-e, NFC-e, CT-e, MDF-e, NFS-e), in the UF or municipality of registration.
- Valid digital certificate, with the expiry date recorded and a renewal owner.
- Series and numbering range defined per unit and per document type, with no overlap with numbers already authorized.
- Test invoices authorized in the test environment for each type of operation (sale, transfer, return, service).
State rules
- State sheet filled in: ST, DIFAL, FCP, benefits, ancillary obligations, with the source link and check date.
- Real sales routes tested, with the tax result compared with the destination state rule.
- Unit material master with consistent NCM and CEST, and highest-volume partners checked for IE and taxpayer indicator.
- Exceptions recorded with owner, justification and review date.
Assessment and obligations
- Complete SAP structure: company code, business place with CNPJ and IE, assigned plants and numbering ranges.
- Test EFD ICMS IPI generated for the unit and compared with the record (CNPJ, IE and totals).
- Unit present in the files centralized by the head office, such as EFD-Contribuições, and in the ECF scope.
- Unit tax calendar loaded and owners for each delivery defined.
Cutover and follow-up
- Opening date set outside the month's close window.
- Owner of the first close follow-up and escalation criterion defined before the cutover.
- Evidence archived: check script, test invoices, test SPED files and decision minutes.
- Unit handed to the governance routine, with the date of the first review of the standard.
A checklist only has value if each item has an owner and evidence. Ticking an item as done with no attachment is the most common way a checklist turns into a ritual. Sample checking of master data is detailed on the page on tax master data, and the diagnostic that organizes this sample by risk is in SAP Tax Diagnostic.
Who does what, and what evidence is left
Tax rollouts fail more for roles with no owner than for technology. The table suggests who answers for what and what evidence each role should leave.
| Role | Answers for | Evidence it leaves |
|---|---|---|
| Group tax lead | Tax standard, state sheets, approval of exceptions, acceptance of the first close | Versioned standard, approved sheets, exception record |
| Unit tax lead | Day-to-day operation, check per unit, delivery of the unit's obligations | Filled-in check script, transmission receipt of the files |
| IT and basis | Organizational structure in SAP, installed certificates, environments and transports | Record of transports and technical tests, certificate control |
| Accounting | Consolidation, ECD and ECF, tax and accounting reconciliation of the new unit | Reconciliation of the first close |
| SAP integrator | Technical build of the rollout, module configuration, cutover | Cutover plan, technical documentation, integrated tests |
| Tax consultancy | Tax layer of the project: method, independent check, decision support | Check report, risk map, follow-up plan |
| Legal and tax advisory | Positions on tax thesis, transfers between establishments, benefits and regimes | Opinion or internal note per topic |
Two remarks. First, the integrator and the tax consultancy have different scopes: the integrator delivers the technical configuration, and the tax consultancy makes sure the tax layer of that configuration is correct, documented and checked. Second, the tax position remains the company's decision, with the legal and tax support it chooses. The page on governance AMS Fiscal describes the follow-up after the rollout ends, so the standard does not disperse again.
What to check
- Each role has the evidence it leaves defined and archived.
- The integrator's scope and the tax consultancy's scope are separate in the plan.
- The tax position stayed with the company and with the legal support it chose.
Where GUEPARDO Tax comes into the rollout
GUEPARDO Tax is an NTT DATA product, and DFSpro sells the license as an Authorized Channel. The question here is what changes in the rollout when the environment uses the tax engine.
The official GUEPARDO site, maintained by NTT DATA, states that the product has compatibility certifications with SAP DRC and SAP TDF, as well as SAP S/4HANA Cloud Private Edition. The details of how GUEPARDO Tax is configured for a new unit follow the product documentation and the NTT DATA implementation team.
The point of contact between the rollout and the tax engine deserves a method rule. When tax calculation is in GUEPARDO Tax, the rollout of a new unit includes the unit in that calculation layer, with the state rules and the master data the engine consumes. DFSpro's governance work is the same as in any rollout: sheet per state, check per unit, evidence. The page on GUEPARDO Tax describes the product and DFSpro's role, and the page on S/4HANA migration covers the integration between SAP and the engine when the version changes.
License and governance are different things
The GUEPARDO Tax license is an NTT DATA product, sold by DFSpro as an Authorized Channel. Governance of the tax layer, that is, the state sheet, the check per unit, the evidence and the periodic review, is method work and applies to any SAP environment, with or without the engine.
What to check
- Unit included in the calculation layer, with the state rules.
- Master data consumed by the engine checked.
- Configuration according to the product documentation and the implementation team.
How DFSpro works in the rollout
DFSpro is a Continuous Tax Governance consultancy for SAP, founded in 2018 in Curitiba. It works on the tax layer of the project and does not replace the integrator.
In the rollout, this means the following. The SAP integrator remains responsible for the technical build, the modules and the cutover. DFSpro works alongside it on the tax layer: what must be set up, what must be tested and what must be documented so that each new unit comes in with the same standard and with exceptions recorded. The work is organized in DFSpro's service lines: the SAP Tax Diagnostic, the ECC to S/4HANA migration, the post-go-live stabilization and continuous governance.
The usual boundaries also apply: the decision on tax thesis remains the company's, DFSpro delivers recommendations and checks, and changing master data or configuration in the environment belongs to the customer or its technical team. Tax rollout is a topic where these boundaries matter, because it involves a lot of environment change in a short time.
Whoever wants to understand how the method applies to their case can start with the 2-minute readiness assessment, which helps organize the questions before any conversation, or talk directly through the contact page.
One group, three establishments and one new state
The following example is illustrative and entirely hypothetical, with no real customer. It serves to show the order of decisions, not to suggest a deadline or result.
Group with three CNPJs
An industrial group with SAP and three establishments in two states decides to open a distribution center in a third state.
Is there a standard?
The group tax lead notices that each unit handles the same tax in its own way. The first deliverable of the project becomes the standard.
What does the new state require?
The state sheet is built: ST of the goods sold, DIFAL and FCP, benefits, ancillary obligations.
What must exist before the invoice?
CNPJ, IE, accreditation, certificate, series and business place, with dates in the schedule.
Step by step:
- Write the group standard in a short document, with the rules that apply to all units and those that vary by state. Each rule has an owner.
- Fill in the new state sheet, with the official source of each decision and the check date.
- Create, with the integrator, the SAP structure of the new unit: company code, business place with CNPJ and IE, plants and numbering ranges.
- Accredit the unit at the state SEFAZ and check the certificate and the series.
- Test the real sales routes in the test environment, comparing the result with the state sheet.
- Generate a test EFD and check CNPJ, IE and totals.
- Choose the opening date outside the close window and define who follows the first close.
- After the first close, record what the unit taught the standard and hand it to the governance routine.
What the example shows is a simple rule. The hard work of a tax rollout is in reaching the new unit with the standard ready and the check agreed, and not in improvising answers when the first close arrives.
What to check
- Standard written before the state sheet.
- Accreditation, certificate and series ready before the first invoice.
- Test EFD checked against the record.
- Owner of the first close defined.
Sources of each fact
Legislation and official documentation, with a link to the text.
- LC 87/1996 (Lei Kandir), art. 11 and art. 12, Planalto
- LC 190/2022, DIFAL, Planalto
- LC 116/2003 (ISS), arts. 3º and 4º, Planalto
- LC 214/2025 (CBS, IBS, IS), Planalto
- LC 227/2026, Planalto
- Convênio ICMS 142/2018 (tax substitution), Confaz
- Ajuste SINIEF 07/05 (NF-e), Confaz
- Ajuste SINIEF 09/07 (CT-e), Confaz
- Ajuste SINIEF 21/10 (MDF-e), Confaz
- Ajuste SINIEF 19/16 (NFC-e), Confaz
- Ajuste SINIEF 02/09 (EFD), Confaz
- IN RFB 2.119/2022 (CNPJ), text at Lex Editora
- IN RFB 2.004/2021 (ECF), Receita Federal
- IN RFB 1.252/2012 (EFD-Contribuições), Receita Federal
- SPED portal, EFD-Contribuições, Receita Federal
- Electronic Invoice Portal
- Mato Grosso do Sul SEFAZ, end of GIA-ST (28/07/2020)
- Alagoas SEFAZ, special ST regimes
- Goiás SEFAZ, DnC Portal (DIFAL of non-taxpayers)
- SAP Help Portal, Business Place (classic documentation)
- SAP Knowledge Base 2516939 (CNPJ not found, 8B060)
- SAP Community, SAP Activate in multi-country deployments (19/04/2021)
- SAP, Document and Reporting Compliance (Brazil)
- SAP Community, TDF SP15
- SAP Community, end of maintenance of SAP NF-e (GRC)
- GUEPARDO (NTT DATA), tax software and certifications
Questions to bring to your internal conversation
01What is a tax rollout and how does it differ from a migration?+
A tax rollout is the replication, with checks, of the SAP tax standard in a new unit: branch, CNPJ, state registration, plant or state. A migration changes the version or the architecture of the system. The two can meet, as when the waves of a migration are units, but the rollout also exists without a version change. The section on situations has the classification table.
02Does every branch require a tax rollout project?+
Not necessarily. A small unit, in the same state and with operations equal to the existing ones, can be a light rollout, with a checklist and a check. What makes the project bigger is a change of state, a change of operation (for example, industry instead of distribution) and the absence of a documented group standard. The classification is the company's decision, and the recommendation is to check the two questions in the situations section.
03Does each establishment need its own CNPJ?+
According to the CNPJ rule, entities register in the registry, and so does each of their establishments, before starting activities (IN RFB 2.119/2022, art. 4º). If the place is an establishment, in the sense of the rule, it has its own registration. The company should confirm the nature of each place with its accountant, because the definition of establishment has legal contours.
04Can the head office certificate be used to issue branch invoices?+
Ajuste SINIEF 07/05 requires a digital signature certified by ICP-Brasil that contains the CNPJ or CPF of any of the taxpayer's establishments (cl. 3ª, IV). The rule, therefore, allows the certificate of any establishment of the owner. Whether this is suitable in practice depends on the security policy, the certificate type, expiry management and the state or municipality rules for the document. The company should decide and record the policy.
05Does the accreditation to issue NF-e apply to all states?+
Ajuste SINIEF 07/05 (cl. 2ª) requires prior accreditation in the federative unit in whose ICMS registry the taxpayer is registered. A unit in another state has a registration in that state and, therefore, accreditation at that SEFAZ. The procedure, the deadline and the portal vary by state.
06Is a duplicate series across branches a problem?+
NF-e numbering is sequential per establishment and per series (Ajuste SINIEF 07/05, cl. 3ª, II), and the issuer's CNPJ is part of the access key. What causes rejection is repeating a number within the same establishment and series. The project precaution is to define the series policy per unit and per document type, before go-live, and to lock manual editing of numbering.
07How do I know whether the goods are subject to tax substitution in the new state?+
Under Convênio ICMS 142/2018, adopting ST in an interstate operation depends on a specific agreement between the federative units, and the substitute taxpayer follows the legislation of the destination UF. The answer, therefore, requires the CEST and NCM of the goods, the route and the legislation of the destination state. The recommendation is to record the answer in the state sheet.
08What is DIFAL and why does it appear in the rollout?+
It is the difference between the internal rate of the destination state and the interstate rate, due to the destination on operations to final consumers, under LC 190/2022. Whoever opens a unit in a new state and sells to final consumers in other states starts to have an assessment and payment flow per state. The states' portals detail the routine, such as the Goiás SEFAZ portal for the DIFAL of non-taxpayers.
09Is the EFD one per branch?+
Ajuste SINIEF 02/09 (cl. 3ª, §6º) says that the EFD requirement covers all establishments of the taxpayer located in the federative unit. How the generating program organizes the files by state registration is in the EFD practical guide and in the Receita and SEFAZ program, and it is worth checking there. EFD-Contribuições, in turn, is centralized by the head office.
10Do EFD-Contribuições and ECF change when I open a branch?+
Because EFD-Contribuições is centralized by the head office, in a single monthly file, and ECF is reported centrally by the head office, the new branch appears in the head office data, and not in a file of its own. The typical error is forgetting to include it. The rollout check must confirm the unit's presence in the centralized files.
11What does the tax reform change for a unit opened in 2026?+
LC 214/2025 provides for a single registry (CNPJ) for IBS and CBS, issuing of an electronic tax document and a place of operation defined by its own rule, plus test rates in 2026 (IBS at 0.1% state and CBS at 0.9%). A new unit must be born with the data structure that supports both regimes, according to the technical notes in force.
12What is the ST inventory in 2032?+
LC 227/2026, arts. 142 to 144, allows a taxpayer with stock of goods subject to ICMS ST at the end of 2032 to take credit for the tax withheld, through an inventory at each establishment and submission to the UF and to the CGIBS. The consequence for the rollout is to keep, per establishment, the ST withholding history.
13How long does a tax rollout take?+
It depends on the number of units, the number of states, the quality of the group standard and the availability of the tax team. There is no deadline in the abstract that fits every case. The useful question is what the critical path is: accreditation, certificate and checks usually define the date.
14Do I need GUEPARDO Tax to do a tax rollout?+
No. The tax rollout is a method that applies to any SAP environment. When the environment uses GUEPARDO Tax, an NTT DATA product, the new unit also needs to enter that calculation layer. DFSpro sells the license as an Authorized Channel and works on the governance of the environment, with or without the product.
15Does DFSpro replace the integrator in the rollout?+
No. The SAP integrator remains responsible for the technical build. DFSpro works on the tax layer of the project, alongside it: what must be set up, what must be checked and what must be documented.
16How do I prevent one unit's rule from becoming the next one's standard?+
By recording every exception with an owner, justification and review date, and approving the exception before it enters SAP. For template projects, SAP describes a standardization board that assesses deviations. In tax, a small committee fills that role. This is project guidance.
17What if the new unit's first close does not match?+
Treat it as an incident with an escalation criterion defined in advance: freeze rule changes, compare the unit's master data, rule and document with the standard and with the state sheet, and involve the group tax lead. The page on post-go-live stabilization details the follow-up of the first cycle.
18Where do I start?+
With two things: check whether there is a documented group tax standard, with an owner, and fill in the new state sheet. To organize the questions, the 2-minute readiness assessment helps, and a conversation through the contact page lets us discuss your case.
Reach the new unit with the standard ready
The first step is to know where the group stands: whether there is a documented standard, how many units already follow the same criterion and which states are on the horizon. The readiness assessment organizes these questions in two minutes, and a conversation through the contact page lets us discuss your case, with no price and no commitment on deadline.
To go deeper first: ECC to S/4HANA migration, tax setup, tax Clean Core and multi-CNPJ tax governance.