Treasury :: Financial Management Service
Enterprise Data Architecture
Transmission Business Message


Business Message Listing
Transmission
Schedule
PaymentDetail [0..unbounded]
PartyDetail [0..unbounded]
PaymentClassification [0..100]
Address [0..1]
ProcurementDetails [0..1]
ACH_Payment [1..1]
CheckPayment [1..1]
WirePayment [1..1]

Element Information
NamePaymentDetail
DefinitionContains pertinent information about a specific payment.
Namespaceurn:us:gov:treasury
Cardinality[0..unbounded]
Content ModelThe <PaymentDetail> element contains 7 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.
Attribute NameUseDataTypeDefinition
IsTOP_Offset[1..1] 1|0Indicates the payment eligibility of the payment offset.
EligibleForOffsetAmount[0..1]Decimal [20, 2]Indicates the amount of the payment that is eligible for offset. This is sent to TOP for offsetting purposes.
AgencyPaymentTypeCode[0..1] [1] [A-Z0-9]Internal agency code used to identify the type of payment within the specific agency.
DiscretionaryText[0..1] String [0, 100] [A-Z0-9"&'>< !#$%\(\)\+\*,\./:;=?@\[\]\\\^_`{}\|~\-]*Free-form field for agency’s use in reconciling the payment using PACER.
Amount[1..1]Decimal [20, 2]The transaction amount.
PayeeName[0..1] String [0, 47]The person to which the payment instrument is made payable.
PayeeIdentifier[0..1] String [0, 16]Account number used internally by an agency to identify a payee.
PaymentID[1..1] String [0, 20]Identifier assigned by the agency that is unique within the Schedule. When combined with the Schedule Number, AgencyLocationCode, and Fiscal Year, this makes a globally unique identifier for the payment.


For help, please contact the Treasury FMS Enterprise Data Architecture team.
Last Updated: 2012-06-28T19:02:15.453-04: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.