Make the plant margin report show decisions rather than conflicting totals

Why the plant head's KPI dashboard and the controller's margin pack disagree at month-end

When Indian factory leaders search for a manufacturing KPI dashboard or redesign their monthly plant profitability report, they rarely suffer from a shortage of charts. Existing industry examples—such as Jobpack's operational manufacturing KPI dashboards tied to machine and scheduling data, SimpleKPI's manufacturing dashboard layout for volume, defects and unit costs, MachineMetrics' shop-floor KPI reporting guide and User Solutions' overview of manufacturing standard costing—already demonstrate visual layouts and standard-cost formulas.

The operational breakdown happens in the monthly management review meeting when two dashboards built from the same factory floor present irreconcilable headline numbers:

1. Mismatched completion and cutoff boundaries: The plant head's production KPI dashboard counts every unit that finishes the final CNC operation before 23:59 IST on the last day of the month, multiplying total machined units by standard unit contribution. By contrast, financial revenue recognition under MCA Ind AS 115 (Revenue from Contracts with Customers, official PDF indexed by MCA) depends on satisfying performance obligations and transferring control under the customer contract—not universally on a gate pass, invoice or QC status alone. Where a plant's approved accounting policy and customer delivery terms require final quality release and completed dispatch/invoicing before control transfers, machined lots still in QC hold or sitting on the dispatch floor at cutoff remain in inventory rather than current-period revenue.
2. Unaligned OEE Quality denominators and rework treatment: Shop-floor screens often compute a raw-piece quality ratio by dividing all non-scrapped pieces by total machine cycles—treating units routed to secondary rework or awaiting inspection at shift close as "good output"—whereas standard OEE methodology (OEE.com on calculating OEE, S12) defines the Quality factor strictly as first-pass good units that meet specification without rework (Good Count / Total Count), weighted by ideal cycle time when multiple products share a cell.
3. Unsupported vendor billing overcharges mixed with legitimate accruals and price variances: At month-end, finance must accrue legitimate received-not-invoiced (RNV) liabilities under applicable accounting policy. However, if a preliminary draft extract also sweeps in an erroneous, duplicate or unsupported vendor overcharge that is sitting in an ERP invoice-matching discrepancy queue (Microsoft Dynamics 365 accounts payable invoice matching, S18), lumping that unverified overcharge into factory conversion cost distorts operational margin for reasons the production manager cannot control.

Make the plant margin report show decisions rather than conflicting totals — reporting workflow

Follow the workflow below, or open its complete text version.

Read the complete workflow as text

1. Lock period cutoff timestamp and physical lot status → Bridge gross machined cycles to inspected and invoiced units
2. Bridge gross machined cycles to inspected and invoiced units → Deduct verified first-pass scrap, rework and tooling variances
3. Deduct verified first-pass scrap, rework and tooling variances → Separate 3-way matched vendor costs from disputed AP holds
4. Separate 3-way matched vendor costs from disputed AP holds → Publish reconciled margin pack with owner action queue

Define a joint operating-and-financial metric contract before building dashboard tiles

Before connecting BI tools to ERP and MES tables, the plant head and finance controller should sign off a joint internal management-reporting contract (kept distinct from statutory general-ledger disclosures). Every headline tile on the manufacturing KPI dashboard should declare its exact numerator, denominator, cutoff rule, authoritative owner, and the reconciliation bridge bucket where timing or discrepancy items are explained:

As documented in OEE.com's calculation standard (S12), OEE is an operational effectiveness diagnostic rather than a financial accounting target; combining multi-product cells requires weighting each part family by its own validated ideal cycle time (see our companion guide on calculating OEE across products with different ideal cycle times) rather than averaging raw piece counts. Similarly, Microsoft's accounts payable invoice matching documentation (S18) describes operational software controls for flagging PO, receipt and invoice discrepancies—not statutory authority for revenue or accrual recognition. An ERP three-way-match hold by itself never justifies omitting a valid liability for goods or services actually received; rather, the matching hold triggers an independent controller review to separate legitimate received-not-invoiced accruals from erroneous vendor overbillings.

Worked example: reconciling a ₹5,55,000 month-end gap at a precision-machining plant (PUN-MACH-02)

Scope note: All part numbers, unit volumes, cycle times, rupee totals and document references below are purely synthetic illustrative data created to demonstrate an internal operating-to-financial management bridge. They do not represent a client facility or statutory financial statement. In this synthetic scenario, assume the Finance Controller has approved the applicable accounting policy under MCA Ind AS 115 and verified that contractual transfer-of-control evidence coincides with the 4,000 invoiced and dispatched units at cutoff (a gate pass or invoice alone does not establish statutory revenue recognition across all contract types).

Consider the September close (Period 2026-09, cutoff 30 Sep 2026 23:59 IST) for synthetic plant PUN-MACH-02, which machines two cast-iron product families across 60 shifts (28,800 minutes of planned production time):

• Pump Housing (PH-200): Net selling price ₹2,500 / unit; standard variable cost ₹1,700 / unit; standard contribution ₹800 / unit (32.00%); validated ideal cycle time 5.50 minutes / unit.
• Valve Body (VB-150): Net selling price ₹2,000 / unit; standard variable cost ₹1,450 / unit; standard contribution ₹550 / unit (27.50%); validated ideal cycle time 5.00 minutes / unit.

Why the two initial reports conflicted by ₹5,55,000

On 02 Oct 2026, the Plant Head's unadjusted manufacturing KPI dashboard and the Controller's preliminary draft extract showed two incompatible stories:

