Avatar PM 2022 Monthly Release 2022.03.01 Acceptance Tests

• Please contact your Netsmart representative for assistance to enable credit card functionality.
• The following registry setting has a value of 'Y': Avatar PM--->Billing->Remittance Processing->->->Enable Credit Card Processing.
• General Information regarding credit card payments: At the current time, payments can be accepted from 'Deposit Entry', 'Front Desk - Check in' section only, and 'Scheduling Calendar - Check in' section only.
• In the 'Credit Care Device Setup' section:
• Note: Only one device can have a value of 'Yes' in 'Is this a Back Office MID?' and a value of 'Yes' in 'Active Device'.
• Note: Each device must have a unique 'Device Name'.
• Note: No grid rows may be deleted. Use the 'Active Device' field to set the value to 'Yes' or 'No'. Devices with either value will continue to display in the grid.
• Note: The grid displays inactive devices first, followed by active devices sorted by 'Device Name'.
• Note: The grid may be sorted by double clicking any column header in the grid.
• Note: The value of any submitted field, except device name, may be changed by clicking on the row in the grid and changing the value in the data entry fields.
• No changes can be made to a submitted device name. If needed, make the device inactive and create a new device.
• Note: The following special characters may not be used in the 'Device Name', 'Merchant ID (MID)', or 'Device Serial Number' fields:
• & - ampersand
• < - less than
• > - greater than
• ' - single quote
• " - double quote

1. Open 'Credit Card Configuration’.
2. Enter the desired value in 'Populate Receipt Number with Credit Card Payment Reference Number'.
3. Enter the desired value in 'Default User ID for myHealthPointe Credit Card and ACH Payments'.
4. Enter the desired value in 'Default Posting Code for myHealthPointe Credit Card Payments'.
5. Enter the desired value in 'Default Posting Code for myHealthPointe ACH Payments'.
6. Select the desired value in 'Payments Received From myHealthPointe'.
7. Set the section to 'Credit Card Device Setup'.
8. Click [New Row].
9. Enter the desired value in 'Device Name'.
10. Enter the desired value in 'Device Description'.
11. Enter the desired value in 'Merchant ID (MID)'.
12. Select 'Yes' in 'Is this a Back Office MID?'.
13. If desired, enter the desired value in 'Device Serial Number'.
14. If desired, select the desired value in 'Site'.
15. Select 'Yes' in 'Active Device'.
16. Click [New Row].
17. Enter the desired value in 'Device Name'.
18. Enter the desired value in 'Device Description'.
19. Enter the desired value in 'Merchant ID (MID)'.
20. Select 'No' in 'Is this a Back Office MID?'.
21. Enter the desired value in 'Device Serial Number'.
22. Select the desired value in 'Site'.
23. Select 'Yes' in 'Active Device'.
24. Click [Submit].
25. Repeat steps 16 - 23 for each additional device.
26. If desired, select the row for the device with 'Yes' in 'Is this a Back Office MID?' and select 'No' in 'Active Device'.
27. Click [New Row].
28. Enter the desired value in 'Device Name'.
29. Enter the desired value in 'Device Description'.
30. Enter the desired value in 'Merchant ID (MID)'.
31. Select 'Yes' in 'Is this a Back Office MID?'.
32. Do not enter a value in 'Device Serial Number'.
33. Do not enter a value in 'Site'.
34. Select 'Yes' in 'Active Device'.
35. Click [Submit].

• Please review the 'Credit Card Processing' configuration guide which will be located on the Netsmart Wiki, in myAvatar, Avatar Training Guides.
• Credit Card Processing Configuration has been used to create ‘Device 1’ with a value of ‘No’ in ‘Is this a Back Office MID?’.
• Credit Card Processing Configuration has been used to create ‘Device 2’ with a value of ‘Yes’ in ‘Is this a Back Office MID?’.
• 'Service Code 1': configure a service code that will be used as the 'Pre Payment Service Code'. The 'Group Code' and 'Covered Charge Category should both be non-billable. There will be no 'Service Fee/Cross Reference Maintenance' record.
• 'Posting/Adjustment Codes Definition 1': configure a payment posting code with a value of 'Credit Card Posting Code in 'Is this a Credit Card or ACH Posting Code'.
• The following registry setting has a value of 'Y': Avatar PM--->Billing->Remittance Processing->->-> Enable Credit Card Processing Functionality.
• The following registry setting has a value of ‘Service Code 1’: Avatar PM->Scheduling->Front Desk->->->Pre Payment Service Code.
• The following registry setting has a value of 'Y': Avatar PM->Scheduling->Front Desk->->->Allow Using Front Desk With Scheduling Calendar.
• Guarantors/Payors 1: Has a 'Financial Class' of 'Self Pay'.
• Client 1:
• Note the client ID.
• Client has one episode/program.
• Is assigned Guarantors/Payors 1 in 'Financial Eligibility, with a daily deductible of $10.00.
• Use 'Client Ledger' to verify that client has a positive amount for 'Guarantors/Payors 1 in 'TOTAL BALANCE BY GUARANTOR (last page of the report). Note the amount.
• Client has an appointment on the current date that is paid, using a credit card, in the amount of $10.00, during 'Scheduling Calendar Check In'.
• Client 2:
• Note the client ID.
• Client has one episode/program.
• Is assigned Guarantors/Payors 1 in 'Financial Eligibility, with a daily deductible of $10.00.
• Use 'Client Ledger' to verify that client has a negative amount for Guarantors/Payors 1 in 'TOTAL BALANCE BY GUARANTOR (last page of the report) Note the amount.
• Client has an appointment on the current date that is paid, using a credit card, in the amount of $10.00, during 'Front Desk Check In'.
• Client 3:
• Note the client ID.
• Client has one episode/program.
• Is assigned Guarantors/Payors 1 in 'Financial Eligibility, with a daily deductible of $10.00.
• Use 'Client Ledger' to verify that client has a positive amount for Guarantors/Payors 1 in 'TOTAL BALANCE BY GUARANTOR (last page of the report). Note the amount.
• A credit card payment is processed in ‘Deposit Entry’ in the amount of $10.00.

1. Open CareFabric Monitor'.
2. Set 'From Date' to current date.
3. Set ''Through Date' to current date.
4. Select 'Client 1' in 'Client ID'.
5. Click 'Click To View Record'.
6. Select the 'CardConnectBalanceUpdated' event.
7. Validate that the 'accountID' is equal to 'Client 1'.
8. Validate that 'cardConnectPayment' is equal to 'null'.
9. Validate that 'currentBalance' is equal to $10.00 less than the 'Client Ledger' amount notes for 'Client 1'.
10. Click [X] on the report.
11. Select 'Client 2' in 'Client ID'.
12. Click 'Click To View Record'.
13. Select the 'CardConnectBalanceUpdated' event.
14. Validate that the 'accountID' is equal to 'Client 2'.
15. Validate that 'cardConnectPayment' is equal to 'null'.
16. Validate that 'currentBalance' is a negative amount that is $10.00 more than the 'Client Ledger' amount notes for 'Client 2'.
17. Click [X] on the report.
18. Select 'Client 3' in 'Client ID'.
19. Click 'Click To View Record'.
20. Select the 'CardConnectBalanceUpdated' event.
21. Validate that the 'accountID' is equal to 'Client 3'.
22. Validate that 'cardConnectPayment' is equal to 'null'.
23. Validate that 'currentBalance' is equal to $10.00 less than the 'Client Ledger' amount notes for 'Client 1'.
24. Click [X] on the report.
25. Click [X] on the form.

• Registry Settings:
• Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement = Y.
• Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged = ‘0'.
• Dictionary Update:
• Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
• Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
• Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
• Posting/Adjustment Codes Definitions:
• 'Payment' definitions exist. The 'Payment' definition may be a 'Credit' (payment) or a 'Debit' (reversal). The definitions may have a value in the ‘Payment Acknowledgement Type’ field. Only 'Payment' definitions will be available in the 'Payment Acknowledgement' section of the 'Payment Acknowledgement' form.
• 'Adjustment' definitions exist. The definitions may have a value in the ‘Payment Acknowledgement Type’ field. All ‘Adjustment’ and 'Payment' definitions will be available in the ‘Payment Acknowledgement’ form in the ‘Post Payment Accounting Entry' section of the 'Payment Acknowledgement' form.
• User Definition has been used to give the tester access to the 'Payment Acknowledgement' form and the ‘SYSTEM.unacknowledged_payments’ table.
• Agency uses the myHealthPointe payment portal to accept patient electronic payments.
• Clients:
• Client 1:
• Is enrolled in myAvatar and has an outstanding Self-Pay balance.
• Payment is made in the myHealthPointe payment portal. Note all information regarding the payment.
• Client 2: Is enrolled in myAvatar and has an outstanding Self-Pay balance.
• Tester can create a query of SQL tables.

