Problem.

A user requirement document ( URS ) has been drafted (Below) Is it good, bad, needs improvement? Explain Identify 10x items from list which need more Details Clarification Suggestions SMART.

Besides bad word choice of "Etc. and It" I have not found anything that stands out as being wrong or incorrect for this USR (User Requirement Specifications) I am new to URSs so if someone would please tell me what I'm missing. Thank you!

User Requirements Specifications (URS)

REQUIREMENTS OVERVIEW -

The requirements below are for Finance, Procurement and Information Technology. The SOW should cover the needs the of the business, however we would like for additional recommendation of features\capabilities which are recommended to help share the scope and phasing of our Source-to-Pay solution.

PROCUREMENT -

Traceability of changes w/ receiving, POs, pricing, etc. Catalog ordering both punchout and internal catalogs Setting up of internal catalogs PO pricing tying back to the contracted pricing (clinical trials, projects, etc.) Building G/L coding for Ad Hoc items in a PO. Setting up Spend categories that help build the G/L code for the line items of the PO Vendor Master set up Set up purchase req routing for specific spend categories (hazardous material, etc.)

FINANCE\ACCOUNTING -

Ability to act as our subledger: all invoices (approved or not) need to be housed in one space, where we can track aging, approvals, and where an invoice is in the approval/payment process; we currently have an Excel tracker, a separate Excel accrual, and then whatever is in ERP that is ready to be paid, so we have invoices in 3 different places Approval/receipt routing: I would like the system to have approval routing that is flexible, so we can have alternate approvers, multiple approvers, or other custom routing requirements that are easily maintained Ability to plug into different systems (NetSuite (Oracle) for one, but if our ERP decision changes, one that can move with us) Reporting I would like to be able to easily pull aging information, vendor spend information and other reports, and have the ability to customize the reports Electronic payments Electronic processing if possible, since we have such a small shop, have the system read PDFs and input the invoices into the system independent of staff intervention where and when possible Mobile access for approval if the system has accessibility (so people can receive/approve) from their phone that would be a nice add-on Support Id like to know what kind of front-end and back-end support we would have, and what kind of support we might require either in-house or through the vendor (if possible)

INFORMATION TECHNOLOGY -

System must by web based and accessible via a browser (i.e. Chrome) Application needs to support single sign on or ADFS integration System must support security controls to logoff users from application Must have APIs\connectors to multiple ERP systems (Oracle, etc.) Is it real time data exchange between ERP and P2P tool? Must have defined DR solution Source must support FX rates Must adhere to Pharma\Biotech regulations and SOX compliance

Does system allow all fields of database to be queried using report writer with the ability to do standard and ad-hoc reports