Bug Fixes and Improvements for March 17, 2026

New update for Homeworks, including several bug fixes and improvements:

Bug Fixes

• Invoicing: Fixed an issue where invoice line items could show the billing address instead of the correct property when visits were completed in Mobile (Field Force), so invoices now reflect the right property for each completed visit.
• Level Billing: Fixed an issue where assigning a Level Billing agreement could remove existing invoiceable items or services from a visit, so services now stay in place and duplicate entries are avoided.
• QuickBooks: Fixed an issue where non-synced customers were missing from the QuickBooks customer mapping list, so it is easier to find and map the right customers.
• Visits: Fixed a visit modal layout issue when a Level Billing agreement was attached, so visit details display more cleanly and consistently.
• Automations: Fixed an issue where Sequence Automations were not staying toggled on or off, so saved automation settings now persist correctly.
• Schedule: Fixed an issue that could prevent some users from creating recurring visits or scheduling future visits, so scheduling and rescheduling works more reliably.

Improvements

• Mobile (Field Force): Updated visit notes so hyperlinked text is more clearly styled, making links easier to spot and use in the app.
• Dispatch Board: Added support for Work Assessment records on the Dispatch Board map and in route sorting, so teams can include them in dispatch planning and optimization.
• Accessibility: Made accessibility improvements across the PHP app to address critical WCAG 2.1 AA issues and improve usability for more users.
• Estimates: Updated the line item reorder icon in Estimates to better match drag-and-drop behavior, making the interaction clearer.
• Settings: Added a tooltip to clarify that the Closed Visit Position setting only affects the CRM, not Mobile (Field Force), so teams know what to expect.
• Settings: Added a tooltip to clarify that the Event Types user privilege only affects the CRM, not Mobile (Field Force), so permission behavior is easier to understand.

Have feedback or questions? Contact our support team.