Contracts Help and User Guide

1. Contract Pre-Requisites

All sections within this Pre-Requisites and settings guide should all be reviewed; some may not be relevant to your required set up but in our experience if you take time and care setting up the module, follow the advice given, it can prove invaluable when you actually start using the module, and like all software if it’s set up correctly, it will be easier to use.

1.1. Product Group Creation A Pre-Requisite

A mandatory requirement for the module is that you set up at least one stock product group, and set the product type as Service/Labour. We also recommend ticking ‘keep movement history’.

When  considering whether you have just one product group or multiple, you should base your decision on the reporting requirements of the company as to how revenue and costs for different types of service contracts need to be reported, and whether you are looking to have different nominal codes based on different services.

If you report different service types separately in your management accounts, it is likely that each service type has a unique nominal code from a revenue and cost perspective. If this is the case, you should set up a stock product group for each of these contract types and associate the relevant nominal code(s) against each one.

If you are using separate P & L nominal codes for different contract types, and for reconciliation purposes, we recommend that you have an equal number of balance sheet codes – one for each contract type.

1.2. Product Group Sicon Maintenance Contract Tab

Only visible when the contracts module is installed, and where all contract module scripts are enabled for the relevant user.

This area should be reviewed and configured before the module is set up. This is especially important when using the contracts module to manage deferred income and costs.

1.3. Product Group Nominal Set-Up for Contracts

If you’re not using the Sicon Contracts module to manage deferred income and/or costs, you should leave the deferred nominals on the ‘Maintenance Contract’ tab all blank .

If you’re not managing deferred income through Sicon Contracts, then for the Sales Order generated from contracts through to Sage 200 Sales Order Processing when posted, use the nominal code set on the standard Sage 200 analysis tab on the stock item within the section ‘default nominal codes’.

For advice on nominal codes and structure, please refer to your Sage 200 Business Partner and/or accountant.

If you’re only managing deferred income but not deferring costs, you only need to populate the top two, labelled ‘Profit and loss revenue nominal code’ and ‘Balance sheet deferred revenue nominal code’.

1.3.1. Managing Deferred Income and/or Costs

Default nominals for managing deferred can be set as default at product group level or on the service stock item if different, and although not recommended (as it can be very time consuming) you can manage on the contract line itself if configured to allow within contract settings and by ticking the enable deferred nominals tab setting.

Fields on this tab explained further

The first two fields are relevant to revenue:

• Profit & Loss revenue nominal code: The default P & L revenue account which will be credited monthly during the month end journal routine, or debited if a contract sales return credit is processed and posted.
• Balance sheet deferred revenue code:  The default balance sheet account which will be debited monthly during the month end journal routine, or credited if a contract sales return credit is processed and posted.

The bottom two fields are only relevant if using the module to manage deferred costs:

• Profit & Loss cost nominal code: The default P & L cost account which will be debited monthly during the month end journal routine, or credited if a contract sales return credit is processed and posted.
• Balance sheet deferred cost code: The Default balance sheet account which will be credited monthly during the month end journal routine, or debited if a contract sales return credit is processed and posted.

Important: Where managing deferred income through the Sicon Contracts module, the ‘balance sheet deferred revenue code’ (second field) must be the same as the one set in the revenue field on the Sage standard analysis tab – as per the example below.

This is because it’s important that the balance sheet account that is debited during the monthly journal routine is the same balance sheet nominal account that the initial sale/SOP invoice (or credit) is posted to during the SOP post routine.

If you’re managing both deferred income and costs through Sicon contracts, then you need to populate all four fields.

1.4. Product Group SOP & Contract Create Options

At product group level, (or as an override at stock item level) and within the Sicon Contracts settings, you will see options as to how the module will treat the contract lines when added via a sales order (as opposed to adding directly within Sicon Contracts). The options being:

• Always create a new contract for the customer, regardless of whether there is an existing contract for the SOP customer; or
• When updating contracts from SOP, look for an existing contract for the customer, but always create a new contract line.

If neither are ticked, where the customer, service stock item, along with other line details such as bill cover from and to dates and pricing all matches at the point of the sales order being posted, the linked/found contract line qty will be incremented.

In all cases when a contract/contract line is added directly onto a sales order within SOP, until the sales order is posted it is treated as ‘pending’.

If neither of the options above are ticked, or just the 2^nd option is ticked, look for an existing contract for the customer, but always create a new contract line. The pending line can be seen within the customers’ existing live contract, by selecting the pending radio button within the contract.

If the top option is selected, always create a new contract, then initially when the sales order is saved a separate pending contract will be created starting with the number 999 and can be visible on the contract list view on the main contract screen selecting the contract status = pending.

Only when the sales order is posted within SOP will a new contract with the final contract number will be created.

Important Notes

• If neither option is enabled, if you create a new sales order for a customer that does not have an existing contract, and where on the sales order you add more than one contract line on to that new sales order, the system will generate a separate pending contract for each line added. This is because when line one is added on to sales order there is no existing contract, and when additional lines are added there is still no existing contract, because until you post the sales order the lines are pending.
• If it’s important to you that there is only one contract, not separate contracts for the same sales ledger customer then you should initially create the contract within the contract module and not via sales orders. 
• If within contract configurations, and on the contract line settings tab, you have ticked the ‘only service items to be visible when adding lines to a contract’, but where on occasion you need a contract invoice to be generated with stock items on it as well, then once you have generated a contract order through to SOP, you could amend the sales order and add stock codes as additional lines.
• Alternatively, you could add a new sales order for a new contract customer, just adding one contract line, print and post so a contract does exist, create a 2^nd sales order so there is an existing contract and the lines will add to the existing contract, (subject to the above settings).
• The cleanest route would be to start within a contract adding the multiple lines, but by following the steps above there are options.
• From within Sicon Contracts, to see what contracts/which contract lines are pending, you can use the contract status ‘pending’ within the contract’s maintenance view.
• Important to note that if you choose to add contract lines via sales order processing, and where the service item product group is set to confirmation not required, you need to be mindful that if the contract start date is in the future, the Sage SOP module will still suggest the generation of an invoice, this is because when the ‘confirmation not required’ flag is set Sage assumes it needs to be invoiced.

1.5. Product Group Default Contract Line Descriptions

Default descriptions can be set at product group or at service stock item level if different to that set at product group level.

It saves time if your contract lines have the same information such as billing period of cover dates, same service descriptions and comments. You can also use the variable insert (as screen shot below) to pull various pieces of information through from data added on to ta contract line.

If defaults are set at product group level, unless different on the service stock item set up you do not need to enter default descriptions as when used the product group defaults will be used.

Selecting the ‘Insert Variable’ button shows the user all the fields that can be used, and when the required one is found in the list, simply double click to select it.

NB: If you do not set any defaults on either the product group or the service stock item level, when adding a contract line onto a sales order, you can use the ‘amend description function’ as per the screen shot below and it will pull through the code and the period of covers.

Recommended – Setting defaults | In our experience with using the module, customers are more likely to pay an invoice if the dates of the service being invoiced for are shown. As such, we recommend setting up defaults or when adding a contract item on to a sales order using the ‘amend description’. Another reason for adding default contract line descriptions on to either the product group or on an individual service stock item, is so that the information added pulls through onto the contract line itself.

The screen shot below shows a contract where line one was from a product group that did not have any default contract line description set, whereas line two and three did.

1.6. Product Group Nominal Code Recommendations

For reasons explained in previous sections, if you are managing deferred income through the Sicon Contracts module then the nominal code, in the second field on the analysis tab, on the stock product group details tab must be the same as the balance sheet revenue nominal as specified on the Sicon tab/maintenance contract option.

Standard Sage 200 requires nominal codes in accrued receipts, but these are not used by the Sicon Contract module, so we advise for contract purposes that you consider populating with a suspense nominal code.

If you are using Sicon Contracts to manage deferred costs, there are two places on a contract line where costs are entered;

• on the contract line enter the cost in the unit cost field; OR
• where the cost is made up of multiple costs from multiple suppliers, enter using multiple cost lines with supplier details on to the Multiple Supplier Costs Tab. For more information on this please refer to the ‘Entering Details on the Multiple Supplier Tab’ section of this Help & User Guide.

1.6.1. Using Sicon Projects?

If you are using Sicon Projects and planning to integrate this with Sicon Contracts, please review the following:

If the nominal code shown on the Sage analysis tab in the revenue field is showing the balance sheet deferred nominal account correctly, but during testing before going live you spot the sales order was posted to another nominal code, you need to check (view) the sales order line to see which nominal code the sales order has picked up/is using.

If the sales order was generated from within Sicon Contracts, the user cannot manually change the nominal code when either an order has been generated from contracts (as we lock it down), however if it’s been manually added on a sales order a user can (shouldn’t, but can!) change the nominal code.

Furthermore, if Sicon Projects is installed and set to integrate with Sicon Contracts, because Sicon Projects is ‘king’ it may be that the project header that was set on the line has overridden the nominal code. This is because the project header, when created during the Sicon Projects set up, has had a default nominal code set against it and is overriding the nominal set up on the stock record.

If this is the case, you should review the project header set up within Sicon Projects and ‘Maintain Project Headers’.

It’s likely you have a project header specifically for contracts. If this is the case, then make sure that the default nominal account is set to be the same as the stock record/analysis tab/revenue field nominal account.

If you are using a generic project header, then make sure there is no default nominal code set on the project header – this way the sales order line will use the stock record nominal code.

1.6.2. Using default CC & Dept’s on sales Ledger Accounts ?

Please be aware that if you have default nominal codes, cc and dept’s set up on customers within sales order processing settings/default accounts tab, and you have both ‘use same nominal code as customer account’ and ‘use same cost centre & dept as customer account’ selected, you may not see the results you expect when the SOP orders/returns are posted.

This is because regardless of what is setup on the stock record as to where to post the revenue, the settings will override it.

If you are part of a group of companies, you may be required to act in accordance with the International Financial Reporting Standards (IFRS), which are a set of accounting rules for the financial statements of public companies that are intended to make them consistent, transparent and easily comparable around the world.

If this is the case, and if the setting is enabled within Contract Utilities on the Deferred Transaction tab, please refer to the screen shot below;

You will see an additional field on the stock product group and contract stock code, and you will need to set a nominal code on the balance sheet to which to post the IRFS initial element.

IMPORTANT NOTE: If you are unsure whether you need to enable and configure, or indeed as a company need to act in accordance with IRFS, then you should speak with your financial advisors for advice; neither your Business Partner or Sicon will be aware of your companies’ structure in this respect and cannot advise.

Below is an example of the expected postings when IFRS is activated at 20%.

1.7. Creating Service Stock items for Contracts

A mandatory requirement for the Sicon Contracts module is that you set at least one stock item that is set to be a product type of Service/Labour and link it to the relevant product group you have previously created, (as described in the previous section).

When creating service items to be used within Sicon Contracts, one thing to consider is the consistency of how they are set up, so not only are they grouped together in the stock list but when adding them to a contract if they all set up in the same way it will be easier for users to search/find and add them. In the example below, you can see we have been consistent with the code and names have been given;

1.7.1. Fields/Settings on the Sicon Tab

When creating your service stock item(s), as well as the standard information entered on the ‘Details’ tab, you should review and populate where necessary details on the Sicon Tab.

Setting 1

In all cases where the service stock item is to be used within Sicon Contracts as a recurring item at set frequencies and values [ i.e. invoice every month at £100 for 3 years), you must tick the ‘Maintenance Contract item’ option.

If the service stock item is to be used within Sicon Contracts, but with variable billing, you would leave ‘maintenance contract item, unticked but tick ‘Use variable Billing’.

If a service item is not ticked as a maintenance contract item, when adding to a contract line the required contract fields will be greyed out, as per the example below;

Setting 2

