Files > FEE BASIS INVOICE

name
FEE BASIS INVOICE
number
162.5
location
^FBAAI(
description
This file contains the payment data associated with the inpatient hospital programs of FEE Basis. Per VHA Directive 10-93-142, this file definition should not be modified.
Fields
#NameLocationTypeDetailsIndexDescription
.01number(+)0;1NUMERICBThis field contains the internal entry number for the Fee Basis Invoice.
1invoice date received(+)0;2DATE-TIMEThis field contains the date the correct invoice was received. It is used by Austin for the calculation of any applicable interest payments.
2vendor(+)0;3POINTER161.2CReference to the vendor file, this field contains the name of the vendor associated with this invoice.
3veteran(+)0;4POINTER161DReference the Fee Basis Patient file, this field contains the name of the veteran for which this invoice is established.
4associated 7078/5830;5VARIABLE-POINTER162.4, 162.7This field contains the pointer to the appropriate 7078 or 583 file.
5treatment from date(+)0;6DATE-TIMEInformation in this field indicates the starting date for this invoice. (i.e. the starting treatment date for which this billing covers).
6treatment to date(+)0;7DATE-TIMEInformation in this field indicates the ending date for this invoice. (i.e. the ending treatment date this billing covers).
6.5discharge type code0;21POINTER162.6This field contains the code pertaining to the type of discharge associated with this invoice.
6.6billed charges(+)0;22NUMERICThis field contains cost information on the amount the VA was initially billed by the vendor for an inpatient stay.
6.7payment by medicare/fed agency(+)0;23FREE TEXTAnswer 'Yes' if Medicare or some other federal agency has paid some of the bill for contract hospital.
7amount claimed(+)0;8NUMERICThe portion of the billed charges that the vendor is requesting payment for from the VA. Usually the billed charges and the amount claimed will be the same.
8amount paid(+)0;9NUMERICThe dollar amount that was actually paid to the vendor for the service provided.
9amount suspended0;10NUMERICThe difference between the amount claimed and the amount paid.
10suspend code0;11POINTER161.27If an amount was suspended, the user is requested to indicate the reason for suspense from the selection of suspense codes.
11fee program(+)0;12POINTER161.8This field contains the valid Fee Program associated with this Invoice as contained in the Fee Basis Program file (i.e. Contract Hospital or Community Nursing Home for an inpatient stay).
12payment type code0;13SET OF CODESR:REIMBURSEMENT
V:VENDOR
S:STATISTICAL
SR:STAT-REIMBURSEMENT
An entry of 'R' will indicate the invoice is for a reimbursement to the veteran for services that he/she has already paid. An entry of 'V' will indicate the invoice is for a payment directly to a vendor. An entry of 'S' will indicate the invoice 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.
13reject statusFBREJ;1SET OF CODESP:REJECTED, PENDING ACTION
C:REJECTED, COMPLETED
An entry in this field will indicate that the invoice has been rejected. An entry of 'P' will indicate the invoice has been rejected and it is awaiting action. An entry of 'C' will indicate the invoice has been rejected and action on it has been completed.
14reject reasonFBREJ;2FREE TEXTIf the invoice has a status of rejected, the user will be prompted to enter a reason that the reject has occurred.
15old batch numberFBREJ;3POINTER161.7This field is populated only if there is a reject pending. It will contain the batch number of the old batch associated with the invoice. This is to provide a link back to that batch if the user deletes the reject.
15.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.
15.6reject codeFBREJC;0MULTIPLE162.515The 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 (#14) field.
16void payment0;14SET OF CODESVP:VOIDED PAYMENT
Entry into this field is made when the user indicates the payment must be voided.
16.5reason for voided paymentR;1FREE TEXTThis field is only populated if the Void Payment field is flagged for a void. The user is prompted to enter a reason the payment was voided.
17supervisor who voided0;15POINTER200This field is only populated when the Void Payment field is flagged for a void. The field is stuffed with the user who voided the payment (and in all instances, the user must be a supervisor).
18description of suspension1;0WORD-PROCESSINGThis field is only populated when there is a dollar amount that has been suspended. The user is prompted to enter a description of the suspension in word-processing format.
19date finalized0;16DATE-TIMEADThis field contains the date the invoice was vouchered by Fiscal.
20batch number0;17POINTER161.7This field contains the batch number associated with this invoice. (The batch number that the invoice resides in).
21purpose of visit0;18POINTER161.82Contains the valid Purpose of Visit code as defined in the Fee Basis Purpose of Visit file.
22patient type code0;19SET OF CODES00:SURGICAL
10:MEDICAL
60:HOME NURSING SERVICE
85:PSYCHIATRIC-CONTRACT
86:PSYCHIATRIC
95:NEUROLOGICAL-CONTRACT
96:NEUROLOGICAL
This field requires the entry of the type of treatment being provided to the patient (i.e. Surgical, Medical, Home Nursing Service, etc.)
23primary service facility0;20POINTER4The VA Hospital responsible for that Veterans care.
24discharge drg0;24POINTER80.2This field should contain the discharge DRG that is returned from the Austin Pricer System.
24.5drg weight2;12NUMERICEnter the DRG weight as reported by the Austin Pricer.
25resubmission0;25BOOLEAN1:YES
Entry into this field indicates that this invoice is a resubmission. Failure to annotate an invoice in such a manner would cause Austin to reject the payment as duplicate.
26nvh pricer amount0;26NUMERICThe amount for this payment as determined by the Austin Pricer.
30icd1(+)DX;1POINTER80The first valid ICD code associated with this payment.
30.02poa1POA;1POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD1 field.
31icd2DX;2POINTER80The second valid ICD code (if one exists) associated with this payment.
31.02poa2POA;2POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD2 field.
32icd3DX;3POINTER80The third valid ICD code (if one exists) associated with this payment.
32.02poa3POA;3POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD3 field.
33icd4DX;4POINTER80The fourth valid ICD code (if one exists) associated with this payment.
33.02poa4POA;4POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD4 field.
34icd5DX;5POINTER80The fifth valid ICD code (if one exists) associated with this payment.
34.02poa5POA;5POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD5 field.
35icd6DX;6POINTER80The sixth valid ICD code (if one exists) associated with this payment.
35.02poa6POA;6POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD6 field.
35.1icd7DX;7POINTER80The seventh valid ICD code (if one exists) associated with this payment.
35.12poa7POA;7POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD7 field.
35.2icd8DX;8POINTER80The eighth valid ICD code (if one exists) associated with this payment.
35.22poa8POA;8POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD8 field.
35.3icd9DX;9POINTER80The ninth valid ICD code (if one exists) associated with this payment.
35.32poa9POA;9POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD9 field.
35.4icd10DX;10POINTER80The tenth valid ICD code (if one exists) associated with this payment.
35.42poa10POA;10POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD10 field.
35.5icd11DX;11POINTER80The eleventh valid ICD code (if one exists) associated with this payment.
35.52poa11POA;11POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD11 field.
35.6icd12DX;12POINTER80The twelfth valid ICD code (if one exists) associated with this payment.
35.62poa12POA;12POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD12 field.
35.7icd13DX;13POINTER80The thirteenth valid ICD code (if one exists) associated with this payment.
35.72poa13POA;13POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD13 field.
35.8icd14DX;14POINTER80The fourteenth valid ICD code (if one exists) associated with this payment.
35.82poa14POA;14POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD14 field.
35.9icd15DX;15POINTER80The fifteenth valid ICD code (if one exists) associated with this payment.
35.92poa15POA;15POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD15 field.
36icd16DX;16POINTER80The sixteenth valid ICD code (if one exists) associated with this payment.
36.02poa16POA;16POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD16 field.
36.1icd17DX;17POINTER80The seventeenth valid ICD code (if one exists) associated with this payment.
36.12poa17POA;17POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD17 field.
36.2icd18DX;18POINTER80The eighteenth valid ICD code (if one exists) associated with this payment.
36.22poa18POA;18POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD18 field.
36.3icd19DX;19POINTER80The nineteenth valid ICD code (if one exists) associated with this payment.
36.32poa19POA;19POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD19 field.
36.4icd20DX;20POINTER80The twentieth valid ICD code (if one exists) associated with this payment.
36.42poa20POA;20POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD20 field.
36.5icd21DX;21POINTER80The twenty-first valid ICD code (if one exists) associated with this payment.
36.52poa21POA;21POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD21 field.
36.6icd22DX;22POINTER80The twenty-second valid ICD code (if one exists) associated with this payment.
36.62poa22POA;22POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD22 field.
36.7icd23DX;23POINTER80The twenty-third valid ICD code (if one exists) associated with this payment.
36.72poa23POA;23POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD23 field.
36.8icd24DX;24POINTER80The twenty-fourth valid ICD code (if one exists) associated with this payment.
36.82poa24POA;24POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD24 field.
36.9icd25DX;25POINTER80The twenty-fifth valid ICD code (if one exists) associated with this payment.
36.92poa25POA;25POINTER161.94This field contains the present on admission (POA) indicator for the diagnosis in the ICD25 field.
39admitting diagnosis(+)5;9POINTER80This is the admitting diagnosis code from the claim.
40proc1PROC;1POINTER80.1The first valid procedure code (if one exists) associated with this payment.
41proc2PROC;2POINTER80.1The second valid procedure code (if one exists) associated with this payment.
42proc3PROC;3POINTER80.1The third valid procedure code (if one exists) associated with this payment.
43proc4PROC;4POINTER80.1The fourth valid procedure code (if one exists) associated with this payment.
44proc5PROC;5POINTER80.1The fifth valid procedure code (if one exists) associated with this payment.
44.06proc6PROC;6POINTER80.1The sixth valid procedure code (if one exists) associated with this payment.
44.07proc7PROC;7POINTER80.1The seventh valid procedure code (if one exists) associated with this payment.
44.08proc8PROC;8POINTER80.1The eighth valid procedure code (if one exists) associated with this payment.
44.09proc9PROC;9POINTER80.1The ninth valid procedure code (if one exists) associated with this payment.
44.1proc10PROC;10POINTER80.1The tenth valid procedure code (if one exists) associated with this payment.
44.11proc11PROC;11POINTER80.1The eleventh valid procedure code (if one exists) associated with this payment.
44.12proc12PROC;12POINTER80.1The twelfth valid procedure code (if one exists) associated with this payment.
44.13proc13PROC;13POINTER80.1The thirteenth valid procedure code (if one exists) associated with this payment.
44.14proc14PROC;14POINTER80.1The fourteenth valid procedure code (if one exists) associated with this payment.
44.15proc15PROC;15POINTER80.1The fifteenth valid procedure code (if one exists) associated with this payment.
44.16proc16PROC;16POINTER80.1The sixteenth valid procedure code (if one exists) associated with this payment.
44.17proc17PROC;17POINTER80.1The seventeenth valid procedure code (if one exists) associated with this payment.
44.18proc18PROC;18POINTER80.1The eighteenth valid procedure code (if one exists) associated with this payment.
44.19proc19PROC;19POINTER80.1The nineteenth valid procedure code (if one exists) associated with this payment.
44.2proc20PROC;20POINTER80.1The twentieth valid procedure code (if one exists) associated with this payment.
44.21proc21PROC;21POINTER80.1The twenty-first valid procedure code (if one exists) associated with this payment.
44.22proc22PROC;22POINTER80.1The twenty-second valid procedure code (if one exists) associated with this payment.
44.23proc23PROC;23POINTER80.1The twenty-third valid procedure code (if one exists) associated with this payment.
44.24proc24PROC;24POINTER80.1The twenty-fourth valid procedure code (if one exists) associated with this payment.
44.25proc25PROC;25POINTER80.1The twenty-fifth valid procedure code (if one exists) associated with this payment.
45date paid2;1DATE-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 use the check date beginning with version 3.5 of Fee Basis.
46vendor invoice date(+)2;2DATE-TIMEThis is the date that the vendor issued the invoice.
47prompt pay type2;3SET OF CODES1:MONEY MANAGED
Field is set to 1 if the payment is subject to interest payments (prompt pay).
48check number2;4FREE 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.
49cancellation date2;5DATE-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.
50reason code2;6POINTER162.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.
51cancellation activity2;7SET OF CODESR:WILL BE REPLACED
C:WILL 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.
52disbursed amount2;8NUMERICThis is the dollar amount paid by the treasury, less any interest paid.
53interest amount2;9NUMERICThe interest amount paid on this line item by the treasury.
54covered days(+)2;10NUMERICThis is the number of total number of Inpatient days that the Fee Staff has determined will be paid. Enter number of inpatient days to be paid.
55patient control number2;11FREE TEXTPlease enter the Patient control number. This could be either the Patient Identification Number or Patient Account Number from the vendor's invoice.
56fpps claim id3;1FREE TEXTEnter the entire FPPS Claim ID as shown on the invoice document. (1-32 character text ID created by FPPS system).
57fpps line item3;2FREE TEXTEnter the line item sequence number associated with this charge. Each charge on the FPPS invoice document will have a line item sequence number associated with it. A line item can be entered individually or a group of charges from multiple lines can be entered. If all line items in a group are in numerical sequence, you may enter the first line item sequence number followed by a hyphen and the last line item sequence number. If the grouped charges are not in sequential order, each line item must be entered individually, followed by a comma.
58adjustment8;0MULTIPLE162.558
59remittance remark9;0MULTIPLE162.559
60contract5;8POINTER161.43ACNIf the payment is for contracted services, the contract number can be specified in this field. The selected contract must be active and applicable to the vendor being paid.
61routing number2;13FREE TEXTEnter the financial routing number information that was returned with the payment from Central Fee for Electronic Fund Transfer (EFT) entries. This information will be forwarded to FPPS so that the vendor can be notified of the payment. This field must be 9 characters, including any leading zeros. Note: The Central Fee nightly update will automatically set this field if the data is included in their message.
62account number2;14FREE TEXTEnter the financial account number information that was returned with the payment from Central Fee for Electronic Fund Transfer (EFT) entries. This information will be forwarded to FPPS so that the vendor can be notified of the payment. This field must be 1-17 characters, including any leading zeros. Note: The Central Fee nightly update will automatically set this field if the data is included in their message.
63financial institution2;15FREE TEXTEnter the financial institution name that was returned with the payment from Central Fee for Electronic Fund Transfer (EFT) entries. This information will be forwarded to FPPS so that the vendor can be notified of the payment. Note: The Central Fee nightly update will automatically set this field if the data is included in their message.
64attending prov name4;1FREE TEXTEnter the Attending Provider's name found in the claim information.
65attending prov npi4;2FREE TEXTEnter the Attending Provider's National Provider Identifier (NPI) found in the claim information. This value must be 10 characters, including any leading zeros.
66attending prov taxonomy code4;3FREE TEXTEnter the Attending Provider's Taxonomy code found in the claim information. This value must be 10 characters, including any leading zeros.
67operating prov name4;4FREE TEXTEnter the Operating Provider's name found in the claim information.
68operating prov npi4;5FREE TEXTEnter the Operating Provider's National Provider Identifier (NPI) found in the claim information. This value must be 10 characters, including any leading zeros.
69rendering prov name4;6FREE TEXTEnter the Rendering Provider's name found in the claim information.
70rendering prov npi4;7FREE TEXTEnter the Rendering Provider's National Provider Identifier (NPI) found in the claim information. This value must be 10 characters, including any leading zeros.
71rendering prov taxonomy code4;8FREE TEXTEnter the Rendering Provider's Taxonomy code found in the claim information. This value must be 10 characters, including any leading zeros.
72servicing prov name4;9FREE TEXTEnter the Servicing Provider's name found in the claim information.
73servicing prov npi4;10FREE TEXTEnter the Servicing Provider's National Provider Identifier (NPI) found in the claim information. This value must be 10 characters, including any leading zeros.
74referring prov name4;11FREE TEXTEnter the Referring Provider's name found in the claim information.
75referring prov npi4;12FREE TEXTEnter the Referring Provider's National Provider Identifier (NPI) found in the claim information. This value must be 10 characters, including any leading zeros.
79line item rendering provRPROV;0MULTIPLE162.579This multiple stores Rendering Provider information that is specific to a line item on the claim. A record should only be added to this multiple if the Rendering Provider for a line item is different from the Rendering Provider at the claim level. Example, if the PROC1 code is entered and has a different Rendering Provider than the claim Rendering Provider (field #70) the multiple will store the different data. Line item #1 would be referencing PROC1; Line Item #5 would reference PROC5.
80servicing facility address5;1FREE TEXTEnter the Servicing Facility street address found in the claim information.
81servicing facility city5;2FREE TEXTEnter the Servicing Facility city found in the claim information.
82servicing facility state5;3POINTER5Enter the Servicing Facility state found in the claim information.
83servicing facility zip5;4FREE TEXTEnter the Servicing Facility zip code, in either the 5 digit format (e.g. 12345) or 9 digit format (e.g. 12345-6789 or 123456789).
85unique claim identifier5;5FREE TEXTThis field contains a unique identifier for tracking claims. Fee5010 Project.
86dod invoice number5;7FREE TEXTDODIThe DoD invoice number that is associated with the invoice. Note that if the invoice vendor is not a federal vendor then this field is null.
87ipac vendor agreement5;10POINTER161.95IPACThe IPAC Agreement record that is associated with this invoice. Note that if the invoice vendor is not a federal vendor this is field is null.

Not Referenced