1. Create a query of the 'SYSTEM.billing_pay_adj_history' table, specific to 'Client 1' using the 'PATID'.
2. Validate the data for the following fields and any other desired fields: 'GUARANTOR_ID', 'date_of_payment', 'payment_amount', and 'option_id' which will contain 'PatientPortal' indicating that the payment was made in the myHealthPointe payment portal.
3. Open 'CareFabric Monitor'.
4. Validate the PatientPortalPaymentProcessed dialog contains "1. Payment Amount 2. Payment method: ACH or CC 3. Account ID 4. Transactional ID".
5. Open 'Client Ledger' and process the report.
6. Validate that the payment displays in the report.
7. Close the report.
8. Close the form.
9. Open 'Registry Settings'.
10. Change the value of the 'Prevent Posting Payments Unless Payment has been Acknowledged' registry setting to include minimum values of '5&6',
11. Click [Submit].
12. Click [OK].
13. Click [No].
14. A payment is made in the myHealthPointe payment portal. Note all information regarding the payment.
15. Create a query of the 'SYSTEM.unacknowledged_payments' table, specific to Client 2, using the 'PATID'.
16. Validate that payment data is correct. Save the query.
17. Open 'Client Ledger' and process the report.
18. Validate that the payment does not display in the report.
19. Close the report.
20. Close the form.
21. Open the 'Payment Acknowledgement' form.
22. Select the 'Post Front Office and myHP Payments' section.
23. Click 'T' in 'Payment Collection Date'.
24. Select desired value in 'Treatment Service'.
25. Select 'myHP' in 'Type'.
26. Click [Review].
27. Select the row specific to 'Client 2'.
28. Click [OK].
29. Enter desired 'Batch Number'.
30. Enter desired 'Deposit Date'.
31. Select desired 'Category'.
32. Enter desired 'Bank Ref#'.
33. Enter desired 'Comments'.
34. Click [Post].
35. Refresh the query of the 'SYSTEM.unacknowledged_payments' table, specific to Client 2.
36. Validate that the table no longer contains data for 'Client 2'.
37. Create a query of the 'SYSTEM.billing_pay_adj_history' table, specific to 'Client 2' using the 'PATID'.
38. Validate the data for the following fields and any other desired fields: 'GUARANTOR_ID', 'date_of_payment', 'payment_amount', and 'option_id' which will contain 'PatientPortal' indicating that the payment was made in the myHealthPointe payment portal.
39. Open 'CareFabric Monitor'.
40. Validate the PatientPortalPaymentProcessed dialog contains "1. Payment Amount 2. Payment method: ACH or CC 3. Account ID 4. Transactional ID".
41. Open 'Client Ledger' and process the report.
42. Validate that the payment displays in the report.
43. Close the report.
44. Close the form.

• Agency uses the myHealthPointe payment portal to accept patient electronic payments.
• Client is enrolled in myAvatar and has an outstanding Self-Pay balance.
• Payment is made in the myHealthPointe payment portal. Note all information regarding the payment.
• Tester can create a query of SQL tables

1. Create a query of the 'SYSTEM.billing_pay_adj_history' table, specific to the client using the 'PATID'.
2. Validate the data for the following fields and any other desired fields: 'GUARANTOR_ID', 'date_of_payment', 'payment_amount', and 'option_id' which will contain 'PatientPortal' indicating that the payment was made in the myHealthPointe payment portal.
3. Open 'CareFabric Monitor'.
4. Validate the PatientPortalPaymentProcessed dialog contains "1. Payment Amount 2. Payment method: ACH or CC 3. Account ID 4. Transactional ID"

• Registry Settings:
• Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement = Y.
• Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged = ‘0'.
• Dictionary Update:
• Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
• Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
• Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
• Posting/Adjustment Codes Definitions:
• 'Payment' definitions exist. The 'Payment' definition may be a 'Credit' (payment) or a 'Debit' (reversal). The definitions may have a value in the ‘Payment Acknowledgement Type’ field. Only 'Payment' definitions will be available in the 'Payment Acknowledgement' section of the 'Payment Acknowledgement' form.
• 'Adjustment' definitions exist. The definitions may have a value in the ‘Payment Acknowledgement Type’ field. All ‘Adjustment’ and 'Payment' definitions will be available in the ‘Payment Acknowledgement’ form in the ‘Post Payment Accounting Entry' section of the 'Payment Acknowledgement' form.
• User Definition has been used to give the tester access to the 'Payment Acknowledgement' form and the ‘SYSTEM.unacknowledged_payments’ table.
• Agency uses the myHealthPointe payment portal to accept patient electronic payments.
• Clients:
• Client 1:
• Is enrolled in myAvatar and has an outstanding Self-Pay balance.
• Payment is made in the myHealthPointe payment portal. Note all information regarding the payment.
• Client 2: Is enrolled in myAvatar and has an outstanding Self-Pay balance.
• Tester can create a query of SQL tables.

1. Create a query of the 'SYSTEM.billing_pay_adj_history' table, specific to 'Client 1' using the 'PATID'.
2. Validate the data for the following fields and any other desired fields: 'GUARANTOR_ID', 'date_of_payment', 'payment_amount', and 'option_id' which will contain 'PatientPortal' indicating that the payment was made in the myHealthPointe payment portal.
3. Open 'CareFabric Monitor'.
4. Validate the PatientPortalPaymentProcessed dialog contains "1. Payment Amount 2. Payment method: ACH or CC 3. Account ID 4. Transactional ID".
5. Open 'Client Ledger' and process the report.
6. Validate that the payment displays in the report.
7. Close the report.
8. Close the form.
9. Open 'Registry Settings'.
10. Change the value of the 'Prevent Posting Payments Unless Payment has been Acknowledged' registry setting to include minimum values of '5&6',
11. Click [Submit].
12. Click [OK].
13. Click [No].
14. A payment is made in the myHealthPointe payment portal. Note all information regarding the payment.
15. Create a query of the 'SYSTEM.unacknowledged_payments' table, specific to Client 2, using the 'PATID'.
16. Validate that payment data is correct. Save the query.
17. Open 'Client Ledger' and process the report.
18. Validate that the payment does not display in the report.
19. Close the report.
20. Close the form.
21. Open the 'Payment Acknowledgement' form.
22. Select the 'Post Front Office and myHP Payments' section.
23. Click 'T' in 'Payment Collection Date'.
24. Select desired value in 'Treatment Service'.
25. Select 'myHP' in 'Type'.
26. Click [Review].
27. Select the row specific to 'Client 2'.
28. Click [OK].
29. Enter desired 'Batch Number'.
30. Enter desired 'Deposit Date'.
31. Select desired 'Category'.
32. Enter desired 'Bank Ref#'.
33. Enter desired 'Comments'.
34. Click [Post].
35. Refresh the query of the 'SYSTEM.unacknowledged_payments' table, specific to Client 2.
36. Validate that the table no longer contains data for 'Client 2'.
37. Create a query of the 'SYSTEM.billing_pay_adj_history' table, specific to 'Client 2' using the 'PATID'.
38. Validate the data for the following fields and any other desired fields: 'GUARANTOR_ID', 'date_of_payment', 'payment_amount', and 'option_id' which will contain 'PatientPortal' indicating that the payment was made in the myHealthPointe payment portal.
39. Open 'CareFabric Monitor'.
40. Validate the PatientPortalPaymentProcessed dialog contains "1. Payment Amount 2. Payment method: ACH or CC 3. Account ID 4. Transactional ID".
41. Open 'Client Ledger' and process the report.
42. Validate that the payment displays in the report.
43. Close the report.
44. Close the form.

• Registry Setting:
• ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
• ‘Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged’ has a ‘Registry Setting Value’ of 5’ at a minimum.
• User Definition has been used to give the tester access to the 'Payment Acknowledgement' form and the ‘SYSTEM.unacknowledged_payments’ table.
• Dictionary Update:
• Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
• Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
• Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
• Posting/Adjustment Codes Definitions:
• 'Payment' definitions exist. The 'Payment' definition may be a 'Credit' (payment) or a 'Debit' (reversal). The definitions may have a value in the ‘Payment Acknowledgement Type’ field. Only 'Payment' definitions will be available in the 'Payment Acknowledgement' section of the 'Payment Acknowledgement' form.
• 'Adjustment' definitions exist. The definitions may have a value in the ‘Payment Acknowledgement Type’ field. All ‘Adjustment’ and 'Payment' definitions will be available in the ‘Payment Acknowledgement’ form in the ‘Post Payment Accounting Entry' section of the 'Payment Acknowledgement' form.
• Client to use in the 'Post Front Office and myHP Payments' section of the 'Payment Acknowledgement' form:
• Client 1: A client with a self-pay balance is identified. Note the program.
• Program Maintenance is used to identify the 'Treatment Service'.
• Deposit Entry’ is used to create a payment for the self-pay guarantor. Note the data entry date.
• Query the ‘SYSTEM.unacknowledged_payments’ table, specific to the client. Validate that the deposit entry payment information is correct.
• Client Ledger is used to validate that the payment was not applied to the client's account.

1. Open ‘Payment Acknowledgement’ form.
2. Verify that ‘Action’ defaults to ‘New’.
3. Verify that ‘Transaction Number’ is read only.
4. Verify that ‘Entered By’ is read only and defaults to the signed in user.
5. Verify that ‘Batch Number’ is required.
6. Verify that ‘Posting Code’’ is required.
7. Verify that ‘Amount’ is required.
8. Verify that ‘Guarantor’ is required.
9. Verify that ‘Receipt Date’ is required.
10. Verify that ‘Deposit Date’ is required.
11. Enter desired value in ‘Batch Number’.
12. Select desired ‘Posting Code’.
13. Enter desired value in ‘Check/EFT Number’.
14. Enter desired value in ‘Amount’.
15. Select desired ‘Guarantor’. If a ‘Self-Pay guarantor is selected, the ‘Client’ field will be enabled.
16. Enter desired value in ‘Name/Source’.
17. Enter desired value in ‘Client’, if enabled.
18. Enter desired value in ‘Check/EFT Date’.
19. Enter desired value in ‘Receipt Date’.
20. Enter desired value in ‘Deposit Date’.
21. Select desired ‘Treatment Service’.
22. Select desired ‘Category’.
23. If the selected item, extended data dictionary value of 'Other Table Files: (5522) Account' - 'Include in Category Dictionary: Yes' the dictionary item will be available for selection. No = not available for selection.
24. If the selected item, extended data dictionary value of 'Other Table Files: (5522) Account' - 'Require Name/Source in Payment Acknowledgement', has a value of 'Y' the 'Name/Source' field will become required. No = not required.
25. Enter desired value in ‘Bank Ref #’.
26. Enter desired value in ‘Comments’.
27. Click [File].
28. Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is 6. Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
29. Clicking [No] returns the user to the ‘Payment Acknowledgement’ section to enter additional payments.
30. Clicking [Yes] allows the user to post payments in 'Post Payment Accounting Entry'.
31. Click [Yes].
32. Click [New Row] in ‘Post Payment Accounting Entry’.
33. Select desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
34. Select desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
35. Select desired ‘Account’.
36. Select desired ‘Amount’.
37. Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgement’.
38. Select desired ‘Posting Date’.
39. Validate that the ‘Posting Summary’ is correct.
40. If desired, and first row partially posts the 'Amount', click [New Row] and repeat the steps.
41. If desired, click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select desired value.
42. Click [File].
43. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
44. Click [Yes].
45. Click the ‘Reverse’ checkbox in one row of the ‘Post Payment Accounting Entry’.
46. Enter desired ‘Reversal Posting Date’.
47. Enter desired ‘Reversal Reason’.
48. Click [Reverse].
49. Validate that a new row was added to the ‘Post Payment Accounting Entry’ grid and that it mirrors the row that was selected to reverse, except for ‘Amount’ displays in parentheses, indicating a negative amount.
50. If desired, add a new row to post and additional payment.
51. Close the form.
52. Open ‘Payment Acknowledgement’ form.
53. Select ‘Edit or View’ in ‘Action, which will enable the ‘Payment Acknowledgement Search’ section.
54. Enter data from the ‘Payment Acknowledgement’, filed above, into desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
55. Click [Search].
56. Select the desired item in the ‘Payment Acknowledgement’ grid.
57. Click [OK] to continue or [Cancel] to end the search. Click [OK].
58. The following ‘Payment Acknowledgement’ displays: Do you need to continue to Post Payment Accounting Entry?
59. Validate the ‘Post Payment Accounting Entry' contains the previously filed data.
60. Close the form.
61. Open ‘Payment Acknowledgement’ form.
62. Select the 'Post Front Office and myHP Payments.
63. Set the 'Payment Collection’ date to the current date.
64. Select the 'Treatment Service' if desired.
65. Select the 'Type'.
66. Click [Review].
67. Select the Deposit Entry item in the 'Unacknowledged Payments' checklist for Client 1.
68. Click [OK].
69. Enter desired 'Batch Number'.
70. Enter desired 'Deposit Date'.
71. Select the desired 'Category'.
72. Enter the desired 'Bank Ref #'.
73. Enter 'Comments' if desired.
74. Click [Post].
75. Click [OK].
76. Close the form.
77. Open the 'Client Ledger' for the client.
78. Process the report.
79. Verify the client ledger displays the deposit entry correctly.
80. Close the Report.
81. Close the form.

