HaloPSA Guides
Documentation to assist with the setup and configuration of the HaloPSA platform
Deferred Revenue for Pre-Pay
Halo has the ability to configure deferred revenue for Pre-Pay, with plans to expland on the deferred revenue functionality in the near future. The idea is that when you invoice for prepay you will allocate the money into a separate location because you may get paid in i.e. January for work that is not carried out until May, so in order to accurately manage the accounting for the work, you may want to defer the revenue. The first thing to do is enable the setting (Configuration>Billing>General Settings>*Click into the Deferred Revenue Tab*):
Before configuring this, please make sure the following has been configured correctly:
- The setting within Configuration > Time Management is disabled:
- This option within configuration > Billing > Charge Rates, is set to 0 (disabled) or populated with a number:
- Enable the Deferred Revenue checkbox in billing general settings
- Set a Deferred Revenue customer
Set an 'Item to use for Pre Pay and Deferred Revenue Invoice line'
Now when Pre-Pay is added to a ticket, and said Pre-Pay is not consumed by a contract i.e. set all billable actions on the billing rules to be billed as Pre-Pay:
When adding billable actions on tickets, which DOES NOT require the charge type to be check as 'Is Deferred Revenue' the following will be displayed:
This type of deferred revenue doesn't require the charge type to be set as deferred revenue, as many customers will use same charge rates for different customers even if those customers are not billed the same i.e. prepay, contract, combination billing. So it would not make sense to defer payment based on charge types in the context of pre pay.
In order to defer revenue for actions on open tickets, enable this setting in Configuration > Billing > General Settings > *Click into Charge Rate Settings* "process actions on open tickets" (Open referring to tickets that have not been closed yet, not to be confused with the a status of open), it will be renamed to "Status of Tickets before they are able to be invoiced" in later versions of Halo, to stop confusion:
Newer versions:
Then on the ticket, there is evidently no contract set against this customer, I have one billable action that is Pre-Pay, as everything that is actioned for this customer goes towards Pre-Pay hours, which is shown in the Billing rules in a previous screenshot:
Now within the Deferred Revenue area of ready for invoicing, there will be an invoicable action in the Pre-Pay table:
An invoice can then be generated, which will include the customer (Deferred Revenue Customer) and the customer that the actual Pre-Pay time will be removed from:
Popular Guides
- Asset Import - CSV/XLS/Spreadsheet Method
- Call Management in Halo
- Creating a New Application for API Connections
- Creating Agents and Editing Agent Details
- Departments, Teams and Roles
- Halo Integrator
- Importing Data
- Multiple New Portals with different branding for one customer [Hosted]
- NHServer Deprecation User Guide
- Organisation Basics
- Organising Teams of Agents
- Step-by-Step Configuration Walk Through
- Suppliers