Request for information template for finance software
Send every vendor the same document, with the same questions and the same pricing table, so their answers line up side by side. This request for information template is one Word document for choosing accounting, ERP, close, payables or expense software.
Finance teams and practices- In the pack
- Finance software selection kit
- Files
- 5, Excel and Word
Get the pack by email
What the request looks like

When to send it
Send it after you have agreed the scope, the budget and your must-have requirements, and before any vendor demo. The kit suggests sending it to four to six vendors and shortlisting two or three.
- You are replacing spreadsheets or an old accounting system
- The business has added entities, countries or currencies the current system can't handle
- You want to compare payables, expense or close software on the same terms
- A practice is choosing software to run client work or its own books
- The board wants evidence for the choice, not only a demo
How to use the request for information template
- Describe your organisation. Fill in the About us table with real volumes. Vendors price on users and transactions.
- Set three objectives. Short, measurable aims, such as removing manual keying of supplier invoices.
- Fill in the timetable. Give vendors a date for questions, and share every answer with all of them.
- Attach your requirements list. Export it from the kit's selection workbook, so vendors answer Yes, Partly, Roadmap or No against each line.
- Compare on total cost. Choose three or five years, then enter every pricing table into the workbook.
Questions
What is a request for information?
A document you send to several vendors before demos, asking the same questions about their company, product, security, implementation and price. It gives you comparable answers to build a shortlist.
What is the difference between an RFI and an RFP?
An RFI gathers information so you can shortlist. An RFP asks the shortlisted vendors for a formal proposal and final price. In this kit the RFI comes first, and final proposals follow the demos and reference calls.
What should a request for information include?
A short description of your organisation and volumes, your objectives, a timetable, how to respond, the questions in a fixed order, a pricing table and a confidentiality note.
What security questions should we ask a software vendor?
Which independent assurance they hold, such as an ISO information security certificate or a SOC 2 Type II report, where data is stored and backed up, which sub-processors they use, and their recovery targets. Under UK GDPR, a processor's work must be covered by a written contract, and it can't use sub-processors without your written authorisation.
Is a request for information binding?
No. This one says it is not an offer to contract, that you may change the timetable or stop at any time, and that you don't pay for responses.
Also in the finance software selection kit
Who it's for
Finance teams and accounting practices choosing new finance software.
Last checked
Checked against UK GDPR rules on processor contracts in November 2026.
