Versions Compared

Old Version 35

changes.mady.by.user Anastasia Medovkina

Saved on

compared with

New Version Current

changes.mady.by.user Anastasia Medovkina

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

MLI Rules

An MLI Rule is a process that allows specific people (collected in an MLI Level) to take specific actions on specific invoices. MLI Rules are configured using diverging approval paths for different trade/category combinations. You will configure each MLI Rule based on your organization’s invoice approval workflow. In this section, you are essentially building an invoice approval hierarchy.

Configuring MLI rule setsImage RemovedImage Added

MLI Rules and the Approval Workflow

MLI Rules check each invoice to determine the appropriate approval workflow:

  • First, it checks the trade and category of each invoice.
  • Next, it checks the MLI Level to see who should receive the invoice, which Actions users in that MLI Level can take (approve, reject, place on hold, or return back), and the maximum invoice amount (or Limit) allowed for each action.
  • Once the MLI Level user takes action, the MLI Rules determine whether the invoice should be either forwarded or sent back (returned) to other levels. The rules of forwarding invoices can be overridden or skipped when an invoice limit is reached.
  • Finally, when the user takes action, the invoice is set to a certain invoice status.

You may also determine the number of days each MLI Level has to take action before the invoice automatically escalates to the next stage in the approval process. See Auto-Escalating Invoices for details.

To reiterate the above, let's look at these examples:

Example of an MLI rule setImage RemovedImage Added

  1. These Safety MLI Rules cover all invoices across only the Alarms, Fire/Life Safety, and Safes trades, and only in the Capital and Remodel categories. 

  2. The levels configured are for General Manager and District Facility Manager. 

  3. Users in the General Manager level have the actions to both approve invoices up to a limit of 1,500 USD (or 1,500 in local currency), and reject invoices up to a limit of 1,000 USD (or 1,000 in local currency).

    note

    Should you need to change the decimal point (.) to decimal comma (,) on monetary amounts, contact your ServiceChannel representative. 

    1. Approved invoices are forwarded to the District Facility Manager level.
      1. If the invoice amount is less than the limit configured for this level, the invoice is forwarded to the District Manager level in the Approved status.
      2. If the invoice amount is greater than the limit configured for this level, the invoice is forwarded to the District Manager level in the Reviewed status.
    2. Rejected invoices are not forwarded to any other user in the hierarchy. In this case, the General Manager has the 'final say,' and a notice is sent to the provider that the invoice was rejected. 
    3. Invoices are Auto-Escalated to the District Facility Manager when the General Manager does not take action in 5 days. 
    4. Finally, invoices that are over 1,500 skip the General Manager and are sent directly to the District Facility Manager. (See Skips and Overrides, below, for more information.)
  4. For District Facility Manager-level users,
    1. an invoice amount of up to 10,000 limit can be approved; these are forwarded to Lead Facility Managers.

    2. an invoice amount of up to 5,000 can be rejected

      ; again, as the 'final say,' the invoice stops in the hierarchy and a notice is sent to the provider

      .

    3. an invoice costing up to 5,000 can be placed on hold; these are forwarded to Facility Managers in the On Hold status.

      District

      Note

      The On Hold action in the MLI hierarchy can work in 3 ways:

      • If the On Hold action checkbox is not selected, users at this level cannot put an invoice On Hold.
      • If the On Hold action checkbox is selected and any other MLI user to forward the On Hold invoice further selected, the On Hold invoice will be forwarded to the specified level. 
      • If the On Hold action checkbox is selected and the same MLI user to forward the On Hold invoice selected, the On Hold invoice will stay at the same level. 

      Let's look at the examples presented in the table below:

      Image Added


    4. Facility Managers can Override the General Manager by taking action on an invoice (approve, reject, or place on hold) before the General Manager takes action. In other words, the District Manager does not have to wait for the General Manager to take action. (See Skips and Overrides, below, for more information.)
    5. Invoices are Auto-Escalated to the Lead Facility Manager when the District Facility Manager does not take action in 3 days.

    6. Finally, invoices over 10,000 do not skip the District Facility Manager. The District Facility Manager has to 'approve' the invoice for it to route to the Lead Facility Manager.

Anchor
MLIRules_AutoEscInv
MLIRules_AutoEscInv
Auto-Escalating Invoices

An MLI Level that has the Approve Action set to forward to the next MLI Level in the hierarchy can be configured to automatically escalate invoices after a certain number of days. This is useful so invoices do not get stuck in the hierarchy for a long period of time.

Anchor
MLIRules_SkipOverride
MLIRules_SkipOverride
Skips and Overrides

