* Formerly knowns as the DATA Act Informa�on Model Schema (DAIMS) Page 1 of 3

Governmentwide Spending Data Model (GSDM*) v1.0.1 

Maintenance Update Notes 

April 11, 2024

GSDM v1.0.1 is a maintenance update that will not significantly change or impact agency submissions of 

Files A, B, C and FABS. This update focuses on two minor improvements: one which will allow the 

capability for agencies to submit older, backlogged awards, and the other will align GSDM to OMB and 

GTAS requirements regarding two new USSGL accounts that were added to the SF-133 in FY23. A 

maintenance update takes place outside the standard annual cycle of one full GSDM release per year; as 

such, it is narrowly tailored, and does not involve changes to all GSDM documents. Nor does it have the 

comment period that a full release would and is instead effective immediately, except as otherwise 

noted below.

Our next release will be our Annual GSDM Release that will take place in November 2024. 

To understand the full set of changes and for specific line-item details, agencies should review the 

change logs of the Repor�ng Submission Specifica�ons (RSS), Valida�on Rules, and Prac�ces and 

Procedures. A highlighted subset of changes for each document is provided below, along with an 

implementa�on �meline for those few changes.

All these documents, as well as sample files, will additionally be available for download from the Fiscal 

Service Data Transparency GSDM site within the next few business days.

GSDM v1.0.1 Release Implementation Timeline:

• July 2024 (Beginning of Q4): Several FABS rules will be updated to allow agencies to submit 

awards where their Federal Hierarchy Office is currently expired but was active at the time of 

the award. FABS21.1, FABS21.2, FABS23.1, FABS23.2, FABS38.2.1, FABS38.2.2, FABS38.4.1, 

FABS38.4.2 will be updated to use Federal Hierarchy Start and End Dates vs Expired Status to 

determine if the award was ac�ve at the �me the award was signed. This does not change any 

policy or guidance, just changes Broker logic that will aid agencies in submi�ng older, 

backlogged awards. 

• October 2024: (FY25 PD 01/02)

o New Data Element headers will be added for USSGLs 480110 and 490110. This impacts 

two related data elements and updates rules B3, B4, C3, C4. This is to align GSDM to the 

GTAS SF-133 repor�ng requirements released in calendar year 2023 and implemented in 

FY24. The SF-133 added the two new USSGL accounts to address an issue with abnormal 

balance valida�ons in GTAS. The new headers will need to be added in Files B and C by 

FY25 PD 01/02, but the repor�ng of data values is op�onal.

o Validation rules A18, A19, and A35 were updated for PYA to correctly check only the line 

with a PYA of X in File B when PYA becomes a required field in FY25. This coincides with

the implementation in GSDM v1.0 of PYA updates made to Files B and C, as well as 

Validation Rules, to allow for Prior Year Adjustments (PYAs) for USSGL balance rows to 

close the PYA gap in presenting resources and obligations over time.
* Formerly knowns as the DATA Act Informa�on Model Schema (DAIMS) Page 2 of 3

Highlighted changes to the GSDM Reporting Submission Specification (RSS)

1. Files B/C: Updates for new USSGLs 480110 and 490110

• Added new Data Element Labels: 

USSGL480110_ReinstatedUndeliveredOrdersObligationsUnpaid_CPE and 

USSGL490110_ReinstatedDeliveredOrdersObligationsUnpaid_CPE.

New headers need to be added by FY25 PD 01/02, but the data values will be optional.

• Updated existing data element ObligationsUndeliveredOrdersUnpaidTotal_CPE for the 

addition of USSGL 480110 in the calculation of this aggregate element.

• Updated existing data element ObligationsDeliveredOrdersUnpaidTotal_CPE for the addition 

of USSGL 490110 in the calculation of this aggregate element.

2. File C:

• Updated the Required/Optional field for: 

USSGL487200_DownwardAdjustmentsOfPriorYearPrepaidAdvancedUndeliveredOrdersOblig

ationsRefundsCollected and 

USSGL497200_DownwardAdjustmentsOfPriorYearPaidDeliveredOrdersObligationsRefundsC

ollected to correctly reflect that it is "Optional (to be conditionally required for non-TOA 

(balance) rows for FY25)."

3. Domain Values:

• Added new domain values AAE, AAF, AAG, AAH, and AAI for the 

DisasterEmergencyFundCode element to realign GSDM documentation to the actual Broker

