Pular para o conteúdo
Problems · from symptom to path

SPED will not close, the invoice was rejected, the tax was calculated wrong: see the path for each symptom

This page starts from what you see day to day, not from the name of a service. It covers 16 tax symptoms in SAP, in eight areas, with what is usually behind each one (as a hypothesis), what to check first and the page that leads to the right path.

The work of DFSpro, a specialist in tax in SAP and in GUEPARDO Tax, is on the system side. What the tax authority requires in each case, the company decides.

Run the triage in three questionsTalk to DFSpro
Versão em português
Index

Start with the area where the problem shows up

Eight areas, one entry for each place where the symptom usually shows first. Each entry leads to the matching symptom.

01Assessment

When the tax number does not match, disappears or arrives different. Symptoms 01, 02, 03.

See the symptoms in this area

02Invoices

When the invoice does not go out, goes out different or is entered by hand. Symptoms 04, 05, 06.

See the symptoms in this area

03SPED

When the file is refused or differs from the assessment. Symptoms 07, 08.

See the symptoms in this area

04Master data

When the master data and the rule stop being reliable. Symptoms 09, 10.

See the symptoms in this area

05Reform

When nobody can say what SAP needs to change. Symptom 11.

See the symptoms in this area

06Foreign trade

When imports and exports do not talk to SAP. Symptom 12.

See the symptoms in this area

07Systems

When the version, the rule or the switch of solution has no plan. Symptoms 13, 14.

See the symptoms in this area

08Support

When a change or the end of the project leaves tax without an owner. Symptoms 15, 16.

See the symptoms in this area
Shortcuts
Shortcuts:triage in 3 questionssymptom tablehow we worklimit of our rolesourcesquestions
The short answer

A tax symptom almost never has a single cause, and the path starts by measuring the case

The direct answer

When tax in SAP goes wrong, what shows up is the effect: a refused file, a rejected invoice, a number that does not close. The cause may be in the master data, the rule, the process or a recent change, and it is confirmed only by reproducing the case in a test. This page links each symptom to the service that handles the cause, without promising that the hypothesis holds.

What this page does

It describes the symptom as it appears, suggests likely causes, points to what to check first and leads to the right service, tool, law or article page.

What it does not do

It does not explain each service, because each service page already does that. It also does not diagnose your system: a cause is confirmed only with your document and your SAP.

How to use it

Run the triage in three questions, or go straight to the area in the index. Read the symptom, check the three points and, if the case persists, bring the example to the conversation.

Triage

Three questions to know where to start

Answer in whatever order makes sense. The list of symptoms appears when you choose the area, and the other two answers add the first check and what to gather.

The triage needs JavaScript. Without it, use the index by area, above, to go to the symptom.

Guidance, not a decision. The triage suggests hypotheses and an order of checks, without diagnosing your system. What you select does not leave your browser.

1. Where does the problem show up first?
2. When did it start?
3. What do you already have at hand?

Where to start

Choose the area of the problem to see the symptoms.

Symptoms, part 1 of 3

When the tax number does not match and when the invoice does not go out

Note. The cause is always a hypothesis: it becomes fact only when the case is reproduced in a test. The checklist follows an order, from what costs least to what costs most. The risk block says when it is worth taking the issue out of the queue.

Assessment and reconciliation

When the tax number does not match, disappears or arrives different.

01Assessment and reconciliation

The assessment does not match the general ledger

At close, the tax balance in the assessment differs from the balance in the ledger account, and the gap is explained in a spreadsheet every month.

Likely causes (hypothesis)

  • An accounting entry created outside the tax document, with no link to the assessment.
  • A document booked in one period and posted in another.
  • A manual adjustment in the assessment with no matching entry in accounting.

What to check first

  1. Pick one gap from the month and follow the document from the accounting entry to the assessment.
  2. List the manual adjustments of the period, with who made them and when.
  3. Compare two months in a row to see if the gap repeats in the same account.

It is a risk when

The gap repeats every month, grows over time or reaches the file the company delivers to the tax authority.

Path

02Assessment and reconciliation

The ICMS, PIS or Cofins credit is lost

The credit balance grows unused, or the credit from a purchase or an asset does not appear in the assessment and nobody can say why.

Likely causes (hypothesis)

  • An entry document missing the data that the credit requires.
  • A credit rule not set up for the operation type.
  • A fixed asset with no asset record and no monthly installment created.