1. Plant Head's unadjusted KPI dashboard (₹30,15,000 projected contribution; 78.80% headline OEE):
   • Cell counters recorded 4,300 machined castings (2,600 PH-200 and 1,700 VB-150) across 25,200 minutes of run time (Availability = 25,200 / 28,800 = 87.50%; ideal standard time = (2,600 × 5.50) + (1,700 × 5.00) = 14,300 + 8,500 = 22,800.0 minutes; Performance = 22,800.0 / 25,200.0 = 90.48%).
   • Because the shop screen computed an unweighted raw-piece quality ratio that only deducted 20 outright scrapped castings (4,280 / 4,300 = 99.53% raw-piece quality), it displayed 78.80% OEE and multiplied all 4,300 machined castings by standard contribution: (2,600 × ₹800) + (1,700 × ₹550) = ₹20,80,000 + ₹9,35,000 = ₹30,15,000.
2. Finance Controller's preliminary draft extract (₹24,60,000 draft contribution, or -₹5,55,000 lower):
   • Under the plant's approved revenue policy and verified transfer-of-control evidence, Finance recognised 4,000 invoiced and dispatched units (2,500 PH-200 for ₹62,50,000 and 1,500 VB-150 for ₹30,00,000, totalling ₹92,50,000 recognised revenue and ₹28,25,000 standard contribution).
   • The preliminary extract then deducted ₹1,45,000 of shop scrap, rework and tooling variances plus an unreviewed ₹2,20,000 preliminary accrual for heat-treatment vendor invoice INV-HT-884, pulling draft contribution down to ₹24,60,000 (26.59%).

The three-part reconciliation bridge

Applying the joint metric contract reconciles both numbers to an agreed management contribution total of ₹25,95,000 (28.05% of ₹92,50,000 recognised revenue) and a verified First-Pass OEE of 75.87%:

Every operational and financial figure now cross-checks without hidden plugs:

• Unit & inventory cutoff reconciliation (4,300 machined vs 4,000 recognised): The 300-unit difference (₹1,90,000 standard contribution) is accounted for physical lot by physical lot: 100 PH-200 in QC hold (₹1,70,000 blocked WIP), 120 VB-150 in unrestricted finished goods where control had not yet transferred at cutoff (₹1,74,000 FG stock), 60 VB-150 in rework (RW-0930, costing ₹36,000 to restore to good stock), and 20 VB-150 scrapped (₹29,000 written off to scrap variance).
• First-Pass OEE reconciliation (78.80% unadjusted vs 75.87% verified): Whereas the initial shop-floor screen used an unweighted raw-piece quality ratio (4,280 / 4,300 = 99.53%), removing the 80 failed/reworked VB-150 castings and the 100 uninspected PH-200 castings leaves 4,120 verified First-Pass Good units (2,500 PH-200 × 5.50 min = 13,750.0 min plus 1,620 VB-150 × 5.00 min = 8,100.0 min, totalling 21,850.0 good standard minutes out of 22,800.0 total standard minutes). That yields a cycle-time-weighted First-Pass Quality factor of 95.83% (21,850.0 / 22,800.0 = 95.8333%), and an unrounded verified First-Pass OEE of 75.87% (21,850.0 / 28,800.0 = 75.868%, or 87.50% Availability × 90.48% Performance × 95.83% Cycle-Weighted Quality), linking the ₹36,000 rework and ₹29,000 scrap charges directly to the OEE Quality loss on the dashboard.
• Controller review of AP matching exceptions (₹2,20,000 preliminary accrual vs ₹85,000 verified surcharge + ₹1,35,000 reversed overcharge): An ERP three-way match hold (S18) is a discrepancy control, not an automatic rule to drop valid accruals. Here, the Finance Controller independently examined PO-4410, goods receipt GRN-0928 and the vendor bill INV-HT-884, confirming that ₹85,000 was a valid alloy surcharge on received castings (retained in September cost of sales alongside all legitimate received-not-invoiced accruals), whereas ₹1,35,000 was an erroneous rate overcharge and duplicate freight claim with no contractual or receipt basis. The Controller therefore approved reversing the ₹1,35,000 error from the preliminary ₹24,60,000 draft and tracking the vendor dispute note separately. For related sub-ledger controls, see how we reconcile job-cost imports with independent source totals, prepare a receivables review queue from current invoice balances and govern item masters so duplicate parts do not break factory planning.

Run a one-close reconciliation pilot before automating executive BI tiles

To eliminate conflicting month-end packs without a multi-month data-warehouse project, run this bounded check on your most recent monthly close:

1. Freeze one shared cutoff timestamp (23:59 IST on close day): Extract the exact lot list sitting between the final machine operation, QC inspection and dispatch at cutoff so both operations and finance reconcile unshipped and QC-held unit counts against the company's approved Ind AS 115 revenue-recognition policy.
2. Split variance lines by accountable owner: Separate shop-floor yield, scrap and tooling usage variances (owned by production and toolroom leads) from purchase-price and subcontracting variances (owned by purchasing), and ensure the Finance Controller reviews open three-way match holds (S18) to separate valid received-not-invoiced accruals from unsupported billing errors.
3. Require every KPI red flag to carry a transaction reference: Whether a variance stems from a tapping-head rework order (RW-0930), a stores insert issue (#912) or a disputed vendor invoice (INV-HT-884), require the dashboard drill-through to show the exact document ID and owner due date.