When comparing treasury software, I would ask to trace a customer payment from its source document to the bank transaction and reconciliation record. A balance on a dashboard does not establish that the team can explain a discrepancy, spot stale information or correct an incorrect match while preserving its history.
This guide is for a finance lead choosing a product or commissioning connections between banking data, payment collections and an ERP. The engagement covers software, data and operations. Financial, accounting and tax decisions remain with their respective owners. I would start with one verifiable workflow before scoping a complete platform.
Define the information your team must be able to explain
Map legal entities, accounts, currencies, collection sources and ERP documents. For each source, name an owner and record how data arrives, what identifies a record and when it is updated. Confirm available access with the providers and your actual accounts; do not assume every bank or ERP edition offers the same connection.
Distinguish bank transactions, recorded receipts, outstanding documents and forecasts. Agree which date each view uses and retain original dates needed to investigate discrepancies. A forecast should expose its assumptions and version rather than appear as a confirmed movement. An old balance needs its update time and a warning, not the appearance of fresh data.
Decide who proposes a match, who confirms it and who can reverse it. If several invoices have similar amounts, amount and date may help suggest a match, but they are not a universal reconciliation rule. Identify cases requiring review and the reason the responsible person will see.
If you need to explain a project cost before reconciling its payment, the construction software matrix separates budgets, approved progress, remaining commitments and allocated costs.
For a teaching academy, a payment also needs its student, enrolment and fee period. The academy software matrix adds group transfers, shared payers and withdrawals before reconciling the receipt.
If the discrepancy starts with what the customer accepted, review the sales management software matrix. It separates quote revisions, partial acceptance and confirmed orders before those documents reach collections.
Buy a product, connect existing systems or build a component
Existing product: when it covers your accounts, sources, permissions and exceptions, the engagement may be configuration, migration and acceptance testing. Request a demonstration with fictional data representing your workflow and the edition you would purchase. Establish which connections are included and which need another agreement.
Integration: this fits when the ERP and collection tools work individually but the team exports and matches records manually. Scope read access, reconciliation proposals and authorized ERP writes separately. Reading transactions does not imply payment initiation. The Odoo Shopify integration guide covers order and stock exchange; here, acceptance ends with an explained receipt and its documentary links.
Custom component: I would consider it for a necessary rule that verified alternatives cannot cover. Isolate that component and its maintenance. I would not build a replacement if configuration solves the problem. If access is unconfirmed or historical data quality is unknown, start with a bounded assessment that delivers samples, dependencies and a revised scope.
An acceptance matrix for treasury software
Give every supplier the same cases. Mark each included, configurable, additional development or excluded; add an owner, cost, expected result and evidence. These are proposed evaluation criteria, not completed product tests or client results.
| Case | Requirement to commission | Acceptance evidence |
|---|---|---|
| Repeated import | Record identity by source and account, including corrected records. | Importing the sample twice does not duplicate transactions. Two legitimate transactions of the same amount remain distinct. |
| Partial receipt | Link the applied amount, document and remaining balance. | A partial receipt leaves the remainder open. Repeating the event does not apply the amount again. |
| Grouped settlement | Link receipts, adjustments and the net bank transaction through verifiable references. | The gross-to-net difference is explained; an unexplained discrepancy stays pending without an invented adjustment. |
| Refund or correction | Retain the original relationship and authorize reversal of a match. | A correction preserves its author, reason and previous states rather than silently deleting history. |
| Interrupted source | Visible data age, alert, recovery procedure and owner. | Disconnect the source: stale data is identified, and recovery detects gaps without duplicating records. |
| Permissions and exit | Access by entity and role; export relationships and unresolved items. | An unauthorized user cannot confirm matches or view restricted data. Another owner can reconstruct the exported sample. |
Also agree volumes, acceptable delay, historical coverage and currency handling. Do not combine amounts in different currencies without an explicit conversion rule and a traceable exchange-rate source. The finance owner validates those rules; the supplier demonstrates their implementation.
Example: the bank deposit differs from gross collections
Hypothetical example: a provider settles several collections together, deducting fees and a refund. Proposal A matches the bank deposit to a single invoice. Proposal B preserves the settlement breakdown, links its components and exposes unresolved differences. They deliver different behavior even if both advertise automatic reconciliation.
I would ask suppliers to reproduce the settlement, import it again and remove one reference. The system should explain what it can match and leave the unknown item for review. If a refund appears in another settlement, it should retain its relationship rather than be assigned by date proximity. Manual intervention can be acceptable when it has an owner and a recorded explanation.
Then test an authorized correction. Show which relationship changed, why and which documents become outstanding again. Acceptance should establish that the workflow can be reconstructed, rather than forcing a discrepancy-free dashboard through unexplained adjustments.
Scope, deliverables and switching systems
A first release might cover one legal entity, agreed accounts, one collection source and one ERP, with import and supervised reconciliation. Write down exclusions: payment execution, financing decisions, tax filings, complete accounting and unnamed connections. Any ERP write needs its own permissions, rules and acceptance checks.
Request a source inventory, field and state dictionary, versioned rules, contracted configuration or code, synthetic-data test evidence, exception records, recovery instructions and training. Define account control, rights to delivered materials, applicable source-code access and handover terms. The software quote guide helps turn those deliverables into comparable milestones.
For migration, agree a cutoff, historical coverage, open documents and previous reconciliations. Rehearse a sample and compare counts, totals by account and currency, and documentary relationships. Name the person approving discrepancies. During parallel operation, identify which system may write so a receipt is not applied twice. Returning to the previous system requires preserving and reconciling work processed during transition.
Implementation, maintenance and exit costs
Separate licenses, source access, analysis, data cleanup, configuration, connectors, migration, testing and training. Effort depends on accounts, entities, currencies, reference quality, update frequency and exceptions. Ask for each item's assumptions and unresolved checks before treating a quote as fixed.
Over the same comparison period, include subscriptions, hosting where applicable, support, interface changes and internal reconciliation work. Verify each offer's billing units and renewal terms. The software total-cost model organizes these obligations without inventing rates or savings percentages.
Maintenance should assign responsibility for expired access, incomplete imports and format changes. Agree coverage, incident priorities and a manual fallback. Distinguish fixing an accepted requirement from adding a bank or a new rule. Include exports of data, relationships, rules and pending work, access revocation and a usable handover when changing suppliers.
What to send me to scope the engagement
Describe your ERP and collection tools, approximate account and entity counts, currencies, required update frequency and manual tasks. Include a fictional settlement with an exception, the reconciliation approver and budget or timing constraints. I do not need credentials, real bank statements or personal records for that initial discussion.
I can review a business software development or integration engagement with you to retain what works and scope the first delivery. You can share your treasury workflow so we can define sources, exclusions and acceptance criteria.