RFP Checklist for Evaluating Financial Consolidation Software
Most failed software implementations trace back to a poorly constructed RFP. When finance teams evaluate financial consolidation software, the RFP is the single document that determines whether the selected vendor will actually solve the problem or simply add another layer of complexity. A rigorous consolidation software RFP checklist is the difference between a tool that produces audit-ready financials and one that becomes shelf-ware within two quarters.
For groups with 15, 50, or 200 subsidiaries spread across jurisdictions, the consolidation problem is structural. Currency translations, intercompany eliminations, multi-GAAP reporting, minority interest computations, and segment disclosures all need to work together in a controlled, auditable environment. The RFP must reflect this complexity. A generic procurement template will not surface the right vendor.
This post walks through each section your RFP should contain, what to ask, why it matters, and how to evaluate responses. A downloadable template is linked at the end.
1. Functional Requirements: The Core of the Consolidation Software RFP Checklist
Group Structure and Hierarchy Management
Consider an Indian conglomerate with a listed holding company, four intermediate holding companies, and 30 operating subsidiaries across India, Southeast Asia, and Europe. Some subsidiaries are wholly owned, others are joint ventures, and a few are associates accounted for under the equity method. The hierarchy changes every year due to acquisitions, divestments, and internal restructuring.
Your RFP should require the vendor to demonstrate how their software handles n-level hierarchies with drag-and-drop restructuring, multiple holding companies under a single uppermost parent, and the ability to maintain parallel hierarchy views (legal entity, business unit, geography). Ask specifically: can a new entity be added and configured within a single working day? Can holding percentages be changed mid-period without rebuilding the consolidation from scratch?
Multi-GAAP and Multi-Period Support
Groups reporting under IndAS to Indian regulators, IFRS to a foreign parent, and local GAAP in specific jurisdictions need the software to produce all three sets of financials from the same underlying data. The RFP should require the vendor to explain how multiple reporting frameworks coexist within one installation, whether account groupings can be independently configured per GAAP, and how the system handles different fiscal year-ends across entities.
Ask for specifics on period handling. Can the system consolidate monthly, quarterly, half-yearly, and annually? Can it handle a subsidiary with a March year-end rolling into a parent with a December year-end? These are not edge cases for Indian groups with global operations. They are standard requirements.
Currency Translation and FCTR
Foreign currency translation is where many consolidation tools fall short. The RFP should require the vendor to describe how the system maintains a foreign exchange rate master, supports multiple rate types (closing rate, average rate, historical rate), and automatically computes the Foreign Currency Translation Reserve. Ask whether the FCTR reconciliation is fully automated and whether the system handles rate differences between the current rate and the rate at the time of original investment.
A group with subsidiaries in Thailand, the UK, and Brazil will have three different functional currencies translating into INR. Each balance sheet line item may use a different rate type. The consolidation software must handle this without manual intervention beyond rate entry.
Intercompany Eliminations and Reconciliation
Intercompany transactions are the largest source of consolidation errors and audit queries. Your RFP should ask the vendor to describe the elimination workflow in detail. Specifically, does the system support a collaborative model where Company A enters its figures for transactions with Company B, and Company B verifies and confirms? Can eliminations be processed in both the originating foreign currency and the base reporting currency?
Also ask about reconciliation reporting. Auditors from firms like Deloitte, KPMG, and BSR will want to see a complete trail of every intercompany balance, the elimination entry, and any unreconciled differences. The software should produce this natively.
Minority Interest, Associate Accounting, and Consolidation Entries
Automated NCI (Non-Controlling Interest) computation based on holding percentages and user-definable formulas should be a baseline requirement. The RFP should also cover how the system handles entries that do not originate from any subsidiary’s trial balance, such as goodwill impairment on acquisition or fair value adjustments at the holding company level. These consolidation-level journal entries need their own audit trail.
Cash Flow, Segments, and Notes to Accounts
Cash flow statement generation (indirect method), segment reporting with inter-segment adjustments, and notes to accounts with linked numbers are all areas where manual processes consume weeks of effort. Ask the vendor whether cash flow statements can be generated at both standalone and consolidated levels, whether segment P&L and segment assets/liabilities are natively supported, and whether notes to accounts can include dynamic placeholders for prior period figures.
For a detailed breakdown of functional capabilities to look for, the key features guide for financial consolidation tools covers this in depth.
2. Technical Requirements
The technical section of your RFP should cover deployment, integration, security, and scalability. Use the following table as a framework for structuring your questions to vendors.
| Technical Area | What to Ask | Why It Matters |
|---|---|---|
| Deployment Options | Cloud (SaaS), on-premise, or hybrid? What infrastructure is required? | Many Indian enterprises have data residency requirements or prefer on-premise for financial data |
| Database | Which databases are supported? Oracle, SQL Server, others? | Must align with existing IT infrastructure and DBA capabilities |
| Integration | How does the system import trial balance data? Which ERPs and accounting systems are supported? | Groups with SAP at the parent, Oracle at one subsidiary, and Tally at another need a system that works with all of them |
| Browser/Client | Is the system fully browser-based? Any client-side installations? | Distributed teams across time zones need browser-only access |
| Security | Role-based access controls? Audit trail of all user actions? | SEBI-listed companies need demonstrable controls over financial data access |
| Scalability | Maximum number of entities, accounts, and concurrent users tested? | Groups planning acquisitions need headroom |
One critical question often missed: does the system require IT involvement for day-to-day operations? For finance teams at regulated enterprises, the ability to run the entire consolidation cycle, from TB import to final report generation, without raising IT tickets is a significant operational advantage. The system should be designed so that functional finance users operate it independently after initial setup.
3. Implementation Approach
Implementation timelines and methodology separate serious vendors from those who rely on long, expensive consulting engagements. Your RFP should require vendors to provide a detailed implementation plan with milestones, resource requirements (both vendor-side and client-side), and a clear definition of “go-live.”
Ask these specific questions: How many weeks does implementation take for a group with 15 entities and two prior periods? What does the implementation team look like, specifically whether it includes finance domain experts (such as Chartered Accountants) alongside technical consultants? What is the training model, and how many days until end users are self-sufficient?
Consider what a realistic timeline looks like. For a group with 15 subsidiaries, a well-structured implementation should complete in 6 to 8 weeks. The first cycle should involve the vendor team working alongside your finance team to import historical data, run through the full consolidation process, and verify that the final consolidated report matches your previously published numbers to the last penny. The second cycle should see your team running the process with the vendor in a support role. By the end of the second cycle, your team should be fully independent.
Vendors who propose 6-month or 12-month timelines for a group of this size are either over-engineering the solution or lack domain expertise. For more on what realistic timelines look like, see this analysis of consolidation software implementation speed.
4. Support Model
Post-implementation support is where many vendor relationships deteriorate. The RFP should require vendors to detail their support structure, response time SLAs, escalation paths, and the composition of the support team.
A critical question for consolidation software specifically: does the support team include people with financial domain expertise, or is it purely a technical helpdesk? When your team calls with a question about FCTR computation or NCI treatment during a quarter-close, the person on the other end needs to understand the accounting, not just the software interface. Support teams that combine CA-qualified professionals with technical specialists resolve issues faster and with fewer back-and-forth cycles.
Also ask about regulatory update handling. When the ICAI issues new guidance on IndAS implementation, or when IFRS standards are updated, how does the vendor incorporate those changes into the software? Is there a regular update cycle? Are updates included in the annual maintenance fee?
5. Pricing Structure
Pricing transparency in your consolidation software RFP checklist prevents surprises in year two and beyond. Require vendors to break down their pricing into the following components.
| Pricing Component | What to Clarify |
|---|---|
| License or Subscription Fee | Per-user, per-entity, or flat? Annual escalation clause? |
| Implementation Fee | Fixed or time-and-materials? What’s included (data migration, training, parallel run)? |
| Annual Maintenance / Support | Percentage of license fee? What’s covered? |
| Add-on Modules | Budget vs. Actual, custom report generators, notes to accounts: included or separate? |
| Infrastructure Costs | For on-premise: server specs. For cloud: hosting fees, data storage limits |
| Additional Entity Costs | What is the cost when the group acquires a new subsidiary? |
Total cost of ownership over a 5-year horizon is the right evaluation metric, not the year-one license fee. A tool with a low entry price that requires expensive consultants for every configuration change will cost significantly more over time than a higher-priced tool that your finance team operates independently. The TCO analysis for financial consolidation software provides a framework for making this comparison accurately.
6. References and Client Validation
Vendor-provided references are always favorable, but the RFP should structure this section to extract maximum value. Require at least three references from organizations of comparable size and complexity, ideally in similar industries or regulatory environments.
When speaking with references, ask these questions: How long did implementation actually take versus the vendor’s original estimate? How many consolidation cycles did it take before the team was fully independent? Has the consolidated output ever failed to match published figures? How responsive is support during quarter-close crunch periods? Have there been any regulatory or GAAP update delays?
For Indian groups, references from companies reporting under IndAS with international subsidiaries reporting under IFRS or local GAAP carry more weight than references from single-GAAP environments. The complexity profile of the reference should match yours. A vendor with clients like large listed Indian conglomerates, financial services groups, and multinational manufacturers has likely encountered and solved the specific challenges your group faces.
7. Demo Evaluation Criteria
A structured demo evaluation prevents the common trap where a polished sales demo obscures functional gaps. Before the demo, provide the vendor with a sample of your actual data (anonymized if necessary) and ask them to demonstrate the following scenarios using your data, not their canned demo dataset.
Scoring Framework for Demos
| Evaluation Area | Weight | What to Observe |
|---|---|---|
| TB Import from Multiple Systems | 15% | Can the system import from SAP, Tally, and Excel in a single consolidation cycle? |
| Hierarchy Setup | 10% | How quickly can a new subsidiary be added with correct holding percentages? |
| Currency Translation | 15% | Demonstrate FCTR computation with at least three currencies |
| Intercompany Elimination | 15% | Show the full workflow: entry, verification, elimination, reconciliation report |
| Report Generation | 15% | Consolidated BS, P&L, Cash Flow, Segment Report: are they print-ready? |
| Audit Trail | 10% | Drill down from a consolidated line item to the originating entity’s GL entry |
| User Independence | 10% | Can a finance user (not a consultant) perform all the above steps? |
| Ad-hoc Reporting | 10% | Can the finance team build a custom MIS report without IT involvement? |
During the demo, pay attention to how many clicks each process takes, whether the interface language uses accounting terminology that your team will recognize, and whether the presenter is a finance professional or a technical sales engineer. The best consolidation tools are built by teams that understand accounting, and that shows in the interface design and workflow logic.
8. Downloadable RFP Template Structure
Your final RFP document should follow this structure. Each section should include specific questions, required response format, and evaluation weightage.
| Section | Contents | Suggested Weightage |
|---|---|---|
| Company Overview | Vendor background, years in business, team composition, client list | 5% |
| Functional Requirements | Hierarchy, multi-GAAP, currency, eliminations, NCI, cash flow, segments, notes | 30% |
| Technical Requirements | Deployment, integration, security, scalability, IT independence | 15% |
| Implementation Approach | Methodology, timeline, team composition, training plan | 15% |
| Support Model | Team composition, SLAs, domain expertise, regulatory updates | 10% |
| Pricing | 5-year TCO breakdown across all components | 15% |
| References | Minimum three comparable clients with structured reference check questions | 5% |
| Demo | Scored evaluation using client data, not vendor demo data | 5% |
When assembling the final scoring, functional requirements and pricing (on a TCO basis) should collectively carry at least 45% of the total weight. Implementation speed and support quality, often underweighted in procurement-led evaluations, directly determine whether the tool will actually be used effectively by quarter two.
Putting the Checklist to Work
A well-constructed consolidation software RFP checklist does more than help you pick a vendor. It forces your own team to articulate exactly what the consolidation process needs to look like, where the current pain points are, and what “success” means in measurable terms. The exercise of writing the RFP often surfaces internal process gaps that need to be addressed regardless of which tool you select.
For groups evaluating consolidation tools, eMerge by Soft Corner is one product worth putting through this checklist. It has been in production for many years across Indian conglomerates, financial services firms, and multinationals, handling multi-GAAP consolidation, automated FCTR, intercompany eliminations, and complete audit trail requirements. Its implementation model, built around CA-qualified consultants working alongside your finance team, is designed to produce independence within two consolidation cycles.
If you are at the stage of building your shortlist or preparing demo evaluations, requesting a walkthrough with the eMerge team using your own group structure and data will give you a concrete benchmark against which to evaluate other vendors on your list.
