Spend Visibility & KPI Reconciliation

The Problem

The company had four major systems handling spend data: JDE for enterprise operations, SAP for some procurement, Anaplan for financial planning, and Salesforce for supplier relationships. Each system calculated spend differently. Finance ran one number to the CFO. Procurement ran another to their leadership. These numbers never matched. Millions of dollars worth of confusion. Executive dashboards showed conflicting data, and reporting cycles took days because finance and procurement would argue over whose number was right before presenting to leadership.

What I Built

I started with root cause analysis, tracing the discrepancies back through the data flows. The problem wasn't one system being wrong, it was four systems defining spend differently. Same transaction, counted multiple ways depending on which ledger you were looking at. Built a reconciliation logic layer that spoke to all four systems simultaneously, and a data integration that mapped each system's spend definitions to a unified taxonomy. Then built automated reconciliation routines that surfaced conflicts in real time so they could be resolved immediately instead of discovered weeks later during reporting.

The Impact

Resolved the KPI conflict. From that point forward, one number that finance and procurement both trusted. Executive visibility was restored and reporting time dropped from days to hours. More importantly, the company could finally manage spend strategically. Decisions that used to be delayed by data debates got made immediately.

My Role

Data reconciliation lead. Root cause analysis, system mapping, reconciliation logic design, data integration, ongoing automation and monitoring.

Built With

• JDE
• SAP
• Anaplan
• Salesforce
• Celonis