GWA Treasury Account Symbol (TAS)

FACTSHEET

Why is there a new TAS?

In our goals to streamline the central accounting and reporting process, we analyzed the Treasury Account Symbols (TAS) reported by Federal Program Agencies (FPAs) to Treasury through the various interface systems. Currently, multiple formats are accepted, depending on the FPA and the reporting system (e.g. IPAC, 224). To implement standardization and consistency, we have developed one standard format that the GWA system will use and that eventually all systems interfacing with GWA will use as well. Additionally, this move for standardization is being made to support most agency accounting systems as well as initiatives under development by the Financial Management Line of Business (FMLOB) Common Government-wide Accounting Classification Structure (CGAC) to standardize the accounting structure for agencies.

Standardization of the TAS is especially important in the new GWA environment, since transactions flowing from these interface systems will be posting to and updating the fund balances of TAS in the future.

When GWA is fully implemented, all FPAs will report transactions using the standard component-based TAS along with a business event type code (BETC).

What are the changes?

Currently, FPAs report their TAS using a string-based format (e.g. 20X1801.1). Based on recommendations from CGAC, FMS will move towards adopting the TAS component pieces, in lieu of the single concatenated string. There are many benefits to using separate, component pieces, such as having the ability to sort, filter, and analyze based on each independent piece.

Within the TAS itself, there are three other changes to note. The main difference or change is the elimination of standard subclasses. This means that FPAs will report a TAS, without having to report sub classification of that TAS based on explicit transaction types (such as borrowings, investments, funds held outside treasury). Instead of the transaction type being reported as a standard subclass on the TAS, it will be reported as a business event separate from the TAS. For example, if an agency invests in Treasury securities, they currently report: (88) 20X1234. In the GWA environment, they will report the TAS - without the (88) - but with a separate business event type code (BETC) of INVTSEC.

The subclass field is being renamed to "Sub-level Prefix" and will only be used for programmatic breakdowns of the TAS for Treasury publication purposes. Sub-level Prefixes have a unique meaning or a unique need for sub classification that is NOT based on transaction types or business events as described previously.

The other two significant changes to the TAS relate to the expansion of the department/agency codes and to the fiscal year fields. See Attachments for further details regarding these field changes.

How will we phase in these changes?

The new standard component TAS will be implemented based on each interfacing system's (IPAC, P224, SAM, etc) status and development schedules.

IPAC: Initially, IPAC will continue to use a String-based TAS until changes can be incorporated to support the Component-based TAS. The format of the String-based TAS can be found in Attachment A. This format, although is still concatenated as one string, does still implement the other significant changes regarding the sub-level prefix and the fiscal year expansion. Additionally, this format utilizes BETC reporting. This format (Attachment A) will be available for use in IPAC only, by the fall of 2008. Subsequent notification will follow once a date is established as to when IPAC can move to the Component-based structure.

Payment and Collection Systems: Currently, FMS' payment systems do not validate TAS; and FMS' collection systems do not require TAS reporting. These systems are being modified to collect TAS and BETCs in the future, and will support the Component TAS structure. The format of the Component-based TAS can be found in Attachment B.

Partial 224: Since the Partial 224 is a transitional application, which will eventually be retired when all FPAs/ALCs become GWA Reporters, it was decided that Partial 224 will not be modified to use the new standardized GWA String-based TAS nor the GWA Component-based TAS with BETCs. This means that the standard subclass will not be replaced by BETCs for Partial 224 reporting. The only change being made to Partial 224 will be the fiscal year field of the format currently being reported. This is in order to accommodate the shortcomings in the use of single digit years. This fiscal year change is expected to be implemented in early 2008.

Shared Accounting Module (SAM): SAM will be able to provide downloads of valid TAS in both the GWA TAS String and the GWA TAS Component formats, along with their associated BETCs. This will help facilitate the transition, since IPAC will use the String-based TAS structure in the near-term, then eventually the Component TAS structure.

Attachment A - String-based GWA TAS

For IPAC reporting only - As of Fall 2008
Interim - until implementation of Component-based GWA TAS

Attachment B – Component-based GWA TAS

Ultimate standard to be implemented by Payment and Collection systems,
Eventually to be implemented by IPAC (date to be determined)

For more information regarding this CGAC-compliant TAS format, refer to http://www.fsio.gov/fsio/download/cgac/CGAC_Structure_Report_07-31-07.doc

* Format of “C” indicates Character.

Viewing PDF files requires Acrobat Reader which is included in many Web browsers. If your browser does not read Acrobat's pdf files, the Acrobat Reader is free to download and use.