# Presentation: 316843

## Project Overview and Status 

**AFC Dallas Forum**
- August 15, 2007
**Anna Hancock**

**Project Overview and Status**

##  GWA Modernization – Time for Change

**  ****Evolution – What have we grown into**
- Inefficient, Outdated, and Untimely (IOU)
-   **Present Day Requirements –  Time to pay off the IOU**
- Accelerated Reporting Requirements
- President’s Management Agenda - Scorecard
- Audited Financial Statements
-   **The Future – Unknown....But we’ll be ready**
- Consolidated, web-based system for the collection, processing, reporting, and storage of all financial information

## GWA Key Goals/Objectives

**Eliminate the two step classification process**
- 	     Capture the Treasury Account Symbol (TAS) and 	Business Event Type Code (BETC) at the earliest 	possible time for agency payment, collection and 	intra-governmental transactions, and post directly to the 	fund balance with treasury.
**Provide timely and accurate accounting information**
**Eliminate the use of redundant processes and systems for the capturing and reporting of financial information**

## Fundamentally change the current process
Develop a new database
Develop the infrastructure to support GWA Reporters
ATM, Account Statement, CAFÉ, P224, SAM, IPAC, Collections, Payments
Automated Enrollment – User-based access control
Phase in GWA Reporters
Streamline GWA’s architecture
Provide agencies with GWA initiated Account Statement
Support NTDO GWA Reporters
Fully replace legacy accounting system

- Develop a new database
- Develop the infrastructure to support GWA Reporters
- ATM, Account Statement, CAFÉ, P224, SAM, IPAC, Collections, Payments
- Automated Enrollment – User-based access control
- Phase in GWA Reporters
- Streamline GWA’s architecture
- Provide agencies with GWA initiated Account Statement
- Support NTDO GWA Reporters
- Fully replace legacy accounting system

**How is GWA Going to Accomplish This?**

## Overall Benefits of theGWA Reporting Methodology

- _Agency Benefits_
- Touch transaction once
- Current Fund Balance data available in one place
- Reduced central agency reporting
- Faster turnaround on processed data
- Supports agency reconciliation processes
- _FMS Benefits_
- Daily receipt of validated financial data
- Improves overall financial reporting capabilities

## GWA Standard Transaction ClassificationTAS/BETC

## TAS Definition

- Treasury Account Symbol (TAS)
- Refers to the receipt, appropriation, and other fund account symbols and titles as assigned by the Department of the Treasury
- Format standardization
- Move towards TAS component pieces, supports CGAC

**   ****GWA Standard Transaction Classification**

## What are the TAS Changes? 

**   ****GWA Standard Transaction Classification**

- Elimination of Standard Subclasses – replaced by BETC.
- Example: Subclass “88” replaced by BETC “INVTSEC”
- “(88)20x1234” replaced by “20x1234 INVTSEC”
- Expansion of Dept Agency Codes – from 2 to 3
- Current 2 digit department codes will be right justified and zero filled
- Standardized names: From “Dept Regular” to “Agency Identifier”
- From “Dept Transfer” to “Allocation Transfer Agency Identifier”
-  Expansion of Fiscal Year –
-  String-based GWA TAS expands FY to 2 characters;
- Multi-year is 5 characters (2 years separated with a slash)
-   Component-based GWA TAS expands FY to 4 characters each
- Beginning FY and Ending FY each have separate fields
- Alpha characters (X, F) are also in separate field

## BETC Definition

- Business Event Type Code (BETC)
- Refers to an 8-character code that indicates the type of activity being reported (e.g. receipt, disbursement, etc)
- BETC determines a transaction’s effect on the Treasury Account Symbol’s FBWT
- BETC replaces transaction codes and standard sub-classes at a more intuitive level of detail

**   ****GWA Standard Transaction Classification**

## Sample BETCs

**   ****GWA Standard Transaction Classification**

**Code****	****Activity****	****	****	****Transaction****	****Trans****	****Sub**
**	****	****	****	****Affect on TAS****	****Code****	****Class**
- DISB	Gross Disbursement		D (decrease)	61	--
- COLL	Offsetting Collection		C (increase)	71	--
- INVTSEC	Investment in Treasury 	D (decrease)	61	88
- 	Securities
- REDTSEC	Redemption of Treasury	C (increase)	71	98
- 	Securities

