HDbeammachineBeam Machine Docs
Help Center

Reviewing the Tax Risk Heatmap

How to interpret the Beam Machine tax risk heatmap, including the current score bands, trend indicators, and the limits of this review-only workspace.

publicusers

Reviewing the Tax Risk Heatmap

This page shows you how to read the Beam Machine tax risk heatmap and, just as importantly, what this screen is not doing for you yet.

Product: Beam Machine
Module: Tax -> Tax Risk Heatmap
Role: Tax Manager, Finance Lead, Reviewer, Risk Owner
Difficulty: Intermediate
Time: 6 minutes
Last Updated: 2026-03-10
Version: Current Beam Machine app build in this repo

Before You Start

  • You need access to Tax.
  • Risk scores must already exist in the system, otherwise the page will be empty.
  • This is a review dashboard. Do not come here expecting to file, close, or resolve tax obligations directly.

What is the tax risk heatmap?

This screen is the BM tax risk dashboard. It takes risk scores already stored in the system and turns them into a simple heatmap-style review list.

In plain English, it helps you answer:

  • which entity looks most exposed,
  • which tax type looks most exposed,
  • and whether the position is improving or getting worse

When do you use this?

Use this page during tax governance reviews, month-end risk checks, internal controls reviews, or before a meeting where somebody will ask, "What is the worst tax fire right now?"

If you ignore risk scoring until a filing deadline, you usually find the problem after the penalty, not before it.

Where to find it

Primary path: Finance -> Tax -> Tax Risk Heatmap
Route: /dashboard/tax/risk-heatmap

How to review the heatmap

  1. Open Tax.
  2. Click Tax Risk Heatmap.
  3. Review the summary cards:
    • Total Scores
    • Critical
    • High
    • Medium
    • Low
  4. Move to the Risk Scores table.
  5. Review each row in this order:
    • Entity
    • Tax Type
    • Risk Score
    • Risk Level
    • Trend
    • Period
  6. Prioritize anything marked critical or high.
  7. Escalate deteriorating items before the next filing cycle, not after it.

āœ… Checkpoint: You should now know which items need management attention first.

How BM currently assigns risk bands

In the current build, BM derives the risk label from the stored numeric score:

  • 0 to 24 = low
  • 25 to 49 = medium
  • 50 to 74 = high
  • 75 and above = critical

Trend is shown visually:

  • upward marker = worse
  • sideways marker = roughly stable
  • downward marker = lower risk

What this screen does not currently expose

  • No visible score-entry form exists on this route.
  • No visible remediation workflow exists on this route.
  • No visible document pack or issue-assignment workflow exists on this route.

So: this page is for review and escalation, not for doing the whole fix on-screen.

Common Questions & Issues

"The page is empty"

Why this happens: No tax risk scores have been calculated or loaded for the current entity yet.

Fix: Treat that as "no data", not "no risk". Confirm how your team is populating risk scores in your environment.

"The entity names are not obvious"

Why this happens: The table currently shows shortened entity identifiers rather than friendly entity names.

Fix: Cross-check the entity in your normal BM entity context before escalating the wrong item.

"Can I resolve the issue from this page?"

Why this happens: The dashboard looks operational, but it is not a case-management screen.

Fix: Use this page to prioritize action, then move to the supporting workflow outside this route.

What's Next

Related Pages

SA Compliance Reference

  • Risk dashboards support governance. They do not replace the real filing, record retention, dispute, or sign-off obligations under South African tax law.
  • Use this screen to focus effort earlier, not to claim that a risk has been resolved.

Still Stuck?

  • If the screen is empty, find out how risk scores are being populated in your environment.
  • If the screen is populated, escalate high and critical items with evidence and owner assignment outside this route.
  • Contact support: support@veva.co.za

Was this page helpful?

[Yes] [No]