Your ERP has the data. Why does Monday morning still start in Excel?

The weekly spreadsheet starts as an export. Someone adds promised dates, checks a shortage list, asks production about three jobs and highlights the rows for the morning meeting.

The workbook may be doing useful work. Before replacing it with a dashboard, identify what that person contributes. Some of the value comes from joining records. Some comes from applying judgment that the ERP does not capture.

Ask what the spreadsheet is deciding

“An order report” is a broad requirement. “Which orders need intervention today to ship this month?” is a decision people can test.

Write down the audience, the action and the timing. A purchasing view may need to identify a missing component and its supplier commitment. A shipping view may need to distinguish a finished part from an order released for dispatch. An executive summary needs to show the financial effect without losing the route to those details.

Agree the definitions before the chart

Consider a single order with an original promise date, a revised customer date and a planned dispatch date. It can be late against one and on track against another. A dashboard that shows only “late” hides the disagreement rather than resolving it.

Measure	Definition to agree
Backorder	Which due date is used, and are partially shipped lines included?
At-risk shipment value	What evidence makes a scheduled line at risk?
Open RFQ value	Is the amount indicative, quoted, weighted or already converted?
Invoice aging	Is age measured from invoice date or payment due date?

Keep the definition, owner and refresh time available beside the measure. A useful number needs enough context for someone to challenge it.

Connect the records without multiplying the value

An order line might have several operations, shortage records and shipment events. Joining those tables carelessly can repeat the same order value several times.

Define the level of each dataset first: order, line, operation, shipment or invoice. Reconcile a small set of known examples before trusting a total. Decide how partial shipments, credits and multiple constraints should appear.

The reporting question also affects the connection. Microsoft’s Business Central reporting documentation describes using available APIs or published web services for Power BI. That is one product-specific route, not a universal prescription for every Dynamics edition or ERP installation. Confirm the supported interface and access model for the actual system.

Preserve judgment explicitly

If an experienced planner knows that a shortage will be resolved by Thursday, capture the status, source and date of that judgment. Do not silently overwrite the source record or present an assumption as a confirmed supplier commitment.

A report can show both the system schedule and the accountable person’s assessment. That is often more useful than pretending the data is complete.

Start with an exception list

A first improvement could be a short list of affected orders, values, constraints, owners and next actions. It does not need to replace every workbook or display every ERP field.

Our executive dashboard demonstration uses fictional records to show that investigation path. Its numbers are examples, not evidence of a deployed customer integration.

If Monday morning depends on somebody reconstructing the same picture, tell us which decision the report needs to support. That is a better starting point than choosing a chart type.