A (UK) Pensions Data Format Standard - let's make it happen!

I have long thought it would be useful for there to be a standard format for exchange of data files for DB (Defined Benefit, i.e. final salary or career average revalued) pension plans, at least in the UK initially.

This would make it easier for pension plans to share information (with actuarial consultants, but also other advisers e.g. buyout companies, investment analysts), not just in mergers and acquisitions, but also in risk transfers (longevity, or pensions buyouts) and would improve the comparability of analysis across companies by investors etc.  It should also reduce costs for trustees and plan sponsors, and may increase the quality of the data held.

I think this both with my InQA hat on (I declare an interest in that our pensionsconcerto.com product would be well placed to use such a standard), but also from the point of view of being an improvement for the pensions industry generally.  Investment banks have standard formats for exchange of information about derivatives contracts, but as far as I know there is nothing comparable in the UK pensions industry.

I have an initial template in mind as a suggested standard, which could be refined/improved as necessary following discussion with relevant parties. I have several organisations in mind and am about to open a dialogue with them to see if we can make this idea a reality, for the good of the industry as a whole. 

Comments and dialogue most welcome.

(Posted by Patrick Lee on 8 August 2017).

Comments

  1. pjlee0111 August 2017 at 01:13

    I'm exploring whether XBRL (eXtensible Business Reporting Language, see https://www.xbrl.org/) would be an appropriate (or perhaps even the best current) format for a standard in this area. Moving company reporting to XBRL has saved Australian businesses and government $1.1 billion annually and it is estimated that the US could save $11 billion if they adopted a common XBRL standard for their various different types of company reporting. Savings in the defined benefit area would be smaller, but would still be sizeable, and of course there would be transparency and comparability gains too.

    ReplyDelete
  2. Patrick Lee15 August 2017 at 14:07

    You can now see Part 2 in this series here.

    ReplyDelete

Post a Comment

Popular posts from this blog

Migrating to the cloud (Microsoft Azure and Office 365)

Image
( This article was first posted on 22 Apr 2016 on a different blog site, but migrated here 06 May 2017 ). I thought I'd share a few thoughts from our experience of moving from Windows servers on which both our corporate and client websites and email were stored to the cloud, specifically Office 365 and Microsoft Azure. ​ The process itself was relatively painless (particularly for migrating email to Office 365).  The only problems we experienced were in migrating some older websites, and some webbased software which, for reasons best known to its manufacturer (whose blushes I will spare by not naming here), needed to be installed as a desktop program (albeit one with a web interface).  Both of these needed to be installed on a virtual machine (a windows server within the cloud) rather than as stand alone web apps (or app services as they are now known) in Azure.  We also had a few teething problems moving some databases from SQL Server...
Read more

Creating a corporate dashboard (using OData and Microsoft PowerBI)

Image
Building a corporate dashboard so that you have key management information at a glance I have recently been building some corporate dashboards (as recommended by Daniel Priestley in his best selling book "24 Assets: Create a digital, scalable, valuable and fun business that will thrive in a fast changing world").  From chapter 15 of the book: A key asset is a dashboard that allows the team to see how the business is performing.  Carefully select some of the metrics that drive performance and make sure they show up prominently on your dashboard.  You might select metrics like cash at bank, payments collected, expected invoices, revenue per employee or monthly users; the general rule is that whatever you measure will improve.
Read more