Tax solution for SAP: how to choose the one that closes the tax cycle
Choosing a tax solution for SAP means deciding whether tax assessment, SPED, NF-e and tax proof run on a native solution, a third-party tax add-on, an external platform or in-house ABAP, and the right choice is the one that covers the whole tax cycle inside the ERP, with no side spreadsheet. The tax cycle runs from the document to the assessment, from the assessment to the filing and from the filing to proof during an audit. Each tax software path delivers something real and stops at some point, and companies with SAP at the center find in GUEPARDO Tax the fit that closes this cycle inside the environment.
Updated on
Choose the entry point that fits your role
Each role sees the choice of tax solution differently. Start with yours.
01Executives and CFO
Why the choice often goes wrong, the cost of getting it wrong and what the law requires of any solution.
Go to the section02Tax and tax law
The eight criteria, the comparison by type of solution and what each module covers.
Go to the section03IT and SAP
How each module connects to SAP, ECC and S/4HANA, and what that asks of ABAP and of the upgrade.
Go to the section04Procurement and contracting
Buyers' doubts, 25 questions for the supplier and the implementation phases.
Go to the sectionShortcuts for choosing the tax solution
Why does the tax solution that is right on paper fail at the SAP close?
The tax solution that is right on paper fails at the close when it is chosen by its feature list, not by what it can prove in assessment, in a change of law and in an audit of SAP.
The tax solution is usually chosen by the feature list in the proposal, and it is judged by what it can prove: at the close, in a change of law and in an audit.
The feature is compared, not the proof
Two proposals list the same obligations. The difference shows up when the law changes, when the tax auditor asks where a number came from and when the ERP is upgraded.
The cost arrives after signing
The rework of each close, each layout change and each SAP upgrade is not in the proposal, and it arrives with the environment already in production.
The deadline does not negotiate
The tax reform and the ECC migration set dates, and the solution chosen now is the one that will run the first close with CBS.
The problems any tax solution can show
Each problem is a limitation of a type of solution, not of a company. Choose the type you are evaluating and see only what concerns it.
72 problems in 12 areas
Showing 72 problems
See problems for:
Coverage of obligations
6 problems
- Covers the main obligations and leaves out your business's exceptions.All types
- State or city outside the contracted scope, or served only by an additional module.Native SAPAdd-onPlatform
- NFS-e for a city with no web service and MDF-e stay in a separate process.Native SAP
- Calculates the tax, but does not book it or generate the file: half of the path.Platform
- A new obligation calls for an additional module, project or contract.All types
- Federal, state and municipal in separate tools, with no single view.Add-onPlatform
Data and side spreadsheet
6 problems
- A side spreadsheet for everything the software does not do.All types
- Manual reconciliation between tax assessment and accounting.All types
- Data leaves SAP by file and comes back typed in or checked by hand.Platform
- Two databases, the supplier's and SAP's, and someone decides which one counts.Add-onPlatform
- Tax master data and rates updated by hand, by checking each website.All types
- Tax rule kept in a spreadsheet or folder, outside the system.In-house ABAP
Legislation and layout
6 problems
- Each layout change depends on who updates and who applies it in your environment.Native SAPAdd-onPlatform
- The change arrives by note or package that someone must apply and test.Native SAP
- In in-house code, the rule is rewritten with each regulation.In-house ABAP
- The update becomes a project or requires downtime of the environment.Add-onIn-house ABAP
- Between the change in the law and the update, the legal basis is out of date.Add-onPlatformIn-house ABAP
- Nobody records which rule applied in each period.All types
Integration and custom code
6 problems
- The interface with SAP is revalidated at each release.Add-onPlatform
- Tax data starts to exist in two databases.Platform
- Each scenario gets an interface, and the interfaces pile up.Add-onPlatformIn-house ABAP
- ABAP programs live in the heads of a few people.In-house ABAP
- Custom code needs adapting when S/4HANA simplifies it.In-house ABAP
- An ERP other than SAP is left out of the solution or requires another product.Native SAPAdd-on
Implementation and timeline
6 problems
- The first verified result takes time: data load and connection tests come first.Add-onPlatform
- The scope grows by module, and each module has its own implementation.Add-onPlatform
- Each new obligation in ABAP is a project of specification, code and testing.In-house ABAP
- The technical test passes, and the close differs from what tax expected.All types
- The tax team joins late, and the adjustment comes after go-live.All types
- A high volume of documents shows the limit only in production.All types
Close and operation
6 problems
- The close is late because assessment depends on manual checking.All types
- The error shows up after submission, and the amendment becomes a scramble.All types
- Without pre-validation, the non-conformity only appears at delivery.All types
- The deadline for each obligation lives in a calendar outside the system.All types
- The difference between assessment and document is left with no demonstrated cause.All types
- Nobody knows who delivers each step.All types
Audit and inspection
6 problems
- From the value of the obligation, you cannot get to the document and the rule that produced it.PlatformIn-house ABAP
- Traceability goes through two systems, and each one keeps its own piece.Platform
- The calculation of an old period cannot be reproduced.All types
- Files and system must stay available to the Federal Revenue Service for the legal period, even after the contract.Add-onPlatformIn-house ABAP
- An incorrect or missing file exposes the company to a fine.All types
- After an assessment notice, rebuilding the rule and the document becomes rework.All types
Support and dependence on third parties
6 problems
- When the case touches SAP and the product, two channels answer, and one points to the other.Add-onPlatform
- Support answers for the product, not for the result of the calculation.Add-onPlatform
- Continuity depends on who wrote the code.In-house ABAP
- The product changes generation, and the company migrates without having chosen the moment.Native SAPAdd-onPlatform
- Compatibility with the next release is in the supplier's hands.Add-onPlatform
- Changing supplier forces you to redo setup and data load.Add-onPlatform
People and organization
6 problems
- The rule lives in the head of one key person.All types
- Tax and IT point at each other when the number differs.All types
- Each analyst has their own way and their own spreadsheet.All types
- Turnover takes knowledge of the rule away.All types
- Changing a parameter has no approver and no record.All types
- Controllership reconciles what tax assesses, with no shared trail.All types
Cost and contract
6 problems
- The license is low, and the cost is in services and maintenance.Add-onPlatform
- An obligation that seemed included calls for an additional module.Add-onPlatform
- The rework of each close, layout and update stays outside the proposal.All types
- The contract grows with volume, users or modules.Add-onPlatform
- The conversion to S/4HANA reopens the compatibility check for each supplier.Add-onPlatform
- Losing the person who wrote the code costs replacement time.In-house ABAP
Migration from ECC to S/4HANA
6 problems
- ECC has mainstream maintenance until 31/12/2027, and the tax solution enters the same decision.All types
- The third-party add-on needs a compatibility check, and the Readiness Check only lists it.Add-on
- In-house code is simplified and adapted at the destination.In-house ABAP
- The native product changes generation, with new configuration.Native SAP
- Brazil localization objects call for a tax test after each package.Native SAP
- In a public cloud ERP, extending the standard is limited.Add-onIn-house ABAP
Tax reform: CBS and IBS
6 problems
- The solution must deliver the version of each NF-e and NFS-e technical note.All types
- IBS and CBS are assessed separately and coexist with ICMS, ISS, PIS and COFINS until 2033.All types
- Split payment links the tax document to the payment transaction.All types
- Imports and exports get their own rules.All types
- Coverage arrives gradually, by scenario and by version.Native SAP
- Without a written delivery roadmap, coverage only shows up when the deadline arrives.All types
A good part of these problems is born from the same origin: the solution lives beside SAP, not inside it.
The dates that tighten this proof
| Date | What the official text sets |
|---|---|
| 01/01/2026 | LC 214/2025, art. 62, requires cities and the Federal District to authorize the national-standard NFS-e or share the documents of their own issuer with the national environment. There is a transitional rule until 31/12/2032. |
| 2026 | EC 132/2023 (ADCT, art. 125) sets IBS at 0.1% (state) and CBS at 0.9%. LC 227/2026 has already amended LC 214: the text keeps changing. |
| 2027 | Under art. 126 of the ADCT, CBS is charged from 2027. IBS comes in at 0.05% state plus 0.05% municipal in 2027 and 2028. EFD-Contributions and SPED must keep up. |
| 31/12/2027 | SAP states mainstream maintenance of Business Suite 7 until 31/12/2027, with optional extended maintenance until 31/12/2030. Those on ECC decide the tax solution and the migration at the same time. |
| 2029 to 2033 | ICMS and ISS fall in decreasing proportion from 2029 to 2032 and are extinguished from 2033. For years the company assesses the old and the new taxes side by side. |
| Every year | Law 8.218/1991 requires digital files to be kept available to the Federal Revenue Service (art. 11) and provides a fine for incorrect information (art. 12). The EFD ICMS/IPI Guide is at version 3.2.4, of 10/09/2026. |
Go deeper on the effect of the reform in SAP in CBS and IBS tax reform. The tax reading of each rule belongs to your company; the tool must be ready for what it decides.
How companies solve the choice today, and where does each path stop?
What is the difference between a native solution, add-on, external platform and in-house ABAP?
A native solution, a third-party add-on, an external platform and in-house ABAP are the four ways to cover SAP tax, and each delivers one part of the tax cycle and stops at a different point.
Companies solve the choice in four ways, and some put the decision off, which the 2027 calendar does not follow. Each path delivers something real and stops at some point.
Native SAP
What it delivers: the base in the ERP itself, with the Brazil localization, DRC for documents and TDF for SPED. Where it stops: scope varies by product and by release, and MDF-e and NFS-e by city need confirmation.
Third-party add-on
What it delivers: dedicated tax scope inside the ERP, by supplier. Where it stops: each supplier covers a different set, and compatibility must be checked at each release conversion.
External platform
What it delivers: serves several ERPs at once, with updates in the supplier's cloud. Where it stops: runs outside SAP, connects by interface and takes tax data out.
In-house ABAP
What it delivers: a tailor-made rule for each exception of the company. Where it stops: each change in the law comes back as a project, and knowledge stays concentrated in a few people.
No path solves everything, and the market has names in each one of them.
What tax software exists for SAP?
Sixteen names present in the Brazilian tax solution market.
ONESOURCE Tax One
Thomson Reuters
Thomson Reuters cloud tax software, aimed at tax assessment and tax obligations.
Synchro Tax Solution (SynchroCloud, Synchro4TDF)
Synchro
Provider of tax solutions, in the cloud and on premise, integrated with the main ERPs.
Avalara Brazil (AvaTax)
Avalara
Provider of cloud tax solutions for the tax and tax law areas.
4Tax-Fiscal and 4TaxCloud
Seidor
Seidor tax solution, listed in the SAP partner catalog.
Sovos Brazil
Sovos
Tax compliance company with international operations and a presence in Brazil.
SAP Document and Reporting Compliance
SAP
SAP solution for electronic documents and mandatory tax reports.
SAP Tax Declaration Framework for Brazil (TDF)
SAP
SAP solution for Brazilian tax declarations, such as SPED and eSocial.
SOFICOM and INVOICECON
CAST Group
CAST Group tax solutions, complementary to SAP.
SAP DRC + SONDA Gallery
SONDA
SONDA tax solution, presented together with SAP DRC.
Comply, Comply e-Docs and Comply Analytics
SONDA
SONDA line of tax solutions, with Comply.
Systax (Content as a Service, J1BTAX Update)
Systax
Tax intelligence company, with tax content for ERPs.
ONESOURCE Mastersaf
Thomson Reuters
Thomson Reuters tax solution, from the ONESOURCE family.
There are other suppliers in the market. In any conversation, check each one's website for the current scope, version and terms.
Which criteria decide the tax solution for SAP?
Eight criteria decide the tax solution for SAP: Brazilian tax coverage, up-to-date legislation without a project, a single supplier, audit trail, support, time to the first result, link with ECC and S/4HANA and readiness for the reform.
- Brazilian tax inside SAP
- Up-to-date legislation without a project
- One supplier for the whole set
- Audit trail
- Support with one owner
- Time to the first result
- Link with ECC and S/4HANA
- Readiness for the reform
1. Brazilian tax inside SAP
Assessment, bookkeeping and obligations for the three levels of government in the environment where tax already works end the side spreadsheet. The question that decides: which obligations, states and cities come out of SAP without an intermediate file?
2. Up-to-date legislation without a project
Every change in the law that turns into a development project consumes budget and calendar. The question that decides: who applies the change, within what deadline, and does it require a project from my team?
3. One supplier for the whole set
Tax, electronic documents, foreign trade and analytics from different suppliers multiply contracts and interfaces. The question that decides: how many contracts and how many interfaces to cover everything?
4. Audit trail
In an audit, whoever explains the number wins. The question that decides: from the value of the obligation, can I get to the document and the rule that produced it?
5. Support with one owner
The solution is only worth it if someone answers for it after go-live. The question that decides: who handles the incident and proves the cause?
6. Time to the first result
Months with no verified delivery are months of risk on the tax calendar. The question that decides: what is the first deliverable that can be verified against what SAP already assesses?
7. Link with ECC and S/4HANA
The solution must survive the migration of your ERP. The question that decides: is compatibility with my version and the next one confirmed in writing?
8. Readiness for the reform
In 2027 CBS comes in and the old taxes coexist with the new ones for years. The question that decides: what is already delivered and how is each scenario proved in my environment?
Step-by-step decision
- 01
Describe the operation
List the ERP and version, companies, states, cities, and the obligations that come out of SAP and those that come from outside.
- 02
Choose the type of solution
Compare the four types of solution and rule out the ones that do not cover your operation.
- 03
Ask the eight questions
Take the same questions to each supplier and demand a written answer, with a real example.
- 04
Prove it in your environment
Ask for a scenario of your own, with the expected value next to the obtained one, before signing.
Extra questions for the supplier meeting
About the product
- Which obligations are in the contract and which depend on an additional module?
- How does the product handle an NFS-e from a city with no web service?
- What does the supplier deliver when a file layout changes?
- Where are the files and history kept, and for how long?
About implementation and support
- Who implements, and who answers when the result differs from the document?
- What is the first verified deliverable, and against what?
- How is compatibility with the next SAP release confirmed?
- What does your team need to decide, and what does the supplier take on?
Those who want to keep the ERP lean need legislation without a project and a safe link with S/4HANA: see Tax Clean Core and the path in migration to S/4HANA.
A solution that covers the three levels of government inside SAP, keeps up with the law without becoming a project, has one owner and proves each number in an audit. Right?
What is GUEPARDO Tax and who implements it in SAP?
GUEPARDO Tax is the NTT DATA tax add-on for SAP, which covers assessment, SPED and ancillary obligations inside the ERP, and DFSpro, Authorized Channel, implements and governs the product in your environment.
Whoever implements GUEPARDO in your SAP is DFSpro, an Authorized Channel and specialist in tax in SAP and in GUEPARDO Tax: design, configuration and proof in your environment.
GUEPARDO
NTT DATA, which holds GUEPARDO, describes it as a portfolio of tax and financial solutions. Tax, installed as an add-on in SAP, is the base.
Founded in 2018, in Curitiba
DFSpro works on tax assessment, SPED and ancillary obligations inside its clients' SAP, and GUEPARDO Tax is its specialty.
The category
Tax governance in SAP with GUEPARDO Tax: assessment, SPED and obligations in the same environment, with proof by scenario.
With clear criteria and a product in sight, the choice stops being an opinion.
Why is GUEPARDO the best choice for the tax solution in SAP?
GUEPARDO is the best choice for those who have SAP at the center and need assessment, SPED, electronic documents, foreign trade and analytics in the same environment, and six reasons support this conclusion.
For a company with SAP that needs assessment, SPED, electronic documents, foreign trade and analytics in the same environment, GUEPARDO is the best choice.
What changes in the tax routine
Tax inside SAP
NTT DATA describes Tax as an add-on that complements the assessments in the standard menu, with queries and reconciliation reports in the SPED formats.
One set, one supplier
Tax, e-Invoicing, Analytics, Global Trade, Audit and Process Automation come from the same family, offered by NTT DATA, which reduces contracts and interfaces.
Legislation without a project
In e-Invoicing, NTT DATA states that new features, layouts and regulatory changes come through the cloud, with no impact on the client.
Deadline and pre-validation
According to NTT DATA, the Tax Calendar assigns an owner per step and warns of the deadline, and the pre-validation routines show the non-conformity before delivery.
One view for the manager
Fiori dashboards bring together assessment, files, payment slips, credits and calendar by company, branch and period, according to NTT DATA.
Implementation with proof
DFSpro implements in phases and keeps, for each scenario, the source document, the expected value and the obtained one.
To see the whole portfolio, go to GUEPARDO modules.
How to compare tax solutions for SAP on twelve criteria?
Twelve criteria compare a native solution, add-on, external platform and in-house ABAP with GUEPARDO: coverage, legislation, supplier, audit, support, timeline, ECC and S/4HANA, reform, implementation, cost, migration and record keeping.
Four factors also weigh on cost and migration: implementation effort, total cost, migration risk and record keeping for audits.
| Criterion | Native SAP | Third-party add-on | External platform | In-house ABAP | GUEPARDO |
|---|---|---|---|---|---|
| Brazilian tax inside SAP | Strength: already in the ERP. Limit: scope varies by product and by release, and MDF-e and NFS-e by city need confirmation. | Strength: dedicated tax scope. Limit: each supplier covers a different set. | Strength: serves several ERPs. Limit: runs outside SAP and connects by interface. | Strength: tailor-made. Limit: each obligation and each exception is built by the company. | According to NTT DATA, an add-on installed in SAP that complements the assessments in the standard menu, at the three levels of government and in all states. |
| Up-to-date legislation without a project | Arrives through Notes and Support Packages, and someone must apply them in the system. | Depends on who updates and who applies it in your environment. | Updates in the supplier's cloud, and the link to the ERP stays yours. | The company follows the rules and rewrites the code at each change. | According to NTT DATA, in e-Invoicing layouts and regulatory changes are applied in the cloud by its team, with no impact on the client. |
| One supplier for the whole set | Different SAP products for documents, SPED and reports, each with its own license and configuration. | Usually one module at a time, from different suppliers. | May cover calculation and e-invoicing, depending on the supplier. | Each module is a development project. | Tax, e-Invoicing, Analytics, Global Trade, Audit and Process Automation, offered by NTT DATA (Global Trade in partnership with Conexos). |
| Audit trail | Data stays in SAP, and the rule is explained by the configuration. | Varies by supplier: ask for the path from the number to the document. | Data stays outside SAP: confirm where and how it leaves at the end of the contract. | Depends on the documentation the team maintains. | According to NTT DATA, the state level keeps a data history for audits, and Audit validates files and cross-checks information. DFSpro keeps the evidence for each scenario. |
| Support with one owner | SAP support, with Brazil localization cases handled through Notes. | Two channels when the case touches SAP. | The supplier answers for the product, and the ERP is another channel. | Continuity depends on who wrote the code. | NTT DATA answers for the product and DFSpro, an Authorized Channel, implements, governs and supports in AMS Fiscal. |
| Time to the first result | Depends on the installed generation of the product and the Notes applied. | Varies by supplier and by contracted scope. | Requires an interface and data load before the first assessment. | Goes through specification, construction and testing of each program. | Installed inside SAP, according to NTT DATA, assessment starts from the data already there, and the first result is checked against the assessment you already have. |
| Link with ECC and S/4HANA | Stays in the SAP ecosystem. ECC has mainstream maintenance until 31/12/2027. | Compatibility must be checked at each release conversion. | The link is maintained at each SAP upgrade. | Code simplified in S/4HANA requires adaptation. | Add-on for SAP, with DFSpro designing the implementation with the migration to S/4HANA already in mind. |
| Readiness for the reform | Arrives gradually, by scenario and by version. | Ask what is already delivered and what is under development. | Depends on the supplier's roadmap. | Each change becomes a development project. | DFSpro keeps its own Tax Reform manual (IBS, CBS and IS) and proves each scenario in your environment, with the expected value next to the obtained one. |
| Implementation effort | Configuration and Notes inside SAP, with the internal team or the integrator answering for the scope. | Add-on installation, configuration and master data load, depending on the supplier. | Interface, data load and connection tests with the ERP before the first result. | Specify, program and test each obligation, one by one. | Add-on implemented by DFSpro in phases: diagnostic, setup, testing, go-live and AMS Fiscal. e-Invoicing follows the SAP Activate methodology, according to NTT DATA. |
| Total cost of ownership, in qualitative terms | SAP licenses already held, plus the cost of applying Notes, testing and keeping knowledge of the rule. | Module license, updates and maintaining compatibility at each release. | Subscription, interface and the data storage layer outside SAP. | Development hours at each change in the law and the risk of depending on a few people. | One product supplier and modules contracted as needed. In cloud e-Invoicing, according to NTT DATA, the layout rework stays with the NTT DATA team. The Tax Diagnostic translates these items to your scenario. |
| Risk in the migration from ECC to S/4HANA | Follows SAP's own roadmap, with ECC under mainstream maintenance until 31/12/2027. | Requires checking the add-on's compatibility at conversion, and SAP's readiness report lists only third-party software. | The interface must be revalidated at each release change. | Part of the code must be adapted or discarded, and ABAP Cloud exists only from release 2022 onward. | NTT DATA describes Payments and Credit & Collections serving ECC and S/4HANA. Compatibility with your version is confirmed in the Tax Diagnostic. |
| Record keeping and reproduction for audits | Documents stay in SAP, and keeping the environment for the legal period is the company's job. | Also keep the add-on and old versions for the statute of limitations period. | The contract must provide for access to the system for the legal period, because part of the assessment runs outside. | Keep code, versions and transports for the whole period. | Data history at the state level, according to NTT DATA, and evidence per scenario kept by DFSpro. The reading of the period is your company's. |
The other types win in specific scenarios. For those with SAP as the main ERP who need assessment, SPED and electronic documents in the same environment, the add-on inside SAP is the shortest path, and GUEPARDO is the best choice within it.
Request the Tax Diagnostic and see GUEPARDO answering with data from your environment.
For what kind of company does GUEPARDO pay off most?
GUEPARDO pays off most in a company that runs SAP as its main ERP, has obligations at the three levels of government and wants a single environment for assessment, documents and proof.
- 01
SAP as the main ERP
The company runs finance and tax in SAP, in ECC or S/4HANA, and wants assessment and obligations in the same place.
- 02
Obligations at the three levels
There is municipal, state and federal assessment, in several states, and each one has its own deadline, layout and exception.
- 03
Many documents to handle
The volume of inbound and outbound invoices calls for direct messaging and several channels of entry, electronic or not.
- 04
Foreign trade in the routine
Imports and exports share data with tax and call for end-to-end automation.
- 05
One supplier, one environment
The manager wants to reduce contracts and interfaces, and to have one owner for the whole set.
- 06
Tax reform with proof
The company wants to reach 2027 with a tested scenario, the expected value next to the obtained one and evidence kept.
Recognize your company? The Tax Diagnostic shows the right first step.
How do GUEPARDO Tax and Audit cover assessment in SAP?
According to NTT DATA, Tax assesses and delivers the obligations inside SAP, and Audit checks the file before it goes out.
What it solves day to day
Assessment, file generation, payment slips and credits in the same environment. According to NTT DATA, the Tax Calendar assigns an owner per step and sends deadline alerts to those involved, which takes follow-up out of the spreadsheet.
What it covers
According to NTT DATA, the three levels of government. At the federal level, a single database in assessment. At the state level, all states, with history for audits. At the municipal level, the layout required by each city, with a view of the whole document history.
How it connects to SAP
According to NTT DATA, it is installed as an add-on in SAP and complements the assessments in the standard menu, with queries and reconciliation reports in the SPED formats. Fiori dashboards consolidate assessment, files, payment slips, credits and calendar by company, branch and period.
Without and with the module
Without: each tax has its own checking spreadsheet and its own date. With, according to NTT DATA: assessment, pre-validation, file and calendar in the same flow, and non-conformities show up before delivery.
Who tends to benefit most
Companies with several states and cities, obligations at the three levels and a small tax team for the volume of deliveries.
First verifiable deliverable
One assessment, of one tax and one period, run in SAP and checked against the value the company assesses today, with each difference explained.
Obligations in the NTT DATA overview
Assessments
- ICMS and IPI, with Block K
- PIS and COFINS
- ISS
- IRPJ and CSLL
- CIAP
Bookkeeping and files
- EFD ICMS/IPI
- EFD Contributions
- ECD and ECF
- EFD-Reinf
- Magnetic files for ISS
Payment slips and ancillary filings
- GNRE Online
- DCTF and DIRF
- PER/DCOMP and REINTEGRA
- GIAs, DIPAM and DIEF
GUEPARDO Audit: the check that comes before delivery
Validation before submission
Integrated with Tax, Audit validates files and cross-checks information from different sources to identify non-conformities, according to NTT DATA.
Less assessment time
NTT DATA also cites reduced assessment time and automated delivery of tax reports.
Services adjusted to the operation
According to NTT DATA, Audit offers tax services adjusted to each operation and supports risk assessment and adaptation to the tax environment. The reading of incentives and of the tax position is your company's.
First verifiable deliverable
One obligation file validated and cross-checked before submission, with the differences listed and the cause of each one.
Go deeper on assessment in GUEPARDO Tax and in Block K in SAP.
Go deeper on bookkeeping in EFD-Reinf and ECD and ECF.
How to handle NF-e, NFS-e and CT-e in SAP with e-Invoicing?
According to NTT DATA, e-Invoicing handles issuing and receiving NF-e, NFS-e and CT-e and EFD-Reinf, with direct messaging to SEFAZ.
What it solves
Issuing and receiving NF-e, CT-e and NFS-e and issuing EFD-Reinf, with direct messaging to the national SEFAZ and the SPED environment, according to NTT DATA. According to NTT DATA, the operations are available by API, for any ERP.
How documents come in
According to NTT DATA, documents come in by web service from SEFAZ and city halls, e-mail with PDF reading by machine learning and OCR, a supplier portal and API, electronic or not. Web service capture runs every hour on SEFAZ and every ten minutes on city halls, according to NTT DATA.
How documents go out
According to NTT DATA, the module generates, signs and validates the XML at the required agency, prioritizes batches, prints the DANFE and the DANFSE, returns the status to the ERP and sends B2B to those involved. It accepts manual or automatic contingency. In city halls with no web service, the NFS-e goes out by RPA.
How it connects to SAP
According to NTT DATA, there are two parts, the cloud and the ABAP add-on in SAP, linked by RFC, a standard method for external connection. The cloud runs on AWS, managed by the NTT DATA team, and the firewall rule lets SAP talk only to GUEPARDO.
Without and with the module
Without: each document source has its own flow, and a new layout becomes a project. With, according to NTT DATA: a monitor in SAP concentrates the documents, and new layouts and regulatory changes come in through the cloud, with no impact on the client. Also with no impact on SAP PO licensing, according to NTT DATA.
First verifiable deliverable
One end-to-end inbound flow, for example the purchase NF-e from capture to posting, checked against the current process.
What the inbound monitor processes in SAP
| Inbound document | Scenarios the monitor processes | Flow suggested by NTT DATA |
|---|---|---|
| Purchase NF-e | Fixed assets, use and consumption, energy in the free market, process with and without a contract, return of loaned goods, processing with and without a combined invoice, return from processing, shipment on behalf of a third party and triangular operations | Purchase order, MIGO, MIRO |
| NF-e with batch and receipt notice | Material with batch and receipt notice | Purchase order, VL31N, MIGO, MIRO |
| Transfer NF-e | Transfer between plants | J1B1N with the outbound reflection, transfer order, MIGO and MIRO |
| Return and shipment NF-e | Return from warehouse, return from repair, free supply, free sample, return from demonstration, trade fairs and supplementary invoice | J1B1N |
| Services NFS-e | Contracting of services with and without a contract and water, power, gas and telephone bills | Purchase order and MIRO, or Purchase order, FRS and MIRO |
| Freight CT-e | Planned or unplanned freight with later debit, freight on an inbound or outbound NF-e and freight planned in the SAP transportation module | Purchase order for the NF-e and MIRO, or Purchase order, MIGO or FRS, and MIRO |
| Sales return | Return of goods sold | VA01, VL01N, VF01 |
NTT DATA records that all inbound scenarios are prepared for foreign currency and recommends not creating the purchase order automatically.
Monitoring in SAP
According to NTT DATA, the NF-e follows transaction J1BNFE and the NFS-e uses the ECG transactions. The add-on brings an outbound NFS-e monitor, and SAP already brings the outbound NF-e and CT-e monitor.
Portal and certificate
According to NTT DATA, the portal brings dashboards and reports for NF-e, NFS-e and CT-e, a preview of documents, digital certificate management, internal and external users and e-mail notifications.
Download and simulation
According to NTT DATA, the portal brings mass download of XMLs and PDFs, a download center, tax simulation and notification to the supplier when automatic processing fails.
Go deeper on e-Invoicing in GUEPARDO e-Invoicing, and on the migration of SAP NFE in from GRC NFE to DRC.
See your volume of documents and your purchase scenarios running in the monitor.
How to cover foreign trade, analytics and automatic master data in SAP?
According to NTT DATA, Global Trade, Analytics and Process Automation extend tax without taking the operation out of SAP: foreign trade, a single dashboard and automatic master data.
Global Trade
What it solves: Management platform that concentrates the managerial and operational demands of foreign trade, imports and exports, in one place, according to NTT DATA.
What it covers: According to NTT DATA, imports and exports among clients, suppliers, carriers, agents, customs clearance and the ERP, with information integration with government entities.
How it connects: Developed by Conexos and offered in partnership with NTT DATA. Integrates the information with the ERP.
Without and with the module: Without: foreign trade lives in a system or spreadsheet beside tax. With, according to NTT DATA: the end-to-end process is visible on a platform that talks to the ERP.
Who tends to benefit most: Industrial distributors of imported products, trading companies and customs brokers, according to NTT DATA.
First verifiable deliverable: One import process, from opening to closing, checked against the current control.
Analytics
What it solves: A central dashboard in place of separate reports by module, to answer questions that would take a long time to find manually, according to NTT DATA.
What it covers: According to NTT DATA, on-premise and cloud data from all GUEPARDO modules in a single analytics tool.
How it connects: According to NTT DATA, based on SAP Analytics Cloud, with the data of the contracted modules.
Without and with the module: Without: tax, finance and controllership look at numbers from different sources. With, according to NTT DATA: a single view, fed by the modules in use.
Who tends to benefit most: Those who contract more than one module and want to compare assessment, documents and finance on the same dashboard.
First verifiable deliverable: A dashboard with the indicators of a module already in use, checked against the current report.
Process Automation
What it solves: Automates repetitive tasks with RPA and machine learning and gives visibility to the steps of each process, according to NTT DATA.
What it covers: According to NTT DATA, from updating the client and supplier master data to setting tax rates in a commercial transaction.
How it connects: According to NTT DATA, it integrates master data from different government websites into the ERP, in a single consolidated database.
Without and with the module: Without: tax master data depends on manual lookups on each website. With: master data reaches the ERP, and the module seeks to eliminate duplicates and inconsistency, according to NTT DATA.
Who tends to benefit most: Companies with many clients and suppliers, changing tax master data and heavy processing loads.
First verifiable deliverable: A master data update routine run on a sample and checked against the current master data.
For foreign trade, see the Global Trade page and the integration with Siscomex.
Go deeper on the integrated dashboard in GUEPARDO Analytics.
How does GUEPARDO cover collections, Pix, cash and credit in SAP?
According to NTT DATA, Payments, Cash Application and Credit & Collections bring collections, Pix, cash and credit into the same SAP environment.
GUEPARDO Payments: collections, Pix and reconciliation in SAP
What it solves
According to NTT DATA, it connects SAP to more than 15 Brazilian financial institutions and manages collections, automatic clearing of receivables and file exchange in a cloud service.
What it covers
According to NTT DATA, Pix (Brazil's instant payment system) and boleto (Brazilian bank slip) in the same collection, with a dynamic QR Code and online settlement, collections tied to the CNPJ through DDA, and credit bureau listing and protest in case of default. NTT DATA states native integration of Bolecode with Itaú BBA.
How it connects to SAP
According to NTT DATA, applications and APIs manage secure communication between SAP, in ECC or S/4HANA, and the institutions. The stated minimum requirement is SAP ECC EHP4, and the Fiori applications handle monitoring, receipts and approvals.
Without and with the module
Without: the QR Code settles or expires and nobody cancels the collection. With, according to NTT DATA: clearing of the receivable or reversal of a letter of credit triggers the cancellation of the QR Code, and the status at BACEN can be queried online.
Who tends to benefit most
Companies with high-volume collections by boleto and Pix and online stores on SAP Commerce. For them, according to NTT DATA, an add-on creates the Pix transaction and checks the payment every 10 seconds.
First verifiable deliverable
A pilot collection portfolio, with automatic clearing checked against the bank statement.
NTT DATA cites lower bank fees, lower EDI VAN costs and real-time clearing among the benefits of Payments.
Cash Application and Credit & Collections: cash and credit in the same environment
| Topic | Cash Application by Serrala | Credit and Collections by Serrala |
|---|---|---|
| What it solves | According to NTT DATA, it compares payments received with open accounts and automates bank reconciliation, with RPA and machine learning. | According to NTT DATA, it simplifies and automates credit and collections management, with 360-degree risk monitoring. |
| What it covers | According to NTT DATA, real-time cash allocation, dashboards, KPIs, integrated workflows and support for any statement format. | According to NTT DATA, an automated scorecard, credit assessment with AI and data from third parties and insurers, a cockpit with credit rating, limit, 12-month exposure and DSO, and rule-based collection strategies, with disputes, plans and promises to pay. |
| How it connects to SAP | According to NTT DATA, it is integrated with the ERP and uses SAP data with no duplicate interfaces or sources, is ready for S/4HANA and Fiori, and posting rules stay with the business team. | According to NTT DATA, it integrates with SAP S/4HANA and SAP ECC 6 and also works without the SAP Business Partner. |
| Without and with the module | Without: cash stays unallocated until someone reconciles it. With, according to NTT DATA: real-time allocation and a customer account updated first thing in the morning. | Without: credit information lives in several systems. With, according to NTT DATA: a cockpit with a customer view, an audit trail of decisions and fewer manual steps. |
| Who tends to benefit most | Those who receive at high volume and still reconcile by hand. | Those who grant credit and collect at volume and want to reduce DSO, a benefit cited by NTT DATA. |
| First verifiable deliverable | One bank account reconciled in parallel with the current process. | A customer portfolio with limit and risk rating calculated in the cockpit. |
Both applications are from Serrala and offered with NTT DATA. DFSpro works on the tax modules, and their implementation stays with NTT DATA and Serrala. To decide where to start, use which module to choose.
Which tax solution fits each company profile with SAP?
Each company profile with SAP weighs the choice differently, and each one has what weighs, what GUEPARDO changes and the first verified deliverable.
Group with several CNPJs
What weighs: Each establishment has its own registration, series and obligation, and assessment repeats by company and by branch.
What GUEPARDO changes: The Tax Fiori dashboards consolidate assessment, files, payment slips, credits and calendar by company, branch and period, according to NTT DATA, and the product documentation covers branches with the same CNPJ with a single record in EFD Contributions, by parameter.
First deliverable: The tax standard of one establishment replicated and checked in another. See tax rollout in SAP.
Intense foreign trade
What weighs: Import data must reach the tax document and the bookkeeping, and the process involves agents and customs clearance.
What GUEPARDO changes: According to NTT DATA, Global Trade, from Conexos, handles the end-to-end process, and the Tax documentation handles the import data on the invoice, including the drawback regime.
First deliverable: One import run from the process to SPED, checked against the current control.
Retail with high NFC-e volume
What weighs: The volume of receipts and collection at the counter and online call for batch bookkeeping and bank reconciliation.
What GUEPARDO changes: The product's SPED Fiscal recognizes NFC-e as model 65, and Payments creates the Pix transaction in SAP Commerce, with the QR Code checked every 10 seconds, according to NTT DATA.
First deliverable: One day of sales booked and reconciled. See NFC-e in retail with SAP.
Services in many cities
What weighs: Each city has its own bookkeeping model and its own declaration, and the national NFS-e still coexists with their own issuers.
What GUEPARDO changes: According to NTT DATA, Tax generates the obligations in the municipal layout required, and e-Invoicing queries the city halls every ten minutes, with RPA in those with no web service, according to NTT DATA.
First deliverable: The cities in the operation listed and checked. See national-standard NFS-e and ISS assessment.
Industry with Block K
What weighs: Processing, return and shipment on behalf of a third party generate their own bookkeeping, and Block K requires consistency between inventory and production.
What GUEPARDO changes: The NTT DATA overview includes Block K in ICMS and IPI assessment, and the e-Invoicing monitor maps processing with and without a combined invoice and triangular operations.
First deliverable: One Block K period generated and checked. See Block K in SAP.
Migration from ECC to S/4HANA
What weighs: ECC has mainstream maintenance until 31/12/2027, and every add-on must have its compatibility checked at conversion.
What GUEPARDO changes: DFSpro designs the implementation with the conversion already in mind. NTT DATA describes Payments and Credit & Collections serving ECC and S/4HANA, and e-Invoicing has a cloud part.
First deliverable: The compatibility matrix for your version. See migration to S/4HANA and release update of GUEPARDO Tax.
What to check in the tax solution when migrating from ECC to S/4HANA?
When migrating from ECC to S/4HANA, the tax solution must have its compatibility confirmed in writing: ECC has mainstream maintenance until 31/12/2027, and SAP says to check third-party add-ons at conversion.
Mainstream maintenance of ECC runs until 31/12/2027, with optional extended maintenance from 2028 to 2030. In October 2026, SAP restated these dates.
What SAP says, and what to check in your company
Third-party add-ons
SAP says to check the compatibility of third-party add-ons with S/4HANA, and the SAP Readiness Check only lists third-party software. In your company: ask each supplier for written compatibility, with the target version.
Custom code
According to SAP, in-house ABAP code must be adapted, because a lot of code was simplified in S/4HANA, and it recommends running the ABAP Test Cockpit with the S/4HANA checks. In your company: list the in-house tax programs before choosing the path.
Simplification Item Catalog
SAP groups the changes that may affect the transition into simplification items, and the Readiness Check shows the subset that applies to the system analyzed. In your company: separate the items that touch tax.
Conversion paths
SAP's training materials cover conversion of the existing system, new implementation (greenfield) and selective data transition. In your company: the choice of path is yours, and the tax solution must serve the path chosen.
SAP NFE and DRC
SAP's documentation records the end of maintenance of SAP NFE 10.0 in 2025, states that the Tax Reform will not be supported in GRC NFE and guides the migration to DRC, in the inbound option, through configuration steps. In your company: confirm which generation you are on.
Brazil localization after an update
SAP maintains note 2516353 on Brazil localization objects, such as condition types and internal codes, which may be missing or have incorrect customizing after a Support Package or Feature Package Stack. In your company: include the tax test in the plan for each update.
Five tax check steps for the conversion
- 01
Inventory
List the tax solutions, add-ons and in-house programs that touch documents, assessment and files.
- 02
Compatibility
Ask each supplier for written confirmation of the target version, and record the date.
- 03
Choice of path
Decide between conversion, new implementation or selective transition, with the tax impact of each on the table.
- 04
Proof
Run your own tax scenarios in the new environment, with the expected value next to the obtained one.
- 05
First close
Follow the first real close in the new environment, the window of highest risk.
The full path is in migration to S/4HANA, and the effect of the release update on the product is in release update of GUEPARDO Tax.
Bring the tax inventory of your ECC to the Tax Diagnostic and leave with the order of the conversion.
What the tax reform changes in each function of the tax system?
The tax reform changes six functions of the tax system, and each has an official text behind it and a question that decides the choice of supplier.
The reform does not change all of SAP at once. It changes specific functions of the tax system, and each function has an official text behind it.
| System function | What the official text says | Question for the supplier | Where the function lives in the GUEPARDO portfolio |
|---|---|---|---|
| Electronic tax documents | Every operation with goods or services, including imports, exports and transfers between establishments, requires an electronic tax document (LC 214, art. 60). Technical note 2025.002 of the NF-e Portal, version 1.52 of 01/10/2026, covers the reform fields in NF-e and NFC-e, and technical note 009 of the national NFS-e covers the IBS and CBS layouts. | Which version of the technical notes does the solution meet today, and by when does it deliver the next one? | e-Invoicing |
| Assessment and bookkeeping | The assessment period for IBS and CBS is monthly, and the balance of each is assessed separately (arts. 43 and 45). Deadline and due date are left to the regulation, and only the Steering Committee creates IBS ancillary obligations (LC 227). | How does the solution assess IBS and CBS separately, and who updates it when a new obligation is published? | Tax and Audit |
| Transition from 2026 to 2033 | For 2026, the text sets CBS at 0.9% and IBS at 0.1%, with offset against PIS and COFINS (arts. 346 and 348). In 2027 and 2028, IBS comes in at 0.05% state and 0.05% municipal. Between 2029 and 2032, ICMS and ISS fall in bands, and from 2033 they cease to exist (EC 132, arts. 125 to 129 of the ADCT). | Does the solution handle ICMS, ISS, PIS, COFINS, IBS and CBS in the same period, and how does it treat each year? | Tax |
| Payment and reconciliation | In split payment, the payment service provider segregates and remits IBS and CBS at settlement, and the tax document is linked to the payment transaction (arts. 31 to 36). | Does the solution keep the link between tax document and transaction and reconcile what was segregated? | Payments |
| Steering Committee and regulation | LC 227 creates the IBS Steering Committee, which exercises the administrative powers of IBS in an integrated way and issues the single regulation (arts. 1 and 2). The form, content and deadlines of documents come from a joint act of the Steering Committee and the Federal Revenue Service (art. 60 of LC 214). | How does the solution adapt to a change in regulation or layout? | All modules, with DFSpro governance in AMS Fiscal |
| Imports and exports | IBS and CBS apply to imports, with payment by delivery for consumption clearance or in advance at registration of the declaration (arts. 63 and 76). Exports are immune, with credits preserved (art. 79). | How does the solution link the import declaration and tax document to the calculation, and treat export immunity? | Global Trade and Tax |
The CBS and IBS coverage of each module, in your version, is confirmed in writing with the supplier and proved in a scenario. The tax reading of the articles is your company's.
DFSpro keeps its own Tax Reform manual and proves each scenario in your environment.
How does GUEPARDO handle EFD-Reinf, ECD, ECF, PIS and COFINS, Block K and ISS?
GUEPARDO handles EFD-Reinf, ECD and ECF, PIS and COFINS, Block K, ISS and import data with controls specific to each obligation, according to the product documentation.
Each obligation calls for its own controls, and GUEPARDO handles each one differently, according to the product documentation.
EFD-Reinf
The documentation covers the assessment panel and the event cockpit with authorization control, validations that warn without blocking the assessment, event simulation that does not record a result, transmission by load and reopening, closing and deletion events. Go deeper: EFD-Reinf in SAP.
ECD and ECF
The documentation covers the ECD panel, validation of balances against postings at generation and the auxiliary ledger. It records that the ECD must be imported for the ECF to be delivered and that, with branches, the ECF is submitted by the head office. Go deeper: ECD and ECF in SAP.
PIS, COFINS and EFD Contributions
The documentation covers manual credits, including from prior periods, allocation in records 1100 and 1500, the error log and pre-validations when the file is generated, and the single record for branches with the same CNPJ, by parameter. Go deeper: EFD Contributions in SAP.
EFD ICMS/IPI and Block K
The documentation covers model 55 and model 65 documents, CIAP and the write-off of fixed assets. The NTT DATA overview includes Block K in ICMS and IPI assessment. Go deeper: Block K in SAP and NFC-e in retail.
ISS and NFS-e
The documentation covers the report of cities with no configuration, the sub-assessment report, the field that shows the ancillary obligation met by city and the magnetic files of each municipal model. Go deeper: ISS assessment and national-standard NFS-e.
Import data
The documentation covers the import data that accompanies the invoice, such as the type of import document and the drawback regime, and carries it to the tax file. Go deeper: integration with Siscomex.
How to implement a tax solution in SAP in five phases?
DFSpro implements the tax solution in five phases, from diagnostic to AMS Fiscal, and proves each scenario in the test environment before switching on.
A method that proves
Each scenario keeps the source document, the result and the expected value next to the obtained one. The check comes before go-live.
Own manuals by obligation
PIS and COFINS, EFD-Contributions, ECD, ECF, EFD-Reinf, ISS and Tax Reform, in a version for the client and one for the consultant.
From choice to routine, in five phases
- 01
Tax Diagnostic
Structured assessment of 5 to 8 weeks, led by a senior team, that shows the real risk of the environment and what GUEPARDO must cover first. See SAP Tax Diagnostic.
- 02
Setup
Each rule gets an owner and its own record, in the three layers of setup: calculation schema, conditions and categories. See tax setup.
- 03
Testing
Scenario matrix with the expected value written beforehand and evidence kept per scenario. See tax testing.
- 04
Go-live
Tax go-live checklist and follow-up of the first real close, the window of highest risk. See post-go-live stabilization.
- 05
AMS Fiscal
Continuous governance, with a change cycle, a record of each change and a periodic report. See AMS Fiscal.
What each phase delivers
| Phase | What DFSpro delivers | Where to read |
|---|---|---|
| Tax Diagnostic | A report that maps the tax environment and the GUEPARDO Tax setup. A risk prioritization plan, with each item as Critical, High, Medium or Monitor. A recommendation for the next step, which may be stabilization, a targeted fix or a new assessment on an agreed date. | SAP Tax Diagnostic |
| Setup | A survey of the rules in use, with the origin, the purpose and who answers for each. A comparison of what the system calculates with what the operation should assess, in each CNPJ and each branch. Correction in the test system and documentation of each rule, with purpose, owner and review date. | Tax setup |
| Testing | A scenario matrix, with the expected value defined before running and the evidence kept per scenario, at six test levels: unit, integrated, regression, user acceptance, parallel and close. | Tax testing |
| Go-live and stabilization | Fixed-term assisted follow-up right after go-live, with the same project team, a direct channel with a technical manager and documented knowledge transfer to the internal team. | Post-go-live stabilization |
| AMS Fiscal | A periodic tax health report, a record of each change applied with the technical justification and an incident response channel, within a six-step cycle that repeats. | AMS Fiscal |
What your company receives
Map of the environment
A picture of what SAP does today, the risks and the order of the modules to implement.
Setup records
Each tax rule with an owner, review date and change history.
Evidence per scenario
Source document, expected value and obtained value, kept and repeatable.
Cycle record
What changed, who decided and what proved the result, at each governance cycle.
The first four deliverables
- The scenario matrix for your operation, with the documents that will be tested.
- The first assessment run in SAP and checked against the value you assess today.
- The list of explained differences, with the cause of each one.
- The plan for the first close with GUEPARDO, with an owner per step.
The scope of each module outside tax is agreed case by case with NTT DATA, and the timeline of each phase depends on the environment.
Start with the Tax Diagnostic and learn what your environment needs before deciding.
What risks does each type of tax solution hide, and what to ask for in the contract?
Each type of tax solution has a structural risk that the commercial proposal does not show, and a contract clause that reveals it before signing.
Every type of solution has a risk that the commercial proposal does not show. Each structural risk has a clause that reveals it before signing.
Native SAP
Risks:
- Legal change arrives through Notes and support packages, and someone must apply and test each one.
- After a Support Package or Feature Package Stack, SAP maintains a note (KBA 2516353) on Brazil localization objects that may be missing or have incorrect customizing.
Ask in writing for:
- A tax test plan for each SAP update.
- A list of the Notes applied and the date of each one.
Third-party add-on
Risks:
- SAP says to check the compatibility of third-party add-ons at conversion to S/4HANA, and the Readiness Check only lists them.
- The legislation update follows the supplier's cycle, which the client does not control.
Ask in writing for:
- A compatibility window with your release and the next one.
- The update deadline after a layout change.
- Access to old versions for the legal period.
External platform
Risks:
- The interface with SAP must be revalidated at each release.
- Tax data leaves SAP, and traceability goes through two systems.
- Art. 11 of Law 8.218/1991 requires digital files and systems to be kept available to the Federal Revenue Service for the statute of limitations period.
Ask in writing for:
- Access to the system and the data for the legal period, even after the contract.
- Form and deadline for data exit at the end of the relationship.
In-house ABAP
Risks:
- Maintaining the legislation is entirely the company's, at each layout. The EFD ICMS/IPI Practical Guide is already at version 3.2.4.
- SAP states that custom code must be adapted in S/4HANA and that ABAP Cloud has released APIs only from release 2022.
- Knowledge stays concentrated in a few people.
Ask in writing for:
- Documentation, versioning and repeatable tests for each program.
- A second owner for each obligation.
For any type, art. 12 of Law 8.218/1991 provides a fine for improper submission of files and for incorrect information. The reading of the retention period is your company's and your legal team's.
Request the Tax Diagnostic and take these clauses to your environment before signing.
What doubts block the decision on the tax solution for SAP?
Doubts about cost, risk, dependence, ECC, team and timeline are the ones that block the decision most, and all of them have a direct answer.
How much does it cost?
The right cost is measured whole: license, implementation, support and the rework of each close and each change in the law. The Tax Diagnostic puts the numbers for your scenario on the table before any decision.
And the risk of implementing?
Implementation does not start in production: it starts with a scenario of yours, run in a test environment, with the expected value next to the obtained one. DFSpro only moves forward when the result matches, and the risk sits in the proof, not in go-live.
Will I depend on one supplier?
You swap several contracts for one product family maintained by NTT DATA, with DFSpro implementing and governing. NTT DATA maintains the product, and DFSpro maintains the evidence for each scenario implemented.
I am on ECC: do I wait for S/4HANA?
Mainstream maintenance of ECC runs until 31/12/2027 and CBS starts in 2027. Deciding only after the migration tightens the tax solution calendar. DFSpro designs the implementation with the conversion already in mind.
Can my internal team handle it?
It can decide the tax treatment and validate the results. The repetitive work of assessment, validation and files leaves the spreadsheet, and DFSpro takes on design, configuration and proof.
And the timeline?
The reform calendar is fixed: 2027 does not negotiate. The question is how much of the following year you want to spend on rework. The Tax Diagnostic defines the first deliverable, checked against the current assessment.
Do I need to contract everything at once?
No. GUEPARDO is a family of modules, and the choice starts with what hurts most. The tool Which module to choose helps put them in order, and the Tax Diagnostic confirms the order.
Does GUEPARDO replace what SAP already does?
No. NTT DATA describes Tax as an add-on that complements the assessments in the standard menu. What SAP does well stays where it is, and the module covers what is missing.
I already have an add-on from another supplier.
The Tax Diagnostic maps what each tool covers today, compares it with your operation and proves a scenario in GUEPARDO before any switch. The migration can be gradual, by obligation.
Will the IT team be overloaded?
The e-Invoicing cloud is managed by the NTT DATA team, and the link to SAP uses RFC. DFSpro does the design, configuration and proof, and IT validates access and the environment.
What questions to ask a tax solution supplier for SAP?
Twenty-five questions, in six groups, cover what to demand in writing from any tax solution supplier for SAP.
Demand a written answer to each question from any supplier, including GUEPARDO.
| Criterion | Questions to demand in writing |
|---|---|
| Coverage and scope |
|
| Updates and legislation |
|
| Integration and migration |
|
| Audit and record keeping |
|
| Implementation and support |
|
| The 2027 reform |
|
Want to see how GUEPARDO answers these in your environment?
Where to check the deadlines and rules cited?
The dates and rules cited come from laws, a constitutional amendment and SAP documentation.
SAP
Frequently asked questions about choosing the tax solution
Deciding on the solution7 questions, 01 to 07
01What is a tax solution for SAP?+
It is the set of software and processes that handles tax assessment, bookkeeping, SPED, ancillary obligations and the issuing and receiving of NF-e inside or beside SAP. It can be a native solution, a third-party tax add-on, an external platform or in-house ABAP.
02What is the difference between a native solution, a tax add-on and an external platform?+
The native solution comes from SAP itself, with scope that varies by product and by release. The tax add-on runs inside SAP and uses the ERP's data. The external platform runs outside SAP and connects by interface. In-house ABAP is code written by the company for each obligation.
03What is the best tax solution for those who use SAP?+
For a company with SAP as its main ERP, that needs assessment, SPED, electronic documents, foreign trade and analytics in the same environment, the best choice is GUEPARDO. It runs as an add-on inside SAP, NTT DATA holds it and DFSpro, an Authorized Channel, implements and governs it.
04Why GUEPARDO and not the tax that already comes with SAP?+
The SAP standard is the base, and scope varies by product and by release. GUEPARDO complements the assessments in the standard menu, according to NTT DATA, and brings together assessment, SPED, documents and foreign trade in one environment.
05External platform or add-on inside SAP: which pays off more?+
The external platform serves those who operate several ERPs well. Those with SAP at the center get more from the add-on: the data stays in the ERP and NTT DATA describes Tax operating on a single database in federal assessment.
06When does in-house ABAP stop paying off?+
It can, but each change in the law becomes a project, the code depends on who wrote it and S/4HANA requires adapting what was simplified. With GUEPARDO, the product is maintained by NTT DATA, and your team takes care of the business.
07In one sentence, which path is worth more for my SAP?+
Each type of solution has its place. For those with SAP as the main ERP, the add-on inside SAP meets more criteria, with GUEPARDO as the best choice within it.
Calendar and reform4 questions, 08 to 11
08When does CBS start being charged?+
The ADCT sets 2026 as a test year, with CBS at 0.9% and IBS at 0.1%, and CBS starts being charged from 2027, with IBS at 0.05% state plus 0.05% municipal in 2027 and 2028. DFSpro keeps its own Tax Reform manual and proves each scenario in your environment.
09Since when does the national NFS-e apply to cities?+
LC 214/2025, art. 62, requires cities and the Federal District, since 01/01/2026, to authorize the national-standard NFS-e or share the documents of their own issuer with the national environment. e-Invoicing automates the issuing and receiving of electronic documents, according to NTT DATA.
10I am on ECC: should I wait for S/4HANA to choose?+
No. Mainstream maintenance of ECC runs until 31/12/2027, the same year CBS starts. Deciding the tax solution together with the migration route avoids paying twice, and DFSpro designs both with the conversion already in mind.
11How do I protect myself in an audit?+
By keeping digital files available to the Federal Revenue Service, as Law 8.218/1991 requires, and by finding the discrepancy before submission. NTT DATA describes pre-validation in Tax, cross-checking of information in Audit and a data history for audits at the state level.
Product and modules4 questions, 12 to 15
12Which obligations does GUEPARDO Tax cover?+
According to the NTT DATA overview, ICMS and IPI assessment with Block K, PIS and COFINS, ISS, IRPJ and CSLL, EFD, EFD Contributions, ECD, ECF, EFD-Reinf, DCTF, DIRF, CIAP, GNRE Online, PER/DCOMP and REINTEGRA, at the three levels of government.
13How do electronic documents get into SAP?+
Through e-Invoicing, which captures NF-e and CT-e from SEFAZ and NFS-e from city halls by web service, plus e-mail with PDF reading, a supplier portal and API. A monitor in SAP processes each purchase scenario, according to NTT DATA.
14Does GUEPARDO serve foreign trade?+
Yes, through Global Trade, developed by Conexos and offered in partnership with NTT DATA. The platform controls imports and exports end to end and integrates the information with the ERP.
15Does GUEPARDO also handle collections and cash?+
NTT DATA offers Payments, with Pix and boleto, Cash Application and Credit & Collections, the last two from Serrala. DFSpro works on the tax modules, and the choice of the others goes through Which module to choose.
Implementation and contracting4 questions, 16 to 19
16How long does it take to see the first result?+
The timeline depends on the scope and the environment, which is why the Tax Diagnostic comes first and defines the first deliverable, checked against the assessment SAP already does. NTT DATA describes Tax as an add-on installed in SAP, not as an external platform.
17Who supports GUEPARDO after implementation?+
NTT DATA answers for the product and DFSpro supports the environment in AMS Fiscal, with a demonstrated cause and a test that proves the result of each incident. Implementation and governance in your SAP stay with DFSpro.
18What does my team need to do in the implementation?+
Decide the tax treatment and validate the results. Design, configuration and proof by scenario stay with DFSpro, and the tax position remains your company's.
19How do I start?+
Request the Tax Diagnostic, or assess the readiness of your SAP in two minutes. If you already know the pain, the page Which module to choose points to the first GUEPARDO module to contract.
Reach 2027 with the right tax solution in SAP: start with the Tax Diagnostic
DFSpro shows what your environment needs and which GUEPARDO module solves it first. We build and test the system to act the way your company decided, and the tax decision is always yours.
Also: which module to choose and talk to a specialist.