In MLI Rules, you can skip an approver's level and also override an approver's level.

  • Skip: any invoice with an amount higher than that level's approval limit will not appear in the user's invoice list.
  • Override: an approver does not have to wait for the level below to take action on an invoice. Users on that level can take action at any time.

Skip and Override checkboxes used in the MLI rules configuration

Anchor
DefaultMLIRuleset
DefaultMLIRuleset
Configuring the Default Rule Set

When you complete at least one MLI Level setup, you will see the default rule set under MLI Rules. This is a catch-all rule for all invoices not addressed by configured rules. Think of the default rule set as a safety net to catch everything else that your other configured rules do not intercept.

Note

You must create MLI Levels before creating MLI Rules. The best practice is first to create all MLI levels so you can easily select them while creating MLI rules.

Configuring the Default Rule Set in MLIImage RemovedImage Added

Warning
titleImportant

You cannot delete any trades or categories in the default rule set.


Panel
bgColor#F9F9F9
titleColor#0e3367
titleBGColor#EAEAEA
borderStylenone
title⦿ How to Configure the Default Rule Set
  1. On the MLI Configuration page, click Default Rule Set. The page for configuring the default rule set appears.
  2. Click the Add Level button to configure the rule.
  3. Under Level, select the appropriate level from the drop-down list of MLI levels you configured before.
  4. Select the appropriate actions that users of that MLI level can take on invoices:
    • Approve is selected by default after you pick an MLI level at the previous step
    • Reject is selected by default after you choose an MLI level at the previous step

    • On Hold is selected when an invoice may need additional information

      Note

      The On Hold action in the MLI hierarchy can work in 3 ways:

      • If the On Hold action checkbox is not selected, users at this level cannot put an invoice On Hold.
      • If the On Hold action checkbox is selected and any other MLI user to forward the On Hold invoice further selected, the On Hold invoice will be forwarded to the specified level. 
      • If the On Hold action checkbox is selected and the same MLI user to forward the On Hold invoice selected, the On Hold invoice will stay at the same level. 

      Let's look at the examples presented in the table below:

      Image Added


    • Return is selected when an invoice goes back to the previous level

  5. (Optional) Under Limit, enter the maximum invoice monetary amount for each action. Mind the following:
    1. When you set a limit, you also need to select an MLI level where invoices whose amount exceeds the limit will be forwarded to.
    2. When you set no limit, invoices, when taken action on, will move to the status selected in Set Status To and remain at the current MLI level — unless you select a level to forward them to. Also, when the Limit field is left empty, the implied default amount in it is 9,999,999.99. It means that a user belonging to this MLI level can take action on invoices with the amount up to that default amount.
  6. (Optional) Under Forward To for an action, select a level where invoices will go to after users take action on them. This automatically:
    • Sets the invoice status for the Approve and Reject actions action to Reviewed under Set Status To.
    • For the Approve action only, makes the Auto-Escalate in Days field editable. If required, enter the number of days after which invoices, if not taken action on, will be auto-escalated to the next level.

    • Adds the next MLI level to the Default Rule Set configuration page.

  7. Repeat steps 2–6 for all MLI levels you need to configure for the Default Rule Set.

    Note

    For the Approve action at least at one of the levels, you need to set the status to Approved in Set Status To.


  8. (Optional) Select Skip for a level to route invoices to the next level in the hierarchy when the invoice amount exceeds the limit set for the current level.

    Note

    Note that you cannot set Skip on the last level of the MLI hierarchy.


  9. (Optional) Select Override for a level to allow users of the current level to review and take action on invoices before users of the previous level do it. Note that you cannot set Override on the first level of the MLI hierarchy.
  10. Click Save. An alert appears indicating that the Default Rule Set was saved. Also, on the MLI Configuration page you are now able to add custom rule sets.

Anchor
CustomMLIRuleset
CustomMLIRuleset
Configuring Custom Rule Sets

Once the Default Rule Set is configured, you may then create your own rule sets to define your approval hierarchy. These rule sets define your business rules on how you want invoices to route for assigned trades and categories.

Unlike the Default Rule Set, you may add and remove the appropriate trades and categories that fit your workflow. You can either create a custom rule set from scratch or clone an existing set.

Note

You must create MLI Levels before creating MLI Rules. The best practice is first to create all MLI levels so you can easily select them while creating MLI rules.