As mentioned within the previous section [Setting up a product group], there are options available to determine how the module will treat the contract lines when added via a sales order (as opposed to adding directly within Sicon Contracts. The options being:

• Always create a new contract for the customer, regardless of whether there is an existing contract for the sop customer; OR
• When updating contracts from SOP, look for an existing contract for the customer, but always create a new contract line.

If neither are ticked,  where the customer, service stock item, along with other line details such as bill cover from and to dates and pricing all matches at the point of the sales order being posted, the linked/found contract line qty will be incremented.

In all cases when a contract/contract line is added directly onto a sales order within SOP, until the sales order is posted it is treated as a ‘pending’.

If neither of the options above are ticked, or just the 2^nd option is ticked, look for an existing contract for the customer, but always create a new contract line  so the pending line can be seen within the customers’ existing live contract, by selecting the pending radio button within the contract.

If the top option is selected, always create a new contract, then initially when the sales order is saved a separate pending contract will be created starting with the number 999 and can be visible on the contract list view over main contract screen selecting the contract status = pending.

Only when the sales order is posted within SOP post will a new contract with the final contract number be created.

Important Notes

• If neither option is enabled, if you create a new sales order for a customer that does not have an existing contract and where on the sales order you add more than one contract line onto that new sales order, the system will generate a separate pending contract for each line added. This is because when line one is added onto a sales order there is no existing contract and when additional lines are added there is still no existing contract, this is because until you post the sales order, the lines are pending.
• If it is important to you that there is only one contract, not separate contracts, for the same sales ledger customer then you should initially create the contract within the contract module and not via sales orders. 
• If within contract configurations and on the contract line settings tab you have ticked the ‘only service items to be visible when adding lines to a contract’ but where on occasion you need a contract invoice to be generated with stock items on it as well then once you have generated a contract order through to SOP, you could amend the sales order and add stock codes as additional lines.
• Alternatively, you could add a new sales order for a new contract customer, by just adding one contract line, print and post so a contract does exist, create a 2^nd sales order so there is an existing contract, and the lines will add to the existing contract (subject to the above settings).
• The cleanest route would be to start within Sicon Contracts and add the multiple lines, but by following the steps above there are options.
• From within Sicon Contracts to see what contracts/which contract lines are pending you can use the contract status ‘pending’ within the contract’s maintenance view.
• Important to note that if you choose to add contract lines via sales order processing, and where the service item product group is set to confirmation not required, you need to be mindful that if the contract start date is in the future, the Sage SOP module will still suggest the generation of an invoice, this is because when the ‘confirmation not required’ flag is set Sage assumes it needs to be invoiced.

Setting 3

This will be greyed out (as per the example above) if the service stock item is to be used at agreed intervals, agreed pricing and for an agreed duration, but if the service stock item is to be used within Sicon Contracts needs to have variable billing, you would leave ‘maintenance contract item’ unticked but tick ‘Use Variable Billing’ as the example below;

Setting 4

Default descriptions can be set at product group or at service stock item level if different to that set at product group level.

Setting defaults saves time if your contract lines have the same information (such as billing period of cover dates, same service descriptions and comments) you can also use the variable insert (as per the screen shot below) to pull various pieces of information through from data added on to a contract line.

If defaults are set at product group level, unless different on the service stock item set up, you do not need to enter default descriptions as when used the product group defaults will be used.

.

Selecting ‘Insert Variable’ button shows the user all the fields that can be used, and when the required one is found in the list simply double click to select it.

NB: If you do not set any defaults on either the product group or the service stock item level, when adding a contract line onto a sales order you can use the ‘amend description function’ as per the screen shot below and it will pull through the code and the period of covers.

Recommendation – Setting Defaults | In our experience with using the Sicon Contracts module, customers are more likely to pay an invoice if dates of the service being invoiced for are shown, as such we recommend setting up defaults, or when adding a contract item on to a sales order using the ‘amend description’.

Another reason for adding default contract line descriptions on to either the product group or on individual service stock item, is so that the information added pulls through on to the contract line itself.

The screen shot below shows a contract where line one was from a product group that did not have any default contract line description set, whereas line two and three did.

At service stock item level, only needs populating if the contract line description needs to be different to that set at the linked product group level.

Setting 5 & 6

Where you are managing deferred Income and/or costs through Sicon Contracts , you need to ensure on the service stock item you tick the relevant options.

Default nominals for managing deferred can be set as default at product group level , so unless they need to be different from the nominal codes set at the linked product group, the only settings you need to do on the service stock item on the Sicon tab is tick the ‘create monthly journal postings from deferred revenue’ and if applicable ‘create monthly journal postings from deferred costs’  as per the example below;

Important: Where managing deferred income through the Sicon Contracts module, the balance sheet deferred revenue code must be the same as the one set in the revenue field on the Sage 200 standard analysis tab.   This is because it’s important that the balance sheet account that is debited during the monthly journal routine is the same balance sheet nominal account that the initial sale/SOP invoice (or credit) is posted to during the SOP post routine.

There is a third option when it comes to setting which nominals to be used during the deferred income and/or cost journal routine and that is by within the Sicon Contracts settings and by ticking the enable deferred nominals tab setting, if ticked on the contract line, an extra tab appears for you to manually (on each line) set the 4 nominals to be used. This is very time consuming and not recommended; it is there as an option where for one particular contract line only the nominal codes to be used need to be different.

Nominal Code fields further explained: 

The first two fields are relevant to revenue:

• Profit & Loss revenue nominal code: The default P & L revenue account which will be credited monthly during the month end journal routine or debited if a contract sales return credit is processed and posted.
• Balance sheet deferred revenue code:  The default balance sheet account which will be debited monthly during the month end journal routine or credited if a contract sales return credit is processed and posted.

The second two are relevant where you need to manage deferred costs.

• Profit & Loss cost nominal code: The default P & L cost account which will be debited monthly during the month end journal routine or credited if a contract sales return credit is processed and posted.
• Balance sheet deferred cost code: The Default balance sheet account which will be credited monthly during the month end journal routine or debited if a contract sales return credit is processed and posted.
• If you are managing both deferred income and costs through Sicon contracts, then you need to populate all four fields.

Important: Where managing deferred income through the Sicon Contracts module, the balance sheet deferred revenue code (second field) must be the same as the one set in the revenue field on the Sage 200 standard analysis tab as per the example below;

This is because it’s important that the balance sheet account that is debited during the monthly journal routine is the same balance sheet nominal account that the initial sale/SOP invoice (or credit) is posted to during the SOP post routine.

Setting 7

When managing deferred income and/or costs using this feature, instead of the deferred income/costs being spread evenly over the course of the invoiced billing period, you could choose to specify that the whole of the invoiced value is posted as one sum, and further more specify when this one sum is included in the deferred journal routine.

If for example, as per the screen shot below, we have ticked the option and set to ‘one off transaction 3 months after’. If we raised an invoice from Sicon Contracts for £1200 for a 12 month contract period 01/01/2024 to 31/12/2024, instead of posting £100 per month deferred , it would post the full £1200 3 months into the contract that being 31/03/2024.

This is not a widely used function, but its there as an option to be set at service stock item level.

1.8. SOP Settings – Contract Pre-Requisites

Option1: To avoid unnecessary steps within sales orders, having to despatch free text/service lines after generating (from the Sicon Contracts module) the contracts through to SOP for invoicing, we recommend within SOP utilities: system set up: sop settings and on the order processing tab, that the service/labour order lines should be defaulted to confirmation not required.

Option 2:  If you do have non-contract line sales orders with service/labour items that do require users to confirm dispatch, then leave as confirmed with goods despatched or confirm as service/free text, because the Sicon Contracts module will override the step, just for service stock codes that are flagged as maintenance contract items.

The next step is to ensure the relevant contract users processing through to sales order have the relevant permissions set.

Within SOP utilities-system setup-user permissions, please ensure the users who will be using Sicon Cnntracts have at least the override prices, override cost prices set to yes to ensure on a contract line they can amend the relevant prices.

2. Review Contract Utilities & Settings

Prior to using the contracts module, please review and configure all the options within contract utilities and configuration as required/as explained below.

2.1. Contract Settings & Defaults

After Sicon Contracts has started to be used and you have contracts processing, you can change the configuration and settings if you feel it’s necessary to do so, accepting that if changed you may see some changes in appearances of screens and how the system manages certain aspects of how transactions are processed/handled.

Functionality

Enable auto number: If enabled, when a contract is added upon saving, a contract number based on the prefix and format set will be allocated.If not enabled upon saving of a contract users will be able to manually enter a contract number using numbers and / or letters of their choice, noting that where contract lines are being added via the SOP module and where the system is set to always create a new contract, regardless of whether there is an existing contract for the sop customer, then until the sales order is posted, a temporary pending contract number is issued.

Allow user to amend contract copy: If enabled, this will allow the users to copy an existing whole contract. This works well for contracts that contain just one single contract line or where separate contracts for the same customer is your preferred use of the module. It does not work so well if you have multiple lines per contract because you would use the function to copy, and then potentially unless all details on all lines are exactly the same, you would need to change details where necessary – so the time saving may not be worthwhile.

Allow contract customer change: Not recommended where managing deferred income and/or costs as there is likely to be a requirement to adjust certain elements on the copied line. As such, the time saving would be minimal and from a future audit and historical purposes allowing a contract line customer change may make auditing more difficult.If you change the customer and then look on the contract ‘Sales orders generated from this contract’ pane, the sales order listed will not show they are for another account, which could cause confusion.

If you do enable this feature, and please note that any previously linked sales orders generated from a contract and deferred postings will not retrospectively change to the revised sales ledger account, this option should be used with care and consideration.

Quantity format: On a contract line, by default two decimal places is set as ’00’, but where more are required enter the number of decimal places here, for example if four are required enter ‘0000’.

Attachment location: Default location for documents to be stored that are added within the attachments tab; we recommend this is a location that is covered as part of your companys nightly backup routine.

Year-end Date: Year End date is purely used in connection with the feature ‘Enable ‘New / Existing’ status’ as per the screen shot below, which in turn could be used for custom reporting to show whether within a 12-month period of invoice period the deferred transaction is class as ‘new’ within that period or ‘existing’.

This is an unusual feature, but works well for those that needs to record within a given 12-month period (and not the same 12-month period as their Sage 200 financial year), whether it was a new contract/transaction or existing.

If the ‘Enable New / Existing’ status feature is enabled within optional settings, then when looking at the deferred transactions where a transaction date is after the year specified, the Year End Date will be show as ‘existing’ whereas the ones prior to the date specified in Year End Date will be shown as ‘new’.

Enable dismiss option on update contract lines screen: When sales orders that include a contract and/or lines are posted within SOP and the SOP routine is complete, an additional Sicon screen appears which is known as ‘Update Contracts’, please refer to the screen shot below.

We do not recommend this setting being enabled for the reasons below.

This second step/process shows which contract(s) and which contract line(s) will be either added, updated or deferred transactions created, without having to manually go into contracts, contract processing and post invoice update to retrieve the update contracts step.

By default, they are all ticked, and the user would select Process.

If however, the ‘enable dismiss option’ is enabled, at the point of post sales orders, a user could choose to dismiss the creation of contracts, which in turn means the user would need to remember to go into contracts\contract processing and post an invoice update.

Without this 2^nd step being run, the contract lines will not be added / updated from the sales order and where you are managing deferred income and costs, the deferred transactions will not be generated.

• Always create a new contract for the customer, regardless of whether there is an existing contract for the sop customer; OR
• When updating contracts from SOP, look for an existing contract for the customer, but always create a new contract line.

If neither are ticked, then the system will look to match the customer and the service stock item, along with various line details such as bill cover from and to dates, pricing and only if all the relevant fields matches, at the point of the sales order being posted the linked/found contract line quantity will be increased rather than a new line or new contract being created.

In all cases when a contract/contract line is added directly onto a sales order within SOP, until the sales order is posted it is treated as a ‘pending’.

If neither of the options above are ticked, or just the 2^nd option is ticked, look for an existing contract for the customer, but always create a new contract line so the pending line can be seen within the customers’ existing live contracts, by selecting the pending radio button within the contract.

If the first option is selected, always create a new contract, then initially when the sales order is saved a separate pending contract will be allocated starting with the number 999 and would be visible on the contract list view over main contract screen selecting the contract status = pending.

Only when the sales order is posted within SOP would a new contract with a proper contract number will be created.

Important Notes

• If neither option is enabled, if you create a new sales order for a customer that does not have an existing contract and where on the sales order you add more than one contract line on to that new sales order, the system will generate a separate pending contract for each line added.
• This is because when line one is added onto a sales order there is no existing contract, and when additional lines are added there is still no existing contract, because until you post the sales order the lines are pending.
• If it’s important to you that there is only one contract, not separate contracts for the same sales ledger customer then you should initially create the contract within the contract module and not via sales orders. 
• If within contract configurations and on the contract line settings tab ticked the ‘only service items to be visible when adding lines to a contract’ but where on occasion you need a contract invoice to be generated with stock items on it as well then  once you have generated a contract order trough to SOP, you could amend the sales order and  add stock codes as additional lines.
• Alternatively, you could add a new sales order for a new contract customer, just adding one contract line, print and post so a contract does exist, create a 2^nd sales order so there is an existing contract, and the lines will add to the existing contract (subject to the above settings).
• The cleanest route would be to start within Sicon Contracts adding the multiple lines, but by following the steps above there are options.
• From within Sicon Contracts to see what contracts/which contract lines are pending, you can use the contract status ‘pending’ within the contract’s maintenance view.
• Important to note that if you choose to add contract lines via sales order processing, and where the service item product group is set to confirmation not required, you need to be mindful that if the contract start date is in the future, the Sage SOP module will still suggest the generation of an invoice, this is because when the ‘confirmation not required’ flag is set Sage assumes it needs to be invoiced.

Maximise Edit Screen:  If not enabled, when you first edit the contract the screen is minimised. If enabled, when selecting ‘Edit’ the Contract Details Screen will be in ‘full screen mode’. Whether this is enabled or not enabled is down to customers preferences. If not enabled, when the form is open you can expand the form, but you would need to do this each time.

For variable billing, reset bill value when sales orders are generated: Variable billing is a method that allows you to add a contract line, but set so that for each billing period the price is/can be different.

If enabled, after a sales order has been generated for each period, at the time the next sales order needs to be generated the user would go into the update variable billing prices process and enter the new billing value, because this setting resets to zero after the previous one is raised.

Where your prices vary every month and there is otherwise a danger you invoice the same value as previously, it is advisable to enable.

Use Sicon CRM instead of SOP delivery addresses: By enabling this feature, customers using Sicon CRM can choose to link a contract line to a Sicon CRM record/contact rather than linking them to a Sage 200 SOP delivery record.

You can choose to make the selection of either SOP delivery addresses or Sicon CRM contacts mandatory on a contract line by an additional setting which can be found on the Contract Line Settings tab.

Use Contract Line List view instead of grid view when amending contract line:  We recommend this to be ticked especially for large volume of contract lines, as the system would be recalculating/refreshing each line upon save and where a contract has lots of lines then this could cause performance/speed issues. However, for small volume contract lines and for those companies who prefer to use the grid method it is an option, if so leave unticked. If making changes to details on a contract line using this preferred method users would edit the contract, edit the line and make the relevant changes to the relevant content.

Another option would be to tick/enable to help with speed/performance by default and as a exercise when needing to change for example content of SOP analysis codes on multiple lines within a single contract, enable for that moment in time, untick/disable, save and then you could go into the contract, and as per the below example, select SOP analysis tab and using grid method change the relevant information.

Disable message asking to suspend contract lines if sales ledger account is place on hold: Useful to companies where the team members who manages the sales ledger accounts have no interaction with the team members who manage contracts and who wouldn’t want the finance team flagging contract lines as suspended.

If this option is ticked, then if a sales ledger account is put on hold via Sales Ledger/Account status then the user will not be prompted with the following message.

By default, the option to disable the message is left unticked.

2.1.1. Optional Features

Enabling any of these features, will determine which if any additional tabs/fields appear against a contract/contract line.

Enable contract details tab: If enabled, when within the contract an extra tab appears showing additional fields available for reference or custom reporting, these were originally in the module before we added the ability to enable and add up 150 analysis codes per contract line, so this feature is not used widely, but could be of interest to some.

The field labels on the contract details tab are not configurable unlike analysis codes, but the drop down selections are within the contract menu item maintenance.

Enable deferred nominal tab: As default, to specify which nominal codes are to be used for managing deferred income and/or costs these are initially configured at stock product group or service stock item level, but if for some reason they need to be different on just certain contract lines, you may want to consider enabling this optional feature and adding the specific nominals codes on the line.

The default ones set at product group or service stock item level do not show and if this optional feature is enabled, and there is no change to the default, you do not need to re-enter any default nominal codes.

Enable Custom Fields Tab: A historical feature from when the module was first created and when contract lines, analysis codes or linking to SOP analysis codes was not available. We recommend contract line analysis codes are used as standard as they are available within filters, list views and could be used in reporting.

If, however you wanted additional custom fields and if enabled. If enabled, within contract settings and on the custom fields tab this can be configured as either text, numerical or dated.

They will then be visible against a contract on the custom tab and users would be able to enter the relevant data. Please Note: The Amendments Tab within the screen shot below has now been renamed Amend/Cancel.

N.B. Any reporting on custom fields would be custom and creating drop-down options to select from are not available unlike contract line analysis codes.

Enable SOP analysis codes: There are up to 150 Sicon contract line analysis codes available, but if as a company you wish to link a contract line to your standard Sage 200 SOP analysis codes for reporting you can instead of using contract lines or as well as, please enable this feature.

If enabled, you will be able to on a contract line within the SOP Analysis codes tab select the standard Sage 200 SOP analysis codes.

Please Note: The Amendments Tab within the screen shot below has now been renamed Amend/Cancel.

Various screens within contracts allows filtering by the sage sop analysis codes.

Show period of grace: If enabled an extra field appears on a contract line where you can choose to enter the number of periods of grace (in months). Please Note: The Amendments Tab within the screen shot below has now been renamed Amend/Cancel.

Use this function to flag the contract line as being in a state of ‘Period of Grace’.

An example of where you may use is where the customer is not sure they are renewing and the contract end date is approaching or has past, but you want to show the line as live instead of expired and you want the system to indicate you are still providing them with a service. If you are using the Sicon Service Module and there are equipment records against the contract line when logging a service case against the linked equipment record to the POG (period of grace) contract line, it will be classed as a live line.

By flagging the line as POG as a visual to note the fact. It would also be possible for any custom reports to pick this flag up.

Period of grace lines still show as a live contract line within the contract even if past contract end date, but the period visible within the period of grace (months) column.

They also will still appear as a reminder to send within the print renewal reminders’ as you would want to be aware they are due, but they do not show on the main contract when using the contract line details radio tab.

Enable Enhanced Discounts: This feature is one where if enabled applies to all lines, not one where you can choose at line level. When considering whether to enable, if you offer discounts based on a campaign, loyalty or a scale basis then this could be a feature that would be worth looking at.

If you offer straight forward discounts for some or all customers, and don’t need to distinguish between type, then do not enable this feature. If not enabled, line discounts are of one type (as per standard Sage 200 functionality) and are visible/amendable on the line as below, which is standard Sage 200 discount functionality.

If enabled the standard two discounts £ and % fields on a line will not appear, but instead an extra tab will appear on a contract line where you can specify discounts for different types such as Campaign, Scale or Loyalty discounts. These could then be reported on within custom reports.

NB: these labels are hard coded and are not configurable.

Within contract view and contract all lines view, the enhanced discounts are also visible by %, Unit Value, and where in use, ‘Pro Rata Unit, Total discount %, Total Discount value & yearly results.

Allow change status on completed contracts: This refers to the main contract header status on a contract. If the option to ‘Allow change’ is unticked, then a user would not be able to change the status from completed and the status would be greyed out.

Deferred Income ‘Change deferred posting status without generating journals’:

Not a recommended feature for accuracy and reconciliation reasons, but where a company is looking to part manage deferred income and/or costs through to the point of month end and would then prefer to raise a manual journal within the nominal ledger rather the Sicon Contracts module generating the journal.

When looking at the deferred transaction against a posted sales order within the contracts module each deferred transaction line is flagged with a status of either ‘Posted’ or ‘Not Posted’ status.

Posted: A journal has been created for that line during a month end process, with movements from the balance sheet to the P & L.

Not Posted: The period end routine\monthly journal postings have not yet been run.

If, as a company, you want to post your contract sales order/invoices to the balance sheet as a deferred transaction, but you do NOT want the contracts module to generate a nominal journal automatically which in turns moves values from the balance sheet to the P & L, you would be looking to enable this feature.

This is a on or off feature which if enabled will apply to all deferred transactions on all contract lines.

Important Note: If this feature is enabled you must still run the monthly journal postings for contracts process for two reasons;

1. To populate the screen to flag the relevant transactions for which you wish to change the status from ‘not posted’ to ‘posted’ but more importantly.
2. For you to know what figures you need to raise/enter a manual journal for. To do this you go into the menu option ‘Period End\Monthly Journal Postings for Contracts’ and select the month (step 1), then you must select ‘extended view’ (step 2). If using this method, we strongly recommend you send this information to excel using the function right mouse click and send to excel’ (step 3).

You would still need to select the post button (step4), as this is the function that changes the status from ‘not posted’ to ‘posted’.

You should keep the excel file in a secure location as part of your month end reporting on your companies’ network for both audit and reconciliation purposes.

Important Note: With this feature enabled after posting, the transaction status would have changed from ‘unposted’ to ‘posted’, your outstanding deferred transaction value will have reduced, this will be seen on within the contract reconciliation are of the module, but no automatic nominal movements will have taken place (until you do a manual journal) and as such you will see a variance.

It is therefore vitally important the manual journal is done straight away for the exact amount reporting on/sent to excel.

We do not recommend this setting for 99.9% of companies, it is very unique to some customers who like to function this way, but it is not a recommend option and in our experience does lead to confusion and lots of support calls with customers reporting contract reconciliation variances.

If you do decide to enable this feature we pop up a warning, as per the scrfeen shot below, to ensure the feature is understood. The feature is only enables when the warning is acknowledged by selecting ‘OK’.

Generate Contract Numbers & Generate Contract line forecasts

Generate Contract Numbers: If auto numbering was not set and contracts added with no contract numbers use ‘Generate Contract Numbers’ to populate numbering of pre-existing Contract.

Also this function can be used if contract were imported with no numbers with auto number not enabled.

Generate Contract Line Forecasts: A useful function if on a contract line you like to see a forecast of future sales orders that would be raised against a contract line. The forecast is automatically generated when a new contract order line is added, the contract is saved.

If contracts were imported, using this function to generate planned sales order forecasts based on contract information within the planned sales order tab against a contract line as per the screen shot below.

There are two types of statuses:

• Confirmed: Shows the forecast sales order value, based on invoice frequency/ values based on the contract period.
• Future: Shows you an estimated forecast if the contract line was renewed based on current period pricing.

2.2. Contract Line Settings & Defaults

Only service items to be visible when adding lines to a contract: Sicon Contracts uses items in stock control that are set as service stock items and flagged as maintenance contract items, therefore enabling this is our recommendation, especially if you have hundreds of stock codes set with a product type of ‘Stock’ – you don’t want to be scrolling through them to find your contract service stock items set as maintenance contract items.

Enable associated account for Contract Lines: If enabled, this allows you to link a 2^nd sales ledger account to a contract line. This may be useful if, for example, you service/support boilers and they are under warranty with the manufacturer, but the site where the boiler is located may also be a customer of yours and has a sales ledger account in their own right. If enabled selecting a 2^nd associated account is mandatory – but it could be the same S/L account the contract is under.

SOP Delivery address is compulsory: Tick if it’s a mandatory requirement for users to select a delivery address for the service being provide, (the standard SOP delivery addresses function is used for this area of the module).

Automatically create default sop delivery address: Only applicable if ‘delivery address is compulsory’ and if enabled this is designed to be used where there are no SOP delivery addresses created already.

• If there are no delivery address created all ready, with this enabled the system will use the customer’s S/L address and create a SOP delivery address and use on the contract line automatically.
• If the customer does have some SOP delivery address already created, then on the contract line users will need to select one from the already created sop delivery addresses.

Delivery Address \ Sicon CRM Contact field Caption: Use where an alternative name for delivery address to be used as a prompt/label – for example, if the services being supplied at a customer’s address is known to your company as ‘Site’ you may prefer to use label ‘Site’ rather than delivery address].

Display address or Sicon CRM contact when viewing contract lines: When ticked, this will show the delivery address when editing a contract line.

SOP Delivery address is compulsory: Tick if it’s a mandatory requirement for users to select a SOP delivery address on a contract line.  This option will be greyed out if on the Contract Settings Tab ‘Use Sicon CRM instead of SOP delivery addresses’ is enabled.

Sicon CRM Contact is compulsory: Tick if it’s a mandatory requirement for users to select a Sicon CRM contact on a contract line. This option will be greyed out if on the Contract Settings Tab the ‘Use Sicon CRM instead of SOP delivery addresses’ is NOT ticked

Default Warehouse for new lines: Sage stock control requires a warehouse, even for service items, when using service stock items for contract if there is no ‘real’ warehouse we recommend you set one up called ‘contracts’ or ‘service items’ and allocate accordingly against the service stock item when creating.

Default Contract Line Qty: If your contract Qty is always or mostly the same use this to set.

Default Price Interval*: If your invoice frequency is always or mostly the same set default here – options are Daily, weekly, Monthly or Annually.

Default Contract Line Duration (In months): If your contract durations are always or mostly the same, use this setting to set a default.

Default Invoice Frequency*: Associated with/works in conjunction with the field ‘Invoice Interval: Set a default invoice frequency’. For example, if most of your contracts are invoiced once every year, you would set this to 1, working with our example Invoice Interval you would have one invoice per year.

Default Invoice Interval: Associated with/works in conjunction with the field ‘Invoice Frequency:  Set a default Invoicing interval’. For example, if most of your contracts are invoiced annually you would set this to ‘years’, working with our example Invoice frequency you would have one invoice per year.

To achieve the same results, as an alternative you could set your Invoice Frequency to 12 and your Invoice Internal to months and you still would be seeing one invoice per year.

However, care should be taken on setting these last two defaults or changing on a line. For example, if you set the frequency to 12 (thinking you were entering 12 months) and you set the Interval to year, then the system would think you only invoice that contract every 12 years.

*When considering Price Interval & Invoice Frequency its important the user should consider the contract value as a whole to ensure they configure the system and use correctly.

For example, if you set the contract price interval to daily and the rate (as an example) is £1 per day, and you set the Invoice frequency to monthly and it’s a 30-day month, the Invoice for the month will be £30, but if it’s a 31day month the monthly invoice will be £31; likewise, if it’s a leap year and it’s only a 29 day month, the invoice value will be £29.

If you have chosen a daily rate (price interval) of £1 per day and chosen an invoice frequency of annually, the annual invoice could be £365 or in a leap year £364.

If your contract prices do not vary depending on the number of days in a month or year then you should be looking to use Price Interval of either Monthly or Annually.

Important Note where deferred transaction functionality is used: Only Contract sales orders/invoices set with an Invoice Frequency of Monthly or Annually will be included within deferred transaction calculations. For any contract lines set to an Invoice frequency of weekly, the revenue will be ignored from a deferred transaction perspective and will be posted to the nominal code set on the Sicon contract tab on the service stock item. A Message is displayed if a user selects invoice frequency of daily or weekly.

For examples and full details of how to use daily, weekly, monthly and annually when adding a new contract line please visit the section ‘Adding Contracts within the Sicon Contracts Module’.

This is because the journal process for journals deferred transactions is a monthly process in conjunction with Sage monthly periods

Enable price change with amendments: If enabled the users will be able to make changes to the price of a contract ongoing during the amendment process being used.

Ask for Reason for deleting contract line: Force users to select from a drop-down of reasons why a contact is cancelled. The system requires a minimum of one cancellation reason to be set. These are setup within the Maintenance Menu item, under ‘cancellation Codes’

Enable contact orders for contract orders: Enable only if you are looking to link items to a contract line that are supplied to your customer free of charge under the terms of the contract line service. If enabled an additional field will appear prompting you to select an internal area. For full details on this feature please visit section 12

Display

Hide warehouse: Will hide the Warehouse drop down list box in the contract entry screen.

Hide unit cost: Hide the amend unit price option when making amendments.

Hide internal description: If unticked the internal description column will show on the summary tab when editing a contract.

Hide Description: If unticked the description column (as per the below screen shot) will show on the summary tab when editing a contract. If the setting is ticked the description line will not show on the summary tab when editing a contract.

Enable paging on lists: If ticked, approves performance when opening lists. Only a certain amount of records will be displayed initially and as a user scrolls down more are loaded.

Hide rolling contract option: If ticked on the contract line the ‘rolling contract option will be hidden/ not visible on a contract line. Rolling contracts is further explained within this Help & User Guide ‘adding a new contract / contract line section’ but in summary its used where you a customer’s contract price is fixed ongoing with no end date and therefore does not need to be include in the renewal process.

Hide trial flag: If ticked on the contract line, the ‘trial contract option will be hidden/not visible on a contract line. Flagging a contract line as a trial is useful where your business is such that you have equipment or services on trial with a customer and you need to maintain a record for the items on trial. A contract flagged as a trial line, will not be included within the renewal processes or within the generate sales order.

