Purchase Requisitions

MSCertUSL Financials Purchase Requisitions is closely integrated with the Accounts Payable, Purchase Orders, Inventory Control and Project Accounting modules. As goods are ordered, all the information is cross-referenced with these other modules.


USL Financials Purchase Requisitions shares vendor, purchasing addresses, and distribution code tables with Accounts Payable and Purchase Orders. Information from the Inventory Control module Item and Warehouse files can be used to create line items for Purchase Requisitions.


• Paperless electronic routing with up to nine levels of review/approval.
• Full encumbrance accounting.
• Real time on-line budget checking to ensure available funds.
• Integration with both system budgets and project budgets.
• Customized requisition order forms.
• Create requisitions when the actual vendor or item price is unknown.
• Review the entire purchasing history of the requisition.
• Easy recall of prior PQs or previously ordered items during PQ entry.
• Unlimited notes may be entered for purchase requisition line items and can be printed on PQ.
• Permits different units to be used for stocking, ordering and receiving.
• Uses the flexible user-defined Purchase Order fields.
• Creates multiple-drop purchase requisitions. For any line item, allows separate deliveries to the same or different locations.

System Integration
USL Financials Purchase Requisitions (PQ) integrates with the Accounts Payable (AP), Purchase Orders (PO) Inventory Management (IM), Project Accounting (PA) and Fixed Assets (FA) modules to price and quantify purchase requisitions created by the system.
PQ allows for verification or account numbers, components and budgets through the Control System module.
Vendor tables, purchasing addresses and distribution codes are shared with the Accounts Payable module and can be maintained from either module.
Integration with both system budgets and project budgets.
Workflow integration with Outlook/Exchange or any SMTP email system.

Download Purchase Requisitions Cut Sheet

• Fast on-line comprehensive vendor history/account inquiry displaying the details of all POs and payment activity.
• Vendor purchasing addresses are maintained separately from the vendor’s remittance address.
• Flexible user-defined vendor fields.

Standard Vendor Items
• Use vendor item codes to speed purchase order entry and ensure accurate line items or to integrate with Inventory Manager.
• Items can be ‘vendor specific’ or available to all vendors.

• Provides comprehensive on-line inquiry tools in Workflow.
• User’s Inbox to monitor the status of a particular user’s workload.
• Exception reporting to monitor the status of requisitions which are behind schedule.
• Requisition History to provide in-formation about all the steps a requisition has gone through, including which users have worked on it.
• Allowed states in workgroup.
• Prints a PQ Exception List to pro-vide information on incomplete purchase requisitions, including which information is required to complete it.

Minimum System Requirements
• Dual Core, 2.3 GHz or better
• 4GB RAM (32-bit Windows Server) sized by need
• 8GB RAM (64-bit Windows Server) sized by need
• Windows Server 2008 – 2012 (R2 supported) (64-bit recommended)
• Microsoft SQL Server 2008 – 2014 (R2 supported) (64-bit recommended)
TERMINAL SERVER (if utilized):
• Dual Core, 2.3 GHz or better
• 4GB RAM (32-bit Windows Server) sized by user count
• 8GB RAM (64-bit Windows Server) sized by user count
• Windows Server 2008 – 2012 (R2 supported) (64-bit recommended)
• Core 2 Processor, 2.3 GHz or better
• 2GB RAM or better
• Microsoft Windows 7 (SP1) – Windows 10 Pro
• Microsoft Office Professional 2007 – 2016 (32-bit only)

Online Help
USL Financials contains context-sensitive, online help for all features and functions of the system.

• Full USL Database, Module, Menu, Function, Action and Account Level security options relative to the system security.
• Full security by Delivery Location in PO and PQ.
• Departmental Security via Workgroups in A/P, A/R, GL, and PQ.
• Security by Project, Sub-Project, and Funding Source (Grant).

Send this to friend