1. Updating Default Coding Rules
Default coding rules are used to automatically complete the coding for a transaction, thereby reducing the amount of time needed by an employee to code transactions. The coding rules are based on a hierarchy that determines the default code to use, such as the company unit an employee belongs to, or the merchant category of the supplier used in the transaction.
- Click Administration.
- On the Administration Overview screen click the Default Codes option.
- On the Default Coding Rule Management screen, click the Default Rule Category to display the items under the category, and then click
for the item you want to build a rule for.
- In the Insert New Default Coding Rule window, enter the Applicability Settings and Default Code Values that will apply to the item, and then click Save.
The Default Coding Rule Management screen displays the rule that apply to the item. To change the rule, hover your cursor over the rule and click on Edit.
2. Updating Transaction Defaults
Transaction type defaults enable you to set the default codes for certain transaction types to save time for the account holder when coding their transactions.
You also have the ability to customise the behaviour of transaction types. For example, you can define the text for the Description field in the Transaction Details window, or force users to complete a Spend Wizard for particular transaction types.
- Click Administration.
- On the Administration Overview screen, click the Organisation tab, and then click the Tran Defaults box.
- On the Transaction Type Settings screen, click
for the transaction type.
- In the Customise Transaction Type Behaviour window, change the settings as required, and then click Save.
Option |
Description |
System Default |
Applies the system default text. |
Blank Description |
Leaves the field empty. |
Fixed Description |
Enables you to define your own text for the field. |
b. In the Advanced Management section, select Yes or No for the following settings.
Setting |
Description |
Auto Personal Flag |
Automatically marks the transaction type as Personal. For example, you may want to set any cash withdrawals as a personal expense. |
Spend Wizard Mandatory |
Makes it mandatory for the account holder to complete at least one Spend for the transaction type. This option is only relevant if the organisation is using the Spend Wizard module. |
Spend Wizard Disabled |
Disables Spend Wizard for the transaction type. This stops a user from completing a Spend Wizard as a means of overriding the default coding set up for this transaction type. |