View full content seriesHow payment technology could close the loop on the virtual CFO model
byIn the last of his three-part series on accounting tech trends, Ben Smith looks at how emerging payment execution technology could close the loop on the virtual CFO model and wraps up his series with examples of the things an ambitious practice could be doing in 12 months’ time.
Not everybody wants to build a virtual CFO (VCFO) practice, but there is an established direction of travel away from compliance services and towards an advisory model. By 2019 you and your clients are going to have more options to execute payments than you do today.
You, or your client, will no longer need to create 12 (or however many employees) different internet banking payments to process the monthly payroll (which is only a problem if your bank doesn’t provide that anyway). You’ll be able to execute one-off or scheduled BACS payments, individually or in bulk, instantly reacting to cash flow management demands, and you won’t even need to access the bank account to do it.
This is about closing the loop on the VCFO model, where you, as the accountant, can provide a truly outsourced finance function, including the management of cash, payments and cash flow.
We’ve seen a few innovations in the accounts receivable space (GoCardless being a prominent example), but the innovations on accounts payable have largely been the preserve of enterprise-facing technology suppliers, not SME vendors. We’re going to see at least two models come to market in the next 12-18 months.
Two-way bank feeds: Cloud accounting vendors will overlay existing bank feeds with multi-directional data flows. This will take a while to complete, and you’ll have the situation emerge where you can execute a payment within one package via one bank, but not with another. It will happen though. I suspect that we’ll start to see these opportunities to execute payments take the form of a practitioner-side interface too.
Middleware products: In the meantime, we’ll see the emergence of middleware products that won’t rely on bank feeds being in place. You’ll be able to link multiple accounting software products into this middleware interface and execute payments from relevant linked bank accounts. It’ll be clunky at first, with the potential for some required prepayments in the early iterations, but this will improve quickly.
In either case, there are going to be all kinds of issues around the equivalent of agent access, and you’ll probably see your institutes and the ICO scramble to provide guidance on this area. But if you think about the practical application of this technology, it’s really aiming to solve some of the most difficult-to-shift administration burdens affecting small businesses:
It’ll take a fraction of the time it previously took to actually make payroll payments
You’ll be able to bulk-pay multiple suppliers via one interface without setting up individual payments each time
I suspect the vendors in this space will take a little longer to gain traction compared to their accounts-payable counterparts. After all, you’re more likely to invest in tools that help you get money into the business than tools that help you move it out again. The progressive firms that really want to be the pro-advisor will see the opportunity this proposition presents for true market differentiation.
Wrapping it all together
That’s it for my three-part series. If you haven’t read the pieces on the platform vs suite debate and why banks want to be accountants’ best friends, you can find them here.
To wrap up this reckless speculation, and perhaps extrapolate things even further, let’s imagine a scenario where your bank, accounting software and practice tools are all connected via either a platform or a suite/workspace - with HMRC and Companies House APIs aligned too.
Your practice management tool will recognise that client ‘A’ is due to complete a quarterly MTDfB update
You push the data from the accounting software into your MTD tax tool to compute the liability
Your workflow then notifies the client what they have to pay, and asks them to authorise you to make that payment via the two-way bank feed in the accounting package
You execute the payment, which is validated back into the practice management tool, which then checks in with the HMRC API to validate that the right payment has been calculated, paid and accepted
Your practice tool then tells your client they’re MTD compliant for this accounting period
There are *lot* of things that have to happen to get to this point, but you can see how this, at least conceptually, may work in the future.
These are the things we may well be talking about in 12 months’ time though. How much progress each area actually makes in that time remains to be seen - but it’s something we’ll be keeping a close eye on at AccountingWEB in the months to come.