CATHAGO Analytics — Order / Delivery / Invoice as distinct € layers

Concept prototype · two real customers · why one "Total Spend" number can't serve both · live prod aggregates (all-time)

Procurement reconciliation funnel

Each layer is a real € value built from existing line-item data (Ordered / Delivered priced & quantified, Invoiced from invoice line items). Bars scaled to this customer's largest layer.

Today vs. the concept

Today the dashboard shows a single invoice-based "Total Spend". That number is meaningful for an invoice-led customer and near-useless for an order-led one.

Today — one number
Concept — three layers
ORDERED
DELIVERED
INVOICED

Project coverage & invoice–PO matching

Project-level analysis (must-have) + the "invoices without PO" flag — both computable from data that exists today.