XBRL GL OverviewThe HUD/FHA Pilot

International Consortium on Governmental Financial Management

February 1, 2006

Gianluca Garbellotto · DynAccSys

XBRL GL Working Group

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

Scope and role of XBRL

ExternalBusinessReporting

BusinessOperations

InternalBusinessReporting

Investment,Lending,

RegulationProcesses

Participants

AuditorsTradingPartners

Investors

FinancialPublishersand Data

Aggregators

Regulators

Software Vendors

ManagementAccountants

Companies

Economic Policymaking

CentralBanks

XBRLGL, the

Journal Taxonomy

XBRL“Financial Reporting”

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.

PostingJournal

Invoice DistributionTo GL Report

SourceJournal

GeneralJournal

TransactionPosting

Journal History Report

Consolidating/Consolidated

Journal Entries

Sub Ledgers

Business Activity

Transaction Detail

XBRL GL And XBRL FRSource Systems

Internal Reporting Pipeline

Reporting

Accounts PayableAccounts ReceivableOrder EntriesPurchasingFixed AssetsHuman ResourcePayroll

Late EntriesAdjustmentsManual Entries

General Ledger

Source Document

s

Regulatory Reporting

Tax

Business Activity Management

Benchmark &Analysis

Annual(Quarterly) ReportingFinancial

Systems

ManualTransaction

Business Events

Aggregation Consolidation

Journalize

Financial Data Mart/Repository

Financial Reporting

Decision Support

Extract & Transform

Monitor, Audit & ControlBudgeting & Forcasting

xbrlInfo xbrlInclude summaryReportingElement

Core has common elements, lays out the framework

Jurisdictional add-ons Functional add-ons Industry add-ons Other add-ons

Modular and Reusable/Generic

One or many types of entry groupings

One or more “entries”

One or more “detail lines” per entry

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

Budget

Reporting

Business Analysis

Performance

INTERFACEPeopleSoft

Audit

Data WarehouseTranslates MSA

GL account format to

US SGL

Monthly Feed

MLSAP/AR

PMSAP/AR

CSMSSystem 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

Journal detail data

Ongoing reconciliation

US SGL Summary Entries

The Problem…

INTERFACE

Budget

Reporting

Business Analysis

Performance

Next Things

MAPPING TO

XBRL GL

PeopleSoft

Audit

Daily Feed

MLSAP/AR

PMSAP/AR

CSMSSystem of

Record

…The Solution

MAPPING TO

XBRL GL

XBRL GL

The use of XBRL GL as a data standard will:1. Streamline the process and reduce

processing time2. Eliminate the need for manual data

integration and manipulation3. Eliminate time consuming reconciliation 4. Enhance the reusability of the same

information across different systems and processes.

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

Resources What’s available to review

XBRL GL 2005, an XBRL 2.1-compliant taxonomy

Where to find it www.xbrl.org/GLFiles

Additional resources GaLaPaGoS – GL Practices Guide for Study

http://gl.iphix.net

Questions? xbrlgl@xbrl.org

Contact Information

Gianluca Garbellotto

XBRL Business Manager, DynAccSys

XBRL GL Working Group

ggarbellotto@dynaccsys.com