# Presentation: 359810

**Kansas City Customer Advisory Board Briefing**

- December 12, 2006

## Fundamental Changes to the current process
Developing 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

- Developing 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?**

## GWA User Enrollment – Getting Started

- Web-based user enrollment – links available on the GWA website and will be available on the GWA System login page by the end of this month
- Certifying supervisors must be enrolled first paper process
- User enrollment time frame has been reduced from 2-3 weeks to 2-3 days
- Agency users will also be able to reset their own passwords
- All Account Statement users are currently in the user provisioning system
- Current Release1 users (approx. 1200) will start enrolling for ATM beginning in June.

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

##  SAM

**CAFE will send SAM transactions with:**
-  TAS/BETCs or
-  CKeys
**SAM will:**
- Validate TAS/BETC or
- Derive valid TAS/BETC from Ckey or
- Default a valid TAS/BETC
- Return transactions to GWA w/valid TAS/BETC.
- Provide valid TAS/BETC reference lists for Agencies

## IPAC Impact

## IPAC – Agency Impact

- IPAC has required sender TAS since October 2003
- Effective October 1, 2006 IPAC will accept only TASs that are valid and appropriate for use through IPAC
- Note:  Most F Accounts are not valid for use through IPAC.
- A list of valid IPAC TAS and BETC is available on the GWA website http://www.fms.treas.gov/gwa

## IPAC – Agency Impact

- _GWA Player and Player Trading Partner Requirements_
- Effective Immediately:
- For GWA Players, a valid TAS/BETC combination must be reported for both the sender and receiver sides of the transaction.
- Trading Partners conducting business with GWA Player Agencies must report a valid TAS/BETC combination for the receiver side of the transaction.
- Only for transactions with the Players.
- All other IPAC transactions follow current reporting requirements.

## IPAC – Agency Impact

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

## IPAC – Agency Impact

- _The Bottom Line_
- Must work with your trading partners now.
- Establish 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.

## Partial 224Agency Implementation

## Partial 224

**Web based application**
- Ability to turn off sections of the P224
- Provides for reclassification capability by using only section I of the P224**.**
**    ****GWA Reporters by:**
- ALC
- Source system
- Categories

## GWAAccount Statement

## The GWA Account Statement

**The GWA Account Statement**

**Definition:**
- An online, daily refreshed, query based application designed to provide each Federal Program Agency with a central location for retrieving information relating to its Fund Balances with Treasury.** **
**Objective:**
- Designed to assist Agencies with their reconciliation processes.
- Replaces the Monthly Undisbursed Ledgers and Trial Balance reports. (FMS – 6653, 6654, 6655)
**Benefits:**
- Access – Online at the Department level
- Timeliness – Refreshed daily
- Flexibility – Full query capability at both TAS and ALC level
- Clarity – Clear description of balance and transaction data

## The GWA Player

Membership Has Its Advantages

**Membership Has Its Advantages**

## GWA Player – Current

** **

**  ****GWA Available Components and User Benefits:**
- GWA User – Official Implementation
- Café 1.3 – Full Utilization
-   **Acceptance of daily transactions with TAS/BETC validation and processing **
- Authority Transactions Module (ATM)
-   **Implements Warrant Journal Vouchers functionality**
**   ****Transitions Release 1 components from BPD to TWAI**
- Account Statement
- Self Enrollment
- Shared Accounting Module (SAM)

**GWA Player – Current**

## GWA Player – First/Second Quarter 07

** **

**  ****GWA Available Components and User Benefits:**
**GWA User – Additional roll out to IPAC users**
-    Partial 224 Rollout to multifaceted Pilot ALC’s
**   ****IPAC – New “GWA Way” of reporting**
**   ****Payments/Collections – Old 224 reporting**
**Begin Payments Pilot with agencies**
**Account Statement enhancements**

**GWA Player – First/Second Quarter 07**

## GWA Player – Third/Fourth Quarter 07

** **

**  ****GWA Available Components and User Benefits:**
- GWA User – Official Implementation of Payment agencies
**   ****Roll out of additional IPAC GWA Players**
- Partial 224 Rollout to multifaceted Pilot ALC’s
**   ****Payments – New “GWA Way” of reporting**
**   ****IPAC/Collections – Old 224 reporting**
- Account Statement (GWA TAS) 3.0
- Work with FSIO on GWA TAS/BETC testing
- Implement ATM 2.0 (appropriation warrants)
- Begin working with Collection Pilot agencies

**GWA Player – Third/Fourth Quarter 07**

## GWA Player – 2008

** **

**  ****GWA Available Components and User Benefits:**
- GWA “Unofficial” Account Statement
- Daily updated view of Fund Balance with Treasury showing impacts of “GWA Way” submitted transactions with TAS/BETC
- Begin Working with NTDO’s
- Implement Mandatory use of **GWA** TAS/BETC
- Implement GWA Player(s) for Collections
- Pilot and Implement **Full** GWA Player with all transaction types

**GWA Player – 2008**

## GWA Player – Payments - 2007

- Work with PAM/PACER to incorporate short term changes
- PACER sends new consolidated file format
- Begin Payment Pilots with Denali, Agriculture, Bureau of Prisons
- Begin SSI Pilot

## GWA Player – Payments  (continued)

- 100 TAS/BETC’s per Payment
- 100 TAS/BETC’s per Schedule
**Routine to roll up Bulk File data by TAS and Amounts**.
**Out of Balance Reports**** **
**Aftermath**** **
**Level of Detail on Account Statement**
- Schedule level

**GWA Player – Payments  (continued)**

## 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 |
| IPAC GWA Players and trading partners must include current [STAR] TAS/BETCs on both sides of IPAC transactions | October 1, 2006 | Impacts 4 pilots and their trading partners |
| ATM Module implementation | August 2006 |   Replaces current NET,  Borrowing and Warrant JV applications
  Need to be enrolled as a GWA user |
| IPAC GWA Players in Production | October 2006 | Impacts 4 pilots 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 – Ongoing | 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 | August 1, 2008 | 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 | August 1, 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 | August 1, 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 |
| All Payment ALCs to include valid GWA TAS/BETCs on Payment Schedules | 2009 | 100 TAS/BETC’s per Payment and per Schedule |
| GWA Collection Pilots – Begin working with pilots to provide valid GWA TAS/BETCS or Classification keys [Ckeys] on all collection transactions | 4th quarter 2007 | GWA Compliant

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

 |
| All Collection GWA Player ALCs to include valid GWA TAS/BETCs or Ckeys on collection transactions | 2008 |  |