What to check first

  1. Take three entry documents with expected credit and see where the credit stopped.
  2. Check whether the operation type has a credit rule in SAP.
  3. For assets, check whether each asset has a record and whether the month's installment was created.

It is a risk when

A lost credit is value the company stops using, and a credit used without proof is exposed in an audit.

Path

03Assessment and reconciliation

The tax is calculated wrong or the payment slip differs from the document

The invoice goes out with a rate, base, ICMS-ST or DIFAL different from expected for an operation type, product or state, or the payment slip does not match the document.

Likely causes (hypothesis)

  • A tax determination rule that does not cover the combination of state (UF), product and operation.
  • Tax master data that differs from what the rule expects, such as the item classification.
  • A rule with an expired validity, or two rules overlapping.

What to check first

  1. Reproduce the case in a test environment with a sample document.
  2. See where each part of the calculation came from: rule, master data or manual adjustment.
  3. Compare the result with the rule your tax team confirmed for that operation.

It is a risk when

The error is recurring in volume, was already booked or created a payment slip paid too high or too low.

Path

Electronic documents and NFS-e

When the invoice does not go out, goes out different or is entered by hand.

04Electronic documents and NFS-e

The invoice was rejected or stays without authorization

The NF-e comes back rejected by the state tax authority (Sefaz), or stays stuck in processing, and billing waits for someone to understand the message.

Likely causes (hypothesis)

  • Issuer, recipient or product master data with a value outside the validation rule.
  • A new NF-e layout or rule not yet reflected in SAP.
  • A communication, certificate or numbering sequence failure.

What to check first

  1. Read the code and the text of the rejection before reissuing.
  2. See whether the rejection repeats for the same issuer, state or product.
  3. Compare with what changed in SAP or in the layout the week before.

It is a risk when

The rejection is in volume, blocks shipping or forces you to work in contingency.

Path

05Electronic documents and NFS-e

Incoming invoices are entered by hand

The purchase NF-e and CT-e arrive by e-mail or portal, and the team types or checks them one by one before posting them in SAP.

Likely causes (hypothesis)

  • XML receipt not integrated with SAP.
  • Frequent mismatch between invoice and order, with no tolerance rule.
  • Document events, such as cancellation, with no automatic handling.

What to check first

  1. Count how many documents of the month were entered by hand and why.
  2. Split the mismatches by type: price, quantity, tax or master data.
  3. See who follows the cancellation and acknowledgment events.

It is a risk when

The queue of invoices without entry grows, the credit is late or a cancelled document is booked.

Path

06Electronic documents and NFS-e

The NFS-e goes out different in each city

Each city asks for a different layout, portal or withholding, and the team keeps rules and exceptions by city.

Likely causes (hypothesis)

  • The national standard living beside each city's own standards.
  • A service code with no mapping to each city's list.
  • An ISS withholding rule set up by city, with no owner.

What to check first

  1. List the cities where the company issues and which standard each one uses.
  2. Check the service code mapping by city.
  3. See who updates the rule when a city changes its portal or rate.

It is a risk when

The invoice is refused by the city, ISS is withheld differently from what is required or issuing stops because of a portal change.

Path

Symptoms, part 2 of 3

When the file is refused, master data fails and the reform arrives

SPED and obligations

When the file is refused or differs from the assessment.

07SPED and obligations

The SPED Fiscal has an error or a mismatch

The PVA (the validation program) refuses the EFD ICMS/IPI file, or the file passes but the totals do not match the assessment and the books.

Likely causes (hypothesis)

  • A document missing data that the record requires, such as participant or item.
  • A version of the current Practical Guide different from the one SAP generates.
  • Bookkeeping past the deadline or a correction with no control.

What to check first

  1. Open the PVA error report and group by record.
  2. Compare the file totals with the assessment of the same period.
  3. Check which version of the Guide the company uses and the date of the layout generated.

It is a risk when

The delivery deadline gets close with no valid file, or the delivered file differs from the assessment.

Path

08SPED and obligations

Block K or the Block H inventory does not close

The stock in the file does not match the accounting stock, the production record does not become an entry or the inventory goes out with the wrong reason.

Likely causes (hypothesis)

  • A production order recorded in a way the record cannot read.
  • Material held by third parties with no control of the stock owner.
  • An inventory with no reason given in the movement master.

What to check first

  1. Compare the file balance with the accounting stock of one month.
  2. Follow one production order from the record to the entry.
  3. List the materials held by third parties and see whether the file separates them.

