Pular para o conteúdo
Dashboards and indicators · Tax in SAP

Tax dashboards in SAP: the dashboard of the tax area, with numbers that match the tax assessment

A tax dashboard is one screen that shows whether the tax area is healthy and what needs attention today, without opening one report at a time. Here are 26 indicators to discuss, each with a question, data source, owner, frequency, alert and action, plus three tools that run in your browser.

This page is for people outside IT and for the SAP team. Your company chooses the indicators and the limits. DFSpro designs the indicators and the quality of the data that feeds them, and proves that the number matches the tax assessment and the SPED file.

Versão em português
Index

Start with the question of your role

Five entry points to the same dashboard: each role has a different question about it, and its entry point leads straight to the section that answers it.

01Tax management

Which few numbers show whether the month is under control, and who answers for each one.

See the section for this role

02Controllership

Which indicator shows the gap between the tax assessment and the accounting before it becomes a problem.

See the section for this role

03Tax operations

Which exception queue the dashboard opens each morning: rejected invoice, master data, withholding.

See the section for this role

04SAP and IT team

Where each indicator comes from, in how many layers, and how the data reaches the dashboard.

See the section for this role

05Audit

How to prove that the dashboard number is the tax assessment number, and who maintains the definition.

See the section for this role
Shortcuts
The short answer

A tax dashboard replaces five reports with a few indicators, and it only pays off if each number has an owner and proof

The direct answer

A tax dashboard gathers, on one screen, the indicators that show whether invoices, tax assessment, credits, filings, withholdings and master data are in order. It does not assess or transmit anything. It shows where to look first. What gives the dashboard its value is that each indicator has a question, a source, an owner, an alert limit and an action, and that the number matches the tax assessment.

What the dashboard does

It brings scattered signals together and shows what drifted from the expected, so the team can act before the close.

What the dashboard does not do

It does not replace the tax assessment, the file or the tax decision. A green dashboard over bad master data misleads.

What DFSpro proves

Where each number comes from, that it matches the tax assessment and the SPED file, and that the alert fires when it should.

NTT DATA's dashboard product has its own page: see GUEPARDO Analytics. Here the subject is the tax dashboard as a method, whatever the tool.

What it is, what it is for and when it is not worth it

Think of a car dashboard: speed, fuel and a warning light, without opening the hood

In a traditional close, someone checks several reports and spreadsheets to find out whether the month is fine. The dashboard shows the few signals that matter and lights up what needs attention.

Before: checking one by one

Invoice report, tax assessment report, books, a withholding spreadsheet and the to-do list. The person who knows where to look becomes a bottleneck.

After: reading what lit up

One screen per role. The indicator outside its limit shows the owner and the action, and the conversation starts at the problem.

What changes in the day

The error shows up when it happens, not on the day of transmission. The close stops being a hunt for problems.

When it is not worth it

When master data is still disorganized, the reconciliation only happens at year end, or nobody wants to own the numbers. In those cases the dashboard shows the noise on a nice screen. Data cleanup and a reconciliation routine come first, covered in tax master data and tax and accounting reconciliation.

Tool 1

Which tax indicators do I need

Choose your role, the filings that weigh on your operation and its size. The list of indicators changes right away, and each one leads to its row in the catalog.

This tool needs JavaScript. Without it, the catalog just below lists all the indicators with the role of each one.

Guidance, not a decision. The list is a starting point from DFSpro. Which indicators your company adopts is your decision, and your choices stay in the browser only, with nothing sent to a server.

Your role
Filings that weigh on you (optional)
Size of the operation

Suggested indicators

Choose your role to see the list.

Dashboard example

Six indicators on one screen, each with a status, owner and action

The drawing below is only an illustration of how the information is organized. The numbers are made up to show the format, and none comes from a real company. This site does not store or show client data.

Illustrative example, no real dataTax view

Open rejected invoices

07 invoices

Action

Owner: Tax. Open the rejection queue and handle the cause.

Difference between assessment and ledger

0 differences

Within the limit

Owner: Controllership. Nothing to do this month.

Materials without a valid NCM

15 materials

Attention

Owner: Master data. Complete before the next order.

Filings of the month with a receipt

3 of 5

