How to choose the best SAP tax consultancy, and the best one for the Tax Reform
There is no best consultancy in the abstract. There is the one that proves, in your environment and before you sign, what it promises. This guide gathers criteria you can check yourself, with no ranking and no vendor names.
The tax position stays your company's choice, never the vendor's. What you buy from a consultancy is design, configuration and proof of how the system behaves.
Start with the role you hold in the decision
Four doors to the same decision. The person who signs, the person who uses, the person who runs and the person who contracts each ask different questions.
01Executive board and CFO
Why the choice often goes wrong, what is at stake in the reform and what proof to ask for before signing.
See the role section02Tax team
The twelve criteria, the ten reform criteria and the interview test on how the law works.
See the role section03IT and SAP
How the consultancy fits with the integrator, with the tax product and with the S/4HANA migration.
See the role section04Procurement and contracting
Proof on paper, clauses, a selection plan and 25 questions for the vendor.
See the role sectionShortcuts on this page
Why does the right consultancy on paper fail in the project?
The right consultancy on paper fails in the project when it is chosen by its presentation and not judged by what it can prove: at the close, when a rule changes and in an audit of the environment. The choice has to swap promises for documents.
The talk is judged, not the evidence
Two proposals list the same services. What sets them apart only shows up when a rule changes, an auditor asks a question or the environment is updated.
The cost arrives after signing
Close rework, layout changes and the reopening of a misread rule are not in the proposal. They arrive once the environment is in production.
The calendar does not negotiate
The year 2026 already has test rates, and CBS starts in 2027. The consultancy you choose now is the one that will design and test the new rule.
The tax decision moves without notice
Without a written boundary, the company starts to accept the position the consultant chose. The decision belongs to the company and must be recorded as such.
Which types of consultancy serve SAP tax work?
SAP integrator
Masters the platform, the architecture and the infrastructure. Often treats tax as one module among many. Check who on the team answers for tax determination and for proof of the calculation.
Specialist consultancy in tax on SAP
Brings together the tax rule and the knowledge of where it lives in the system. Check the depth in electronic documents, ancillary obligations and the reform, and the testing method.
Tax consultancy with no SAP focus
Knows the law and the legal position. Usually lacks the path to configuration. Good for deciding; needs a technical partner to implement and prove it in the system.
Consultancy tied to a tax product
Knows a tax layer integrated with the ERP in depth. Check whether the advice stays neutral when your case does not call for the product.
In-house team and independent contractors
Know the company and answer fast. Check dependence on one person, documentation of what was done and coverage during vacations, departures or role changes.
A badly framed question: who is the best consultancy?
Ranking and badge
- Measures the vendor, not your project.
- Rarely shows the criteria and weights used.
- Rewards what is easy to count: size, years in the market, number of clients.
- Says nothing about your legacy of customization, your establishments or your close calendar.
Verifiable criterion
- Measures what the vendor delivers in your scenario.
- You write the criteria and weights before looking at proposals.
- Rewards what can be checked: a sample document, a test, an acceptance form.
- Changes from company to company, and that is what makes it useful.
There is no vendor list and no score for anyone here. The choice is editorial, and the reason is simple: a list would only help the reader if its criteria matched those of your project, and nobody knows that before seeing your environment.
DFSpro appears further on as one option that meets the criteria, with facts the company itself can stand behind. Read that section with the same yardstick you use for any other vendor.
Define what you are buying
Implementation or rollout
Delivering tax for a new SAP project or a new establishment. Ask who designs tax determination, who tests and who signs the tax scenario acceptance before go-live.
Tax calculation fix
Making SAP calculate what the tax owner decided, when today it does not. Here the central criterion is reproducing the error: without a reproduced case there is no cause, and without a cause the fix is a bet.
Migration to S/4HANA
Moving rules, ledgers and accounting entries to the new platform. The question is how tax enters the cutover plan and what proof the vendor leaves that the calculation stayed the same.
Reform readiness
Designing, configuring and testing how SAP reacts to the new taxes. Ask for the test plan before the configuration proposal, because the test shows what the vendor understood of the rule.
Support after go-live
Who looks after the tax environment the following month. This case has its own criteria, already detailed in how to choose SAP tax support, and they are not repeated here.
Training your team
Training the people who operate it. The criterion is material produced about your environment, not a generic course: the team must leave knowing where each rule lives in your system.
Twelve criteria you can verify
| Criterion | How to verify | Warning sign |
|---|---|---|
| 1. Tax and SAP on the same team | Ask for the résumé of the person who would design the rule and ask where in SAP it would sit. The answer must name a configuration object, not only the name of the tax. | The tax person explains the law and promises the technical team will solve it later. The handoff between two departments is where the error is born. |
| 2. Written method | Ask for the method document: phases, what goes into each and what must be ready to leave it. Read a sample deliverable. | A method described only in a presentation, with no sample of a document produced. |
| 3. Reproduce before you fix | Ask how a calculation error is handled: where it is reproduced, with what document and who confirms the expected value. | The fix starts with a configuration change, with no reproduced case and no expected value. |
| 4. Evidence for each delivery | Ask for a sample of evidence: expected value next to the value obtained, with document, date and owner. | Evidence is an email saying it was tested. |
| 5. Repeatable test | Check that the scenarios are kept and can run again when the rule, the version or the legislation changes. | A test done once, in a personal spreadsheet, that leaves with the consultant. |
| 6. Knowledge handover | Agree where the documentation lives, who maintains it and how your team gets access. Require that each rule has an owner inside the company. | Documentation is handed over at the end and nobody updates it afterward. |
| 7. Clarity on who decides | Ask what the vendor does when an interpretation is in doubt. The right answer returns the decision to the tax owner and records the alternative. | The vendor picks the legal position on its own, or promises tax savings as a result of the service. |
| 8. Primary source cited | Ask the proposal to cite the rule, the article and the reading date of each legal premise. Check one of them yourself. | Legal premises with no rule cited, or based on another vendor's text. |
| 9. Relationship with the integrator | Ask where its work ends and the integrator's begins, and how the two teams share the test environment. | Scope with no clear boundary, which causes a dispute at the first incident. |
| 10. Product neutrality | Ask what the vendor recommends when your case does not call for the product it sells. See the section on the tax product. | Every problem finds its solution in the same product. |
| 11. Proposal with a closed scope | Check for named deliverables, an acceptance criterion and what stays out. The estimate must explain what drives it. | Open scope, described with vague verbs such as support and follow. |
| 12. None of your data outside the contract | Ask how the consultancy handles tax data, production access and credentials, and what happens to all of it at the end. | Broad, permanent access to production, with no log and no deadline. |
Weights, scores and a conversation for each criterion
- Choose the weights before reading proposals. Give more weight to what your project fears most. A company that has just moved to S/4HANA weighs the repeatable test. One that struggles with a slow close weighs reproduction and cause.
- Score each criterion from 0 to 3. Zero when there was no answer, one when there was only a statement, two when there was a sample document and three when the document was for the kind of project you have.
- Ask everyone for the same material. A sample deliverable, a test evidence and the acceptance template. Comparing proposals with different materials measures sales skill.
- Hold a separate technical meeting. Bring a real scenario, anonymized if you prefer, and ask the vendor to show how it would handle it. Watch who speaks and who asks.
- Record the decision for each criterion. When the choice is challenged internally, the record shows it came from criteria defined before the proposals.
Note on numbers
The 0 to 3 scoring and the idea of weights are our own working method, not a procurement standard or a recommendation from any body. Adapt it to your company's purchasing policy.
Questions by role, for the same table
Executive board and CFO
What evidence will I get at the end of each phase? Who answers if the calculation differs after go-live? What happens to the documentation if the contract ends? How does the vendor report a risk that is not its own?
Tax team
Who approves the correct result of each scenario? How are exceptions by state and by city handled? What record is left of an interpretation decision of mine? How is the rule reviewed when the law changes?
IT and SAP
Where do the tests live? How does a change reach production and how is it rolled back? Which custom objects does the vendor propose and why not use the standard? How does the integrator's team take part?
Procurement and legal
Are scope, acceptance and deliverables named? How are confidentiality and environment access handled? What exit clauses exist? How are scope changes recorded?
Controllership and accounting
Does the vendor know the reconciliation between tax calculation and the ledger? How are differences classified? Which report shows the tax and accounting close side by side?
How do the types of consultancy compare on twelve criteria
| Type of vendor | Usually shows | What to check before hiring |
|---|---|---|
| SAP integrator | Mastery of the platform, the architecture and the infrastructure, and experience in large projects. | Who answers for tax determination and for proof of the calculation, and how tax testing fits into the overall schedule. |
| Tax specialist on SAP | The tax rule and where each rule sits in the system, with proof by scenario. | Depth in electronic documents, obligations and the reform, the written method and neutrality toward the product. |
| Tax firm with no SAP focus | Reading of the rule, opinions and support for the legal position. | Who takes the decision through to configuration and proves it in the system, because the consultancy does not do that part. |
| Tied to a tax product | Deep knowledge of a tax layer integrated with the ERP and of its updates. | What it recommends when your case does not call for the product, and how it proves the calculation after each release. |
| In-house team or contractors | Knowledge of the business, fast answers and low coordination cost. | Dependence on one person, documentation of what was done and coverage during vacations, departures or role changes. |
How to read the comparison
It is our reading, by type of vendor, and not a measurement. Inside each type there are huge differences, which is why the twelve criteria in the previous section apply to the specific vendor.
Five pieces of proof that end the discussion
Sample tax specification
Shows how the vendor turns the client's decision into a system rule. Check whether the document cites the legal rule, the configuration object and the matching test scenario.
Test scenario matrix
Shows coverage: operations, states, regimes, exceptions and documents. Check whether there is an expected value calculated independently and whether edge cases appear.
Root cause report
Shows how an error was explained and fixed, with the data hidden. Check whether the cause is shown with evidence or only described in words.
Acceptance form
Shows what the vendor agrees to be measured on. Check whether the criterion is verifiable and whether the tax owner signs.
Knowledge handover plan
Shows how knowledge leaves the project and reaches your team. Check whether each rule has an internal owner and a documentation location the company controls.
Ten signs that justify more questions
- The proposal promises to reduce tax, instead of proving that the system follows the rule the client decided.
- There is no name of who does the work, only the name of the company.
- The vendor will not run a small pilot before the full project.
- The answer to every technical question is that it depends, without saying on what.
- The whole scope is described by modules and none by deliverable.
- The deadline does not change when the scope changes.
- The proposal ignores your company's close and obligations calendar.
- There is no mention of the legislation that will apply during the project period.
- It asks for permanent production access for work that is one-off.
- It disqualifies the current integrator without having seen the environment.
A small pilot is worth more than ten presentations
If the project is large, ask each finalist for a short, closed scope: one real tax scenario, with a defined deliverable. It can be the specification and test of a single operation, or the root cause analysis of a known error.
The pilot does not need to be long. It needs to be enough for you to see the vendor working with your data, your tax owner and your test environment. How it asks, records and proves says more than the commercial proposal.
What to choose
A case where you already know the answer, so you can measure. Avoid the most urgent case: haste distorts the assessment.
What to agree
Deliverable, short deadline, who on your side validates and what happens to the material if the contract does not go ahead.
What to watch
Questions asked, a record of what was decided, an expected value calculated independently and clarity in saying I do not know.
What the law has already set and the consultancy must master
A consultancy's legal premise is checked at the primary source. The information below was read in the text of Constitutional Amendment 132 and Complementary Law 214, at the Planalto website, on 25/10/2026, and is listed under Sources.
| Period | What the text says | Source |
|---|---|---|
| 2026 | IBS at the state rate of 0.1% and CBS at 0.9%, with the amount paid offset against PIS and Cofins in the same period. Without enough debits, offset against another federal tax or reimbursement within 60 days. | EC 132, art. 125 of the ADCT; LC 214, arts. 343, 346 and 348 |
| 2027 and 2028 | CBS starts to be charged and the PIS and Cofins contributions end. IBS is collected at 0.05% by the states and 0.05% by the cities. | EC 132, art. 126 of the ADCT; LC 214, arts. 344, 347 and 542 |
| 2029 to 2032 | ICMS and ISS charged in decreasing proportion of their rates: 9/10, 8/10, 7/10 and 6/10. The IBS reference rates come from a resolution of the Federal Senate. | EC 132, art. 128 of the ADCT; LC 214, arts. 349 and 361 |
| 2033 | Repeal, from January 1, of LC 87/1996 and LC 116/2003, among other rules. | LC 214, art. 543 |
What the table does not settle
It shows the calendar of rates and phase-outs. Regulations, acts of the Steering Committee and document layouts change over time, and a serious consultancy says which version it read and on what date.
What no consultancy should promise on the reform
Do not promise
- The final effective rate before it is set by Senate resolution.
- Tax savings as a result of the project.
- Full readiness while regulations and layouts are still changing.
- A final interpretation of a topic with no published rule.
May promise
- Design, configuration and testing of what the client decided.
- A record of the version of the rule used and the reading date.
- Scenarios that run again at every change.
- A clear warning when the rule depends on an act not yet published.
Ten criteria for choosing a consultancy for the reform
| Criterion | Check question | Answer that satisfies |
|---|---|---|
| Separates law from regulation | Of what you told me, what is in the law and what depends on regulation? | A list with article and reading date for the first column, and a statement of what is not yet published for the second. |
| Tests in 2026 | How do we run the test-rate year in a test environment? | A plan with operation scenarios, issued document and simulated calculation, with the expected value calculated outside the system. |
| Understands coexistence | How does SAP treat old and new taxes in the same document? | An explanation of how ICMS, ISS, PIS and Cofins coexist with the new taxes, with the rule by period. |
| Masters electronic documents | Which layout changes affect issuing and receiving, and how are they validated? | A table of the old layout next to the new one, affected fields listed and a test run in the test system. |
| Handles master data | Which master data changes, and what do you do with the legacy? | An inventory of customer, supplier and material fields that enter the new rule, with a cleanup plan owned by the client. |
| Plans split payment | Where does your design touch settlement and reconciliation? | A map of the flow between tax document and payment, and of the points where SAP must record the split. |
| Looks after credits | How does the system separate IBS credit from CBS credit? | A design that keeps credits separate, with no cross offset, as the text of the law says. |
| Accepts review | What happens when the regulation changes what you configured? | A review clause with a reopening criterion, and a repeatable test for each change. |
| Respects the boundary | Who decides the classification and treatment of each item? | The client. The consultancy presents alternatives and records the choice. |
| Prepares the team | What can your team do at the end of the work? | Training on the client's environment, with a checklist the team runs on its own. |
Eight questions to measure whether the consultancy understands the mechanics
On the calculation base
Ask what the calculation base for IBS and CBS is under the law and which components of the transaction value are included. A good answer cites art. 12 of LC 214 and the full amount charged by the supplier.
On credits
Ask how the credit is taken. A good answer recalls the regular-regime recognition, the separation of IBS and CBS and the ban on cross offset, with a reference to art. 47.
On split payment
Ask when the split happens. A good answer points to the financial settlement of the transaction and the link between the electronic tax document and the payment, arts. 31 and 34.
On 2026
Ask what is offset in the test year. A good answer describes the offset against PIS and Cofins and the possibility of reimbursement, and does not promise any extra payment.
On coexistence
Ask until when ICMS and ISS coexist with the new taxes. A good answer cites the proportional reduction from 2029 to 2032 and the repeal from 2033.
On interpretation doubts
Ask what happens when two readings of the rule are possible. A good answer returns the decision to the client and records the alternative not chosen.
On testing
Ask how it will be proven that SAP does what was designed. A good answer describes scenarios, an independent expected value and a rerun at every change.
On what does not exist yet
Ask what the vendor does not know today. Whoever answers precisely about what depends on regulation deserves more trust than whoever answers everything.
The one who sells the product can be the one who says when it does not fit
Some consultancies are tied to a tax product; others work only on the native Brazil localization. Neither model is wrong. What changes is how much you need to test the neutrality of the advice.
Ask, with an open question, in which scenario the vendor would say its product is not needed. An answer that describes that scenario precisely is a good sign. An answer that cannot describe it calls for more conversation.
If you use a tax product
Check who does the release update, how the calculation is proven after it and who maintains the setup between releases.
If you do not
Check whether the consultancy masters the Brazil localization, the calculation engine you have and the document and obligation layers SAP offers.
If you are deciding
Ask for a written comparison by criterion, with what each path demands in upkeep, and who makes the choice inside the company.
How DFSpro measures up to the yardstick
Our place on this list is that of a tax specialist, inside SAP and GUEPARDO Tax. The table shows what we state and what you can ask to check, using the yardstick we suggest for any vendor.
| Criterion | What DFSpro states | What you can ask for |
|---|---|---|
| Origin | Founded in 2018, in Curitiba. Part of the team came from FH, which created GUEPARDO Tax and is now NTT DATA Business Solutions. | A technical conversation with the person who would design your work. |
| Partnership | SAP partner and Authorized Channel of NTT DATA, which holds GUEPARDO Tax. | The description of the scope the authorized channel covers. |
| Tax product | Implements and governs GUEPARDO Tax, and serves SAP ECC and S/4HANA environments with or without the product. | A comparison by criterion between the paths for your case. |
| Scope | Also implements SAP, migrates and does rollout, beyond the tax work. The table of parameters by city for NFS-e is part of what we deliver. | The list of named deliverables for your project. |
| Support | AMS Fiscal in phases, each with an exit criterion. | The method text and a sample deliverable. |
| Boundary | The tax position is the client's. DFSpro designs the rule in the system, configures it and shows the result. | The acceptance template signed by the tax owner. |
For the support scope after go-live, read how to choose tax support. For the general scope, see the page on SAP tax consulting.
Which consultancy suits each type of SAPcompany?
Group with several CNPJs
Weigh standardization across establishments and the tax rollout. Ask how the group standard is recorded and how each new unit joins.
Industry with ICMS-ST and IPI
Weigh error reproduction and the scenario matrix by state and by NCM. Require an expected value calculated outside the system.
Services across many cities
Weigh the handling of NFS-e and withholdings by city and the table of parameters by city, which DFSpro delivers.
Foreign trade operation
Weigh knowledge of imports, exports and special regimes, and the link to tax calculation.
Company that already has a tax product
Weigh the release update, the proof of the calculation after it and the governance of the setup.
Company without SAP, about to implement
We serve this case when the buyer comes to DFSpro to implement SAP. Weigh the ability to deliver tax together with the implementation.
What to ask the consultancy in the migration from ECC to S/4HANA?
Cutover plan
Ask where tax appears in the schedule and who signs the tax acceptance before go-live. See the detail in tax in the migration to S/4HANA.
Business partner master data
SAP treats the Business Partner as the master object in S/4HANA and requires converting customers and suppliers. Ask how the consultancy handles the partner's tax data in the conversion.
Transition path
SAP describes system conversion, new implementation and selective data transition. Ask for an analysis of the effect of each path on ledgers, balances and tax history.
Clean core
Ask how the consultancy avoids unnecessary tax customization and what criterion it uses to choose between standard, extension and custom development.
The SAP S/4HANA tax consulting page covers this topic on its own.
Clauses that turn criteria into obligations
Scope and deliverables
Each deliverable with a name, format and acceptance criterion. What was not named is out, and that must be written down.
Signed acceptance
The tax owner signs the acceptance of the scenario. Without the signature of the decision owner, the evidence closes nothing.
Ownership of the documentation
Documents, tests and specifications stay in a place the company controls, with a permanent right of use.
Access and data
Who accesses what, with what log and for how long. Tax data handled under the company's data protection policy.
Review for regulatory change
A criterion to reopen the work when the rule or the layout changes, with what is included and what is new scope.
Exit
Deadline and way to return access, hand over the living record and transfer knowledge at the end.
Selection in four weeks, from the briefing to the decision
- Week 1: scope and criteria. Define what you are buying, choose the twelve criteria and the weights, and prepare a real scenario for the technical meeting.
- Week 2: request for material. Send the same plan to every candidate and ask for a sample specification, a scenario matrix, a root cause report and an acceptance template.
- Week 3: technical meeting and pilot. Run the meeting with the scenario and, if the project is large, the short pilot. Record questions and answers by criterion.
- Week 4: scoring and decision. Score with the weights set in the first week, record the decision and negotiate the clauses that turn criteria into obligations.
Six costly mistakes that are avoidable
- Buying by name: choosing by reputation without checking who will actually do the work. The reputation belongs to the company, the work is done by people.
- Mixing support and project: using the same criterion for who implements and who supports, when the roles call for different proof.
- Choosing only by product: picking the vendor from the product, and not the product from the problem.
- Skipping the pilot: signing a large project without seeing how the vendor works with your data.
- Ignoring the integrator: hiring the tax layer without aligning with whoever looks after the platform, and finding the dispute at the first incident.
- Delegating the tax decision: handing the consultancy the choice of legal position, which belongs to the company and must be recorded as such.
Which doubts stall the decision on the consultancy?
We already have an integrator. Do we need another vendor?
It depends on who covers the tax layer. If nobody answers for proof of the calculation, a front is missing, and the boundary with the integrator must be written down.
A smaller or a larger consultancy?
Size does not answer it. Ask who does the work, with what method and how the knowledge stays in the company. At any size, the work is done by named people.
Fixed or on demand?
It depends on whether the work has a defined deliverable. A project with a closed scope calls for acceptance; a routine calls for a periodic report and a priority criterion.
Is it worth waiting for the regulation?
The year 2026 already has test rules and rates. What depends on regulation can be designed with a review built into the contract, and the repeatable test lowers the cost of change.
Which questions to ask an SAP tax consultancy before hiring?
| Topic | Questions to bring to the meeting |
|---|---|
| Method and proof | What is the written method? How is an error reproduced? What evidence is left for each delivery? Where do the tests live? Who confirms the expected value? |
| Team | Who does the work, with what experience in my kind of environment? Is there a named substitute? Do tax and SAP people work together? How is the handoff between phases? |
| Legislation | Which rules support the scope, with article and reading date? How does a change in the rules reach the project? What was left out of what was read? |
| Boundary and decision | Who decides the legal position? How is it recorded? Where does your work end and the integrator's begin? What do you not do? |
| Contract and exit | What are the deliverables and the acceptance? Who owns the documentation? How are access and data handled? How does the close-out work? |
How to talk to a client reference of the consultancy
A client reference is the most cited and least explored material in a selection. The fifteen-minute talk that usually happens repeats what the vendor already said. Better questions move the reference from praise to fact.
Who from the vendor worked on your project and stayed to the end?
Shows whether the team presented in the sale is the one that does the work. An informative answer gives names, roles and who left and when.
What did not work at the start?
Shows how the vendor deals with error, not only with success. An informative answer gives a concrete problem and what changed in the method afterward.
How was the first close after the delivery?
Shows whether the evidence delivered held up in the routine. An informative answer gives differences found and who explained them.
What was documented and where?
Shows whether the knowledge stayed with the company. An informative answer gives a location controlled by the client and the date of the last update.
Would you hire them again for the same kind of work?
Shows the limit of satisfaction. An answer with a specific reservation is worth more than one with no reservation.
Ask for two references from different profiles, and not only the one most comfortable for the vendor. Also ask whether that client's scenario looks like yours: a group with several establishments, an industry, services or a company in migration.
Governance after signing: what to track week by week
A good part of the risk in a tax contract is born after signing, when the company's attention goes back to the month-end close. A simple tracking rhythm keeps the evidence coming and avoids surprises at delivery.
- A short, fixed meeting. Half an hour a week, with a repeated agenda: what was delivered, what is blocked and who decides. The decision maker is present.
- Decision log. Each choice by the tax owner becomes a line with date, alternatives considered and source. It is the document that answers the auditor later.
- Risk log. A list the vendor also feeds, with an owner and a date. A risk that is not the vendor's, but that it can see, must go in there.
- Milestone with evidence. Each milestone in the plan ends with a document, not a statement. A milestone with no document stays open.
The most reliable indicator of project health is the share of decisions pending on the client side. When it grows, the schedule slips without the vendor having made a mistake, and it is worth talking about it early.
The first thirty days: what the first delivery should show
The first delivery is the best test of fit between what was sold and what will be done. It is worth defining in the contract what it must contain, instead of accepting whatever is presented.
- An initial inventory of the environment, with stated limits of what was and was not surveyed.
- The list of open questions for the tax owner, with an agreed deadline for answers.
- A real case reproduced end to end, showing the method at work on your data.
- The test plan for the main scenarios, with the expected value still to be approved.
- A proposal for organizing the documentation, with the chosen location and who maintains it.
- The log of risks seen in the first month, including those that depend on the company.
A delivery that brings only a schedule and a company presentation is not a first delivery. It is a continuation of the sale, and acceptance should wait for the first working document.
What your company needs in place for the consultancy to pay off
The best consultancy cannot make up for the absence of the tax owner. Projects stall more often on the client's decision than on the vendor's execution, and whoever hires helps themselves by preparing the house before starting.
A decision owner
One person with authority to approve the expected result and time set aside in the calendar. Approval done in a batch, on the last day, loses quality.
Agreed access
Test environment, named users and transport history available at the start, not negotiated every week.
Source material
Real documents, known rules and the list of exceptions the team carries in their heads. What exists only in memory must go on paper.
If the tax owner has no time, that is the point to resolve before contracting, not the scope. An honest vendor warns that the schedule depends on that presence.
Exit plan: how to know the knowledge stays with the company
Nobody signs a contract thinking of ending it, but every vendor relationship ends, by term, by a change of strategy or by a change of team. A company with no exit plan learns what it lost when it needs an explanation that only the vendor knew how to give.
- Documentation in a company location. Specifications, tests and reports stay in a repository controlled by the client, with read access for whoever the tax owner names.
- A handover session for each delivery. At the end of each delivery, a recorded meeting where someone from the company explains the solution in their own words.
- Substitute test. A person who did not take part in the project tries to reproduce a scenario with the documentation available. What blocks them is what is missing from the documentation.
- List of dependencies. What only the vendor knows how to do, why, and what the company would need to take it over. The list shows the real dependence.
Rules and documents read for this page
The changes made by Complementary Law 227 of 2026 appear in the compiled text of LC 214 and were not analyzed one by one. The full reading record is in the sources file for this page.
Frequently asked questions about SAP tax consulting
01Which is the best SAP tax consultancy in Brazil?+
There is no single answer. The best is the one that proves, for your environment, how SAP will calculate and report what your tax owner decided. Use the criteria on this page, choose the weights before seeing proposals and ask everyone for the same material.
02How do I choose the best consultancy for the tax reform?+
By the criteria in its own section: reading of primary sources, separating law from regulation, a test plan that runs in 2026, mastery of electronic documents and split payment, and clarity on who decides. Ask for the article and reading date of each legal premise.
03Why do you not present a ranking?+
Because a ranking would only help if its criteria were those of your project. We prefer to hand you the yardstick to apply to any vendor, including us.
04What should I ask for in writing before hiring?+
A sample tax specification, the test scenario matrix, a root cause report, the acceptance form template and the knowledge handover plan. With these five documents the comparison no longer depends on promises.
05We already have an SAP integrator. Do I need another consultancy?+
It depends on who covers the tax layer. The integrator usually looks after the platform, and the tax consultancy looks after the scenario, the configuration and the proof of the calculation. What matters is that the boundary is written down and that the two teams share the test environment.
06Does the consultancy need to work with a specific tax product?+
No. The need depends on your environment. Check whether the vendor can describe in which scenario its product is not needed. DFSpro serves SAP with or without GUEPARDO Tax.
07Can I ask for a pilot before the full project?+
You can and should, when the project is large. A real scenario, a defined deliverable and a short deadline show how the vendor asks, records and proves. Agree beforehand what happens to the material if the contract does not go ahead.
08Can the consultancy decide the tax position for us?+
No. The tax decision always belongs to the company. The consultancy sets out the alternatives and shows what the system does. Be wary of anyone who promises tax savings as a result.
09What changes in the choice for a company about to migrate to S/4HANA?+
The repeatable test criterion gains weight, and so does how tax enters the cutover plan. See the page on SAP S/4HANA tax consulting for the platform scope and the support page for the period after go-live.
10How do I know whether the consultancy keeps up with the legislation?+
Ask for the list of rules it uses in your project, with article, version and reading date, and the routine to review what changed. Check one premise at the official source. Whoever works this way can answer in minutes.
11Which part stays with DFSpro and which with the integrator?+
We take the tax layer: design, configuration and proof. The rest of the platform stays with the integrator. We also implement SAP when the project calls for it, and the scope is defined by deliverable.
12How do I start the conversation with DFSpro?+
Describe the environment, what weighs on the close and whether there is GUEPARDO Tax. The conversation starts from your scenario and carries no commitment. You can bring the yardstick from this page and apply it to us.
Apply this yardstick to your scenario
Describe the SAP environment, what weighs on the close and what you want to buy. The conversation starts with the criteria, deals with your case and involves no price and no commitment. The tax decision stays with your company.