Summitview Studio

Live demo · Power BI rescue

Sales said $13.0M.
Finance said $12.6M.
Both were right.

Harborline Components is a fictional $17M industrial distributor with the most common reporting problem there is: three revenue numbers that never matched, so every meeting started with an argument. Below is the dashboard after the model was rebuilt — every figure on this page comes from one definition of revenue. Change the filters; it's live.

⚠︎ Fictional company · synthetic data generated by Summitview · no client data
Jan–Aug 2026 vs Jan–Aug 2025 · net revenue by invoice date

Trend

Net revenue by month

Net revenue = invoiced minus credits and returns, by invoice month.

20262025

Margin

Gross margin by category

Gross margin %, Jan–Aug, this year against last.

20262025

Operations

On-time delivery by region

Share of order lines invoiced within the 14-day promise, 2026. Target 90%.

At or above targetBelow target

Customers

Top 10 customers

Ranked by net revenue, Jan–Aug 2026.

The fix

Why Harborline had three revenue numbers — and why none of them was wrong.

Each report measured something real, and every one of them called it “Revenue.” Sales summed orders on the day they were booked. Billing summed invoices before returns. Finance netted out credits. Nobody was lying; the model just never said which number was the official one. The fix wasn't a new chart — it was one definition in the model, with the other two renamed for what they actually are.

Before

Eleven tables, three measures called “Revenue”

Exports joined to exports, many-to-many relationships, and each report page with its own formula.

After

One fact table, three dimensions, one definition

A star schema. The date table relates to sales twice: invoice date is active and drives the official revenue; order date stays inactive and is switched on only for the pipeline view.

Company-wide figures, Jan–Aug 2026 — these three are not affected by the filters above.

Take it with you

Build it yourself in Power BI.

The same dataset, as a clean star schema, with the DAX measures that make the three numbers agree. Load it into Power BI Desktop and you'll have this model in about ten minutes.

  • Fact_SalesLine — 13,000+ order lines, Jan 2025 → Aug 2026
  • Dim_Customer, Dim_Product, Dim_Date
  • measures.dax — net revenue, margin, YoY, on-time, and the two “other” revenues, named honestly
  • Free to use. Fictional data, no strings.