Attention

Owner: Tax management. Call whoever answers for the remaining two.

Validator errors

0 errors

Within the limit

Owner: Tax and IT. Attach the report to the close.

Withholdings payable

4 slips

Within the limit

Owner: Accounts payable. Check the slips on the eve.

The status is written out, and color alone never carries the meaning. Each tile says who answers and what to do.

How to read it

A tile in attention or action status leads to the list behind it. The words within the limit only hold when the owner has already approved the limit and the test against the tax assessment has passed.

Public dashboard and internal dashboard

A deadline dashboard with public data already works, and the internal dashboard uses the company's own data

To see a deadline dashboard working with public data, open the tax deadline dashboard and the tax calendar. They show the format, and they do not replace the dashboard your company will read over its own data.

Point of comparisonPublic deadline dashboardCompany internal dashboard
Data usedDates, deadlines and rules published by official bodies.The company's own invoices, tax assessment, credits and withholdings.
Where it livesOn an open page of the site, for any visitor.In SAP, in the company's BI or in the GUEPARDO Analytics the company has contracted.
Who sees itAnyone.Only whoever the company authorizes.
What it answersWhen each filing is due.How the company's tax area is doing today and what needs action.
What DFSpro doesShows the format of a deadline dashboard with public data.Designs the indicators and the data quality, and proves that the number matches the tax assessment and the SPED file.
Your company's data

This site does not receive, store or show client data. The screen of the internal dashboard lives where your company decides, and its data stays with it.

Three layers of dashboard

SAP dashboard, analytics layer and product module are different paths

Many conversations mix the three. The screen can live in SAP, in your company's BI or in GUEPARDO Analytics, and the choice depends on where your data is, who will use it and what the company already has.

SAP's own dashboard

Fiori analytical apps, such as indicator tiles in the Launchpad, overview pages and analytical lists. SAP describes these features in training material (read on 19/10/2026). In our assessment, they fit best the daily routine of the SAP user.

Limit: Each client has the catalog and the version it has: the list of tax apps available for Brazil must be checked in your system.

Analytics layer over the tax data

An analysis tool that reads data from SAP and other systems, such as SAP Analytics Cloud, or a market tool of your standard. In our assessment, it fits best for crossing tax with accounting, sales and logistics, and for showing a trend over several months.

Limit: The SAP source describes SAP Analytics Cloud as a cloud service for analysis, with live or copied data (search of 19/10/2026, page not opened in the body). What is contracted and how it is connected is your company's decision.

GUEPARDO Analytics module

A product from NTT DATA, which DFSpro sells as an Authorized Channel. What it delivers, for whom and with what data is on its own page. Here it appears as one of the options, without repeating the product.

Limit: Product facts only as NTT DATA describes them, and they stay on the dedicated page.

Official source and limit

SAP source: SAP Learning training material on embedded analytics in S/4HANA, read on 19/10/2026, which mentions analytical pages, indicator tiles in the Launchpad and overview pages. The part about SAP Analytics Cloud comes from a search result of the same date, without opening the page. Confirm the version of your system and the list of tax apps for Brazil in your version.

The data that must exist first

A nice dashboard over bad data misleads

The dashboard is the last layer. If the data below it is inconsistent, the indicator shows the inconsistency with an appearance of precision.

Quality master data

A material without an NCM and a partner without a registration become exceptions every day. The dashboard only repeats the noise, louder.

Decided tax determination

If the calculation rule changes without a record, the indicator swings and nobody knows whether the problem is the business or the setup.

Reconciliation as a routine

The difference indicator is useless if the reconciliation only exists at year end. The routine comes before the screen.

Electronic documents with a trail

Status, rejection reason and event time must be stored so the dashboard can tell the full story.

Written definitions

If two areas count invoices differently, both dashboards will be true and disagree.

Tax determination and calculation are in tax assessment in SAP, and the master data rules are in tax setup.

Indicator design and governance

Data at the base, processing in the middle, screen on top and an owner for each number

