# Presentation: 359827

## Government-Wide Accounting Program Initiatives 

- Federal Investments and Borrowings Seminar
- Becoming a GWA Player
- April 12, 2007

##   Evolution – What have we grown into?

**  ****Evolution – What have we grown into?**
- The current accounting and reporting process has become 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 redundant reporting**

## Fundamental Changes to the current process
Developed a New Database
Developing the infrastructure to Support GWA Players
ATM, Account Statement, CAFÉ, P224, SAM, IPAC, Collections, Payments
Automated Enrollment – User-based Access Control
Phase in GWA Players
Streamline GWA’s Architecture
Provide Agencies with GWA initiated Account Statement
Support NTDO GWA Players
Fully Replace Legacy Accounting System

- Developed a New Database
- Developing the infrastructure to Support GWA Players
- ATM, _Account Statement_, _CAFÉ_, _P224_, _SAM_, _IPAC_, Collections, Payments
- _Automated Enrollment_ – User-based Access Control
- Phase in GWA Players
- Streamline GWA’s Architecture
- Provide Agencies with GWA initiated Account Statement
- Support NTDO GWA Players
- Fully Replace Legacy Accounting System

**How is GWA going to accomplish this?**

## Implementation Strategy

- Developed to provide a method to bring on the maximum number of agencies as soon as possible.
- Take advantage of initiative to create a web based 224 application.
- Provides for reclassification capability by using only section I of the 224.
- Ability to turn off sections of the 224.
- Incremental approach allows for efficient planning and scheduling of resource utilization and testing in manageable parts.

## Benefits

- Touch transaction once
- Most current fund balance always available
- Fund balance detail available in one place
- Reduced central agency reporting
- Faster turnaround on processed data
- Interfaces with FMS remain the same
- Supports agency reconciliation processes
- Safe and secure Internet access

## TAS Definition

- Acronym for Treasury Account Symbol (TAS)
- The receipt, appropriation, expenditure and other fund account symbols and titles as assigned by the Department of the Treasury
- A 27-character field – with 24 currently identified characters
- Supercedes 21 position TAS and any other suggested formats

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

## BETC Definition

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

** ****GWA Standard Transaction Classification (cont)**

## Shared Accounting ModuleSAM

##  SAM

-     to all transactions entering the GWA System
-   **Developed to assist agencies** in complying with GWA
-     standard transaction classification
-   **GWA will provide** SAM with a table of **valid TAS/BETCs**
-   **Agencies will define** in SAM valid TAS/BETCs for:
-  Default rules and
-  Classification (Ckey) translations

** ****SAM**

## Initial Impact to Agencies

- Process changes to support new GWA reporting
- System changes to support IPAC TAS/BETC implementation
- System changes to support migration to GWA TAS/BETC
- Update of Trading Partner agreements

## IPAC Impact

## IPAC Reporting Cheat Sheet

|  | 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 |  |
|  |  |  |

**IPAC Reporting Cheat Sheet**

##     The Bottom Line

-     _The Bottom Line_
- Must work with your trading partners now.
- Update Trading Partner Agreements (TPAs)
- Communication is essential
- All Agencies will transition to TAS/BETC reporting during October 2006 through August 2008.
- The 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.

## GWA Wants You!

- Do you have what it takes to be a pilot?
- ALC must be a 224 reporter
- SOD’s must be clear
- Be prepared to capture TAS/BETC info
- Willing to participate

## What should my agency be doing to prepare?

- Set up your Trading Partner Agreement with your customers
- Communicate with your trading partners
- Modify your accounting systems to provide and accept TAS/BETC on IPAC transactions
- Submit request to become GWA Player
- Work with SAM implementation team to set up profiles/default rules

## 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 |
| IPAC Pilots 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**

## 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 | Once IPAC turns on the GWA TAS, any current TAS formats will NOT be accepted

Must be GWA compliant.

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

**GWAMP Roll out Strategy**

## GWAMP Roll out Strategy

| Action | Target Date | Impact on Agency |
| --- | --- | --- |
| Payment Pilots – Valid GWA TAS/BETC’s on Transactions | 2nd 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 Appropration 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

 |

## 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, (202) 874-8782 – **_**lori.makle@fms.treas.gov**_
_**GWA Project Agency Outreach**_
**Carolyn Dunston - 202-874-7491 – **_**carolyn.dunston@fms.treas.gov**_
**Peter Moore – 202-874-6578        -  ****Peter.moore@fms.treas.gov**