As the below image shows contract lines flagged as ‘trial’ can be seen within the Contracts Lines List View, and where the contract line is flagged as trial in the column headed ‘Trial’ there will be a ‘Yes’.

As per the above image, trial lines are also visible on the main contract’s maintenance view, using the radio button Contract Line details.

2.3. Contract Sales Order Generation Settings

Sales Order analysis code to be set: Select which SOP header analysis code, (pre-configured in standard Sage 200) you wish to stamp with the title in Value of sales order analysis code been set.

Value of sales order analysis code been set: Enter a Description for the content, which will be populated as set in the relevant SOP Sales Order analysis code. This is then pulled through to the SOP module on the sales order and can be viewed on list views, printed on documentation and used for reporting.

Use Contract billing description if populated: If enabled the Billing Description entered on the main contract screen is added as a comment line on to the sales order underneath the contract line itself.

NB: If a contract has multiple lines with same renewing dates, you may not want to enable this option as you may end up with the additional ‘billing description comment’ appearing multiple times on the sales order and therefore invoice.

Create orders for customers on hold: If enabled, during process renewals and the generate sales order process, a sales order for the relevant contract will be generated; thereafter standard Sage 200 credit/on hold functions take precedent. If not enabled, the system will not generate a sales order and the account in standard Sage 200 would need to be taken off hold before the module allowed users to either ‘generated the sales order’ or processed renewals for that account.

Separate sales orders for each delivery address: If enabled, the system will generate separate sales orders per delivery SOP delivery address. For example, if you have one contract for a customer with two lines and both renew on same date for different delivery addresses, if enabled the system would generate two sales orders, whereas if you do not enable this option only one sales order would be generated and you may want to then ensure that the invoice layout on the lines show the end users contract SOP delivery address.

In Conjunction with the above, and only editable if the above setting enabled: The system will change the sales order delivery address details to match the contract line delivery address.

In conjunction with the above: Use customer delivery address description as customer order number: Use if the customer delivery address is to act as their order number on the header of the sales order. This would only work if you used the function ‘separate sales orders for each delivery addresses.

Do not generate sales orders for contract lines with zero-unit values: Where a customer has a contract with you and you do not charge but you still wish to add a contract line, you wish to review annually and go through renewal process but not generate a sales order and send an £0 invoice to them then enable this feature.

This does not affect current functionality whereby ‘if you add a contract line with a unit value, but add 100% discount, the sales order, £0/zero value invoice will be generated’.

IMPORTANT NOTE: Consolidation of Contract Lines to generate one Sales Order ONLY works where the lines are on one contract.  Consolidation of Contract Lines does NOT work across multiple contracts.  From Sicon v22, there is an override on a Sales Ledger account to take preference over the Sales Order consolidation setting above, again this setting ONLY works where the lines are on a single contract.

2.4. Contract Renewal Settings & Defaults

Rolling contracts will not appear in any of the processes such as process renewals, update renewals or print reminders.

If all your contract lines are to be set as rolling (never expires) you do not need to review or set any defaults on this tab.

Using the rolling function is not our recommended method where you like to review contracts with a view to increasing prices or/and have regular contract reviews with your customers, but if as a company once a contract price is set it’s set for the duration that you provide your customer with the said service, (and you are not looking to review them at all) then it could be you use the rolling function on some, or all of your lines.

Where you do enter a contract end date, before generating the renewal invoice you will need to go through a renewal process which, depending on your preference, can be done at line level or on mass within the menu item ‘Contract Processing’ section of the module.

If this is your preferred option for some or all of your contract lines, you should review this section before you begin using the Sicon Contracts module.

Renewal Settings

First renewal reminder in xx months and second renewal reminder in xx months: When run, the options set on this tab will determine which layout (of which there are two) is printed when printing the renewal reminders from within the Contract printing menu item.

Printing reminders is not a compulsory step within the renewal process so if you have a process where you verbally agree renewal prices with customers or if perhaps these are agreed up front, your contracts will increase at renewal by a set % then it could be you miss out the printing reminders step.

The first two settings on this tab will determine which transactions appear within the print renewal process in conjunction with the renewal month.

If you send two reminders to customers, for example one 90 days in advance of expiry and the second one 60 days ahead, you would set 3 months and 2 months as per the example above.

You then process print renewal reminders depending on which type you choose ‘First reminder’ or Second reminder’.

N.B. It’s possible to reprint a reminder by using the ‘display previous printed’ tick box as highlighted on the screen shot below.

In our example the first reminder is as below:

The layouts for each or both can be tailored to suit your companies own requirements using the standard Sage 200 Report Designer, picking up xxDayRenewalReminder.report

And our second reminder is slightly different:

Hide Renewal Quantity: Enable if you always raise a contract with a single qty of 1.

If however, you invoice for services based on number of licences for example, then you would not want to enable this feature, as when you added a contract line you would not have the option to change the qty from 1.

In our experience the majority of customers using the module will set renewal defaults as described below in order to save time during the renewal process.

Allow confirming renewals whilst updating renewal prices: By enabling this feature during the update renewal process on the ‘Update Renewal’ Screen a ‘Confirm Renewal for All Lines’ button will appear as Step 1 in the below screen shot shows:

If this feature is enabled and used, the ‘Renewal Confirmed’ box within the Renew Contract column will be automatically tickedfor those Contract lines selected, (step 2 on the above screen shot).

If this feature is not enabled the ‘renewal confirmed lines’ (step 2 above) will need to be manually ticked, or the user going into each line, on to the renewal tab and ticking ‘renewal confirmed’.

If the user performing the ‘Update Renewal Prices’ has the authority, then this feature will save lots of manual processing. As such, our recommendation is that this setting should be enabled.

Use existing annual unit price if renewal price is zero:

When a contract line is added / set up, on the renewal tab it’s possible to in advanced enter the ‘next year’s renewal price’ – for example if a first-year price was agreed at a special price, but on renewal it will revert back to a standard price. If you did work this way it’s important not hit ‘renewal confirmed’ button on the renewal tab.

If you were not looking to add the renewal price ready for renewal at the time of originally adding the contract line (as most people do not), then this feature should be enabled if you would prefer the suggested renewal price to be the same as the current price. (You could then change it if required on the renewal tab on the contract line, or on the update renewal price function).

If you do not enable this feature, and you have not added the renewal price at the time of the original contract line being added, during the renewal process, whether on a line or doing the on-mass update renewal process, the new renewal price will be £0 and you would have to manually enter each line renewal price or use price book function.

Enable if you would prefer on the contract line, on the renewal tab, that the current contract line unit price is pulled through into the Renewal annual unit price field rather than £0.

When renewing, default renewal discounts to current discounts if renewal discounts are not set: Enable if at renewal you want the system to suggest that the renewal discount remains the same as prior to renewal.

Default renewal frequency to current line frequency: Enable if at renewal you want the system to suggest that the renewal invoice frequency (how often you invoice) remains the same as prior to renewal.

Default renewal duration: If, as a rule, all your contract renewals have the same contract length/duration, to save time at renewal set your default duration here – for example if your contracts are for 12 months.

Default price % increase: If, as a rule you, always increase your contracts by a certain % at renewal, to save time set the default increase % here.

2.5. Deferred Transaction Settings & Defaults

Set first movement of deferred to be based on a percentage (%) of the contract value: If, as a company, you have to recognise to the P & L a higher deferred income in the first month, then enable this feature and set the %. 

When the deferred transactions are generated after SOP invoice post, you will see within the deferred transactions against the relevant sales order the first month is higher. 

Important Note: This feature is an ‘on or off’ feature and if enabled will apply to all deferred transactions on all contract lines. It’s not a feature which can be determined at line level. 

If this feature is not enabled, the associated items will disappear, as per the screen shot below. 

Calculate deferred amount based on the number of days in the month: By default this setting is enabled for new sites / customers upgrading.

The options are therefore either to be spread evenly throughout the period of cover OR based on the number of days in a month.

If this feature is not enabled and your annual contract value/sales order Invoice posted is £1200 then the deferred movement monthly will be £100.

If this feature is enabled for the same £1200, for the period 01/04/2019 to 31/03/2020 (366 days) the monthly deferred movement would be as below:

Sage 200 as standard in SOP / the Invoice and in turn the deferred transaction will be rounded to 2 decimals.

Important Note: Changing this setting after previous transactions have been generated will ONLY apply for new Sales Orders/SOP invoices posted from contracts, no changes will be made to previous generated deferred transactions whether posted/not posted transactions.

Enable IFRS: If you are part of a group of companies, you may be required to act in accordance with the International Financial Reporting Standards (IFRS) which are a set of accounting rules for the financial statements of public companies that are intended to make them consistent, transparent and easily comparable around the world.  

When this setting is enabled, you will see an additional field on the Contract Stock code.

Below is an example of the expected postings when IFRS is activated at 20%: 

2.6. Sicon Projects Integration

If Sicon Projects (previously known as Sicon job Costing) is installed, the ‘Sicon Projects’ tab will appear within Contract Settings.

If, as a company, you are not interested in integrating the two modules you would not enable Sicon Projects.

If you are looking to integrate, there are several options available as detailed by the numbering on the screen shot below.

Point 1 | Enable Projects, if integration between the two modules is required tick Enable Projects.

Point 2 | New project for each contract: If you would like a Sicon Project for every contract automatically created at the point you save the contract, and all lines within that one contract to be visible on that same project, tick ‘Create project for every contract’.

Point 3 | Automatic Project Numbering: If configured, when you save a contract the system will use the format entered here to create a project/set the project number.

For example, your projects start with the letters ‘AC’ and are 6 digits long and you would like the first one to be created with a number of 10 you would set it to be AC0010. The field length is not mandatory.

If you have enabled Sicon Projects and do not set a number, when adding a line you will need to select an existing project and project header.

If you have set a number for a format of 6 digits, no letters or numbers example 000000 and you add a contract which, when saved, is saved with a contract number of 000036, your project number will be 000036.

If you have chosen to create a new project for each contract line where your format was simply 6 digits 000000, and you added a new contract with 2 lines which when saved was contract number 000040, the project numbers will be 000040-0001  and 000040-0002.

Point 4 | Default Project Header: Every transaction linked to a Sicon Project also has to be linked to a project header. Using project headers is the modules way of categorising and grouping costs/revenue (Similar to within the Nominal ledger, you have a Nominal Account code and a CC & Dept).

Project Headers will be need to be configured and set up before a default can be selected on this tab. For further information on please refer to the Sicon Projects Help & User Guide; Maintenance Menu Job Header Types.

In the screen shot above, we created within Sicon Projects Maintain Project headers a project header called ‘Cont Rev'(as a code) with a Description Contract Revenue.

In this example we set both the header & Project header type to be revenue. A Header type is simply Cost or Revenue, and helps control which headers are presented to you when entering a transaction and when, (so you only see revenue headers when putting on a sales order for example).

If Sicon Projects is enabled, but you have chosen not to automatically create a new contract and/or create contract per line, you can choose to set a default project header and when adding a contract line, it would just be the project you have to select.

A Project Header Type gives you another level of analysis, as it’s then possible to group multiple project headers into a type.

You can then use this type in reports it drives, which headers will be available where in another  Sicon addition for sage 200 , that being on Sicon Approvals, (so the header type can be associated with expenses, timesheets or purchase requisitions) and also controls which Project Group the headers will appear within when looking at the Project Summary tab in the enquiry screen.

You do not need to set any other defaults on this screen as they are not relevant to contracts especially the nominals, as nominal codes for contract service stock items are configured at product group or service stock item level.

Point 5 | New Project for each contract line: If you would like to create separate Sicon projects for every line not grouping all lines on one contract to a single project tick the Create new project for each contract line.

If create a new project for contract line is ticked but create a new project for each contract line is not ticked, and you have a contract with five lines, there will be just one project and all revenues from those five lines will be seen on the created single project.

If ‘create a new project for each contract line’ is ticked as well, you will see five separate projects one for each of the five lines.

If Sicon projects is enabled, but you have not chosen to either create a new contract for each contract or create new contracts for each line, when adding a contract and contract lines these will need to be selected when adding a new line as per the screen shot below

If you only enable Sicon Projects Integration after you have started to process contracts, you will either need to go into each contract or process any further sales orders/invoices into each contract – select the Projects tab where you will see the blank columns for both Projects and Project Headers and these will need to be set before re-saving.

Alternatively, if auto creating projects based on the defaults set on this Sicon Projects tab, within settings there is an option to retrospectively create as explained further down in Point 7.

Point 6 | Zero sales order transactions in Project costing and show deferred postings instead: Only editable if ‘Enable Projects’ is selected. If managing deferred income through the Sicon Contracts module, and if on the Project you prefer to see the revenue in the month that the deferred income is moved to the P & L during the monthly journal process rather than one lump sum from the sales order, tick this.

If not enabled, then the contract period revenue will appear as one lump figure when the sales order is invoiced.

If enabled, when you post a sales order, to begin with the whole value of the posted sales order will show within the project.

When the first months deferred transaction is from the balance sheet to the P & L during the month end monthly journal process, (where the transaction status changes from not posted to posted).

When looking at the same job enquiry view you will see the original value is cleared and the monthly amount now showing in deferred transactions with the status posted.

Point 7 | Create projects for Contract Lines with no Projects: You would be looking to use this function if for example you purchased Sicon Projects after you had started using Sicon Contracts and you wish to integrate the two modules together, or you have been using both modules but independently of each other and now wish to integrate them. This is then used if uou want a way of adding the project and project headers automatically, based on the format set within settings on to all the lines rather than editing each line.

2.7. Renewal Prices & Sage Price Book Settings

Renewal Prices using Sage 200 Price Book Functionality

If as a company you prefer to use Sage 200 Standard Price Book functionality for controlling your contract selling prices you can on this tab select your current price book and what the price book to use up to a date, and after a date

You would need to maintain this ongoing and ensure you have new price books created annually in order to link the new price book and the Increase date annually

It only is beneficial the majority if not all service stock items set up for contracts are linked to a price book.

If you have a mixture of some service stock items that are linked to price book and some not, it could get confusing as to which ones you need to amend manually.

N.B. For further information and training on Sage 200 Price Book functionality please refer to your sage 20 help and user guide or discuss further with your sage 200 Business partner.

Current Price book: the price book that will be used to update renewal prices for contracts with a renewal date before the ‘Price Increase Date’ field.

Price Increase date/Renewal price book: any contracts with a renewal date after the ‘Price increase date’ will use the ‘Renewal price book’ when updating renewal prices.

In our example we have created two price bands one for 1^st January 2019 – 31^st December 2019 and for the next years pricing one for the period 1^st January 2020 – 31^st December 2020

Example Prices for Price Band effective 1^st January 2019 – 31^st December 2019

Example Prices for Price Band effective 1^st January 2020 – 31^st December 2020

These can then be used during the renewal process using the Sicon contract function ‘Update Renewal Prices’ routine and you have set contract pricing using price bands.

By renewing through the update renewal process you can renewal multiple contract lines in one process and depending on settings confirm all within this one process

Alternatively, you renew line by line by editing each contract line within the contract by selecting the renewal tab

If within settings you have set that on renewal the system shows the current price it will show as our example below (the current price before renewal)

By Selecting the ‘Update Renewal Price’ button the relevant price book price will pull through.

After checking other details on this tab, the user would tick renewal confirmed in order for the contract line to appear in the ‘Process Renewals’

2.8. Custom Fields Setup

Custom fields are a historical feature from when the module was first created, and when contract lines analysis codes or linking to sop analysis codes was not available. We recommend contract line analysis codes are used as standard as they are available within filters, list views and could be used in reporting.

But if you would like to use custom fields then you would first configure within this section and then on the Main Contract Settings Tab (screen shot below) ensure you have ticked the ‘Enable custom fields tab’ to ensure they are visible within the contract line

Custom Fields Set-Up

Custom Fields (configurable spare fields) are visible not only on the contract line, but on screen on the main contracts list, selecting the Contracts, Contract line details or Custom fields radio buttons.

It is possible to setup up to 5 text, 5 Number & 5 Date/Time custom fields and maintain a number of configurable text, numeric or date fields which are then against each contract Line on the custom tab

N.B. SpareDateTime, SpareNumber and SpareText fields 1 and 2 are reserved for system use.  It is not possible to configure the number of decimal places shown for ‘numeric’ spare fields.

N.B. Any reporting on custom fields would be custom, and creating drop down options to select from are not available unlike contract line analysis codes.

As well as being seen on the Main Contract List as with Sage 200 Standard, users can right mouse click on the screen/lines and ‘Send to Excel’, ‘Print’, or ‘Find’. The columns can be sorted, and moved around to suit users own requirements.

2.9. Contract Reconciliation / Sales Ledger Analysis Codes Settings

A very simple way of flagging which (if any) Sales ledger Account Analysis Codes will be visible within the contract reconciliation process / screen when selecting display on the Tab Customer and Products

When flagged the relevant sage 200 Sales Ledger Analysis codes will be shown in the Deferred Income by Customer and Product section at the bottom of screen

In our example we have selected / filtered by a single customer and hit display, if not single customer selected when selecting display all customers will show

Users can choose to send this information to Excel or Print by using the function ‘right mouse click and export ‘Selected’ Line’ or ‘All’

2.10. Contract Line Analysis Code Setup & Configuration

Sicon Contract Line analysis codes are different to standard Sage 200 SOP Analysis codes.

If SOP analysis are enabled on the main contract settings tab as seen on the screen shot below

The system will display an additional tab on a contract, that being SOP Analysis codes, as per our screen shot below

Which in turn gives you the ability to set and configure depending on the settings / defaults set when the sop analysis codes were crated within Sage 200 , of which currently there is up to 20

At a line level, using Sicon Contract Line Analysis where you can add up to 150 codes

The steps to configure are: –

Tick to enable; Enter a Label / Name; Tick if mandatory; Select whether it’s to be a free text field, Date field, Drop-Down, Numeric Value or a simple tick

When creating the contract line analysis fields within settings if you set the data type to be drop down your mange the list for users to select from by clicking on square …

The select Add, enter the options and click ok

When adding a contract line these analysis codes are selectable at line level,

If there are any mandatory analysis codes and where you forget to select when you save a line the one that is mandatory will be highlighted and a warning given

Sicon Contract Line Analysis can be used for filtering within various places within the module. Our example below is within Process Amendments,

But they are also available within: –

Process Renewals, Update Variable Billing Prices, Generate sales Orders and View Contracts

And also, on the Main Contact Maintenance Screen by selecting the radio button ‘Contract analysis codes’

And the list can be sent to excel, or print by using the function ‘Right Mouse Click’ and either Export or Print

2.11. Other Sections to review during Setup

Before the 150-contract line analysis code option was added to the module, (used to filter on various screens amongst reporting purposes), to enable companies to analysis contract and contract lines they would have used the options available within the maintenance menu item where there are options to set up Contract Types, Payment Types, visit frequencies, and who sold:

The top item within this section ‘Cancellation Codes’ – is one that needs populating with at least one reason for cancellation.

The others are rarely used by customers new to Sicon Contracts and from our experience are only used by a few original Sicon Contracts users.

However, it is still worth during reviewing the options during setup to see if they are of interest.

For more details, please visit the section of the help and user guide headed ‘Maintenance’.

3. Contracts Menu Structure

Within the Sicon Contracs module menu, based on users & role permissions you can:

• Import contracts & default settings for service stock item records in relation to contract settings; where there are deferred income/costs associated with the records imported/generated the deferred income transactions which are stored are then used to generate the monthly deferred routine.
• Import service stock settings, where the Sicon Contracts module has been added since stock was added, it is possible to add via .csv relevant settings on to the Sicon Contracts tab.
• Maintain new and update existing contracts.
• For those users who only need ‘view’ access to certain areas, there are several options within the enquiries menu option.
• Print customer contract renewal notices; this does not apply to where the line has been set as a rolling contract.
• Maintain cancellation and deletion reason codes; a minimum of one is required.
• Process any pre-notified contract line non renewals.
• Print a purchase order from within the Sicon Contracts module for the contract lines where supplier details and costs have been entered using the multiple supplier tab.  This feature does not integrate, link or post through to the Sage 200 Purchase Order Processing module.
• Manage deferred income.
• Month end routines and reconciliation.

4. Contract Maintenance Main Screen

When you first open the Contract Maintenance Screen, by default all Live contracts are visible.

The screen will show the currency symbol relating to the customer’s account currency, and the currency therefore used on the contract line. In the screen shot above, we have highlighted a contract that is in Canadian Dollars (CAD) and one that is in USD ($), the other 2 are sterling accounts that are variable billing lines; as such, these don’t show any values.

The ‘Net Before Discount Column’ is the ‘Line Unit Price’ before discount and is the currency value; in our example 150 CAD (Canadian dollars) and 9090.91 USD.

