Questions to ask every reconciliation software vendor

As noted in r/Accounting, eventually your team may grow out of Excel and need a more robust reconciliation solution. Most reconciliation software demos show you the best-case scenario: clean data, simple 1:1 matching, and a polished dashboard built on pre-configured examples. 

That’s why it’s essential to prepare questions to ask every reconciliation software vendor.  The questions in this guide are the ones vendors are least prepared for, covering data ingestion with your actual formats, many-to-many matching, implementation reality, audit trail completeness, and who owns configuration after go-live. 

Ask these reconciliation software demo questions before you sign, not after.

TL;DR

• Request a live demo using your actual data format, not the vendor's prepared dataset.
• Ask who makes rule changes after go-live and how long it takes.
• Get the implementation timeline committed to in writing before signing.
• Ask to see the full audit trail including rule change history, not just matched outputs.
• Watch for vague answers and "that's handled in professional services." Both are red flags.

Implementation and IT dependency questions (ask these first)

Implementation failure is the most common reason reconciliation software projects stall. Determine what to ask reconciliation vendors before evaluating any features. A platform that takes six months to deploy and requires IT for every change may not be worth evaluating further regardless of its feature set.

"How much internal IT resource does implementation require? Can you show me a project plan?"

A credible answer: The finance team owns deployment, IT involvement is minimal and front-loaded, and a typical first reconciliation type goes live within weeks. Be cautious of vendors who cannot give a specific timeline. According to Smartsi's BlackLine implementation guide, BlackLine implementations typically take 3 to 6 months and require a dedicated system administrator.

"When matching rules need to change, who makes the change and how long does it take?"

A credible answer: A finance user changes the rule directly in a drag-and-drop builder, the change is live within minutes, and no IT involvement is required. If the answer involves raising a ticket or waiting for professional services, the finance team will have traded Excel dependency for IT dependency.

"What happens if we want to add a new data source six months after go-live?"

A credible answer: The finance user adds the connector in the platform's no-code builder without IT involvement or a professional services engagement. If adding a data source requires a new statement of work, factor that cost into the total cost of ownership before signing.

Data ingestion and integration questions (the ones demos skip)

Most demos run on a single, clean data source prepared by the vendor. Real reconciliation environments pull from multiple systems simultaneously, each with different formats, schedules, and data structures. 

According to Intuit's 2024 Business Solutions Survey, 91% of finance professionals say manual data wrangling has undermined their productivity, which is exactly what happens when a platform cannot ingest your actual data environment cleanly.

"Show me how you handle many-to-many matching with real data, not a prepared example."

A credible answer: The vendor runs a live matching scenario against messy, real-world data with configurable rules, not a curated 1:1 demo dataset. If the vendor switches to a prepared example when asked, assume their tool will not handle your real environment.

"What ERPs, banks, and payment gateways do you connect to natively?"

A credible answer: Specific named connectors, not "we integrate with most systems." Look for named ERP connectors, such as NetSuite, Xero, Microsoft Dynamics 365, and Oracle, plus API connectivity to major PSPs including Stripe, Adyen, and PayPal, and file-based SFTP connections for sources that do not support API access.

"How long does a new data source take to connect after go-live?"

A credible answer: Hours to days for standard connectors, with no developer involvement required for sources that support API or SFTP connectivity. If adding a connector requires a professional services engagement, factor that cost and timeline into your total cost of ownership calculation.

Matching logic and configurability questions

Matching logic is where reconciliation software either earns its cost or creates a new set of problems. These questions reveal whether the platform handles your real complexity or only the simple version shown in demos.

"Show me what an exception looks like. What context does the system provide to resolve it?"

A credible answer: Each exception surfaces with full transaction context from both sides of the mismatch, aging information showing how long the item has been unresolved, categorization by exception type, routing to the assigned reviewer, and a resolution history log. If the vendor shows only a list of unmatched items with no surrounding context, the exception workflow is not built out. The remaining exceptions after matching are where most of the manual work lives; context determines how fast they resolve.

