To customize transaction behaviour:
The Transaction Type Settings screen appears.
If your organization uses more than one account type, eg. card, cash, phone or requisition, you will see that you can set up transaction defaults specific to each account type.
The Customize Transaction Type Behaviour window appears.
Option |
Function |
System Default |
Click this icon (green tick) to apply the system default description text within the Description field of the Transaction Details window (Coding tab) |
Blank Description |
Click this icon (red cross) to leave the Description field of the Transaction Details window (Coding tab) empty. |
Fixed Description |
Click this icon (red cross) to define your own text that will populate the Description field of the Transaction Details window (Coding tab). Note: If you are customizing the behaviour for either the Cash Expense Payment DR or Cash Expense Payment transaction types, you can also use this field to change the default text (Payment Processing) that displays on a user's account statement for cash expenses. Note: Alternatively you can translate the text into another language. |
Auto Link Descriptions |
Click Yes if you want the information the user types into the Description field (Description 1 field) to automatically populate the Description 2 field on the Coding tab of the Transaction Details window. Note: This option is only relevant if your company has the second description field enabled. |
Auto Personal Flag |
Click Yes if you want to automatically mark a transaction of this type as personal. For example, if any ATM or cash withdrawals are to be treated as personal and offset against the employee's cash balance. |
Spend Wizard Mandatory |
Click Yes if you want to make it mandatory for an account holder to complete at least one Spend Wizard for this particular transaction type. Note: This option is only be relevant if your organization is using the Spend Wizard module. |
Spend Wizard Disabled |
Click Yes if you want to prevent a user from completing a Spend Wizard for any transactions of this particular transaction type. This stops a user from completing a Spend Wizard as a means of overriding the default coding you have set up for this transaction type. |