CARS logo

Transitioning to the New Standard Component Format of the Treasury Account Symbol (TAS)

Fact Sheet

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’s Financial Management Service (FMS) 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, FMS is adopting the Component TAS format, as published by the Common Government-wide Accounting Classification Structure (CGAC) in July 2007. FMS will collect the Component TAS and the Business Event Type Code (BETC) from internal and external systems, and post directly to the fund balances of TAS.

Agencies should plan to adopt the Component TAS as required by each FMS system and as set forth in FMS Commissioner David Lebryk’s January 14, 2011, letter to the CFO community. Commissioner Lebryk Reaches Out to Agency CFOs Regarding Modernization Initiatives

This FACT SHEET identifies how the TAS format changes, what transition phases agencies can expect, and two attachments that show the specific TAS format changes.

What are the changes?

Currently, FPAs report their TAS using a string format (e.g. 20X1801.1). FMS is adopting the Component TAS (Attachment B), in lieu of the String TAS (Attachment A). 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 first 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 the 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 has Funds Held Outside the Treasury, they currently report TAS (41) 20X1234. In the GWA environment, they will report the TAS 20X1234 – without the (41) – but with a separate business event type code (BETC) of FHOTXD.

As a result, 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?

For information about the upcoming FMS system changes and timelines related to the Component TAS, please see the FMS Commissioner’s January 14, 2011, CFO Letter at: Commissioner Lebryk Reaches Out to Agency CFOs Regarding Modernization Initiatives

Here is a summary of some of the upcoming changes:

Applications within the Central Accounting Reporting System (CARS, formerly GWA): The Account Statement (AS), the Agency Transaction Module (ATM), and the Classification Transactions and Accountability (CTA, formerly P224) all provide the capability to display either the string TAS format (Attachment A) or the component TAS format (Attachment B). Each user can select his/her individual preference of the TAS format for entering transactions, and displaying or downloading reports.

For a complete listing of TAS BETCs valid for use in the AS, ATM, and CTA applications, please see https://www.sam.fms.treas.gov/sampublic/tasbetc.htm

This listing, maintained by the Shared Accounting Module (SAM), also provides a crosswalk between the string and component TAS formats, along with their associated BETCs. SAM assists CARS/GWA in TAS classification via validation, translation, and default. For more information on SAM, please see Shared Accounting Module (SAM)

IPAC: As of March 2011, IPAC’s online application only accepts the component TAS format (Attachment B). IPAC bulk files currently still accept: 1) the new standard component TAS format; 2) the STAR component TAS format or; 3) the original string-based, single-digit fiscal year TAS format. However, as of July 1 2013, bulk files will only be accepted in the new standard component TAS format. Please see the IPAC website for more information Intra-Governmental Payment and Collection (IPAC)

For a complete listing of TAS BETCs valid for use in the IPAC system, please see the following link, and click on IPAC TAS BETC (date) http://www.fms.treas.gov/cars/ref_guidance.html. This listing provides valid TAS in the component format for IPAC Online users, as well as a crosswalk to the single-digit fiscal year string TAS format for IPAC Bulk users. It also provides an indicator whether the BETCs for each TAS are appropriate on the Payment or Collection side of an IPAC transaction.

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 (Attachment B).

For more information on TAS BETC classification of payments, please see the Payment Application Modernization (PAM) and Secure Payment System (SPS) websites at: PAM Support of GWA SPS changes for GWA TAS-BETC

For more information on TAS BETC classification of collections, please see the Transaction Reporting System (TRS) website at: Transaction Reporting System (TRS)

Attachment A – String TAS

Currently available for use in the Account Statement, Agency Transaction Module and
Classification Transactions and Accountability (formerly P224)

