How to Run a Lease Accounting Software RFP & Vendor Selection Process
Selecting lease accounting software is a multi-stakeholder decision affecting accounting, real estate, IT, internal audit, and procurement teams. A structured RFP (request for proposal) process produces better outcomes than ad-hoc evaluation: defined requirements, comparable vendor responses, structured demos, and documented decision rationale. Effective lease software RFPs cover functional requirements (ASC 842/IFRS 16/GASB 87 compliance, abstraction capabilities, critical date tracking, reporting), technical requirements (ERP integration, security certifications, deployment model, data migration), commercial terms (pricing model, implementation costs, term, exit provisions), and operational support (implementation methodology, training, ongoing service). The selection criteria should align with the organization’s portfolio characteristics, current state, and strategic priorities. This guide covers the RFP process phases, functional and technical requirements to cover, implementation and support considerations, and the red flags that warrant attention during evaluation.
Written by Kathrina Catolico, Chief of Staff · Reviewed October 2026
Why a Structured RFP Process Matters
Lease accounting software is a multi-year investment with significant operational and financial reporting implications. The wrong choice produces compliance gaps, manual workarounds, and integration friction; the right choice produces consistent accounting, audit-ready documentation, and operational efficiency. A structured RFP process reduces the risk of mismatch between requirements and vendor capabilities. Ad-hoc vendor evaluation — watching demos from a few vendors, choosing based on impression or price — frequently produces suboptimal outcomes. Demos can be misleading: vendors show their best capabilities and skip over weaknesses. Pricing can be opaque: implementation costs, integration fees, and renewal pricing often differ substantially from initial quotes. Operational considerations — implementation methodology, training, ongoing support — often surface only after contract signing when changes are expensive. A structured RFP process addresses these risks by defining requirements upfront, soliciting comparable responses from multiple vendors, validating capabilities through structured demos and reference checks, and documenting the decision rationale. The result: a defensible selection decision aligned with organizational requirements, with documentation supporting later evaluation if the chosen vendor underperforms. The process is more time-intensive than ad-hoc evaluation. Defining requirements takes weeks to months depending on organization size and complexity. Soliciting and evaluating responses takes additional weeks. Demos, references, and final decisions extend the process further. For a major lease software investment serving hundreds or thousands of leases, the time investment is typically justified by the better outcome and reduced risk of replacement.Defined Requirements
Upfront requirement definition produces specific, actionable evaluation criteria rather than impressionistic vendor comparisons.Comparable Responses
Structured RFP solicits responses to the same questions, making comparison across vendors meaningful rather than apples-to-oranges.Validated Capabilities
Structured demos with prepared scenarios and reference checks with similar organizations validate vendor capabilities beyond marketing claims.Documented Decision
Documentation of the decision rationale, criteria weighting, and vendor comparison provides defensibility and supports later evaluation.RFP Process Phases
| Phase | What happens | Scale and timing |
|---|---|---|
| 1. Requirements definition | Functional, technical, commercial and operational requirements defined with stakeholders across accounting, real estate, IT, internal audit and procurement | — |
| 2. Vendor long list | Candidates drawn from analyst reports, industry referrals, peer organizations and industry publications | 8–15 vendors |
| 3. RFP issuance and response | Issued to the long list; responses scored against weighted evaluation criteria | 3–6 weeks to respond |
| 4. Short list and demos | Hands-on demos using prepared scenarios from the actual portfolio, not vendor-controlled walkthroughs | 3–4 vendors |
| 5. References and validation | Reference customers contacted, matched on industry, size and portfolio characteristics | — |
| 6. Final decision and contracting | Decision rationale documented; contract negotiated on commercial terms, implementation methodology, service levels and exit provisions, with legal review before signing | — |
-
1
Phase 1: Requirements Definition
Define functional requirements (what the software must do), technical requirements (how it integrates with existing systems), commercial requirements (pricing, terms), and operational requirements (implementation, support). Engage stakeholders across accounting, real estate, IT, internal audit, procurement, and other affected functions. Document requirements with sufficient specificity to support vendor evaluation. -
2
Phase 2: Vendor Long List
Develop a long list of vendors potentially capable of meeting requirements. Sources include analyst reports, industry referrals, peer organizations, and industry publications. The long list typically contains 8-15 vendors that could potentially fit. -
3
Phase 3: RFP Issuance & Response
Issue the RFP to long-list vendors with sufficient time to respond (typically 3-6 weeks). The RFP should request specific responses to functional, technical, commercial, and operational questions, plus reference customers, security certifications, and other documentation. Score responses against weighted evaluation criteria. -
4
Phase 4: Short List & Demos
Based on RFP scoring, develop a short list of 3-4 vendors for detailed evaluation. Conduct structured demos with prepared scenarios reflecting actual lease portfolio characteristics. Demos should be hands-on (not vendor-controlled walkthroughs) and cover the specific use cases that matter to the organization. -
5
Phase 5: References & Validation
Contact reference customers identified by short-list vendors. References should be similar in industry, size, and portfolio characteristics. Reference questions cover actual implementation experience, ongoing service quality, accuracy of vendor representations, and any surprises encountered post-implementation. -
6
Phase 6: Final Decision & Contracting
Make the final decision based on consolidated evidence from RFP scoring, demos, references, and other validation. Document the decision rationale. Negotiate the contract addressing commercial terms, implementation methodology, service levels, and exit provisions. Engage legal review before signing.
Functional Requirements to Cover
ASC 842 / IFRS 16 / GASB 87 Compliance
Specific standards required by the organization — US GAAP, IFRS, GASB, or multiple. Detailed coverage of classification, measurement, modifications, remeasurements, impairment, terminations, lessor accounting if applicable.Lease Abstraction
Capability to extract structured lease data from PDFs. AI-powered extraction substantially accelerates abstraction; capabilities, accuracy, and human review workflows should be evaluated.Critical Date Tracking
Notifications for renewal options, termination options, escalations, and other lease milestones. Configurability of notification recipients and timing.Reporting & Analytics
Disclosure reports, custom reports, portfolio analytics, and BI integration. Required reports vary by organization; the platform should support both standard and custom needs.Modifications & Remeasurements
Comprehensive handling of lease changes — modifications, remeasurements, terminations, partial terminations, buyouts — with appropriate ASC 842 treatment.Lessor Accounting (if applicable)
For organizations that are lessors as well as lessees, sales-type, direct financing, and operating lease classifications with appropriate accounting.Technical & Commercial Requirements
ERP Integration
Integration with the organization’s ERP — supported ERPs vary by platform. Native integration significantly reduces operational friction.Security Certifications
SOC 1, SOC 2, ISO 27001, or other relevant certifications. SOC 1 supports financial audit reliance; SOC 2 supports broader trust services criteria including security and confidentiality.Deployment Model
Cloud SaaS vs. on-premise. Most modern lease platforms are cloud-based with associated security, availability, and scalability characteristics.Data Migration
Migration of existing lease data from spreadsheets or legacy systems. Migration approach, support, validation methodology, and timeline should be addressed.Pricing Model
Per-lease, per-user, tiered, flat, or hybrid pricing. Implementation costs, integration fees, professional services, renewal pricing terms, and total cost of ownership over the expected term.Exit Provisions
Data export rights, data format, exit assistance, transition support, and contract terms enabling later migration if needed. Avoid lock-in arrangements that prevent practical exit.Implementation & Support
Implementation Methodology
Vendor’s standard implementation approach, typical timelines, milestones, and required customer resources. Implementation methodology often determines success or failure independent of software capabilities.Training Approach
User training methodology, training materials, certification programs, and ongoing training resources for new users. Adequate training is critical for sustained adoption.Ongoing Support
Support tiers, response times, escalation paths, account management, and customer success resources. Ongoing support quality often differs substantially from initial implementation experience.Product Development
Product roadmap, release cadence, customer feedback mechanisms, and accounting standard update commitments. Software in the lease accounting space must continuously adapt to standards changes and customer needs.References from Similar Customers
Reference customers with similar industry, size, and portfolio characteristics validate vendor capability for the specific organization’s needs.Service Level Commitments
Uptime commitments, response time guarantees, and remediation obligations in the contract. Service level commitments matter for business-critical applications.How LeaseCommand Helps
LeaseCommand covers eight capability areas in total — see the full feature set.
LeaseCommand provides infrastructure designed to address requirements typically captured in lease accounting RFPs.AI-Powered Document Extraction
Extract structured lease data from PDFs supporting comprehensive abstraction workflow with substantially reduced manual effort.ASC 842/IFRS 16 Compliance
Automated calculations for ROU assets, lease liabilities, classification, modifications, terminations, and disclosures under both US GAAP and IFRS.Critical Date Notifications
Notifications for renewal options, termination options, escalations, and other lease milestones with configurable recipients and timing.Reporting & Analytics
Disclosure reports, custom reports, and portfolio analytics supporting both standard and custom reporting needs.ERP Integration
Integration with Oracle NetSuite, Sage Intacct, Restaurant365, and QuickBooks Online for journal entry sync.Audit-Ready Documentation
Comprehensive documentation supporting external audit and internal controls requirements.Evaluate Lease Software Systematically
LeaseCommand provides infrastructure addressing the functional, technical, and operational requirements captured in lease accounting RFPs.Related guides