It is a risk when

The stock reported to the tax authority differs from the company's stock.

Path

Setup and master data

When the master data and the rule stop being reliable.

09Setup and master data

The tax master has wrong NCM and other data

Materials with swapped NCM, CST or origin, items with no classification and batch fixes that nobody knows are right.

Likely causes (hypothesis)

  • A master created by several areas with no filling rule.
  • A classification never reviewed after a table change.
  • No validation at the moment the material is created.

What to check first

  1. Pull a sample of the best-selling materials and compare the NCM with the classification the tax team confirms.
  2. See who can create and change the field.
  3. Cross the rejections and calculation errors with the same materials.

It is a risk when

The master error repeats in every document of the item and multiplies in calculation, in files and in the reform.

Path

10Setup and master data

Companies in the same group apply the same rule in different ways

Two companies in the group issue the same type of invoice with different taxation, and the difference shows up only in an audit or in the migration.

Likely causes (hypothesis)

  • Each unit set up tax its own way, through acquisition or expansion.
  • There is no single model with a defined owner.
  • A change applied in one company and forgotten in the others.

What to check first

  1. Compare the rule for the same operation in two companies.
  2. See whether there is a document stating the group standard.
  3. List the changes of the last months and which companies they were applied to.

It is a risk when

Unequal treatment between companies of the same group is hard to defend and makes the rollout more expensive.

Path

Tax reform

When nobody can say what SAP needs to change.

11Tax reform

We do not know what SAP needs for CBS and IBS

The tax reform is on the calendar, but nobody can say which part of SAP changes, when and who is responsible for it.

Likely causes (hypothesis)

  • The scope of the reform was not translated into SAP items.
  • Masters without the new data, such as the item classification and the alphanumeric CNPJ.
  • Reform SAP Notes not yet applied.

What to check first

  1. Take an inventory of what the reform touches: document, master data, calculation, file and integration.
  2. Check the status of the reform SAP Notes in your system.
  3. Define who in the company is responsible for the thesis and who for SAP.

It is a risk when

The test period arrives with no inventory, and the thesis decision is left too late.

Path

Symptoms, part 3 of 3

When imports, GUEPARDO or support are left without an owner

Foreign trade

When imports and exports do not talk to SAP.

12Foreign trade

Import or export does not talk to SAP

Declaration, process and document data from the Single Portal reach SAP by typing or differ from what tax posts.

Likely causes (hypothesis)

  • No integration, or a partial one, with the Single Portal.
  • Import taxes and costs with no standard allocation.
  • The foreign trade process and the tax process in systems with no common key.

What to check first

  1. Follow one import from the process to the tax document and the material cost.
  2. List what is typed and what is integrated.
  3. See who checks the tax calculation base.

It is a risk when

The declaration differs from the bookkeeping, or the material cost is calculated on the wrong base.

Path

GUEPARDO and integrations

When the version, the rule or the switch of solution has no plan.

13GUEPARDO and integrations

The GUEPARDO Tax release is behind

The company uses an old version of GUEPARDO Tax, a product of NTT DATA, and nobody knows what the update changes in the tax rules.

Likely causes (hypothesis)

  • A release update with no owner and no window.
  • Fear of breaking a customized rule.
  • No tax regression test.

What to check first

  1. See the version in use and the date of the last update.
  2. List the customized rules that the update may touch.
  3. Define the regression script before asking for the window.

It is a risk when

The rule changes and the version in use does not follow, or the update is done without proof.

Path

14GUEPARDO and integrations

The GRC NF-e has no replacement plan

The company issues through the GRC NF-e, and the switch to another electronic documents solution has no scope or date yet.

Likely causes (hypothesis)

  • An S/4HANA migration planned without the scope of electronic documents.
  • GRC customizations and integrations with no inventory.
  • No decision on when and how to switch.

What to check first

  1. Take an inventory of the document and event types issued by the GRC.
  2. List the customizations and integrations that depend on it.
  3. Confirm with SAP the maintenance date of your version.

It is a risk when

The switch is left to the last minute and coincides with the migration and with rule changes.

Path

Support

When a change or the end of the project leaves tax without an owner.

15Support

IT changes SAP and Tax finds out later

A patch, a customization or an upgrade goes into production, and Tax notices only when the document goes out different.

Likely causes (hypothesis)

  • No tax checkpoint in the change flow.
  • Tax regression testing that is missing or manual.
  • A transport approved with no view of the tax impact.

