This release represents a significant investment in the billing experience, addressing feedback from teams processing high volumes of invoices daily. The changes span from UI improvements to backend audit enhancements.
Bulk Invoice Actions
The most requested feature from billing teams was the ability to work with multiple invoices at once. Previously, each invoice required individual attention—open, review, approve, send. Now, the invoice list supports multi-select with a floating action bar that appears when items are selected. Teams can approve a batch of reviewed invoices, send them all at once, or export a selection for external processing.
This is particularly valuable at month-end when billing teams need to process dozens or hundreds of invoices quickly. What previously took hours of repetitive clicking now takes minutes.
Billing Review Screen
A new dedicated review screen provides a focused workspace for checking invoices before they go out. The screen presents all the details a reviewer needs—line items, totals, customer information, payment terms—in a clean layout optimized for verification.
Auto-save runs continuously in the background, so if a reviewer steps away or the browser closes unexpectedly, their draft changes are preserved. No more lost work from forgotten save buttons.
Rate Card Improvements
Rate cards define how services are priced for different customers. The rate item editor now supports full CRUD operations including deletion, with confirmation dialogs to prevent accidental removals. The editing experience is smoother, with inline validation and immediate feedback on changes.
Audit Trail Enhancements
Every billing action now captures not just what happened, but who initiated it and who was affected. Audit logs include sender and receiver details, creating a clear chain of accountability. This is essential for compliance and dispute resolution, where teams need to trace exactly what was sent to whom and when.
Modular UI Architecture
Behind the scenes, we’ve refactored the billing UI into modular components. This doesn’t change the user experience directly, but it means we can iterate faster on billing features going forward. Each component is now self-contained and testable, reducing the risk of regressions when we add new capabilities.