A deleted time entry could still be billed
This is the one to read, and it came from a customer telling us their deleted entries were showing up as billable.
They were right. Deleting a time entry hides it from your timesheet immediately — that part always worked. But the monthly billing run was not looking at whether an entry had been deleted. So a deleted entry still appeared in the billing preview as billable time, and if you carried on through the run, it was invoiced to your customer and marked as billed.
An hour you deleted and an hour you worked looked identical to the biller.
Three separate places had the same blind spot, and all three are fixed:
- The billing preview, which is where you decide what to invoice.
- The invoice generator, which is what actually charges the customer.
- The time detail report that accompanies a billing run, which would have listed deleted hours as work done.
It could also spend a prepaid block twice
The same problem had a second effect on prepaid customers, and it is worth spelling out because the money involved is theirs.
When you delete a time entry that used prepaid hours, those hours are returned to the block — the balance goes back up, correctly. But because the billing run could not see that the entry was deleted, it picked the entry up again and drew the same hours off the block a second time, then billed them. One entry, one set of hours, deducted twice.
Both of these are now closed off at every point in the billing run, including one that only bites if someone deletes an entry while a billing run is in progress.
What to check
This is not a recent regression — it dates back to before this year's platform move and has been present for as long as monthly billing has. So it is worth a look at any period you have billed, not just recent ones:
- Compare a recent invoice against the timesheet for that customer and period. If the invoice covers more hours than the timesheet shows, deleted time is the likely reason.
- Prepaid customers: check block balances. If a block has been drawn down further than the entries against it explain, that is the second bug's signature.
We would rather you checked and found nothing than not thought to look. If something doesn't reconcile, tell us and we will help you work out what was affected.
One thing still to fix
Being straight about the edge of this: the time reports still count deleted hours. If you look at reported hours or revenue for a past period, deleted entries are still in that total. Nothing is being billed from it — billing is fixed — but the reporting figure and the invoice can now disagree, and the invoice is the one that is right.
We left that alone deliberately rather than rushing it, because fixing it changes totals for months you may already have reconciled against, and that deserves its own release rather than being smuggled into this one.
Submitting a time entry twice no longer spends prepaid twice
Related, and found separately: double-clicking save on a time entry — or a slow connection causing the request to go twice — could create the entry once but deduct the prepaid hours twice. The second submission is now refused instead of quietly charging the block again.
Money fields now behave like money fields
Every amount you type is now handled by the same input, and it formats itself when you click
away — type 1500 and see 1,500.00. Previously different screens handled amounts differently,
so what you typed and what got saved were not always obviously the same thing.
Dates and currency now come from one place across the app too, which fixes rows in lists that were formatting the same value two different ways depending on which screen you reached them from.
One invoice line-item editor instead of three
Editing invoice lines used to work slightly differently on the new-invoice screen, the edit screen and the detail view — different layouts, different behaviours, occasionally different results. They are now one editor. The same has been done for client records, where creating and editing a client were two separate forms that had drifted apart.
You get warned before losing unsaved work
- Closing a form with unsaved changes now asks first, instead of discarding them silently.
- Selecting text inside a dialog no longer closes it. Dragging to highlight a value and having the whole form vanish was maddening, and it is fixed.
Quote and purchase order fixes
- A quote line that fails to save now tells you. It used to move you on to the next screen as though the save had worked, so a line could go missing without a word.
- Invoice titles are editable.
- Quote terms and internal notes are wired up properly, along with the project selector.
- Purchase orders carry billing details over from the quote they came from, rather than making you retype them.
Xero
- Sync controls no longer appear for people who cannot use them. If your access does not permit changing the Xero connection, the buttons are simply not offered, rather than appearing and then failing.
- Sync errors are readable. The error banner was passing raw technical text straight through; it now shows something written for a person.
- Permissions on Xero actions are consistently applied across every action that changes something.
Smaller things
- Creating things uses one consistent verb across the app, status colours mean the same thing everywhere, and delete sits in the same place on every screen.
- Renewals and prepaid balances read through Claude picked up further fixes following the reporting problems in the last release.
- General reliability and stability improvements.