Panel
bgColor#F9F9F9
titleColor#0e3367
titleBGColor#EAEAEA
borderStylenone
title⦿ How to Configure a Custom Rule Set
  1. On the MLI Configuration page, locate MLI Rules, and click Add Rule Set. The page for configuring a custom rule set appears.

    Creating a custom rule set
  2. In the upper-left corner, enter the name for your custom rule set.
  3. Next to Trades, click Add/Remove. The overlay for managing trades appears.
  4. Pick individual trades, or hit the Select All checkbox to select all trades, and click OK. The selected trades will show up on the page.
  5. Next to Categories, click Add/Remove. The overlay for managing categories appears.
  6. Pick individual categories, or hit the Select All checkbox to select all categories, and click OK. The selected categories will show up on the page.
  7. Under Level, select the appropriate level from the drop-down list of MLI levels you configured before.
  8. Select the appropriate actions that users of that MLI level can take on invoices:
    • Approve is selected by default after you pick an MLI level at the previous step
    • Reject is selected by default after you choose an MLI level at the previous step

    • On Hold is selected when an invoice may need additional information

      Note

      The On Hold action in the MLI hierarchy can work in 3 ways:

      • If the On Hold action checkbox is not selected, users at this level cannot put an invoice On Hold.
      • If the On Hold action checkbox is selected and any other MLI user to forward the On Hold invoice further selected, the On Hold invoice will be forwarded to the specified level. 
      • If the On Hold action checkbox is selected and the same MLI user to forward the On Hold invoice selected, the On Hold invoice will stay at the same level. 

      Let's look at the examples presented in the table below:

      Image Added


    • Return is selected when an invoice goes back to the previous level

  9. (Optional) Under Limit, enter the maximum invoice monetary amount for each action. Mind the following:
    1. When you set a limit, you also need to select an MLI level where invoices whose amount exceeds the limit will be forwarded to.
    2. When you set no limit, invoices, when taken action on, will move to the status selected in Set Status To and remain at the current MLI level — unless you select a level to forward them to. Also, when the Limit field is left empty, the implied default amount in it is 9,999,999.99. It means that a user belonging to this MLI level can take action on invoices with the amount up to that default amount.
  10. (Optional) Under Forward To for an action, select a level where invoices will go to after users take action on them. This automatically:
    • Sets the invoice status for the Approve and Reject actions action to Reviewed under Set Status To.
    • For the Approve action only, makes the Auto-Escalate in Days field editable. If required, enter the number of days after which invoices, if not taken action on, will be auto-escalated to the next level.

    • Adds the next MLI level to the Custom Rule Set configuration page.

  11. Repeat steps 7–10 for all MLI levels you need to configure for the Custom Rule Set.

    Note

    For the Approve action at least at one of the levels, you need to set the status to Approved in Set Status To.


  12. (Optional) Select Skip for a level to route invoices to the next level in the hierarchy when the invoice amount exceeds the limit set for the current level. Note that you cannot set Skip on the last level of the MLI hierarchy.
  13. (Optional) Select Override for a level to allow users of the current level to review and take action on invoices before users of the previous level do it. Note that you cannot set Override on the first level of the MLI hierarchy.
  14. Click Save. An alert appears indicating that the Custom Rule Set was saved.

Anchor
MLIRules_Clone
MLIRules_Clone
Cloning an MLI Rule Set

You may clone a rule so you do not have to configure one from scratch. You may clone any Rule Set, even the Default Rule Set.

Panel
bgColor#F9F9F9
titleColor#0e3367
titleBGColor#EAEAEA
borderStylenone
title⦿ How to Clone a Rule Set
  1. On the MLI Configuration page, click the desired rule set. The page for configuring the appears.
  2. In the upper-right corner of the page, click Clone. The rule is cloned, and a yellow bar appears, indicating that trades and/or categories must be unique in order to save the new rule set.
  3. In the upper-left corner of the page, enter the name for the new rule set.
  4. Make the desired changes, and then click Save. An alert appears informing you that the rule set was saved.
  5. Click Close. The created MLI rule set appears on the MLI Configuration page.

Deleting an MLI Rule Set

You may delete any MLI rule set at any time, except for the Default Rule Set. 

Panel
bgColor#F9F9F9
titleColor#0e3367
titleBGColor#EAEAEA
borderStylenone
title⦿ How to Delete an MLI Rule Set
  1. On the MLI Configuration page, click the trash icon next to the undesired rule set. A confirmation alert appears.
  2. Click Delete.An alert pops up indicating the rule set was deleted successfully, and the rule set will not list on the page.


Live Search
spaceKeySCU
additionalpage excerpt
placeholderSearch our Knowledge Base
typepage

Panel
titleColor#ffffff
titleBGColor#5fa7d0
borderStylegroove
titleIn this Article

Table of Contents
maxLevel3
minLevel2
indent20px

Panel
titleColorwhite
titleBGColor#75a346
titleRelated Articles

Filter by label (Content by label)
showLabelsfalse
max8
showSpacefalse
sorttitle
cqllabel in ( "mli" , "configuration" , "rules" ) and space = currentSpace ( )