GTAS Updates

Alex Abshire

April 2021
Page 2 L EAD ∙ T RANSFORM ∙ D ELIVER

• Can we utilize our GTAS ATB’s in our Data Act File submissions? 

• Yes, currently all of the data is contained within GTAS for File A

• Data Act broker currently has the capability to generate the File A submission 

for agencies from the GTAS data that feeds into the broker

• What about the Data Act File B submission? 

• GTAS currently has all of the needed data except:

• Budget Object Class (BOC)

• Program Activity Code

• Data Act File C submission

• There are currently no plans for GTAS data to be able to generate File C for 

agencies

Utilizing GTAS data for Data Act submissions
Page 3 L EAD ∙ T RANSFORM ∙ D ELIVER

• 4-Character Code within GTAS bulk file (no decimal places)

• GTAS will be ready to accept BOC’s beginning this summer of 2021

• Agencies can start submitting BOC at that time

• It will not be required until a later date

• The list of acceptable BOC values to use in GTAS bulk file will be 

provided

• Initially 3 digits will only be used with the 4th digit being a placeholder 

• Leaves room for flexibility in the future with minimal impact to agencies

Budget Object Class (BOC)
Page 4 L EAD ∙ T RANSFORM ∙ D ELIVER

• Future enhancement to GTAS

• There is currently an internal project within OMB to look further into the 

Program Activity Code before implementing in GTAS

• Will be implemented at a later date

• Fiscal Service/OMB will communicate this out once the GTAS implementation 

date has been finalized

• Automates File B in Data Act broker from GTAS data

Program Activity Code
Page 5 L EAD ∙ T RANSFORM ∙ D ELIVER

• Currently the DEFC is a 1 alpha character format

• Expanding the DEFC due to remaining available characters

• DEFC will be updated to be a 3 alpha character field

• Fiscal Service will be ready to accept the updated format in Summer 

2021

• Exact date will be communicated to agencies once GTAS deployment date has 

been finalized

• Fiscal Service will be able to accept 1-digit or 3-digit DEFC during 

implementation phase 

• We will be converting the 1-digit DEFC to the 3-digit systematically in GTAS

• This will be required for agencies at a later date

• Fiscal Service/OMB will communicate this out when date has been finalized

Disaster Emergency Fund Code (DEFC)
Page 6 L EAD ∙ T RANSFORM ∙ D ELIVER

• 4-character Alphanumeric field

• Provides the ability to track spending at a lower, more detail level 

within a DEFC/Public Law

• Multiple disasters could be contained within a single Public Law

• Event Indicator will be required beginning with Obligations and through 

Outlays within the GTAS bulk file

• EI will be required on all 48XXXX and 49XXXX USSGL accounts

• The goal is to be available within GTAS FY2022

• This will be required for agencies at a later date

• Fiscal Service will communicate this out when date has been finalized

• Date will coincide with the requirement of the 3-digit DEFC

Event Indicator (EI)
Page 7 L EAD ∙ T RANSFORM ∙ D ELIVER

• Fiscal Service met with all Significant Entities in 2020 regarding 

generating financial statements from GTAS 

• A request we received was being able to generate financial statements 

at a bureau or sub-component level 

• Fiscal Service is looking to implement a bureau code within the GTAS 

bulk file to enable this functionality within GTAS

• This will not be required for agencies that are generating statements at the 

department/FR Entity level

• Currently analyzing different types of functionality within GTAS to accept 

multiple types of bulk files 

Bureau Code
Page 8 L EAD ∙ T RANSFORM ∙ D ELIVER

Contact Information

Alex Abshire, Supervisory Accountant 

General Ledger & Advisory Branch 

Bureau of the Fiscal Service

(304) 480-8383

Alexander.Abshire@fiscal.treasury.gov

Dan Adams, Senior Accountant 

General Ledger & Advisory Branch 

Bureau of the Fiscal Service

(304) 480-5152

Daniel.Adams@fiscal.treasury.gov

GTAS Questions:

GTAS.Team@fiscal.treasury.gov