All other values are the companies base currency values; in our demo data £ (Sterling).

The exchange rate is a view from ‘Accounting System Manager’ and from within the ‘Currencies and Exchange Rates’ area of the module.

Filers are available to filter by;

• Customer: Contract Status (Live by default but can be changed to On Hold, Cancelled, Completed)
• Service Item Code or Name
• SOP or Contract Line Analysis codes

NB: If you apply a filter, this is shown to the side of the field with the words ‘Filter applied’. To remove all filters, click the ‘Clear Filters’ button.

Users can also choose on this screen to view by using the radio buttons which then list the contract lines, rather than top level.

Use the Radio buttons to show different detail:

• Contracts: (As above screen shot) showing the Contract Number, A/C Ref, Customer Name, Description, Status, Contract Totals (Net before discount, Total Discount, Total Net after Discount).
• Quantities: Will show the Quantity, Currency, Unit Price, Base Unit Price and Cost, No. Used – number of times used (number of times the contract line has had a SOP contract order generated from it), and no of invoices remaining (for example Annual contract, but invoiced per Quarter, 2 invoices invoiced, 2 left).
• Contract Line Details: Will show the Quantity, Pricing, Unit Cost, No. of times used, Customer Delivery/site address (Label of which is configurable within settings), no of invoices remaining, Contract Start Date (current contract period), End Date, Current Bill cover to: from dates, Invoice frequency, i.e. if invoicing annually this would display 12, if invoicing per Qtr this would show 3 and if invoicing monthly this would show 1. Also displayed would be any analysis codes attached to line, the Sicon Projects Job associated with the contract if linked (and if Sicon Projects is enabled), and any renewal or amendment details.
• Contract Analysis codes: Will show the Sicon Contracts Module Analysis codes associated with the contract line (as opposed the SOP analysis codes).
• Custom Fields:  Will show any custom fields (spare fields) assigned to the contract line. Custom fields can be either text, numbers, date & time, and there are 5 of each available and are configurable within configuration settings.
• Edit the Contract Selected to View (or edit)
• Description: Contract description for internal purposes only, such as Jim Murry’s Contract(s) – When there is one master contract for a customer with multiple lines.
• Status: Manual Status users can set to define the status of a contract and can be used on various list views – No automation process changes this status, and should not be confused with the contract line status.

• Customer Contact: For reference only; users can enter the contract point of contact.
• Customer Order Number: For reference only; users can enter the customers order number, but please remember this is the main contract information and if your customer issues different order numbers for each contract type/line, you should look to use contract line analysis codes to enter the customer order number as these could be pulled though to the contract line using variables for invoicing.
• Purchase Order Printed: When a contract line on the contract has had a PO printed (not to be confused with Sage 200 POP printing) this flag is ticked. NB: even if there are multiple lines on a contract at this time, it only takes one line to have had a PO printed to flag this; this feature will be enhanced and extended in future releases.
• Purchase Order Expiry Date: For reference only; users can enter an expiry date for the customer’s order number, but please remember this is the main contract information and if your customer issues different order numbers for each contract type/line, you should look to use contract line analysis codes to enter the customer order number expiry date as these could be pulled through to the contract line using variables for invoicing.
• Total invoiced to date/total remaining: Total value invoiced and total value remaining based on sales orders generated from this contract and remaining values to be invoiced.
• Sales Orders: Sales Orders generated from this contract will be listed and can be viewed.
• Orders Created from this contract: This section shows sales orders and sales returns generated from within the contract or from a sales order linked to the contract. Use ‘View Order’ to view the order/return. Where a one off credit, one off charge or an amendment has been generated, thus producing a SOP order or return, they will also be shown.
• View Deferred Postings: Select to view the deferred posting transactions associated to the order/return.

The details being displayed include:

• Deferred Transaction Line for the relevant month
• SOP Document Number
• Amount that has or will be deferred on that date
• The Posting Status ( Posted means the deferred routine has been run for that month, and the journal has been created)
• The URN allocated to that posting
• The Nominal codes used within the journal
• Deferred Ref ( Balance Sheet code debited for an order/credited if a sop return)
• P/L Ref ( P & L code credited for an order/debited if return)

If for some reason the journal was created as a recurring journal manually in the nominal by the finance team, not realising its automatic, users can create a ‘Reversal’ of the posted or yet to post transaction. Likewise, if a manual credit note has been raised against the contract and not linked correctly to the line, the transaction line can be adjusted by using the ‘Edit’ function.

Important Note : The transactions stored for deferred income/costs are stored and used in the ‘Contract Reconciliation’ and therefore it is important to try and ensure that all adjustments to contracts are done in the correct way and that no manual journals are posted to the nominal accounts within the nominal ledger; if they are there will be variances. Please refer to the Contract Reconciliation section for more information.

4.1. New to Sicon Contracts?

When new to Sicon Contracts, if you are adding contract lines already invoiced manually or within a different ERP system, you can add the lines with the current in cover contract start, end dates, bill cover from and to, but so the system does not suggest that period needs invoicing, you must tick ‘Current invoice already generated’. This means you can prepare for the next invoice out of Sicon Contracts in advance.

NB: until there has been at least one sales order raised from the contract line, the ‘Amend/Cancel Tab’ will not be visible to use on a line.

Due to the above it is also important to note that where you have invoiced for a service in a different ERP system, if you later need to credit that same invoice(s), you should raise a manual credit note within Sage 200 SOP returns.

If you are using Sicon Contracts to manage deferred income, you should post the manual SOP return to a nominal code, such as legacy contracts, to ensure there are no discrepancies within the reconciliation screens/process within the Sicon Contracts month end routine. If you do post any manual sales returns to a contract designated deferred balance sheet account, you will see variances.

4.1.1. Top Level Tabs

Tabs visible at this at top level are as follows:

• Details: This is the main contract summary as first entered when first adding the contract, along with a view of any sales orders raised previously on a contract.
• Attachments: An area when you can add attachments and after they have been added you can open or delete them. Attachments can only be added at contract header level, not line level. The location for attachments to be saved is specified within the configuration settings on the ‘Contract Settings Tab’. We recommend you follow both your IT’s and standard Sage 200 location rules regarding where attachments are stored, ensuring that the location is one that is backed up and is a network drive.
• Memo: A simple way off adding memos. This could be details of why the price has changed, for example at renewal, although on the memo tab there is a follow-up date, there is no reminder functionality.
• Default Payment Information: This is only visible when Sicon Debtor Management installed (for historic purposes and for those who are still using this module). Where it is, the customers default direct debit preferences will be displayed for the whole contract. Noting that, subject to permission, they can be changed at contract line/document level. For more information about the Direct Debit Integration which would help you manage customers direct debits please visit; https://www.sicon.co.uk/user-guide/enhancement-pack-help-and-user-guide/#4

4.1.2. Second Level of options – Contract line status count

• Live Lines: Live lines are active/in contract lines.
• Expired Lines: Contracts that the contract end date has past (the current date) and has not been renewed or cancelled.
• Deleted Lines: Lines that have been selected and the user has chosen to be removed. Care should be taken when doing this where there are outstanding invoices remaining and where deferred transactions are in use.
• Cancelled Lines: Lines that have either been flagged manually cancelled (on the contract flags tab) or via the amendment screen.
• Pending Lines: When service stock items that are flagged on the stock record/Sicon tab as being a contract item, and where they have been originally added to a sales order in SOP rather than added within the Sicon Contracts module, until the sales order is posted they are treated as a pending line . We class these as pending lines, because until the sales order is posted the sales order can be amended and/or cancelled. When the sales order is posted the status will change to Live and either (depending on settings, options being:
  • Always create a new contract regardless of whether one for that customer exists.
  • Always add a new line to a pre-existing contract for that customer if one exists; OR
  • Increment the Qty on an existing contract line , but only if the line is the:
    • Same service stock code
    • Same contract cover bill date from:to
    • Same unit price
    • same price interval
    • same duration in months
    • same invoice frequency
    • same Invoice interval
• Completed Non-Contract Lines: It is possible to add a service stock item line on to a contract that is not flagged as a contract item (a recurring contract item). For example, you have a service stock code for contract admin/Set up fee or Service Install, and when you sell a customer a contract you also charge them for installation or set up, which is treated as a one-off charge (non-recurring / a non-deferred type service).
  • When these types of lines are added on to a contract and once invoiced (they appear in the normal contract generate sales order process), they will then be treated as a ‘Completed Non-Contract lines.
• Variable Billing Lines: Where the type of Service you are providing on the contract is of a variable price nature (i.e. telephone charges which differ each month) you can choose to via the Sicon tab on the service stock record set as a variable item.
  • When these types of service are added to a contract line, you do not see the standard ‘bill cover from and to’ fields and are processed slightly different. For more details visit the ‘Variable Billing Contracts Menu Item’ of the Sicon Contracts help and user guide.
  • Against each of the contract line type will be a count of the number of contract lines (line count) applicable to that status.
  • By default, only live contract lines show when first opening this screen, to show others simple tick the relevant options.
• Suspended: Where you have flagged a contract line as suspended, by doing so flags them as ‘not to be renewed’ / Invoiced’ so this should be used with care.
• Amendments in Progress: Where on the renewal tab, or on the amend/cancel tab amendments or advance non renewals are in progress but not yet processed.

4.1.3. Third layer of details (tabs against the lines, when some have been added)

As the relevant tab is selected, line information will be shown, and/or used for certain actions when contract lines have been added but are as below:

NB: Depending on the size of your screen, you can use the scroll bar at the bottom of the form to see additional information not visible in the initial view when opening the form.

• Summary: A summary view of all the lines, showing only live contract lines by default when opening this form.
• Amend/Cancel: The tab to access where you need to record in advance a non-renewal or make other changes to the Quantities / process / or add a one of credit or one of invoice.
• Renewal: The tab to access when you wish to renew the contract on a line by line basis as an alternative method to ‘Update Renewal Prices’ on mass via the contract processing menu option.
• Cancellation: The tab to view the cancellation code and cancellation date assigned to previously cancelled lines.
  • Where contract lines have been left to simply expire, users can from this tab select the line and use the drops downs on the code/date fields to select the relevant details
  • For the full process of amendments, Renewals and cancellations please visit the ‘Contract Processing’ element of the help and user guide.
• SOP Analysis Codes: If enabled, within utilities and configurations settings and on the Contract Settings Tab, under Option Features as well as assigning a Sicon Contract Line analysis code (of which it’s possible to have 150) to a contract line, you can also link the line to a Sage 200 Standard SOP analysis code. Using SOP Analysis codes could be useful for filtering within SOP and standard SOP reporting.
• Deferred Nominals: Use with caution – See important note: As part the of module set up, and when managing deferred income, the relevant nominal codes to be used when a) posting the sales order  b) when running the month end monthly journal process in the contract module moving values from the balance sheet to the P & L are initially configured at either stock product group or service stock item level. They are not visible on the contract line and users do not need to re-enter as during the month end journal process which move values from the balance sheet to the P & L the module looks at the defaults set on the maintenance contract tab on either the product group or the service stock item.
  • However if for a particular contract line (s) , during the month end journal process you wish the movement to come from a different balance sheet nominal and/or a different P & L code (See Note) , and if the feature ‘enable the deferred nominal tab on a contract line’ has been enabled  you could use to change it at line level.
    • Important note: At line level you cannot change the nominal code for which the sales order value will initially be posted to, this will still be taken from the service stock item and on the Sage analysis tab and the revenue nominal code. It’s only the nominal codes to be used during the contract month end journal routine that can be changed at line level.
  • As an example, if the original sales order is posted to balance sheet code 19101 and the service item on the maintenance contract tab has been set to debit 19101 and credit 39999, during the month end journal process if at line level you change both the B/S deferred nominal and P/L deferred nominal, after the SOP is posted you will be looking at a contract reconciliation variance between accounts, (because you would during the month end journal process potentially be taking the monthly value out of a balance sheet account that the value was posted to originally). As such, we recommend that this feature is only used to change which P & L revenue code that would be used during the monthly month end journal process, unless for some reason, you do not use the reconciliation function within the Sicon Contract module, and you are not worried that you are posting the original income to one balance sheet account, but during the month end journal routine it takes it from another.
  • This setting is not recommended where multiple users are using the contracts module and where you do not wish for any changes to what nominal codes are to be used over and above those set as defaults on the stock product groups and/or at the service stock item level.
• Payment Information: only visible when Sicon Debtor Management installed, configured and in use. Where it is, the customers default direct debit preferences will be displayed for the whole contract. Noting that subject to permission they can be changed at contract line / document level.
  • For more information about the managing Direct debits, please visit https://www.sicon.co.uk/product/sicon-debtor-management/
• Cover Types: this is only visible when Sicon Service is installed. Where it is service, cover types can set at contract line level so when a service call is logged within Sicon Service the service admin team can see what cover type the customer has (for example gold, response with 4hrs, silver response with 2hrs, Ad-Hoc – no response time guaranteed). For more information, please visit Sicon Service.

4.2. Adding a New Contract

Select Contract Maintenance from the side menu, click on new (bottom left hand side of the form) and tab through populating the relevant required information as explained below:

If Sicon Debtor Management is installed, and if this is the first time a contract has been added for a customer then you will see a message as below.

Explaining that the payment information (for direct debit collection) will be taken from the customer’s account and stored against each line of the contract. For more details on Direct Debit management, please visit https://www.sicon.co.uk/user-guide/enhancement-pack-help-and-user-guide/#8-4

• Customer Contact: For reference only; users can enter the contract point of contact.
• Customer Order Number: For reference only; users can enter the customer’s order number, but please remember this is the main contract information and if your customer issues different order numbers for each contract type/line, you should look to use contract line analysis codes to enter the customer order number as these could be pulled through to the contract line using variables for invoicing.
• Purchase Order Printed: When a contract line on the contract has had a PO printed (not to be confused with Sage 200 POP printing) this flag is ticked – NB: even if there are multiple lines on a contract at this time it only takes one line to have had a PO printed to flag this; this feature will be enhanced and extended in future releases.
• Purchase Order Expiry Date: For reference only; users can enter an expiry date for the customer’s order number, but please remember this is the main contract information and if your customer issues different order numbers for each contract type/line , you should look to use contract line analysis codes to enter the customer order number expiry date as these could be pulled through to the contract line using variables for invoicing.

• Customer Order Number: This is where you would, if applicable, enter your customers purchase order number. If entering here, it applies to the whole contract (meaning if you are adding multiple lines for the one contract and the same PO number applies).
  • If you are adding multiple lines on one PO and the customers PO number is different for each line, you would use one of the 150 Sicon Analysis Codes that are available on each contract line.
  • On the renewal tab against each contract line renewal, PO numbers can also be added where the customer issues different PO numbers for each renewal. This number (because it is on each line) does not populate the front screen.
• Purchase Order Printed:  Within the module there is a very basic method against a contract line to raise a back to back purchase order relating to a contract line (where you are supplying a service, but then backing it off to a 3^rd party), then used this tick box will be ticked. It’s for internal reference only and only recommended where one supplier is involved with supplying the service for the while contract.
• Total Invoiced to date: This is only populated after the first sales order for this contract has been raised and is a simple visual of values of a contract Invoiced to date for the in-contract period of the line/all lines and Total Remaining is a visual of what’s remaining to be invoiced for the in-contract period of the line/all lines on the contract.
  • For example; you have an Annual Contract £1200 but they are paying monthly and you have invoice 2 months. Total Invoiced to date would show £200
• Total remaining: In our example above, if annual contract £120, to date we have raised sales orders for £200 the total remaining would be £1000.

NB: Values shown are net/before vat.

On Saving the Contract the system generated contract number will be displayed (If auto numbering is enabled within settings).

If auto numbering is not enabled/not ticked.

When a user adds a contract and saves a contract they will be prompted to enter their own unique contract number.

During implementation companies should consider the best practice as to whether they are going to use auto generated numbering or not.

If not, they should ensure consistency/agree a best practice for an agreed numbering/alpha number/alpha system so when looking at the main contract maintenance list they will appear in the order that you want them to appear, this is handy for reporting and when sending data to excel.

• Status: By default, contracts when added are set to a status of Live. Only live contracts are included in any processing’s for generating sales orders.
  • If a sales order has been raised and a deferred transaction is captured, they will still be included within the monthly journal routine process. This is simply because the original transaction would have been posted to the nominal and to ensure contract reconciliation is correct the journal process needs to happen. If you do not wish for deferred transactions to happen on a particular raised sales order/with linked not posted deferred transactions, then you will need to adjust the open deferred transactions for that / those relevant sales order (s). For more details on this please visit section 6.6 Adjusting Deferred Transactions.
  • By default, when looking at the contract maintenance list only live contracts are display.
• Contract Statuses: The main contract header status could be changed to internally flag the whole contract is on hold, completed, ending ,this contract header status is different to the contract line status which drives the behaviour of the contract generation.

Once contracts have been processed through to sales orders, the linked sales orders against a contract on the main contract header summary as shown below are visible within ‘orders created from this contract’ and you can choose to view each sales order and drill down on to the sales order lines.

This view shows all sales orders on the whole contract.

The reasons column shows the user where the transaction was processed.

Contract Amendment: An amendment has been made and processed through to SOP from the amendment tab on the contract line.

This could be a Sales Order/Contract Amendment where the amendment is a positive value/additional charge is raised against the line on the amendment tab or a Sales Return where a negative/credit has been raised against the contract line via the amend/cancel tab. The Amend/Cancel Tab on a line is only visible when at least one sales order has been generated from the contact line. 

Generated from Contract: A contract and thereafter a sales order was processed starting off from within the Contracts Module or having been originally added on to a sales order, and once the sales order has been saved, depending on settings either a new contract or new contract line has been saved

Generated from Contract at Renewal: A contract renewal has been processed

Select a transaction, and select ‘View Order’ to drill down to the relevant sales order or sales return raised.

The view deferred postings button as our screen shot above is useful if you wish to see any deferred transactions against one of the sales orders, to review the status of the deferred element.  Users can also see what nominal codes have been captured and will be or have been used during the monthly journal routine.

When an order is selected and the view Deferred Postings button is selected, users will either see the status as showing as:

• Not Posted: The journal for that month for that relevant transactions have not occurred; OR
• Posted Status: The journal has happened as part of the ‘Period End Routine: Monthly Journal Posting for Contracts’ – Where this status applies the relevant nominal URN is also visible

Where the company is not using deferred transactions within any of their contracts and posting direct to the P & L, then they will if clicking this option ‘view deferred postings’ they would not not see any transactions to be deferred.

This view shows all orders raised against the contract.

If, as a company, you have multiple lines on a single contract and you are looking for orders/deferred transactions raised against a particular contract line, you can gain the same visibility at a line level.

Select your contract from the main contract maintenance list, select the lines tab, select the relevant contract line and select ‘Sales Orders and deferred Trans.’ button. This view is just looking at sales orders and any deferred transactions previously raised and/or generated from this individual line.

NB: The Amendments Tab within the screen shot below has now been renamed Amend/Cancel.

4.2.1. Adding a New Contract Line

Select Lines Tab and Select Add.

The fields that require populating are explained in detail below, noting that some of them are mandatory dependent on other selections:

• Code: Enter or search for the Sage 200 service stock item that has been created to pull through on the contract.
  • In our example above, we have a service stock item for an annual contract to service a coffee machine.
  • The item had (during implementation) been flagged as a Sicon maintenance item on the Sicon tab on the stock code set up and been flagged as a deferred transaction item.
  • Important Note: If the service stock item is not flagged as being a contract item, you can add it to a contract line and invoice it, but it will be once invoiced once it will be deemed as a non-contract item and will be flagged as a ‘non-contract line, and no longer available for invoicing against.
• Name: This field pulled through from the service stock record. If the stock item is flagged as using a full Item description this is shown underneath the name for reference.
• Warehouse: Can be defaulted within Contract Configuration Settings on the contract line settings tab. This is handy if your service stock items for contracts are created against a ‘contracts warehouse’ Sage standard stock functionality is even though they are not proper stock items, you have to assign a warehouse, which is why we recommend a sage stock warehouse is set up for ‘Contracts’.
• Site: The address for which the service is being provided under this contract. Only really relevant if the contract is being invoiced to a head office/or another company*, and the service to another address and where you want to capture this information.
  • *An example of this is that we at Sicon (who uses the module heavily) have one contract for each business partner, and each line is for a different end user of our software, so our settings, during implementation were configured so that we:
    • We did not enable ‘automatically create a default delivery address’
    • We enabled ‘delivery address is compulsory’
    • On every line, we enter first time for a BP’s end user we create a new delivery address by clicking on the Site Search Icon as below.

