Files > SERVICE PROVIDED

parent
162.02
name
SERVICE PROVIDED
number
162.03
Fields
#NameLocationTypeDetailsIndexDescription
.01service provided(+)0;1POINTER81BThe Current Procedural Terminology Code (CPT Code) as specified on the vendors invoice identifying the service the vendor provided to the veteran.
.05ipac agreement3;6POINTER161.95IPACThis is the pointer to the IPAC Agreement file that is associated with the invoice.
.055dod invoice number3;7FREE TEXTDODIThe DoD invoice number that is associated with this VistA invoice. Note that one DoD invoice number may have more than one VistA invoice.
1amount claimed(+)0;2NUMERICThe amount the vendor is billing us for this service provided.
2amount paid(+)0;3NUMERICThe amount that the VA is going to pay for this service provided, not to exceed the amount entered in the AMOUNT CLAIMED (#1) field. Users holding the "FBAASUPERVISOR" key may override this limit.
3amount suspended0;4NUMERICThe portion of the vendor's claimed amount that the VA will not pay for various reasons. This amount is usually the difference between the vendor's amount claimed and the amount paid.
3.5date suspended0;11DATE-TIMEThe date that this payment is suspended.
4suspend code0;5POINTER161.27The code that identifies why the amount paid was less than the amount claimed. The valid list of codes are contained in the Fee Basis Suspension file.
5date finalized0;6DATE-TIMEAKThe date that this payment line item was finalized (Certified) by the Fee Supervisor.
6clerk(+)0;7POINTER200The Fee clerk who entered in the payment data.
7batch number0;8POINTER161.7ACThe batch number with which this payment was associated. If the batch file has been purged this may be blank.
8obligation number(+)0;10FREE TEXTThe obligation number identifying which funds this payment will be paid with.
12date paid0;14DATE-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. Entries prior to version 3.5 are the date the system automatically entered when the payment line item was queued to be transmitted to the Austin Automation Center for payment.
13date correct invoice received(+)0;15DATE-TIMEDate that the VA receives what it feels to be a complete/correct invoice. This date is very important since it is the date used by the Central Fee system in determining if interest should be paid because of untimely processing by VA. Requirements for the prompt payment act apply.
14invoice number0;16NUMERICCAn automatically generated number associated with a vendor's bill.
15patient type code(+)0;17SET OF CODES00:SURGICAL
10:MEDICAL
60:HOME NURSING SERVICE
85:PSYCHIATRIC-CONTRACT
86:PSYCHIATRIC
95:NEUROLOGICAL-CONTACT
96:NEUROLOGICAL
The patient's type code (ie medical, surgical) related to this payment line item. This is based on the authorization that is selected during the payment process.
16purpose of visit(+)0;18POINTER161.82This identifies the purpose that the veteran received the service provided. This data is obtained from the authorization data for the patient, at the time of payment entry.
17treatment type code(+)0;19SET OF CODES1:SHORT TERM FEE STATUS
2:HOME NURSING SERVICE
3:I.D. CARD STATUS
The treatment type code this payment is related to. It is obtained from the authorization data for the patient which was selected at the time of payment entry.
18payment type code(+)0;20SET OF CODESR:REIMBURSEMENT
S:STATISTICAL
V:VENDOR
SR:STAT-REIMBURSEMENT
Identifies whether this is a payment to a vendor, a reimbursement to the veteran, a statistical payment which only updates veteran year-to-date amounts and results in NO payment and a statistical reimbursement which allows the user to update payment record with a reimbursement paid out of system.
19reject statusFBREJ;1SET OF CODESP:REJECTED, PENDING
C:REJECTED, COMPLETED
Identifies whether this line item has been rejected and is pending assignment to another batch.
20reject reasonFBREJ;2FREE TEXTThe reason this line item was rejected for payment. Normally, the Austin reject code is entered.
21old batch numberFBREJ;3POINTER161.7AHThe batch number this line item was associated with before the line item was rejected.
21.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.
21.6reject codeFBREJC;0MULTIPLE162.031The 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 (#20) field.
22description of suspension1;0WORD-PROCESSINGThis field is used only when the suspend code entered is '4' meaning 'Other'. This allows the entering of the reason that the payment amount was not in full. This will be printed on the suspense letter.
23fee program0;9POINTER161.8The Fee program that this line item is associated with (ie Outpatient Medical, Contract Hospital).
24void payment0;21SET OF CODESVP:VOID
This field is set when a payment was made in error and the site has initiated a bill of collection to retrieve the dollars expended. The ability to void a payment is restricted to the holder of the FBAASUPERVISOR security key.
24.5reason for voided paymentR;1FREE TEXTThis field will allow the Fee Supervisor to store the reason why they had to void a payment.
25supervisor0;22POINTER200This is the Fee Supervisor who cancelled(voided) the payment.
26primary service facility0;12POINTER4The VA Hospital responsible for the veterans care.
27associated 7078/5830;13VARIABLE-POINTER162.4, 162.7AMContains the related 7078 or 583 if an unauthorized claim.
28primary diagnosis0;23POINTER80This field contains the primary diagnosis of the patient for the service provided.
29va type of service0;24POINTER163.85The information recorded in this field will be sent with the payment record to the Austin DPC. It will allow the program office to do some comparisons between VA supplied services and those supplied by Fee Basis.
30place of service0;25POINTER353.1This field determines where the service was administered to the veteran.
31hcfa type of service0;26POINTER353.2This information will be used to determine payment amounts in the future. It is currently asked on the HCFA 1500 form.
32service connected condition?0;27FREE TEXTIndicates whether the service provided was for a Service Connected condition. Answer 'Yes' if service provided was for a Service Connected condition, 'No' if eligible under NSC such as Aid and Attendance.
33vendor invoice date(+)2;1DATE-TIMEThis is the date that the vendor issued the invoice.
34prompt pay type2;2SET OF CODES1:MONEY MANAGED
Field is set to 1 if the payment is subject to interest payments (prompt pay). Otherwise it remains blank.
35check number2;3FREE 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.
36cancellation date2;4DATE-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.
37reason code2;5POINTER162.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.
38cancellation activity2;6SET 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.
40disbursed amount2;8NUMERICThis is the dollar amount paid by the treasury, less any interest paid.
41interest amount2;9NUMERICThe interest amount paid on this line item by the treasury.
42site of service zip code(+)2;10FREE TEXTZip Code of the location where the service was actually performed.
43anesthesia time (minutes)2;11NUMERICEnter time billed for an anesthesia service in minutes. The bill may specify anesthesia units which will need to be converted to minutes.
44fee schedule amount2;12NUMERICThis is the dollar amount obtained from a fee schedule for the service provided.
45fee schedule2;13SET OF CODESF:VA FEE SCHEDULE
R:RBRVS FEE SCHEDULE
Specifies which fee schedule was used to obtain the fee schedule amount for this service provided.
46cpt modifierM;0MULTIPLE162.06
47units paid(+)2;14NUMERICUnits of service being paid for this line item if any payment is being made for the line item. If payment disapproved for the line item then enter the units of service that were billed.
48revenue code2;15POINTER399.2Revenue code is a 3-digit code associated with itemized charges on a UB92 billing invoice. A revenue code should be entered if a CPT/HCPCS code was not specified for the line item. If both revenue code and a CPT/HCPCS code have been entered for a line item, the revenue code will be considered the more accurate description of the service.
49patient account number2;16FREE TEXTPlease enter the Patient control number. This could be either the Patient Identification Number or Patient Account Number from the vendor's invoice.
50fpps claim id3;1FREE TEXTEnter the entire FPPS Claim ID as shown on the invoice document. (1-32 character text ID created by FPPS system).
51fpps 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.
52adjustment7;0MULTIPLE162.07
53remittance remark8;0MULTIPLE162.08
54contract3;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.
55routing number2;17FREE 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.
56account number2;18FREE 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.
57financial institution2;19FREE 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.
58attending prov name4;1FREE TEXTEnter the Attending Provider's name found in the claim information.
59attending 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.
60attending 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.
61operating prov name4;4FREE TEXTEnter the Operating Provider's name found in the claim information.
62operating 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.
63rendering prov name4;6FREE TEXTEnter the Rendering Provider's name found in the claim information.
64rendering 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.
65rendering 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.
66servicing prov name4;9FREE TEXTEnter the Servicing Provider's name found in the claim information.
67servicing 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.
68referring prov name4;11FREE TEXTEnter the Referring Provider's name found in the claim information.
69referring prov npi4;12FREE TEXTEnter the Referring Provider's National Provider Identifier (NPI) found in the claim information. This value must be 10 characters, including ay leading zeros.
73li rendering prov name3;3FREE TEXTEnter the associated line item Rendering Provider's name found in the line item level claim information. Note: This field is only necessary if the line item Rendering Provider is different than the claim Rendering Provider.
74li rendering prov npi3;4FREE TEXTEnter the associated line item Rendering Provider's name found in the line item level claim information. This value must be 10 characters, including any leading zeros. Note: This field is only necessary if the line item Rendering Provider is different than the claim Rendering Provider.
75li rendering prov taxonomy3;5FREE TEXTEnter the associated line item Rendering Provider's Taxonomy code found in the line item level of the claim information. This value must be 10 characters, including any leading zeros. Note: This field is only necessary if the line item Rendering Provider is different than the claim Rendering Provider.
76servicing facility address5;1FREE TEXTEnter the Servicing Facility street address found in the claim information.
77servicing facility city5;2FREE TEXTEnter the Servicing Facility city found in the claim information.
78servicing facility state5;3POINTER5Enter the Servicing Facility state found in the claim information.
79servicing 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).
81unique claim identifier5;5FREE TEXTThis field contains a unique identifier for tracking claims. Fee5010 Project.

Error: Invalid Global File Type: 162.03