• Select a client to use for a payment through a 'Deposit Entry' web service request. Note the guarantor assigned to the client.

1. SoapUI or other web service tool is used to create a request for Deposit Entry.
2. Use the client ID and guarantor from setup. Note amount of payment, date of payment, and any other desired information.
3. Process the request and validate that it completed successfully.
4. Open ‘Client Ledger’ for the client.
5. Process the report and validate that the web service deposit entry payment displays in the client’s record and that the submitted data was retained.
6. Close the report.
7. Close the form.

• This can be tested with and without credit card functionality. If credit card functionality is not enabled, please use non-credit card posting codes. For our testing credit card functionality is enabled.
• The following registry setting has a value of 'Y': Avatar PM--->Billing->Remittance Processing->->->Enable Credit Card Processing.
• 'Receipt Definition' has been defined.
• 'Service Code 1, will be used to accept client payments in the 'Deposit Entry' form:
• Service Code = any value.
• Service Code Definition = any value.
• Service Required By = Client Only.
• Type of Service = Individual.
• Type of Fee = any value.
• Group Code = any value, typically meaning non-billable.
• Covered Charge Category = any value, typically meaning non-billable.
• Is This A Balance Forward Service Code = No.
• Does This Code Have A Professional Component = any value.
• Is This Service A Visit = No.
• Is This Service An Intervention = No.
• 'Service Code 2:
• Service Code = any value.
• Service Code Definition = any value.
• Service Required By = Both or Provider.
• Type of Service = Individual.
• Type of Fee = any value.
• Group Code = any value.
• Covered Charge Category = any value.
• Is This A Balance Forward Service Code = No.
• Does This Code Have A Professional Component = any value.
• Is This Service A Visit = any value.
• Is This Service An Intervention = any value.
• 'Posting/Adjustment Codes Definition 1':
• Note the ‘Code Definition’.
• 'Adjustment, Payment or Transfer’ = 'Payment'.
• ‘Credit or Debit’ = 'Credit'.
• ‘Is this a Credit Card or ACH Payment Code’ = 'No' or is blank.
• After creating 'Posting/Adjustment Codes Definition 2', return to this code in ‘Edit’ mode and add a value of ‘Yes’ to ‘Generate Receipt’ and a value of 'Posting/Adjustment Codes Definition 2' to ‘Void Receipt Posting Code'.
• Posting/Adjustment Codes Definition 2':
• Note the ‘Code Definition’.
• 'Adjustment, Payment or Transfer’ = 'Payment'.
• ‘Credit or Debit’ = 'Debit'.
• ‘Is This a Reversal Code’ = 'Yes’.
• 'Which Pym/Adj Code Is This A Reversal For' = 'Posting/Adjustment Codes Definition 1'.
• 'Posting/Adjustment Codes Definition 3':
• Note the ‘Code Definition’.
• 'Adjustment, Payment or Transfer’ = 'Payment'.
• ‘Credit or Debit’ = 'Credit'.
• ‘Is this a Credit Card or ACH Payment Code’ = 'Yes'.
• After creating 'Posting/Adjustment Codes Definition 4', return to this code in ‘Edit’ mode and add a value of ‘Yes’ to ‘Generate Receipt’ and a value of 'Posting/Adjustment Codes Definition 4' to ‘Void Receipt Posting Code'.
• Posting/Adjustment Codes Definition 4':
• Note the ‘Code Definition’.
• 'Adjustment, Payment or Transfer’ = 'Payment'.
• ‘Credit or Debit’ = 'Debit'.
• ‘Is This a Reversal Code’ = 'Yes’.
• 'Which Pym/Adj Code Is This A Reversal For' = 'Posting/Adjustment Codes Definition 3'.
• The following registry setting has a value of 'Service Code 1': Avatar PM->Services->Ancillary/Ambulatory Services->Deposit Entry->->Default Service Code.
• The following registry setting has a value of 'Posting/Adjustment Codes Definition 1': Avatar PM->Scheduling->Front Desk->->->Pre Payment Default Posting Code.
• Credit Card Configuration:
• Has 'No' in 'Populate Receipt Number with Credit Card Payment Reference Number'.
• Enter desired values for the other fields.
• In the 'Credit Card Device Setup' section: '
• Credit Card Device 1': Has a value of 'No' in 'Is this a Back Office MID?'. Note the device name. Enter desired values for the other fields.
• 'Credit Card Device 2': Has a value of 'Yes' in 'Is this a Back Office MID?'. Note the device name. Enter desired values for the other fields.
• 'Guarantors/Payors 1': Has a 'Financial Class' of 'Self Pay'.
• 'Client 1':
• Note the episode/program.
• Use 'Program Maintenance' to note the program default location.
• Is assigned Guarantors/Payors 1 in 'Financial Eligibility.
• Use 'Client Ledger' client to note the balance for 'Guarantors/Payors 1' in 'TOTAL BALANCE BY GUARANTOR.
• 'Client 2':
• Note the episode/program.
• Use 'Program Maintenance' to note the program default location.
• Is assigned Guarantors/Payors 1 in 'Financial Eligibility.
• Use 'Client Ledger' client to note the balance for 'Guarantors/Payors 1' in 'TOTAL BALANCE BY GUARANTOR.
• 'Client 3':
• Note the episode/program. There is no 'Attending Practitioner' in the admission record.
• Use 'Program Maintenance' to note the program default location.
• Is assigned Guarantors/Payors 1 in 'Financial Eligibility.
• Use 'Client Ledger' client to note the balance for 'Guarantors/Payors 1' in 'TOTAL BALANCE BY GUARANTOR.

