1. XBRL GL Overview The HUD/FHA Pilot Gianluca GarbellottoDynAccSys San Jose, CA January 18 th 2006

2. Agenda  XBRL GL, The Journal Taxonomy  XBRL GL and XBRL FR  The HUD/FHA Pilot  Resources

3. Scope and role of XBRL External Busines s Reportin g Business Operations Internal Busine ss Reporti ng Investme nt, Lending, Regulatio n Processes Participants Auditors Trading Partners Investors Financial Publishers and Data Aggregators Regulators Software Vendors Management Accountants Companies Economic Policymak ing Central Banks XBRL GL, the Journal Taxonomy XBRL “Financial Reporting”

4. Standard Payload: XBRL GL Can Represent 1. Trigger: a source document is represented electronically 2. Source Journal The document is entered and posted, creating a source journal. 3. Journal entries: The accounting implications are gathered and prepared for the GL. 4. GL Entries: the journal entries are prepared for posting to the GL. 5. Journal History: The entries are posted to the Journal History. 6. Consolidation: The data at journal entry or trial balance level are brought together. 7. Reporting: Consolidated numbers combine for eventual reporting. Posting Journal Invoice Distribution To GL Report Source Journal General Journal Transaction Posting Journal History Report Consolidating/ Consolidated

5. Journal Entries Sub Ledgers Business Activity Transaction Detail XBRL GL And XBRL FR Source Systems Internal Reporting Pipeline Reporting Accounts Payable Accounts Receivable Order Entries Purchasing Fixed Assets Human Resource Payroll Late Entries Adjustments Manual Entries General Ledger Source Documents Regulatory Reporting Tax Business Activity Management Benchmark & Analysis Annual(Quarte rly) Reporting Financial Systems Manual Transaction Business Events Aggregation Consolidation Journalize Financial Data Mart/ Repository Financial Reporting Decision Support Extract & Transform Monitor, Audit & Control Budgeting & Forcasting xbrlInfo xbrlInclude summaryReportingElement

6. The Story at HUD/FHA  DynAccSys hosts one of the many legacy systems that are part of HUD/FHA’s information system: a loan and property administration system that manages AP and AR related to loan servicing, rents, expenses related to property maintenance, tax payments and fees.  In the current architecture, a data warehouse collects legacy data and feeds them to the main general ledger.  The data warehouse has two functions:  Converting entries from MSA to SGL format  Maintain the detail information: the main GL only stores summary information

7. The Story at HUD/FHA The use of XBRL GL will: 1.Streamline the process. 2.Eliminate the need for manual data integration 3.Eliminate time consuming reconciliation 4.Enhance the reusability of the same information across different systems and processes.

8. Budget Reporting Business Analysis Performance INTERFACE PeopleSoft Audit Data Warehouse Translates MSA GL account format to US SGL Monthly Feed MLS AP/AR PMS AP/AR CSMS System of Record Rekey data for other uses Challenge: Consistent, timely, complete and accurate data Summary data out of balance with transaction detail Journal detail data Ongoing reconciliation US SGL Summary Entries The Problem… INTERFACE

9. Budget Reporting Business Analysis Performance Next Things MAPPING TO XBRL GL PeopleSoft Audit Daily Feed MLS AP/AR PMS AP/AR CSMS System of Record …The Solution MAPPING TO XBRL GL

10. The Solution Benefits for HUD: Avoid data manipulation at HUD Reduce processing time. Re-use of data in other systems or analytical tools without further intervention. Reduced reconciliation time. This will also enable HUD to adhere to the Presidents Management Agenda (PMA) regarding Performance Improvement and Budget.

11. Using XBRL as a data standard and XABRA as the tool to implement it will enable HUD to achieve:  Implementation of daily cash reporting features  Simplify financial reporting to its core financial system, PeopleSoft  Gain interoperability between systems and data reusability through standardization. XBRL GL

12. 1.Meet downstream information and reporting requirements with transaction processing data linked to transaction engines 2.Accept standard information integration and electronic data to and from other internal, government-wide, or private-sector processing environments 3.“One-time” data entry and reuse of transaction data to support downstream integration, interfacing, or business and reporting requirements 4.Be modular in design and built with reusability as an objective What will be achieved

13. Resources  What’s available to review  XBRL GL 2005, an XBRL 2.1-compliant taxonomy  Where to find it  www.xbrl.org/GLFiles www.xbrl.org/GLFiles  Additional resources  GaLaPaGoS – GL Practices Guide for Study http://gl.iphix.net http://gl.iphix.net  Questions? xbrlgl@xbrl.orgxbrlgl@xbrl.org

14. Contact Information Eric E. Cohen XBRL Global Technical Leader, PwC eric.e.cohen@us.pwc.com Gianluca Garbellotto XBRL Business Manager, DynAccSys XBRL GL Working Group ggarbellotto@dynaccsys.com