April round up
In April we introduced the new price grid tool and with it the ability to bulk update room rates, booking rates and contract fees. We also expanded the API with new endpoints for invoice item types, location contacts and billing contacts, along with numerous other improvements and fixes.
Bulk fee and rate updaters
CareHQ now supports updating target room rates, booking rates and contract fees in bulk, saving you time and reducing billing errors. Find out more about bulk updating rates and fees.
Other updates & fixes
- New video guide uploaded for configuring your room rate matrix.
- New video guide uploaded for bulk updating contract fees and booking rates.
- Added read API endpoints for invoice item types.
- Added read API endpoints for location contacts.
- Added read API endpoints for billing contracts.
- Added user status (active, suspended) to application usage report.
- Added room name/no. to the workings sheet on the location performance report export.
- Added a notes field to bookings.
- A phone/mobile number or email is now required for care enquiries.
- Added learning disability care as a service option for locations.
- Added support for setting a fixed until date for fees against billing contracts.
- Fixed issue where sorting with the location column on the app usage report would generate an error.
- Fixed issue with some date fields within the API not accepting correctly formatted dates.
- Changing the rate of a booking on the same date as the booking starts now updates the existing booking instead of creating a new one and ending the old one.
- Fixed issue where updating an action via the API would generate an error.
- Removed Save & book button from update service user page.
- Fixed issue where the same service user could appear multiple times when using the swap rooms UI.
- Optimised performance of billing discrepancies check (with future scale requirements in mind).
- Fixed issue where the care fund tracker would error if the predicted date when funds would deplete exceeded sensible bounds (e.g. after 31st December 9999).
- Fixed issue where figures within the location performance report could be inaccurate when users specified short periods (less than the default 28 days).