• • • When clicking ok, you have the option as setting as the default address.
    • In our case we wouldn’t because each line is for a different end user.
    • On our screen shot it shows as ‘Site’ this is because within our contract line settings (as seen below) we have set our ‘Delivery Address caption’ as ‘Site’.

• • • You can set the system to ensure the ‘delivery address on a contract line is compulsory’
    • You can also choose within settings to set the delivery address based on the customer’s account.
    • For more details on set up and configuration ahead of using Sicon Contracts module please visit (prior to the implementation stage) Sicon Contract Pre-Requisite’s.
• Internal Description: This additional text field / box to enter additional information which can be used for internal reference/purpose only.
  • It is possible using the ‘Insert Variable’ function to show internal descriptions on any sales order / invoice raised.
• Sales Order Description: As explained within the Sicon Contract Pre Requisites, it is possible to set default contract Order Line descriptions against a product group and on an individual service stock item.
  • If defaults are set the description will pull through into the ‘Sales Order Line Description Box’ on to the contract line saving the users time not having to enter a description with dates on.
  • If no default descriptions are created then when the service stock code is select the sales order description box will be blank. If left blank on the invoice only the Stock name will be displayed.
  • In our example above our service stock item is linked to the product group ‘Service Contracts’ and on our product group for ‘Service Contracts’ we had set a default as below:

• • We used the insert variable function to pull through the relevant bill cover from: to dates as set on the lines, and they will increment every time a sales order is raised.
  • Using ‘Insert Variables’ in this way means that users do not have to change dates before they raise new sales orders.

• • Insert variables can be added at product group, service stock item level or at contract line level.

Important Notes

Since release 19.2 (end Nov 2019) we introduced additional fields on this screen, it is important for users to understand about the following relationships between certain fields and the implications of using:

• Unit Price and how it relates to Price Interval
• Invoice Frequency and how it relates to Invoice Interval
• And how all fields work in connection with each other

Unit Price: You need to enter the Unit Price Quoted per ‘Price Interval’

Within the modules configurations Settings, on the contract line settings you can set defaults for all the following fields:

Price Interval: Duration in months; Invoice Frequency & Invoice Interval.

If the customer wanted to pay quarterly, you would enter 3 in the Invoice Frequency.

Once the user is happy with the details entered select save (Bottom left hand of the form).

Thereafter when ready to, users would then generate the sales order through the sub menu item ‘Generate Sales orders’ under the menu option ‘Contract Processing’.

Some companies run this routine daily, others weekly or monthly or on an ad-hoc basis when they need to add a new contract and raise the sales order/invoice.

When selected and when the user enters the date for which they wish the system to search or contract lines that are due to be invoiced.

Overdue contract orders due for invoicing prior to the date entered will show in red invoices.

You could choose to filter by date and various other options as seen at the top of the screen.

By default, when opening the screen all lines are selected, but users can deselect all, select all, or if they want to check out the contact select a line and select ‘Contract details’ which in turn would open the contract.

When ready to push the order through to sales orders for invoicing select ‘Process Selected Contracts and Generate Sales Orders)

When processed confirmation will be shown as below:

Before this process is run, as explained within the Sicon Contracts pre-requisites within standard Sage SOP Utilities – System Setup – User Permissions, those users using the contract module MUST have at least Override Prices, Override Cost Prices set to yes.

If this has not been configured the message displayed instead of the one above will be one that warns that the users’ permissions have not been set.

Using the Days and weeks functionality

Users must be aware of how a contract overall value will / could change one (if) they use the days and weeks functions

If using days as there are a different number of days in certain months, and where you (if you) choose to price based on a daily rate, but invoice monthly – your monthly invoice values will be different throughout the year

Likewise, if you choose to price based on a week, but invoiced monthly – then because some months have 5 weeks, throughout the year there will be different monthly invoice value.

If your prices do not vary based on number of days in a month or weeks in a month / year then we recommend you only use months and years.

And on the front Contract screen the values are as below, rounded to 2 decimal places.

Other fields available when adding a contract Line:

• Current Invoice already generated: Entering contracts into the module ready for the next renewal because you are new to Sicon Contracts, and for the current period they have been invoiced on another system. In which case you could make use of the ‘Invoice Already Generated’ tick box/function.
  • In our example below, the customers contract started 01/05/2019 was for 2 years (24 months) and we invoiced for those 2 years on another system prior to using Sicon contracts.

• • We entered the original start date, and that it was a 24-month contract, the system calculated the end date of 30/04/2021.
  • We ticked the ‘Current invoice already generated function. This flags / then knows that the current period 01/05/2019 to 30/04/2021 does not need billing from the Sicon Module and that the next period of cover that would be invoiced for is 01/05/2021 to 30/04/2023, and the sales order will be ready for processing through ‘generate sales orders’ on 01/05/2021.
• Rolling Contract Function: Use on a line where you are not looking to increase the prices and therefore you do not want to go through the process of renewing the line, because process never change.
  • In our example below we entered a start date 01/20/2019 and its for £120 per year, invoiced once per year (so Invoice frequency 1 and Invoice Interval of years, although I could have selected invoice frequency 12 and invoice interval months as both combinations result in the same).
  • Rolling Contract is ticked and as a result the contract end date field is blank because there is no end date, because the contract is rolling.

• • The system will generate a sales order for the period 01/10/2019 to30/09/2020 for £120, and because we have enabled rolling, it will generate the period after 01/10/2020 to 30/09/2021 without having to go through a renewal process.
  • If you were adding a contract on when new to Sicon Contracts, you could also use the ‘Current Invoice already generated’ in conjunction with the Rolling Contract Function.

Notes on Rolling Contract Lines

On the main contract screen where we show the contract values the value shown will be for the contract period billed (current bill cover from:to).

Rolling contract lines will never appear in the ‘Update Renewal Prices’ process because for reasons above they are not lines that need renewing.

To see a list of Rolling contract Lines from the Main Contract Maintenance Screen, select the Contract Lines details radio button and you will see a Rolling Column with an indicator not the relevant rolling lines. The columns in this view/screen are sortable so you can group the rolling lines together and could highlight those rolling lines, right mouse, and send ‘selected’ to excel for example.

• Pro Rata dates: Use where you want to enter a contract for a full year’s period, with a full year’s price, but for whatever reason you are pro rating the price for the first year.
  • In our example below, we have entered a contract for £1200 per year, duration 12 months starting 01/04/2019 ending 31/03/2020.
  • But we are only wanting to bill them from 01/10/2019 to 31/3/2020 as we have as an example given them the first 6 months free (but normally and at renewal next year it will be a full year).
  • To accommodate this, use the Pro rata function and enter the date for which within the complete contract period we wish to start billing them from.
  • In our case 01/10/2019. You will see that the current bill covers from: to changes to that 6-month period and the bill cover duration and value of next invoice and next sales order due date reflect this pro rata from date.

• • When the contract period has been billed in full and expires, upon renewal it will revert back to the default £1200 with a full year’s cover.
  • If you are not seeing fields such as rolling or Trial on a line its likely because within Utilities on the Contract Settings tab, it had been disabled. so please contact your internal system administrator
• Other fields on the ‘add new line screen/form’
  
  Unit Cost: A method to manage deferred costs on a contract line. Depending on whether you are using method 1 or method 2 for deferred costs, will depend on whether the unit cost field is visible on the contract line.
  • For a full explanation and a user guide for managing supplier costs associated with a contract line please refer to Contract Line Cost of Sale / Supplier Costs.
• Bill xx months in advance: If when using the ‘Generate Sales Orders’ process and you are required to enter a date in the ‘show orders due before’, and where you prefer to bill in advance and want to put what date you plan to invoice, rather than the actual bill cover from date.

• • To further explain, our contract below has been entered with a start date of 01/09/2019, and the current bill cover from reflects this as does the Next Sales Order due date.
  • On this line I have not set any ‘bill in advance months’.

• • When I generate sales orders, to see this contract line I enter 01/09/2019.

• • If however on the contract line, we set the bill in advance to 2 months in advance the next sales order date is 01/07/2019 which is the 2 months ahead of the bill cover from date (hence the setting bill 2 months in advance).

• • And to see this contract for sales order generation within the generate sales order process I would need to enter 01/07/2019.

• • There is no right or wrong method, and no advantage of using the ‘Bill in advance’ it is purely down to the company’s preference as to what they are going to use when they use the generate sales order process.
  • If you do not use the Bill in Advance function, you simply need to remember that you need to enter the bill cover from date in to the ‘Show orders due before’ date field.
  • However, if as company you decide to use the function ‘Bill in Advance’ then we recommend you do it on all lines to avoid confusion.
• View Changes Button: Only visible if the Sicon Audit Log module is installed. If installed Audit log records any changes made to the contract line. For more details, please refer to Sicon Audit Log 

4.3. Creating a Contract via Sage 200 Sales Order Processing (SOP) Module

This option is good for those who would prefer to add a new contract line on to a sales order at the same time as selling their customer some goods; for example selling them a washing machine, which is a standard stock item and selling them a service contract to go with that washing machine, where it will then be a recurring service contact and you would like the system to generate you a contract line.

If using SOP standard quotes to quote a customer for a contract line, and you then convert the quote to a sales orders, you will need to go into the order and populate the contract additional fields; Sicon Contracts does not integrate with SOP Quotes.

When you add a service stock item that is flagged as a maintenance contract item, the screen dynamcally changes and loads the Contract detals and CLAnalysis codes (and Service if installed).

On the details tab all fields except the quantity will be greyed out, and you will need to click on Contract details on the left-hand side.

