| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | transaction(+) | 0;1 | NUMERIC | B | This DINUM field is the entry number for each transaction within a receipt. This field is sequentially assigned by the computer. | |
| .02 | confirmation # | 0;2 | FREE TEXT | This data should reflect the confirmation number that the credit card machine returns when entering credit card payments. | ||
| .03 | account(+) | 0;3 | VARIABLE-POINTER | 430, 2 | AACCT | This field is used to store where the payment should be applied. If the payment is associated to a specific bill, then the payment will be applied to the bill first and any money left over will be applied to any other bills the patient has remaining. If the bill is not a patient bill, then the money will be applied to the specific bill and any money left over will be refunded. If this field is associated with a Patient, then the program will automatically search the patient bills and apply payments to their respective bills until the payment is exhausted. |
| .04 | payment amount(+) | 0;4 | NUMERIC | This field is the amount of payment to be posted to A/R. | ||
| .05 | amount processed | 0;5 | NUMERIC | Once payments begin to post to bills, this field will reflect the amount of payment actually processed. For example, if the payment amount is $20.00 and only $15.00 of the payment could be applied, this field would reflect the $15.00 processed. | ||
| .06 | date of payment(+) | 0;6 | DATE-TIME | Date of Payment represents the date the payment was received and should be credited to the account. For example, if the payment was received yesterday, but due to time-delays is being input today, this field should be set to T-1 (yesterday). This is necessary so the patient will get credit for paying bills on time. If the patients' payment date was, for example, 5/10/92 and the payment was received 5/9/92 but is being input on 5/12/92, this field should have 5/9/92. If 5/12/92 is entered, the patient will be incorrectly charged interest and administrative charges. | ||
| .07 | check # | 0;7 | FREE TEXT | If available the check # should be entered for check payments. This information will be valuable for tracking 'lost' payments or to provide information for patient inquiries. The check number will be logged with the payment transaction for each bill to which the payment is applied. | ||
| .08 | check bank/routing # | 0;8 | FREE TEXT | If available, the bank # should be entered for check payments. This information will be valuable for tracking 'lost' payments or to provide information for patient inquiries. The check number will be logged with the payment transaction for each bill to which the payment is applied. | ||
| .09 | patient name or bill number | 0;9 | FREE TEXT | |||
| .1 | date of check | 0;10 | DATE-TIME | If available, the date appearing at the top of the check should be entered for check payments. This information will be valuable for tracking 'lost' payments or to provide information for patient inquiries. The Date of Check will be logged with the payment transaction for each bill to which payment is applied. | ||
| .11 | credit card # | 0;11 | FREE TEXT | If available, the credit card # should be entered for credit card payments. This information will be valuable for tracking 'lost' payments or to provide information for patient inquiries. The Credit Card number will be logged with the payment transaction for each bill to which payment is applied. | ||
| .12 | entered by(+) | 0;12 | POINTER | 200 | This field contains the person who entered the payment into the AR system. | |
| .13 | check account # | 0;13 | FREE TEXT | This field is used to store the account number from a check. | ||
| .14 | edited by | 0;14 | POINTER | 200 | This field contains the person who edited the payment entry into the AR system. | |
| .21 | account lookup | 2;1 | FREE TEXT | This field is used to store the account lookup information. The account lookup information is obtained from automatic payment processing. The account lookup information may not be successful in finding the correct account and is stored for manual linking of the account by the user. | ||
| .22 | batch number | 2;2 | NUMERIC | The batch number in combination with the sequence number is supplied by automatic payment processing and is used to identify the payment at the central bank. | ||
| .23 | sequence number | 2;3 | NUMERIC | The sequence number in combination with the batch number is supplied by automatic payment processing and is used to identify the payment at the central bank. | ||
| .24 | payment type | 2;4 | SET OF CODES | 1:CASH 2:CHECK 3:CREDIT CARD | This field is used to identify the type of payment used by automatic payment processing. | |
| .25 | unapplied deposit number | 2;5 | FREE TEXT | This field stores the unapplied deposit number used on the Cash Receipt document when referencing the suspense fund. | ||
| .26 | clear suspense fms doc id# | 2;6 | FREE TEXT | This field is used to enter the FMS Document ID Number used to clear a payment from suspense in FMS. | ||
| .27 | era worklist sequence | 0;27 | NUMERIC | This is the ien of the entry in file 344.491 that was used to create this line in the receipt. | ||
| .28 | auto decrease adjustment | 0;28 | BOOLEAN | 0:NO 1:YES | This is the flag that indicates the EOB Worklist has a pending decrease adjustment for this payment. | |
| 1.01 | posting error | 1;1 | FREE TEXT | If a payment transaction cannot be posted to a bill, this field will contain the type of problem encountered. | ||
| 1.02 | comment | 1;2 | FREE TEXT | This field is used to enter comments for payments cancelled or unapplied. |
Error: Invalid Global File Type: 344.01