Skip to main content

Feedback Request: Non-Billable Tasks within Billable Projects

  • September 16, 2026
  • 1 reply
  • 22 views
  • Translate All

Adelina Basyrova
Acumatica Moderator
Forum|alt.badge.img+1

We’re considering introducing a new setting in Acumatica that would allow individual project to be marked as billable. The question is about the project tasks. Does it happen in your practice, so the billable project is configured with a non-billable task?

For example, a billable project might include internal administration, rework, training, or warranty-related tasks that should be tracked for cost and profitability under a separate project task (and excluded from customer billing).

We’d appreciate your feedback:

  • Do you currently have projects that are billable but contain non-billable tasks? 

  • What scenarios require this?

  • Are there any exceptions or additional controls we should consider?

Please share examples of your current workflows and how you would expect this setting to behave.

Thank you!

1 reply

Eric Ratté
Jr Varsity I
Forum|alt.badge.img+4

Hi, 

Yes, within a project, there are tasks that are not billable.

For example, the project planning can be a non-billable milestone (project task). Also, all administrative activities such as getting a permit or sometimes documentation are not billable. 

Therefore, at the project-level, the project is billable but some project tasks (engineering, getting the drawings, taking mesearements) may incure costs (mostly labour) but are not billable.

Some other times, scheduled values (revenue project tasks - billable) may be imposed by the customer but do not correspond to the way the operations manage the project, the execution is planned and progress as well as costs are entered and meseaured (cost project tasks - unbillable).

 

I already seen situations were some parts of a project would be billed by a third party. Let say that a specialized constractor is performing the job for a general contractor. So, the GC is billed for the work performed. At one point, the final customer wants to change something and he should pay for this directly. Currently, we can bill a project task separately and change the customer location but the customer should stay the same as the one from the project.

We have to use a workaround or in 26R2, create a child project but…

Translate