1. Open 'Deposit Entry'.
2. Validate 'Date Of Receipt Or Adjustment' is equal to "required".
3. Validate 'Client ID' is equal to "required".
4. Validate 'Episode Number' is equal to "required".
5. Validate 'Guarantor' is equal to "required".
6. Validate 'Service Code' is equal to "required".
7. Validate 'Amount To Post' is equal to "required".
8. Validate 'Posting Code' is equal to "required".
9. Validate 'Receipt' is "enabled".
10. Validate 'Check #' is equal to "enabled".
11. Validate 'Program Of Service' is equal to "required".
12. Validate 'Location' is equal to "required".
13. Validate 'Transaction Type' is equal to "disabled".
14. Validate 'Select Credit Card Device' is equal to "disabled".
15. Validate 'Pay With Credit Card button is equal to "disabled".
16. Click [Submit].
17. Validate that a 'Submitting' message is received stating: The following fields are missing: Amount To Post, Client ID, Date of Receipt Or Adjustment, Episode Number, Guarantor, Location, Posting Code, Program Of Service, Service Code.
18. Click [OK].
19. Click the 'Y - Date Of Receipt Or Adjustment' button.
20. Validate 'Date Of Receipt Or Adjustment' is equal to "yesterday's date".
21. Click the 'T - Date Of Receipt Or Adjustment' button.
22. Validate 'Date Of Receipt Or Adjustment' is equal to "current date".
23. Set 'Client ID' to "Client 1".
24. Select desired 'Episode Number'.
25. Validate 'Program Of Service' is equal to "Client 1 program of service".
26. Validate 'Location' is equal to "Client 1 program of service default location".
27. Set 'Service Code' to "Service Code 1".
28. Select "Guarantors/Payors 1" in 'Guarantor'.
29. Set 'Amount To Post' to "5".
30. Select "Posting/Adjustment Codes Definition 1" in 'Posting Code'.
31. Click [Submit].
32. Validate the receipt is generated and contains data including: 'Payment Received For ' = Client 1, 'The Sum of $5.00' and 'Type of Payment:' = ‘'Posting/Adjustment Codes Definition 1', Code Definition’. Note the value of 'Receipt #'.
33. Close the receipt.
34. Open 'Deposit Entry'.
35. Click the 'T - Date Of Receipt Or Adjustment' button.
36. Set 'Client ID' to "Client 2".
37. Select desired 'Episode Number'.
38. Set 'Service Code' to "Service Code 1".
39. Select "Guarantors/Payors 1" in 'Guarantor'.
40. Set 'Amount To Post' to "5".
41. Select "Posting/Adjustment Codes Definition 3" in 'Posting Code'.
42. Validate 'Pay With Credit Card' is equal to "enabled".
43. Validate 'Transaction Type' is equal to "enabled and required".
44. Validate 'Transaction Type' is equal to "Insert/Swipe Card".
45. Validate 'Select Credit Card Device' is equal to "enabled and required".
46. Click [Submit].
47. Validate the 'Error' message is equal to: Please use the 'Pay With Credit Card' command button to process a credit card posting code or select a different code.
48. Click [OK].
49. Select the desired 'Transaction Type'.
50. Click [Pay With Credit Card] and follow the prompts to process the payment.
51. Review the 'Card Connect Payment' message. A successful payment will generate a receipt.
52. Click [OK] on the 'Card Connect Payment' message.
53. Validate the receipt, if generated, contains data including: 'Payment Received For' = Client 2, 'The Sum of $5.00' and 'Type of Payment' = ‘'Posting/Adjustment Codes Definition 3', Code Definition’. Note the value of 'Receipt #'.
54. Click the 'T - Date Of Receipt Or Adjustment' button.
55. Set 'Client ID' to "Client 3".
56. Select desired 'Episode Number'.
57. Set 'Service Code' to "Service Code 2".
58. Select "Guarantors/Payors 1" in 'Guarantor'.
59. Set 'Amount To Post' to "5".
60. Select "Posting/Adjustment Codes Definition 1" in 'Posting Code'.
61. Click [Submit].'
62. Validate the 'Error' message is equal to "Attending Practitioner Is Not Assigned. Process Aborted".
63. Click [OK].
64. Select "Posting/Adjustment Codes Definition 3" in 'Posting Code'.
65. Click [Submit].'
66. Validate the 'Error' message is equal to "Attending Practitioner Is Not Assigned. Process Aborted".
67. Click [OK].
68. Click [X] to close the form.
69. Open 'Client Ledger' for 'Client 1'.
70. Validate that a $5.00 payment was made on the current date for "Posting/Adjustment Codes Definition 1", and 'Service Code 1'.
71. Update the 'Client Ledger' to 'Client 2'.
72. Validate that a $5.00 payment was made on the current date for "Posting/Adjustment Codes Definition 3", and 'Service Code 1'.
73. Update the 'Client Ledger' to 'Client 3'.
74. Validate that no payment was made on the current date.

• Registry Setting:
• Set the 'Avatar PM->System Maintenance->File Import->->->Import File Delimiter' registry setting to the desired value.
• Guarantors/Payor:
• An existing guarantor is identified to be assigned to the client. Note the guarantor code/value.
• Program Maintenance:
• Identify an existing program code / value to be used for client's admission.
• Identify the location of the program to be used for Client's admission.
• Admission:
• An inpatient or outpatient client is created using the program identified above or an existing client is identified. Note the Client id/name, admission date/program.
• Financial Eligibility: The existing guarantor is assigned to the client.
• Service code:
• An existing service code to be used with inpatient/ outpatient program is identified. Note the service code for further validation.
• Posting/Adjustment Code Definition:
• An existing payment, adjustment or transfer code is identified to be used. Note the code and type of the code.
• File Import:
• An import file is created to process the deposit entry. Ensure that the file contains all required fields and desired optional fields. Note the file name / location of the file.

1. Open the 'File Import' form.

2. Select the 'Deposit Entry' from the File Type field.

3. Upload the file Import file created in the setup section.

4. Compile the file.

5. Verify the file compiles successfully.

6. Post the compiled file.

7. Verify the file posted successfully.

8. Open the 'Client Ledger' for the client.

9. Process the report.

10. Verify the client ledger displays the deposit entry correctly.

11. Close the Report.

12. Close the form.

1. Open the 'Registry Settings' form.
2. Set the Limit Registry Settings to 'Enable Payment Acknowledgement'
3. Set the Registry Setting Value input box to ‘N’.
4. Click [Submit].
5. Click [OK].
6. Click [Yes].
7. Submit the form.
8. Set the Limit Registry Settings to 'Prevent Posting Payments Unless Payment has been Acknowledged'.
9. Validate the Registry Setting input box contains 'Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged'.
10. Validate the Registry Setting Details text area contains: [FACILITY SPECIFIC] - The 'Enable Payment Acknowledgement' registry setting must be enabled to select any values. The valid values are: 0 or 1, 2, 3, 4, 5 and/or 6. Multiple values can be selected. They will be separated by ampersands. Example: 1&2. When '1' is selected, it will restrict the ability to post payments in the '835 Health Care Claim Payment/Advice' form to only payments that have been acknowledged in the 'Payment Acknowledgement' form. When '2' is selected, it will restrict the ability to post payments in the 'Batch Cash Posting' form to only payments that have been acknowledged in the 'Payment Acknowledgement' form. When '3' is selected, it will restrict the ability to post payments in the "Payment/Adjustment Posting" 'File Import' to only payments that have been acknowledged in the 'Payment Acknowledgement' form. When '4' is selected, it will prevent the system from applying payments entered in 'Scheduling Calendar - Check In' until those payments have been acknowledged in the 'Payment Acknowledgement' form. This will also add the 'Name on Card' field to 'Scheduling Calendar - Check In'. When '5' is selected, it will prevent the system from applying payments entered in 'Deposit Entry' until those payments have been acknowledged in the 'Payment Acknowledgement' form. This will also add the 'Name on Card' field to 'Deposit Entry'. When '6' is selected, it will prevent the system from applying payments entered in myHealthPointe until those payments have been acknowledged in the 'Payment Acknowledgement' form. Selecting '0' will remove this functionality. This is the default behavior.
11. Set the Registry Setting Value input box to '1'.
12. Validate the error message dialog contains 'The selected value is not valid in the current system code for the following reason: The 'Enable Payment Acknowledgement' registry setting must be enabled to make any selections other than zero.'
13. Set the Limit Registry Settings to 'Enable Payment Acknowledgement'.
14. Set the 'Enable Payment Acknowledgement' registry setting to 'Y'.
15. Click [Submit].
16. Click [OK].
17. Set the Limit Registry Settings to 'Prevent Posting Payments Unless Payment has been Acknowledged'.
18. Validate that the Registry Setting Value defaults to ‘0’.
19. Set the Registry Setting Value input box to 'Y'.
20. Click [TAB].
21. Validate the error message dialog contains 'The selected value is not valid in the current system code for the following reason: Invalid selection found (Y).'
22. Set the Registry Setting Value input box to 'N'.
23. Click [TAB].
24. Validate the error message dialog contains 'The selected value is not valid in the current system code for the following reason: Invalid selection found (N).'
25. Set the Registry Setting Value input box to '1'.
26. Click [Submit].
27. Click [OK].
28. Click [Yes].
29. Set the Limit Registry Settings to 'Prevent Posting Payments Unless Payment has been Acknowledged'.
30. Set the Registry Setting Value input box to '2'.
31. Click [Submit].
32. Click [OK].
33. Click [Yes].
34. Set the Limit Registry Settings to 'Prevent Posting Payments Unless Payment has been Acknowledged'.
35. Set the Registry Setting Value input box to '3'.
36. Click [Submit].
37. Click [OK].
38. Click [Yes].
39. Set the Limit Registry Settings to 'Prevent Posting Payments Unless Payment has been Acknowledged'.
40. Set the Registry Setting Value input box to '4'.
41. Click [Submit].
42. Click [OK].
43. Click [Yes].
44. Set the Limit Registry Settings to 'Prevent Posting Payments Unless Payment has been Acknowledged'.
45. Set the Registry Setting Value input box to '5'.
46. Click [Submit].
47. Click [OK].
48. Click [Yes].
49. Set the Limit Registry Settings to 'Prevent Posting Payments Unless Payment has been Acknowledged'.
50. Set the Registry Setting Value input box to '6'.
51. Click [Submit].
52. Click [OK].
53. Click [Yes].
54. Set the Limit Registry Settings to 'Prevent Posting Payments Unless Payment has been Acknowledged'.
55. Set the Registry Setting Value input box to '1&2&3&4&5&6'.
56. Click [Submit].
57. Click [OK].
58. Click [Yes].
59. Set the Limit Registry Settings to 'Prevent Posting Payments Unless Payment has been Acknowledged'.
60. Validate the Registry Setting Value input box contains '1&2&3&4&5&6'.
61. Close the form.

• Registry Setting:
• Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement = 'Y'.
• Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged = '5', at a minimum, but may contain any combination of '1&2&3&4&5&6'.
• User Definition has been used to give the tester access to the 'Payment Acknowledgement' form and the ‘SYSTEM.unacknowledged_payments’ table.
• Guarantors/Payors:
• An existing guarantor is identified to be assigned to the client. Note the guarantor's code/value.
• Program Maintenance:
• Identify an existing program code / value to be used for client's admission.
• Note the location of the program to be used for Client's admission.
• Admission:
• An inpatient or outpatient client is created using the program identified above or an existing client is identified. Note the client's id/name, admission date/program.
• Financial Eligibility: The existing guarantor is assigned to the client. Note the guarantor's code/name.
• Service code:
• An existing service code to be used with inpatient/ outpatient program is identified. Note the service code for further validation.
• Posting/Adjustment Code Definition:
• An existing payment, adjustment or transfer code is identified to be used. Note the code and type of the code.
• File Import:
• An import file is created to process the deposit entry. Ensure that the file contains all required fields and desired optional fields. Note the file name / location of the file.