## GWA ReporterImplementation Strategy

## GWA Implementation Strategy

- Bring on the maximum number of agencies as soon as possible
- Implement feeder mechanisms (IPAC, Payments, Collections) through a phased in approach
- Develop tools to assist in implementation (SAM, Account Statement)
- Provide tools to agencies to phase in GWA processing
- P224 provides for reclassification capability by using only section I of the 224
- Ability to turn off sections of the P224
- Use an incremental approach to allow for efficient planning and scheduling of resource utilization and testing in manageable parts

## Shared Accounting ModuleSAM

##  Shared Accounting Module

- Utility responsible to ensure a valid TAS/BETC is posted
-     to all transactions entering the GWA System
- Assists agencies in complying with GWA standard            transaction classification
- GWA will provide SAM with a table of valid TAS/BETCs
- Agencies will define valid TAS/BETCs in SAM for:
-  Default rules and
-  Classification (Ckey) translations

## IPAC Impact

## IPAC Reporting Cheat Sheet

**AS OF 05/31/2007**

|  | Sender  | Receiver |
| --- | --- | --- |
| GWA Reporter with a GWA Reporter | TAS/BETC | TAS/BETC |
| GWA Reporter with a
Non-GWA Reporter | TAS/BETC |  |
| Non-GWA Reporter transacting with a GWA Reporter | TAS | TAS/BETC |
| Non-GWA Reporter transacting with a Non-Reporter | TAS |  |
|  |  |  |

##  The Bottom Line for IPAC

- Mandatory Trading Partner Agreements (TPAs)
- IG Business Rules 2007-03
- Mandatory transition to TAS/BETC reporting
- Transition to a single standard TAS format instead of the current 6+ formats available today is coming
- F-Account Issue:  Treasury will continue to work with agencies to identify alternatives to using F Accounts

** ****The Bottom Line for IPAC**

## Current GWA Reporters for IPAC

- Bureau of Public Debt (BPD)
- Financial Management Service (FMS)
- Internal Revenue Service (IRS)
- Government Printing Office (GPO)
- _Future GWA Reporters_
- Federal Energy Regulatory Commission
- IRS Service Centers

## GWAMP Roll out Strategy

| Action | Target Date | Impact on Agency |
| --- | --- | --- |
| ALL IPAC ALCs must have current [STAR] TAS for sender side | Now | CURRENT REQUIREMENT –
Valid IPAC TAS only |
| ATM Module implementation | August 2006 | Replaces current NET,  Borrowing and Warrant JV applications
Need to be enrolled as a GWA user |
| First GWA Players live | October 2006 | Impacts 4 GWA players and their trading partners
 |
| New User enrollment process. http://fms.treas.gov/gwa/forms.html
 | Ongoing | For GWA Applications, Agencies are required to enroll using new process |
| Additional IPAC ALCs to include current TAS/BETC on both sides of IPAC transactions | October 2006 – August 2008 | Impacts IPAC ALCs and their trading partners.
 |
| Agencies research and prepare to provide valid TAS/BETCs on both sides of IPAC transactions | ASAP | All IPAC reporters |

## GWAMP Roll out Strategy

| Action | Target Date | Impact on Agency |
| --- | --- | --- |
| Update Trading Partner Agreements to include BOTH Treasury Account Symbol (TAS) and Business Event Type Code | ASAP | Must know how [Business Event Type Code - BETC] transactions are affecting what TASs
 |
| Agencies to Implement P224 Functionality via FSIO COTS Packages or home grown systems
TESTED AND IN PRODUCTION | 4th quarter 2007 | Agencies will move to P224 once they become a GWA Player |
| Complete testing & certifying to ensure that  ALL FSIO vendors can provide valid GWA TAS/BETCs on both sides of IPAC Bulk Files | 4th Quarter 2007 | Agencies need FSIO certification to implement new functionality |
| ALL FPA systems must be able to provide valid GWA TAS/BETCs on BOTH sender and receiver sides for IPAC bulk files 
TESTED AND IN PRODUCTION | 3rd quarter 2008/09 | Once IPAC turns on the GWA TAS, any current TAS formats will NOT be accepted