"Can finance users change matching rules without IT, and how is that audited?"

A credible answer: A finance user opens a drag-and-drop rule builder, makes the change, and the updated rule is live without IT involvement. Every rule change is logged with user ID and timestamp. If the answer involves raising a ticket or contacting professional services, IT dependency has not been eliminated.

"What is your typical auto-match rate in real customer deployments — not in the demo?"

A credible answer: A specific numeric range such as 80 to 95%, with reference to customer deployments in a similar industry and transaction volume. A vague "very high" claim is not an answer. Ask for customer references who can confirm the match rate in a real multi-source environment.

Multi-currency and FX questions (often skipped, costly if ignored)

Multi-currency handling is one of the most common gaps discovered after signing, not during the demo. If your business operates across borders, raises invoices in one currency, and settles in another, ask these questions before evaluating any other feature.

"Can it handle multiple currencies natively, or does conversion happen outside the platform?"

A credible answer: Multi-currency matching is built into the core matching engine, not handled via a manual pre-processing step or external spreadsheet. If currency conversion happens outside the platform before data is ingested, the reconciliation is already compromised before it starts.

"How does it manage FX rate conversions and revaluations, daily rates, period-end rates, or both?"

A credible answer: The vendor explains the rate source clearly, whether a central bank feed, an ERP-fed rate table, or a configurable rate schedule, and confirms whether revaluation runs automatically at period close or requires manual intervention.

"What happens when a payment settles in a different currency than the invoice was raised in?"

A credible answer: The FX variance is handled as part of the matching logic, within configurable tolerance thresholds, and does not generate a manual exception every time. If the answer is that cross-currency settlements always create exceptions, the platform is not built for multi-currency environments. Raise this question early if you operate cross-border or across multiple entities. The answers determine fit, not just feature coverage.

Payment reconciliation questions (chargebacks, refunds, fees)

Generic "connects to payment gateways" claims do not reveal whether a platform can handle the real complexity of payment reconciliation. These questions go deeper. Ask them if your environment includes multiple payment providers, high transaction volumes, or complex fee structures.

"Can it reconcile across multiple payment providers, gateways, and acquiring banks in a single workflow?"

A credible answer: Yes, with a single consolidated view across all providers rather than separate reconciliations per gateway that the finance team manually combines. Ask the vendor to demonstrate this with more than one payment provider in the same workflow.

"How does it handle high-volume, high-speed transactions, card payments, direct debits, digital wallets?"

A credible answer: The vendor cites a specific volume benchmark from a real deployment, not a generic "it scales" claim. Solvexia reconciles payment gateways, POS systems, and bank data for 7-Eleven, processing at 100x faster than their previous manual process.

"How does it identify and flag discrepancies like chargebacks, refunds, and partial payments?"

A credible answer: Chargebacks, refunds, and partial payments are treated as distinct exception categories with their own matching logic, not grouped into one generic unmatched bucket.

"Can it reconcile processor fees and commissions against agreed rate cards?"

A credible answer: The platform ingests the rate card and flags variances automatically, rather than requiring a manual cross-check in a spreadsheet after each settlement cycle.

AI and intelligent automation questions (what auditors will ask)

As more vendors market "AI-powered matching," procurement teams and auditors are starting to ask harder questions about what the AI actually does and how its decisions can be explained. These questions separate genuine capability from marketing language.

"How are you using AI or machine learning to improve matching accuracy?"

A credible answer: The vendor explains specifically what the AI or ML does, fuzzy matching on reference number variations, anomaly detection, pattern learning on recurring exceptions, not just "we use AI." Vague AI claims with no functional explanation are a red flag.

"How do you ensure transparency and explainability in AI-driven matches?"

A credible answer: Every AI-suggested match can be traced back to the specific rule or pattern that triggered it. A black-box decision that cannot be explained to an auditor is a compliance risk, not a feature.

"What audit trail exists for AI-driven decisions? Can we see why a match was made or flagged?"

A credible answer: AI-driven matches are captured in the audit trail with the same level of detail as rules-based matches, including the logic applied and the confidence threshold used.

