# Building an Executive KPI Dashboard for Your Custom ERP

> How to design and build a real-time executive KPI dashboard in a custom ERP — choosing the right metrics, data architecture, visualization, and performance optimization.

URL: https://www.matthewswong.com/en/blog/erp-kpi-dashboard-executives/

- Author: Matthews Wong (https://www.matthewswong.com/en/about/)
- Published: 2025-06-10
- Updated: 2025-06-10
- Category: ERP

Businesses leveraging real-time KPIs in their ERP environment have a competitive advantage through the ability to see, understand, and act on data in real time. For executive teams at Indonesian companies, the ERP dashboard is often the most visible deliverable of the entire ERP project — the one thing the CEO looks at every morning. Getting it right means choosing the right metrics (not every metric), designing for speed, and making it actionable rather than just informational. In my freelance ERP consulting work, I've built executive dashboards for manufacturing, trading, and services companies. This post covers what works.

## Choosing the Right KPIs

The most common mistake in executive dashboards is showing too many metrics. An executive dashboard should have 8-12 KPIs maximum — the ones that reflect business health and enable decisions. For a trading company in Indonesia, the core KPIs are: Revenue (current month vs. target, vs. same month last year), Gross Margin %, AR Days Outstanding (DSO), AP Days Outstanding (DPO), Inventory Turnover, Cash Position (current bank balance by account), Open Orders (unshipped orders by value), and Overdue Invoices (by count and value). Each of these tells a story — together they give the CEO a complete business health picture in 30 seconds.

### The Dashboard Data Model

For performance, executive dashboards should not query raw transaction tables directly. I pre-compute a daily_kpi_snapshot table that stores the key metric values as of each business day. A NestJS cron job runs at 1 AM WIB nightly and populates this table with yesterday's closing values. The dashboard then queries the snapshot table — a simple SELECT with no joins — returning in milliseconds. For real-time metrics (current cash position, today's orders), I allow direct queries but optimize them with materialized views refreshed every 15 minutes.

> From my experience building ERP systems as a freelance ERP consultant: always show the metric, the target, and the trend together. A revenue number means nothing without context. '₹2.4B revenue this month' tells you nothing. 'Rp 2.4B vs. Rp 3B target (80%) — down 12% vs. same month last year' enables a decision. Design every KPI card with: current value, target or benchmark, variance (absolute and %), and a sparkline showing the last 12 months. This 'metric with context' format is what makes dashboards actionable rather than decorative.

## Dashboard Architecture and Performance

The dashboard API returns all 12 KPIs in a single endpoint call — not 12 separate API calls. I batch the KPI computation and return a single JSON payload. This reduces the number of round-trips and prevents the 'waterfall loading' effect where each card pops in at a different time. For the front end, I use React Query with a 15-minute staleTime so the dashboard doesn't refetch on every navigation — the executive isn't going to get new information in 15 minutes, and unnecessary queries put load on the database.

### Drill-Down from KPI to Transactions

Every KPI card should be clickable and drill down to the underlying transactions. Click on 'Overdue Invoices: 23' and you get a list of 23 invoices with customer name, amount, days overdue, and the AR owner. Click on 'Inventory Turnover: 4.2x' and you see turnover by product category for the last 12 months. This drill-down capability is what separates a useful dashboard from a vanity screen. The drill-down views use standard paginated list endpoints — no special optimization needed since they're used on-demand, not on every page load.

> **Warning: Metric Definition Disagreements**

> Different stakeholders often define the same KPI differently. 'Revenue' might mean gross sales to the sales director and net-of-returns to the CFO. 'DSO' might be calculated on billing date or delivery date. Before building the dashboard, document the exact formula for each KPI, have the CFO and business owner sign off on it, and display the formula definition in the dashboard tooltip. I've had two situations where executives disputed the dashboard numbers because they were mentally calculating differently. The solution is not better data — it's explicit formula documentation.

## How I Approached This

The dashboard backend I built is a NestJS DashboardModule with a single KpiService. The service orchestrates queries across FinanceService, InventoryService, ARService, and APService, assembles the KPI payload, and caches it in Redis with a 15-minute TTL. The front end is a React dashboard using Recharts for sparklines and KPI cards built with a shared component pattern. I use CSS variables for theming — the same dashboard component renders in dark and light mode depending on the user preference.

## Mobile Dashboard for Executives

