What your SAP is not showing you
A complex tax environment can look like it works while building up risk in practice. The SAP Tax Diagnostic is a structured assessment of 5 to 8 weeks, led by a senior team, that shows where the real risk is before any project proposal.
Serious risk rarely comes from a lack of system. It comes from layers of setup with no owner, made at different times, by different people, and never reviewed together. The Diagnostic makes those layers visible before a close, an audit or a regulatory change exposes them.
The SAP Tax Diagnostic is a structured assessment of 5 to 8 weeks, led by a senior team, that shows where the real risk is before any project proposal. It delivers a diagnostic report and a risk prioritization plan. Carrying out what is recommended is contracted separately.
Choose your entry point by your role
Four entry points, one per role, going straight to the block that answers your question.
01Tax and accounting
The symptoms of structural risk, the cost of not assessing and the difference between a technical test and a tax test.
Go to the section02IT and SAP integrator
What the diagnostic maps in the setup of GUEPARDO Tax integrated with SAP, the method and the scope.
Go to the section03Management and decision
What is delivered, what is out of scope and how to choose between the quick read and the diagnostic.
Go to the section04Self-assessment
The criteria to assess your situation and the 2-minute assessment.
Go to the sectionDirect links
How do I know whether my SAP operation has structural tax risk?
Three symptoms, alone or together, usually point to yes: a close that takes longer every month, a recurring gap between the tax assessment and the accounting that nobody explains precisely, and an audit question that the internal team cannot answer with confidence. The section below details why this happens and how the SAP Tax Diagnostic maps that gap.
The problem the diagnostic solves
Like any tax module integrated with SAP, GUEPARDO Tax depends on continuous setup. Tax rules change, the company grows, new CNPJs (company tax IDs) and branches join the operation, and each adjustment adds to the previous ones. Without a periodic review of the whole, the distance between what the system calculates and what the operation should assess grows in silence.
The failure rarely shows up in a visible way. It shows up as a close that takes longer every month, a recurring gap between the tax assessment and the accounting that nobody explains precisely, or an audit question that the internal team cannot answer with confidence. Alone, none of these symptoms proves serious risk. Added up and repeated, they show that the environment needs an outside assessment before the next event, a year-end close, a regulatory change or an audit, forces that assessment under pressure.
Why an outside view, and not one more internal review
People who run the environment every day grow familiar with their own exceptions. This is not a failure of the internal team: it is the natural bias of any team that lives with the same system for long enough. A structured outside diagnostic exists to bring a second senior look at what is already so automated that nobody questions it anymore.
That blind spot is what sets the cost of delaying the assessment.
What happens if this is not assessed
Without a structured assessment, the most likely consequences are not hypothetical: they are the pattern seen in SAP environments with GUEPARDO Tax that pile up setup without a consolidated review.
01
A tax close that gets slower and slower
Each undocumented exception requires repeated manual checking, month after month, using up time from the tax and IT teams.
02
Rework between Tax, IT and Accounting
Gaps between systems force recurring manual reconciliation, instead of the system delivering the correct data on the first run.
03
Exposure of the person directly responsible
Whoever signs the tax close is the one who answers, personally, for an error that began in a setup made years earlier, by someone else, with no clear record of why.
04
Risk of an infraction notice in an audit
A gap that went unnoticed internally for months can be exactly what a tax auditor finds first.
Why the Diagnostic comes first. The Diagnostic exists so the company sizes the real problem before defining scope, and not after. Scope and commercial terms are handled based on what it reveals, with no price range or cost comparison published.
Criteria to assess your situation
The questions below do not replace a conversation with DFSpro, but they help you assess, before any contact, whether your operation fits the profile the SAP Tax Diagnostic was designed to serve.
01
Does your team manually reconcile values between GUEPARDO Tax and SAP at every tax close?
02
Was there a change in tax scope in the last 12 months (new branch, new CNPJ, change of tax regime) without a formal reassessment of the existing setup?
03
Is the monthly tax close taking longer than it did one or two years ago, with no clear, documented technical cause?
04
Is there recurring rework between the Tax, IT and Accounting teams to reconcile assessment gaps?
05
If an auditor asked today why a specific setup rule exists the way it does, could someone on the team answer with confidence, or would the answer depend on "it has always been this way"?
06
Does the company run SAP (ECC or S/4HANA) as its central ERP, with GUEPARDO Tax active or under evaluation, large-scale invoicing and a tax operation across several states or several CNPJs?
Two yes answers are enough
Two or more yes answers show that the operation already has enough signal to justify a conversation.
If most answers are no, the low-risk path is to deepen your understanding first, with no need yet to commit to a full diagnostic.
Before the diagnostic, a quick read
The readiness assessment takes about 2 minutes and needs no sign-up to start. It shows whether it is worth going deeper, and it does not replace the diagnostic.
What the assessment asks
Ten objective questions about the tax operation: close duration, dependence on spreadsheets, recurring errors, work outside business hours, audit trail, IT tickets with a tax origin, the status of the S/4HANA migration (SAP's current ERP generation, its enterprise management system), leadership confidence, concentration of knowledge and management of legal change.
What it returns
A report on the scenario of your tax operation and what that pattern usually indicates, shown on screen. There is no comparison with other companies, and the email is only requested when the result is delivered. Answering takes a few minutes and can be done by anyone who knows the company's tax close, with no document to prepare.
From the quick read to the SAP Tax Diagnostic
The two have different roles and complete each other.
When to use each one
The assessment answers whether there are signs of structural risk, in about 2 minutes. The SAP Tax Diagnostic, structured in mapping, analysis and prioritization, measures where the points are and in what order to handle them. Anyone who already has two or more signs usually skips straight to the diagnostic.
Methodology
The SAP Tax Diagnostic is the first phase of DFSpro's method (see Our Methodology for the full view of the three phases: Diagnostic, Stabilization and Continuous Governance). It lasts 5 to 8 weeks and is led by a senior team, never by junior staff in training on the client's environment.
Mapping
Technical survey of the SAP environment and of the GUEPARDO Tax setup, together with the people who run it day to day (usually the Tax Director or Manager), without interrupting the current operation.
Analysis
Identification of gaps between the tax assessment and the accounting, and of setup points that piled up exceptions without review.
Prioritization
Classification of each risk found on an objective scale (Critical, High, Medium, Monitor), with a clear recommendation on what to handle first and why.
Working alongside the internal team and the SAP partner
The Diagnostic does not replace the knowledge of the internal team and does not conflict with an SAP implementation partner already hired. It is run with the internal team, and works on the specific scope of tax governance and GUEPARDO Tax, which is usually distinct from the scope of a generalist SAP partner. Hiring the Diagnostic does not mean changing vendors: it means adding a one-off specialist layer before any bigger decision.
What is inside and outside the scope
| Inside the scope | Outside the scope |
|---|---|
| Survey and mapping of the real setup of GUEPARDO Tax integrated with SAP (ECC or S/4HANA). | Carrying out what the Diagnostic recommends (the next phase of the method, Stabilization, contracted separately if the company decides to move forward). |
| Identification of gaps between the tax assessment and the accounting. | Replacement of the existing SAP implementation partner or of the internal tax team. |
| Prioritization of the risks found, with an explicit severity criterion. | Formal tax audit for legal or tax purposes (the Diagnostic assesses technical and setup risk, and does not replace a legal or tax opinion). |
| Recommendation of the order in which to handle the risks identified. | Any guarantee of a specific numerical result (reduction of X% of risk, guaranteed payback period). |
| Identification of points where an AI assistant (such as SAP Joule), if present in the environment, already touches a tax flow without formal control. | Setup, training or deployment of SAP Joule (a product and support of SAP itself), outside the scope of this diagnostic. See SAP Joule. |
This boundary exists so the page works as support material for whoever needs to design, internally, the hiring process (Procurement) or assess the contractual framework of the service (Legal) before approving the conversation.
What the diagnostic delivers
At the end of the 5 to 8 weeks, DFSpro delivers a concrete object, not a verbal impression of what was found.
Diagnostic report
Mapping of the tax environment and of the GUEPARDO Tax setup.
Risk prioritization plan
Each item classified as Critical, High, Medium or Monitor, with a recommendation on the order of handling.
Structured recommendation for the next step
Whether the case justifies Stabilization, a one-off fix, or a reassessment within a set period.
This report is the same type of auditable document described in Our Methodology: the client can review it at any time, and it is the object the buyer champion can forward internally to justify the next decision to a CFO, CIO or risk committee.
Proof of method
What DFSpro can state today, with real backing
- The SAP Tax Diagnostic is led by a senior team, not by assigning junior profiles.
- The methodology follows the three steps described above (Mapping, Analysis, Prioritization), lasting 5 to 8 weeks.
- The risk classification criterion (Critical, High, Medium, Monitor) is the same one used consistently in the Stabilization phase and in Continuous Governance, not a methodology isolated for this service alone.
The method and the risk classification criterion are documented and applied consistently across the three phases of the work.
Where this leads on the journey
The SAP Tax Diagnostic is Stage 2 of DFSpro's portfolio journey: the point where a vague suspicion of risk turns into a concrete prioritization plan. What happens next depends on what the Diagnostic finds.
If the report identifies a concentrated risk that requires technical intervention (a pending migration, a structural setup fix), the natural next step is a Stabilization project. If the environment is already in a stable condition, the Diagnostic serves as the base to go straight into the Continuous Governance model, with permanent monitoring instead of a new project.
See the full journey, with the six stages and the decision criteria of each
A technical test is not a tax test
A technical test confirms that the transaction runs without error. A tax test confirms that the assessed value is correct for the real scenario of the operation. These are different questions, and passing the first says nothing about the second: an environment can pass the whole technical battery and reveal the gap only at the first close.
Checklist for a tax audit in SAP
Items that can be checked, each one an objective verification, not a benefit:
- Is there a list of the configured tax rules, with a named owner for each rule?
- Does each rule have the date of its last review and its legal basis recorded?
- Do the Z rules in use have a documented purpose and an identified approver?
- Does tax determination reflect the real operation, including exceptions by state, CFOP and material type?
- Do the tax master records for material, customer and vendor support the assessment, or is incorrect master data being processed efficiently?
- Is there a structured check before transmitting a filing, and not only after the tax authority's screening result comes back?
- Is there a reconciliation between what the tax area assessed and what the accounting recorded, in the same period?
- Are the SPED records (for example C100, C170, C190 and Block K) consistent with the movements of the modules that feed them?
- Does a change in tax setup go through a test environment before going to production?
Each "no" on this list is a point where the system may be assessing wrongly without signaling anything. The diagnostic maps those points and prioritizes them by real exposure, without deciding the tax position, which belongs to the client.
Where this fits
The diagnostic is the starting point. What comes after it depends on what it finds:
AMS Fiscal Advisory: post-go-live stabilization
When the environment has just gone into production and needs assisted follow-up.
AMS Fiscal Advisory: continuous governance
When the environment is already stable and the risk is silent regression over time.
Cases of tax governance in SAP
The type of problem that earlier diagnostics found in practice.
Questions to take to the internal conversation
01Who exactly leads the Diagnostic?+
DFSpro's senior team, together with the people who run the tax environment internally. No junior profile in training is assigned as the main technical lead of this phase.
02What happens if the Diagnostic finds a risk outside the expected scope?+
The risk is recorded and classified the same way as any other prioritized item (Critical, High, Medium, Monitor), with a recommendation on how to handle it, even if the indicated answer is not a new project with DFSpro.
03Does the Diagnostic interrupt the current tax operation?+
That is not how the service is designed: the survey is done alongside the normal operation, together with the internal team, without requiring a pause in the tax close under way.
04Is there any commitment beyond the Diagnostic itself when hiring this step?+
No. The Diagnostic is contracted as a standalone deliverable, with its own scope and timeline. The decision to move on to a Stabilization project is made afterwards, based on what the report shows, not before.
05How does governance of the environment continue after the Diagnostic ends?+
That depends on what the report recommends: it can be a reassessment within a set period, a Stabilization project for whatever is classified as Critical or High, or direct entry into the Continuous Governance model if the environment is already stable (see Portfolio for the full journey).
06How long does the Diagnostic last, in practice?+
From 5 to 8 weeks, led by a senior team. The exact time depends on the complexity of the environment (number of CNPJs, SAP version, scope of filings) and is confirmed at the start.
07Does the Diagnostic come with a built-in project proposal?+
No. It delivers a prioritized risk map, not a sales proposal. Any project that follows is sized from what the Diagnostic reveals, and the decision to go ahead is yours.
08Do I need to prepare a lot before starting?+
You do not need to prepare a dossier. The work starts from the real environment (setup, close history, filings), and the senior team leads the collection with your team, without requiring an internal pre-project.
09Can the result be presented internally to the board?+
Yes. The deliverable is an objective document with the risks prioritized by severity, in a format suited to support an investment decision before executives and committees.
10Does it work for an ECC environment or only S/4HANA?+
Both. The Diagnostic assesses the real tax setup, whether it is ECC or S/4HANA, and it even helps size the tax risk before a possible migration.
Related content
AMS Fiscal, Post-go-live Stabilization
Follow-up of the first complete tax cycle in production, right after a go-live.
ECC migration → S/4HANA
Tax governance in the version migration, not just the infrastructure.
Two paths, neither committing you to a big project today
If the operation already recognizes two or more signs from the self-assessment criteria list, the natural next step is to request the Diagnostic: a qualified technical form, not a generic sales call. If you still doubt whether the problem already justifies that conversation, the lowest-commitment path is to understand your own scenario better before deciding.