FMS is working with FSIO to determine a new implementation date

http://fms.treas.gov/gwa/factsheet_tas.html |
| IPAC
Turn on GWA TAS/BETC both sides | 3rd quarter 2008/09
 |  |

## GWAMP Roll out Strategy

| Action | Target Date | Impact on Agency |
| --- | --- | --- |
| Payment Pilots – Valid GWA TAS/BETC’s on Transactions | 3nd quarter 2007
 | GWA Compliant
 |
| Implementation of GWA Initiated Account Statement - | 2008
 | Transactions available at detail level |
| Agency Partnership Council | Quarterly | Agency participation at every meeting |
| ATM 2.0 – Appropriation Warrants | 3rd quarter 2007 | Add access to Appropriation to current ATM access |
| All TDO Payment ALCs to include valid GWA TAS/BETCs on Payment Schedules | 2009 | 100 TAS/BETC’s per Payment and per Schedule |
| Collection Pilots – Begin working with collection pilots to ensure valid GWA TAS/BETCS or Classification keys [Ckeys] are on all collection transactions | 4th quarter 2007 |  |
| All Collection ALCs to include valid GWA TAS/BETCs or Ckeys on collection transactions | 2009 | GWA Compliant

Ckeys identified and set up in the Shared Accounting Module [SAM] for translation to valid TAS/BETC’s

 |

## Communicate with your trading partners and set up your Trading Partner Agreements.

Analyze your current business reporting processes and begin to associate them with established GWA TAS/BETC combinations.  Identify areas that do not comply and work with FMS and/or your business partners to resolve these issues.

Review and analyze your business processes to eliminate the use of F/Suspense Accounts, particularly for IPAC reporting.

Modify your accounting systems to provide and accept TAS/BETC on IPAC transactions.

Review your systems and processes that are based on monthly cycles and determine how to transition them to daily processes incorporating the GWA TAS/BETC.

Look into upgrading your COTS packages or modifying your legacy systems to accommodate GWA Reporter requirements.

Work with the GWA Agency Outreach Group to learn more about the process of becoming a GWA Reporter and to discuss any questions or concerns.

- Analyze your current business reporting processes and begin to associate them with established GWA TAS/BETC combinations.  Identify areas that do not comply and work with FMS and/or your business partners to resolve these issues.
- Review and analyze your business processes to eliminate the use of F/Suspense Accounts, particularly for IPAC reporting.
- Modify your accounting systems to provide and accept TAS/BETC on IPAC transactions.
- Review your systems and processes that are based on monthly cycles and determine how to transition them to daily processes incorporating the GWA TAS/BETC.
- Look into upgrading your COTS packages or modifying your legacy systems to accommodate GWA Reporter requirements.
- Work with the GWA Agency Outreach Group to learn more about the process of becoming a GWA Reporter and to discuss any questions or concerns.

**What should my Agency be doing to prepare?**

## Contact Information

_**GWA Modernization Project**_
**Michael Norman – (202) 874-8788**** ****– michael.norman@fms.treas.gov**
**Anna Hancock – 202-874-9868 – **_**anna.hancock@fms.treas.gov**_
_**Web site – www.fms.treas.gov/gwa**_
**Email box –**_ __**GWA.Project@fms.treas.gov**_** **
**Enrollment – GWA.Enrollment@fms.treas.gov**** **
_**IPAC Project**_
**Susan Markland -(202) 874-9816 – **_**susan.markland@fms.treas.gov**_
**Lori Makle-Sellman - (202) 874-8782 – lori.makle-sellman@fms.treas.gov**
_**SAM**_
**Robin Gilliam – (202) 874-9133 – robin.gilliam@fms.treas.gov**
**Cheryl Murray – (202) 874-7078 – cheryl.murray@fms.treas.gov**
_**GWA Project Agency Relationship Management Division**_
**Carolyn Dunston - 202-874-7491 – **_**carolyn.dunston@fms.treas.gov**_
**Peter Moore – 202-874-6578        -  Peter.moore@fms.treas.gov**