Treasury :: Bureau of the Fiscal Service

Enterprise Data Architecture

CollectionsReport Data Exchange

Data Exchange Listing CollRpt [1..1] Sumry [0..unbounded] TrfrSumry [0..unbounded] FcastSumry [0..unbounded] Tot [0..2] Library Resource Documentation Data Dictionary and Change Log Data Dictionary Attribute DataDictionary Element DataDictionary CollRpt Data Documents Browse the Mind Map Data Listing Message Component Relationship View Help Basic Help Generic Help Downloads Published Releases Current Release 5.0.1 Archived Releases Release 4.8 Release 4.7 Release 4.6 Release 4.5 Release 4.4 Release 4.3 Release 4.2.1 Release 4.2 Release 4.1 Release 4.0 Release 3.0 Release 2.2 Release 2.1 Expand All Collapse All

Element Information Name CollRpt Definition The container for Summarized Voucher and Business Transaction information. DataType Container Attribute Information Attribute Name Use DataType Definition EOD_Ind required 1|0 The indicator denoting whether a file is considered the end-of-day file. IptSysTxt required String [0, 40] The sending trading partner that provides information to a receiving trading partner. SeqNr required String [0, 4] \d+ The number of the item in reference to a sequential number of items. ID required String [0, 80] The unique identifier for a transmission. TrnsmTs required YYYY-MM-DDTHH:MM:SS or may end in 'Z' to reflect UTC (Coordinated Universal Time) The date and time of a transmission. Technical Information Schema version urn:us:gov:treasury Cardinality [1..1] Content Model The <CollRpt> element contains 4 children elements and has a multiple content model where there exists more than one content model (sequence, choice, all or some combination of these three content models). Please review the XML Schema document to fully understand the implications of the multiple content model.

For help, please contact the Treasury Bureau of the Fiscal Service Data Registry team.

Last Updated: 2017-11-15T07:58:41.593-05:00

This web site is informative only and may contain publishing errors/inconsistencies - please carefully review the appropriate XML Schema documents in the Download section.