1. Open the 'File Import' form.
2. Select the 'Deposit Entry' from the File Type field.
3. Upload the file Import file created in the setup section.
4. Compile the file.
5. Verify the file compiles successfully.
6. Post the compiled file.
7. Verify the file posted successfully.
8. Open the 'Client Ledger' for the client.
9. Process the report.
10. Verify the client ledger does not display the deposit entry payment.
11. Close the Report.
12. Close the form.
13. If desired, query the ‘SYSTEM.unacknowledged_payments’ table, specific to the client.
14. Verify that the query results display the Deposit Entry item correctly.
15. Close the query.
16. Open 'Payment Acknowledgement'.
17. Select the 'Post Front Office and myHP Payments.
18. Set the 'Payment Collection’ date to the current date.
19. Select the 'Treatment Service' if desired.
20. Select the 'Type'.
21. Click [Review].
22. Select the Deposit Entry item in the 'Unacknowledged Payments' checklist.
23. Click [OK].
24. Enter desired 'Batch Number'.
25. Enter the 'Deposit Date' which would the 'Date Of Receipt Or Adjustment' in the Deposit Entry file.
26. Select the desired 'Category'.
27. Enter the desired 'Bank Ref #'.
28. Enter 'Comments' if desired.
29. Click [Post].
30. Click [OK].
31. Close the form.
32. Open the 'Client Ledger' for the client.
33. Process the report.
34. Verify the client ledger displays the deposit entry correctly.
35. Close the Report.
36. Close the form.

• Registry Settings:
• Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement = Y.
• Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged = ‘5’ at a minimum.
• User Definition has been used to give the tester access to the 'Payment Acknowledgement' form and the ‘SYSTEM.unacknowledged_payments’ table.
• Admit a new test client or select an existing self-pay client. Note the client’s ID.
• Assign a self-pay Financial Eligibility record to the client.
• Use 'Deposit Entry' to post a payment to the client. Note the details of the payment.
• Use 'Client Ledger' to validate that the payment did not post to the account.
• Use Crystal Reports or other SQL reporting tool to query the 'SYSTEM.unacknowledged_payments' table, specific to the client. Validate that payment data is correct. Save the query.

1. Open ‘Payment Acknowledgement’.
2. Select the ‘Post Front Office and myHP Payments’ section.
3. Click [T] on ‘Payment Collection Date’.
4. Select ‘Front Office’ in ‘Type’.
5. Click [Review].
6. Select the row with the 'Deposit Entry' payment for the client.
7. Click [OK].
8. Enter desired ‘Batch Number’.
9. Enter desired ‘Deposit Date’.
10. Select desired ‘Category’.
11. Enter desired ‘Bank Ref #’.
12. Enter desired ‘Comments.
13. Click [Post].
14. Open ‘Client Ledger’ for the client.
15. Process the ‘Simple’ ledger report.
16. Validate that the 'Deposit Entry' payment posted to the client’s account.
17. Close the report.
18. Close the form.
19. Use Crystal Reports or other SQL reporting tool to query the 'SYSTEM.unacknowledged_payments' table, specific to the client. Validate that no results are returned.

• Registry Setting:
• ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
• ‘Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged’ has a ‘Registry Setting Value’ of 5’ at a minimum.
• User Definition has been used to give the tester access to the 'Payment Acknowledgement' form and the ‘SYSTEM.unacknowledged_payments’ table.
• Select a client to use for a payment through a 'Deposit Entry' web service request. Note the guarantor assigned to the client.

1. SoapUI or other web service tool is used to create a request for Deposit Entry.
2. Use the client ID and guarantor from setup. Note amount of payment, date of payment, and any other desired information.
3. Process the request and validate that it completed successfully.
4. Open ‘Client Ledger’ for the client.
5. Process the report and validate that the web service deposit entry payment is not included in the client’s account.
6. Close the report.
7. Close the form.
8. Query the ‘SYSTEM.unacknowledged_payments’ table, specific to the client.
9. Verify that the query results display the web service deposit entry item correctly.
10. Close the query.
11. Open 'Payment Acknowledgement'.
12. Select the 'Post Front Office and myHP Payments.
13. Set the 'Payment Collection’ date to the current date.
14. Select the 'Treatment Service' if desired.
15. Select the 'Type'.
16. Click [Review].
17. Select the web service deposit entry item in the 'Unacknowledged Payments' checklist.
18. Click [OK].
19. Enter desired 'Batch Number'.
20. Enter the 'Deposit Date' which would the 'Date Of Receipt Or Adjustment' in the Deposit Entry file.
21. Select the desired 'Category'.
22. Enter the desired 'Bank Ref #'.
23. Enter 'Comments' if desired.
24. Click [Post].
25. Click [OK].
26. Close the form.
27. Query the ‘SYSTEM.unacknowledged_payments’ table, specific to the client.
28. Verify that no query results are returned.
29. Close the query.
30. Open the 'Client Ledger' for the client.
31. Process the report.
32. Verify the client ledger displays the deposit entry correctly.
33. Close the Report.
34. Close the form.

• This can be tested with and without credit card functionality. If credit card functionality is not enabled, please use non-credit card posting codes. For our testing credit card functionality is enabled.
• The following registry setting has a value of 'Y': Avatar PM--->Billing->Remittance Processing->->->Enable Credit Card Processing.
• 'Receipt Definition' has been defined.
• 'Service Code 1, will be used to accept client payments in the 'Deposit Entry' form:
• Service Code = any value.
• Service Code Definition = any value.
• Service Required By = Client Only.
• Type of Service = Individual.
• Type of Fee = any value.
• Group Code = any value, typically meaning non-billable.
• Covered Charge Category = any value, typically meaning non-billable.
• Is This A Balance Forward Service Code = No.
• Does This Code Have A Professional Component = any value.
• Is This Service A Visit = No.
• Is This Service An Intervention = No.
• 'Service Code 2:
• Service Code = any value.
• Service Code Definition = any value.
• Service Required By = Both or Provider.
• Type of Service = Individual.
• Type of Fee = any value.
• Group Code = any value.
• Covered Charge Category = any value.
• Is This A Balance Forward Service Code = No.
• Does This Code Have A Professional Component = any value.
• Is This Service A Visit = any value.
• Is This Service An Intervention = any value.
• 'Posting/Adjustment Codes Definition 1':
• Note the ‘Code Definition’.
• 'Adjustment, Payment or Transfer’ = 'Payment'.
• ‘Credit or Debit’ = 'Credit'.
• ‘Is this a Credit Card or ACH Payment Code’ = 'No' or is blank.
• After creating 'Posting/Adjustment Codes Definition 2', return to this code in ‘Edit’ mode and add a value of ‘Yes’ to ‘Generate Receipt’ and a value of 'Posting/Adjustment Codes Definition 2' to ‘Void Receipt Posting Code'.
• Posting/Adjustment Codes Definition 2':
• Note the ‘Code Definition’.
• 'Adjustment, Payment or Transfer’ = 'Payment'.
• ‘Credit or Debit’ = 'Debit'.
• ‘Is This a Reversal Code’ = 'Yes’.
• 'Which Pym/Adj Code Is This A Reversal For' = 'Posting/Adjustment Codes Definition 1'.
• 'Posting/Adjustment Codes Definition 3':
• Note the ‘Code Definition’.
• 'Adjustment, Payment or Transfer’ = 'Payment'.
• ‘Credit or Debit’ = 'Credit'.
• ‘Is this a Credit Card or ACH Payment Code’ = 'Yes'.
• After creating 'Posting/Adjustment Codes Definition 4', return to this code in ‘Edit’ mode and add a value of ‘Yes’ to ‘Generate Receipt’ and a value of 'Posting/Adjustment Codes Definition 4' to ‘Void Receipt Posting Code'.
• Posting/Adjustment Codes Definition 4':
• Note the ‘Code Definition’.
• 'Adjustment, Payment or Transfer’ = 'Payment'.
• ‘Credit or Debit’ = 'Debit'.
• ‘Is This a Reversal Code’ = 'Yes’.
• 'Which Pym/Adj Code Is This A Reversal For' = 'Posting/Adjustment Codes Definition 3'.
• The following registry setting has a value of 'Service Code 1': Avatar PM->Services->Ancillary/Ambulatory Services->Deposit Entry->->Default Service Code.
• The following registry setting has a value of 'Posting/Adjustment Codes Definition 1': Avatar PM->Scheduling->Front Desk->->->Pre Payment Default Posting Code.
• Credit Card Configuration:
• Has 'No' in 'Populate Receipt Number with Credit Card Payment Reference Number'.
• Enter desired values for the other fields.
• In the 'Credit Card Device Setup' section: '
• Credit Card Device 1': Has a value of 'No' in 'Is this a Back Office MID?'. Note the device name. Enter desired values for the other fields.
• 'Credit Card Device 2': Has a value of 'Yes' in 'Is this a Back Office MID?'. Note the device name. Enter desired values for the other fields.
• 'Guarantors/Payors 1': Has a 'Financial Class' of 'Self Pay'.
• 'Client 1':
• Note the episode/program.
• Use 'Program Maintenance' to note the program default location.
• Is assigned Guarantors/Payors 1 in 'Financial Eligibility.
• Use 'Client Ledger' client to note the balance for 'Guarantors/Payors 1' in 'TOTAL BALANCE BY GUARANTOR.
• 'Client 2':
• Note the episode/program.
• Use 'Program Maintenance' to note the program default location.
• Is assigned Guarantors/Payors 1 in 'Financial Eligibility.
• Use 'Client Ledger' client to note the balance for 'Guarantors/Payors 1' in 'TOTAL BALANCE BY GUARANTOR.
• 'Client 3':
• Note the episode/program. There is no 'Attending Practitioner' in the admission record.
• Use 'Program Maintenance' to note the program default location.
• Is assigned Guarantors/Payors 1 in 'Financial Eligibility.
• Use 'Client Ledger' client to note the balance for 'Guarantors/Payors 1' in 'TOTAL BALANCE BY GUARANTOR.