What to check first

  1. See whether the month's list of changes goes through Tax before production.
  2. Check whether there is a fixed set of test documents to repeat after each change.
  3. Find out who signs the tax test.

It is a risk when

The change reaches production and the difference shows up in a document already issued.

Path

16Support

After go-live, nobody looks after tax

The project is over, the team left, and tax tickets stay without an owner or come back with the same problem.

Likely causes (hypothesis)

  • Support with no tax scope.
  • Rule knowledge that left with the people who left.
  • A tax close with no routine that anyone follows.

What to check first

  1. See how many tickets of the last quarter are tax-related and how many come back.
  2. Check whether each rule has documentation and an owner.
  3. Find out who follows the tax close in the first cycles.

It is a risk when

The problem comes back at every close and the cost spreads across internal hours.

Path

GUEPARDO Tax and the NTT DATA channel. DFSpro is an Authorized Channel for GUEPARDO Tax, a product of NTT DATA: it sells the license, implements it and governs the rules in SAP. What is product behavior follows the product's support channel, and what is configuration of your system DFSpro handles.
Reference table

Symptom, where to look and who decides

One line per symptom, for quick reference, with the split between what belongs to the company and what belongs to the work in the system.

SymptomWhere to look firstWho decides
01. The assessment does not match the general ledgerSource accounting document, bookkeeping periods and manual adjustments of the assessment.Client: how to treat the adjustment and the gap. DFSpro: builds and proves the reconciliation in SAP.
02. The ICMS, PIS or Cofins credit is lostEntry invoice data, credit rule by operation and the asset record.Client: the credit thesis. DFSpro: sets up the credit and tests the result.
03. The tax is calculated wrong or the payment slip differs from the documentDetermination rule, item master data and rule validity.Client: what the correct rule is. DFSpro: adjusts the calculation and proves it by scenario.
04. The invoice was rejected or stays without authorizationReturn message, master data involved and recent change.Client: contingency and billing priority. DFSpro: finds the cause in SAP and tests the fix.
05. Incoming invoices are entered by handXML source, tolerance rule and event handling.Client: tolerances and who approves the mismatch. DFSpro: designs the flow and tests it in SAP.
06. The NFS-e goes out different in each cityList of cities, service mapping and withholding rule.Client: service classification and withholding. DFSpro: sets up each city and tests issuing.
07. The SPED Fiscal has an error or a mismatchPVA report, totals by record and Guide version.Client: whether to correct and what to report. DFSpro: adjusts the generation and validates the file.
08. Block K or the Block H inventory does not closeOrder record, balance by warehouse and inventory reason.Client: classification, layout and reason. DFSpro: maps the SAP record and reconciles the stock.
09. The tax master has wrong NCM and other dataMaterial master, filling rule and change history.Client: the classification of each item. DFSpro: designs the master validation and tests it.
10. Companies in the same group apply the same rule in different waysRules by company, group model and change history.Client: the group standard. DFSpro: models it, applies it and checks it in each company.
11. We do not know what SAP needs for CBS and IBSImpact inventory, SAP Notes and masters.Client: the reform thesis. DFSpro: maps the impact in SAP and tests what is configured.
12. Import or export does not talk to SAPForeign trade process, key between systems and cost allocation.Client: the tax treatment. DFSpro: designs the integration and checks the data end to end.
13. The GUEPARDO Tax release is behindVersion in use, customized rules and regression script.Client: the window and the risk. DFSpro: plans the update and runs the tax regression.
14. The GRC NF-e has no replacement planInventory of documents, customizations and integrations.Client: deadline and scope of the switch. DFSpro: takes inventory, migrates and tests the documents.
15. IT changes SAP and Tax finds out laterChange flow, test set and test sign-off.Client: who approves the change. DFSpro: designs the tax checkpoint and the regression test.
16. After go-live, nobody looks after taxTax tickets, rule documentation and close routine.Client: the support model. DFSpro: proposes it and runs it within the contracted scope.
From symptom to diagnosis

Five steps between seeing the problem and proving the fix

This is the order in which DFSpro handles any symptom on this page, from the first recorded case to the evidence that is kept.

  1. 01

    Record the symptom with a case

    A real document, file or screen, with the date of the first occurrence. Without a concrete case, the cause becomes a guess.

  2. 02

    Measure the size

    How many documents, periods or companies have the symptom. The size decides whether the treatment is a one-off or structural.

  3. 03

    Separate the cause into data, rule, process or change

    We reproduce the case in a test and see where each part of the result comes from. The hypothesis becomes a cause only after that proof.

  4. 04

    Prove the fix in a test environment

    We run the same scenarios before and after, and keep the evidence. Only then does the change go on to production.

  5. 05

    Leave the control in place

    We document the rule, the owner and the test that repeats at every change, so the symptom does not come back at the next close.

