Skip to main content

ERPNext how-to & fixes

ERPNext Marks the Whole Timesheet Billed When You Invoice One Project: the Fix (2026)

Invoice one project from a shared timesheet and older ERPNext marks it all billed. Fixed in v15.104.0 and v16.1.0; how to avoid it and recover hours.

Updated 12 Oct 20268 min readBy ManojFirst published 30 Jul 2026

ERPNext timesheet billing had one trap that strands real revenue. A consultant logs a week across two client projects on one timesheet. You raise a Sales Invoice for the first project, and ERPNext marks the entire timesheet billed, including the second project's hours, which you never invoiced and now cannot. Frappe fixed this in ERPNext v16.1.0 (January 2026) and v15.104.0 (April 2026). This guide shows how to tell whether your version has the fix, the route that bills one project cleanly on older versions, and how to recover hours that are already locked.

The worst billing bugs don't lose you an argument with a client. They quietly stop you invoicing work you actually did. I lead ERPNext and Frappe implementations at MithTech, a team of Frappe specialists in Bengaluru. This one turned up in services firms that put more than one project on a timesheet.

Which invoicing routes exist, and what does each bill?

On versions before the fix, the trap is the difference between two routes:

RouteWhat it marks billed (before v15.104.0 / v16.1.0)Safe for multi-project timesheets?
Sales Workspace → Fetch TimesheetThe entire timesheetNo: strands the other projects' hours
Sales Invoice from the ProjectOnly that project's hoursYes
One timesheet per projectN/A: nothing to strandYes (structural fix)

From v15.104.0 and v16.1.0, the timesheet's status follows what was actually billed per time log, so a partial invoice leaves it "Partially Billed" rather than "Billed".

What actually happens in ERPNext timesheet billing?

An ERPNext timesheet holds time logs. Each log can carry a project and a billing rate. When you invoice from a timesheet, ERPNext marks the consumed logs as billed so they can't be charged twice. That guard against double billing is sensible.

The behaviour in #44167 was narrower. You create a Sales Invoice via the Sales Workspace and use Fetch Timesheet to pull one project's hours. ERPNext then marks the whole timesheet billed, not just the hours you invoiced. If the timesheet also carries hours for other projects, those hours are now flagged billed. They were never invoiced, and because the double-billing guard is what tripped, you can no longer invoice them. The report noted the problem did not occur when the invoice was created from the project, which is the workaround.

PR #51295, merged on 14 January 2026, reworked timesheet billing status across partial billing, full billing, returns and return cancellations, and Frappe closed #44167 as solved by it. It shipped in v16.1.0 and, via #53996, in v15.104.0.

Calculator

Timesheet Billing Simulator

Enter the hours per project and your rate, then toggle the invoicing route to see how much billable work each route strands.

Currently: Sales Workspace + Fetch Timesheet

Invoiced now (Project A)₹18,000
Timesheet total20 h
Stranded unbillable (Project B)₹12,000

Invoicing Project A via the Sales Workspace marks the whole timesheet billed, so Project B’s 8 h — ₹12,000 of billable work — can no longer be invoiced. That revenue is stranded until the timesheet is corrected.

Models the behaviour in frappe/erpnext #44167 (reported on v15.41.1; fixed in v16.1.0 and v15.104.0 by PR #51295). Verify on your own version before relying on it.

Which invoicing route should you standardise on?

On a fixed version, either route bills correctly; standardising on invoicing from the Project is still a good habit, because it keeps each invoice scoped to one client's work. On an older version, the route decides whether hours get stranded, so choose it deliberately rather than letting each biller pick.

Interactive

Invoicing Path Decider

Choose how your timesheets and projects are structured to see which invoicing route avoids stranding hours.

Pick how your timesheets and projects are structured.

For a single-project timesheet the route doesn't matter: marking the whole timesheet billed and marking that project's hours billed are the same thing. The trap is specific to timesheets spanning projects. There, on older versions, invoice from the Project rather than the Sales Workspace. The most robust option, where your process allows, is one timesheet per project; then the problem cannot arise on any version, which matters for firms billing many clients from shared staff, the pattern in our IT and software companies guide.

If you create invoices through the API on v16, note one change from Frappe's ERPNext v16 migration guide: a Sales Invoice no longer pulls the linked project's unbilled timesheets by default. Make the extra add_timesheet_data call (PUT /api/v2/document/Sales%20Invoice/<name>/method/add_timesheet_data).

How do you fix it and recover locked hours?

Code recipe

Diagnose · Invoice · Recover · Prevent

Copy-paste the diagnosis, the per-project invoicing route, the recovery steps for a timesheet already locked, and the habits that prevent stranding.

Confirm the whole timesheet was marked billed when only one project was invoiced, before you change how you invoice.

text
1. Open the Timesheet that won't let you invoice the
   remaining project.

2. On each Time Log row, check the "Is Billable" and
   "Billed" state:
     • Rows for the invoiced project: Billed = yes
     • Rows for OTHER projects: Billed = yes  ← the bug
       (they should still be un-billed)

