When utilizing a payment processing application within the iiQ Resource platform, users can automatically apply various fees through iiQ’s advanced Rules Engine. This feature allows for customizable fee structures, enabling users to set specific criteria and conditions that determine when and how fees should be applied.
To create a rule that automatically applies a fee, navigate to Admin > Rules in the left menu. Select “Assets” under Resources and choose “when ‘On a schedule’" for the Trigger.
Please note that this action:
It can only be applied with the trigger “on a schedule.”
Accessible to only the iiQ Resource Module
The rule's action does not support Intune payment process integration.
When the fee is charged to a user account, it will not automatically send an email notification to the user at this time.
You are able to generate and send an invoice or statement manually. Please see the following knowledge base guide:
Click + Create New Rule.
Select "Schedule" as a condition filter and choose how often the rule should run. This is a necessary filter when using a scheduled rule.
An “on a scheduled” rule excludes business days.
Next, add an additional filter Number of Days Overdue.
The "number of days overdue" filter should be set to 0 if you want the due date to be included, or set to 1 if items are considered overdue the next business day after the due date.
After applying the filters, add an action by selecting "Add the Feetracker Fee or Payment." Then, enter the dollar amount of the fee you wish to charge.
Field | Required/Optional | Description |
Rule action: Add Feetracker Fee or Payment | Required | The Line item type field dropdown becomes available when this action is selected. It contains the list of fee types that you can define ahead of time within the Fee Tracker app. The Amount field will default to the initial amount defined in the Fee Tracker app but can be changed here as needed.
|
Max # of line items to add: | Required | This field represents the number of times the fee will be applied to the same item. In other words, this field defines the amount of fees that could accrue on one overdue item. For example, the fee only is applied for the first 5 days. |
Add one fee/payment per item checked out: | Required | If this field is toggled ON, the rule will add a fee for EACH overdue item. If a student has 5 items overdue there will be 5 line items with a fee. Alternatively, if this field is toggled OFF, the rule will add only one line item with a fee regardless of the number of items overdue. This rule is run per checkout record (not user). A checkout record will be one if it is a serialized resource but could be multiple if generic or consumable. |
Next, you will select Save Rule.
After the rule is executed, it will check the checkout record for any items checked out in the product. Based on that record, it will apply a fee to the user profile for any overdue items.
Example Scenarios:
If you have a group fee of $30 for all overdue assets that applies once to a student, you will set up the following logic:
Fee = $30
Max # of line items to add = 1
Add one fee/payment per item checked out = no
If you have a flat one-time $10 fee for each overdue item, your setup will be as follows:
Fee = $10
Max # of line items to add = 1
Add one fee/payment per item checked out = yes
If you have a daily $3 fee for each overdue item, your setup will be as follows:
Fee = $10
Max # of line items to add = blank
Add one fee/payment per item checked out = yes
(Pictured Above: A preview of the fee applied via the rules engine.)