Treasury :: Bureau of the Fiscal Service
Enterprise Data Architecture
PIR Standard Reporting Format Document Data Exchange


Data Exchange Catalogue
PaymentReporting
PaymentReportingBatch
ReportingDetail
ProcurementDetails
ProcurementDetail [1..100]

Element Information
NameProcurementDetail
DefinitionContains the fields necessary to connect to a Federal Procurement Data System (FPDS) record set at USAspending.gov.
DataTypeContainer
Attribute Information
Attribute NameUseDataTypeDefinition
ProcurementInstrumentIdentifieroptional String [0, 50]The unique identifier for each contract, agreement or order.
ProcurementAgencyIdentifieroptional String [0, 4]This is a code for a governmental agency, but it does not necessarily represent the agency that issued the contract. Instead, it serves only as part of the unique identification for Federal Procurement Data System awards records.
IDV_ProcurementInstrumentIdentifieroptional String [0, 50]When reporting orders under Indefinite Delivery Vehicles (IDV) such as a GWAC, IDC, FSS, BOA, or BPA, report the Procurement Instrument Identifier (Contract Number or Agreement Number) of the IDV. For the initial load of a BPA under a FSS, this is the FSS contract number. Note: BOAs and BPAs are with industry and not with other Federal Agencies.
IDV_ProcurementAgencyIdentifieroptional String [0, 4]This is a code for an agency, but it does not necessarily represent the agency that issued the contract. Instead, it serves as part of the unique identification for Federal Procurement Data System IDV records. For awards records, it partially identifies a linked IDV record.
AmountoptionalDecimal [20, 2]Min Inclusive: 0.00The transaction amount.
Technical Information
Schema versionurn:us:gov:treasury
Cardinality[1..100]
Content ModelThe <ProcurementDetail> element does not contain any further nested children elements.



For help, please contact the Treasury Bureau of the Fiscal Service Data Registry team.
Last Updated: 2015-01-17T06:09:20.132-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.