It is on the Contract details form that you enter the relevant contract details, the unit price, the price interval (for example as our screen shot above £1200 is the annual price so the unit price is £1200 and the price internal is = years.

If you are using Sage Price Book in conjunction with this service stock code/customer, then the unit price will come through as standard.

There is an ‘amend description’ option on the top right hand corner of the form, if selected any default text/variables configure at product group or within contract settings or on the service stock item will put through. In our example, at product group level we had set a description of ‘Service Contract Bill cover from: to’ and used variables to pull through the dates automatically based on dates entered onto the sales order line.

You can add some text within this box if you would like to add some additional information for this sales order/invoice.

If Sicon Projects is installed and set to integrate, you will need to on the Details tab select the relevant project and project header.

If any contract line analysis codes are set as mandatory within contract settings and you forget to enter them, you will be prompted to when saving the line and those that are mandatory are highlighted.

If within contract settings on the contract line settings tab, the ‘delivery address is flagged as being compulsory (as per screen shot below).

If on the contract details tab you forget to select you will be prompted to when saving the sales order line.

When selecting a delivery address you can either select the default one or create a new one of the fly.

When all the contract details have been entered and the sales order is saved it shows as a standard sales order on the standard SOP list view.

As far as integration with the Sicon Contracts module is concerned, it would have been determined during set up as to how the module will handle contract lines that are added on to a sales order rather than from within the Sicon Contracts module itself.

Within Settings, at product group level or within Sicon Contracts settings, you will see options to specify whether to (on saving the sales order) the system should;

• always create a new contract for the customer (regardless of whether there is an existing contract for the sop customer); OR
• When updating contracts from SOP, look for an existing contract for the customer, but always create a new contract line.

If neither are ticked, then the system will look to match the customer, the service stock item, the price and the bill cover from: to dates and if all matches at the point of the sales order is posted an existing line qty will be incremented.

In all cases, when a contract/contract line is added directly onto a sales order within SOP, until the sales order is posted it is treated as a pending.

If neither of the options above are ticked , or just the 2^nd option is ticked (look for an existing contract for the customer, but always create a new contract line), the pending line can be seen within the customer’s existing live contract by selecting the pending Radio button within the contract.

If the top option is selected, (always create a new contract) then initially when the sales order is saved a separate pending contract will be created starting with the number 999 and can be visible on the contract list view over main contract screen selecting the contract status = Pending. Once the sales order is posted a new contract with the final contract number will be created.

If neither options are enabled, and there is no existing contract, if you create a new sales order for a customer that DOES NOT have an existing contract and where you add more than 1 contract line on to that new sales order, when you save the sales order for each contract line on that sales order you will see separate pending contracts.

Important Note: When you post the sales order for the new contract customer, you will see separate contracts. This is because when line 1 is added onto a Sales Order there is no existing contract and when additional lines are added there is still no existing contract, this is because until you post the sales order, the lines are pending. 

If its important to you that there is only one contract, then you should consider your starting point to creating the contract first within the Sicon Contracts module itself rather than sales orders, thus adding all the contract lines within one contract and generating through to sales orders and then adding any additional items such as stock.

Alternatively, you could add a new sales order for a new contract customer, just adding one contract line, print and post so a contract does exist, create a 2^nd sales order so there is an existing contract and the lines will add to the existing contract. The recommended route would be to start within the contract adding the multiple lines, as that way you will get one single sales order/invoice.

From within Sicon Contracts, to see what contracts/which contract lines are pending you can use the contract status ‘pending’ either within the contract’s maintenance view.

OR within a contact itself on the lines tab selecting Pending Lines.

Within Sicon Contracts, on the contract itself on the Details view/tab you can see which sales were derived from a sales order being added with SOP as opposed to being generated from a contract.

If a user cancels a sales order with a contract line on it before its posted, any references within contracts of that pending contract/will be removed.

4.4. Contract View / Contract Line View

When opening a contract and viewing the contract Lines, by default ONLY Live contract lines will show and the Live contract lines status filter ticked.

Other available statuses are:

• Expired contract Lines – Contract lines that have expired.
• Deleted Lines – Lines that have been Removed from the contract.
• Cancelled Lines – Lines that have had a credit raised against the line/contract line cancelled and a reason flag status recorded.
• Pending Contract lines – Contract Lines that have been added initially via a Sales order, and where the sales order has not yet been posted and therefore the contract not 100% confirmed as such.
• Completed non contract lines – Service Stock Items that have been added on t the contract, but are not flagged as a Maintenance Contract Item, on the Maintenance Contract Tab on the stock Record.
  • It is possible to have this type of service stock item onto a contract, but it’s not treated as a recurring line and once invoiced, it will be flagged with a status of a ‘Complete non contract line’.

4.5. Rolling - Never Expiring Contracts

Where a contract line is flagged as ‘Rolling’s as per the screen shots below, the dates on the contract automatically increment and the contract will appear in the Generate Sales Orders process automatically without any renewal process/action.

Caution should be taken when considering whether to use this function.

We do not recommend using unless you know that your pricing never increases and the company’s policy is one that they don’t review contract pricing.

It is very easy to renew contracts (even if no price increase), using the update renewal process (using a 0% increase if there are no price changes).

If you do decide to use this function, you do not have to use them on all contract lines or all contracts, so if you do have the situation where you do have some contracts that will never have an increase, this would be the method to use.

If created originally by adding a contract item via a SOP sales order, when viewing you will note that there is no contract end date and it shows as a rolling contact with the duration showing as ‘Indefinite’.

When adding directly from within the Sicon Contracts module, the rolling function is underneath the contract start date.

When a start date is added and then the rolling tick box ticked, then the Contract end date field is blank.

Remember … rolling contract lines will appear in any renewal process or any renewal reminder reports.

4.6. Custom Invoicing Profile

Where a contract invoicing frequency cannot be set as monthly, quarterly, annually, every xx months, we have added the ability to have a custom invoice frequency profile.

Example Scenario

A Contract that officially runs Sep – Aug for a 2-year period, then is renewed.

However the Customer will only accept invoices within each financial year.

So for the contract example of Sep16 to Aug 18 (24 months) – Total Value £2400 plus VAT.

By using the custom invoicing profile our 2-year contract will have (within a 2-year period) just 3 invoices raised each covering the periods.

• 01/09/2016 to 31/3/2017   – 7 Months @ £ 700
• 01/04/2017 to 31/3/2018 –  12 Months @ £ 1200
• 01/04/2018 to 31/8/2019 – 5 Months @ £ 500

4.6.1. How to create a line with a custom Invoicing profile

NB: this can ONLY be done from within Sicon Contracts.

On the line itself there is a Custom invoicing profile tick box;

When selected the fields / sections not relevant will be greyed out, and as you tab through the No. of Invoices Remaining will not display any dates , but instead the text ‘ Custom Invoicing Profile’.

Use the ‘Planned Sales Orders’ Tab to enter the invoicing profile (when you need the sales orders to be generated).

If you attempt to save the line without adding, you will be warned.

4.6.2. Planned Sales Orders Process

Using Add, enter each of the planned/required sales order details, as below and Save.

If you attempt to add more than you should (past the contract required dates/value) you will warned.

Once you are happy with the planned sales order lines, click Save.

If you have any analysis codes set to mandatory you will be required to set them at this point.

If this is a new contract, and the line is the first on the contract you will see the contract number displayed.

If you are adding a line to an existing contract the screen will close taking you back to the Summary screen showing the line(s).

And also the relevant dates, the period of first planned sales order, and in the Invoice Frequency Column the indication that the line is one with a ‘Custom Invoicing Profile’.

The next step will be generating through to sales order processing, using the ‘Generate Sales Orders’ within ‘Contract Processing’.

Enter the date that you wish the system to list those contracts that require sales orders generating thereafter invoicing, in this example we have entered 31/06/2016. The list can be filtered using various analysis codes, or by customer, invoice frequency, contract number or contract type (Contract Type can be set up within Maintenance).

Overdue contract lines will be shown as red with a message

The Sales order would then be invoiced, posted and contract updated as standard.

The Sales order will then be visible from within contracts as standard from either the Main Contract Screen and the ‘Orders created from this Contract Pane as below.

Or from the contract line itself, selecting View Details.

And on the Planned Sales Order Tab, users can see the sales order numbers against each planned sales order line if generated.

When Viewing the Line after the first planned sales order has been raised users can see when the next planned sales order is due.

When all the planned sales orders have been raised, the planned sales order tabs will show all relevant sales orders, with no more showing TBC.

Users can also click on a line and View the sales order.

Because all planned sales orders have been raised then on the Summary screen there will be no ‘next sales order date’.

After all Planned Sales orders have been raised / The Contract invoicing has ended the options thereafter will be to;

Either leave to expire naturally if not renewing and if required set a reason flag.

If the renewal is going to result in another custom invoicing profile, then the renewal should be done from the line, by initially entering the details on the renewal tab (example below).

Once Saved you will see the following message.

After Clicking OK users need to go back on to the line and the planned sales orders tab and enter the new planned sales order details for the second year

If the renewal is going to result in a standard invoice frequency i.e., every month, every xx months then because the contract in effect has changed (invoice frequency changed) then because of restrictions, by the pure nature the line was ‘custom’, you will  need to to leave the ‘custom invoicing profile line to expire’ and add a standard contract line , this time, not ticking custom invoicing profile and entering a contract start / end dates, current bill cover to:/end dates etc as you would normally.

• It may be in the future we can allow swapping types, but at this time we can’t.
• You can use the one of credit, one off charge as you would normally.
• You can use the amendment tab to cancel the contract and credit all or some of the previously raised planned sales orders.
• Again because of restrictions by the pure nature its custom at this time you cannot increase / decrease qty’s.

4.7. Process an Amendment or Cancel on a Contract Line

On a contract line where at least one sales order has been raised, this functionality can be used to process an amendment or flag a contract line as being cancelled.

Important notes about the functionality on the Amend/Cancel Tab

• In previous versions, this tab was called ‘Amendment’.
• This tab is ONLY visible on a live contract line when at least one sales order has been generated from the contract line, and the invoice is printed/posted.
• The tab will only appear after there has been at least one sales order generated from the contact line.
• If you have entered a contract line, but not yet generated through to sales orders, any amendments would be needed to be done on the line itself before processing.
• If you are new to Sicon Contracts and you are adding lines in preparation for the renewal where previous invoices have been generated manually or on another system, if you have added a new contract line and you need to raise a credit for the current period (prior to expiry) this should be done as a manual transaction within SOP.  It can’t be done on a contract line where no orders have been generated from.
• If you have added contract lines within SOP on to a sales order (as opposed to starting it off within Sicon Contracts) until the sales order has been posted the line is a pending contract line, adjustments cannot be made on pending lines.
• If you have added a sales order/contract line which has become a pending contract, you would use the sales order amend order status to cancel the order and invoice if printed and adjust within the sales order.
• Depending on which option users select (they can only choose 1) the user will be able to perform certain tasks. Each option has a blue information icon which when selected will explain the function to the user.
• The tab will only appear after there has been at least one sales order generated from the contact line (this has been the case for several years).
• Initially the form looks blank at the bottom of the form, but when a user selects a function, addition fields populate that are relevant to that selection for futher information to be entered into the system.

In the example below, we had invoiced a qty of 2 but it should have only been 1, and we not only needed to adjust the qty going forward but also raise a credit note for the extra once invoiced.

On the amend/cancel tab we specified the adjustment qty, selected the sales order we wanted to part credit and the system confirmed a sales return/credit of £1200 would be set.

When we are then ready to push that amendment through to SOP to raise and send the credi,t we would use the Process Amendment menu item, filter by customer (if we want to), select display, select the relevant transaction and select process.

The system will confirm that the amendment has been processed through to SOP for generating.

The non-renewing option is new and works in conjunction with those contract lines that have a contract end date set, not Rolling contracts, which are never ending/have no expiry date.

This function allows users to in advance specify that the contract line is not renewing either at the end of the contract end date or prior to if for some reason the customer has decided to cancel early.

When Non-renewing is selected the user will be able to:

• Select from the pre-configured list of cancellation reason codes (the reason why the customer is cancelling), this is a useful piece of information which appears after the date has past not only on the cancellation tab within a contract, but also within the menu item screen enquiries>cancelled contracts, both of which can be useful for reporting via the form using right mouse click, send to excel.
• Set a notification date (the date in which the customer advised they are cancelling), this defaults to the current date, but can be changed.
• Set an Effective cancellation date: This defaults to the contract line contract end date, but can be changed to earlier; for example if the customer has gone into administration earlier than the contract line contract end date.
  • If the effective cancellation date is different to the current contract line contract end date, we would advise you consider on the contract line changing the contract end date to the same as the effective cancelled date, the duration in months / invoice frequency. This is not mandatory, but please consider when sending data to excel from contract line views that you may be relying on the contract end date for reporting, and where using Sicon Contracts in conjunction with other Sicon Modules you may want the dates to be the new contract not renewing/cancelled from date rather than the original proposed contract end date.
  • There is also a notes box for you to enter a summary of the reason. If left empty, upon saving the system will ask you to confirm that you wish to leave the reason blank. The written contents are stored in the database and could be used on custom reports, as such we recommend you enter a summary for referring to later/custom reporting.
  • Up until the effective cancellation date the contract line will have a status of live.
• This ‘Non-Renewal’ Process should be used in conjunction with the New ‘Process Non-Renewals/cancellations ‘which can be accessed from within Contract Processing.

• • This process should be performed on a regular basis, some may want to perform daily, weekly, or monthly or even more frequently, as this process is used to set the contract line status to ‘cancelled’ at the given date based on the set ‘Effective Cancellation Date’.  The frequency would very much depend on whether you have a process where you only allow whole months for contracts, so any effective cancellations would take effect on the 1^st of a month, or whether you have contract dates.
  • If users do not run this routine and simply on the amend/cancel tab set the contract line as ‘Not Renewing’, at the effective cancellation date the line will go to ‘Expired Status’.
  • We have introduced these two new functions to allow users to specify the contract line is not going to renew at the set effective cancellation date in advance, and not to then have to set a task to go into the contract line and set the contract flag as cancelled on the effective cancellation date. For Sicon Contracts users who have hundreds if not thousands of contract lines often with lots of cancellations in a month, having this new two-step process will help.
  • It is important to note that once the second step has run and the contract line status is set to ‘cancelled’, the fields on the amend/cancel tab will be greyed out but the information will still be visible, so users can retrospectively see the various bits of information.
  • As such, if the customer wishes to re-instate the contract then a new line would need to be entered. Previously you would have been able to untick the cancelled flag and change the dates/duration and frequency on the line, but from an audit perspective this could lead to issues and confusion.
  • If the user has selected the incorrect cancellation code and needs to change it, then if the ‘use contract list view’ is enabled within Settings, the user could (against the contract line) using the drop down in the grid view change the reason.
  • We recommend this to be ticked especially for large volume of contract lines, as the system would be recalculating/refreshing each line upon save and where there are a contract has lots of lines then this could cause performance/speed issues, but for small volume contract lines, and for those companies who prefer to use the grid method it is an option.

Other Notes about options on this form:

• The functionality behind the other options remains the same as previous versions with the exception that if you select ‘Contract Line Quantity Increase’ you cannot enter a negative figure, i.e. if your contract line has a current quantity of 2 and you wish to increase to 4 you would enter 2 in the box.
• If you want to decrease the Qty from 2 to 1, then you would select ‘Contract Line Quantity Decrease ‘and enter 1 in the box, not as you would in previous versions where you would enter -1.
• In both scenarios you will see the ‘Quantity after adjustment ‘field to make it clear what the final Quantity will be before you commit to the change.
• Cancel and Credit Previous Sales Order: This function allows you to set a notification date, select a cancellation reason, set an effective cancellation date, enter a summary and select a previous sales order(s) to credit and raise a sales return. Once the Sales Return has been processed through to Sales Order Processing the system will reset the Contract start and end dates as well as the current bill cover from: to dates to what they were before the latest sales order that you are crediting.
  • One off Credit and One-off Charge functionality has not changed from previous versions.
• Suspended Contracts functionality has not changed from previous versions.
  Tick for example there is you wish to suspend billing  that being  if you want to flag the contract as being suspended, if ticked a free text box for entering a reason why appears.

• • Contract Lines were Suspended Flag is ticked will not allow generation of ‘Sales Orders’.
• Price Amendment: Where you need to enter a new unit price (in years) and available is a new field to enter a New Unit Cost (in years).
  • For customers actively using the Multiple Supplier Costs functionality on a contract line you would not see the unit cost field on the New Unit cost field.

4.8. Sales Order Paid Status

Visible ONLY to sites where Sicon Enhancement Pack is installed and the feature SOP 034 is enabled ‘Show if SOP Invoice/Order’ has been paid as screen shot below.

Previously, if users wanted to see if the sales order raised from the contract line had been paid they would need to click through on the sales order tab, select the sales order, select ‘View Order’, find the invoice number, close Sicon Contracts and go into the sales ledger account.

That process has been made much simpler by still selecting the line and the ‘Select Orders and Deferred Trans.’ option where the users will see a new Paid Status Column, and either a status of Paid or Unpaid.

5. Supplier Costs Relating to a Contract Line

For further advice on deferred costs and the associated nominal codes please refer to section 1 of this help and user guide Contract Pre-Requisites

Where required users can record any supplier costs, they expect to incur from a third party.

You can choose to simply record the cost for referencing and reporting purposes or to go one step further flag the service stock item as a deferred cost type transaction.

Alternatively if you enter the supplier costs on to the multiple supplier tab via the contract line you can go even further and after the authorised suppliers invoice has been entered on to the suppliers purchase ledger using standard sage 200 functionality choose to allocate the suppliers invoice to the relevant contract line.

The allocation set is mandatory if you are planning to treat the costs as deferred , this is because it’s at the point of allocating the authorised suppliers invoice to the line on the multiple supplier cost tab that the deferred contract cost value is captured in preparation to be used as part of the period end monthly journal postings for contracts routine.

You can allocate a single supplier invoice to multiple contract lines either on a single contract or across multiple contract lines for the same supplier.

Where you choose to enter the cost on the line itself if the service stock item has been set as a deferred item then during the period end monthly journal postings for contracts, the value entered in the unit cost field of the line will be used (Using the same method for calculation as the revenue line) and you would not need to use the allocate supplier costs process.

If your cost is not flagged as a deferred item, you can still choose to allocate the suppliers invoice to the multiple supplier cost line, but it would be for reference only and no deferred transaction will occur.

5.1. Where to enter the supplier cost?

The first of two possible places is on the line itself within the unit cost field as shown below

This cost field on the contract line is not linked to the cost price on the stock item and is a unique field for Sicon contracts.

Alternatively, where you would like to record more than simply a figure / the cost value you should enter the relevant details on to the multiple supplier costs tab.

If you choose this second method, the unit cost field on the line itself will not be available.

You can have a mixture whereby some lines on your contract that you enter the cost on the line itself, and others where you use the multiple supplier costs tab, but it is important to ensure all users are aware of the different methods are being used as it could get confusing in later processes.

5.2. Non Deferred Cost item field on Contract Line

If using the unit cost field simply to record a cost, but you are not looking to manage the cost as a deferred item then on the services stock itself you would leave the create monthly journal postings from deferred costs unticked.

If you do wish to treat the cost as a deferred cost you would tick the create monthly journal postings from deferred costs , enter the relevant profit and loss and balance sheet codes which are used during the monthly journal posting routine nominal code and post the supplier invoice when receiving it to the balance sheet deferred code rather than the profit and loss

Important Note: Please refer to section 1.3 of this help and user guide , section Managing Deferred Income and/or Costs before using the cost field / multiple supplier costs from a nominal code perspective as there are set up requirements which need to be understood and actioned.

5.3. Deferred Cost item field on Contract Line

If you enter the unit cost on to the line itself and the services stock item is flagged as a deferred item (as per our screen shot below), the deferred transaction cost value is captured when the sales order is posted and the movement from balance sheet to P & L then occurs during the standard contract, period end, monthly journal routine.

The nominal codes used within the journal are specified either as a default on the stock product group, or on the service stock item as per the screen shot below.

For further advice on deferred nominal codes see Contract Pre-Requisites

5.4. Entering Details on the Multiple Supplier Tab

Important Note: This feature does not integrate with Sage 200 Purchase Order Processing (POP)

Use this method where you wish to record more than a single cost value, where you wish to allocate supplier invoices to the contract lines, where you need to manage any differences between the expected cost and the actual supplier invoice cost and if you need to send the supplier a purchase order.

Despite the tab being called multiple supplier costs, for the reasons above you can still use these methods where there is only a single supplier.

Supplier Line Currency: When adding a supplier to the multiple supplier tab the currency will be set to that of the supplier, the currency symbol along with other relevant information will be visible once saved.

Dates: The supplier dates are not linked to the main customer contract line, and could be different, although in most cases it’s unlikely.

When adding the supplier cost details you would first select the supplier code, the period of cover your suppliers contract to you covers the cost for that total period, the expected invoice frequency and the expected invoice interval.

In our example below on the first line we entered we entered £120 to cover the period 01/01/2024 to 31/12/2024, and said we were expecting a monthly invoice and so entered 1 for the invoice Frequency = 1 set the interval months to monthly result being we expected 12 monthly invoices of £10 per month.

Once later in the process the supplier’s invoice has been entered and allocated the fields on this form, are greyed out and cannot be amended.

5.5. Print Suppliers Purchase Order

Not a mandatory step and only possible where the supplier costs have been entered via the multiple supplier tab

Reminder: This feature does not integrate with Sage 200 Purchase Order Processing (POP)

Under the menu option Contract Printing Menu select Print Purchase Orders.

Using the report criteria options select your contract and contract line, if you only have a single supplier, you will print the given purchase order.

If you have multiple lines for one contract line (even if they are the same supplier) and where the dates from: to are different they will print as separate purchase orders.

If you have multiple supplier lines, all for the same supplier with all the same dates the system will print one purchase order with multiple lines.

Typically, you would only print the purchase order from contracts, if the supplier requires a purchase order to be sent and you have not already added the purchase order into Sage POP.

5.6. Allocating Suppliers invoice Costs

5.6.1. Pre-Requisite to Allocation

Prior to allocating the suppliers invoice against the contract line (on the multiple supplier tab) you must ensure the supplier’s invoice has been added on to the suppliers account and where your system is configured to ‘require authorisation’ that it has been authorised.

You should also ensure that where the invoice relates to items that are flagged as deferred items that the invoice has been coded/posted post to the balance sheet deferred costs nominal code and not to the profit and loss. This is because the deferred cost element is fed through to the relevant profit and loss account (as configured on the service stock record/Sicon tab) during the monthly journal routine, so if you did code the suppliers invoice direct to the P & L you will see after running the monthly journal routine overstated P & L costs.

Where Sicon Projects is also installed when entering the supplier’s invoice for a deferred item (posting to the balance sheet) and selecting a project you will see the message [ The nominal selected on row xx is a balance sheet code.  Are you sure you want to post this to the project?] our example screen shot below.

You would in this instance select yes, as you do need the invoice posted to our deferred balance sheet code for the deferred element. If the suppliers invoice includes items that are not to be deferred, you would need to enter separate lines.

You wouldn’t see this message if you selected the N/A Project.

For further advice on deferred nominal codes see Contract Pre-Requisites.

5.6.2. Process of Allocating Supplier Invoice

After the supplier’s invoice has been received and entered on to the supplier’s account, select Allocate Supplier Costs menu item from within the contract processing section of the contract’s menu structure (step 1).

When the form opens select the Supplier (step 2), hit display (step 3), or if you prefer to filter the list user the 2^nd reference field on the suppliers’ details section or on the planned supplier costs section (bottom half of the screen) or filter by either sop analysis codes or contract line analysis codes on the bottom half of the screen.

If the suppliers invoice matches your expected cost, you would select the supplier invoice from the top half of the screen (step 4) select the supplier cost line from the bottom half of the screen (step 5) enter the amount to allocate (double click will also populate), select allocate (step 6).

After selecting allocate you will be asked to confirm (step 7)

At this point if the supplier cost was relating to a deferred item the system would capture the value which will be used when creating your monthly journal postings and both the suppliers invoice line and the suppliers cost line will no longer appear in this screen.

View Contract from this Screen:  Just above the allocate button (bottom left) you will see a view contract button; this allows the user to select a supplier cost line at the bottom half of this screen and view the contract line in full.

We do not allow changes to be made on the contract line within the contract via this route, If whilst viewing the contract via the allocate screen you spot mistakes on the contract you would close the allocate process and amend the contract as normal.

Suppliers Invoice Value Different? Where the invoice value is different, but correct (and it was the cost on the supplier tab that was incorrect) users can choose to ‘update the cost for this planned supplier cost line to the amount to allocate entered.

In our example, we had expected the cost to be £100 (step 2), the invoice came in at £10 (step 1), we changed the amount to allocate to £10 (step 3), it prompted us to update the cost for this planned supplier cost line to the amount to allocate entered (step 4).

The system will prompt you with the message where the invoice is greater or lower.

Finished allocating but there is a remaining un-allocated balance on the supplier’s invoice?

The supplier’s invoice may not 100% be for services provided in relation to the multiple supplier contract line. In this instance where, after the user has finished allocating the contract cost element, you will see a difference on the supplier’s invoice between the value and allocated.

In our example above the supplier’s invoice was £620, we had allocated £240 and the difference £380 does not relate to any other contract line.

To clear the supplier’s transaction off the list (only this list not any ledgers) so it does not appear in this process going forward you would select the line you wish to clear, select remove selected Invoice (step 2) and confirm (step 3).

Once the supplier cost has been removed there is no way to retrieve it back within this process so it should be used with care.

Removed in error and the contract cost is a deferred item? As it’s at the point of allocation where Sicon contracts captures any deferred transactions if a user has removed the selected invoice in error, then to create the future deferred postings, within the contract line itself, subject to user permissions you would edit (step 5) the deferred transaction against the line on the multiple supplier tab as the example below.

5.6.3. Renew Supplier Contract Lines

Only applicable where you have entered your supplier costs via the multiple supplier tab against a contract Line.

Where you have renewed your customers contract, and where supplier costs still apply for the renewal periods you should use the process renew supplier contract lines.

Select the date that you wish to see the supplier lines due for renewal prior to the date.

Select the relevant supplier lines and by processing the ‘Selected Renewals’ the supplier dates will advance on.

6. Contract Processing

From within this section, you can: –

• Generate contract lines through to sop that are due for invoicing (based on next sales order due date).
• Process through to sop any amendments you have made on the amend/cancel tab on a contract line.
• Update prices on mass and run the renewal process.
• Update variable contract line prices.
• Run the post Invoice update which is a function which needs to be run (if after the SOP post routine within SOP fails, or the user was not set to perform that function as standard).
• Renew supplier costs (where applicable and if relevant / if set on the line on the multiple supplier tab).
• Allocate supplier costs to a suppliers invoice (at which point if deferred costs are in use generate the cost for later use in the monthly journal routine ).
• Process any non-renewals / cancellations which in turn flags the status of the line from live to cancelled.

6.1. Process an Amendment

Use process amendments to push through any amendments you had made on a contract line to SOP for processing either an invoice or a credit note.

An example would be where you have renewed a contract line, it was invoiced to the customer, you are then notified they have gone into administration and you need to cancel and raise a credit note or where you invoiced too much or invoiced a qty of 2 instead of 1 as per our screen shot below.

To correct on the amend/cancel tab we specified the adjustment qty, selected the sales order we wanted to part credit and the system confirmed a sales return/credit of £1200 would be set.

To send the customer a credit note use the process amendment option as our screen shot below, filter by customer if we want to select display, select the relevant transaction and select process

The system will confirm that the amendment has been processed through to SOP for generating

6.2. Renewals – Setting Defaults

The first of two ways to renew a contract line is from within the contract, by editing the relevant line and selecting the renewal tab

Setting up the renewal defaults before using the module are further explained within the help and user guide section labelled ‘Contract Renewal Settings & Defaults’

If no defaults are set and/or ‘use existing’ enabled then during the renewal process the user will need to enter as the renewal values displayed as they will be £0, blank or 0%

6.2.1. Renewing Contracts – At Line Level

The first of two ways to renew a contract line is from within the contract, by editing the relevant line and selecting the renewal tab

When using this method and if configured in settings to do so on the line renewals tab the current contract price will show, change if renewal price needs to increase or decrease or choose update pricing by selecting to ‘update using price book value’ ( for further details on sage standard price book please refer to the sage 200 help and user guide or speak with your sage 200 business partner).

If configured to do so in settings the current period duration in months and invoice frequency will display change if necessary for the renewing period.

Choose to, if relevant enter a discount %, if entered the renewal unit discount value field will be populated, alternatively if you enter a renewal unit discount value, the renewal unit discount % will be populated.

Once you are ready to confirm the renewal tick the renewal confirmed tick box noting that if you forget to tick the renewal confirmed tick box, the system will not display the contract line for renewal in the later stage of the renewal process at being ‘Process Renewals’

6.2.2. Process Renewals by line next step

When you have finished going through the relevant individual lines to confirm renewals, the next step is to select from the contract processing menu, ‘Process Renewals’

When the process renewals screen opens, as seen below:

In our example our contract is next due for renewal on the 01/01/2025, having expired on the 31/12/2024 and on the contract line itself we had left the ‘bill in advance field as 0 months’.

In our example below we chose to show renewals due prior to 01/01/2025 for a single account and selected ‘display’.

To select the line (s) the user can select individually or select all, or to clear unselect all

From this form also by selecting a single contract line the user could choose to view the contract

If required to check some details if required before selecting the ‘process selected renewals and generate sales orders.

Note: If on the line we were using the bill in advance function, and we had it set to bill 2 months in advance.

On the process renewals screen you would enter a date 2 months on from the renewal 31/03/2025 which in this case equals 2 months ahead of the renewal date of 31/01/2025.

If you use the bill in advance function, no contract dates are affected, it’s simply a user’s / company’s preference as to what date they use /enter when using the process renewals screen.

If you have multiple lines for renewal for a single customer by selecting all after processing the selected lines for the same customer will be consolidated on to a single sales order, if you need separate sales orders for the customer you will need to carefully select the lines you need to be on a single sales order and process separately.

Once happy to process the renewals though to sales orders tick individually as required or select all and then then Process Selected Renewals and Generate Sales Order.

You will be prompted to enter a date which will go through as the sales order header date, once processed you will see a visual confirmation that the sales orders generated and will appear within the standard sage 200 sales order list.

Once the renewal is within sales order processing. The line is set as confirmation not required by the contracts module so there will be no requirement to pick/confirm or despatch. To invoice you would use the standard sop invoice process as you do others

Important Note:  Whilst the renewal invoice is within sales order processing, and before it has been posted through to the sales ledger, it cannot be amended from within SOP, f if you spot a mistake once it’s in SOP and you need to correct something i.e. the pricing, duration or dates you would need to use the standard  sage standard ‘amend order status functionality, as per our screen shot below

Once the order has been selected to be cancelled the system will warn you that because the order is related to a contract the line will be reversed back to how it was before you processed the renewal, you would then amend the contract line / the details on the renewal tab and process through again

If the order has been generated through to sales order processing correctly it will be linked to the contract line and visible by clicking on the relevant sales order, within the orders created from this contract view

Until the sales order is posted the order status will be Live, and if managing deferred income until the sales order is posted there will be no deferred transactions captured

Once the sales order is posted the status changes to complete and were managing deferred income by selecting the order or the line from within the contract itself, you can ‘view deferred postings’

It’s worth noting that even if using sicon contracts you generate separate sales orders, depending on standard sage 200 sales ledger settings, if within standard sage 200 sop it’s still possible to consolidate multiple sales orders for a customer on to one invoice depending on settings on the customer’s account on the document tab.

6.3. Renewal Process Multiple Contract Lines

The second way to manage and process contract renewals and by far the best way if you have lots of contract lines to manage so you are not having to edit each contract line individually is to use Update Renewal Prices

The purpose of using this method is to allow you to update/confirm, and renew on mass, in one screen by either enter renewal prices within a grid form, filter the update multiple contract lines by either SOP, customer or sicon contract Line analysis codes, use price bands or apply a % increase and based on a setting within contract utilities; configuration settings and on the renewals, tab as shown below.

If enabled, within utilities, settings and on the renewals tab then the ‘allow confirming renewals while updating renewal prices’ button / function will appear on the update renewal prices screen allowing the user to ‘confirm renewal for all lines and an extra column as shown below

The function is a quick way of confirming the lines you have either increased, or simply reviewed and left the same as the current contract price, and after processing sets the ‘renewal confirmed flag on the contract line renewal tab as ticked, thus allowing the generation of the contract renewal order through to sales orders for invoicing

Without the setting enabled on the renewal tab within configuration settings, the update renewal prices screen will display as below, no extra column for flagging lines as renewal confirmed, and no button to confirm for all lines flagged for renewal and the user will need to confirm at line level

If the setting is not enabled, you can still use this screen to filter / calculate an increase based on a price book or a % increase, but you would then need to on each individual contract line, access the renewal tab, and confirm renewal

Some companies like this 2-step approach, as it may be one user within the companies prepares what the renewals will look like after applying a price band increase / % increase or manually by using ‘update renewal prices’, in our example we selected just one line to increase, manually entered a renewal price, ticked the left-hand column tick box

and then on this screen select process at which time the user will see a message that the ‘Update Prices is complete’;

but it’s another user’s responsibility to print the reminders

and once the customers confirm renewal the user goes into the individual line, on the renewal tab and ticked confirm

In order for the renewal contract invoice to be generated through ‘process renewals which in turn pushes the contract renewal transaction through to sop or invoicing

If however, it is one sage 200 user that primarily manages all the contract renewals, then using the ‘update prices with the setting ‘Allow confirming of renewals while updating prices does save a lot of time.

If you different types of contracts, for example hardware contracts, remote only support contracts and onsite inc. contracts and you have separate sage 200 users each looking after a type of contract , you would to save time use the update renewal process but each user would filter the screen (use filter by contract line analysis codes) to show only their area’s contracts.

6.3.1. Update Renewal Prices using Sage 200 Price Book

One method to apply increases is to make use of the standard sage 200 price book, this would work well if you have set prices that change each year

Sage 200 price book functionality is standard Sage 200, for assistance on how to create a price book please refer to your business partner for advice or the Sage 200 help files within the programme itself

Once set up you will need to set

Your current price book (in our example Apr 22 – to Mar23)

The date that that current price book expires (in our example 01/04/2023)

And select which price book to refer to thereafter (in our example SUP Apr23 to Mar24)

In our example using sage 200 standard price book functionality we had created three different price lists and gave them the names price books up Apr 22 – to Mar23 and SUP Apr23 to Mar24 and SUP Apr24 to Mar25

In contract settings we set the contract module to currently use the prices set in price book Apr 22 – to Mar23, but set it that any contracts due for renewal from 01/04/2023 would use the prices set within price book SUP Apr23 to Mar24

Once 1^st April 2023 has passed, I would need to

Change / set my ‘current price book’ to be SUP Apr23 to Mar24

Change the date in the Price Increase date to be 01/04/2024

And select the next renewal price book which would be SUP Apr24 to Mar25

When ready to update renewal prices using the price book: –

From within the Contract Processing menu option select Update Renewal Prices

Step 1. Once the form opens the first thing is to do is enter the two in between dates you are looking to work with

If needed, you can filter by sop, customer or contract lines analysis codes if you wish to, it may be different contract manager user look after different regions which are associated to an analysis code.

Step 2. After you have entered the relevant dates, select ‘use price bands’

Step 3. Then select ‘Calculate Renewal Prices’

The system will then look for all the contract lines relevant and assign the relevant renewal price (s) associated with the price book configured to be used

The renewal price will be displayed in the column New Renewal Price

If necessary, the user can click in the field in the new renewal price column on a line and change if for this one line it was going to be different

Step 4. Once happy with the renewal prices you would in the contract number’ column either tick individually, or if happy with all lines, select all

Step 5. If you are ready to confirm all lines are ready for generating through to sales orders (via the process renewals function) and you have the feature enabled, you would then use the button ‘Confirm Renewals for All Lines’

If you do not have the ‘confirm renewals for all lines button’, they will need confirming on the contract lines themselves as explained previously within section.

Step 6. Select Process, after which you will see confirmation that the lines have been updated and are now ready for processing through to sales orders via the contract’s menu Contract Processing \ Process Renewals

Note: If no price books are configured / set up within contract settings the price book option on this screen will be greyed out.

6.3.2. Update Renewal Prices using a % Increase

From within the Contract Processing menu option select update renewal prices

Step 1. Once the form opens the first thing is to do is enter the two in between dates you are looking to work with

If needed, you can filter by sop, customer or contract lines analysis codes if you wish to, it may be different contract manager user look after different contract types or regions which are associated to a contract line analysis code.

Step 2. After you have entered the relevant dates, select ‘Increase by % option, and enter your desired increase %, in our example we have entered 5% I

Step 3. Then select ‘Calculate Renewal Prices’

The system will then look for all the contract lines relevant to contract end between dates as entered, and increase by the set %

The renewal price will be displayed in the column New Renewal Price

Alternative use of the ‘Increase by %’ Option

If you are not increasing any prices for the contracts for the selected dates, but you wanted a quick way to renew your contracts on mass at 0% increase rather than go into each line you would use the same process as explained above, using the Increase by % option but simply leave the ‘Increase by% at 0%

If necessary, the user can click in the field in the new renewal price column on a line and change if for this one line it was going to be different.

Step 4. Once happy with the renewal prices you would in the contract number column either tick individually, or if happy with all lines, select all

Step 5. If you are ready to confirm all lines are ready for generating through to sales orders (via the process renewals function) and you have the feature enabled, you would then use the button ‘Confirm Renewals for All Lines’

If you do not have the ‘confirm renewals for all lines button’, they will need confirming on the contract lines themselves as explained previously within this section

Step 6. Select Process, after which you will see confirmation that the lines have been updated and are now ready for processing through to sales orders via the contract’s menu Contract Processing \ Process Renewals.

6.4. Variable Billing Process

Variable Billing is for contract lines where the amount varies each invoice, for example electric metre readings.

Where required to be used, on the Service stock item enable the ‘Use Variable Billing Box, if ticked the maintenance contract tick box at the top of this form is greyed out (and vice versa).

Variable item lines are treated different and do not require a bill cover from / to dates  or a start/ed date to be entered on the contract line and as such are treated as a non-maintenance item is the same way as a service item not flagged as maintenance item, but the difference being is that the system will not remove a variable contract line after being invoiced once (where as a standard service non contract item line will be removed/flagged as non-contract item) once invoiced.

Important Notes

1. It’s important and we recommend you use the Insert Variable function (either on the product group or the service stock item itself because there is no bill cover to date fields populated from the contract).By selecting the %%date:NextDateOfVariableBilling%% The system will add this date in to the sales order description field on the contract line every time, so the customer knows what date is being billed up to.
2. The Variables are different to those used for standard maintenance contract items, so whether you are adding default variables on the variable product group, the service stock item itself or on the contract line / sales order line description be careful you pick up the correct ones.
3. We recommend you have a different product group / service stock item(s) for variable lines, to allow you to configure default contract Line descriptions to save entering this manually on every contract line. The variables required for showing the relevant billing date is a different variable to a normal contract item, as shown below.

You may also want to consider different nominal codes for the revenue costs. As these orders are more likely to be billed after the event you would probably not be deferring these types of contracts and therefore you would want to post the revenue direct to a profit and loss income nominal account rather than a balance sheet deferred income nominal account.

Once the ‘Use Variable billing’ box is enabled, when adding a new contract line, because the item has been flagged as a variable item, you only enter the quantity.

The annual unit price should be left £0.

No dates are required and therefore are greyed out.

Enter other details as you would a normal contract line (You may want to consider using one of the sop analysis codes or Sicon contract line analysis codes to mark the line as a variable).

6.4.1. Invoicing

When you know the variable amount to bill, to process the line through to a standard sales order for invoicing select the ‘Update Variable Billing Prices’ within the Contract Processing Menu.

Select display to show all the variable contract lines.

You can filter by Product Group, Stock Code or Customer – leaving these fields blank will search for all the variable contract lines.

Enter the Bill Date, that you wish to record that you are billing up to i.e. electricity usage up to xx/xx/xx.

Enter the Billing Net Total (Next Invoice Unit Price).

Select the lines to and select process after which the screen will display ‘Update Process Complete’.

Note: You are able to import Variable Billing Prices, click the Import Template to generate 2 Excel spreadsheets the screenshot below shows the Example file, the other one is the one to populate and save as a CSV file for importing.

The next step is to generate sales orders using the ‘Generate Sales Orders’ within ‘Contract Processing’.

Enter the date to list the contracts that require sales orders generating and then invoices. In this example we have entered 25/06/2019. The list can be filtered using various analysis codes, or by customer, invoice frequency, contract number or contract type (Contract Type can be set up within Maintenance).

Overdue contract lines will be shown as red with a message.

Variable billing lines are shown in green.

Select All, or manually tick the lines to generate the sales orders for.

Click Process Selected Contracts and Generate Sales Order.

Select a Date from the Date Selection screen, this is to allow you to be able to select a specific date for the orders to be generated on as opposed to defaulting to today’s date.

The Sales order will then be visible from within contracts, on the relevant contract tab.

6.4.2. Next Invoicing Period

Follow the steps above, no need to go into the contract again, no need to renew and it’s only when you want to mark the variable billing line as cancelled and set cancellation flags, change any other details that you need to go into the contract line again.

6.5. Generate Contract through to SOP

Use this function to raise the invoice for the ‘first Invoice’ of a contract just added, a contract line is marked as ‘rolling’ or a variable billing contract line

Enter the date that you wish the system to list those contracts that require invoicing, in this example we have entered 31/06/2016. The list can be filtered using various analysis codes, or by customer, invoice frequency, contract number or contract type (Contract Type can be set up within Maintenance).

Overdue contract lines will be shown as red with a message.

Click Display to get the list of contracts due before the date entered.

Tick the relevant contract or select all and select process selected contracts and generate sales orders.

Something not looking right on this screen, by ticking a contract and clicking contract details it would take you through to the contract screen if you wanted to check any details on the line before generating

Once they have been posted through to SOP, they will disappear from the list, and you can either choose more or close

Once the contract is through to the SOP module, standard Sage 200 processes apply

Noting that the order is posted through to the customers ledger from SOP, the contract is not updated fully, and where the line(s) include service stock items flagged as a deferred item they are not be written to the deferred table until the sales order/return is posted) this is because until orders are posted completed) they can be amended.

