Please can there be an option to restrict which BI-codes are available against a general ledger code.
Guest
Feb 17, 2026
This is proving more and more of a problem and agree wholeheartedly with Emily, it is creating unnecessary correction journals that need to be approved and are queried with Auditors. As well as time wasted on variance analysis explaining why something is budgeted in one place with actuals in another.
Users are constantly coding things to weird mixes of analysis codes and GL codes and then because you cant change the analysis code once posted you then have to journal the correction. This then means when someone looks back at an invoice in item invoice to check where it has previously been coded to it shows incorrectly and it is a constant cycle.
Being able to only allow certain combinations of codes being used would prevent this. Or at least having default analysis codes for certain GL codes would be helpful so you can suggest where things should be posted!
This would be a total game-changer if it was introduced. We used PASS previously which had this functionality, so it feels like we've taken a step backwards in this respect. We're approaching audit season and I know they will question the volume of correction journals which have been posted due to purchase orders being raised against incorrect GL codes. Much about iFinance is time-saving, but we're spending more than the time saved checking and correcting transactions.
This is crucial for our organisation to limit budget holders from coding to wherever they like, despite them knowing which codes to use. Makes reporting against budget difficult and its time consuming journaling corrections.
Agree with this we have two schools in the one system and to keep it uniform have the same codes with only the analysis code denoting which school it is. being able to restrict various BI codes to a general code would also stop so many mis-postings in the system, that then need to be corrected
This is proving more and more of a problem and agree wholeheartedly with Emily, it is creating unnecessary correction journals that need to be approved and are queried with Auditors. As well as time wasted on variance analysis explaining why something is budgeted in one place with actuals in another.
This feels like a like a very basic feature!
Users are constantly coding things to weird mixes of analysis codes and GL codes and then because you cant change the analysis code once posted you then have to journal the correction. This then means when someone looks back at an invoice in item invoice to check where it has previously been coded to it shows incorrectly and it is a constant cycle.
Being able to only allow certain combinations of codes being used would prevent this. Or at least having default analysis codes for certain GL codes would be helpful so you can suggest where things should be posted!
Completely agree, this should be a a basic function of any finance system, I can't understand the logic behind why it's not set up that way.
This would be a total game-changer if it was introduced. We used PASS previously which had this functionality, so it feels like we've taken a step backwards in this respect. We're approaching audit season and I know they will question the volume of correction journals which have been posted due to purchase orders being raised against incorrect GL codes. Much about iFinance is time-saving, but we're spending more than the time saved checking and correcting transactions.
This is crucial for our organisation to limit budget holders from coding to wherever they like, despite them knowing which codes to use. Makes reporting against budget difficult and its time consuming journaling corrections.
Agree with this we have two schools in the one system and to keep it uniform have the same codes with only the analysis code denoting which school it is. being able to restrict various BI codes to a general code would also stop so many mis-postings in the system, that then need to be corrected