The following details need to be established in each SunSystems database before SunSystems Collect is fully functional :
Action Codes
Action codes are user-defined codes that categorise different types of notes and/or past and future actions, for example, PTP = Promise To Pay.
To access the action codes window: from the Maintenance menu select Action Codes to define your action codes.

The following is a list of the fields on the Action Codes screen:
Code
Enter a meaningful code (up to 5 characters) for the action.
Colour
A colour can be allocated to the action code to help, in the Account Details screen, identify at a glance just what type of actions have been applied to the notes for the specified account.
Note: Use sparingly as too many colours will defeat the purpose of highlighting specific actions
Description
Enter a description of the action code.
User ID
Displays the user ID of the person who last modified the action code.
Modified
Displays the date and time of latest modification.
Discuss in forum

Contact Categories
Categories are user defined codes used to describe a contact, for example, FINCO = FINancial COntroller.

To access the contact categories menu: from the Maintenance menu select Categories to define your contact categories.
The following is a list of the fields on the Categories screen:
Code
Enter the category code (up to 5 characters) for the company contact, for example, you could use ACCNT for accountant.
Colour
A colour can be allocated to the Category code to help identify the category at a glance.
Description
Enter a short description of the category code, for example, Accountant.
User ID
Displays the user ID of the person who last modified the category code.
Modified
Displays the date and time of latest modification.

Transaction Ageing Details
Ageing is the process used to track outstanding balances, for example, transactions can be aged at 7, 14 , 30 and 60 days, or any other user defined band. To access transction ageing details screen: from the Maintenance menu select Ageing to define your ageing bands.
Click here to see a screenshot
From the Maintenance menu, select:

Ageing, to define your ageing bands. Additional Details >> DSO Analysis Maintenance, to enter the Transaction and Amount Analysis Dimension to be used in the DSO calculation. Global Update, to age SunSystems Collect transactions. Run Global Statistics to create a Run History that can then be used to produce the DSO (Days Sales Outstanding) Analysis Report.

For ageing bands for external use, for example, those that will be displayed on a client's statement, see Statement Ageing.
The following is a list of the fields on the Ageing screen:
Display Order
Enter the order in which this ageing band will be displayed on the Ageing Summary. This is the sequence in which data ranges will apply. You can have any number of ageing bands.
Number of Days
Enter the number of days this band will be aged. This figure will be added to the number in the bands before it. For example, if today's date is the 1st June, 2002, then, using the figures shown in the screen above, invoices based on a 30 day payment term would be aged in the following way :

Note: Reports: Each ageing band will pick up transactions with a due date / transaction date that falls between these dates.
Description
Enter a description of the ageing band. This description will show on the Account Details screen.
User ID
Displays the user Id of the person who last modified the ageing band.
Discuss in forum
Modified
Displays the date and time of the last modification.