1. Open 'Deposit Entry'.
2. Validate 'Date Of Receipt Or Adjustment' is equal to "required".
3. Validate 'Client ID' is equal to "required".
4. Validate 'Episode Number' is equal to "required".
5. Validate 'Guarantor' is equal to "required".
6. Validate 'Service Code' is equal to "required".
7. Validate 'Amount To Post' is equal to "required".
8. Validate 'Posting Code' is equal to "required".
9. Validate 'Receipt' is "enabled".
10. Validate 'Check #' is equal to "enabled".
11. Validate 'Program Of Service' is equal to "required".
12. Validate 'Location' is equal to "required".
13. Validate 'Transaction Type' is equal to "disabled".
14. Validate 'Select Credit Card Device' is equal to "disabled".
15. Validate 'Pay With Credit Card button is equal to "disabled".
16. Click [Submit].
17. Validate that a 'Submitting' message is received stating: The following fields are missing: Amount To Post, Client ID, Date of Receipt Or Adjustment, Episode Number, Guarantor, Location, Posting Code, Program Of Service, Service Code.
18. Click [OK].
19. Click the 'Y - Date Of Receipt Or Adjustment' button.
20. Validate 'Date Of Receipt Or Adjustment' is equal to "yesterday's date".
21. Click the 'T - Date Of Receipt Or Adjustment' button.
22. Validate 'Date Of Receipt Or Adjustment' is equal to "current date".
23. Set 'Client ID' to "Client 1".
24. Select desired 'Episode Number'.
25. Validate 'Program Of Service' is equal to "Client 1 program of service".
26. Validate 'Location' is equal to "Client 1 program of service default location".
27. Set 'Service Code' to "Service Code 1".
28. Select "Guarantors/Payors 1" in 'Guarantor'.
29. Set 'Amount To Post' to "5".
30. Select "Posting/Adjustment Codes Definition 1" in 'Posting Code'.
31. Click [Submit].
32. Validate the receipt is generated and contains data including: 'Payment Received For ' = Client 1, 'The Sum of $5.00' and 'Type of Payment:' = ‘'Posting/Adjustment Codes Definition 1', Code Definition’. Note the value of 'Receipt #'.
33. Close the receipt.
34. Open 'Deposit Entry'.
35. Click the 'T - Date Of Receipt Or Adjustment' button.
36. Set 'Client ID' to "Client 2".
37. Select desired 'Episode Number'.
38. Set 'Service Code' to "Service Code 1".
39. Select "Guarantors/Payors 1" in 'Guarantor'.
40. Set 'Amount To Post' to "5".
41. Select "Posting/Adjustment Codes Definition 3" in 'Posting Code'.
42. Validate 'Pay With Credit Card' is equal to "enabled".
43. Validate 'Transaction Type' is equal to "enabled and required".
44. Validate 'Transaction Type' is equal to "Insert/Swipe Card".
45. Validate 'Select Credit Card Device' is equal to "enabled and required".
46. Click [Submit].
47. Validate the 'Error' message is equal to: Please use the 'Pay With Credit Card' command button to process a credit card posting code or select a different code.
48. Click [OK].
49. Select the desired 'Transaction Type'.
50. Click [Pay With Credit Card] and follow the prompts to process the payment.
51. Review the 'Card Connect Payment' message. A successful payment will generate a receipt.
52. Click [OK] on the 'Card Connect Payment' message.
53. Validate the receipt, if generated, contains data including: 'Payment Received For' = Client 2, 'The Sum of $5.00' and 'Type of Payment' = ‘'Posting/Adjustment Codes Definition 3', Code Definition’. Note the value of 'Receipt #'.
54. Click the 'T - Date Of Receipt Or Adjustment' button.
55. Set 'Client ID' to "Client 3".
56. Select desired 'Episode Number'.
57. Set 'Service Code' to "Service Code 2".
58. Select "Guarantors/Payors 1" in 'Guarantor'.
59. Set 'Amount To Post' to "5".
60. Select "Posting/Adjustment Codes Definition 1" in 'Posting Code'.
61. Click [Submit].'
62. Validate the 'Error' message is equal to "Attending Practitioner Is Not Assigned. Process Aborted".
63. Click [OK].
64. Select "Posting/Adjustment Codes Definition 3" in 'Posting Code'.
65. Click [Submit].'
66. Validate the 'Error' message is equal to "Attending Practitioner Is Not Assigned. Process Aborted".
67. Click [OK].
68. Click [X] to close the form.
69. Open 'Client Ledger' for 'Client 1'.
70. Validate that a $5.00 payment was made on the current date for "Posting/Adjustment Codes Definition 1", and 'Service Code 1'.
71. Update the 'Client Ledger' to 'Client 2'.
72. Validate that a $5.00 payment was made on the current date for "Posting/Adjustment Codes Definition 3", and 'Service Code 1'.
73. Update the 'Client Ledger' to 'Client 3'.
74. Validate that no payment was made on the current date.

• Registry Setting:
• The 'Enable Payment Acknowledgement' registry setting is enabled.
• The 'Prevent Posting Payments Unless Payment has been Acknowledged' registry setting includes value '1'.
• The 'Check Number' registry setting is set to '1'.
• The 'Posting Date for Automated 835s' registry setting is set to '1'.
• Claim Adjustment Group/ reason code Definition:
• A group code is selected for the credit adjustment code and debit adjustment reversal code. Note the adjustment codes and group code setup.
• Admission:
• Admit a client into an outpatient episode. Note the Client id/name, Admission date/program.
• Guarantor/Payors:
• Two existing guarantors are identified who have a Financial Class that has the Extended Data Element for (1500) System Financial Class set to Self Pay.
• Financial Eligibility:
• The desired guarantors identified above are assigned to the client. Note the primary and secondary guarantor.
• Client Charge Input:
• A service is rendered to the client.
• Client Ledger:
• Make sure the service is distributed to one of the guarantors assigned to the client.
• Close charges.
• Electronic Billing:
• Claim the service using the 837 Professional bill for the guarantor.
• Create an 835 file based on the claim information found in the 837 professional bill.

1. Open the '835 Health Care Claim Payment/Advice' form.
2. Load and compile the 835 file created that includes the claim for the defined guarantor in the setup.
3. Verify the 835 file loads/compiles successfully.
4. Select 'Post File' option.
5. Select the compiled file.
6. Populate all the required fields with desired value.
7. Verify the Check/EFT# is populated correctly with the status of acknowledged or unacknowledged in the 'Check/EFT#' checkbox.
8. Check the Check/EFT# that is unacknowledged.
9. Click [Process File].
10. Verify the message: 'Selecting Unacknowledged Check/EFT numbers is not permitted.'
11. Click [OK].
12. Close the form.
13. Open the ‘Payment Acknowledgment’ form.
14. Enter desired value in ‘Batch Number’.
15. Select desired ‘Posting Code’.
16. Enter desired value in ‘Check/EFT Number’ from the TRN*02 segment of the 835 file created in the setup.
17. Enter desired value in ‘Amount’ that matches the amount entered in the CLP*04 segment of the 835 file.
18. Select desired ‘Guarantor’ set up in the setup section. Note: If a ‘Self-Pay guarantor is selected, the ‘Client’ field will be enabled.
19. Enter desired value in ‘Name/Source’.
20. Enter desired value in ‘Client’, if enabled.
21. Enter desired value in ‘Check/EFT Date’ that matches the date entered in the BPR*16 segment of the 835 file.
22. Enter desired value in ‘Receipt Date’.
23. Enter desired value in ‘Deposit Date’.
24. Select desired ‘Treatment Service’.
25. Select desired ‘Category’.
26. Enter desired value in ‘Bank Ref #’.
27. Enter desired value in ‘Comments’.
28. Click [File].
29. Verify that the ‘Payment Acknowledgment’ message is received and states the following: Filed successfully. The Transaction Number is [number] Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
30. Click [No].
31. Close the form.
32. Open the '835 Health Care Claim Payment/Advice' form.
33. Select 'Post File' option.
34. Select the compiled file.
35. Populate all the required fields with desired value.
36. Verify the Check/EFT# is populated correctly with the status of acknowledged or unacknowledged in the 'Check/EFT#' checkbox.
37. Check the Check/EFT# that acknowledged in above steps.
38. Click [Process File].
39. Verify the file posts successfully.
40. Open the 'Client Ledger' for the client.
41. Verify the payments are posted correctly on the ledger.
42. Open the 'Crystal Report' or any other SQL Data viewer.
43. Create a query to retrieve data from the SYSTEM.billing_pay_adj_history table.
44. Validate the check number field contains check number from the TRN-02 segment of the 835 file.
45. Validate the 'pay_acknowledge_trans_num' column contains the transaction number from the 'Payment Acknowledgement' form for the Check/EFT.

• Registry Setting:
• The 'Enable Payment Acknowledgement' registry setting is enabled.
• The 'Prevent Posting Payments Unless Payment has been Acknowledged' registry setting includes value '1'.
• The 'Check Number' registry setting is set to '1'.
• The 'Posting Date for Automated 835s' registry setting is set to '1'.
• Claim Adjustment Group/ reason code Definition:
• A group code is selected for the credit adjustment code and debit adjustment reversal code. Note the adjustment codes and group code setup.
• Admission:
• Admit a client into an outpatient episode. Note the Client id/name, Admission date/program.
• Guarantor/Payors:
• Two existing guarantors are identified who have a Financial Class that has the Extended Data Element for (1500) System Financial Class set to Self Pay.
• Financial Eligibility:
• The desired guarantors identified above are assigned to the client. Note the primary and secondary guarantor.
• Client Charge Input:
• A service is rendered to the client.
• Client Ledger:
• Make sure the service is distributed to one of the guarantors assigned to the client.
• Close charges.
• Electronic Billing:
• Claim the service using the 837 Professional bill for the guarantor.
• Create an 835 file based on the claim information found in the 837 professional bill.