"What ongoing support and monitoring do you provide for AI capabilities once live?"

A credible answer: A clear explanation of whether AI models are monitored, retrained, or adjusted post-go-live, and by whom.

Honest note: If a vendor's matching is primarily rules-based rather than AI-driven, that is not automatically a gap. Rules-based matching is deterministic, fully explainable, and easier to audit, which is why some finance teams and auditors prefer it. A vendor that is transparent about this distinction is more trustworthy than one that overstates AI capability.

Exception management questions

According to Kani Payments' 2025 research of 250 UK payments professionals, not one said their reconciliation process was completely error-free. Exceptions are not an edge case; they are a guaranteed part of every close cycle. These questions to ask every reconciliation software vendor  reveal whether a platform manages them well or simply buries them in a queue.

"Walk me through resolving an exception end-to-end, not just flagging it."

A credible answer: The vendor demonstrates the full resolution workflow, showing aging information, exception categorization, automatic routing to the right reviewer, and an audit log of how the exception was resolved and by whom. If the demo stops at flagging the exception without showing resolution, the workflow is not built out.

"What happens to exceptions that are never resolved? Do they expire, escalate, or sit indefinitely?"

A credible answer: Configurable aging rules with automatic escalation after a defined period. Exceptions that sit indefinitely in a queue without escalation become a control risk.

"Can I see your real exception rate, not your match rate?"

A credible answer: A specific number with an explanation of what drives it, whether data quality, matching complexity, or transaction type mix. A vendor who deflects to match rate alone when asked about exception rate has not thought carefully about the other half of the process.

Approval workflow and audit trail questions

Audit trail and approval workflow questions are where compliance requirements meet day-to-day operational controls. These questions reveal whether a platform enforces controls or merely offers them as optional settings that can be bypassed.

"Show me the full audit trail for a reconciliation, including who changed which rule and when."

A credible answer: The vendor demonstrates a complete history of all matches, approvals, modifications, and rule changes, each with a user ID and timestamp. An output-only audit trail that shows what matched but not who changed the matching logic will not satisfy SOX or external audit requirements. Ask specifically to see rule change history, not just the reconciliation output.

"Does the platform enforce segregation of duties, or just allow it?"

A credible answer: Configurable approval workflows that structurally prevent a single user from completing the full reconciliation workflow without a second approver. A permissions setting that can be turned off or bypassed is not enforced segregation of duties. Ask the vendor to demonstrate that the workflow cannot be completed without the required approvals in place.

"Can auditors get read-only access without being able to modify anything?"

A credible answer: A dedicated read-only auditor role with full visibility into matches, exceptions, approvals, and rule history, and zero modification capability. Ask the vendor to log in as the auditor role during the demo and show what is and is not accessible. 

Pricing and total cost of ownership questions

License cost is rarely the number that surprises buyers. Implementation fees, professional services charges, per-connector costs, and year-two pricing are where the real total cost of ownership emerges. Ask these questions before any commercial discussion begins.

"What is the full cost: License, implementation, professional services, training, and year-two+ pricing?"

A credible answer: A complete cost breakdown covering all components, not just the license fee. A vendor who cannot give a total cost estimate at the evaluation stage is a vendor whose costs will surprise you after signing. Enterprise reconciliation platforms can range from $77,000 to $340,000 per year when implementation and administration costs are included, according to Transformance.ai.

"Is there a fee for adding data sources or making configuration changes after go-live?"

A credible answer: No additional fee for a no-code platform; configuration changes and new data source connections are handled by the finance team within the platform at no extra cost. If the answer involves professional services or a change request process, add that to your total cost of ownership calculation.

"What does year-two pricing look like compared to year one?"

A credible answer: Transparent, predictable pricing with no steep renewal increase. Ask for the renewal terms in writing before signing the initial contract. Introductory pricing that resets significantly at renewal is a common pattern, verify it does not apply before committing.

The demo scenarios to request (not just the polished one)

