èßäapp

Non P.O. contracts are contracts that do not require issuance of a Purchase Order. Examples of these contracts are some consulting agreements, speaker/lecturer agreements, licensing contracts, and collaborative agreements.

CAMPUS NON-P.O. CONTRACTS

Most Non P.O. contracts are processed through the appropriate campus Contracts office without the involvement of Procurement.  However, some of these require execution by the Chief Procurement Officer (CPO).  When necessary, èßäappProcurement works with the campus Contracts Office to revise and finalize the contracts. When all reviews are complete, the contract is provided to the CPO for execution.  The fully executed contracts are returned to the campus Contracts Office for distribution and retention in their files.

èßäappSYSTEM NON-P.O. CONTRACTS

For System offices, èßäappProcurement assists in preparation, negotiation, review, finalization and execution of Non P.O. contracts. èßäappProcurement works with System departmental contacts to prepare and review drafts, circulate drafts for review by the General Counsel's Office, Risk & Insurance Management, and any other departments that should be involved. èßäappProcurement logs and tracks the progress of these contracts. Some èßäappSystem contracts may require a PeopleSoft requisition be created in order to facilitate payment.

When all reviews are complete, the final contract is provided to the CPO or delegated Strategic Sourcing Specialist for execution. The fully executed contracts are maintained by èßäappSupply Chain with additional copies sent to the sponsoring department for retention and further distribution.

Templates

• Purchased Services Agreement

SUBMITTING NON-P.O. CONTRACTS FOR PROCESSING

Campus specific contracts should be sent to the respective campus Contracts office where they will be reviewed and processed at the campus level.

èßäappSystem contracts may be sent to èßäappSupply Chain by email. Hard copies may be sent to èßäappSupply Chain, attention: Teresa Vest.  Some èßäappSystem contracts may require a PeopleSoft requisition be created in order to facilitate payment.  Information should be included about the nature of the contract, the action requested, the name of the University contact who can provide further information, and where the contract is to be sent after execution.

Inquiries regarding the status of contracts sent to èßäappSupply Chain should be made to: vestt@umsystem.edu