Stabilization ends. Staying stable is continuous.
AMS Fiscal (Continuous Governance) is the permanent specialist follow-up contract that keeps the SAP tax environment stable after the initial stabilization.
Once the tax environment has been through stabilization, it does not stay stable on its own. Continuous governance is the discipline that prevents silent regression: not a project that ends, but a permanent specialist follow-up.
AMS Fiscal (Continuous Governance) is the permanent specialist follow-up that keeps the SAP tax environment stable after the initial stabilization. It runs in cycles on a cadence agreed in the contract, with a direct channel to a senior specialist. DFSpro configures and proves the result in the system; the tax decision belongs to the company.
Find the part of governance that answers your role
01Tax lead
Wants to know what is decided in each cycle and what proof comes with it.
Go to section02IT and Basis
Wants to know what changes in the system, in what order and with what record.
Go to section03Controllership and audit
Wants to know what evidence supports what was computed.
Go to section04Procurement and contracts
Wants to know what the advisory covers and where DFSpro's role ends.
Go to sectionQuick links
Long-term dependence on specialist knowledge of long duration
A stabilized tax environment depends on continuity of specialist knowledge. And that is exactly what an internal team, on its own, struggles to sustain over time. Team turnover, constant regulatory change and SAP version updates: each of these events requires a setup review that day-to-day routine rarely prioritizes.
This is not a failure in how the stabilization project was run.
It is the nature of any complex tax system: it needs ongoing specialist maintenance continuously so it does not regress, even after being technically correct on the day it was delivered.
Consequences of not acting
Without a layer of continuous governance, small changes (a legislation update, a one-off setup adjustment, an internal specialist leaving) pile up silently. The environment keeps working day to day, with no visible sign of trouble, until these small differences add up to a larger new tax incident.
Silent regression
Small, unreviewed changes pile up until they become a visible problem.
Dependence on internal heroes
Stability comes to depend on 1-2 people who "know how to fix it on the spot", with no documented process.
Recurrence
The same kind of incident that motivated the original stabilization project happens again.
Assessment criteria
Concrete signs that an already stabilized environment needs a permanent layer of specialist follow-up.
- Frequent tax law changes, with no internal response process defined.
- The internal specialist who mastered the setup left the company, or may leave soon.
- A new branch or CNPJ (the Brazilian company tax ID) is opening, requiring the setup to be replicated or adapted.
- A SAP or GUEPARDO Tax update is scheduled or recent.
- No formal routine of periodic audit since the end of stabilization.
The Continuous Governance layer
It is not reactive support. It is a fixed sequence that repeats on a defined cadence, and each step feeds the next, closing the cycle before a small deviation becomes an incident. The frequency is not daily: the goal is to keep the technical standard. Day-to-day operations stay with the company's internal team.
Periodic audit
A recurring, systematic review of the tax setup on a defined cadence, to find deviations before they become incidents.
Response to regulatory change
A technical impact analysis each time a change in tax legislation reaches the environment's setup, with a recommendation for the adjustment needed.
Setup review
A periodic check of existing rules and parameters, to verify that they still reflect the company's real operation.
Direct channel to a specialist
A defined point of contact with a senior specialist, for questions and decisions that come up between one periodic audit and the next.
When the environment starts to use an SAP artificial intelligence assistant, such as Joule, continuous governance gains one more question at each of these four points: what can this assistant suggest or run inside the tax flow, and with what trail is it recorded for later review. The technology changes who executes, never who answers for the decision. See SAP Joule in tax operations.
Each of the four steps exists to answer the same question: is the environment still right, or has it regressed without anyone noticing?
A governance cycle, from start to record
Continuous governance is not a meeting, it is a cycle that repeats. The frequency is agreed in the contract. What does not change is the order of the six steps and what each one leaves in writing.
Open the cycle
A list of what is expected in the period: rule changes, SAP notes, company events and the open items inherited from the previous cycle.
Measure the state
Reading the environment's health signals at the source, the system, with the date of the reading. A number with no origin does not count.
Assess the impact
For each expected change: which rule, which object and which obligation it touches, and what happens to the period already closed.
Decide and schedule
The company's tax lead decides the position and the date. DFSpro designs the adjustment and the test that will prove the result.
Apply and prove
Adjustment made in a test environment, regression of the affected obligations, transport through the company's routine and a check in production.
Close the cycle
A record of the changes with justification and approver, a reading of the health report with minutes, and the open items that pass to the next cycle.
Who decides, who executes and who approves
Governance fails when everyone thinks someone else is the owner. Each role has its own question, and the answer is recorded.
The company's tax lead
Decides the tax position, approves each rule change and sets the date. This is the person who answers to the tax authority for what was computed.
The company's IT and Basis
Keeps the environments aligned, transports what was approved and opens the technical window. Without this role, the approved adjustment does not reach production.
Controllership and audit
Checks the accounting effect, reconciles the computation with what was booked and uses the change record as proof before an auditor.
DFSpro specialist
Assesses the impact, designs and configures the adjustment, proves the system's behavior and reports the state of the environment. Recommends, does not decide the tax position.
What is included and what is on demand
Included in the cadence
- Periodic audit of tax setup.
- Impact assessment of regulatory change.
- Setup review on a defined cadence.
- Direct channel to a senior specialist.
Additional scope on demand
Situations outside the agreed periodic cadence (opening a new branch or CNPJ, a one-off project to adapt to a major regulatory change, or support for a SAP or GUEPARDO Tax update) are treated as additional scope, sized case by case, never included by default in the continuous governance cadence.
What you receive in each cycle
Audit frequency and incident response time are set by contract, according to the size and complexity of the environment.
Periodic tax health report
An overview of the state of the setup at each audit cycle, flagging any deviation found.
Record of changes applied
Each setup adjustment made is documented with the matching technical justification: nothing changes without a trace.
Incident response channel
A direct point of contact for questions and decisions that come up between one periodic audit and the next.
Eight signs that the environment is still right
These are signs the environment itself lets you check, without relying on impressions. Each company sets the acceptable limit for its own. The indicators of the service report are in how to choose tax support in SAP. These look at the configuration, not the queue.
Rules with an owner and a review
What to look at: How many main tax rules have a named owner and a date of last review within the cycle.
Decision it enables: Which rules go first in the audit.
Pending SAP notes
What to look at: Notes that apply to tax and are still without analysis or without being applied, by environment.
Decision it enables: Which fixes go into the next cycle.
Alignment between environments
What to look at: Whether the production setup is the same as the test environment's and whether production changed outside a transport order.
Decision it enables: Whether there is a direct adjustment to regularize.
Test coverage
What to look at: Obligations and document types that have an up-to-date regression script, and the date of the last test.
Decision it enables: Where an adjustment still cannot be proven.
Computation against bookkeeping
What to look at: The difference between what the system computed and what was delivered, period by period.
Decision it enables: Whether the cause is in the rule, the data or the process.
Recurring validator messages
What to look at: Warnings and rejections that come back from one month to the next in the obligation files.
Decision it enables: Which permanent fix replaces the workaround.
Rule validity
What to look at: Rules, benefits and rates whose validity has expired or is about to expire.
Decision it enables: Which dates go into the change calendar.
Dependence on a person
What to look at: Tax routines that only one person knows how to run or explain.
Decision it enables: Where to document and train before someone leaves.
Where changes come from and when they enter the environment
Five sources push change into the tax environment, each at its own pace. Between 26/03/2026 and 01/10/2026, the NF-e Portal published 17 technical notes in force, five of them on the same day, 01/10/2026. Without a single calendar, each one arrives as a surprise.
| Source | What goes in the calendar | Where to look |
|---|---|---|
| Electronic tax documents | Layout, validation rule and DANFE model (the printed invoice view), each with an effective date and a test date. | NF-e Portal, Technical Notes |
| Consumption tax reform | Stages of the CBS and IBS transition and the acts that regulate each one. | Complementary Law 214/2025, Planalto |
| Ancillary obligations | Annual deadline and layout change for ECD, ECF and the EFD bookkeeping. | Sped Portal |
| SAP fixes and version | Notes that apply to tax and the end of maintenance for the version in use. | Note Assistant, SAP Support Portal and S/4HANA maintenance strategy, SAP News |
| The company's own events | A new branch or CNPJ, a merger, a change of tax regime and the annual close. | The company's internal plan |
Each line of the calendar carries two dates: the effective date and the date of the safe window to apply it. The window criteria and the annual deadlines of the obligations are in GUEPARDO Tax release update.
What advisory means in practice
What the advisory does
- Reads the environment and says what has changed since the last reading.
- Explains the impact of each change in the language of whoever decides.
- Recommends the adjustment and prepares the test that proves it.
- Leaves the state of the rules documented for the next cycle.
What it does not do
- Does not run the daily routine, which stays with the company's team.
- Does not monitor the system all day.
- Does not decide the tax position.
- Does not replace the tax analyst or the IT team.
Each recommendation follows the same short format: what changed, what it affects and what DFSpro recommends. The decision comes afterward, on the company's side.
What stays on record for each change
Tax law requires that the mandatory tax books and the supporting documents of the entries be kept while the tax credit can still be collected, until the statute of limitations (art. 195, sole paragraph).
The supporting document shows the amount computed. The change record shows why the system calculated that amount on that date. When a rule changes, an auditor's question is which rule applied in each period. Six items answer it.
- What changed, with the rule before and after.
- The technical justification and the standard or decision that prompted it.
- Who at the company approved it and on what date.
- The transport order and the environment of each step.
- The regression test that proved the result, comparing expected with obtained.
- How to undo it, if needed.
How long to keep each item is the company's decision, with its own legal advice.
What supports this offer
The direct precedent for this offer is the 90-day grace model already validated in AMS Fiscal Stabilization, the same discipline of specialist follow-up, extended beyond the fixed term. Audit frequency and SLA go into the contract, adjusted to the size and complexity of the environment.
DFSpro proves the system. The tax decision belongs to the company.
Where the rule allows more than one reading, the company decides. DFSpro configures the reading chosen and proves the result in the system.
| Topic | DFSpro designs, configures and proves | The company decides |
|---|---|---|
| Interpretation of the rule | Assesses how the change affects the setup and leaves the impact in writing. | Which interpretation to apply, with its own legal and tax support. |
| Benefit or regime | Configures in the system what the company chooses. | Whether or not to adopt the benefit or the regime. |
| Date of the change | Prepares the adjustment and the test that proves it. | When to apply, within the window the company accepts. |
| Period already delivered | Shows the effect of the rule in the system, period by period. | What to do with what has already been declared. |
The difference between the two continuity offers
The source of truth for the distinction between AMS Fiscal Stabilization and AMS Fiscal Continuous Governance, so the scope of the two is not confused.
AMS Fiscal Stabilization
- Term: Fixed, 90 days
- Nature: Intense support after go-live, by the team that ran the project
- Who delivers: Project team in transition
- When to hire: After the S/4HANA migration or the GUEPARDO Tax implementation
AMS Fiscal Continuous Governance
- Term: Recurring, no fixed term
- Nature: Advisory: audit, response to regulatory change, periodic setup review, keeping the technical standard
- Who delivers: Senior specialist on a periodic (not daily) cadence
- When to hire: Environment already stable, but with no long-term layer of specialist maintenance
AMS Fiscal Advisory is not IT AMS
AMS Fiscal Advisory is the recurring service that keeps the tax setup of an SAP environment correct after the technical project ends. Generic IT AMS guarantees system availability; AMS Fiscal Advisory guarantees that the tax rule configured in SAP keeps reflecting the law and the company's real operation over time.
Each service measures its success by a different yardstick.
| Criterion | IT AMS | AMS Fiscal Advisory |
|---|---|---|
| When it is working | The system is up, the job ran, the ticket closed within the SLA. | The configured rule matches the law in force and the real operation. |
| Who answers and when | The ticket queue, within the contracted time. | A named owner and the date of the last recorded review. |
| How success is measured | Availability. | Correctness, not availability. |
An environment can be 100% available and, at the same time, computing with a rule that has been out of date for months. IT AMS does not detect this, because it is not its job. This is the gap that AMS Fiscal Advisory covers.
Service boundary: DFSpro builds, configures and tests the behavior of the system. The tax position is always decided by the client, with support from its own legal and tax teams.
To compare tax support proposals in SAP before hiring, see how to choose tax support in SAP.
Where this fits
Continuous governance is the destination of the journey, not the start:
Related content
AMS Fiscal, Stabilization Post-go-live
Support during the first full tax computation in production, right after go-live.
GUEPARDO Tax
Governance of the rules already configured: setup, documentation and owners.
Training in GUEPARDO Tax and Tax Reform
Technical training so the company's team can run the system on its own.
Blog articles about AMS Fiscal and SAP tax consulting
Questions to guide the decision
01Is this real support or just a monthly fee with nothing concrete delivered?+
In each cycle you receive a tax health report and the record of the changes applied, with the justification for each one. The delivery is documented and can be checked, instead of a charge with no visible return.
02Why not leave it to the internal team, now that the environment has stabilized?+
Keeping an environment stable takes specialist knowledge that is not lost over time. Staff turnover and frequent regulatory change make this hard for an internal team on its own, without dedicated follow-up.
03How is this different from AMS Fiscal Stabilization?+
Stabilization lasts a fixed 90 days and comes right after go-live, with the team that ran the project. Continuous Governance is advisory and recurring, with no end date, and reviews from time to time whether the environment is still correct. The full comparison is above.
04How does recurring contracting work for the Procurement team?+
The contract is recurring and has no end date, unlike Stabilization, which lasts 90 days. Audit frequency, scope and price adjustment rules are set in the contract, adjusted to the size and complexity of the environment.
05How often do the audits happen?+
Audits follow a frequency agreed in the contract, according to the size and complexity of the environment. They are not daily: the goal is to keep the technical standard, not to watch the operation every day.
06What exactly do I receive in each cycle?+
A periodic tax health report and a record of the changes applied with technical justification. The delivery is documented and verifiable, not a charge with no visible counterpart.
07Do I need to have been through Stabilization first?+
It is not a requirement, but it is the most natural path. Continuous Governance serves environments that have already stabilized; if the operation is still in the first cycles after the project, the right service is Stabilization.
08Does this replace my internal tax team?+
No. The service is specialist follow-up on the setup and does not take over the daily operation, which stays with the company's internal team.
09Who answers when a question comes up between audits?+
There is a direct channel to a senior specialist for questions and decisions that come up between one cycle and the next, with no ticket queue.
10How does the Tax Reform fit into continuous governance?+
Regulatory changes such as CBS andIBS enter as an impact assessment in the governance cadence, with a recommendation to adjust before the change exposes the operation to risk.
11What is the difference between AMS fiscal advisory and an SAP help desk?+
AMS fiscal advisory keeps context, finds recurrences and works on the root cause. A traditional help desk tends to handle isolated tickets without necessarily reducing tax instability.
12What is senior support like?+
The person who answers is an SAP tax specialist, who analyzes the case and advises on impact, likely cause, urgency and what to do next.
13Who approves a setup change, DFSpro or our team?+
The company. DFSpro assesses the impact, designs and proves the adjustment. The tax lead decides the position and the date, and the approval stays in the change record.
14Does continuous governance touch our production environment?+
Only through an approved adjustment, which first goes through a test environment, regression and transport through the company's routine, in the window it accepts. Without approval, nothing changes.
15How does governance follow SAP notes?+
SAP fixes arrive as notes, applied with SAP's own tool, Note Assistant. Governance identifies which notes affect tax, assesses the impact and brings the recommendation to the cycle. Applying them follows the company's change process.
16Do I need a test environment for this to work?+
Proving an adjustment requires a place where the test can be repeated without affecting the real computation. When the environment does not offer this, the risk goes on the cycle's agenda and the company decides how to proceed.
17What happens when the law changes in the middle of a cycle?+
The change goes into the calendar with its effective date and goes through the impact assessment. If it requires an adaptation project, it is treated as additional scope, sized case by case.
18What documents does the company keep at the end of each cycle?+
The tax health report, the change record with justification and approver, and the minutes of the reading. How long to keep each one is the company's decision, with its own legal advice.
Stabilizing was the technical part. Staying stable is governance.
Governance is not a project that ends: it is a continuous discipline. The next step is a conversation about the cadence that makes sense for your environment.