The layered design separates where the data comes from, where it is processed and where it appears. Governance says who answers for each number and what happens when something changes.

  1. 01

    Definition owner

    Each indicator has a business owner, who approves what counts, what does not count and the limit. IT builds, the owner answers.

  2. 02

    Definition version

    Each change of formula or limit gets a version, a date and who approved it. Without a version, the historical series misleads.

  3. 03

    What changes with the law

    A change in legislation or layout enters the review queue of the affected indicators, together with the SAP setup.

  4. 04

    Who reads the dashboard

    Whoever sees numbers by establishment, by tax and by partner needs an access profile that is decided and reviewed, including by data protection.

Proof of the number

Five tests to check whether the dashboard tells the truth

DFSpro test script, valid for any tool. To assess NTT DATA's dashboard product, see the page GUEPARDO Analytics.

  1. 01

    Trace a number to the document

    Choose an indicator and go down from the dashboard number to the tax document behind it, step by step.

    Evidence kept: A walkthrough from number to document, signed by the owner.

  2. 02

    Compare with the tax assessment

    Compare the value of the tax indicator with the assessment result of the same period, tax by tax.

    Evidence kept: Comparison spreadsheet with the difference, or proof that it is zero.

  3. 03

    Compare with the delivered file

    Compare the dashboard totals with the totals of the file that was transmitted to the authority.

    Evidence kept: Totals side by side and the delivery receipt.

  4. 04

    Force an alert case

    In a test environment, create a rejected invoice or a material without an NCM and watch the alert fire.

    Evidence kept: Screenshot of the alert, the time and the action it triggered.

  5. 05

    Repeat after a change

    After a rule or layout change, repeat the script on the affected indicators.

    Evidence kept: Result of the retest, attached to the change.

What the test requires on the file side is in filings and SPED, and the test plan is in tax testing.

Common mistakes

Eight ways to build a dashboard that nobody defends

Too many indicators

Forty indicators on the same dashboard and no owner. Start with the core marked in the catalog and grow only with demand from those who use it.

Dashboard without action

The alert fires and nobody knows what to do. Each indicator in the catalog brings the action, and the dashboard must show it.

Number of unknown origin

The value appears, but nobody knows which table, filter or cutoff date it came from. Record the source together with the definition.

Limit chosen by IT

IT guesses a limit so the screen looks nice. The limit is the decision of the indicator owner.

Manual spreadsheet copy

A spreadsheet feeds the dashboard and someone forgets to update it. Prefer a single point of data.

Dashboard that ignores the change in law

The indicator keeps the old definition after a rule change. Every legal change goes through a review of the definitions.

Mixing data from different periods

One indicator uses the issue date and another the posting date, and the two disagree. Decide and write down the cutoff date.

Delivering the screen and forgetting the test

The screen is delivered without a comparison with the tax assessment. The first wrong number discredits the whole dashboard.

Tool 3

Data readiness checklist for a tax dashboard

Check what your company already does today. The score updates with each mark. No answer is stored, and reloading the page starts over from zero.

This tool needs JavaScript to count. Without it, the items below serve as a meeting agenda.

12 readiness items

Status

0 of 12 items ready

