Procurement: requirements checklist
From the guide at bestfinancesoftware.com/guides/procurement, published 29 October 2026. Use your browser's print command; the site header and footer are left off the page.
| Requirement | Vendor A | Vendor B | Vendor C |
|---|
| Must have |
|---|
| One intake form for every kind of purchase, routed by type, amount and department. | | | |
| Approvals by budget owner, finance, legal and security, in parallel where possible, with a log. | | | |
| Purchase orders that sync to your ERP and match to invoices. | | | |
| Supplier onboarding that collects tax, bank and compliance details before first payment. | | | |
| Committed-spend reporting against budget by department. | | | |
| Depends on you |
|---|
| Contract storage with renewal dates and alerts, if software and services are large spend lines. | | | |
| Catalogues and punchout to suppliers, if you buy goods repeatedly. | | | |
| Sourcing events and bids, if you run competitive tenders. | | | |
| Price benchmarks or negotiation support, if you buy a lot of software. | | | |
Questions to ask in the demo
- Submit a software purchase as an employee would, and show every approval it triggers.
- Show the supplier onboarding form and what blocks payment until it is complete.
- Show committed spend against budget for one department.
- Show a contract renewal alert and what happens if nobody acts on it.
- How does a purchase order reach our ERP, and how is it matched to the invoice?
- What do requesters see on a phone?
Back to the guide, with the reasons behind each item and the vendors described from their own pages.