Page Comparison

This page explains about the log billing of Service log and Plant Maintenance log.

Invoicing

In terms of timing, you can send invoices to client in various waysat different stages:

1. At the end of the service: Wait until all services are completed and send one invoice.

2. Bill as you go: Invoice the client for each activity or transaction as it happens by creating an invoice before marking the service as 'completed.' For this, the Log should not have its own Charge Type. These invoices will also appear in the Completion tab.

3. Both: A combination of both methods: bill for each transaction and, when the service is finished, send an invoice for any remaining items.

In the term of billing sourceterms of where to bill from, you can invoice the Client:

• Directly from Log: normally applied for Small Job or by transactions via the Charge Type Input/Output based.

• By Job that Log belongs to: This method is applicable only for Jobs (mean as in a project, not the Service itself) that have the Charge Type specified as Contract Claim.

...

All the next steps are similar as normal per the Job sales Invoices process.

Log charge types

You can set the Charge Type of a Log when creating or editing and it sticks together with the Log statues.status. 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.

...

There are billing statuses to better represent the billing stages for the different Charge Types on the Log (if selected) or the Charge Type on the Job. Note that if there is no Charge Type selected on the Log, then the system uses the Job’s charge type. Refer to the Service log for more details.

...