Payment Settlement Reconciliation Software: Custom Build or Duco, SmartStream and Kani
Buy. One processor, one currency and a daily file that already balances to the deposit means a matching tool plus a disciplined close is enough, and building would be an expensive way to automate two analyst hours a month.
On this page
Buy. One processor, one currency and a daily file that already balances to the deposit means a matching tool plus a disciplined close is enough, and building would be an expensive way to automate two analyst hours a month. Build once you run three or more acquirer connections, more than one currency or legal entity, or hold funds for other people.
What the off-the-shelf products actually do well
There are four kinds of product sold into this problem and they solve different halves of it, which is why buyers end up with two subscriptions and still reconcile in Excel.
Duco is genuinely good at self service data matching. A finance team can load two files, define a match, and be productive in an afternoon without an implementation project, which is a real capability and rare in this category. SmartStream Transaction Lifecycle Management and Gresham Clareti are serious enterprise matching engines with long track records, implemented and priced the way enterprise programmes are. Kani Payments is purpose built for fintech and programme manager reporting and onboards quickly when your model resembles the one it was designed around. AutoRek sits close to that space with a controls emphasis.
Then there is the ledger side. Modern Treasury and Ledge are strong on bank payment operations and ledgering, and if your pain is bank to processor matching with straightforward fee logic, one of those is a better purchase than a build and rebuilding it to save a subscription is poor arithmetic.
All of them will tell you matched or unmatched. That is the honest boundary of the category, and for a great many companies it is enough.
Where they stop: the lifecycle, the rate card and the journal
Three things sit outside every matching product, and they are the three that keep your close open.
The first is lifecycle. An authorisation, a capture, a partial refund, a second partial refund, a chargeback, a representment and a final funding line are seven events describing one customer purchase, spread across weeks and arriving from three sources. Reconciliation is not pairing rows. It is assembling that group, holding it open until it reaches a terminal state, and asserting that the money nets to what the ledger says it should. Row pairing works in testing and fails in week three, usually on the second partial refund.
The second is your contract. Your acquirer agreement has an interchange plus structure with a negotiated markup, specific scheme fee pass throughs and a monthly minimum. What lands is a net figure. Almost nobody checks it, because checking means recomputing expected cost per transaction from card type, region, entry mode and merchant category, then adding scheme fees and the markup. Do it once and you find downgrades caused by your own authorisation data quality, which is a fixable engineering problem worth real basis points, fees charged on transaction types the contract excludes, and cross border assessments on domestic transactions.
The third is the journal. A break queue living in a separate tool and producing a monthly summary changes nothing, because the finance team still posts by hand and the suspense account still grows. Matched groups should post automatically with the correct split across gross revenue, processing cost, chargeback loss and foreign exchange gain or loss, carrying a reference that lets an auditor walk from journal line to source file row in two clicks. Unmatched items post to a controlled suspense account with an owner and an age.
The tell that you have crossed the boundary: an adjustment line on a funding advice that references nothing in your system, and nobody can say what it was.
The arithmetic: matching tool pricing against analyst days
Matching products price either per named user or against matched volume, and both scale in the wrong direction for a growing payments business. Work the comparison in three numbers rather than one.
Take the annual subscription. Add the analyst days: count the working days your close waits on settlement, multiply by the fully loaded daily cost of the people involved, and multiply by twelve. Then add the amount currently sitting unallocated in suspense, because unreconciled settlement is unrecognised revenue and that balance is the real cost of the arrangement.
The crossover in this category tracks connections rather than volume, which surprises people. One processor, one currency, one entity: buy, at any transaction count, because the file already balances and a tool plus discipline closes the gap. Two processors: still buy in most cases. Three or more processor or scheme connections, or two currencies, or two legal entities funded from one processor account, and the subscription plus analyst days typically passes a first release cost within eighteen months. Past roughly two million transactions a month with multiple connections the case is no longer marginal, because at that point the fee validation alone tends to recover more than the build.
What a custom build actually costs
From Digital Heroes delivery experience, a first release covering ingestion for your live processor and bank connections, lifecycle level matching against your ledger, and a break queue with categories, owners and aging runs $70,000 to $160,000 and ships in 12 to 16 weeks. A full platform adding interchange and scheme fee validation against contracted rates, foreign exchange handling, chargeback and refund lifecycle matching, automated journal posting and multi entity support runs $200,000 to $500,000 across 6 to 14 months.
Migration runs 10 to 25 percent of first release cost and it is almost entirely historic backfill. Reconciling the last two years rather than starting clean is a scope decision with a price, not a free extra, and it sits at the top of the range when older files were archived in a format nobody kept a parser for. Year two costs 15 to 20 percent of build cost annually, driven by file grammar changes that arrive without notice, scheme fee structure updates, and rate card revisions each time you renegotiate.
What pushes cost up: the number of processors and schemes, since each is a distinct file grammar; multi currency, because foreign exchange turns every tolerance into a policy question; multi entity structures where one processor account funds several legal entities and the split has to be derived; and marketplace or facilitator models where you reconcile sub merchant balances and reserves rather than only your own money. The cheapest week in the project is usually fixing your own data upstream, because a ledger that does not store the acquirer reference on each transaction makes the first matching pass far harder than it needs to be.
The four situations where building wins
Regulatory fit. Bank statements arrive as BAI2, MT940 or ISO 20022 camt.053 messages depending on the institution, and scheme reporting arrives in its own shapes such as Visa settlement service reports and Mastercard clearing files. If you are audited, the control that matters is that corrections happen as reversing entries rather than edits, with immutable postings and traceability from journal line to file row. Design for a late arriving file to be applied without rewriting a closed period, because that requirement always appears eventually.
Scale economics. Three or more processor connections, or two or more currencies, is where subscription plus analyst days overtakes the build.
A workflow that is your competitive advantage. Encoded rate cards with expected against actual fee comparison per transaction. That is the part with the clearest payback and the part most teams skip, and it is also the conversation that gets a credit from your acquirer, because a conversation with transaction references gets money back and a conversation without them gets an explanation.
Integration sprawl. Count the parties that must agree on one payment: two or three processors, the schemes, one or two banks, your ledger, the accounting system and treasury. Once three or more have to reconcile on the same transaction group, the normalisation layer is the product and no vendor owns your definitions.
How to decide in a week
Run the fee test, not the matching test. Everybody already knows matching is manual.
Pick 500 card transactions from one day last month across your largest acquirer. Recompute the expected cost of each from your contracted rate card, using card type, region, entry mode and merchant category. Compare to what you were actually charged on the settlement detail for those transactions. One analyst, three days, and a copy of the agreement rather than the summary the account manager sent.
Three outcomes and each points somewhere different. If the recomputed figures match, your commercial arrangement is behaving and your problem is purely operational, so buy a matching tool. If you cannot recompute at all because the settlement detail does not carry the fields, that is the finding: raise it with the acquirer before you buy anything, because no software can validate fees the file does not describe. If you can recompute and the numbers disagree, extrapolate the variance across your annual volume. That figure is what the build has to beat, and it is usually not close.
Then commission a paid discovery of two to three weeks ending in a signed product requirements document covering the source adapters, the match grouping rules, the break taxonomy with owners, the rate card model and the posting rules. Digital Heroes writes that before code and you keep it whichever firm you choose, which is the only way four quotes for reconciliation software become comparable.
Who we are wrong for: a team that wants a tool this quarter and no engineering ownership. Buy Duco and get productive next week. Digital Heroes builds systems you own, with more than fifty specialists and over 2,000 projects delivered, India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law, and a named team you meet before signing. Verify us on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Organizations that scaled intelligent automation report an average cost reduction of 32% (up from 24% in 2020), and respondents expect an average 31% cost reduction over the next three years. Source: Deloitte (2022) →
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (2024) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- In an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
Frequently asked questions
How much does custom settlement reconciliation software cost?
A first release with processor and bank file ingestion, lifecycle level matching against your ledger and a categorised break queue runs $70,000 to $160,000 and ships in 12 to 16 weeks in Digital Heroes delivery experience. A full platform adding contracted fee validation, currency handling, chargeback lifecycle matching and automated journal posting runs $200,000 to $500,000 over 6 to 14 months. Historic backfill of prior periods adds 10 to 25 percent.
Why does our acquirer payout never match the sum of our transactions?
Because the payout is a net figure covering a funding window that does not align with your transaction dates, after interchange, scheme fees, adjustments, refunds netted rather than debited, and sometimes currency conversion at the processor's rate. A total to total comparison hides every one of those behind a single difference. Matching at transaction lifecycle level and classifying each unmatched item is what turns that number into a list somebody can work.
How long before a reconciliation build is closing the month for us?
Twelve to sixteen weeks for a first release covering your live connections, lifecycle matching and a working break queue. The main schedule risk is your own data rather than the vendor files: if your ledger does not carry the acquirer reference against each transaction, the first matching pass is much harder, and fixing that upstream is often the cheapest week in the whole project.
Who owns the encoded rate cards and matching rules if an agency builds this?
You should own the repository, the rate card definitions, the matching rules and the cloud accounts, written into the contract before kickoff. Those rules are the reason the system keeps paying for itself year after year, and a developer holding them inside their own platform has quietly converted your reconciliation into their subscription. Digital Heroes assigns everything from the first commit and runs the system in your accounts.
What happens if a settlement file arrives after we close the period?
The design has to allow it without rewriting a closed period, which is a structural decision made at the start rather than a patch later. Late items post to the current period with a reference back to the original transaction group, and corrections happen as reversing entries so the audit trail stays intact. Systems that permit edits to prior periods eventually produce two versions of the same month and neither is defensible.
Can we validate that we were charged the right interchange?
Yes, and it is usually the fastest payback in the build. Encode the contracted rate card, recompute expected cost per transaction from card type, region, entry mode and merchant category, then compare against what was actually charged. Expect to find downgrades caused by your own authorisation data quality, fees on transaction types the contract excludes, and cross border assessments on domestic transactions. Take exceptions to the acquirer with transaction references.
What is the difference between reconciliation software and a ledger?
A reconciliation tool compares two datasets and reports matches and exceptions. A ledger is the authoritative record of what is owed, to whom, and in which account, with immutable entries that sum to a balance. Matching tools do not own your revenue recognition, your suspense policy or your contracted fee schedule, so posting logic and fee validation still land on your team even after you have bought one.
Should we reconcile in the accounting system instead?
Not at transaction level. Accounting platforms are built to hold journals and produce statements, not to hold millions of settlement events with lifecycle grouping and tolerance rules. The pattern that works is reconciling in a purpose built layer and posting summarised, referenced journals into the accounting system, with unmatched items landing in a controlled suspense account carrying an owner and an age rather than an unexplained balance.
How do we handle reconciliation across multiple currencies?
Record the rate, the rate source and the date used for every conversion, and never assume the processor's rate matches your treasury rate. Tolerances have to be set per currency because rounding behaves differently, and gains or losses need their own ledger accounts rather than being absorbed into processing cost. Multi currency is one of the two decisions, alongside processor count, that moves a build from the lower band to the upper one.
What should we budget annually once the system is live?
Fifteen to twenty percent of build cost. That covers file grammar changes that processors ship without notice, scheme fee structure updates, rate card revisions each time you renegotiate an acquiring agreement, and support during month end. Adding a new processor, a new currency or a new legal entity is new scope rather than maintenance, because each brings its own file format, its own adjustment vocabulary and its own tolerance policy.
What tech stack should custom accounting software use?
A boring, proven one. Digital Heroes defaults to PostgreSQL for the ledger because transactional integrity is non-negotiable, a typed backend such as Node with TypeScript, .NET, or Java, and standard React on the front end. The avoid list is clearer than the pick list: floating point math for money, a NoSQL database as the primary ledger store, and any framework young enough that hiring for it in three years will be a problem.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
What should I prepare before contacting an agency about accounting software?
Bring three things: the 5 to 10 workflows that hurt most today, sample data such as your chart of accounts and a redacted month of transactions, and a list of every system the software must connect to, including banks and payroll. You do not need a formal spec; a good agency writes that with you during discovery. In our experience buyers who arrive with concrete workflow pain get accurate quotes, and buyers who arrive with a feature wishlist get padded ones.
How do I vet a development agency for an accounting software project?
Ask to see a live accounting or fintech system they built, then ask how they handle double-entry integrity, period closing, and audit trails; a team that has never built a ledger will learn on your budget. Check whether they bring an accountant or finance-literate analyst into scoping sessions. A portfolio proves design skill, but a walkthrough of how their system blocks an unbalanced journal entry proves domain skill.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
How much does custom accounting software cost for a small business?
Most small business accounting builds land between $25,000 and $75,000 for a working first version, while a full double-entry platform with invoicing, payroll, and reporting runs $100,000 to $250,000. Across 2,000+ projects at Digital Heroes, the biggest cost driver is how many external systems the software must connect to, not the accounting logic itself. A tool that automates a single painful workflow, like reconciliation or job costing, can come in under $20,000.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
How do I migrate years of QuickBooks data into a custom system?
Use a staged migration: export full history through the QuickBooks API or backup files, load it into the new system, then run both systems in parallel for at least one full closing cycle before cutting over. Expect cleanup work, because books older than three years almost always contain miscategorized transactions that surface during import. Digital Heroes schedules migration as its own project phase with its own sign-off, never as a launch-week task.
Who can build a custom accounting software system?
Digital Heroes builds custom accounting software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other accounting software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
