Tax master data in SAP: the root cause of many tax mismatches
Before a rule calculates the tax, the master record tells the rule what is being calculated: which product, from which origin, for which partner, in which branch. If the record is wrong, the right rule gives the wrong result.
The master data behind tax in SAP, how it fails, and the check that keeps it reliable.
Before a rule calculates the tax, the master record tells it what is being calculated: material, partner, branch. A wrong record makes the right rule give the wrong result, and the error repeats in every document. DFSpro checks the highest-impact master data by sample, without changing the system.
Choose your entry point by your role
Four entry points, one per role, straight to the block that answers your question.
01Tax and accounting
The three records that support tax, where each one fails, and what shows up in SPED.
Go to the section02IT and SAP integrator
How the check works in four steps, from the record to the rule, and the partner record.
Go to the section03Management and decisions
Who maintains the tax record and which signs show the problem is in the data.
Go to the section04NCM and tax reform
NCM as the record that decides the tax, and the questions about NCM and the reform.
Go to the sectionDirect links
Three records support tax
In the record, what supports the checks of CFOP (Brazil's code for the type of operation), CST (Brazil's tax situation code), NCM (the Mercosur Common Nomenclature, the tax classification of goods) and the tax setup per branch.
Material
NCM, origin, CEST and tax classification group. This record feeds tax determination more than any other, and it is the one most often changed without tax review.
Customer and supplier
CNPJ (the Brazilian company tax ID) or CPF, state registration, tax regime and taxpayer indicator. It defines how ICMS (Brazil's state value-added tax) and withholdings are treated.
Branch and company
CNPJ, registration, regime and tax setup per unit. In groups with several CNPJs, differences between branches are a risk in themselves.
What SAP does not check on its own is whether the content of a field is right for the operation. A filled field does not mean a correct field. The acronyms on this page are in the glossary.
An error in the record repeats in every document
A wrong rule affects a group of operations, and it is usually noticed. A wrong record affects every document that uses that record, and the effect spreads quietly: the cost of one item, the credit of another, the SPED (Brazil's digital tax reporting system, the set of digital filings sent to the tax authorities) of a third.
It is also the cause that hides behind other causes most often. The close does not match, people look for the rule, they adjust the rule, and the record stays wrong. The adjustment works until the next material of the same type.
That is why the check starts with the data. When the record is correct, what remains of the mismatch is the rule, and the investigation gets smaller.
Where master data fails and what shows up
What shows up in each system varies.
| Data | Typical failure | What shows up |
|---|---|---|
| Material NCM | A code different from what the tax authority or the import declaration requires. | Tax calculated with the wrong rate and a difference in SPED. |
| Material origin | Origin indicator not reviewed, especially for imported goods. | Wrong interstate ICMS and a credit disallowed by the tax authority. |
| CEST | Missing or not matching the NCM on an item subject to tax substitution. | Rejection or wrong handling of the tax substitution. |
| Partner regime and indicator | Outdated taxpayer or regime record. | Taxation and withholding that differ from the partner's real situation. |
| Partner CNPJ | A field that assumes digits only, now that the CNPJ can contain letters. | Record, validation or integration failure. See the page on Tax Reform: CBS and IBS. |
| Tax setup per branch | Branches of the same group treating the same tax in different ways. | Differences between units and an unstable close. |
The item on the alphanumeric CNPJ follows the Federal Revenue regulation, described on the reform page.
Signs that the problem is in the record
If more than one item on the list sounds familiar, check the data before you review the rule.
- The same type of mismatch returns at every close, on different items.
- The fix is always made in the document or in the tax calculation, never in the record.
- NCM or classification changes that do not go through the tax team.
- A side spreadsheet to check the records, kept by one person only.
- Branches of the same group with different treatment for the same item.
Master data check in four steps
The four steps below describe how the master data check is run, from the record to the rule.
Extraction
Select the relevant records and extract a sample by type, without changing the system.
Check rule
Define what is correct for each field, together with the tax team: NCM, origin, CEST, regime.
Mismatches
List what fails the rule, ranked by tax impact and by number of documents.
Fix at the source
Fix the record and the process that produces it, so the error does not come back.
Who maintains the tax record
Fixing the data is a one-time job. Maintaining it is ongoing work.
Ask internally
Who approves the creation and change of a tax record, and does the tax team take part? When the record process and the tax process do not talk to each other, the error comes back. The SAP Tax Diagnostic includes the check of critical master data.
Duplicates, public lookup and personal data in the partner record
The partner is created in purchasing, sales or finance, rarely in tax, and what was typed there flows on to the tax, the invoice and the filing. Three points in the record need proof.
Public lookup
The Consultar CNPJservice, from gov.br, checks that the company exists, its registration status and its partners. It is valid for the day of the lookup: the status can change later. State registration is checked on each state's portal (not checked).
Duplicates
According to SAP (KBA 2886187, read on 16/10/2026), in S/4HANA Cloud Public Edition the duplicate check by tax number category comes switched off (Off): the same number enters two partners with no warning and no error. When it is on, it warns, and the warning can become an error. The warning for a potentially duplicate partner at creation is the behavior described in SAP Learning. How it works for the CNPJ in each edition was not checked.
Personal data
The record of a partner's owner or of an individual is personal data. The LGPD (Brazil's data protection law) asks for purpose, necessity and security (arts. 6 and 46) and gives the data subject the right to correct outdated data (art. 18). The legal basis is the client's decision.
What to keep as proof
- Proof of the CNPJ lookup, with the date.
- The result of the duplicate test in a test system, warning or error.
- Purpose and retention period for personal data, defined by the client.
According to NTT DATA (read on 16/10/2026), the GUEPARDO Process Automation handles master data and repetitive tasks; the public databases it queries are not published. DFSpro acts as an Authorized Channel for selling GUEPARDO: it licenses, implements the module and follows the record in governance. For the CNPJ format, see the page on alphanumeric CNPJ.
Sources read on 16/10/2026: SAP Learning, SAP Knowledge Base 2886187, gov.br and Law 13,709/2018.
NCM and tax classification: the record that decides the tax
NCM is the material field that decides tax the most: today for IPI, imports and tax substitution, and under the reform also for the IBS and CBS rate. The full design, from the official table to the invoice, with classification rules, penalties and the review of the record, has its own page.
Questions about NCM and the reform, the most frequent
01Does NCM also apply to services?+
No. The EFD ICMS/IPI Practical Guide says there is no NCM for services. For services the law uses NBS, and the national-standard NFS-e requires NBS on every invoice.
02If the NCM is on the annex list, is the benefit guaranteed?+
Not always. Some items carry a product condition, such as the milk in Annex I, which must comply with the specific legislation, and the medical devices in Annex IV, which must be registered with Anvisa (art. 131, § 1). The medicines in art. 146 depend on the use that matches the health registration. NCM is a necessary condition, not a sufficient one.
03What happens if the NCM changes by official act?+
It depends on what the change does. For tax substitution, ICMS Agreement 142/2018 says that reclassification or splitting neither adds nor removes the good and that the document carries the NCM in force. For Complementary Law (LC) 214/2025, art. 492, § 2, protects the earlier classification of the products named in the law. In all cases, the record must be reviewed.
04Who decides the NCM of a product?+
The company classifies its own product, following the rules of the nomenclature. The consultation service on tax classification is the Federal Revenue's responsibility. DFSpro finds the mismatches in the record and indicates the fix, and does not replace the client's classification decision.
05How do I start reviewing the NCM record?+
With a sample of the highest-value materials and those that appear in the reform annexes. Compare the material NCM with the one in the info record, the one in recent orders and invoices, and the one in record 0200. Where there is a difference, fix it at the source.
Blog articles about records and zero rate
Frequently asked questions to take to your internal conversation
01What is tax master data?+
It is the records that feed tax determination: material, customer and supplier, branch and company, with fields such as NCM, origin, CEST, CNPJ, registration and regime.
02Does SAP check that the NCM is correct?+
SAP checks the format and, depending on the setup, that the code exists. Whether the code is the right one for the goods is a tax check.
03Why does the mismatch come back after it was fixed?+
Because it was fixed in the document or in the tax calculation, and the source record is still wrong. Fixing at the source ends the cycle.
04Does DFSpro fix the record?+
DFSpro finds the mismatches and indicates the fix. Changing the record in the system is up to the client or the client's technical team.
05Does this apply only to those who use GUEPARDO Tax?+
Master data applies to any SAP system.
06What changes does the alphanumeric CNPJ bring?+
Fields and validations that assume digits only become points of failure. The tax reform page gives the detail.
07How long does a check take?+
It depends on the number of records and the number of companies. DFSpro does not promise a timeline without knowing the system.
08Where do I start?+
With a sample of the highest-volume materials and the highest-value partners. The SAP Tax Diagnostic organizes that sample by risk.
09Does SAP stop you from registering the same CNPJ twice?+
It depends on the setup and the edition. In S/4HANA Cloud Public Edition, SAP documents the check by tax number category as switched off by default (KBA 2886187, read on 16/10/2026, with an example from another country). How the CNPJ behaves in each edition was not checked: test it in your system.
10Who checks the supplier's registration status before payment?+
The client's process. The public CNPJ lookup shows the status of the day, not tomorrow's (gov.br, Consultar CNPJ, read on 16/10/2026). DFSpro designs where the check enters the record and the payment and proves that it happens; whether to block payment by registration status is the client's decision.
11Does the partner record hold personal data, and how long should it be kept?+
It does, when the partner is an individual or when an owner is in the record. The LGPD requires purpose, necessity and security (arts. 6 and 46) and requires the data to be deleted at the end of processing, except where it must be kept to meet a legal obligation (art. 16, read on 16/10/2026). The retention period is the client's decision with legal counsel, by document type.
Check the record before you review the rule
The first step is a sample-based check of the highest-impact master data.