What to do first

    Guidance, not a decision. This list is not an audit and certifies nothing. Saying what is ready is up to your company.

    DFSpro's role

    From the core indicators to the evidence, in five steps

    As a specialist in tax in SAP and in GUEPARDO Tax, DFSpro designs, on the tax dashboard, the indicators and the quality of the data that feeds them, and proves the number against the tax assessment and the SPED file. The choice of what to measure belongs to the client.

    1. 01

      Choosing the core

      Together with the tax area and controllership, we choose the few indicators that answer the questions that hurt most at the close.

    2. 02

      Definition and owner

      Each indicator gets a written definition, a source at process level, a named owner and a proposed limit, which the owner approves.

    3. 03

      Layered design

      We design where the data comes from, where it is processed and where it appears, in the tool your company chooses.

    4. 04

      Proof against the tax assessment

      We compare each dashboard number with the tax assessment and with the delivered file, and we keep the evidence.

    5. 05

      Governance and review

      We leave the change rule written down: who reviews, when and with what test.

    Limit of our role

    Who chooses what to measure, and who decides

    Limit of our role

    The indicators, the alert limits and what each number means for the business are your company's decision. No indicator here interprets the law for you. DFSpro designs, configures and proves the behavior of the system, and the tax position stays with whoever answers for it. This page is knowledge content: it is not a hosted dashboard and does not show client data.

    Sources

    Who published each piece of information, and when

    Confirm in your operation

    Which tax Fiori apps exist in your version and your catalog. Which tables or views each indicator comes from. What GUEPARDO Analytics delivers beyond what its own page says. The content of SAP Analytics Cloud in the client's version. The search demand for this topic. The alert limits in the catalog are a starting point and were not measured in any operation.

    Frequently asked questions

    Frequently asked questions about tax dashboards in SAP

    01What is a tax dashboard, in one sentence?+

    It is a single screen that shows, with a few indicators, whether the tax area is healthy and what needs attention today, instead of forcing people to open several reports and spreadsheets. Each indicator answers a question from everyday tax work.

    02How much does it cost to design and prove the indicators of a tax dashboard?+

    There is no single figure, and DFSpro does not publish prices. The cost depends on how many indicators are included, where the data comes from, the tool chosen and the effort to clean up master data. In general, the work on the data weighs more than the screen design. Ask for a proposal with the scope of the core indicators; the screen itself depends on the tool your company uses.

    03Is it worth it for a small company?+

    It is worth it when the tax close takes a lot of time or when errors arrive late. For a lean operation, start with the core marked in the catalog and a weekly review routine. A dashboard with dozens of indicators in a small operation tends to become a cost with no use.

    04Do I need SAP S/4HANA to have a tax dashboard?+

    Not necessarily. What matters is having tax data that is organized and accessible. The Fiori analytical features, described by SAP in training material, belong to S/4HANA, but it is also possible to build the analytics layer outside SAP. What holds for your version must be checked in your environment.

    05What is the difference between the SAP dashboard, BI and GUEPARDO Analytics?+

    The SAP dashboard is the feature inside the system itself. BI is an analysis tool that reads SAP and other data. GUEPARDO Analytics is a module of NTT DATA's product, described on its own page on this site. They are different paths, and the choice is your company's.

    06Does a tax dashboard replace SPED or the tax assessment?+

    No. The dashboard shows, it does not assess and does not transmit. The tax assessment and the files are still produced in your processes. The dashboard helps you see errors early, and does not change the obligation.

    07How long does it take to have the first dashboard working?+

    We do not promise an average time. What sets the time is the quality of the master data, the availability of the owners and the tool. A small core, with data already organized, moves faster than a broad dashboard over dirty data.

    08How do I know whether the dashboard number is right?+

    By comparing it with the tax assessment of the same period, with the delivered file and with the source document, and keeping the result. The proof section of this page gives the script, and the GUEPARDO Analytics page gives the test from the point of view of whoever is evaluating the product.

    09Who should own each indicator?+

    Whoever answers for the result that the indicator measures, usually someone from the tax area or controllership. IT builds and maintains the data, but does not decide what the number means or the alert limit.

    10How many indicators does a tax dashboard need?+

    Fewer than you might think. The catalog on this page has 26, and the marked core has ten. Start with the core, prove each number and grow with real use, instead of turning everything on at once.

    11Does the dashboard help with the tax reform?+

    It can help track the transition, for example documents with the new fields and operations without an approved classification. The classification of operations and the tax position are the client's decision. What changes in the layout follows what the authority publishes.

    12Can the dashboard connect to tools we already use, such as Power BI?+

    In general, yes, as long as the tax data can be extracted with quality and access is decided. The tool is your company's choice, and DFSpro designs and proves the path of the data.

    13What are the risks of a poorly built tax dashboard?+

    Deciding with a wrong number, exposing data to people who should not see it and creating false confidence because the dashboard is green while the master data is bad. Proof against the tax assessment and access control reduce these risks.

    14Does DFSpro decide which indicators to use?+

    No. Your company chooses. DFSpro suggests a core to start with and proves the behavior of the system. The choice of indicators, the limits and any tax position belong to your company.

    Next steps

    Tell us which tax number you most wanted to see without opening a report

    The conversation starts from the question that costs the most time in your close, and from there come the core indicators, the owner of each one and the proof against the tax assessment.

    Also read: tax assessment, tax and accounting reconciliation, filings and SAP TDF.