<style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><p><strong>In this guide we will cover:</strong></p><p data-pasted="true"><strong>- What is an Agreement/Contract in Halo?</strong></p><p><strong>- Initial Agreement Setup</strong></p><p><strong>- Set when Labour (actions) is covered by or associated with an Agreement</strong></p><p><strong>- Agreement Charge Types</strong></p><p><strong>- Override the Charge Rates for Labour (actions) covered by the Agreement</strong></p><p><strong>- Link Assets and Users to the Agreement</strong></p><p><strong>- Creating a Recurring Invoice for the Agreement</strong></p><p><strong>- Using Agreements</strong></p><p><strong>- Creating Agreement Types and Subtypes</strong></p><p><strong>- Agreement Expiry</strong></p><p><strong>- Using Agreements</strong></p><p><strong>- Customising the Tabs Shown within Agreement Setup</strong></p><p><br></p><p><strong>Admin Guides: </strong></p><ul><li><a href="https://usehalo.com/halopsa/guides/1843" target="_blank" rel="noopener noreferrer"><strong>Agreements (Contracts) </strong></a></li></ul><p><br></p><p data-pasted="true"><strong><em>Note: Throughout this guide and Halo the terms 'agreement' and 'contract' are used interchangeably. </em></strong></p><p><br></p><p>This guide covers contracts/agreement functionality when creating agreements between yourself and a client/customer. For information on creating agreements between your own organisations check out <a href="https://usehalo.com/haloitsm/guides/2539" target="_blank" rel="noopener noreferrer">Organisation Contracts/Agreements. </a></p><p><br></p><p>For information on supplier contract functionality check out <a href="https://usehalo.com/haloitsm/guides/2537" target="_blank" rel="noopener noreferrer">Supplier Agreements/Contracts. </a></p><p><br></p><p><strong><span style="font-size: 14pt;">What is an Agreement/Contract in Halo?<br></span></strong></p><p>Client agreements are used for the following purposes in Halo:</p><ul><li>To hold a record in Halo of the details of the contract you have with a client for reference purposes.</li><li>Automatically tracking the amount of labour hours associated with a contract a client has used.</li><li>Allowing time logged to be covered under the cost of an agreement, preventing it being billed. </li><li>Associating Invoices with a particular agreement.</li><li>Tracking the business value of a particular agreement. </li><li>Restricting which charge types an agent can use.</li><li>Overriding the rate at which work is billed at. </li></ul><p><br></p><p><br></p><p><strong><span style="font-size: 14pt;">Initial Agreement Setup</span></strong></p><p>To create a new agreement, head to the Agreements module (this may also be called Contracts). From here you can view existing and create new agreements (you can also create a new agreement under the "Agreements" tab of a customer. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjA3YzhkZWEyLWE3OWYtNDIyYi04MDM5LTdiMWJkZDRjZmIyOCJ9.yQFw_rONzIaU2633B2pAi2uZdrvXocRrLrP3MlC1pCA" class="fr-fic fr-fil fr-dib" width="2025" style="width: 2027px; height: 668.807px;" height="669"></p><p><strong><span style="font-size: 10pt;">Fig 1. Agreements Module</span></strong></p><p><br></p><p>When creating a new agreement you will need to complete some key fields.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImU2MGY4OGQ5LTBjNWMtNGZhNS05Mzk1LWI0ODZmOTVmOTlkZCJ9.s_SV6Jm326MCBvn8RdIBiS6Kja9B5Ji7F2uGQyeTTpA" class="fr-fic fr-fil fr-dib" width="2022" style="width: 2024px; height: 1035.17px;" height="1035"></p><p><strong><span style="font-size: 10pt;">Fig 2. New Agreement</span></strong></p><p><br></p><p>The Key Fields to consider on this screen are as follows:</p><p><strong>Customer -</strong> The customer the agreement is with. </p><p><strong>Agreement Type/Subtype -</strong> This is used to categorise your agreements for reporting and billing purposes. Agreement types and subtypes can be created and edited under Configuration > Agreements > Agreement Type/Subtype. More information on setting these up can be found under the "Creating Agreement Types and Subtypes" section of this guide. </p><p><strong>Agreement Reference - </strong>This should be the unique identifier of the agreement. This can be generated for you using the "Generate" button, this will generate the next reference in the series. For more on creating agreement references, please refer to this guide: <a href="https://usehalo.com/halopsa/guides/2852" target="_blank" rel="noopener noreferrer">Generating Agreement References</a>.</p><p><strong>Labour Type - </strong>This field controls how labour time logged against this agreement is tracked. Once saved this cannot be changed. Fields/options on the agreement will differ depending on the labour type chosen here. </p><ul><li>If a fixed number of hours are provided each period as part of this agreement and you would like to track the usage of these hours, set this to "Fixed". </li><li>If the client pays for a number of hours upfront and you would like to track their usage of these hours, set this to "Pre-Pay".</li><li>If this agreement is not being used to track labour hours (e.g. a licencing provisioning agreement) set this to "Fixed".</li></ul><p><strong>Start date -</strong> The date the agreement commenced.</p><p><strong>Labour Period -</strong> Used on fixed labour type agreements only. Choose the period in which the hours (of labour) included in the agreement covers, hours will re-fresh after each period. This does not impact how the agreement is billed. If the agreement is not being used to track labour any period can be chosen, usually the billing period. </p><p data-pasted="true"><strong>Hours per Period -</strong> Used on fixed labour type agreements only. Enter the number of hours, per period, the client is entitled to as part of this agreement. If the agreement is not being used to track labour or unlimited labour is provided as part of this agreement, check "unlimited" here. </p><p data-pasted="true"><strong>End date type - </strong>Used on fixed labour type agreements only. This controls how the end of the agreement is calculated. Whether the agreement lasts for a specified number of periods (based on the Labour Period chosen) ends on a fixed date, or has no end (rolling).</p><p><strong>Active - </strong>Controls if the agreement is active or not.<span style="color: rgb(235, 107, 86);"> </span><span style="color: rgb(0, 0, 0);">Only active agreements can be used in billing rules and linked to tickets. More information on managing the expiry of agreements can be found in the "Agreement Expiry" section of this guide. </span></p><p><br></p><p>Once saved, additional setup for the agreement will become available. </p><p><br></p><p>If the agreement you are creating is for pre paid labour (Labour Type = "Pre-Pay") then some additional setup is required. </p><p><br></p><p style="margin-left: 20px;"><strong><span style="font-size: 12pt;">Setup for Pre-Pay Agreements </span></strong></p><p style="margin-left: 20px;">Pre-pay can also be configured directly against a client under their 'Pre-Pay' tab. A pre-pay agreement will add pre-pay hours to this agreement, not to the pre-pay directly against the customer. Pre-pay agreements are preferable to configuring pre-pay directly against a customer when a client has multiple pre-pay 'pots' or when you would like to track this in the context of a contract. For information on setting up pre-pay hours directly against a client checkout our guide <a href="https://usehalo.com/halopsa/guides/1955/" target="_blank" rel="noopener noreferrer">here</a>. </p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;">Additional setup for pre-pay agreements is completed under the "Pre-pay" tab. </p><p style="margin-left: 20px;"><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjVhZjkyZjJhLWI2ZjQtNGUzYy04Y2MxLTU3ZmJmODU0YjM2MyJ9.IwfUNA-CK9wJR7oN-D4jLf1XPXflRCsmfhGeb1bAdEg" class="fr-fic fr-fil fr-dib" width="1770" style="width: 1772px; height: 915.376px;" height="915"></p><p style="margin-left: 20px;"><strong><span style="font-size: 10pt;">Fig 3. Pre-pay tab within an agreement</span></strong></p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;">Here, you will need to configure when and how prepay hours within this agreement are topped up and invoiced. </p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;"><strong>Pre-Pay Balance</strong></p><p style="margin-left: 20px;">This section shows the total pre-pay hours purchased by the client (the total of all pre-pay records), the amount of those hours used and the amount remaining (balance). The balance reflects the hours the client has available to use. </p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;"><strong>Billing</strong></p><p style="margin-left: 20px;">In this section you can configure how pre-pay hours are billed. </p><p style="margin-left: 20px;"><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjE1NzUwOGFkLTI0ODQtNGQ4YS04YTA5LTIzNzk0NDFiMTE2YSJ9.a09xLaRD3epcGTN0TEC8EaCoaFp9HrjvIvIpMPGiMgI" class="fr-fic fr-fil fr-dib" width="1385" style="width: 1387px; height: 238.917px;" height="239"></p><p style="margin-left: 20px;"><strong><span style="font-size: 10pt;">Fig 4. Options to control how Pre-Pay hours are billed</span></strong></p><p style="margin-left: 20px;"><br></p><p data-pasted="true" style="margin-left: 20px;"><strong>Linked Item -</strong> This is the product that will be used to represent the pre-pay record on invoices. Important when syncing invoices to your accounting tool. </p><p style="margin-left: 20px;"><strong>Set Recurring and Auto Pre-pay as already invoiced -</strong> Controls whether invoices are generated for auto-top up. Enable this when you want hours to be topped up automatically, but do not need/want invoices for these hours to be generated automatically. Disable this when you would like to invoice for these top ups from Halo. This option is enabled by default, so if you would like to invoice for these pre-pay top ups from Halo ensure you disable this. </p><p style="margin-left: 20px;"><strong>Use Amount for Pre Pay instead of Time -</strong> Enable this when you would like to track the labour used as part of this agreement using the value of the time, rather than the hours. Used when the client does not purchase a set amount of hours but rather provides a retainer of a set value. Useful when different types of work can be covered as part of this agreement, but different work has a different hourly rate. </p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;"><strong>Recurring Pre-Pay</strong></p><p style="margin-left: 20px;">In this section you can configure pre-pay hours/amounts to automatically top up on a scheduled basis. This will automatically change (top up) the<span style="color: rgb(0, 0, 0);"> pre-pay balance and total </span>for the agreement. This can also automatically generate invoices for the top-up amount, allowing you to easily invoice the client for the top up. </p><p style="margin-left: 20px;"><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjdlNjQwMDg5LTg5Y2MtNDQxMC1hMDEyLTEzOTBjNzQ2N2ZlNyJ9.5SoYlkTyuCI5lVNPyUSiOXEcV49fEEsmi3z-r3sKZdM" class="fr-fic fr-fil fr-dib" width="1352" style="width: 1354px; height: 529.69px;" height="530"></p><p style="margin-left: 20px;"><strong><span style="font-size: 10pt;">Fig 5. Recurring Pre-pay section</span></strong></p><p style="margin-left: 20px;"><br></p><p data-pasted="true" style="margin-left: 20px;"><strong>Date of next payment - </strong>Enter the date in which pre-pay should next be topped up. </p><p data-pasted="true" style="margin-left: 20px;"><strong>Expiry of Pre-Pay in Months from payment -</strong> Enter how many months this pre-pay is able to be used for before it expires. Once expired, hours will be removed from the agreement's pre-pay <span style="color: rgb(0, 0, 0);">balance</span>. </p><p style="margin-left: 20px;"><strong>Amount -</strong> Enter the amount (in your default currency) you would like to charge the client for this top up. </p><p style="margin-left: 20px;"><strong>Hours -</strong> Enter the number of hours to top up by each time. Not applicable if using amount for pre-pay instead of time.</p><p style="margin-left: 20px;"><strong>Recurring Period - </strong>Choose the interval in which pre-pay should automatically be topped up. For example, if "Monthly" is chosen, pre-pay hours/amount will be topped up by this amount every month. </p><p data-pasted="true" style="margin-left: 20px;"><strong>Minimum Deduction -</strong> Enter the minimum amount of hours that must be used/deducted from the agreement each period here. If the hours consumed in the period do not meet the value set here, then the difference between the consumed hours & minimum deduction value will be deducted. Useful when hours have a long expiry as this prevents too many hours being rolled over into the next period.</p><p data-pasted="true" style="margin-left: 20px;"><strong>Automatic Deduction -</strong> Enter the number of hours you would like to be deducted from the agreement automatically each period. This amount/hours will be deducted irrespective of the pre-pay time consumed in the period. Useful when a level of background maintenance is provided as part of the agreement each period, and you would like the value of this to be accounted for. </p><p data-pasted="true" style="margin-left: 20px;"><strong>Process deduction only when account is active -</strong> When the account status of the client is set to "Stopped" the deduction of pre-pay will not be in effect. Enable this if you would not like deductions to occur when the client account is not active/on hold. </p><p style="margin-left: 20px;"><br></p><p data-pasted="true" style="margin-left: 20px;"><strong>Pre-Pay Auto Top Up</strong></p><p style="margin-left: 20px;">In this section you can configure pre-pay hours to automatically be topped up by a set amount/hours each time the current pre-pay balance drops below a threshold. This can also automatically generate invoices for the top-up amount, allowing you to easily invoice the client for the top up. </p><p style="margin-left: 20px;"><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImRhNjVlNWU4LWU0MjgtNGFhOS1hMmVlLWZjMjk3ZTRlOWZkNSJ9.kRuvgEZoogDviOXl2EZ56_xtVqyRnrFTNBBdLoCVITA" class="fr-fic fr-fil fr-dib" width="1426" style="width: 1428px; height: 303.035px;" height="303"></p><p style="margin-left: 20px;"><strong><span style="font-size: 10pt;">Fig 6. Pre-pay Auto Top Up</span></strong></p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;"><strong>Threshold -</strong> Set the amount/hours the pre-pay balance on the contract must fall below for automatic top up to take place. </p><p data-pasted="true" style="margin-left: 20px;"><strong>Top up by this amount of hours - </strong>Choose the amount of hours to top up the agreement with when it drops below the threshold. The client will be invoiced for this amount of hours in line with the "Cost per hour" set provided "Set Recurring and Auto Pre-pay as already invoiced" is disabled. Only available when using pre-pay hours and not amount. </p><p style="margin-left: 20px;"><strong>Top up to this amount of hours -</strong> Choose the amount of hours the agreement's pre-pay balance should be topped up to when it drops below the threshold. Used when you would like to ensure the agreement always has at least this amount of hours. The client will be invoiced for the amount of hours required to bring their balance up to this (provided "Set Recurring and Auto Pre-pay as already invoiced" is disabled). Only available when using pre-pay hours and not amount. </p><p style="margin-left: 20px;"><strong>Cost per hour -</strong> Choose the hourly rate to invoice auto-top up hours at. When prepay hours are auto topped up, the specified amount of hours will be invoiced at this rate. Using the Figure 6 example, the client will be invoiced for 3 hours at a rate of £60 per hour bringing the total to £180. Only available when using pre-pay hours and not amount. </p><p style="margin-left: 20px;"><strong>Amount to add -</strong> Choose the amount to top up the agreement with when it drops below the threshold. The client will be invoiced for this amount when the agreement <span style="color: rgb(0, 0, 0);">balance </span>drops below the threshold. Only available when using amount for pre-pay instead of time. </p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;"><strong>Pre-Pay Records</strong></p><p style="margin-left: 20px;">This section holds a record for each instance of pre pay hours/amount being added to/removed from the agreement. This can also be used to manually add/remove pre pay hours/amount to the agreement, useful when adding/removing hours on an ad hoc basis. </p><p style="margin-left: 20px;"><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImYyOTM4M2NiLWQ4ZGMtNGI3Ni05ODcxLWQ4MDM5MmY4ZTVmNiJ9.sQhOvLm9JOAj4Lclm_7EE-i04exNMbC6rX5a0aQ-UrY" class="fr-fic fr-fil fr-dib" width="1406" style="width: 1408px; height: 286.166px;" height="286"></p><p style="margin-left: 20px;"><strong><span style="font-size: 10pt;">Fig 7. Pre-pay records section</span></strong></p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;">To manually add a pre-pay record use the "Add" button and complete the details shown on the pop up.</p><p style="margin-left: 20px;"><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImRiZTJkYzc5LWMwODMtNGNmYy05MmJlLTZiOGE3NGNlNzZhMSJ9.Yg4diY0wegN75dw0NXThGOr1EqhO3Diu7uyIiBq6Trc" class="fr-fic fr-fil fr-dib" width="540" style="width: 542px; height: 714.039px;" height="714"></p><p style="margin-left: 20px;"><strong><span style="font-size: 10pt;">Fig 8. New pre-pay record</span></strong></p><p style="margin-left: 20px;"><br></p><p data-pasted="true" style="margin-left: 20px;"><strong>Pre-Pay Hours - </strong>Choose the number of hours to add. Negative numbers can be used to remove hours. </p><p style="margin-left: 20px;"><strong>Amount - </strong>Choose the amount this record is worth, this will be the amount the client is invoiced for.</p><p style="margin-left: 20px;"><strong>Date -</strong> Choose the date these hours should be added on. They will only be available to use after this date. </p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;">If you have not yet invoiced for these hours/amount leave the following fields blank. Halo will generate an invoice for you for this record, once you have create the invoice, the invoice details will be linked to this pre-pay record. </p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;"><strong>Invoiced Date -</strong> If the hours being added here have already been invoiced, enter the date they were invoiced. When this is populated Halo will not generate an invoice for these hours for you.</p><p data-pasted="true" style="margin-left: 20px;"><strong>Related invoice line - </strong>If the hours being added here have already been invoiced (and the invoice is present in Halo) choose the invoice line to link this pre-pay record to. You will be able to choose from all invoice lines for this client. </p><p style="margin-left: 20px;"><strong>Invoice number -</strong> If the hours being added here have already been invoiced enter the number of the invoice the hours were invoiced on here. </p><p data-pasted="true" style="margin-left: 20px;"><strong>Expiry Date -</strong> Choose the date these hours should expire after. These hours will not be able to be used after this date. </p><p style="margin-left: 20px;"><br></p><p><strong><span style="font-size: 14pt;">Set when Labour (actions) is covered by or associated with an Agreement</span></strong></p><p data-pasted="true">Associating time logged with an agreement allows you to track how much time a client has used as part of this agreement. If the agreement covers the costs of certain labour, the action/ticket logged will need to be associated with the agreement in order for the time to be deducted from the agreement hours, rather than being billed for. </p><p><br></p><p>There are two ways to associate time with an agreement:</p><ul><li>Use billing rules to associate each action that meets set criteria.</li><li>Use a ticket field to associate all actions on a ticket with a chosen agreement.</li></ul><p><br></p><p>Where possible, it is preferable to use billing rules to associate actions with an agreement as this automates the billing process and allows for more flexibility around which actions are/not covered by an agreement. </p><p><br></p><p data-pasted="true">Associating a ticket with an agreement is only used when:</p><ul><li>You would like agents to be able to choose which tickets are covered by an agreement (association does not follow set criteria).</li><li>You would like to restrict the charge types agents can use on the ticket based on the associated agreement.</li></ul><p><br></p><p data-pasted="true"><span style="color: rgb(235, 107, 86);"><strong>Important: If a ticket is associated with an agreement all actions on the ticket will be associated with the agreement, overriding any billing rules. So these methods cannot be used in conjunction with one another. </strong></span></p><p><br></p><p><strong><span style="font-size: 12pt;">Creating Billing Rules to Associate Actions to an Agreement</span></strong></p><p>Under the Charge Types tab of the agreement you can configure 'Billing Rules' for the agreement. Agreement billing rules are used to automate when each action logged on tickets for this client are associated with the agreement</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjliMTBjZDM2LTRjYzAtNDNhZC1hNjdkLTA0NDljMWQyNGRhNSJ9._Kt61WGONkexotzJ1KePdj8Dyxbftj-Tu0WB5IkwfOg" class="fr-fic fr-fil fr-dib" width="1648" style="width: 1650px; height: 600.758px;" height="601"></p><p><strong><span style="font-size: 10pt;">Fig 9. Agreement Billing Rules </span></strong></p><p><br></p><p>Any action that meets the criteria of a rule added here will come under the agreement. Adding rules here will automatically create billing rules for the customer, using this agreement as the billing plan. Additionally any billing rules against the customer that use this agreement, will be visible against the agreement here. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjA4NDg4YzYxLTlkY2YtNDY4YS1hMTY4LWE1MTk0MTBlY2JhNCJ9.186sZ4zQKSE22Tllv9j_pUISSABEZqb0E0xkBB53L5I" class="fr-fic fr-fil fr-dib" width="1649" style="width: 1651px; height: 961.513px;" height="962"></p><p><strong><span style="font-size: 10pt;">Fig 10. Agreement Billing Rules against customer </span></strong></p><p><br></p><p><strong><em>Note: You don't have to set rules here, you can set them against the customer. Although it can be simpler to configure all agreement related rules against the agreement setting them directly against the customer is often easier as this gives you better visibility of the overall billing plan for the customer when creating the rules.</em></strong></p><p><br></p><p>For more information on how to setup/use billing rules checkout our guide <a href="https://usehalo.com/halopsa/guides/1957/" target="_blank" rel="noopener noreferrer">here</a>. </p><p><br></p><p><strong><span style="font-size: 11pt;">Check if an Action is associated with an Agreement</span></strong></p><p>After an action is logged, you can see how it is due to be billed, shown in Figure 11.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjI1NmJjMzE1LWYwZTYtNDZlYi04MWU0LTJjYTEyOTk4YmNkMyJ9.qAGmjAJlkx40-Wk7wv__1IiKEiw7l_KAmcIamq9P8Sw" class="fr-fic fr-fil fr-dib" width="1571" style="width: 1573px; height: 336.005px;" height="336"></p><p><strong><span style="font-size: 10pt;">Fig 11. Billing Plan used for action</span></strong></p><p><br></p><p>If "Contract Hours" is stated here, this means this time will be deducted from the agreement associated with the action and therefore the action will not be invoiced. </p><p><br></p><p>You can check to see which agreement is associated by editing the action and viewing the "Agreement" field under the Time Tracking tab. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjZkYWJhYWU4LTlkZjAtNDE2YS1hY2ZlLWJkYmMwOWJmYTE4MSJ9.SNcIRsCT6wt_SfWRrfgGm5_onk6UHKXQ4BMr2GfcMRQ" class="fr-fic fr-fil fr-dib" width="726" style="width: 728px; height: 606.805px;" height="607"></p><p><strong><span style="font-size: 10pt;">Fig 12. Agreement Associated with Action</span></strong></p><p><br></p><p><span style="color: rgb(0, 0, 0);">If agreement hours have run out (or none are included in the agreement), actions may still be associated with an agreement, but the billing plan on the action will show if/how the time is going to be billed rather than showing it will be covered by the agreement. </span></p><p><span style="color: rgb(0, 0, 0);"><br></span></p><p><span style="color: rgb(0, 0, 0);"><strong><span style="font-size: 12pt;">Associating a Ticket with an Agreement</span></strong></span></p><p>To associate a ticket with an agreement you will need to add the "Agreement" field to the field list of your ticket types.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImU3Y2YxODMwLTVkZDYtNGUwNC1hZmM1LTQxY2Y1NWMwYTljYSJ9.SRgEA2ZbuKaYbd2a70-bEZp58IQQLxg2ZM-V1Y0yYHc" class="fr-fic fr-fil fr-dib" width="1585" style="width: 1587px; height: 452.967px;" height="453"></p><p><strong><span style="font-size: 10pt;">Fig 13. Agreement Field on Ticket Type</span></strong></p><p><br></p><p>Now, when a ticket of this type is logged agents will see this field and be able to set the agreement associated with this particular ticket. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijc2OGVmZGNhLWU5OTctNDY0OC04NzgyLTYwOTlkZmY4MjVhZCJ9.zMxK4hY_YVFwUmQmWE8SQKMOqyZvGFE545JqYJRho4o" class="fr-fic fr-fil fr-dib" width="1890" style="width: 1892px; height: 787.759px;" height="788"></p><p><strong><span style="font-size: 10pt;">Fig 14. Agreement Field on Ticket</span></strong></p><p><br></p><p>You can also add this field to an action's field list if you would like agents to populate this field using a particular action e.g. when triaging the ticket. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImEzOTAyNDhjLTVjMWUtNGY2NS05YTc2LTM2NGFhZGM0YmI0MyJ9.WSDP5nM8Z_INqubuVsm0XDVlBYx3Uny8lM89_u39xec" class="fr-fic fr-fil fr-dib" width="1428" style="width: 1430px; height: 508.344px;" height="508"></p><p><strong><span style="font-size: 10pt;">Fig 15. Set Agreement using an action</span></strong></p><p><br></p><p>When the "Agreement" field is set using an action, this will set the "Agreement" field for the whole ticket so this, and any future actions, will be associated with this agreement. </p><p><br></p><p><strong><em>Note: If this field is added to an action but not the ticket type, the ticket will still be associated with the agreement, the agreement associated will show in the ticket's details. </em></strong></p><p><br></p><p>Now, all actions on the ticket will be associated with the agreement chosen in this field. If the field is not set, billing rules will be used to determine how an action is billed/what agreement it is associated with. </p><p><br></p><p><strong><span style="font-size: 14pt;">Agreement Charge Types</span></strong></p><p>Under the Charge Types tab of the agreement you can configure agreement charge types. These are charge types that are specific to this agreement, so will only be used on tickets that are associated with this agreement (for<span style="color: rgb(0, 0, 0);"> information on how to associate a ticket with an agreement see sectio</span>n the "Associating a Ticket with an Agreement" of this guide). It is beneficial to create agreement specific charge types when you have a specific labour type and rate that is only offered as part of this agreement and not to any other clients/agreements. As this avoids cluttering up your global charge types with types that are only used in this contract specific context. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImZkZWM5ZDY4LTc0NWEtNDYwYi04MWYzLWIyZmY3NDczMTc5MCJ9.YRdVwoyIYFAW8P4l1aCpzHaJ2aNJtNvX3Dykv2yBy8o" class="fr-fic fr-fil fr-dib" width="1409" style="width: 1411px; height: 967.294px;" height="967"></p><p><strong><span style="font-size: 10pt;">Fig 16. Agreement Charge Types</span></strong></p><p><br></p><p><strong><em>Note: Keep in mind, if you have any charge type restrictions (for customers/agents) these restrictions will override rates added here. This means rates added here will need to be added into the clients/agents allowed charge types. </em></strong></p><p><br></p><p>Add a new charge type using the "Add" button in the highlighted area of Figure 16. For information on how to setup charge types checkout our dedicated guide <a href="https://usehalo.com/halopsa/guides/1954/" target="_blank" rel="noopener noreferrer">here</a>. </p><p><br></p><p data-pasted="true"><strong>Charge Type Nominal Code Override -</strong> The Accounts code chosen here will be used as the accounts code for all labour (regardless of charge type) logged against tickets associated with this agreement. Used when actions are logged against the agreement that need to be billed and you would like the revenue from this labour to be recorded under a different accounts code to the one set against the item linked to the charge type. </p><p data-pasted="true"><strong>Contract Charge Rate multiplier -</strong> Labour logged against tickets associated with the agreement will be multiplied by this. Excluding actions that use an agreement charge type or a charge type that has a overriding rate. </p><p><br></p><p><strong><span style="font-size: 12pt;">Set Which Rates can be used on Tickets linked to this Agreement </span></strong></p><p>You can also choose whether agents can only use these charge types or use this in addition to existing charge types on tickets linked to this agreement. This is done using the setting "Charge Types selection".</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjRmNjQwMDkyLWNlNjItNDI2Mi1iODliLTMzODg4NjUxN2FlYSJ9.9XblICWdMvd8kYyzZIW009ZhET1aFo4aSkJUctBHksw" class="fr-fic fr-fil fr-dib" width="1347" style="width: 1349px; height: 891.208px;" height="891"></p><p><strong><span style="font-size: 10pt;">Fig 17. Charge Types Selection</span></strong></p><p><br></p><p><strong>Charge Types selection -</strong> Determines which charge rates will be available to use on tickets linked to this agreement.</p><ul><li><strong>Agreement Charge Types and all Global Charge Types -</strong> Allows agents to use all existing charge types <span style="color: rgb(0, 0, 0);">(in line with customer/agent restrictions) </span>as well as any charge types configured here, on tickets linked to this agreement. </li><li><strong>Agreement CT and Global Charge Types with an override -</strong> On tickets linked to this agreement, agents will only be able to use the agreement specific charge types (configured here) and any existing charge types that have a rate override for the agreement (charge rate overrides are covered in the next section of this guide). </li></ul><p><br></p><p><strong><span style="font-size: 14pt;">Override the Charge Rates for Labour (actions) covered by the Agreement </span></strong></p><p>If you have agreed work to be billed at a non-standard rate as part of this agreement, you can set up overriding charge types for the agreement. This allows you to override the rate that labour is billed at for actions covered by the agreement. </p><p><br></p><p>Overriding rates are set per charge type, so agents can log actions using existing charge rates, but the time will be billed at the rate set against the agreement. Allowing you to have a simplified list of charge types, but various rates.</p><p><br></p><p>Overriding charge Types are set up under the Overriding Charge types section of the Charge Types tab in the agreement. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjFjNmYyOWVkLTAzYzAtNDdkNy05OWQ1LTMxM2FlYzE4OTcwOSJ9.ftioVCaMwjmK_w0DFn0Ic9OczhF5xk9gDCv-EsigEEw" class="fr-fic fr-fil fr-dib" style="width: 1372px;"></p><p><strong><span style="font-size: 10pt;">Fig 18. Overriding Charge Types</span></strong></p><p><br></p><p>To set a rate override add to the table shown in Figure 18, pick the charge type you would like to override the rate of, and then pick the rate to be used in the "Rate" field. For information on setting up charge rates and all the options available see our guide <a href="https://usehalo.com/halopsa/guides/1954" target="_blank" rel="noopener noreferrer">here</a>. </p><p><br></p><p><strong><em>Note: Other elements of the rate can be overridden here too, such as the multipliers used. </em></strong></p><p><br></p><p>In the Figure 18 example, actions that are covered by the agreement that also use the "Remote Support" charge type will be billed at a rate of £50 an hour as opposed to the standard £25 an hour. </p><p><br></p><p>This rate will apply to any actions that come under the agreement. This includes actions that are associated with the agreement via billing rules and actions that inherit agreement association as they are logged on a ticket that is linked to the agreement. </p><p><br></p><p>Keep in mind charge rate overrides can also be set up per customer, for more information on charge type overrides and how they interact checkout our guide <a href="https://usehalo.com/halopsa/guides/2181/" target="_blank" rel="noopener noreferrer">here</a>. </p><p><br></p><p><strong><span style="font-size: 14pt;">Link Assets and Users to the Agreement</span></strong></p><p>Assets and users can be linked to the agreement, useful for value tracking and determining which actions are covered by the agreement. </p><p><br></p><p><strong><span style="font-size: 12pt;">Adding Assets</span></strong></p><p>To link assets to the agreement head to the "Assets" tab within the agreement.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjZkZTYzNGExLTUzOTYtNDU3NS1iOWZkLWJlNjExYjcxMDUwYyJ9.yS8iIDG8Bn6S8-Co8Y9qbAffO3xR2IcL6OOFc__lR-s" class="fr-fic fr-fil fr-dib" width="1491" style="width: 1493px; height: 687.28px;" height="687"></p><p><strong><span style="font-size: 10pt;">Fig 19. Assets tab within Agreement</span></strong></p><p><br></p><p>When adding you will be able to choose from a list of assets in your instance, filters and search can be applied to the list to make selection easier. </p><p><br></p><p data-pasted="true">Assets can also be created from the contract, making it easy to add new managed devices into your system. When adding choose the asset type to create and how many assets to create. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjcyMDY3YTI2LWFlMGYtNGI4OS1hOGU3LTQwNjkxNDdhOThkOCJ9.HJqcfXSf3a-IS9vMkMDwdR1xwnOgODn8wzH9qsEzYC8" class="fr-fic fr-fil fr-dib" width="602" style="width: 604px; height: 283.838px;" height="284"></p><p><strong><span style="font-size: 10pt;">Fig 20. Creating 10 new Workstation assets from an agreement</span></strong></p><p><br></p><p>Once the agreement is saved these assets will be created and their "Asset Tag" and "Value" fields will populate.</p><p> </p><p><strong>Tracking Agreement Value through Assets</strong></p><p>Once assets are added to an agreement the "Value" of each asset can then be set by editing the asset. The value of all assets under the agreement will be totalled to give the total agreement value. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjIxYTcwMmExLWE4NzMtNDdmZS1hYTg0LTZhOTJlNDNhYjFkNCJ9.RKvdH-zS1EXnl6hmIK1f0fjTX4PputlSp8iLI2dWeSE" class="fr-fic fr-fil fr-dib" width="1314" style="width: 1316px; height: 723.247px;" height="723"></p><p><strong><span style="font-size: 10pt;">Fig 21. Total Agreement Value</span></strong></p><p><br></p><p>This can be reported on to help track the business value of the agreement. </p><p><br></p><p><strong>Only cover labour under the agreement if the Asset is covered</strong></p><p>Adding all assets covered by the agreement also allows you to restrict the labour that is covered by the agreement so only labour associated with one of the covered assets is included. </p><p><br></p><p>To do this, when setting billing rules for the agreement, check "Asset must be covered by the Agreement".</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjMxZmQ2MThiLTc5ZDQtNGY3Ni1iYzIwLTgwMjE3NWZlMjZiNCJ9.MsLXXHhDy85f4bQvEmXRr1fy7lxzyv9WKs0KagSVzSY" class="fr-fic fr-fil fr-dib" width="506" style="width: 508px; height: 843.109px;" height="843"></p><p><strong><span style="font-size: 10pt;">Fig 22. Billing rule to only cover action under agreement if the asset is covered by the agreement</span></strong></p><p><br></p><p>Now, actions will only be covered by the agreement if they are logged on tickets that have one of the covered assets as a related asset (as well as meeting the other conditions in the billing rule). </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjJjYWU5MDVmLTU5NjgtNDhiOS05NmU5LTkwZTE3YzM3YmI4OSJ9.q2L8SfrCwe8PhebnTbBqe83Tmm_Fuq0_A1g9-JE2vl0" class="fr-fic fr-fil fr-dib" width="1769" style="width: 1771px; height: 965.701px;" height="966"></p><p><strong><span style="font-size: 10pt;">Fig 23. Ticket with related asset covered by agreement</span></strong></p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImYwNDMwZTgzLThkNDYtNGRmNC1hNGZkLWJiNTJiMmYwMjVhMyJ9.O0rStE20IXIdMsOoS12iBj4pEGgYhlHxOpJCsHc4aL0" class="fr-fic fr-fil fr-dib" width="1770" style="width: 1772px; height: 965.724px;" height="966"></p><p><strong><span style="font-size: 10pt;">Fig 24. Ticket with related asset not covered by agreement</span></strong></p><p><br></p><p><strong><span style="font-size: 12pt;">Add Users</span></strong></p><p data-pasted="true">To link assets to the agreement head to the "Users" tab within the agreement.</p><p><br></p><p data-pasted="true">When adding you will be able to choose from a list of users in your instance, filters and search can be applied to the list to make selection easier. After selecting the users to add you will be prompted to enter the value each user brings to the agreement and the date they should no longer be covered by the agreement (End Date). </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjE2N2E2MTc5LWI4YjAtNGVlMy05M2YzLTc3NDA5NDFjOTY5YSJ9.pugMm6DBazp9WJmNgVfuAuwC_OlXJeoyGSsdXo6Ma4M" class="fr-fic fr-fil fr-dib" style="width: 615px; height: 315.23px;" width="613" height="315"></p><p><strong><span style="font-size: 10pt;">Fig 25. Add users to agreement</span></strong></p><p><br></p><p>Once added you will see all users that are covered as well as the total value they bring to the agreement. The end date/value of a specific user can be changed by editing the user after adding. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjM1OGIwNDAzLTc5OTYtNDljMC05M2M4LTkwOGFkYjIyZDA5YSJ9.TO4IqhhhMY_rGr0G5FYy_iSkKJRkJy_mckfFfaTwQOg" class="fr-fic fr-fil fr-dib" width="1529" style="width: 1531px; height: 470.347px;" height="470"></p><p><strong><span style="font-size: 10pt;">Fig 26. Users Covered by contract and their total value</span></strong></p><p><br></p><p data-pasted="true">This can be reported on to help track the business value of the agreement. </p><p data-pasted="true"><br></p><p><strong>Only cover labour under the agreement if the User is covered</strong></p><p>Adding all users covered by the agreement also allows you to restrict the labour that is covered by the agreement to labour logged on tickets for these users only </p><p><br></p><p>To do this when setting billing rules for the agreement check "User must be covered by the Agreement".</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjNlY2I1MDg0LTA0NGYtNDQ4NS1iNzlmLTc0YWI5ZjlmZTk0ZSJ9.I1XAxSyjUk_Ly8vw7Kxw0WmNjjzFiL-GpJ3gLua_kMA" class="fr-fic fr-fil fr-dib" width="506" style="width: 508px; height: 845.949px;" height="846"></p><p data-pasted="true"><strong><span style="font-size: 10pt;">Fig 27. Billing rule to only cover action under agreement if the end user of the ticket is covered by the agreement</span></strong></p><p><br></p><p data-pasted="true">Now, actions will only be covered by the agreement if they are logged on tickets that have one of the covered users as the end user (as well as meeting the other conditions in the billing rule). </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImI3MjAzMTIxLTY3MzUtNDQwYi05YTY5LWE5MDZlNTAwODJhYyJ9.DmjyVcwVNiIQ0nbOf5nbbbCvGO7C4xos3BIn0ise7O4" class="fr-fic fr-fil fr-dib" width="1932" style="width: 1934px; height: 663.421px;" height="663"></p><p data-pasted="true"><strong><span style="font-size: 10pt;">Fig 28. Ticket with end user covered by agreement</span></strong></p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImRmZjRiYjAyLTc1OWMtNGZjMi1iZjg5LTE4MTY0NjdmNGYzMiJ9.xeHMIOhouYkomXxG4R2j4_iInE-ZYIoBBcSV7pw_yW4" class="fr-fic fr-fil fr-dib" width="1931" style="width: 1933px; height: 661.331px;" height="661"></p><p data-pasted="true"><strong><span style="font-size: 10pt;">Fig 29. Ticket with related end user not covered by agreement</span></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Creating a Recurring Invoice for the Agreement</span></strong></p><p>If the agreement is billed on a recurring basis a recurring invoice will need to be setup to bill for this. To make setup easier the recurring invoice can be created from the "Recurring Invoices" tab within the agreement. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjI2MWIyNjcyLThkZTctNDc5OS05ZjYwLTU1NDEyNDU4MWZjZSJ9.qFt8-UOUpe4LKVAzgzAX3581-bJqOyooy_PR4Mvjd98" class="fr-fic fr-fil fr-dib" width="1492" style="width: 1494px; height: 599.434px;" height="599"></p><p><strong><span style="font-size: 10pt;">Fig 30. Create New Recurring Invoice</span></strong></p><p><br></p><p>Recurring invoices created from here will be automatically linked to this agreement. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjI2YWRiY2JkLTRkOWEtNDgxYi1iYWU4LTMxYmY2NTcwYzg1YiJ9.hG9wrvpUcLXIm7mdXGs8CGBlxf42_9mdFJE6xjFEfJc" class="fr-fic fr-fil fr-dib" width="1691" style="width: 1693px; height: 966.199px;" height="966"></p><p><strong><span style="font-size: 10pt;">Fig 31. Recurring Invoice linked to agreement</span></strong></p><p><br></p><p>The setup for the recurring invoice is the same as when setting up Recurring invoices elsewhere in Halo. For information on how to set up a recurring invoice checkout our guide <a href="https://usehalo.com/halopsa/guides/1975" target="_blank" rel="noopener noreferrer">here</a>. </p><p><br></p><p>Quantities of recurring invoice lines can be automated based on the counts of various entities in Halo (such as licence and user count). In order to automate quantities based on the asset or user count against the agreement, you will need to use a <a href="https://usehalo.com/halopsa/guides/2241" target="_blank" rel="noopener noreferrer">custom SQL quantity</a>. </p><p><br></p><p><strong><span style="font-size: 14pt;">Creating Agreement Types and Subtypes </span></strong></p><p>Agreement Types and Subtypes are used to categorise an agreement, useful for tracking the profit/revenue of agreements. They also tie into billing rules, allowing you to cover work under an agreement if the user is under an agreement of a specified type. </p><p><br></p><p>Some agreement types and subtypes are available out of the box, but these can be created under Configuration > Agreements > Agreement Type/Agreement Subtype.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijg5YjAwYzVjLWIxZjYtNDViMy04ZmY4LTRiNTU0ZDA1MzE5NSJ9.5LZ0gEj7kJkYTDlz8lPEtDSXccnFllq_EvNb0Q3jX6Y" class="fr-fic fr-fil fr-dib" width="816" style="width: 818px; height: 526.339px;" height="526"></p><p><strong><span style="font-size: 10pt;">Fig 32. Agreement Types and Subtypes</span></strong></p><p><br></p><p>When creating a new agreement type you can set various overrides for the agreement based on this type. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImI1NzI4NzRjLTQyNGEtNGE1Yi04NGM5LWQ5NDI1ODA2MDVjMyJ9.-ON7vcc4oklukrGYuyyVCYPclUwbGgTqdzJqPmCI0hg" class="fr-fic fr-fil fr-dib" width="1856" style="width: 1858px; height: 539.977px;" height="540"></p><p><strong><span style="font-size: 10pt;">Fig 33. New Agreement Type</span></strong></p><p><br></p><p><strong>Prefix -</strong> When generating references for agreements of this type, this string will be used as the prefix for the agreement reference. </p><p><strong>The Agreement with this description will be the default for the Customer -</strong> When checked, & "Auto select the Contract on a Ticket based on billing description" in Configuration>Contracts is also selected, if a Ticket is logged for a client with an active agreement of this type, then the agreement will be automatically added to the ticket.</p><p><strong>Email Template -</strong> Determines the email template used when sending out agreements of this type.</p><p><strong>SLA Override -</strong> Here you can choose the default SLA an agreement will have when creating an Agreement of this type. </p><p><br></p><p><strong><span style="font-size: 14pt;">Agreement Expiry</span></strong></p><p>The expiry of agreements can be tracked in Halo, allowing you to notify agents when an agreement is coming up for expiry so you can carry out any of the necessary expiry/renewal steps. </p><p><br></p><p data-pasted="true">When creating a Agreement the "End Date" field is used to denote when the contracted period ends, at which point the agreement can be terminated or renewed. </p><p><br></p><p data-pasted="true">Automated tickets can be used to have a ticket created automatically when an agreement is nearing its end date. To do this head to Configuration > Tickets > Automated Tickets > New. Give the automated ticket a name and set the "Automation Criteria" to be "Agreements". </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijg1NGE4ZjNjLTI1NTAtNGMwNC05ZDI0LTViNWY5MDkzM2NlYSJ9.h8U0L2aw5zO0DDEf7J7QTXI-dRICYqWR2VtOZ97vVQg" class="fr-fic fr-fil fr-dib" width="1660" style="width: 1662px; height: 805.378px;" height="805"></p><p><strong><span style="font-size: 10pt;">Fig 34. New automate ticket for agreement expiry</span></strong></p><p><br></p><p data-pasted="true">Then, in the "Criteria" table add criteria based on the "Days Before Agreement End Date". This will determine how many days before the agreement end date a ticket will be created. In the below example a ticket will be created 14 days before an agreement is due to expire. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjBlZWM1ZDgwLWU2OTYtNDQ3Ni1iMTlmLTU1ZGRkYjhhZmNjZCJ9.mmEI111SLUK-Z6Sr1OX-eX10hE0TunFcWiwIKwbLo-k" class="fr-fic fr-fil fr-dib" width="1691" style="width: 1693px; height: 270.975px;" height="271"></p><p><strong><span style="font-size: 10pt;">Fig 36. Criteria for automated ticket creation</span></strong></p><p><br></p><p><strong><em>Note: In the above example a ticket will be made for each agreement that has less than or equal to 14 days until the agreement end date, however you can add additional criteria here to restrict which agreements have tickets created. For example, you could restrict this to only specified agreement types.</em></strong></p><p><br></p><p data-pasted="true">Then, configure the rest of the automated ticket as usual, such as setting the user who should be assigned the ticket and the ticket type that should be logged. </p><p><br></p><p data-pasted="true">Variables can be included in the automated ticket values to have ticket fields populate with information about the specific agreement it was created for. In the Figure 37 example the variable $-CONTRACTREF has been added to have the agreement reference included in the summary of the ticket. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjZjZGViMWExLTJiMzAtNDBkNy05OTJiLTg3YzA2NTUzNjA1MyJ9.oru2aPL5yq8hMsEbNi9HwFfkC8eAoDOtdFo7UwsPtXM" class="fr-fic fr-fil fr-dib" width="867" style="width: 869px; height: 529.285px;" height="529"></p><p><strong><span style="font-size: 10pt;">Fig 37. Variables used for Automated Ticket Summary</span></strong></p><p><br></p><p data-pasted="true">If you would like the agreement to automatically be made inactive as soon as the automated ticket is logged (usually if this is logged on or after the end date) you can enable "Make the associated entity inactive after the Ticket is created" against the automated ticket. </p><p><br></p><p>Now, when an agreement meets the criteria outlined in the automated ticket, a ticket will automatically be created. A link to the agreement the ticket was created for will be added to the ticket automatically. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQxNmQyZTgxLTE1OTktNDA1OS04Y2M1LWUzYjAzMzM3NWJhMyJ9.HEyL_lYFkz74bG11pLQhNC5WKiYTPPcAU9QKV436_ps" class="fr-fic fr-fil fr-dib" width="1800" style="width: 1802px; height: 656.979px;" height="657"></p><p><strong><span style="font-size: 10pt;">Fig 38. Automated Ticket created for Agreement Expiry </span></strong></p><p><br></p><p><strong><span style="font-size: 12pt;">Automatically Change the status of an Agreement when it is Expired</span></strong></p><p>If you would like the status of agreements to change after their end date passes head to Configuration > Agreements and set "Agreement Status to use for Automatic Expiry". </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjJkZTdhODM1LWQ1ZmQtNDU5Yy1hZDhmLTE4ZWZhZWZlMDNjMiJ9.T1guTzm7AtcE2FVGLYErFRK68jy9fqkUtvQt9Chk2Do" class="fr-fic fr-fil fr-dib" width="855" style="width: 857px; height: 364.411px;" height="364"></p><p><strong><span style="font-size: 10pt;">Fig 39. Agreement Status to use for Automatic Expiry</span></strong></p><p><br></p><p>If set, agreements will be given this status automatically when their end date passes. </p><p><br></p><p>If you would also like the agreement to be made inactive, ensure the status chosen here is set to make the agreement inactive. This is done against the status configuration under Configuration > Agreements > Contract Statuses > select the status > "Make Contracts with this status inactive".</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjljYWFhZTBjLTAzMDEtNGEwYS1iN2IyLWIxNjhhNTUxMjNkMSJ9.EM09rIrSWfm1ZD5CXyUePwlnR3cKGhY06N5-Snvmdds" class="fr-fic fr-fil fr-dib" width="1002" style="width: 1004px; height: 384.8px;" height="385"></p><p><strong><span style="font-size: 10pt;">Fig 40. Set status to make agreements inactive </span></strong></p><p><br></p><p>Inactive agreements cannot be associated to actions, so any billing rules using an inactive agreement will be ignored. This allows you to prevent time being logged under an agreement that is no longer valid. </p><p><br></p><p data-pasted="true"><strong><span style="font-size: 14pt;">Using Agreements</span></strong></p><p>Once your agreement is setup you can review the agreement activity from within the agreement itself. This includes time logged against this agreement and invoices generated for this agreement. </p><p><br></p><p><strong><span style="font-size: 12pt;">View Time (Actions) Logged against this Agreement - Periodic History</span></strong></p><p>The Periodic History tab within the agreement can be used to view each of the actions logged against/covered by this agreement. Useful for tracking agreement usage. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijg4MjA3YzBmLTQ5YjQtNDIxZi04MDlkLTg0ODhlYjU5MDAxNSJ9.Et3zlPh9iqsDZ3cx77hqMIg9qAh7w3MLqllV-6KT_l0" width="1815" style="width: 1817px; height: 669.157px;" height="669" class="fr-fic fr-dii"></p><p><strong><span style="font-size: 10pt;">Fig 41. Periodic history of agreement</span></strong></p><p><br></p><p>Here we can see an overview of the amount of units (hours or monetary value) used per period. The columns shown here reflect units as follows:</p><ul><li><strong>Units on Contract -</strong> The amount of units available at the start of the period. Fixed agreements will always have the same number of hours available at the start of the period. Pre-pay agreements will have varied amount of units available depending on when unit expire. </li><li><strong>Units Used -</strong> The amount of units used in this period that are included in the cost of the agreement,</li><li><strong>Units Remaining -</strong> The amount of units left at the end of this period.</li><li><strong>Units Chargeable -</strong> The amount of units that were billed for on top of the agreement cost. If a client uses up all hours included in the agreement further work that would usually be included in the agreement will be billed on a pay as you go basis. This column reflects the number of units that were billed on this basis. </li><li><strong>Units Total -</strong> The total amount of units associated with the agreement. This is the total of "Units Used" + "Units Chargeable". </li></ul><p><br></p><p data-pasted="true"><strong><em>Note: It is not possible to change the period length, this will always be displayed in months based on the start date of the agreement. </em></strong></p><p><br></p><p>Clicking into a period will allow you to see all tickets that contain actions included with/ associated with this agreement. From here the ticket can be opened to view it further. Useful in investigating anomalies in the periodic history. </p><p><br></p><p><strong><span style="font-size: 12pt;">View the invoices created for an Agreement</span></strong></p><p>Any invoice linked to the agreement will show under the "Invoices" tab of the agreement. Invoices can be opened up from here. Allowing you to easily review invoicing and payment history for the agreement. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjY3OGViNmRlLWYwY2ItNDY0OS04OGYyLTdiZDJjZjE0Y2I0YyJ9.Tnk1DaLqD616A-6Usgb168t1KGLRjUDBQyMiAe-vMOw" width="1817" style="width: 1819px; height: 497.604px;" height="498" class="fr-fic fr-dii"></p><p><strong><span style="font-size: 10pt;">Fig 42. Invoices linked to agreement</span></strong></p><p><br></p><p>If a recurring invoice is setup for the agreement, any invoice generated from this will be linked to the agreement automatically. Invoices created for pre-pay records associated with this agreement will also automatically be linked to the agreement. Any additional invoices can be manually linked to the agreement using the "Agreement" field. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjM2ZDBiYjg4LTgzZjYtNGM4Mi05MDU5LTI3ZTA1MTMyMzU5OSJ9.CHU34Bl26yRtXMSQsky2axJiZn1sr1CbdEaeEAr8D9Y" width="1706" style="width: 1708px; height: 499.286px;" height="499" class="fr-fic fr-dii"></p><p><strong><span style="font-size: 10pt;">Fig 43. Field to associate an agreement with an invoice</span></strong></p><p><br></p><p data-pasted="true"><strong><span style="font-size: 14pt;">Customising the Tabs Shown within Agreement Setup</span></strong></p><p>The tabs that show when setting up an agreement can be customised to allow you to hide setup tabs that are not applicable to you. To do this you will need to create an agreement screen layout profile.</p><p><br></p><p>Head to Configuration > Advanced Settings > Screen Layout Profiles > Change the "Entity" dropdown at the top to "Agreement", then click "New" in the top right corner.</p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><img data-fr-image-pasted="true" src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQwMTIzN2ViLWQwOTEtNDRlZi1hNzkzLTBiM2VmYTlkMzgzNSJ9._KHYnzqltNEU5NmCbscGBpQwGayxfV0LE7F6BF_6F5U" width="1221" height="574" style="box-sizing: inherit; border-style: none; text-align: left; width: 1223px; height: 573.9px;" class="fr-fil fr-dib"></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><strong><span style="font-size: 10pt;">Fig 44. Creating a new layout profile<br></span></strong></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><br style="box-sizing: inherit;"></p><p data-pasted="true">To set which tabs are shown/hidden head to the "Tab Layout" tab of the screen layout profile > change "Tab layout" to "Custom" then all available tabs will show. Edit each tab to set if it is shown or hidden. </p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><img data-fr-image-pasted="true" src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjMxNGJkYTMzLTQwYmQtNDZmMS1iZTU2LTE0NzhjZGU5NDQwYiJ9.vJfmnGq8EA-0acOJz-O6NiQxsMvLje4qWSU6IqEw3Eg" width="1230" height="579" style="box-sizing: inherit; border-style: none; text-align: left; width: 1232px; height: 578.892px;" class="fr-fil fr-dib"></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><strong><span style="font-size: 10pt;">Fig 45. Customising the tabs</span></strong></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><br></p><p data-pasted="true">To set which fields are visible against agreements, head to the "System field visibility" tab and toggle the visibility of each field. <br><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjM0ODAyNzhkLTAzMjUtNDExNC05MWY5LWViOTNiNzE5MWNjZiJ9.JNyAhzCU5Y0CWbI6UlSIkpHRNihC2KkPwByI229i624" class="fr-fic fr-fil fr-dib" style="width: 1571px; height: 609.163px;" width="2154" height="836"></p><p data-pasted="true"><strong><span style="font-size: 10pt;">Fig 46. Toggle System field visibility for screen Layout Profile</span></strong></p><p><br></p><p data-pasted="true">To use this profile set it as the global default, or each agent can choose this screen layout in their preferences. The screen layout chosen by an agent will override the global default. </p><p><br></p><p>Set this as the global default for agreements under Configuration > Advanced Settings > use "Default Agreement Details screen layout".</p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><img data-fr-image-pasted="true" src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImVkMjIwYjEyLTk1MzYtNDQxYS05Yzc2LTVlZjVmNmVmZDE5OSJ9.FlLfa9JR72fdnj99vDyD3-AoOrdiGWVvSSivZH2zLQg" width="1233" height="580" style="box-sizing: inherit; border-style: none; text-align: left; width: 1235px; height: 580.418px;" class="fr-fil fr-dib"></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><strong><span style="font-size: 10pt;">Fig 47. Changing the Default Agreement Details screen layout<br></span></strong></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><br></p><p data-pasted="true">To set the screen layout profile for a specific agent, head to the agent's preferences > Screen Layouts section > use "Agreement Details screen layout".<br><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjYwMDY3ODRmLWY0YmQtNDc4MS04NDZiLTMxOWFmM2Q0N2RmNCJ9.OmwVv0Q0iincHblhs6QeBHq9ePJAEbz34Wn0DpJ2X2w" class="fr-fic fr-fil fr-dib" width="518" style="width: 520px; height: 860.364px;" height="860"></p><p data-pasted="true"><strong><span style="font-size: 10pt;">Fig 48. Agreement Screen Layout for Agent </span></strong></p><p><br></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><br style="box-sizing: inherit;"></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><br></p>