Indonesian executives are mobile-first. The CEO reviews the dashboard on their phone while traveling between meetings. I built a mobile-optimized dashboard view that collapses the 12 KPIs to the 5 most critical, shows large numbers with minimal labels, and uses green/amber/red color coding for instant status. The mobile view is a separate React route with a breakpoint at 768px. I also built a WhatsApp bot that sends a daily KPI summary at 7 AM — the CEO's favorite feature, because they get the numbers before they arrive at the office.

## Alerting and Exception Management

A dashboard is reactive — the executive sees it when they look. Alerts are proactive. I added threshold-based alerts: if AR DSO exceeds 60 days, email the CFO. If cash position drops below a configured minimum, WhatsApp the director. If overdue invoices exceed Rp 500M, SMS the collections manager. These alerts run as NestJS cron jobs that check the KPI values daily and send notifications when thresholds are breached. The thresholds are configurable by the admin — no code deployment needed to adjust alert sensitivity.

## Sources & Further Reading

- Versa Cloud ERP — Real-Time KPIs in ERP: Powering Growth in 2025 — https://www.versaclouderp.com/blog/erp-without-insight-is-just-software-why-real-time-kpis-define-growth-in-2025/
- Sysgenpro — Best ERP Analytics Dashboard Setup for Executive Leadership Teams — https://sysgenpro.com/resources/erp-analytics-dashboard-setup-for-executive-leadership-teams-in-2026
- CoderRapper — ERP KPIs: The Most Critical Metrics to Track in 2025 — https://coderapper.com/article/erp%E2%80%91supply%E2%80%91chain/top-erp-kpis-to-measure/

> **Key takeaway:** An executive KPI dashboard is often the only part of the ERP leadership actually opens, which makes the choice of metrics the whole design. Deriving each number from live transactions rather than a nightly export is what lets a decision be made on it the same day.

## Source links

- https://www.versaclouderp.com/blog/erp-without-insight-is-just-software-why-real-time-kpis-define-growth-in-2025/
- https://coderapper.com/article/erp%E2%80%91supply%E2%80%91chain/top-erp-kpis-to-measure/

## FAQ

### How many KPIs should an executive ERP dashboard display?

An executive dashboard should have 8–12 KPIs maximum — enough to reflect overall business health and enable decisions without overwhelming the viewer. Showing too many metrics is the most common mistake. For a trading company, core KPIs include revenue vs. target, gross margin %, DSO, DPO, inventory turnover, cash position, open orders, and overdue invoices.

### Why shouldn't the dashboard query raw transaction tables directly?

Querying raw transaction tables on every page load is too slow for an executive dashboard that needs to return results in milliseconds. Instead, a daily_kpi_snapshot table is pre-computed nightly by a NestJS cron job at 1 AM WIB, storing closing values for each business day. The dashboard then runs a simple SELECT with no joins against this snapshot table, while truly real-time metrics like cash position use materialized views refreshed every 15 minutes.

### What information should each KPI card display to be actionable?

A number alone is never enough context for a decision. Each KPI card should show the current value, the target or benchmark, the variance (both absolute and percentage), and a sparkline covering the last 12 months. For example, 'Rp 2.4B vs. Rp 3B target (80%) — down 12% vs. same month last year' enables a decision, whereas a bare revenue figure does not.

### How are metric definition disagreements handled before building the dashboard?

Different stakeholders often define the same KPI differently — for instance, 'revenue' might mean gross sales to the sales director and net-of-returns to the CFO. The solution is to document the exact formula for every KPI before building, get sign-off from the CFO and business owner, and display the formula definition in the dashboard tooltip. This explicit documentation — not better data — resolves disputes when executives calculate numbers differently.

### How does the mobile dashboard and alerting work for Indonesian executives?

Indonesian executives are mobile-first, so a separate mobile route collapses the full 12 KPIs down to the 5 most critical, uses large numbers with minimal labels, and applies green/amber/red color coding for instant status. A WhatsApp bot delivers a daily KPI summary at 7 AM before executives arrive at the office. Threshold-based alerts — configured by an admin without code deployment — send email, WhatsApp, or SMS notifications when KPIs breach defined limits, such as AR DSO exceeding 60 days or overdue invoices surpassing Rp 500M.

---

- HTML version: https://www.matthewswong.com/en/blog/erp-kpi-dashboard-executives/
- Bahasa Indonesia: https://www.matthewswong.com/id/blog/erp-kpi-dashboard-executives/
- Site index for agents: https://www.matthewswong.com/llms.txt
- Sitemap: https://www.matthewswong.com/sitemap.xml
- API description (OpenAPI): https://www.matthewswong.com/openapi.json