{"id":21136,"date":"2022-08-25T08:08:56","date_gmt":"2022-08-25T07:08:56","guid":{"rendered":"https:\/\/www.argonandco.com\/?post_type=article&p=21136"},"modified":"2022-08-25T08:08:56","modified_gmt":"2022-08-25T07:08:56","slug":"your-p2p-health-is-more-than-just-dpo","status":"publish","type":"article","link":"https:\/\/www.argonandco.com\/en\/news-insights\/articles\/your-p2p-health-is-more-than-just-dpo\/","title":{"rendered":"Your P2P health is more than just DPO"},"content":{"rendered":"

Measuring Days Payable Outstanding (DPO) does not allow effective performance steering of a Procure to Pay (P2P) process.<\/h3>\n

We are all told that an effective P2P process has a healthy DPO measure \u2013 but what is healthy?<\/p>\n

If DPO is high, then cashflow is strong, but vendors are constantly chasing their money, too low and cash leaves the business faster than it\u2019s coming in, how do we find the proverbial \u2018just right\u2019?<\/p>\n

The answer lies in the detail, DPO is an Inside Out, Lag measure (i.e. it measures your own performance, in the past), it is good for your own confirmation bias and broadly summarises past performance, but it is useless for steering the activity of today and tomorrow.<\/p>\n

DPO is calculated as: ( Average Accounts payable \/ COGS ) x # days in the accounting period.<\/strong><\/p>\n

For example: If the output of this calculation returns a DPO of 40 days for one period and then 41, or 39 days for the next, does this really mean things have got better or worse? We know that the real process heartbeat exists in the detail \u2013 and knowing that, how could you possibly steer your business on DPO?<\/p>\n

You may be able to take some high level decisions based on DPO \u2013 you could aim to increase your AP, or you could decrease COGS (both increasing DPO) \u2013 however neither decision explicitly connects to the process intention \u2013 to deliver products or services to your organisation and then make the subsequent payment.<\/p>\n

By steering on DPO, you are not seeing the live performance or variability within the P2P process, and it is this variability that causes your vendors (and therefore you) pain.<\/p>\n

If you felt sick and went to the doctor, you would be surprised if they assessed your current symptoms by referring to data they gathered three months ago. They may use your historical blood pressure\/weight\/o2 levels to understand your general health, but they would take todays readings, and use this live data to steer you towards becoming healthy again.<\/p>\n

A P2P process is no different, a process heartbeat needs to be established, this should be real time (i.e. happening now), reportable and reflective of the process health.<\/p>\n

Taking an Outside In view<\/strong><\/p>\n

How about if we took a look at this process from an Outside In perspective? Vendors want to be paid for each of their goods\/services supplied, On Time.<\/p>\n

Therefore, if you were able to measure On Time Payment at an order level, and zoom into individual events that contributed to poor process performance (that will almost certainly not show in an aggregated DPO measure), in real time, without the need for hours of ad-hoc data extraction and analysis,\u00a0why wouldn\u2019t you?<\/em><\/p>\n

If you could also then model this improvement into future process performance,\u00a0why wouldn\u2019t you?<\/em><\/p>\n

If you could visualise the pain of variability that poor process performance causes your vendors and then systematically eradicate that variability to make the pain less,\u00a0why wouldn\u2019t you?<\/em><\/p>\n

There are three broad areas that should be in scope to assess your P2P performance: The efficacy, productivity, and capability to mitigate risk.<\/p>\n

\"\"<\/p>\n

Within these categories the actual measures will likely include<\/p>\n