Aging Report Excludes Claim Submissions Excluded from Aging
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Finance >Reports >GL Transactions >All Transactions
- Finance >Reports >GL Transactions >A/R Account Balances
- Client>Reports>Finance Reports>A/R Account Balances
- Accounts Receivable Balances
- Claims Maintenance
- Claim Submission
Scenario 1: GL Transactions - A/R Account Balances Report
Specific Setup:
Claim has been submitted to Payer.
Steps
- Navigate to "Finance > Reports > GL Transactions > A/R Account Balances".
- Set "Month/Year "and "Parameters" for "Claim" from preconditions.
- Select "Report Selection"(example Aging Details by Receiver - Age From Service Date).
- Click "Preview" button.
- Validate the "Claim" from preconditions displays.
- Click on "Claim".
- Click on "Submissions", click on "Edit".
- Check "Exclude from Aging Reports", save.
- Close "Submission" and "Claim".
- Close "Report".
- Click "Preview".
- Validate "Claim" no longer displays on "Report".
- Scroll to "Report Footer".
- Validate "Grand Totals:" display "Payer/Contracts".
|
Topics
• Reports • Finance
|
Billing Run Management Screen Displays Batches
Scenario 1: Billing Run Management Screen Displays Batches
Specific Setup:
Test system must contain at least one finance batch.
Steps
- Navigate to "Finance>Accounts Receivable>AR Batch Form>Billing Batches Management".
- Validate that "Batches" are available for review.
|
Topics
• Finance
|
Improved Claim Output Performance
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Finance >Processing >Create Claims/Invoices >Processing for a Period
Scenario 1: Validate Getting Output For Multiple Billing Runs
Specific Setup:
Requires a system with multiple billing runs.
Steps
- Navigate to "Finance > Processing > Create Claims/Invoices > Processing for a Period".
- Select desired "Submitter".
- Open "Billing Run" from preconditions.
- Click on the "Receiver" link.
- Click "Get Output" button.
- Click "Create AR Output File".
- Validate "Output" window opens.
- Repeat steps 4-7 for the remainder of the "Billing Runs" from preconditions.
|
Topics
• Finance
|
myEvolv NIAM Login
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Agency by Managing Office
- Agency > Staff & Security > Staff Information > Staff Profiles with Security
- Staff Listing - Agency Employees (By People ID)
- Staff with Security [EDIT]
- Agency [EDIT]
- Staff Look Up Their Own Information
- Setup > System > EvolvCS System Setup > System Settings/Preferences
- Staff Information
- Staff with Security (EDIT Form)
- Staff with Security
Scenario 1: NIAM Log In with Active Directory
Scenario 2: NIAM Log In without Active Directory
Scenario 3: NIAM Log In Without Active Directory With Two Agencies
|
Topics
• Third Party Solution • NIAM
|
Adding Multiple Checks To A Deposit Slip
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Finance >Accounts Receivable >Deposit Slip/Batch Checks >Batch
- Select Deposit Slip -- Webpage Dialog
- Deposit Slip Only
- Payers and Self-Payers
- Receiver Information by Payer
- GL Cash Accounts
- GL A/R Temporary Unallocated Account
- Finance >Accounts Receivable >Deposit Slip/Batch Checks >Deposit Slip - Self Pay
Scenario 1: Create A Self Pay Deposit Batch With Multiple Checks
Steps
- Navigate to "Finance > Accounts Receivable > Deposit Slip/Batch Checks > Deposit Slip - Self Pay".
- Click on "Select Deposit Slip" button.
- Set "Batch #" input box to desired value.
- Click "Search" button.
- Click "New" button.
- Set desired "Batch Number".
- Set "Deposit Date".
- Select desired "Cash Account".
- Select desired "Temp Unallocated Account".
- Click "Save".
- Within the "Checks" SubForm select desired "Payor" and "Receiver".
- Set the desired "Check Number", "Check Date", and "Amount".
- Validate the second row within the SubForm appears.
- Repeat steps 11 and 12 in the second row.
- Validate a third row within the SubForm appears.
- Set the "Total Deposit Amount".
- Save.
- Validate the third row is still visible.
- Repeat steps 11 and 12 in the third row.
- Validate a fourth row within the SubForm appears.
- Save.
- Validate the fourth row is still visible.
|
Topics
• Finance
|
837 Output Where Batch Includes Service Flagged "Is LA COS Service"
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Create Claims Invoices
- Submitter -- Webpage Dialog
- Unread Alerts
- Claim Output Ready - Internet Explorer
- 837 Output File
Scenario 1: Validate Client's IBHIS ID in NTE Segment On 837 Output File For A Wraparound Outreach Event
Specific Setup:
- Billable Outreach Event configured.
- Program is set for "is wraparound".
- Billing payment plan scheme linked to Outreach event with "is wraparound" is checked.
- Claim Receiver set to output 837p.
- Event form displays ‘All Wraparound Clients Program Enrollment’ LUT.
- For the LUT to display People, a Program with People enrolled needs to be flagged as ‘Is Wraparound’.
- Wraparound Client has a IBHIS ID.
- Billable Outreach service with Wraparound Person configured and billed.
Steps
- Navigate to "Finance > Processing > Create Claims/Invoices > Processing for a Period".
- Create a "Billing Run" to capture "Services" from preconditions.
- Upon completion of "Billing Run", open "Batch".
- Click "Create AR Output File".
- Click "Retrieve the file - File Name".
- Open the "837 text" file.
- Verify "NTE Segment" Exists (NTE*DCP*number).
|
Topics
• Finance • LA IBHIS
|