A Project can contain billable work from Tasks, Timesheets, and Expenses. AIUNIFY CRM provides a Project pre-invoice workflow that allows authorized users to review eligible work before creating an Invoice.
The Project source confirms billing structures including:
The Project's billing structure affects how billable activity should be reviewed before invoicing.
Expenses can be associated with a Project when they belong to that Project's work.
Review Project Expenses to determine which expenses are:
Before an Invoice is created from Project work, use the Project's pre-invoice review process when available.
This step helps identify which billable Tasks and Expenses should become part of the Invoice.
For Project Task billing, review:
The CRM can prevent Tasks whose Start Dates are still in the future from being included as normal billable work in the Project Invoice process.
Do not alter Task dates solely to force future work onto an Invoice.
AIUNIFY CRM checks for active Timers on billable Project Tasks.
If billable Task Timers are still running, the Invoice cannot be completed normally until the applicable Timers are stopped.
The Project invoicing workflow can provide options such as:
Use these only after confirming that the affected work sessions have actually ended.
When Project Task time is converted into Invoice data, the system can construct Invoice information using the Project and selected Tasks.
Depending on the chosen billing structure, Task names and logged time can contribute to the resulting Invoice description and amount.
If the CRM reports that there are no Tasks available to bill, review:
Do not create duplicate time or change completed billing history merely to make a Task appear billable.
The Project Invoice workflow contains logic related to billed Tasks, including identifying Tasks included on the Invoice and the treatment of Tasks that become billed.
Review the resulting Project and Task records after invoicing rather than assuming all Project work has automatically been completed.
Once the Project is invoiced, the resulting Invoice becomes part of the Project and Customer financial history.
Future billing should take existing Project Invoices into account so the same Task time or Expense is not billed twice.