Marketing Beta Preview - Visit production site
Skip to main content
All Releases
v0.43.0 September 3, 2026

Time you track but don't want to bill now stays unbilled

Un-ticking "Bill time on this project" never saved — the setting was silently discarded every time, so a fixed-fee project could not be marked non-billable at all. And even if it had saved, the invoice run was ignoring it and charging those hours hourly. Both are fixed, and there are two limits worth reading about below.

"Bill time on this project" now actually saves

This came from a customer running a fixed-fee project and logging hours against it purely to compare the time spent against the estimate — not to bill it.

They un-ticked "Bill time on this project", pressed Update, reopened the project, and found it ticked again. They were right, and it was worse than it looked: the setting was being discarded on the way to the server every single time. Not saved and then lost — never saved at all.

The same gap applied when you created a project, which means until now there was no way to mark a project non-billable from anywhere in the app. The control had been on the form the whole time and had never once done anything.

It saves now, on both the create and the edit screen.

And the invoice run now honours it

Fixing the checkbox turned up something more serious behind it.

The billing preview — the screen where you choose what to invoice — was correctly leaving out time logged on a non-billable project. The invoice generator, the part that actually charges your customer, was not. It only ever looked at whether an individual time entry was marked billable, and never at the project setting.

So the two disagreed, and only one of them writes invoices.

For a customer who has both a fixed-fee project and ordinary hourly work in the same period, that meant the preview showed the flat-fee hours excluded, and the invoice that came out charged them hourly, on top of the agreed fee. The time detail report attached to that invoice left those hours out as well, so the total had no backing detail to explain it.

The invoice generator now applies exactly the same rule as the preview. The two can no longer disagree, and there is now a test that fails if they ever drift apart again.

Nothing you have already invoiced is affected

Worth saying plainly, because a billing fix usually means "go and check your invoices": this one almost certainly changed nothing you have already sent.

The reason is the first bug. The project setting could never be saved, so no project was ever in the non-billable state, so the invoice generator never had the chance to get it wrong. The overcharge described above was real but unreachable. Fixing the checkbox is what would have made it possible — which is why both fixes are shipping together rather than the easy one first.

If you have seen an invoice cover more hours than you expected for a client with a fixed-fee project, tell us and we will help you work out what happened.

Two limits to know about

Being straight about the edges of this, in the same spirit as the last release.

The client-level "Billable" toggle still does nothing

There is a Billable tick-box on the client record as well as on the project. The project one now works. The client one does not — it saves, it shows you the value you chose, and no part of billing reads it. A client marked not billable is still previewed and still invoiced as normal.

If you have been relying on that tick-box to stop a client being billed, it has not been doing that, and you should check any invoices for a client where you set it. We have not changed it in this release because switching it on would reduce invoice totals for anyone currently affected, and that deserves its own release and its own warning rather than being slipped into this one.

Reliable today: the Billable tick-box on an individual time entry has always worked and still does, and the project setting now works too.

Time reports and invoices can now disagree for one setup

If you mark an hourly-billing project non-billable, the invoice will correctly leave its hours out, but the time reports will still count those hours as revenue. The invoice is the one that is right.

This does not affect the case this release is about — a fixed-fee project's hours were already being reported against the agreed fee rather than as hourly revenue, so reports and invoices agree there.

One more thing, if you use prepaid blocks

Marking a project non-billable stops its time being invoiced from now on, but it does not give back prepaid hours that time had already drawn from a block. If you need those hours returned, un-tick Billable on the individual entries instead — that does credit them back.

Claude connection

Time entries read through Claude now report whether they are billable. That field had been coming back blank for every entry ever returned, so if you had asked Claude which of your hours were going to be invoiced, it had no way to tell you. It does now.

Smaller things

  • General reliability and stability improvements.

Ready to try these features?

Start your free trial today and see how Current can help your business.

Get Started Free