Reject Rejects the item. You must enter a rejection reason. The program notifies the originator of the rejection and reason. The originator determines the next course of action (alteration and resubmission or deletion). Forward Allows you to choose another Munis user to review this pending record Hold Retains an item in your approval queue for additional review. It will remain here until further action is taken. Close the Contract Entry program and return to the Work Flow Manager Web part. What’s Next? After a contract has been approved and posted, it may be referenced on requisitions, purchase orders. If additional changes need to be made, they may be entered now, as only one change order per contract may be processed at one time. Contract Change Orders Objective This document provides instructions on how to create contract change orders. Overview Occasionally, during the life-cycle of a contract, it becomes necessary to make changes to amounts, accounts, line items, or other aspect of the contract. This is done using a contract change order. Changes that involve encumbering or liquidating amounts require the change order to be posted to the general ledger. When a contract is in the process of being changed, two versions of the contract exist: the original contract and the change order. Only one change order may exist at any time. If your organization uses Workflow, the change order is routed through an online workflow approval process and once approved, the contract change is posted. This incorporates it into the original contract and the change order no longer exists. The original contract, however, has a change number denoting the number of changes that have occurred. are the changes that are possible for each contract type. Note that updates to prior year lines are not allowed. Encumbered Accounts: Main tab, User Defined tab (if applicable), Subcontractor tab, and Insurance tab information.
Reject Rejects the item. You must enter a rejection reason. The program notifies the originator of the rejection and reason. The originator determines the next course of action (alteration and resubmission or deletion). Forward Allows you to choose another Munis user to review this pending record Hold Retains an item in your approval queue for additional review. It will remain here until further action is taken. Close the Contract Entry program and return to the Work Flow Manager Web part. What’s Next? After a contract has been approved and posted, it may be referenced on requisitions, purchase orders. If additional changes need to be made, they may be entered now, as only one change order per contract may be processed at one time. Contract Change Orders Objective This document provides instructions on how to create contract change orders. Overview Occasionally, during the life-cycle of a contract, it becomes necessary to make changes to amounts, accounts, line items, or other aspect of the contract. This is done using a contract change order. Changes that involve encumbering or liquidating amounts require the change order to be posted to the general ledger. When a contract is in the process of being changed, two versions of the contract exist: the original contract and the change order. Only one change order may exist at any time. If your organization uses Workflow, the change order is routed through an online workflow approval process and once approved, the contract change is posted. This incorporates it into the original contract and the change order no longer exists. The original contract, however, has a change number denoting the number of changes that have occurred. are the changes that are possible for each contract type. Note that updates to prior year lines are not allowed. Encumbered Accounts: Main tab, User Defined tab (if applicable), Subcontractor tab, and Insurance tab information.
JeffCo%20Munis%20Financial%20End%20User%20Process%20Document-Final%2008032015.docx