Build vs Buy: Marketplace Payout and Settlement Software
Most platforms should buy. Stripe Connect or Adyen for Platforms carries the regulated role, the identity checks and the money movement, and a few hundred sellers in one currency does not justify a ledger.
On this page
Most platforms should buy. Stripe Connect or Adyen for Platforms carries the regulated role, the identity checks and the money movement, and a few hundred sellers in one currency does not justify a ledger. Build the record of what sellers are owed once reserves, goodwill refunds and off cycle fees live outside the provider and finance cannot explain the monthly gap.
Stripe Connect is the right purchase far more often than platform teams admit
Start with the case against building, because it wins more arguments than it loses. If your platform pays out to a few hundred sellers, all in one currency, all in one country, on a commission that is a single percentage, Stripe Connect or Adyen for Platforms already does this properly. They carry the regulated role, run identity checks at onboarding, hold the funds, move the money, and absorb the failure behaviour of ACH and SEPA so your team never sees it. Writing your own ledger to serve 200 sellers is a way to spend engineering budget on a problem you do not yet have.
The honest test is not seller count, it is whether finance is confused. If your controller closes the month in a morning, if no seller has ever asked a balance question you could not answer from the provider dashboard, and if every dollar that reaches a seller passed through the provider on its way, buy the platform and stop reading. The difference is better spent on the categories that grow gross merchandise value.
Buying also covers more of the compliance surface than people expect. Depending on how the platform account is configured, the provider can carry seller tax form collection and filing, and that is precisely the work platform teams underestimate. Take it while your shape still fits. Hyperwallet and Trolley are sensible additions rather than replacements when you need payout reach into markets your primary provider serves badly, and adding a payout partner is a much smaller commitment than owning a ledger.
The month end that tells you the ledger has to be yours
Finance has three numbers that should agree. What the provider says settled to your bank. What the order system says was collected. What the payout records say went to sellers. They differ by a few thousand dollars, the gap moves every month, and after two days of chasing it goes to a suspense account. The write off is small. That nobody can explain it is the actual problem, because it means you cannot prove seller balances, and seller balances are money you owe other people.
The drift is structural rather than sloppy. Your provider holds a view of the money that passed through it. It has never seen the goodwill refund you funded yourself, the marketing fee agreed with a top seller off cycle, the reserve your risk team applied by hand, or the adjustment made after a support escalation. Each of those changes what a seller is owed, and none of them exists in the provider's record. Meanwhile the order table with a paid flag and a payout reference feels adequate until somebody asks a question sideways: what was seller 4,281's balance on 14 March, and what made up the payout of 8,417 dollars they received on the twentieth.
Build the ledger when two or more of these hold. Sellers query balances and you cannot show the calculation. You operate more than one currency and foreign exchange gain and loss is not booked to any identifiable account. You hold reserves or apply adjustments outside the provider. Or you now carry seller tax reporting duties in more than one jurisdiction. Note what building does not mean: the provider keeps moving money and keeps the licence. You own the record of what is owed.
Two budgets, and the reasoning behind each
On the buy side the licence is rarely the number that hurts. Payout economics are, and they behave in a way that catches people. Payout fees on most rails are charged per payout instruction rather than per dollar moved, so a marketplace that switches sellers from monthly to weekly payouts as a retention gesture roughly quadruples its payout cost overnight for exactly the same volume. Cross border payouts carry a separate per instruction fee, and the foreign exchange spread is priced again on top. Model the fee bill against payout frequency before you promise sellers faster money, because that promise is very hard to withdraw.
Then add finance time. Two days a month of a controller reconciling a gap nobody can explain is a salary line, and it grows with seller count rather than staying flat.
On the build side, a first release covering a double entry ledger, split calculation, reserve accounts, scheduled payouts through your existing provider, seller statements and daily reconciliation runs $90,000 to $190,000 over 14 to 20 weeks in our delivery experience. A full platform adding multi currency with an explicit foreign exchange policy, several payout corridors, negative balance recovery, tax identity collection and annual reporting runs $240,000 to $600,000 phased across 9 to 15 months.
What moves you up that range is not seller count. It is the number of payout corridors, since each rail has its own file formats and failure behaviour, and the number of tax jurisdictions, since each reporting regime is separate work rather than a configuration flag.
The costs that never reach the business case
First, the custody question, which is legal before it is technical. If your design leaves funds resting in an account you control at any point, you may be inside money transmission licensing in the United States or payment institution requirements in Europe. Get counsel to answer that before architecture, because the answer decides where money sits and who the regulated party is, and retrofitting it is not cheap.
Second, the January chase. Tax reporting fails operationally long before the filing. You did not collect valid tax identity at onboarding, and now you are pursuing thousands of sellers for a form while a deadline runs. Make valid tax identity a gate on payout eligibility rather than on listing, because that is the moment a seller has a reason to complete it. Reporting rules under 1099-K in the United States and DAC7 in the European Union have both moved in recent years, so confirm the current position with your tax advisers rather than a figure you read somewhere.
Third, negative balances. Refunds and chargebacks arrive after a seller has been paid and sometimes after they have stopped trading, leaving you with an unsecured receivable against a small business abroad. Budget the write off as a line and set a threshold at which you stop chasing.
Fourth, the migration parallel run. Moving live seller balances means opening the new ledger with an explicit opening entry per seller from a frozen snapshot, then running both systems side by side for two to four weeks with a daily comparison of computed balances. That window is real project cost, and compressing it to hit a date is how balances end up wrong.
Fifth, on the buy side, settlement file changes. Providers revise their formats, they announce it with modest notice, and whoever wrote your reconciliation script inherits the work each time.
The test that settles it in one afternoon
Pick a seller with real volume and a dispute history. Ask four questions and time the answers. What was their balance on the fourteenth of March. What made up the payout they received the following week, line by line. Which of those lines came from your own funds rather than the provider. And what is currently held in reserve for them, why, and when does it release.
If all four arrive inside ninety minutes from records rather than reconstruction, and the last answer matches what the seller sees in their own statement, you do not need to build. Your provider plus your order system is carrying the load.
If the first answer requires recalculating from current order rows, stop there. Mutable rows do not remember. A balance you rebuild from today's data is a balance you cannot defend in a dispute or an audit, and no amount of reporting polish changes that.
Then run a second check on reconciliation. Take last month's provider settlement file and ask how many lines failed to match your own records, how they were classified, and how old the oldest unexplained break is. Fee treatment, timing across a settlement boundary and rounding are all normal and should be categorised automatically. The break with no category is where a genuine defect lives, and if nobody is looking for it, it has been sitting there a while.
What to do next
Write the economic events down before you talk to anyone. One line each: sale, commission, refund, partial refund, chargeback, chargeback reversal, reserve hold, reserve release, manual adjustment, payout, failed payout, foreign exchange settlement. For each, say which accounts move and in which direction. Most platform teams discover during this exercise that two people hold different views of what a refund does to commission already earned, and settling that on paper is worth more than any tooling decision you make this year.
Then ask any developer three questions. How do they store money, where the only acceptable answer is integer minor units with an explicit currency on every amount and a clear explanation of why floating point is unacceptable here. What happens when a payment webhook is delivered twice, where idempotency keyed to the source event should be the first thing they say rather than something added after the first duplicate payout. And how a historical seller balance is answered, where the answer should be a query over immutable entries rather than a recalculation from current rows.
Digital Heroes builds the ledger and reconciliation layer for platforms that keep their payment provider exactly where it is, and every engagement starts with a written product requirements document before any code, which for a system that is ultimately a record of money owed to other people is the deliverable that survives staff turnover. The team is 50-plus people across 2,000-plus delivered projects, taking on more than 100 new clients a month, with entities in India, the United States and the United Kingdom so contracting and IP assignment happen under your own law. If you want to judge how the team explains its thinking before committing budget, the Digital Marketing Heroes channel carries 2.5 million subscribers. Send one month of provider settlement files and your commission rules, and the scoping conversation gets specific quickly.
When the shortlist is down to two and you need a tiebreaker, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. 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.
- 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) →
- Gartner estimates RPA can eliminate up to 25,000 hours of avoidable rework caused by human errors in the finance function each year, equating to savings of roughly $878,000 for an organization with 40 full-time accounting staff (based on interviews with more than 150 corporate controllers and chief accounting officers). Source: Gartner (2019) →
- 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) →
- 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) →
Frequently asked questions
How much does it cost to build marketplace payout and settlement software?
A first release covering a double entry ledger, split calculation, reserve accounts, scheduled payouts through your existing provider, seller statements and daily reconciliation runs roughly $90,000 to $190,000 over 14 to 20 weeks. Adding multi currency with a stated foreign exchange policy, several payout corridors, negative balance recovery and annual tax reporting takes it to $240,000 to $600,000 across 9 to 15 months. Corridors and tax jurisdictions drive that range far more than seller count.
How long before a custom ledger can run real payouts?
Fourteen to twenty weeks to a first release, then two to four weeks running in parallel with your existing process before you rely on it. The schedule risk is almost never the ledger logic itself. It is the provider integration and the opening balance exercise, because every seller has to start on the new system with a figure you can defend, and that figure comes from a frozen snapshot rather than a live query.
Can we migrate live seller balances without paying anyone twice?
Yes, if you treat it as a parallel run rather than a cutover. Open the new ledger with an explicit opening balance entry per seller sourced from a frozen snapshot, keep paying out from the old system during the window, and compare computed balances daily for two to four weeks. Only when the two agree for several consecutive days do payouts move across. Budget that window as real project cost instead of assuming it happens quietly.
Which payout integrations cause the most trouble?
Cross border corridors, because each rail has its own file format, its own settlement timing and its own way of failing. A payout that fails on ACH looks nothing like one that fails on SEPA or through a partner such as Hyperwallet or Trolley, and the funds must return to the seller's balance atomically rather than sitting in limbo while support investigates. Provider settlement file format changes are the recurring maintenance nobody scopes.
Does building a ledger mean leaving our payment provider or taking on licensing?
No on both counts if the design is right. The provider keeps moving money and keeps the regulated role while you own the record of what each seller has earned, what is held and what remains owed. Taking custody of funds yourself can bring money transmission licensing or payment institution requirements into scope, which is a legal question with architectural consequences and belongs with counsel before design rather than after.
Who actually builds marketplace settlement systems?
Specialist custom software firms rather than payment vendors, because the work is ledger design, reconciliation and integration rather than money movement. Digital Heroes fits this for platform teams because every engagement begins with a written product requirements document before any code, which matters when the deliverable is a record of money owed to other parties, and because the firm contracts through Indian, United States and United Kingdom entities so IP assignment happens in the buyer's own jurisdiction.
What separates Digital Heroes from a generic development shop here?
The insistence that every amount is stored as integer minor units with an explicit currency, that every entry is idempotent against its source event, and that nothing is ever edited, only reversed. Those three decisions are what make a historical balance answerable in three years. Digital Heroes also runs its own commerce products, including ShopScore, HeroCheckout and Section Vault, so the same discipline is applied to systems the firm has to maintain itself.
How do we verify a development partner before paying anything?
Check the company holds a D-U-N-S registration, which confirms a verified business entity rather than a trading name. Read the Clutch profile for reviews tied to named contacts and stated project values, and read Trustpilot for the pattern of complaints rather than the headline score. Then ask which legal entity will sign in your jurisdiction and confirm the IP assignment clause names it before any money moves.
Should the first version of my accounting software be an MVP?
Yes, but scope it around one complete workflow rather than a thin slice of everything. A strong first release fully owns, say, invoicing and receivables while QuickBooks keeps running the general ledger, letting you validate the software with real money movement in 10 to 14 weeks. In Digital Heroes projects, one-workflow MVPs reach a stable full system faster than big-bang replacements almost every time.
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.
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 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.
What happens to my accounting software if the agency shuts down?
If you own the repository, the hosting accounts, and the documentation, another team can take over within weeks, usually before a missed closing cycle does real damage; if the agency owns any of those, you have a hostage situation. Before signing, confirm the code sits in your GitHub or GitLab organization, hosting bills to your card, and a written deployment runbook exists. A competent agency agrees to all three without friction, and hesitation is itself the answer.
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.
How long does it take to build custom accounting software?
A focused first version takes 10 to 16 weeks, and a complete QuickBooks-class replacement takes 6 to 9 months. In Digital Heroes delivery data, schedules slip most often during data migration and bank feed integration, so we budget those two phases at double the first estimate. Treat any promise of a full accounting system in under two months as a warning sign.
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.
Can I extend QuickBooks with custom features instead of replacing it?
Yes, and it is often the right first step. QuickBooks Online has a public API, so an agency can build a custom layer for quoting, inventory, or field service that pushes clean transactions into QuickBooks, which stays your ledger of record. Roughly half of the accounting engagements Digital Heroes scopes start this way because it costs a fraction of a full build and leaves your accountant's workflow untouched.
I'm outgrowing FreshBooks. Is custom software the logical next step?
Usually not directly, because FreshBooks is an invoicing tool more than a full accounting platform, and the natural next step is QuickBooks or Xero for proper double-entry books. Custom development makes sense when those do not fit either, typically because of a billing model none of them handle, like usage-based or milestone billing. In that case a custom billing engine that feeds a standard ledger is often smarter than replacing everything.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
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.
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 .