3. Look at how the paid invoice was raised:
     • Sales Workspace > new Sales Invoice > Fetch
       Timesheet  → marks the whole timesheet billed
       (the #44167 path)
     • From the Project                     → marks only
       that project's hours

4. If other projects' rows are billed and were invoiced
   via the Sales Workspace, that is #44167.

0 of 5 steps done

Tick a step’s number when it is done; the ticks stay on this device.

Check your version first

bench version. If ERPNext is v15.104.0 or later, or v16.1.0 or later, new invoices will not strand hours this way; you only need to recover timesheets locked before you upgraded.

Confirm the whole timesheet was flagged

Open the timesheet that won't let you invoice the remaining project and check the billed flag on each time log. Rows for the project you invoiced should be billed; rows for other projects should not. If those other rows are flagged billed too, and the invoice was raised via the Sales Workspace, you are seeing #44167.

Invoice from the Project instead

On an older version, create the Sales Invoice from each Project rather than via the Sales Workspace and Fetch Timesheet. The project route filters the time logs to that project, so it consumes and marks billed only that project's hours, leaving the others available.

Recover hours already locked

Where a timesheet is already fully flagged, don't cancel the legitimate invoice: that revenue is correct. Un-bill the wrongly flagged time logs, either by correcting the billed flag or by cancelling and re-raising via the per-project route so the flags set correctly. Then invoice the remaining projects from their own projects.

Reconcile the timesheet

Confirm that total invoiced hours across all invoices equal the timesheet's billable hours; a shortfall means hours are still stranded. On versions before the fix, re-check the flags after any return or credit note, because returns did not un-bill timesheets (#51131).

What happens when the biller isn't the person who logged the time?

The consultant who logged hours across two projects has moved on to next week's work. The person raising invoices is in accounts. They bill from the Sales Workspace because that's where invoices live, with no reason to know the route behaves differently. The stranded hours surface only when someone tries to bill the second project and can't, often at month end, under time pressure.

The fix is a billing convention, not a permission. Upgrade to a fixed version where you can. Standardise on invoicing project work from the Project and write it down for whoever raises invoices. Pair it with one timesheet per project where practical, so the safe path is also the default. Add a month-end check that compares invoiced hours to logged billable hours per timesheet, so stranded hours show up as a variance instead of a client complaint.

Draft policy for your delivery and finance leads to agree. Time on client projects is invoiced from the Project, not via the Sales Workspace. Where the process allows, one timesheet is logged per project. At month end, invoiced hours are reconciled against billable hours logged per timesheet, and any shortfall is investigated before the period closes. On ERPNext versions before v15.104.0 / v16.1.0, billed flags are re-checked after any credit note, since returns did not un-bill timesheets.

Should you invoice from the project or split the timesheet?

Staff genuinely log across projects in one sheetWork naturally separates by project
You want a workflow change, not a logging changeYou can change how time is logged
Timesheets already exist spanning projectsYou're setting the process up fresh
Billers can be trained on the routeYou'd rather remove the trap structurally
Occasional multi-project timesheetsRoutinely billing many clients from shared staff

FAQ

Why does ERPNext mark the whole timesheet billed when I invoice one project?

On versions before v15.104.0 and v16.1.0, an invoice raised via the Sales Workspace with Fetch Timesheet marked the entire timesheet billed rather than only the invoiced project's hours (#44167). Invoicing from the Project marks only that project's hours. Later versions bill timesheets per time log and show "Partially Billed".

How do I invoice only one project's hours from a shared timesheet?

Create the Sales Invoice from the Project itself. The project route filters the time logs to that project, so only its billable hours are consumed and marked billed, and the other projects' hours stay available to invoice from their own projects. On v15.104.0+ and v16.1.0+, the timesheet then shows "Partially Billed".

Which ERPNext version does this affect, and which fixes it?

It was reported on ERPNext v15.41.1 with Frappe v15.47.1 in #44167. PR #51295 fixed it; it shipped in v16.1.0 (20 January 2026) and, through #53996, in v15.104.0 (7 April 2026). Confirm on your own site with a two-project test timesheet.

How do I recover hours that were wrongly marked billed?

Don't cancel the correct invoice. Un-bill the wrongly flagged time logs, by correcting the billed flag or by cancelling and re-raising via the per-project route so the flags set correctly, then invoice the remaining projects from their own projects. Reconcile total invoiced hours against the timesheet's billable hours afterwards.

What happens if I don't fix it?

Real billable work becomes uninvoiceable. The hours are flagged as already charged when they weren't, so that revenue is stranded until you correct the flags. Across many multi-project timesheets it adds up to a gap between hours delivered and hours billed, which usually surfaces as a month-end shortfall nobody can explain at once.

Does cancelling the invoice or raising a return un-bill the timesheet?

From v15.104.0 and v16.1.0, yes: the same fix handles returns and return cancellations (#51131). On older versions it did not, so check the flags on the affected time logs after any credit note before re-invoicing.

What is the bottom line?

On a current ERPNext release this is fixed: timesheets bill per time log and returns un-bill. On an older one it is a routing problem that looks like a bug: the same timesheet bills correctly from the project and incorrectly from the workspace. Either way, invoice project work from the project, keep one timesheet per project where you can, and reconcile invoiced hours against logged hours each month, so the hours your team worked stay billable.

Your next step

Billable hours going missing between the timesheet and the invoice?

ERPNext how-to & fixes

Now see what an audit finds in yours

When the same problems keep coming back, tick what you see and get an audit of the ERPNext you have, then fixes in order of what costs you most.

Comments & ratings

No comments yet. Start a new discussion.

0

Manoj · Published on 30 July 2026

Worked with us? Leave a Google review

Questions about this? Talk to the team.

Book a 30-minute Google Meet, WhatsApp us, or send a message. The engineer who works on this replies.

Send us a message

Your details go to our team's CRM and are used only to reply.