6.0.119 Billing Release Notes
Billing Release Scheduled for 6/30/25 at 9:00 PM EST
IMPORTANT NOTICE:
Please be advised that the release window for this update will be in the evening (9 PM) instead of the typical 7 AM time. The release window for this update is also 1 hour instead of the typical 30 minutes. During this time, all AIM modules will be inaccessible.
NOTICE: Release will take place from 9PM - 10PM, the application will not be accessible during the update.
It is recommended after each release; users clear their browser cache. This can be done by using the F12 key on your keyboard, right-clicking on the browser refresh button and selecting "Empty Cache and Hard Reload".
This document explains functionality updates to the AIM Online V6 Billing application. For additional information, please contact Customer Support at 1-800-726-4362 or support@aim-system.com.
Report/Queue Updates
- Added help icon to Provider Actions by Date report.
- Improved load time when opening the Reports Module.
- Improved load time for the Overall Summary Report in the A/R Reports module.
Setup Updates
- Form Definitions Setup now lists all users who have user-specific form definitions enabled in User Maintenance Setup.
Billing Updates
- AIM has begun alpha testing electronic patient bills via eServices integration. Please contact AIM Support to learn more.
- Printed bill batches now indicate the number of bills printed in the Post Transactions prompt.
- Resolved an issue where bills could not be routed to AIM ePCR for correction in some cases.
- Corrected the order of Statement Cycles in the dropdown when printing statements for specific cycles.
- When entering cities, if one or more zip codes exist for that city, they will be sorted numerically.
- Updated Automatically Remove From Timed Payments setting so that bills in timed payments now automatically leave the timed payments process once the balance reaches $0.00 instead of being released when the balance is less than the timed payment amount.
Improvements
- Resolved an error that would sometimes occur when running the Fix Ledger Balances Data Maintenance utility.