GWA Treasury Account Symbol (TAS)

FactsSheet

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-based TAS will be implemented based on each application and interfacing system's development schedules.

GWA Applications: Currently, the GWA Account Statement (AS) and the GWA Authority Transaction Module (ATM) display the string-based GWA format (Attachment A). This format reflects GWA's original attempt at standardizing the TAS, prior to the CGAC effort. The GWA AS and ATM applications will be converting to the CGAC component-based TAS in the near future (dates to be determined).

IPAC: Currently, IPAC's online application accepts the original string-based TAS format. Beginning Mid 2009, IPAC will become fully CGAC-compliant and will only accept the component-based TAS format (Attachment B) for transactions processed on-line. For transactions submitted via bulk file, IPAC will accept: 1) the new standard CGAC component-based format; 2) the STAR component-based format or; 3) the original string-based TAS format. Please see the IPAC website for more information regarding their upcoming releases. http://fms.treas.gov/goals/ipac/index.html

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: Currently, Partial 224 accepts the original string-based TAS format. Partial 224 will be transitioning to the component-based TAS format (Attachment B), but the date is yet to be determined. Once target dates are finalized, they will be published on the GWA website. Examples of the current string TAS in P224 and the future Component TAS and BETC in P224 are the same as the examples provided above for IPAC.

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 systems or applications will be on different implementation schedules.

Attachment A - String-based GWA TAS

Attachment B – Component-based TAS

CGAC-compliant format to be implemented by all GWA applications and FMS source systems

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