implementation.

Highlighted changes to the GSDM Validation Rules

1. Updates for new USSGLs 480110 and 490110

• Updated Rule Detail, Status, and Data Element Label to rules B3 and C3 to include USSGL 

480110.

• Updated Rule Detail, Status, and Data Element Label to rules B4 and C4 to include USSGL 

490110.

2. The following validations, A18, A19, and A35, were updated to correctly check only the line with 

a PYA of X in File B.

3. FABS21.1, FABS21.2, FABS23.1, FABS23.2, FABS38.2.1, FABS38.2.2, FABS38.4.1, FABS38.4.2 were

updated to use the Federal Hierarchy’s Office Start and End Dates vs Expired Status to 

determine if the Office was active at the time the award was signed.

Highlighted changes to the GSDM Practices and Procedures (P&P)

1. Added an introductory paragraph to explain how award files tie to the monthly DABS submission 

process. This does not change any guidance or procedures, only intends to provide 

documentation clarification.

2. Updated DABS and FABS User Management Sections to replace descriptions of MAX access for

new Broker CAIA login (sections 1.9 and 2.7). Explains the AppOwner role, Broker Permission

levels and troubleshooting tips.

3. Added timeline implementation for PARK (section 1.3.5). PARK header is required and available 

for testing in FY25 PD 01/02. In FY25 PD 07 either PAC/PAN or PARK will be accepted, and FY26 

PD 01/02 PARK will completely replace PAC and PAN in File B and C for new activity.
* Formerly knowns as the DATA Act Informa�on Model Schema (DAIMS) Page 3 of 3

4. To reflect current Broker practices, several links were updated (sections 1.3.2.4 and 1.8.6);

added clarification for flex fields (section 1.6.4); warning clarification update on blank file C

(section 1.3.2.1); usability of the Broker Submission History (section 1.7.2); 

AssistanceListingNumber and CFDA (section 2.1.4); and zero padding (Section 2.1.6).

5. For Appendix B: Updated for REST API usage for Geopolitical Entities and sorted the table by 

territory name instead of code, to reflect current Broker practices. 

6. For Appendix F: Updated Object Class to Budget Object Class, added Disaster Emergency Fund 

Code and Funding Opportunity Number; updates to City Code, County Code, and Country Code;

and alphabetized the table.

7. Corrected spacing for Data Element Label Assistance Listing Number.

8. Updated references to DATA Act to be more consistent throughout the document.

General Reminders

GSDM v.1.0 rebranded DAIMS as the Governmentwide Spending Data Model (GSDM). The rebranding is 

being done to reflect the inclusion of legisla�on and policies that go beyond the DATA Act. This is an 

ongoing effort and impacts all DAIMS documents and websites.

Timeline Reminders of All Upcoming Events:

FY25 PD 01/02

• USSGL487200 and USSGL497200 in File C will become conditionally required, with the 

‘condition’ being that the row is a non-TOA (balance) row. This requirement is enforced by rule 

C30. (DAIMS v2.2)

• FABS47.2, FABS47.3, and FABS48.2 will become fatal errors as of October 1, 2024. These rules 

are to support approved changes for Funding Opportunity Number and Funding Opportunity 

Goals Text. (DAIMS v2.2.2)

• PYA is required in File B, optional in File C. Rules Impacted: A18, A19, A35, B3, B4, B5, B6, B7, 

B13, B14, B15, B19.1, B20.1, B21, B22, B25, B26, B29, C3, C4, C5, C6, C7, C20, C21.1, C26, C27.1, 

C28.1. (GSDM v1.0)

• New data element Program Ac�vity Repor�ng Key (PARK) will replace the combination 

PAC/PAN. The header ProgramActivityReportingKey will be required and available for testing.

(GSDM v1.0)

• B12 edited rule to remove “excluding USSGL accounts for downward adjustments and 

transfers”. (GSDM v1.0)

• USSGL480110 and USSGL490110 headers in Files B and C will become required but data values 

will be optional. Rules impacted: B3, B4, C3, C4. (GSDM v1.0.1)

FY25 PD 07

• Either PAC/PAN or PARK will be accepted for monthly submissions. (GSDM v1.0)

FY26 PD 01/02

Submissions for new activity will only accept PARK. PAC/PAN will be accepted for resubmissions of prior 

periods only. (GSDM v1.0)