What Portfolio-Wide AP Reporting Should Show

1. Cycle time by company: speed from receipt to approval and payment. 2. Cost per invoice by company: efficiency of each operation. 3. Exception rate by company: process and data quality. 4. Aging by company: timeliness and overdue risk. 5. Electronic payment rate: modernization of payments. 6. Cash measures: discount capture and days payable outstanding. 7. Outliers and trends: who leads, who lags, and the direction.

The core of portfolio-wide reporting is the same metric set for every company, presented side by side and rolled up to a total. Cycle time, cost per invoice, exception rate, aging, electronic payment rate, discount capture, and days payable outstanding, shown per company, let leadership compare operations directly. The portfolio total gives the aggregate view.

This comparison is the whole point. Seeing that one company processes invoices in days while another takes weeks, or that one has a high exception rate while others do not, is what turns reporting into a tool for action. The view exists to surface those differences, not just to display each company's numbers.

Beyond the raw metrics, the view should make outliers obvious. A company with a much higher cost per invoice, a longer cycle time, or a higher exception rate is a candidate for improvement, and the portfolio view should make those stand out rather than burying them in a list. Outliers are where value-creation opportunities usually sit.

Control adherence belongs in the view too. Showing whether each company is operating the expected controls, consistent approvals, segregation of duties, clean reconciliation, lets portfolio leadership confirm that control standards hold everywhere, not just on average. A company that lags on controls is a risk the portfolio view should surface.

Comparability is the requirement that makes everything else work. If cycle time or cost per invoice is defined differently at each company, the numbers cannot be compared, and the portfolio view shows noise. Standardizing the definitions across companies is what makes the comparison meaningful, so the same metric means the same thing everywhere.

The cash measures deserve care. Discount capture and days payable outstanding should both appear, and they should be read together, since paying early to capture discounts and extending terms to hold cash pull in opposite directions. A portfolio view that shows DPO without discount capture, or the reverse, can give a misleading picture of a company's cash posture.

Stampli gives centralized, real-time visibility across entities, so portfolio leadership can see each company's AP process in one place rather than collecting reports separately. Because each company runs the same workflow on one platform, the underlying operational data is consistent rather than assembled by hand from different systems.

That consistency is what makes the metrics comparable across the portfolio. The same measures, defined the same way, apply at each company even when the ERPs differ, so cross-company comparison and roll-up reflect real differences rather than definitional noise. Outliers and aging are visible in the operational view.

Because every action is captured in an immutable audit trail and each ERP remains the system of record for the financials, the operational reporting rests on a traceable process and authoritative numbers. Stampli supports the cross-company operational picture, while each ERP holds the financial figures the cash measures draw on.