Overriding Blocking Spending Limits

Background information

Blocking limits on expense reports are rarely final. In some cases, an employee may have to spend more than your expense policy’s normal limits. So it is reasonable to reimburse them the entire amount.

For example, it is possible that only more expensive hotels will be available on a last minute trip.

Increasing limits for an expense

You can configure Cleemy Expenses to allow certain users to remove the reimbursement limit on expense reports they approve or control. These users will then see an ‘Increase limit’ link on the expenses that exceeded the reimbursement amount.

When you click on this link, the amount of the reimbursement is revised to the invoice amount.

You can also enter a temporary reimbursement amount after increasing the expense limit.

In this example, the total reimbursement amount will be 25 £.


After a limit is increased on an expense, the expense report systematically appears with a warning indicating that at least one limit was increased. Similarly, the limit increase is saved in the expense report history.

This is the warning message:


Granting users permission to increase limits

To do this, you must add the ‘Increase expense limits’ permission to a role in role management. You must also set the scope of application for this permission. In general, use the same scope as the one that the user already has approval or control permissions for.

To increase a limit, the user must have permission to modify the expense report whose limit they want to raise:

  • For approvers, this means giving them permission to ‘Modify an expense report at any time’ so they can increase the limit at the approval stage


  • For controllers, simply make sure they have permission to ‘Control - with change permissions’


Sometimes you will have to create a new role (for example, if only some approvers have permission to increase limits) and then assign this new role to those who are entitled to it.

Page content

Was this article helpful?
2 out of 4 found this helpful