I recently took some time to look into the Google Analytics for our blogs and noticed this blog post on Payments-on-behalf-of (POBO) and Collections-on-behalf-of (COBO) is getting a lot of traffic. I think this is because companies are increasingly focusing on harmonising their banking landscape to obtain better visibility of cash balances, to mitigate fraud risks and to improve automation and security in their treasury processes.
In a world where the next fraud attempt is lurking around every corner, no company wants to create processes with different banks, tokens, and user lists for each of their different local entities. With this harmonisation, companies start to rethink their processes and this naturally leads to in-house banking, including POBO and COBO. This is because the question soon arises as to why, for example, not all euro payments should be handled from one account, if that were possible within the regulatory context.
Setting up an in-house bank doesnâ€™t happen overnight. Itâ€™s the result of several steps taken to centralise an organisationâ€™s cash management. The six steps are:
Today I would like to focus on POBO and COBO. POBO and COBO are the ultimate goals of a payments project because they create transparency and make cash management processes more efficient and automated. This sounds great, right? So why, then, arenâ€™t all organisations just setting up POBO and COBO and calling it a day?
Moving from disparate processes, tools and a varied (if you want to be positive) banking landscape to a centralised treasury doesnâ€™t happen easily. Companies might even feel hesitant about implementing on-behalf-of structures because their set-ups are too complicated. Thatâ€™s an interesting point and Iâ€™d like to stress that the more complex a company is in its cash management or enterprise resource planning (ERP) structures, the more they will benefit from an on-behalf-of set-up.
Increased control, transparency and efficiency
In the POBO model, the subsidiaries process the payment data in their systems according to internally harmonised processes, and the group treasury decides on the most cost-efficient payment method and banking connection. The group treasury is able to centralise cash outflows, which significantly enhances the safety of and control over the payment process.
COBO and POBO make it possible for the group to reach the highest level of independence from banks and maximise cost efficiency.
The benefits of POBO and COBO can be summarised into increased control, transparency, and efficiency. But there are also challenges associated with on-behalf-of structures that need to be evaluated before setting them up.
Where thereâ€™s a benefit thereâ€™s a challenge
POBO is possible for most payment types, but some are regulated in such a way that they cannot be completed by the on-behalf-of method. This is often related to tax or salary payments. Legal restrictions specific to each country can make it difficult to set up POBO and companies need to assess whether the benefits they will gain are worth the effort. There is no one true answer for all companies; it really depends on the level of complexity they are facing.
Another reason why companies might feel hesitant about implementing POBO is because they use multiple ERP systems. If that is the case, the mere idea of POBO is simply far too complicated. To be honest, when I hear that â€˜excuseâ€™ I see it as a challenge and it makes me happy. Because this then means I can talk about payment factories â€“especially our payment factory solution. We can create a process that makes it possible for all entities to pay with internal bank accounts as payments-on-behalf-of. Iâ€™d even go so far as to say that the more ERP systems a company has, the more benefits it will get from POBO.
When it comes to COBO, the main challenge is that companies are dependent on their buyers to know what to collect from whom. Companies need to retrieve all accounts receivable (AR) information and maintain an overall view of account balances. In some countries that might be relatively easy, as invoices generally have a reference number. But thatâ€™s not the case in all countries. It comes back to identifying incoming payments correctly. For example, this can be achieved by matching payments to open invoices. A solution for automatic bank account reconciliation would be able to automatically match incoming payments based on information provided, for example in the message to the right AR account. My colleague took a closer look at the topic in this blog post about how an in-house bank with modern matching solves the COBO challenge.
That said, of course, itâ€™s not an easy task to create on-behalf-of structures, but itâ€™s something that organisations will greatly benefit from if done correctly. If you are interested, please join us in our upcoming webinar on 19 May where we will take a closer look at this topic with our partner Engima.