When using the generate sales order process, and you enter your chosen date, if there are sales orders that were due before that date, you will be warned with a message in red ‘ Lines in red are overdue’ , and as it says , line in red are those that should have been generated before now (as per screen shot example below).

Important Note: If there are lines in red, and you then process them, you may find that when using this process next, they may appear again but for the next period which means if you have missed 3 months of monthly invoices it will not generate 1 sales order for 3 months , because your invoice frequency is set to 1 (monthly) you will need to generate the 3 missing sales orders separately.

6.5.1. Need to Correct a contract line after generating?

Once you have generated a sales order from sicon contracts, we lock down the fields with the sales order, and therefore any amendments need to be done back in the contract/contract line itself if it’s a case of you have noticed you had entered the wrong price or dates etc.

You should NOT cancel and/or remove the lines from the sales order, as this method does not update the contract/contract line correctly.

If the sales order is not posted, the first step us to use the Sage standard amend order status to cancel the sales order.

The system will warn you that the sales order is related to a contract and that by continuing to cancel the sales order will revert the contract to back to how it was before you originally generated the sales order, reversing the billing dates.

If happy click OK. Once the transaction has been reversed (no postings made) you can go back into sicon contracts, on to the contract line and make the amendments you needed to and generate the sales order again.

If the sales order has been posted you will need to from within the contract and the contract line, use the amend/cancel tab to cancel the sales order, raise a contract sales order return.

For more details on raising a credit via the amend/cancel tab please refer to the section ‘Process Amendments’ on the help and user guide.

If the Sales Order Value is correct and it’s just dates you need to amend:

If the value of the sales order is correct, but you have agreed to change the dates with the customer, for example the start date was too early, or you have agreed to offer 15 months for the price of 12 months for the first year, because the original contact sales order was partially incorrect we would recommend from an audit perspective that that is credited and a new line added.

This method (crediting and re-invoicing) is more important if you are using deferred transactions because when the sales order would have been posted, deferred transactions would have been captured and movements to the P & L via the month end journal process would commence at an incorrect date and would be visible viewing the deferred transactions against the contract lie

If you do decide to edit the dates on the deferred transactions, do it with care, if you by mistake delete a line, not noticing it, and save, then automatically within contract reconciliation you will have a variance.

To edit unposted deferred transactions dates, you would select ‘Edit Transactions’ and change each line.

If the status is posted (meaning the journal has already happened as part of a month end routine) we really would recommend that you consider crediting the original sales order, which in turn creates credit deferred transactions and you then add the contract line again.

You could raise a manual journal within the nominal ledger for the months already journaled and use the same process as above, editing the deferred transaction, changing the dates as above, and for those months that have a status of posted, change status unposted, this is not our recommended route, but it can be done, and would recommend you are confident with this option by trying in a test company to make sure you are happy with the process and the results.

6.6. Process Non-Renewals / Cancellations

This New ‘Non-Renewal’ Process’  enables users to complete the final step of a contract line cancellation / non-renewal as described in detail within Process an Amendment or Cancel.

This process should be performed on a regular basis, some may want to perform daily, weekly, or monthly or even more frequently, as this process is used to set the contract line status to ‘cancelled’ at the given date based on the set ‘effective cancellation date’.

The frequency would very much depend on whether you have a process where you only allow whole months for contracts so any effective cancellations would take effect on the 1^st of a month, or whether you have contract dates.

If users do not run this routine, and simply on the amend/cancel tab set the contract line as ‘not renewing’ then the line will at the effective cancellation date go will show a status of expired.

This process was added to allow users in advance to specify the contract line is not going to renew at the set effective cancellation date , and not to then have to set a task to go into the contract line and set the contract flag as cancelled on the effective cancellation date and for contract users who have hundreds if not thousands of contract lines often with lots of cancellations in a month then having this new two-step process will help.

It is important to note that once the second step has run and the contract line status is set to ‘cancelled’ then the fields on the amend/cancel tab will be greyed out but the information still visible so users retrospectively can see the various bits of information.

As such if the customer then wishes to re-instate the contract, then you would need to enter a new line. Previously you would have been able to untick the cancelled flag and change the dates / duration and frequency on the line but from an audit perspective this could lead to issues and confusion.

If the user has selected the incorrect cancellation code and needs to change it, then if the ‘use contract list view’ is enabled within settings then the user could against the contract line using the drop down in the grid view change the reason.

We recommend this to be ticked especially for large volume of contract lines, as the system would be recalculating/refreshing each line upon save and where there are a contract has lots of lines then this could cause performance / speed issues, but for small volume contract lines, and for those companies who prefer to use the grid method it is an option.

Other Notes about options on this form:

The functionality behind the other options remains the same as previous versions with the exception that if you select contract line quantity increase’ you cannot enter a negative figure i.e. if your contract line has a current quantity of 2 and you wish to increase to 4 you would enter 2 in the box

If you want to decrease the qty from 2 to 1, then you would select ‘contract line quantity decrease ‘and enter 1 in the box, not as you would in previous versions where you would enter -1.

In both scenarios you will see the ‘quantity after adjustment ‘field to make it clear what the final quantity will be before you commit to the change.

Cancel and Credit Previous Sales Order:
This function allows you to set a notification date, select a cancellation reason, set an effective cancellation date, enter a summary, and select a previous sales order (s) to credit and raise a sales return. Once the sales return has been processed through to sales order processing the system will reset the contract start and end dates as well as the current bill cover from: to dates to what they were before the latest sales order that you are crediting.

One off credit and one-off charge: functionality has not changed from previous versions.

Price Amendment:
Where you need to enter a new unit price (in years) and available is a new field to enter a new unit cost (in years).  For customers actively using the multiple supplier costs functionality on a contract line you would not see the unit cost field on the new unit cost field.

6.7. Enquiries

View Contracts
An enquiry screen of contracts and contract lines with no permission to edit, ideal for users that are allowed to look at contracts but not amend

Contract Invoices Not Paid
Visible ONLY to sites where Sicon Enhancement Pack is installed and the feature SOP 034 is enabled Show if SOP Invoice / Order has been paid as screen shot below.

Previously if users wanted to see if the sales order raised from the contract line had been paid they would need to click through on the sales order tab, select the sales order, select ‘View Order’ , find the invoice number, close contract manager and go into the sales ledger account.

That process has been made much simpler by still selecting the line and the ‘Select Orders and Deferred Trans’ option where the users will see a new Paid Status Column, and either a status of Paid or Unpaid.

6.7.1. View Contracts

An enquiry screen of contracts and contract lines with no permission to edit, ideal for users that are allowed to look at contracts but not amend.

6.7.2. Contract Invoices Not Paid

Visible ONLY to sites where Sicon Enhancement Pack is installed, and the feature SOP 034 is enabled Show if SOP Invoice / Order has been paid as screen shot below.

Previously if users wanted to see if the sales order raised from the contract line had been paid they would need to click through on the sales order tab, select the sales order, select ‘View Order’, find the invoice number, close contract manager and go into the sales ledger account.

That process has been made much simpler by still selecting the line and the ‘Select Orders and Deferred Trans’ option where the users will see a new Paid Status Column, and either a status of Paid or Unpaid.

6.7.3. Expired Contracts

Expired Contracts
By selecting Expired Contracts users can review contracts lines that have expired naturally but where no reason code thereafter entered.

Users may add the reason why (by selecting the line and selecting the reason from the drop-down list available as screen shot below) not only from a visual aspect within a contract, but where they have written custom reports for expired / cancelled contracts they may want to ensure there are always reason codes entered, but also then the true status of the line will be reflected that being cancelled (and therefore acknowledged) as opposed to simply expired.

It’s important to note that simply by adding a reason codes the contract line is not cancelled/further invoicing will be suspended.

6.7.4. Suspended Contracts

An enquiry screen of contract lines that are flagged as suspended (A tick box on the amend cancel tab on the line).

Users can select to filter which lines are flagged as suspended by using the criteria fields at the top, if all left blank then all lines flagged as suspended will be displayed.

If the user has permission to do so from this screen the user can edit the contract to view, edit and if required remove the suspended flag.

6.7.5. Contracts on Trial

An Enquiry screen where users can see those contract lines that are flagged as Trial (A tick box on the line).

Users can select to filter which lines are flagged as on Trial by using the criteria fields at the top, if all left blank then all lines flagged as on Trial will be displayed.

If the user has permission to do so from this screen the user can edit the contract to view, edit and if required remove the suspended flag.

6.7.6. Cancelled Contracts

An enquiry screen where users can see which contract lines have been flagged as cancelled, details visible include the reason code selected at the point of cancellation.

Users can select to filter which cancelled contract lines they report on by using the criteria fields at the top, if all left blank then all lines flagged as cancelled will be displayed.

7. Period End Routines

Use these menu option to generate your monthly deferred income/cost postings, if you are using this for your contract DI reconciliation.

7.1. Monthly Journal Postings for Contracts

Select the month you wish to post the journals for.

In this example, we have chosen April 2019, you will note that the system has warned us that there are postings due for previous months, (in red text) which means that contracts have been added relating to a previous period or we did not run the month end for that period, or we did not select all relevant transactions during a previous routine.

If this message appears we recommend you do not continue but investigate those past month’s transactions before continuing to ensure you action accordingly.

If the periods are still open, they will post into to the relevant period. If the previous periods are closed, they will (as is standard within Sage 200), post into the current open period.

Important Note: If you have future months open and in error you select a future month, it is possible if you ‘Post’ that postings will occur (a journal moving from balance sheet to P & L) for future months.

Where this applies monthly journal postings for deferred transactions the system will split journals by date. This will make sure that journals are posted on the correct date.

The screen allows you to view what the journal entry would look like to make sure you are happy with the postings and if not, close/amend the correct contract and process again.