1. Open the '835 Health Care Claim Payment/Advice' form.
2. Load and compile the 835 file created that includes the claim for the defined guarantor in the setup.
3. Verify the 835 file loads/compiles successfully.
4. Select 'Post File' option.
5. Select the file that is recently compiled successfully.
6. Populate all the required fields with desired value.
7. Verify the Check/EFT# is populated correctly with the status of acknowledged or unacknowledged in the 'Check/EFT#' checkbox.
8. Check the Check/EFT# that is unacknowledged.
9. Click [Process File].
10. Verify the message: 'Selecting Unacknowledged Check/EFT numbers is not permitted.'
11. Click [OK].
12. Close the form.
13. Open the ‘Payment Acknowledgment’ form.
14. Enter desired value in ‘Batch Number’.
15. Select desired ‘Posting Code’.
16. Enter desired value in ‘Check/EFT Number’ from the TRN*02 segment of the 835 file created in the setup.
17. Enter desired value in ‘Amount’ that matches the amount entered in the CLP*04 segment of the 835 file.
18. Select desired ‘Guarantor’ set up in the setup section. Note: If a ‘Self-Pay guarantor is selected, the ‘Client’ field will be enabled.
19. Enter desired value in ‘Name/Source’.
20. Enter desired value in ‘Client’, if enabled.
21. Enter desired value in ‘Check/EFT Date’ that matches the date entered in the BPR*16 segment of the 835 file.
22. Enter desired value in ‘Receipt Date’.
23. Enter desired value in ‘Deposit Date’.
24. Select desired ‘Treatment Service’.
25. Select desired ‘Category’.
26. Enter desired value in ‘Bank Ref #’.
27. Enter desired value in ‘Comments’.
28. Click [File].
29. Verify that the ‘Payment Acknowledgment’ message is received and states the following: Filed successfully. The Transaction Number is [number] Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing. Note the transaction number.
30. Click [No].
31. Close the form.
32. Open the '835 Health Care Claim Payment/Advice' form.
33. Select 'Post File' option.
34. Select the file that is recently compiled successfully.
35. Populate all the required fields with desired value.
36. Verify the Check/EFT# is populated correctly with the status of acknowledged or unacknowledged in the 'Check/EFT#' checkbox.
37. Check the Check/EFT# that acknowledged in above steps.
38. Click [Process File].
39. Verify the file posts successfully.
40. Open the 'Client Ledger' for the client.
41. Verify the payments are posted correctly on the ledger.
42. Open the 'Crystal Report' or any other SQL Data viewer.
43. Create a query to retrieve data from the SYSTEM.billing_pay_adj_history table.
44. Validate the check number field contains check number from the TRN-02 segment of the 835 file.
45. Validate the date of payment column contains the posting date from the '835 Health Care Claim Payment/Advice' form.
46. Validate the 'pay_acknowledge_trans_num' column contains the transaction number from the 'Payment Acknowledgement' form for the Check/EFT.