Unstable close

The same process takes one length of time one month and another the next, with no clear cause. Read about unstable close.

Multi-CNPJ governance

Each company in the group reads the same rule in its own way. Read about multi-CNPJ.

Divergence between Tax and IT

A change in SAP reaches production without passing through Tax. Read about Tax and IT.

If your case is not on the list, start with the SAP Tax Diagnostic. To see the services by topic, use the service catalog.

To read about your sector, see sectors. The technical terms are in the glossary.

Limit of our role

Who defines what, and who decides

Limit of our role

The causes on this page are hypotheses to prove in your system, not a diagnosis. Choosing the thesis, the classification and the tax treatment is up to your company. DFSpro enters the system: it designs, configures and proves what SAP does, on top of the decision the client made.

Sources

Who published the rule, and when it was read

Electronic tax documents

Ancillary obligations

Reform and consumption taxes

Confirm in your operation

The latest version of the NF-e MOC. The rule of each city and each state. The maintenance date of each SAP version. The causes described in the symptoms are hypotheses to prove, and the frequency of each symptom was not measured.

Frequently asked questions

Frequently asked questions about tax problems in SAP

01How long does it take to find the cause of a tax problem in SAP?+

We do not promise a deadline before seeing the system. The time depends on the size of the symptom and the evidence available: with a sample document and the date of the first occurrence, the path tends to be shorter.

02Do I need to know the name of the service before talking to DFSpro?+

No. This page exists for people who arrive with the symptom. Describe what happens, and the path to the service or to the SAP Tax Diagnostic comes out of the conversation.

03Does DFSpro say whether our tax thesis is right?+

No. The thesis is your company's choice, together with its advisers. Our side is the system: making SAP behave as the company decided, and showing with tests that it does.

04How do I tell whether the problem is in SAP, in the master data or in the tax rule?+

Reproduce the case in a test environment with a sample document and see where each part of the result comes from: rule, master data, manual adjustment or integration. This is the reading of the cause that the 16 situations on this page propose, always as a hypothesis to prove.

05Can we fix it in production and save time?+

We do not recommend it. A fix in production with no test and no record can swap one symptom for another. The safest path is to reproduce, fix in test, prove with the same scenarios and only then transport.

06When does a symptom become a risk for the company?+

When it repeats, when it grows in volume or when it has already reached an issued document, a paid slip or a file delivered to the tax authority. Framing the risk and talking to the tax authority are up to your company and its tax advisers.

07My system is still SAP ECC. Do these symptoms apply?+

The symptoms described hold as a hypothesis for both. What changes is the path: in the migration, several symptoms become scope items. See migration to S/4HANA and tax cutover on the pages listed in each situation.

08Is it worth hiring the AMS Fiscal for a symptom that always comes back?+

If the same symptom comes back at every close, it signals a lack of control, and the AMS Fiscal is one of the answers. The page on how to choose support compares the options, and the choice is the client's.

09What do I bring to the first conversation?+

A concrete example of the error (document, file or screen), the date of the first occurrence, what changed in SAP or in the rule at that time and who in the company decides the rule. No third-party data that does not need to leave the company.

10We already use GUEPARDO Tax. Can the symptom come from it?+

It can come from a rule, data, an integration or the version. DFSpro is an Authorized Channel for GUEPARDO Tax, a product of NTT DATA, and separates what is configuration from what is product behavior. If it is the product, the referral follows its support channel.

11Do I need to stop billing while you investigate?+

That is your company's decision, with its advisers. DFSpro helps measure the impact and prove what changes, but does not decide for you between billing, using contingency or waiting.

12What if my problem is not among the 16 situations?+

The list is not closed. The SAP Tax Diagnostic looks at the system to find where the symptom starts, even when it has no ready name.

Next steps

Bring your case to the conversation, with an example and the date of the first occurrence

With a sample document and what changed at the time, the conversation already separates what is master data, rule, process or change. The thesis stays with your company.

Bring my case to DFSproSAP Tax Diagnostic

Read also: tax governance program, assess readiness, methodology and GUEPARDO Tax.