Files > TRAVEL PAYMENT DATE

parent
162
name
TRAVEL PAYMENT DATE
number
162.04
Fields
#NameLocationTypeDetailsIndexDescription
.01travel payment date0;1DATE-TIMEABThe date the travel being paid was performed.
1travel batch number(+)0;2POINTER161.7ADThe batch number that this travel payment will be associated with.
2travel amount(+)0;3NUMERICThe amount to be paid for the travel.
3travel obligation number0;4FREE TEXTThe obligation number identifying the funds from which this travel payment will be paid.
3.5payment type code0;13SET OF CODESR:REIMBURSEMENT
S:STATISTICAL
SR:STAT-REIMBURSEMENT
V:VENDOR
An entry of 'R' will indicate the travel is for a reimbursement to the veteran. An entry of 'S' will indicate the travel was paid "out of system" to a vendor and allows the update of the payment history files. An entry of 'SR' will indicate a statistical reimbursement to a party other than the vendor. An entry of 'V' or 'S' is not used currently. Travel is only paid to a veteran.
4reject statusFBREJ;1SET OF CODESP:REJECTED, PENDING
C:REJECTED, COMPLETED
Identifies whether this line item is in a reject status pending assignment to another batch.
5reject reasonFBREJ;2FREE TEXTThe reason this line item was rejected for payment. Usually, the error code identified by the Austin Central Fee system is entered.
6old batch numberFBREJ;3POINTER161.7AGThe batch number this line item was associated with prior to being rejected.
6.3interface rejectFBREJ;4BOOLEAN1:YES
This field is populated by the FBAA BATCH SERVER and FBAA REJECT SERVER server options when a payment line item is rejected via the interface with Central Fee. This field is used to distinguish line items that were locally rejected from those that were rejected by a downstream system. This field is not populated for a local reject.
6.6reject codeFBREJC;0MULTIPLE162.041The REJECT CODE multiple is populated with one to four reject codes by the FBAA BATCH SERVER and FBAA REJECT SERVER server options when a line item is rejected via the interface with Central Fee. The REJECT CODE multiple is not used for local rejects. The reason for a local reject is entered into the REJECT REASON (#5) field.
7date finalized0;5DATE-TIMEALIndicates the date and time the travel payment was vouchered by Fiscal.
8date paid0;6DATE-TIMEThis is the date of the check, as issued by the treasury. This information will be passed back to DHCP from the Financial Management System (FMS) when the check is issued to the vendor. This field will be populated beginning in version 3.5 of Fee Basis.
9check number0;7FREE TEXTContains the check number as issued by the treasury. This field is updated after the check is issued, through a server option that records actual payment information for each Fee payment made.
10cancellation date0;8DATE-TIMEThis is the date the treasury cancelled the check. This field is updated through a server option that records cancellations of previously recorded payment data.
11reason code0;9POINTER162.95This field contains a pointer to the Fee Basis Check Cancellation Reason file. It is populated through a server option that updates the payment record when the treasury cancels a check that was previously payed.
12cancellation activity0;10SET OF CODESR:WILL BE REPLACED
C:WIL BE REISSUED
X:WILL NOT BE REISSUED
This field is populated when a cancellation is recorded for the payment referenced. This field will always remain populated, to indicate that there was cancellation activity on this payment at one time. New payments will replace the cancellation date and reason code fields, but the cancellation activity flag will not be overwritten. This flag will allow the user to know that previous cancellation activity existed, and to review the cancellation history output for further information.
13disbursed amount0;11NUMERICThis is the dollar amount paid by the treasury, less any interest paid.
14interest amount0;12NUMERICThe interest amount paid on this line item by the treasury.

Error: Invalid Global File Type: 162.04