Choose to leave all selected (default option), or deselect some if you do not wish to post the journal at this time.

Select a contract and choose show contract to view that specific contract or

Select a contract and choose show transactions to display the order history and any deferred transactions.

If selecting view past transactions, the system will display any postings previous for the same period

You can choose your views as follows:

• Standard list, shows Contract number, A/C Ref, A/C Name, Contract Line and amounts or
• Extended list which shows the relevant nominal codes as well as the above fields as standard list

To process the journal simply press Post.  The system will ask you if you are sure you want to post deferred revenue, if you are select yes.

Subject to your standard Sage 200 Nominal ledger settings, the journal transactions will either appear on the relevant nominal accounts straight away or sit in deferred waiting until update nominal postings are processed.

7.2. Contract Reconciliation

Contract reconciliation relates to deferred transactions only and they a breakdown all the transactions captured for these service stock items flagged as deferred items  and where a invoice or credit has been raised from a contract line and where the sales invoice or credit has been posted from with Sage 200 SOP

There are multiple tabs on this screen, each giving different views each to help with you reconciliation period end process and on the reconciliation tab there the details are in blue you can use the hyperlinks drill down further.

First Tab: Deferred Income over Months: Displays the total value of the deferred income nominal transactions stored broken down by month and grouped by nominal code and should match the value sitting on your balance sheet deferred nominal account(s) and shown on the third tab (reconciliation)

Second Tab: Customer and Products: The top two panels show customer and product contract values and should always balance. This is a total value for the contract, not just the remaining deferred income.

The bottom three panels provide a detailed breakdown of the remaining deferred income postings , you do have the option to filter out transactions already posted to give you the remaining total deferred income by customer, product or by both

Reconciliation Screen: this shows the total remaining deferred income for each nominal code that the contract lines are linked to.

This is compared to the current nominal balance plus any waiting (deferred or pending) nominal postings and provides a variance

On this screen you can using the hyperlinks drill down to the relevant nominal account

In an ideal world there should be no variances, if there is it’s likely that a manual journal has been posted to the balance sheet nominal code, we always recommend to users and business partners not to make manual journals to nominal accounts where that balance sheet account is nominated on a service stock item as it will / could lead to variances

Where you are seeing a variance then there are several investigatory steps you can take to investigate, and to help further the columns on this screen are explained below: –

Outstanding Deferred Column
These figures are taken from the first tab deferred transactions over months

The deferred transactions are those captured after the sales orders/returns have been posted within sage 200 SOP. Where a service stock item used on a contract line is flagged as being a deferred item, and are shown month by month, and includes a hyperlink for users to drill down further

Noting (as further explained below) that if after the sales order processing post step the contracts are not updated correctly (because the user dismiss that option, or the feature was not enabled) then the system would not have captured the values to include in the deferred transaction file and will not be seen on this first tab.

Where the update contracts after sop post is not run , when a user next goes into sicon contract module , contract maintenance there is a warning displayed to say there are unposted contract lines, but the user can still choose to dismiss this

Nominal Balance Column: A snapshot in real time / at that moment in time of the nominal balance on the relevant nominal account.

Waiting Postings Column:
If as a company, you do not have update nominal set to automatically, and the system is not telling you there are any unposted contracts to update you the value in this column is equal to the ‘waiting to be updated’ within the nominal ledger for the relevant deferred nominal code (s)

Variances Column:
A sum of all 3 columns, hopefully this will be Zero £0.00, but if not the below may help you to identify why not, and suggest how you can correct

Things to Consider and Check:

Has someone raised any manual journals within the nominal ledger? If yes, then this is likely to be the reason why you are seeing a variance as contract manager will not know about those manual journals.

Manual journals in the balance sheet accounts would be the first thing we recommend you check

Have you got the setting ‘change deferred posting status without generating a journal’ enabled within utilities/configuration settings/contract settings?

If so then the system will not create any journals during the period end routine ‘monthly journal postings for contracts’ it will only change the deferred transaction status from not posted to posted, and unless you create a manual journal, you will see variances within contract reconciliation equal to the value of the transactions that had their status changed’

Another area to check would be to make sure none of the service stock codes used in contracts are set for the revenue to go direct to the P & L instead of the balance sheet code (the nominal is on the analysis tab on the service stock record

Make sure also that the same balance sheet nominal code is being used for the monthly journal on the same stock code

Make sure the ‘create monthly journal postings from revenue was ticked, (and it’s not a case of it was only ticked after contract sales orders had been raised, because if it had, contract manager would not have generated any deferred postings)

For further information on the correct usage of nominal codes within contracts please refer to section 1 of this help and user guide, Contract Pre-requisite’s

Using Sicon Projects

If the nominal code shown on the sage analysis tab in the revenue field is showing the balance sheet deferred nominal account correctly but the sales order was posted to another nominal code, you need to check (view) the sales order line to see where it has posted to. If the sales order was generated from within contracts the user cannot manually change the nominal code when either an order has been generated from contracts as we lock it down, however if it’s been manually added on a sales order a user can (shouldn’t but can) change the nominal code

Furthermore, if Sicon Projects is installed and set to integrate because Sicon projects is ‘king’ it may be that the project header that was set on the line, has overridden the nominal code, because the project header itself when created in projects has had a default nominal code set against it and is overriding the nominal set up on the stock record

If this is the case, you need to review the project header set up within Sicon projects and ‘maintain project headers

It’s likely you have a project header specifically for contracts, if this is the case then make sure that the default nominal A/C is set to be the same as the stock record/analysis tab/revenue field nominal account

If you are using a generic project header, then make sure there is no default nominal code set on the project header, this way the sales order line will use the stock record nominal code. If you have checked and this is the case the cause of the variance you will need to journal the value of the sales order (net) that was posted to another nominal instead of the balance sheet deferred, and then raise a manual journal debiting the incorrect nominal account, and crediting the correct nominal code referencing the invoice / sales order number for audit purposes

Has a contract user, been into a contract, and edited, deleted, added any deferred transactions? Users may not realise that any amendments, adding, clearing done here (screen shot below) only effects deferred transactions and not the original value posted to the balance sheet from the sales order raised.

When you go in to Sicon Contract are you seeing a warning that there are contracts not updated? (as per the screen shot below).

If so, then this means that although the sales order has been posted, the contract deferred postings tables/file have not been updated, and therefore when the monthly journal routine is run, they will not be included and a journal entry not made, so the original value posted to the balance sheet is not reducing.

To correct this, use the following menu option / process to update.

he balance sheet from the sales order raised.

When you go in to contract manager are you seeing a warning that there are contracts not updated? (as per the screen shot below).

If so, then this means that although the sales order has been posted, the contract deferred postings tables/file have not been updated, and therefore when the monthly journal routine is run, they will not be included and a journal entry not made, so the original value posted to the balance sheet is not reducing.

To correct this, use the following menu option / process to update.

If everything above is checked and you are happy, and you believe everything is in order with the above then it’s likely that you need some consultancy to help you investigate and you should contact your business partner and/or Sicon to arrange some consultancy (this will be chargeable at your business partner standard consultant rates).

8. Contract Printing

8.1. Print Renewal Reminders (not applicable to ‘rolling contracts’)

Two different renewal reminder letters can be printed from the Contract Manger Module; first reminder and second reminder.  You can use either, or both, and the layouts are based on standard Sage 200 report designer layouts, which can be amended. NB: using reminders is not a mandatory step.

The renewal month will be picked up from the next start date of the contract line and the First and Second Reminders will be sent out in accordance with this date and in conjunction with the module settings (see Utilities – Configuration Settings – Renewals).

Select Display to show all the contracts due for reminders to be sent (or use the filters as required).

Select the relevant contracts or select all and select print.  Standard Sage 200/3rd Party print options apply for sending to customers.

8.2. Print Purchase Orders

This facility in this version is relatively new and may grow in function over the next few releases.

On a contract Line you can specify a supply that the contract is ‘backed off to’ (for example).

The purchase order layout is a simple one, but can be customised through Sage 200 report designer (This function is not at this time linked through to Sage 200 POP).

The details listed are contract numbers, in this example on contract number 10 ‘Hulme Home Fitters’.

The contract has 2 lines, one for hardware support, one for software support, both lines are backed off to 3^rd parties and both have suppliers (different suppliers) associated with.

The system will generate 2 pages.

Page 1 for the back to back / 3^rd party supplier costs in association with line 1.

Page 2 for the back to back / 3^rd party supplier costs in association with line 2

9. Maintenance

9.1. Contract Type Maintenance

9.2. Payment Type Maintenance

The ability to create payment types were in the legacy contracts as standard and were included before the ability to have up to sicon contract line analysis codes (up to 150), and there was a requirement for some customers to analyse contracts by payment method within custom reports.

Once configured sits within the ‘contract details tab’ which can be enabled from within the contract settings tab within configuration settings.

If enabled, an additional tab appears on the contract line and is a selectable drop-down feature.

9.3. Visit Frequency Maintenance

The ability to create payment types were in the legacy contracts as standard and were included before the ability to have up to 150 analysis codes, and there was a requirement for some customers to visually see / note if onsite visits were included in the contract.

Once configured sits within the ‘contract details tab’ which can be enabled from within the contract settings tab within configuration settings.

If enabled, an additional tab appears on the contract line and is a selectable drop-down feature.

9.4. Deletion Reason Codes (Cancellation Reason Codes)

At least one ‘Cancellation is required’ to process amendments/credit of previously raised contract sales order.

For custom reporting purposes / for a visual reference to record why a contract has expired, not renewed or cancelled.

The system has cancellation flags on the contract lines which are visible / editable on a contract when using the function ‘edit’ / ‘amend’ and ‘View’.

The only time that the system populates the date cancelled flag and cancellation code (reason) automatically is when the contract amendment process is used to cancel and credit a previously raised contract sales order.

If the contract line is left to ‘expire’, the line, by default is not shown on the contract line, but can be accessed by ticking the expired flag, at which time the line can be edited and the contract flags manually set.

If a cancellation code is unticked so it is disabled, you will no longer be able to select this as a cancellation reason however, all contract lines that have  an association with a disabled code will retain this in the background.

9.5. Who Sold Maintenance

The ability to create Who Sold maintenance were in the legacy contracts as standard and were included before the ability to have up to 150 sicon contract line analysis codes, or the use of SOP Analysis codes  within the module (SOP Analysis Codes is the  most frequent method used to allocate a sales person against a transaction).

Once configured the data sits within the ‘contract details tab’ which can be enabled from within the contract settings tab within configuration settings and can be used on custom reports, and as a filter within ‘generate sales orders’.

10. Imports

10.1. Import Contracts

Import contracts using the csv import available from within the module itself, this ensures the correct template for the correct version.

By Selecting ‘example import file’ the system will generate / create two excel workbooks.

One will have definitions of the data to be populated on a spreadsheet with headers, types, length, details of whether the field is mandatory or optional, notes for your reference and examples.

We do not recommend contract numbers starting with a 0 (zero) as excel / saving as csv have a habit of stripping these off;

We recommend you ensure that date columns, qty columns are formatted correctly and other excel formatting and configuration is considered.

The other one will be an example of a csv (which is the file format required for importing).

As with all Sicon module import routines if there are errors in the file to be imported the system will give you details of which line is causing the issue, and what field on that line is the issue.

10.2. Import Service Item Stock Settings

If managing deferred revenue and/or costs through sicon contracts, default nominals can be set at either stock product group level or stock code level. Nominals for these types can be imported against each stock record using the Import Service Item Stock Settings using the csv import available.

Initially selecting ‘example import file’ to generate your template.

11. Generate Deferred Postings

As standard deferred transactions are created and stored in database at the point of the contract sales order being raised and then posted , but where contracts lines are being imported, and the service items are flagged on the stock record as being a type where deferred income/costs apply , and where the current period of contract has been invoiced in a another system prior to importing you may want to generate the deferred transactions  in the new system in order for monthly postings / journals to occur rather than manual journals manually within the nominal ledger

If however, for the imported contract lines, where the service item is flagged as deferred, but you do not wish (until renewal) for the system to generate monthly journals, then simply do not use this function.

If this is the case, use the menu option within utilities.

Enter the date you wish the system to generate deferred transactions from, tick the mark as posted’ option, select display and the relevant contract lines will be displayed.

Select the relevant ones and select ‘Generate Deferred Postings’.

Once complete if you were to look at a contract line and then view details.

And select the ‘deferred Transactions Tab’.

The newly created deferred transactions will be listed.

Important Note: Consideration needs to be given current balances on the relevant nominal codes prior to import and the requirement to ensure the correct nominal codes are associated to the stock product groups or stock codes for service stock items being used within contracts. We would recommend that new nominal codes are created on take on of contracts where it’s felt the balances on the nominal codes are not accurate.

12. Contract Orders

12.1. Contracts where Items/Assets/Equipment are included

For those customers that as part of their service contract with them include items on long term hire for the duration of the contract this feature is ideal.

Anyone who has more complex hire requirements, then our advice is to take a look at the feature rich Sicon Hire Module

A prerequisite for this contract order feature to be used is that you have the Sicon Fixed Assets Module installed, configured and set-up

Scenario / Example of where you may want to use this feature

You supply electric bikes to commercial and retail customers.

Some of those customers have a contract with you to maintain and service those e-bikes for which you charge an annual fee and as part of the contract itself the bike is supplied to them free of charge to be used during the duration of the contract

The e-bikes until supplied to the customer are stock items within the Sage 200 stock module, once supplied, the e-bikes remains your property, a company asset but as part of the process needs to be transferred to your asset register depreciating in line with the relevant fixed asset categories default values

This feature allows you to link what is to start off with a stock item, allocate, pick and despatch it producing a despatch note and at the same time an internal stock issue / movement thereafter creating a fixed asset record, NBV of which is taken from the cost of the stock item, category & subcategories taken from the sicon fixed asset defaults on the stock item record

It also creates an equipment record (equipment records are part of the Sicon Common Components module which is installed alongside the Sicon modules)

If as a company you are using Sicon Service, you would be able to see the equipment records within the service module and create service cases accordingly

Depending on how you prefer your assets to be created when despatching the stock item against a contract line, you can choose to either create an asset per single item, or if for example one customer has 5 e-bikes all the same (a single stock item) as part of their contract, you can choose to create a single asset with a batch qty of 5

This is something you should decide before you start using the feature, and enable during set-up.

12.2. Pre-Requisites / Set Up

If you are looking to create a single asset with a batch qty then within Fixed Asset Settings tick the ‘Enable multiple quantity asset batch’ as per the screen shot below

If against a contract line the customer has just 1 e-bike in our example a single asset will be created with a batch qty of 1

Categories & Sub Categories

Create & configure the relevant categories and sub categories relating to the assets/equipment that are supplied as part of the contract. (Examples below)

Internal Areas Set up within Maintain Stock Control Settings

During the process to despatch a stock item against a contract order line, the module uses Stock Internal Areas at two different stages of the process allocating and pick/despatch

Our recommendation however for month end reconciliations within the stock and nominal modules is to have a different contract order issue internal area and nominal accounts

If it’s not important to you as a company to know the different values, then you can use your standard internal issue area, or use separate contract order issue area, but the nominal account behind it remains your stock holding nominal account

If following our recommendation, we recommend the Internal Account to be a balance sheet additions nominal code associated with the Fixed Asset category

In our example our e-bikes within fixed assets are linked to a category ‘Long term contract Hire Orders’ with a sub category E-Bikes All Types

In our example we have created a Stock Internal Area called ‘Contract Order Issue’ and the balance sheet nominal code is set to be our ‘Long Term Contract Hire Additions’

The first time the Internal area is used is at ‘allocation stage’ this moves the stock from Qty Available to Qty Allocated’

When allocated stock history shows

The second time the Internal area is used is when the item is despatched, and the module issues the stock item / creates the fixed asset (s)

When despatched stock history shows Out – Internal, with the reference being the contract number, plus the contract order line number

Stock Item & Fixed Asset Defaults

On the stock item itself you need to set the default category and if Sub category

This is done within the Sicon tab, select Fixed Asset Defaults to link the asset category and sub category, when despatching the stock item against a contract line using contract orders, the system will use these defaults

Stock Item / Warehouse

You will also need to ensure the stock item (s) has a cost price set, as this will be used to create a net book value (nbv) when the asset is created, and make sure the stock item has the relevant warehouse set, from where long-term contract item items are despatched from.

If you do not set a cost price your asset will be created with a £0 value, and you will need to amend the asset details before depreciation takes place.

Contract Order Settings

Before you start adding contract lines which include contract orders, please ensure within the settings tab you select the newly created internal area you have created for contract orders.

12.3. Adding contract Order lines - Linking Hired Out Item to a Contract line

Add your contract line as you would normally do so within contract module.  For further details please visit the section within the Contract module help and user guide section ‘Adding a New Contract and New Contract lines’

In our case we have a service stock item set up for an E-Bike Annual Service & Maintenance Includes the Bike Hire

When the contract line is added, highlight the line and use the ‘contract orders’ button to link add the stock item (s)

The group No is there only for if you are adding lots of stock items within this form and you wish to group / list certain ones together on the despatch note. If this is not relevant the grouping can be left at 0

Select the Item code (stock item), tab it shows the stock name.

The description field can be left blank or you can type some extra info into the field

To set a default Sage stock warehouse for all stock items on this contract order, set a default at the top left of this screen

If you haven’t selected a default warehouse at the top of this form, you can select each time per line

Enter an Order date and Due date (Shown on the despatch note layout) and will be used during the internal stock issue appearing in stock history as the date issued

Until the lines are allocated and despatched no internal stock issues take place and the assets / equipment records are not created.

You can use the move up / down function, (highlighting a line first) to reorganising the order in which the items will appear on the despatch note if not using grouping.

Or if added on by mistake you can remove.

12.4. Print, Allocate, Picking Note & Despatching

Also, from this screen you can print the contract order details, noting this is not the contract itself, this is the lines you have added on this ‘Contract Order’ Form.

Use Allocate Lines, just like you would on a normal sales order, to ensure the stock is reserved against this contract order

When ready to ship the stock items (in our example e-bikes), use Print Picking list /print despatch note.

Layouts can be amended using standard sage 200 report designer

This documents can be re printed at any time using the same buttons on this screen :- Print Order, Picking List, Despatch Note

We recommend when testing this feature that at each stage you check the stock record / balance / history so you are aware off the stock movements that take place.

12.5. Process to Create the Fixed Asset & Equipment Record

It’s at the despatch stage of the process that the asset (s) are created which in turn creates an equipment record (s) which are visible when against the contract line, the user selects the ‘Equipment Button’.

The despatch date is used as the capitalisation date when creating the fixed asset

This will create an Equipment Record on the contract line for the items despatched.

The assets are created using the category and subcategory set stock item level, the cost value from the stock record.

The date of purchase and capitalisation date will be set to the despatch date during the despatching of the item against the contract line.

The Asset Type is by default set to ‘Contract Asset’.

The equipment record remains linked to the contract line, the equipment record shows the contract end date, but even after this end date the equipment record remains so if you are using Sicon Service you can still log a service / support call against the equipment. But you will see that the contract has expired

The asset remains as an active fixed asset, and in line with the depreciation values / life will continue to depreciate

If the asset/equipment record needs to be written off, for example if the customer damage the e-bike beyond repair, then within fixed assets you would use the modules ‘write off asset’ process and if using the sicon service module you can un-assign the equipment record from the linked customer

Important Note: The above contract order process does not generate the actual contract line for the contract itself through to sop for billing, this should be done using the standard Sicon Contract processing method, for further details please visit the relevant section of the Sicon Contract help and user guide titled ‘Contract Processing’.

13. Enable Module

This screen is used to show all configured Sicon Add-ons and allows the entry of enable strings to allow use of a module.  When a new module enable string is provided, copy into the ‘Enable string’ field and then click Apply to save the changes.

If online enable strings have been activated these will self-populate.

14. Contract Reports

Within the Contracts module there is a suite of reports that are available.

As with all the reports, they are written in Sage report designer and are therefore editable by business partners and / or customers who are experienced with the report designer package

Important: you should ensure you have copy of the report you are amending, or a backup of the report folder before any changes are made.

Each report has a criteria values window which allows for filtering of information before the report is run.

15. Release Notes

The release notes page shows which release of the system includes new features or issues resolved.

At the release of Sicon v21 we announced that going forward, we will only be supporting Sage 200c and as such we are able to drop the year from our version numbers. We moved from 201.201.0.0 to 210.0.0.

New features detailed in the Release Notes relating to Pre-Release versions will not be detailed in the current Help and User Guide until the end of development phase.

16. New Features & Important Information