• Registry Setting:
• The 'Enable Payment Acknowledgement' registry setting is enabled.
• The 'Prevent Posting Payments Unless Payment has been Acknowledged' registry setting is set to '1'.
• The 'Check Number' registry setting is set to '1'.
• The 'Posting Date for Automated 835s' registry setting is set to '2'.
• Claim Adjustment Group/ reason code Definition:
• A group code is selected for the credit adjustment code and debit adjustment reversal code. Note the adjustment codes and group code setup.
• Facility Defaults:
• The 'File Input Path On Server For 835 Files' input box set to desired path.
• The 'Output Path On Server For Electronic Files' input box set to the location where electronic files are saved.
• 835 Import/Export File Configuration:
• The 'Process File Path' input box set to desired location to be used to store the 835 file which is ready to process (i.e. "c:\Billing\835 \proc\").
• The 'Successful File Path' input box set to desired location to be used to store the 835 file which is successfully processed (i.e. "c:\Billing\835 \succ\").
• The 'Error File Path input box set to desired location to be used to store the 835 file which is not processed successfully (i.e. "c:\Billing\835 \error\").
• The 'Default 835 Filing User' input box is set to desired username.
• The 'Processing Interval' input box is set to desired value.
• The 'Interval Units' radio button is set to desired value.
• Admission:
• Admit a client into an outpatient episode. Note the Client id/name, Admission date/program.
• Guarantor/Payors:
• An existing guarantor is identified who have a Financial Class that has the Extended Data Element for '(1500) System Financial Class' set to 'Self Pay'. Note the guarantor codes/names.
• 837 section:
• Set the Submitter Payer Identification Code (1000A-N1-04) input box to the value that match with the N1*PR-04 segment of the 835 file (i.e.N1*PR*1000A-N1-2*XV*1000A-N1-04~).
• Financial Eligibility:
• The desired guarantors identified above are assigned to the client. Note the primary and secondary guarantor.
• Client Charge Input:
• A service is rendered to the client.
• Client Ledger:
• Make sure the service is distributed to one of the guarantors assigned to the client.
• Close charges.
• Electronic Billing:
• Claim the service using the 837 Professional bill for the guarantor.
• Create an 835 file based on the claim information found in the 837 professional bill.

1. Place the 835 file created in the setup section in the Process File Path folder identified in the 'Facility Defaults' form (i.e. "c:\Billing\835 Files\proc\").
2. Wait for desired time set up in the 'Facility Defaults' form.
3. Verify that the file will be removed from the Process file folder and added to the Success folder.
4. Open the '835 Health Care Claim Payment/Advice' form.
5. Select 'Post File' option.
6. Select the file that is recently moved to Success folder.
7. Verify the status of the file is 'Partial-Posted'.
8. Verify the Check/EFT# is populated correctly with the status of unacknowledged in the 'Check/EFT#' checkbox.
9. Close the form.
10. Open the ‘Payment Acknowledgment’ form.
11. Enter desired value in ‘Batch Number’.
12. Select desired ‘Posting Code’.
13. Enter desired value in ‘Check/EFT Number’ from the TRN*02 segment of the 835 file created in the setup.
14. Enter desired value in ‘Amount’ that matches the amount entered in the CLP*04 segment of the 835 file.
15. Select desired ‘Guarantor’ set up in the setup section. Note: If a ‘Self-Pay guarantor is selected, the ‘Client’ field will be enabled.
16. Enter desired value in ‘Name/Source’.
17. Enter desired value in ‘Client’, if enabled.
18. Enter desired value in ‘Check/EFT Date’ that matches the date entered in the BPR*16 segment of the 835 file.
19. Enter desired value in ‘Receipt Date’.
20. Enter desired value in ‘Deposit Date’.
21. Select desired ‘Treatment Service’.
22. Select desired ‘Category’.
23. Enter desired value in ‘Bank Ref #’.
24. Enter desired value in ‘Comments’.
25. Click [File].
26. Verify that the ‘Payment Acknowledgment’ message is received and states the following: Filed successfully. The Transaction Number is [number] Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
27. Click [No].
28. Close the form.
29. Wait for desired time set up in the 'Facility Defaults' form.
30. Open the 'Client Ledger' for the client.
31. Verify the payments are posted correctly on the ledger.
32. Open the 'Crystal Report' or any other SQL Data viewer.
33. Create a query to retrieve data from the SYSTEM.billing_pay_adj_history table.
34. Validate the check number field contains check number from the TRN-02 segment of the 835 file.
35. Validate the date of payment column contains the check date as 'date of payment' when the 835 file is posted.
36. Validate the 'pay_ack_transaction_num' displays correct transaction number for the check which is acknowledged in the 'Payment Acknowledgement' form.

• Registry Settings:
• Avatar PM->System Maintenance->Client Merge->->->Allow Merging Into Existing Episode = Y.
• Avatar PM->System Maintenance->Client Merge->->->Allow Merging Of All Client Data Through Single Filing = Y.
• Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement = Y.
• Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged = ‘5’ at a minimum.
• User Definition has been used to give the tester access to the 'Payment Acknowledgement' form and the ‘SYSTEM.unacknowledged_payments’ table.
• Program Maintenance:
• Program 1 exists.
• Program 2 exists.
• Client 1:
• Is enrolled in Program 1. Note the client ID.
• Financial Eligibility record is for a self-pay guarantor.
• Client Charge Input has been used to create a charge that distributed to the self-pay guarantor.
• Deposit Entry has been used to make a payment for the self-pay guarantor. Note the date and amount.
• Crystal Reports or other SQL reporting tool has been used to create a query of the 'SYSTEM.unacknowledged_payments' table, specific to Client 1. The query results have been validated and saved.
• Client 2: Is enrolled in Program 2. Note the client ID.

1. Open ‘Client Merge’.
2. Enter ‘Client 1’ in ‘Source Client’.
3. Enter ‘Client 2’ in ‘Target Client’.
4. Select ‘Yes’ in ‘Merge All Client Data Through Single Filing’.
5. Select ‘Yes’ in ‘Create New Episode On Merge’.
6. Click [File].
7. Click [Yes].
8. Click [OK].
9. Close the form.
10. Use Crystal Reports or other SQL reporting tool to create a query of the 'SYSTEM.unacknowledged_payments' table, specific to Client 1.
11. Validate that no results are returned.
12. Use Crystal Reports or other SQL reporting tool to create a query of the 'SYSTEM.unacknowledged_payments' table, specific to Client 2.
13. Validate that the query results are equal to the saved results from setup, except for the ‘Episode_Number’, which will be ‘2’, and the ‘PATID’ field, which will be the ID of Client 2.
14. Close the query results.

• Registry Settings:
• Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement = Y.
• Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged = ‘5’ at a minimum.
• User Definition has been used to give the tester access to the 'Payment Acknowledgement' form and the ‘SYSTEM.unacknowledged_payments’ table.
• Admit a new test client that will be used in the ‘Client Delete’ form. Note the client’s ID.
• Assign a Financial Eligibility record to the client.
• Use 'Deposit Entry' to post a payment to the client. Note the details of the payment.
• Use Crystal Reports or other SQL reporting tool to query the 'SYSTEM.unacknowledged_payments' table, specific to the client. Validate that payment data is correct. Save the query.

1. Open ‘Delete Service’
2. Select the desired ‘Client ID’.
3. Enter the desired ‘Start Date’.
4. Click the ‘End Date’ ‘T’ button.
5. Select ‘No’ in ‘Would You Like To Post A Charge Reversal Against The Selected Services’.
6. Click [Display Client].
7. Select the payment in the ‘Service Delete’ checklist.
8. Click [OK].
9. Click [Delete].
10. Click [OK].
11. Click [Yes].
12. Click [OK].
13. Close the form.
14. Open ‘Delete Last Movement’.
15. Enter desired client in ‘Select Client’.
16. Click [OK].
17. Click [OK].
18. Click [OK].
19. Select the ‘Episode Number’.
20. Click [Submit].
21. Click [Yes].
22. Open ‘Client Delete’.
23. Click [OK].
24. Enter the desired ‘Client ID’.
25. Click [Submit].
26. Use Crystal Reports or other SQL reporting tool to query the 'SYSTEM.unacknowledged_payments' table, specific to the client. Validate that no results are returned.

• Registry Settings:
• Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement = Y.
• Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged = ‘5’ at a minimum.
• User Definition has been used to give the tester access to the 'Payment Acknowledgement' form and the ‘SYSTEM.unacknowledged_payments’ table.
• Admit a new test client that will be used in the ‘Change MR#’ form. Note the client’s ID.
• Assign a Financial Eligibility record to the client.
• Use 'Client Charge Input' to place a charge on the client's account.
• Use 'Deposit Entry' to post a payment to the client. Note the details of the payment.
• Use Crystal Reports or other SQL reporting tool to query the 'SYSTEM.unacknowledged_payments' table, specific to the client. Validate that payment data is correct. Save the query.

1. Open ‘Change MR#’.
2. Select the client admitted above.
3. Click [Assign MR#].
4. Validate that the ‘New Client ID#’ contains a different client ID noted in setup. Note the ID.
5. Click [Submit].
6. Use Crystal Reports or other SQL reporting tool to query the 'SYSTEM.unacknowledged_payments' table, specific to the client ID noted in setup.
7. Validate that no results are returned.
8. Use Crystal Reports or other SQL reporting tool to query the 'SYSTEM.unacknowledged_payments' table, specific to the client ID noted in ‘Change MR#’.
9. Validate that the results data is the same as the saved query, except for ‘PATID’, which will contain the ID noted in ‘Change MR#’.
10. Close the query.

• Registry Settings:
• Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement = Y.
• Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged = ‘0'.
• Dictionary Update:
• Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
• Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
• Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
• Posting/Adjustment Codes Definitions:
• 'Payment' definitions exist. The 'Payment' definition may be a 'Credit' (payment) or a 'Debit' (reversal). The definitions may have a value in the ‘Payment Acknowledgement Type’ field. Only 'Payment' definitions will be available in the 'Payment Acknowledgement' section of the 'Payment Acknowledgement' form.
• 'Adjustment' definitions exist. The definitions may have a value in the ‘Payment Acknowledgement Type’ field. All ‘Adjustment’ and 'Payment' definitions will be available in the ‘Payment Acknowledgement’ form in the ‘Post Payment Accounting Entry' section of the 'Payment Acknowledgement' form.
• User Definition has been used to give the tester access to the 'Payment Acknowledgement' form and the ‘SYSTEM.unacknowledged_payments’ table.
• Agency uses the myHealthPointe payment portal to accept patient electronic payments.
• Clients:
• Client 1:
• Is enrolled in myAvatar and has an outstanding Self-Pay balance.
• Payment is made in the myHealthPointe payment portal. Note all information regarding the payment.
• Client 2: Is enrolled in myAvatar and has an outstanding Self-Pay balance.
• Tester can create a query of SQL tables.

1. Create a query of the 'SYSTEM.billing_pay_adj_history' table, specific to 'Client 1' using the 'PATID'.
2. Validate the data for the following fields and any other desired fields: 'GUARANTOR_ID', 'date_of_payment', 'payment_amount', and 'option_id' which will contain 'PatientPortal' indicating that the payment was made in the myHealthPointe payment portal.
3. Open 'CareFabric Monitor'.
4. Validate the PatientPortalPaymentProcessed dialog contains "1. Payment Amount 2. Payment method: ACH or CC 3. Account ID 4. Transactional ID".
5. Open 'Client Ledger' and process the report.
6. Validate that the payment displays in the report.
7. Close the report.
8. Close the form.
9. Open 'Registry Settings'.
10. Change the value of the 'Prevent Posting Payments Unless Payment has been Acknowledged' registry setting to include minimum values of '5&6',
11. Click [Submit].
12. Click [OK].
13. Click [No].
14. A payment is made in the myHealthPointe payment portal. Note all information regarding the payment.
15. Create a query of the 'SYSTEM.unacknowledged_payments' table, specific to Client 2, using the 'PATID'.
16. Validate that payment data is correct. Save the query.
17. Open 'Client Ledger' and process the report.
18. Validate that the payment does not display in the report.
19. Close the report.
20. Close the form.
21. Open the 'Payment Acknowledgement' form.
22. Select the 'Post Front Office and myHP Payments' section.
23. Click 'T' in 'Payment Collection Date'.
24. Select desired value in 'Treatment Service'.
25. Select 'myHP' in 'Type'.
26. Click [Review].
27. Select the row specific to 'Client 2'.
28. Click [OK].
29. Enter desired 'Batch Number'.
30. Enter desired 'Deposit Date'.
31. Select desired 'Category'.
32. Enter desired 'Bank Ref#'.
33. Enter desired 'Comments'.
34. Click [Post].
35. Refresh the query of the 'SYSTEM.unacknowledged_payments' table, specific to Client 2.
36. Validate that the table no longer contains data for 'Client 2'.
37. Create a query of the 'SYSTEM.billing_pay_adj_history' table, specific to 'Client 2' using the 'PATID'.
38. Validate the data for the following fields and any other desired fields: 'GUARANTOR_ID', 'date_of_payment', 'payment_amount', and 'option_id' which will contain 'PatientPortal' indicating that the payment was made in the myHealthPointe payment portal.
39. Open 'CareFabric Monitor'.
40. Validate the PatientPortalPaymentProcessed dialog contains "1. Payment Amount 2. Payment method: ACH or CC 3. Account ID 4. Transactional ID".
41. Open 'Client Ledger' and process the report.
42. Validate that the payment displays in the report.
43. Close the report.
44. Close the form.

• Registry Settings:
• Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement = Y.
• Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged = ‘0'.
• Dictionary Update:
• Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
• Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
• Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
• Posting/Adjustment Codes Definitions:
• 'Payment' definitions exist. The 'Payment' definition may be a 'Credit' (payment) or a 'Debit' (reversal). The definitions may have a value in the ‘Payment Acknowledgement Type’ field. Only 'Payment' definitions will be available in the 'Payment Acknowledgement' section of the 'Payment Acknowledgement' form.
• 'Adjustment' definitions exist. The definitions may have a value in the ‘Payment Acknowledgement Type’ field. All ‘Adjustment’ and 'Payment' definitions will be available in the ‘Payment Acknowledgement’ form in the ‘Post Payment Accounting Entry' section of the 'Payment Acknowledgement' form.
• User Definition has been used to give the tester access to the 'Payment Acknowledgement' form and the ‘SYSTEM.unacknowledged_payments’ table.
• Agency uses the myHealthPointe payment portal to accept patient electronic payments.
• Clients:
• Client 1:
• Is enrolled in myAvatar and has an outstanding Self-Pay balance.
• Payment is made in the myHealthPointe payment portal. Note all information regarding the payment.
• Client 2: Is enrolled in myAvatar and has an outstanding Self-Pay balance.
• Tester can create a query of SQL tables.

1. Create a query of the 'SYSTEM.billing_pay_adj_history' table, specific to 'Client 1' using the 'PATID'.
2. Validate the data for the following fields and any other desired fields: 'GUARANTOR_ID', 'date_of_payment', 'payment_amount', and 'option_id' which will contain 'PatientPortal' indicating that the payment was made in the myHealthPointe payment portal.
3. Open 'CareFabric Monitor'.
4. Validate the PatientPortalPaymentProcessed dialog contains "1. Payment Amount 2. Payment method: ACH or CC 3. Account ID 4. Transactional ID".
5. Open 'Client Ledger' and process the report.
6. Validate that the payment displays in the report.
7. Close the report.
8. Close the form.
9. Open 'Registry Settings'.
10. Change the value of the 'Prevent Posting Payments Unless Payment has been Acknowledged' registry setting to include minimum values of '5&6',
11. Click [Submit].
12. Click [OK].
13. Click [No].
14. A payment is made in the myHealthPointe payment portal. Note all information regarding the payment.
15. Create a query of the 'SYSTEM.unacknowledged_payments' table, specific to Client 2, using the 'PATID'.
16. Validate that payment data is correct. Save the query.
17. Open 'Client Ledger' and process the report.
18. Validate that the payment does not display in the report.
19. Close the report.
20. Close the form.
21. Open the 'Payment Acknowledgement' form.
22. Select the 'Post Front Office and myHP Payments' section.
23. Click 'T' in 'Payment Collection Date'.
24. Select desired value in 'Treatment Service'.
25. Select 'myHP' in 'Type'.
26. Click [Review].
27. Select the row specific to 'Client 2'.
28. Click [OK].
29. Enter desired 'Batch Number'.
30. Enter desired 'Deposit Date'.
31. Select desired 'Category'.
32. Enter desired 'Bank Ref#'.
33. Enter desired 'Comments'.
34. Click [Post].
35. Refresh the query of the 'SYSTEM.unacknowledged_payments' table, specific to Client 2.
36. Validate that the table no longer contains data for 'Client 2'.
37. Create a query of the 'SYSTEM.billing_pay_adj_history' table, specific to 'Client 2' using the 'PATID'.
38. Validate the data for the following fields and any other desired fields: 'GUARANTOR_ID', 'date_of_payment', 'payment_amount', and 'option_id' which will contain 'PatientPortal' indicating that the payment was made in the myHealthPointe payment portal.
39. Open 'CareFabric Monitor'.
40. Validate the PatientPortalPaymentProcessed dialog contains "1. Payment Amount 2. Payment method: ACH or CC 3. Account ID 4. Transactional ID".
41. Open 'Client Ledger' and process the report.
42. Validate that the payment displays in the report.
43. Close the report.
44. Close the form.