Skip to main content

Authorisation level showing too high for package authorisation

In this article, we explain why the authoriser level may be too high or not match rule settings when sending an authorisation request.

Y
Written by Yusef Abulaynain
Updated over 4 months ago

You may find that when you try to make a purchase dated in the next financial year and seek authorisation, the system only lets you choose from higher-level authorisers, with lower levels unavailable.

This may go against what you've configured in the authorisation rules of the admin tool. In this scenario, if you had an authoriser level 4 rule for up to £1000, and anything over £1000 went to authoriser level 6. If in the current financial year, you've maxed out your costs for the rule level, and then from that current financial year you make a purchase for the following financial year, the code currently takes that figure into account along with the current year's costs.

Example

If you've used £1000 in 2022/23 and then purchase £1 while we're still in the current financial year of 2022/23 (today being 31/03/2023) but for the following financial year of 2023/24, the code seems to be:
adding £1000 (current year) + £1 (new financial year but purchased in current year)
= £1001 = Level 6 authorisation required.

The higher-level authoriser will need to approve these package requests if they're entered in the current financial year for the following financial year.

However, if the purchase is entered for the financial year you're already in, the reset of costs for that year will have already happened at the start of the new financial year. Therefore, the appropriate authoriser level for your rules will be offered to you since you're in your current financial year.

Did this answer your question?