How to Hire a Marketplace Payout and Settlement Software Development Company
Two questions settle most shortlists. How do you store money, and what happens when a webhook arrives twice. If the answers are not integer minor units with an explicit currency, and idempotency keyed to the source event, do not hand that team your ledger.
On this page
Two questions settle most shortlists. How do you store money, and what happens when a webhook arrives twice. If the answers are not integer minor units with an explicit currency, and idempotency keyed to the source event, do not hand that team your ledger. Expect $95,000 to $190,000 and fourteen to twenty weeks for a first release.
Every marketplace passes a moment without noticing it, and that is the moment it stops being a software business and becomes a financial one. On the surface it looks like two calls: charge the buyer, pay the seller. Underneath it is a ledger, and if nobody has built one, your finance team is the ledger. You can tell because month end produces three numbers that should agree and do not, and the gap is written to a suspense account after two days of chasing.
What makes this category hard to buy is that the failure is silent and the demonstration is not. Any competent developer can show money leaving an account. What a demonstration cannot show you is whether a seller's balance on the fourteenth of March last year can be answered as a query rather than reconstructed by archaeology, or whether a duplicated webhook has been quietly paying somebody twice. Buyers therefore evaluate candidates on payment provider integrations, when the real question is who holds the authoritative record of what is owed.
What a settlement software development company actually does
The visible build is a payouts screen and a seller statement. Both are outputs of the part that matters.
The core is double entry done properly. Every economic event writes balanced entries against accounts: a sale credits the seller payable and credits your commission revenue, a refund reverses, a chargeback moves the amount to a dispute account, a payout debits the payable and credits cash in transit until the provider confirms. Nothing is edited, only reversed with a new entry, so any historical balance is a query. Two implementation details separate a real ledger from a cosmetic one: idempotency keyed to the source event, because payment webhooks arrive twice and a duplicate credit is money you pay out and never recover, and amounts stored as integer minor units with an explicit currency rather than as floating point.
Around that sit the parts sellers actually argue about. Reserves as first class accounts with their own entries, graduated by seller history rather than applied uniformly, so a statement shows what is held, why and when it releases. A defined negative balance recovery sequence rather than improvisation: net against future earnings, attempt a debit where you have that authority, hold payouts, write off at a threshold. Multi currency handled as policy, with entries in transaction and functional currency, the rate and its timestamp on the entry, and foreign exchange gain or loss booked to its own account instead of vanishing into the payable. Tax identity as a gate on payout eligibility, with reportable amounts accumulating by jurisdiction. And daily reconciliation against the provider settlement file with a categorised, aged break queue.
What it really costs in 2026
| Scope | Cost | Timeline |
|---|---|---|
| Ledger core: double entry engine, split calculation, reserve accounts, payout scheduling through your existing provider, seller statements, daily reconciliation | $95,000 to $190,000 | 14 to 20 weeks |
| Full platform: multi currency with an explicit rate policy, multiple payout corridors, negative balance recovery, tax identity and annual reporting, dispute handling, finance console | $245,000 to $600,000 | 9 to 15 months |
| Support, new corridors and reporting regimes | 18 to 25 percent of build per year | Retainer |
Two costs are almost never in the quote and both are large.
The first is the balance migration. Moving live seller balances into a new ledger has to be provably exact, because those balances are money you owe other people. The pattern that works is an explicit opening balance entry per seller from a frozen snapshot, then two to four weeks running both systems in parallel with daily comparison of computed balances while payouts continue from the old system. That parallel period is real project cost and real calendar, and the temptation to shorten it to hit a launch date is where these projects go wrong.
The second is that corridors, currencies and tax regimes are each separate work priced as one word. Each payout rail has its own file formats, timing and failure behaviour, and a failed payout must return funds to the seller's balance atomically rather than leaving them in limbo while support investigates. Each reporting jurisdiction is separate again. Related and genuinely timeline setting: whether you ever take custody of funds is a legal question before it is a technical one, since it can bring money transmission licensing or payment institution requirements into scope. Get counsel to answer it before design rather than after, because it decides the architecture instead of decorating it.
Signals of a strong partner
- They answer the money storage question instantly. Integer minor units with an explicit currency, and a clear explanation of why floating point is unacceptable here.
- Idempotency is their first thought, not their fix. Keyed to the source event, applied to every entry, discussed before you raise duplicates.
- They keep your payment provider. The right outcome is usually the provider moving money while you own the record, and a good team says so unprompted.
- They ask what lives outside the provider's view. Goodwill refunds funded by you, off cycle marketing fees and manual adjustments are exactly why a ledger is needed.
- They have opinions about reconciliation breaks. Timing differences at settlement boundaries, fee treatment and rounding classified automatically, with ageing on anything uncategorised.
- They raise tax identity collection timing. Gating the first payout rather than the first listing is the difference between a report and a January chase.
- They insist on ownership before kickoff. This is the record of money you owe other people and it cannot sit in a supplier's account.
Red flags
- Balances are computed from order rows. If a historical balance requires recalculating from current data, the design cannot survive an audit or a dispute.
- Reserves are a single percentage setting. Uniform reserves either strangle good sellers or fail to cover the risky ones, and sellers dispute reserves more than any other line.
- Foreign exchange is described as a conversion. Who bears the movement between sale and payout is a commercial policy decision that must be explicit in the ledger.
- The migration plan has no parallel run. Cutting over seller balances without a comparison period is a way of discovering errors from angry sellers.
- Licensing is treated as your problem to raise later. Custody of funds changes the architecture, and a partner who has built these will ask about it on the first call.
Questions to ask on the first call
- How do you store monetary amounts, and why is that the right choice here?
- A payment webhook is delivered twice. What stops the second one crediting a seller again?
- How would you answer what a seller's balance was on a specific date eighteen months ago?
- Walk me through reconciling against a provider settlement file, including how breaks are categorised and aged.
- How do reserves appear on a seller statement, and how do levels change as a seller builds history?
- What is the recovery sequence when a seller's balance goes negative after refunds?
- Where does foreign exchange gain and loss get booked, and who bears the movement between sale and payout?
- How do you collect and validate seller tax identity, and at what point does it gate a payout?
- What is your migration plan for live seller balances, and how long is the parallel run?
A simple way to decide
Do not choose on price. Buy a short paid discovery phase from your two best candidates and require the same deliverable: a written specification containing the chart of accounts and entry model, the idempotency and precision decisions, the reserve policy design, the foreign exchange policy, the reconciliation and break handling approach, the tax identity gate, a balance migration plan with a stated parallel period, and a phased estimate. Also require them to state which questions need your counsel before design starts.
That specification is yours to take anywhere, including to firms that did not write it. Digital Heroes delivers this way as standard, producing a product requirements document before any code exists, with the client owning the repository and the ledger data from the first commit and contracting through an India LLP, a US LLC or a UK LTD so intellectual property assigns under the buyer's own law. More than 2,000 projects delivered and in-house products of its own including HeroCheckout, verifiable through D-U-N-S, Clutch and Trustpilot.
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.
- 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) →
- APQC's Open Standards Benchmarking data on the monthly financial close found median performers take about 6.4 calendar days to close the books, while top performers (top 25%) do it in 4.8 days or fewer and bottom performers (bottom 25%) take 10 or more days. Source: APQC (2018) →
- Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
- Technology 'Leaders' grow revenue at more than twice the rate of 'Laggards'; laggards surrendered 15% in foregone annual revenue in 2018 and stood to miss out on as much as 46% in revenue gains by 2023 if they did not change their enterprise technology approach. Based on a survey of more than 8,300 organizations across 20 industries and 20 countries. Source: Accenture (2019) →
Frequently asked questions
How much does it cost to hire developers for marketplace settlement software?
A ledger core with a double entry engine, split calculation, reserve accounts, payout scheduling through your existing provider, seller statements and daily reconciliation runs $95,000 to $190,000 over fourteen to twenty weeks. A full platform adding multi currency, multiple payout corridors, negative balance recovery and tax reporting runs $245,000 to $600,000 across nine to fifteen months. Currencies, corridors and tax jurisdictions drive cost far more than seller count.
Do we still need Stripe Connect if we hire developers to build a ledger?
Almost always yes, and that is the recommended outcome rather than a compromise. The provider keeps moving money and carrying the regulated role while you own the authoritative record of what each seller has earned, what is held in reserve, what has been paid and what remains owed. Your ledger includes things the provider never sees, such as goodwill refunds you funded and off cycle fees.
What are the two questions that disqualify a settlement developer?
How do you store monetary amounts, and what happens when a payment webhook is delivered twice. The correct answers are integer minor units with an explicit currency on every amount, never floating point, and idempotency keyed to the source event applied to every ledger entry. A team that has not thought about either will produce unexplainable cent differences and, eventually, a duplicate payout nobody can recover.
How long does a settlement platform take to build?
Fourteen to twenty weeks for a ledger core, then nine to fifteen months in phases for currencies, corridors, recovery and tax reporting. The item most often left out of the schedule is migrating live seller balances, which needs an opening balance entry per seller from a frozen snapshot and two to four weeks of parallel running with daily comparison before cutover. Do not compress that window.
Does holding marketplace funds require a licence?
Taking custody of funds can bring money transmission licensing into scope in the United States and payment institution requirements in Europe, which is why most marketplaces keep a licensed provider as holder of record while owning the ledger themselves. This is a legal question with architectural consequences, so have counsel answer it before design rather than after. It determines where funds sit and who is the regulated party.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
When does it make sense to move off QuickBooks to custom accounting software?
Move when you are paying people to work around the tool, not when the subscription feels expensive. Common triggers are hitting the 25-user cap on QuickBooks Online Advanced, consolidating multiple entities in spreadsheets, or a billing model that forces manual journal entries every month. If your team spends several hours a week exporting to Excel just to answer basic questions, you are already paying for custom software in salaries.
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.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
How much do developers charge per hour for accounting software work?
In the competing quotes clients share with Digital Heroes, established US and UK agencies charge $90 to $200 an hour for accounting and fintech work, senior freelancers $60 to $150, and offshore teams $25 to $60. We price accounting builds as fixed-scope milestones instead, because hourly billing on ledger work rewards slow debugging. Compare total quoted cost against your workflow list rather than comparing rates against rates.
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.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
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.
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.
Who owns the code when an agency builds my accounting software?
You should, outright, and the contract must say so with an explicit IP assignment clause rather than a usage license. Insist that the code lives in a repository you control from day one, so nothing, including the ledger schema and migration scripts, can be held back at the final invoice. Third-party libraries and any framework the agency reuses stay under their own licenses, and a clean contract lists exactly which those are.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
What does it cost to maintain custom accounting software each year?
Budget 15 to 20 percent of the build cost annually, so a $100,000 system needs $15,000 to $20,000 a year for hosting, security patches, dependency updates, and small fixes. Accounting software carries one extra obligation most software does not: keeping tax rates, filing formats, and bank feed connections current as banks and tax authorities change their systems. Skipping maintenance for two years usually costs more to repair than the maintenance would have cost.
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.
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.
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 .
