Skip to main content

Avatar PM 2024 Update 80

Product Requirements and Recommendations

Avatar PM required
RADplus required

Recommended Update Level

Avatar PM 2024 Monthly Release 2024.01.01
Avatar PM 2024 Update 44
Avatar PM 2024 Update 72
RADplus 2024 Monthly Release 2024.01.01

Product Update Description

An issue with the 'Remittance Processing' widget where transactions may not file in the 'SYSTEM.billing_pay_adj_history' table is resolved.

Required Updates

None

Included Updates

8, 9, 16, 17, 23, 28, 29, 31, 34, 35, 42, 44, 46, 57, 60, 77

Details

NEW0 CHANGED0 FIXED1
Fixed (1)
Payment by Posting Date
an Isue is resolved where after creating and posting a batch in the Remittance Processing widget, the user was unable to run a Payment by Posting Date report using either the check number or the receipt number used on the batch posted. The report returned no records found. This issue was specific to batches posted through the Remittance Processing widget. KB0076858 v0.01
An issue in the Remittance Processing widget has been addressed.
Users can now create and post a batch in the widget, and subsequently run a Payment by Posting Date report using either the check number or the receipt number used on the batch posted.
The report will now return the correct records.
This update applies specifically to batches posted through the Remittance Processing widget.
Topics
• Remittance Processing
 
Acceptance Tests

AV-98605 Summary | Details
Payment by Posting Date
Scenario 1: Remittance Processing widget - Creating / Saving / Editing / Posting a remittance batch - Unclaimed services
Specific Setup:
  • Home View:
  • The 'Remittance Processing' widget is added in the home view.
  • Registry Setting:
  • The registry setting ‘Prevent Posting Payments Unless Payment has been Acknowledged’ does not include the value ‘7’.
  • Posting/Adjustment Codes Definition:
  • Existing posting code(s) are identified to be used for Payment, Adjustment, and Transfer.
  • Admission:
  • An existing client is identified, or a new client is admitted. Note the client's id/name, episode number, and admission program.
  • Client A.
  • Guarantors/Payors:
  • Guarantors are identified, or new guarantors are created to be assigned to the client. Note the guarantor's code/name.
  • Guarantor 1
  • Guarantor 2
  • Financial Eligibility:
  • The guarantors identified above are assigned to the client.
  • Recurring Client Charge Input:
  • 5-6 services are rendered to the client. Note the service start/ end date and service code used.
  • The charges are closed.
  • Client Ledger:
  • The services are distributed to the guarantor assigned to the client in the financial eligibility record.
Steps
  1. Open 'Client Ledger'.
  2. Run the ledger for 'Client A'.
  3. Verify that there are services charged and they are closed.
  4. Close the report.
  5. Select [No].
  6. Locate the 'Remittance Processing' widget on the home view.
  7. Select 'Create Batch' in the 'Action for Batch' field.
  8. Enter a description in the 'Description' field. Note the batch description.
  9. Enter the desired date in the 'Posting Date' field.
  10. Enter the desired date in the 'Receipt Date' field.
  11. Enter the desired date in the 'Deposit Date' field.
  12. Leave the 'Check/EFT Number' field blank.
  13. Enter any desired value in the 'Receipt Number' within the below condition:
  14. Only Alphabets.
  15. Select all other fields as required.
  16. Navigate to the 'Remittance Details' section.
  17. Click [Add Row].
  18. Enter 'Client A' in the 'Client' cell.
  19. Verify that the system displays all the matching clients.
  20. Select 'Client A' from the results.
  21. Double-click the 'GuarID#' cell.
  22. System displays all the available guarantors of the client.
  23. Select 'Guarantor 1'.
  24. If the client has 'Claimed' services then search any particular claim number and verify the system returns only the searched 'Claim Number'.
  25. If the client has 'Unclaimed' services then the result will be returned as 'No matches found, please refine search.'
  26. Verify the 'Start Date' and 'End Date' are auto-populated with the start and end date of the services rendered to the client.
  27. Select the desired date of service to post the payment for the service.
  28. Enter the desired amount in the 'Pmt Amt' field.
  29. Select the desired code in the 'Pmt Code' field.
  30. Enter the desired amount in the 'Adj Amt' field.
  31. Select the desired code in the 'Adj Code' field.
  32. Enter the desired amount in the 'xfr Amt' field.
  33. Select the desired code in the 'xfr Code' field.
  34. Select the desired guarantor in the 'xfer to Guar' field.
  35. Click [Save and Exit].
  36. Click [OK].
  37. Go to the 'Batch' section.
  38. Select 'Yes' in the 'Remittance Ready to Post'.
  39. Click [Post Batch].
  40. Validate the successful posting message.
  41. Open the 'Crystal report' or any other SQL data viewer tool.
  42. Query the 'remittance_batch' table for 'Client A'.
  43. Validate the below in the table:
  44. Verify the 'ID' column displays the correct batch ID.
  45. Verify the 'batch_description' column displays the description of the batch created.
  46. Verify the 'deposit_date' column displays the correct deposit date as entered while creating the batch.
  47. Verify the 'receipt_date' column displays the correct deposit date as entered while creating the batch.
  48. Query the 'billing_pay_adj_history table for Client A'.
  49. Validate the table displays all the information including the below correctly for the posted batch:
  50. Verify the 'reciept_number' column displays the correct receipt number.
  51. Verify the 'check_number' column displays the correct receipt number.
  52. Verify the 'date_of_receipt' column displays the correct receipt date as entered while creating the batch.
  53. Verify the 'date_of_payment' column displays the correct posting date as entered while creating the batch.
  54. Repeat Steps 2 and 3 for 'Client A' for the below combination of value(s) for 'Check/EFT Number' and 'Receipt Number':
  55. Case 1:
  56. In step 2(f):
  57. Without any value entered in the 'Check/EFT Number' field.
  58. In step 2(g):
  59. With the value of Alphabet, Numbers, and Special characters.
  60. Example: "ALPHANUM123@".
  61. Case 2:
  62. In step 2(f):
  63. Without any value entered in the 'Check/EFT Number' field.
  64. In step 2(g):
  65. Without any value entered in the 'Receipt Number' field.
  66. Case 3:
  67. In step 2(f):
  68. With the value of Alphabet, Numbers, and Special characters.
  69. Example: "ALPHANUM123@".
  70. In step 2(g):
  71. Without any value entered in the 'Receipt Number' field.
  72. Case 4:
  73. In step 2(f):
  74. With the value of only Alphabets.
  75. Example: "ONLYALPHA".
  76. In step 2(g):
  77. Without any value entered in the 'Receipt Number' field.
Topics
• Remittance Processing