Every vendor has a polished demo flow designed to show the platform at its best. The real evaluation happens when you ask for scenarios outside that flow. Send these requests to the vendor at least one week before the demo: 

1. Run the demo on your actual data export, anonymized if needed. Not the vendor's curated dataset. If the vendor declines or needs significant preparation time, that is a signal about how the platform handles real-world data variety.
2. Show a transaction that does not match cleanly, and demonstrate how the system surfaces and routes it. Watch what the exception view shows: context, aging, categorization, and routing, not just a flag.
3. Show what happens when a data source is temporarily unavailable or sends malformed data. Does the platform fail silently, alert the team, or pause and wait? The answer matters for daily operations.
4. Make a live rule change during the demo, not a description of how rule changes work. Time how long it takes and note whether IT is involved.
5. Show the audit trail for a transaction that was modified after initial matching. Verify that the modification is logged with user ID, timestamp, and the before and after state.

Red flags in vendor responses — what to watch for

When putting together your vendor evaluation checklist and planning which questions to ask every reconciliation software vendor, watch for these red-flag responses:

1. Vague implementation timeline with no specific week or month commitment. A confident vendor gives a written timeline. Vagueness protects the vendor, not the buyer.
2. Inability to demo many-to-many matching with real data. If the vendor switches to a prepared 1:1 example when asked, assume their tool cannot handle your real environment.
3. "That's handled in professional services" for basic rule changes or new data source requests. This means IT or external consultants own your configuration after go-live.
4. Cannot show a specific audit trail on demand. Describing the audit trail verbally is not the same as demonstrating it.
5. Deflects pricing questions or will not quote total cost including implementation and year-two pricing. Cost surprises after signing are a pattern, not an accident.
6. Claims 100% or near-100% auto-match rate without context. Realistic auto-match rates in complex, real-world environments are 80 to 95%. 
7. Cannot name a specific exception rate from real deployments. Match rate and exception rate are different numbers. A vendor who only quotes match rate has not thought carefully about the other half of the process.
8. Segregation of duties described as "possible" rather than "enforced." Ask the vendor to demonstrate that the workflow cannot be completed without required approvals in place.

How to run a fair reconciliation software RFP

A structured RFP process protects buyers from being sold the polished version of a product rather than the real one. Here are five steps that make the difference, along with reconciliation software RFP questions to ask:

1. Define your evaluation criteria before inviting any vendor. Criteria set after seeing demos are criteria shaped by vendor positioning. Start with the questions that matter to your environment.
2. Ask all vendors exactly the same questions from this list. Consistency across vendors is what makes comparison meaningful. 
3. Require a live demo using your own data, not a vendor-prepared dataset. If a vendor cannot demo on your data, they cannot guarantee performance in your environment.
4. Ask for customer references in your industry and company size, not just logo lists. A reference from a comparable organization is worth more than several logos from unrelated sectors.
5. Request the same pricing breakdown from every vendor: License, implementation, professional services, training, and year-two pricing.

When this level of scrutiny may be overkill

Not every reconciliation evaluation needs all 20+ questions in this guide. If you are processing under 1,000 transactions per month from a single data source with stable formats and no compliance pressure, a lighter evaluation is genuinely appropriate. Excel or an ERP-native module may be sufficient, and running a full RFP process for a low-complexity use case adds cost and delay without proportionate benefit.

Focus on the four or five questions most relevant to your situation. For single-source, low-volume environments, the most important questions are implementation timeline, who owns configuration changes, and whether the audit trail meets your compliance requirements. The full question set in this guide is designed for mid-market to enterprise teams with multi-source data complexity, meaningful transaction volumes, and audit or compliance requirements that demand more than a spreadsheet can provide.

Conclusion: how Solvexia answers these questions

Every good answer described in this guide, including finance-led implementation, no-code rule changes, many-to-many matching demonstrated on real data, complete audit trails, including rule change history, and transparent pricing, is what Solvexia delivers in practice.

These questions to ask every reconciliation software vendor were written to be brought to any vendor demo to help you evaluate reconciliation solutions, including ours. Book your Solvexia demo today.