Activity Budget/Date Edits

We are using budget edits on the activity level and not the activity account category level. This helps in budget edits much easier and we do not have to tranfer money from one account catgory to another when we had the budget edits on the activity account category level.

As Ruma indicated where you set the budget at directly effects the effort needed to successfully maintain. With account category level edits usually requiring the most effort and activity group requiring the least. Dates though should be a little easier to control. I typically recommend that the activity end date is typically set at least sixty days past expected completion date and then reviewed on a regular basis to determine if adjustments need to be made. If budget edits are becoming a bottle neck you may also want to consider using the tolerance capability to allow the smaller over budget issues to continue to be processed automatically, then make your budget adjustments once a month to take these transactions into account.

You can also look at Budget modifications and can make budget mods on activity budgets. You can set it up in such a way that one person enters the budget mods and another person approves the budget mods and locks down the budget.

If you are on 9.0 applications or higher, you can use Period of Performance settings to help with the date edits. They allow you to set a specific number of additional days past the activity end date to process transactions. The nice thing is that they are by system code, so you can allow an extra 60 days for AP invoices to process, but stop any more requisitions from being entered. PoP can give you the same general process as what Kevin suggested by moving the end date out.