Enter |
For |
Description |
A description of what the rule does/what it is for. |
Process Name |
How ProMaster will handle the import activity. You can choose to Process, Auto Post or Do Not Process transactions:
· Process - the transaction will be presented to the Account Holder to verify (standard workflow).
· Auto Post - the transactions will be processed to the status of ` Waiting GL Post' and coded accordingly to the logic of the defined import rule.
· Do Not Process - the transactions will not be processed and will adopt the status of ` Unprocessed'. Typically, this is selected for transaction types that are already recorded in the GL system, such as payments to the Account Provider. Processing this transaction type through ProMaster's export would result in duplicate processing within the General Ledger system.
|
Transaction Type |
Viewing and selecting the transaction type for an existing rule provided by the drop-down list of transaction types on the right. Alternatively, activate All Transaction Types? if the same rule is to apply to all transactions. |
All Transaction Types? |
Selecting all transaction types to be applied to the import rule. This allows you to only select the `All' option in Selection Ind. |
Selection Ind |
Selecting either one of the following three states:
· All - the import rule applies to all Accounts.
· All Except - the import rule applies to all Accounts except those selected. Not an option if All Transaction Types? flag is activated.
· Only - the import rule applies to the selected Account(s) only. Not an option if All Transaction Types? flag is activated.
|
Accounts |
Indicating the rule for applying to the Accounts listed in the Accounts field. The rule may apply only to the nominated Accounts or to a range of Accounts except for the nominated Account. You will not be able to make a selection here if All Transaction Types? flag is activated or Selection Ind is set to `All'. |
Tax Code |
Indicating the specific tax code applied to the transaction type based on the rules specified. The tax code can be set in either one of three ways:
· Default - the tax code will be based on the originating currency of the transaction and the Domestic Default or Foreign Default tax codes set in the Tax Code table.
· Merchant - the tax code will be set from the tax code setting in the Merchant Type table for the merchant of the transaction
· Selected - allows a specific tax code to be set for all transactions processed by this import rule. This is typically used for tax-free transaction types, such as bank fees.
|
Override Expense Type Tax Code? |
Indicating whether the tax code selected in the Tax Code field should override the tax code specified by the expense type, if applicable. |
Expense Type |
Indicating the specific expense type applied to the transaction type based on the rules specified. The expense type can be set in either one of three ways:
· None - no expense type will be set for the transaction, forcing the Account Holder to select an appropriate expense type.
· Merchant - the expense type will be set from the expense type setting in the Merchant Type table for the merchant of the transaction.
· Selected - allows a specific expense type to be set for all transactions processed by the import rule.
|
GL Code Overlay Order |
Based on the GL pack, specifying the order that will be used to overlay General Ledger codes with the transaction type during the statement data import:
1. Select the appropriate GL code overlay from the Available GL Code Overlays pane and then click the left-hand directional button to include the GL code overlay to the GL Code Overlay Order pane;
2. Repeat the above step to ensure all the necessary GL code overlays are included;
3. Order the GL code overlays according to GL stamping requirements. GL code overlays will be applied in bottom-up order.
|