How Much Does Payment Settlement Reconciliation Software Cost?
Custom settlement reconciliation software runs $70,000 to $500,000, and the number that moves the budget most is how many processor and acquirer connections you ingest, not how many transactions you process.
On this page
Custom settlement reconciliation software runs $70,000 to $500,000, and the number that moves the budget most is how many processor and acquirer connections you ingest, not how many transactions you process. Each settlement source is a distinct file grammar with its own idea of gross versus net, its own funding window and its own adjustment lines that reference nothing you can find. Volume costs you almost nothing once the pipeline exists, so a business doing twenty million transactions on two connections builds cheaper than one doing two million across six. Count your connections before you budget, not your transactions.
The bands a reconciliation build falls into
A first release covering ingestion for your live processor and bank connections, transaction lifecycle matching against your ledger and a categorised break queue with aging runs $70,000 to $160,000 and ships in 12 to 16 weeks in Digital Heroes delivery experience. A full platform adding interchange and scheme fee validation against contracted rates, multi currency handling, chargeback and refund lifecycle matching, automated journal posting and multi entity support runs $200,000 to $500,000 over 6 to 14 months.
The first release answers the question your controller is asking, which is what the unexplained difference is made of. It turns one red number into a list of items with categories and owners. The full platform answers a different question, which is what your true net take rate is by product line after real costs, and that is the one your pricing decisions actually depend on.
Neither band includes fixing your own transaction data. If your ledger does not store the acquirer reference against each transaction, that gap makes the first matching pass materially harder, and fixing it upstream is usually the cheapest week in the whole project.
What drives a reconciliation build up
Processor and scheme count is the first driver. Each connection needs its own adapter, its own parsing of adjustment lines, and its own handling of the funding window that does not align with anyone else's.
Multi currency is the second and it is a policy question dressed as a technical one. Tolerances have to be set per currency because rounding behaves differently, gains and losses need their own ledger accounts rather than being absorbed into processing cost, and you have to record the rate, the rate source and the date used for every conversion because the processor's rate is not your treasury rate.
Multi entity structures are the third. When one processor account funds several legal entities, the split has to be derived rather than read, and that derivation needs rules somebody owns.
Marketplace and payment facilitator models are the fourth and the largest. You are no longer reconciling only your own money, you are reconciling sub merchant balances and reserves, which makes reconciliation a custody question rather than an accounting one, with a correspondingly higher bar for correctness.
Historic backfill is the last. Reconciling the previous two years rather than starting clean is a defensible choice and it is scope, not a free extra.
What keeps the number down
The strongest lever is fixing your transaction data before the build starts. Storing the acquirer reference on your own transaction record costs almost nothing and removes the hardest part of first pass matching.
The second lever is starting with your two largest connections. The matching engine, the break taxonomy and the tolerance model are written once. Additional adapters are additive work later, and they get cheaper after the second one because the internal settlement event model is settled.
The third is deferring fee validation. It has the clearest payback in the whole build, and it depends on your contracted rate card being encoded, which requires someone to sit down with the acquirer agreement and read it properly. That is a real prerequisite and it is often not ready when the project starts.
The fourth is starting clean rather than backfilling. Reconcile forward from a cutover date, keep the old spreadsheet as the record for prior periods, and backfill later only if you have a reason such as an audit or a disputed fee claim.
A worked example that adds up
Take a payment service provider or marketplace with three acquirer connections, two settlement currencies, a single legal entity and a ledger that already stores the acquirer reference on each transaction.
- Discovery, mapping your ledger to an internal settlement event model, and reading the actual funding files: $12,000
- Ingestion adapters for three processors plus bank statements, retaining raw files with line level traceability: $34,000
- Lifecycle matching engine grouping authorisation, capture, refunds, chargebacks and funding into one open group until terminal, with configurable tolerances: $38,000
- Break taxonomy with categories, owners, aging and required resolution notes: $18,000
- Suspense posting into the general ledger with immutable entries and reversing corrections only: $16,000
- Six month backfill and a parallel close against the existing spreadsheet: $14,000
- Testing, controller sign off and training: $10,000
That totals $142,000, in the upper part of the first release band because of three connections and a real backfill. Launch with two connections, saving $11,000 of adapter work, and hold ledger posting for phase two while your team continues journalling from the break report, saving $16,000, and the same project lands at $115,000.
How the spend phases
The first two to three weeks are discovery, and in this category discovery means reading real settlement files rather than documentation. Roughly a tenth of the budget, and it is where you discover the adjustment lines that reference nothing.
The middle stretch builds the adapters and the matching engine, which is where most of the money goes and where nothing looks finished for several weeks. Matching is the part that either works on real data or does not, so expect a period where the match rate climbs slowly as edge cases surface. That is the project working, not the project failing.
The last stretch is the break queue, posting and the parallel close. Run at least one full month end close in parallel with your existing process before you rely on the new system, and treat the differences as findings rather than as bugs, because some of them will be errors in the old process.
The ongoing costs nobody quotes
Adapter maintenance is the standing obligation. Processors revise file formats, add fields and occasionally change how adjustments are expressed. A parser that silently misreads a column is worse than a parser that fails loudly, so part of the ongoing cost is monitoring that the ingestion is still correct rather than merely still running.
Rate card upkeep is the second, if you build fee validation. Contracts get renegotiated and scheme fee schedules change, and the encoded rate card has to follow. Build it as data your finance team edits.
Hosting is modest, though retaining raw settlement files for the period your auditors expect adds storage that grows every year and needs a lifecycle policy. Budget 15 to 20 percent of build cost annually for support, adapter upkeep and enhancement.
Comparing a build against your current renewal
Use your own numbers. Take the annual cost of whatever matching tooling you run today, at your current renewal, whether that is Duco, SmartStream, Gresham, Kani Payments or a ledger platform such as Modern Treasury. Add the fully loaded cost of the analyst days consumed each month by reconciling and by re opening files by hand. Add the cost of a delayed close, which for a business with reporting obligations is a real number your finance director can quantify.
Then add the item that usually dwarfs the rest: the fees you are paying that your contract does not entitle your acquirer to charge. You cannot know that figure until someone recomputes expected cost per transaction from card type, region, entry mode and merchant category and compares it against what was actually charged. If nobody has ever done that, treat it as an unmeasured liability rather than as zero.
Compare that annual total against a build amortised over three years plus the retainer. Fee validation is frequently the line that settles the argument, because exceptions taken to an acquirer with transaction references get credits while the same conversation without references gets an explanation.
When buying beats building
Some readers should not build. If you have one processor, one currency and a daily file that already balances to the deposit, buy a matching tool and spend the money on the ledger underneath it instead. Duco is genuinely good at self service data matching and will get a finance team productive quickly, and at that shape of business matching is the whole problem.
If your problem is bank payment operations and ledgering rather than card scheme fee detail, Modern Treasury is built for that and building a reconciliation platform to solve it would be aiming at the wrong target. If your model closely resembles a fintech programme manager setup, Kani Payments onboards fast for exactly that shape.
And if you are an enterprise with a mature matching programme already running on SmartStream or Gresham, the argument is not to replace it. It is whether to build the fee validation and revenue recognition layer those engines do not own.
Build when you run three or more processor connections, when you operate in more than one currency or legal entity, when you hold funds for sub merchants, when your close is being delayed by unreconciled settlement, or when you cannot state your true net take rate by product line, which means your pricing is being set on an estimate.
When the shortlist is down to two and you need a tiebreaker, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Independent reporting of Gartner's 2025 survey confirms 59% of finance leaders use AI, up from 37% in 2023, with error and anomaly detection (34%) and accounts payable automation (37%) among the leading use cases. Source: CPA Practice Advisor (reporting Gartner) (2025) →
- 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) →
- The Standish Group 1995 CHAOS Report found only 16.2% of software projects fully succeeded; success varied sharply by size, with large-company projects succeeding about 9% of the time versus far higher rates for small projects - best treated as an industry survey, not an audited dataset. Source: Standish Group (1995) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
Frequently asked questions
What does custom payment reconciliation software cost in total?
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, multi currency, chargeback lifecycle handling and automated journal posting runs $200,000 to $500,000 over 6 to 14 months.
Processor connection count and currency count drive the figure far more than transaction volume does.
What does it cost to run every year?
Budget 15 to 20 percent of build cost annually for hosting, support and enhancement, with adapter maintenance as the recurring item specific to this category. Processors revise file formats and adjustment conventions, and a parser that silently misreads a column is worse than one that fails loudly, so part of that budget is monitoring correctness rather than uptime.
Add rate card upkeep if you build fee validation, and build it as data your finance team edits rather than a developer task.
How long does implementation take?
Twelve to sixteen weeks for a first release covering your live connections, lifecycle matching and a working break queue. Expect a stretch in the middle where the match rate climbs slowly as edge cases surface on real data. That is the project working.
Run at least one full month end close in parallel with your existing process before relying on the new system, and treat the differences as findings, because some will be errors in the old process.
Should we buy Duco or SmartStream instead of building?
If your problem is purely matching, they will solve it and we would say so. Duco in particular gets a finance team productive quickly on self service matching. The limitation is that matching is half the job: they do not own your ledger, your contracted rate card or your revenue recognition, so posting logic and fee validation still land on your team.
Building makes sense once you run several processors, more than one currency or entity, or hold funds for sub merchants, at which point reconciliation becomes a custody question.
Why does multi currency add so much cost?
Because it is a set of policy decisions rather than a conversion function. Tolerances have to be set per currency since rounding behaves differently, gains and losses need dedicated ledger accounts rather than being absorbed into processing cost, and every conversion has to record the rate, the source and the date used.
Along with processor count, multi currency is one of the two decisions that moves a reconciliation build from the lower band into the upper one.
How much does interchange fee validation cost, and is it worth it?
It sits in the full platform band because it requires your contracted rate card encoded and expected cost recomputed per transaction from card type, region, entry mode and merchant category. It is also the line with the clearest payback in the entire build.
Expect to find downgrades caused by your own authorisation data quality, fees on transaction types your contract excludes, and cross border assessments on domestic transactions. Take the exceptions to your acquirer with transaction references, because references get credits.
Can we reduce cost by starting with fewer connections?
Yes, and it is the most effective reduction available. The matching engine, break taxonomy and tolerance model are written once regardless. In the worked example, dropping from three connections to two saved $11,000, and each adapter after the second is cheaper because the internal settlement event model is already settled.
Backfill is the other lever. Reconciling forward from a cutover date and leaving prior periods with the old spreadsheet removes a whole workstream.
What should we fix before the project starts?
Store the acquirer reference against each transaction in your own ledger if you do not already. That single change removes the hardest part of the first matching pass and it costs almost nothing compared with building matching logic to work around its absence.
Also have your acquirer agreements to hand, read and understood. Fee validation cannot be built from an assumption about what your rate card says.
Who owns the matching rules and the encoded rate cards?
You should own the repository, the encoded rate cards, the matching rules and the cloud accounts, written into the contract before kickoff. At Digital Heroes the client owns everything from the first commit.
Those rules are the reason the system keeps paying for itself, and a developer holding your reconciliation logic inside their own platform has converted a solution into a subscription you cannot leave.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
How many developers does it take to build accounting software?
The standard Digital Heroes team is 4 to 6 people: a backend developer, a frontend developer, a QA engineer, a part-time designer, and a project lead who owns the accounting logic. A single-workflow automation can ship with two people, while multi-entity platforms with payroll can need eight. Headcount matters less than having one named person accountable for the books balancing.
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.
Will custom accounting software scale as my company grows?
It scales exactly as far as its data model was designed to, so multi-entity support, multi-currency, and consolidation should be day-one design decisions even if you launch with a single company. Retrofitting multi-entity onto a single-entity ledger is among the most expensive changes we handle, and in Digital Heroes rescue work it often costs a third of the original build. Compare that with QuickBooks Online, which requires a separate subscription for every company you add.
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.
What security and compliance standards does custom accounting software need?
At minimum: encryption at rest and in transit, role-based access control, and immutable audit logs recording every change to the ledger. If outside parties rely on your numbers you will want SOC 2 style controls, and storing card data pulls you into PCI DSS, which most builds avoid by tokenizing payments through Stripe or a similar processor. Your industry adds its own rules, so compliance requirements belong in the written spec, not in a post-launch retrofit.
Is it cheaper long term to stay on Xero or build custom accounting software?
Xero stays cheaper as long as its workflows fit your business, since even its top plan costs around $1,000 a year and custom development starts around $25,000. The math flips once you stack add-ons: companies Digital Heroes scopes after they have bolted inventory, job costing, and approval apps onto Xero are usually paying more for the app stack and the labor of keeping five tools in sync than for Xero itself. Custom wins when the real cost is that labor and its errors, not the license fee.
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
More from Oliver.
Senior Account Director · UK · London · 3 posts on the site
Published · Last updated .
