Financial Statistics Database and Reporting Project

Richard BarrProject Manager20 January 2011

Existing Reports

• The 3 Reports being discussed are complementary

• Each address a different but very important and critical information need for stakeholders

• OECD – what’s happening with all ODA?• DESA – What’s the UN doing for Development?• CEB – What’s happening at the UN?

Are we answering those questions?

• OECD Report - 147 pages• CEB Report – 107 pages• DESA Report - 61 pages

• Lots of data but what about information?• The “one page” Manager• “3 clicks” or you are “out”!

Challenge of classification

• To consolidate across entities, need common classification “systems”

• UNDP budget sub-categories (6)• ACC Programme categories (20 ~ 100)• FB Network – 2010 (8)• New initiative (UNDP, UNICEF, UNFPA) ?

Other common issues / themes

• Ease of data collection • As a consolidated source of information, what

is the correct level of granularity?• How do we make the data more user-friendly?• Who are the target audiences?• How much analysis should be provided?• How to make use of IT tools?

HLCM view

• Across the UN system, donors (and others) want a view of what is being “raised” and what is being spent

• Donors also want to know what we are doing with the funds

• “Value for money” audits, RBB and RBM systems in vogue but not well understood – long on theory, short on practical solutions

Financial Statistics Database and Reporting Project

Background

• Plan of Action for the Harmonization of Business Practices in the UN system, endorsed by HLCM

• Managed by the CEB Secretariat• One of 2 “first” projects from the FB Network• Highly visible, lots of possibilities to “stumble”• UN system-wide Financial Statistics• Target completion date: June 2012

Project objectives• Integrate existing databases• Eliminate data collection overlaps• Strengthen consistency of data collection• Enhance data analysis• On-line system for collection and reporting• Provide timely consolidated financial data, analysis

and reports for the various stakeholders• Make the data fully “public”

Project milestones

• March 2011 – Issue identification• June 2011 – Design specifications complete• September 2011 – HLCM approval• December 2011 – IT solution in place• June 2012 – project complete

• Thank you

• Questions / comments?