...
You can set the Charge Type of a Log when creating or editing and it sticks together with the Log statuesstatus. If the Log Charge type is not specified, the system will use the Job’s Charge Type
While the Log's Charge Type is not mandatory, it proves beneficial in ensuring all charges are invoiced to the Job, especially when the Jobs charge type is Contract Claims.
Input and Output Based Billing: only transactions linked to this Log will be available for selection on [Get Sales] of the Job Sales Invoice screen. Even if some transactions are Deferred or Pending, the [Invoice] button will still be visible, enabling billing at a later stage. On the Job Invoice, you can choose to Save, transitioning the Log's status to ‘Allocated - Billed’ workflow status. Alternatively, you can select Save & Finalise, which not only saves the Job invoice but also changes the Log's status to Finalised - Billed status. Should additional transactions need to be added, clicking [Reopen & Unfinalise] will revert the status to Allocated - Part billed, making the Log editable again. Existing invoices remain linked, and more can be generated.
Contract Claims billing:
Automatic setting by the Job the Log belongs to:
If the Log Charge Type is undefined (null), and the Log belongs to a Job with the Charge Type set as Contract Claim, the Log Charge Type will be automatically set as Contract Claims. It is necessary to flag the Log as 'Finalised' in the invoicing process. This is a sensible step to indicate that the Job has been billed, and no further action is required. This is a logical way to ensure consistency and alignment with the Job's Charge Type.Manual billing from Contract Claim:
When the Log is not billed directly and billing is intended to be done from a Contract Claim with a manual line, there's an option to Save and Finalize the Log, indicating that no further action is needed. This step makes sense, signaling completion when billing is indirectly associated with a Contract Claim. In this the Log billing status remains ‘Unbilled’. This is logical since there is no direct connection between the Log job transactions/outputs and the invoice.
...