Data Element Description Format Total Identified Spaces Example of Concatenated TAS
1.The Sub-level Prefix(if populated) is the first two characters of the TAS separated from the rest of the TAS by parenthesis. The Sub-level Prefix represents a programmatic breakdown of the account for Treasury publication purposes. (##) 4 (01)
2. Agency Identifier. ### 3 (01)11
3. A Hyphen will be added to separate the Agency Identifier from the Allocation Transfer Agency Identifier, if one exists. - 1 -
4. Allocation Transfer Agency Identifier. If authority for the Account has been transferred from the Agency Owner to another agency, the Agency Owner will move to the third element of the TAS. The Co-Owner will move to the second position immediately before the Agency Owner, separated by a hyphen. ### 3 (01)14-11
5. Fiscal Year field. The Fiscal Year, if presented, will contain a two-character year field, a five character multi-year field (two years separated with a '/'), or a single alpha character. Some of the Fiscal Year values may include:
   No Year
   Single Year
   Multi Year
Y
YY
YY/YY
5 (01)14-11X
(01)14-1101
(01)14-1104/05
6. Main Account Number. The Main Account Number represents the type of Fund and the purpose of the account within that Fund. For Example:
   Trust Fund: 8501
   Trust Revolving Fund: 8402
   General Fund (customs duties): 0300
AAAA 4 (01)14-1104/050300
7. Sub-Account Symbol. The Sub-Account Symbol Identifies an available receipt or other Treasury-defined subdivision of the main account. Valid ranges are 1 - 999 and are presented immediately following the Main Account Number separated by a '.'. There will be no leading zeroes in this field. .SSS 4 (01)14-1104/050300.123
8. Filler. Reserved for future use. - 3 -
Maximum field size - 27 -

Attachment B – Standard Component TAS

Field Name
(abbreviation)
Size Format Description Format/Validations
Sub-level Prefix
(SP)
2 CC The Sub-level Prefix (if populated) is a programmatic breakdown of the account for Treasury publication purposes.
  • If Sub-level Prefix does not apply, it shall be blank/spaces/empty.
  • If Sub-level Prefix applies, it shall be 00-99.
Allocation Transfer Agency Identifier
(ATA)
3 CCC The Agency Identifier of the agency receiving funds through an allocation transfer.
  • If Allocation Transfer Agency Identifier does not apply, it shall be blank/spaces/empty.
  • If Allocation Transfer Agency Identifier does apply, it shall be 000-999.
  • Current 2 digit Allocation Transfer Agency Identifier shall be right justified and zero filled.
    (ex. Allocation Transfer Agency Identifier 75 = 075)
Agency Identifier
(AID)
3 CCC Agency Identifier of account owner. Used in conjunction with the main account code, the Agency Identifier represents the department, agency or establishment of the U.S. Government that is responsible for the TAS.
  • Value Required.
  • Shall be 000-999.
  • Current 2 digit Agency Identifier will be right justified and zero filled.
    (ex. Agency Identifier 20 = 020)
Beginning Period of Availability
(BPOA)
4 CCCC In annual and multi-year funds, identifies the first year of availability under law that an appropriation account may incur new obligations.
  • 4 digit year shall be (0000-9999).
  • If single/annual year account, it shall be the same value as the Ending Period of Availability.
  • Value not applicable for no-year "X" accounts, clearing/suspense "F" accounts, central summary general ledger "A" accounts, and unavailable receipt accounts, it shall be blank/spaces/empty.
Ending Period of Availability
(EPOA)
4 CCCC In annual and multi-year funds, identifies the last year of funds availability under law that an appropriation account may incur new obligations.
  • 4 digit year shall be (0000-9999).
  • Value not applicable for no-year "X" accounts, clearing/suspense "F" accounts, central summary general ledger "A" accounts, and unavailable receipt accounts, it shall be blank/spaces/empty.
Availability Type Code
(A)
1 C Identifies no-year accounts "X", clearing/suspense accounts "F", and Treasury's central summary general ledger accounts "A"
  • Value not applicable for single/annual year accounts, multiyear accounts, or unavailable receipt accounts - it shall be blank/space/empty.
Main Account Code
(MAIN)
4 CCCC Identifies the type and purpose of the fund.
  • Value Required.
  • Shall be "0000-9999".
Sub-Account Code
(SUB)
3 CCC Identifies an available receipt or other Treasury-defined subdivision of the main account.
  • Value Required.
  • Shall be "000-999".

* Format of “C” indicates Character.

Viewing PDF files PDF 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.

   Last Updated:  March 14, 2014