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


Business Message Listing
Transmission
Schedule
TypeA_Details
SameDayPayments
SameDayPayment [1..60]
AccountClassification [0..100]
Payment [1..1]
SameDayPaymentPayeeBankInfo [1..1]
BeneficiaryBankRemarks [0..1]
PaymentRemarks [0..1]
ProcurementDetail [0..1]

Element Information
NameSameDayPayment
DefinitionSame Day Payment detail information
Namespaceurn:us:gov:treas:fms:BusinessTransaction:v4.7
Cardinality[1..60]
Content ModelThe <SameDayPayment> element contains 6 children elements and has a sequence content model. The sequence content model means that there is a particular order to the children elements of the parent element - in this case, the <SameDayPayment> element has a particular order of elements that must be followed.
Attribute NameUseDataTypeDefinition
ID[0..1] String [0, 20]An identifier for the record. For a receiving system, this value can be used to reconcile updates to an existing record and qualify new records. For a sending system, this value can be used to reconcile acknowledgements for the submitted records.
PayeeIdentifier[1..1] [0-9A-Z\-][0-9 A-Z\-]{0,8}The Payee's Taxpayer Identification Number (TIN), Vendor ID, SSN, or other valid Payee ID.
IsTOP_Offset[1..1] 1|0Indicates the payment eligibility of the payment offset
PartyName[0..1] String [1, 47] [A-Z0-9&=,\.\?$\(\)\-][A-Z0-9&= ,\.\?$\(\)\-]*Contains the full name of a payee.
FedwireTypeCode[1..1]10 [Standard Funds], 15 [Foreign Funds]Indicates the type of funds transfer. (For example: Standard, Foreign)
FedwireProductCode[1..1]CTR/ [Customer], BTR/ [Bank]A code that identifies the type of payment recipient (either customer or bank)
PaymentReference[0..1] [A-Z 0-9\-]{1,16}Optional Reference for Payment Information. Formerly RFB. 440(SDPR05:269-284)


For help, please contact the Treasury FMS Enterprise Data Architecture team.
Last Updated: 2011-11-14T05:53:51.296-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.