Marketplace payouts, commissions and vendor settlement: how the money layer should work

This guide is for CTOs, product owners and finance leads of multi-vendor marketplaces. It goes one level deeper than our marketplace platform architecture guide, which places payments among vendors, catalogue and orders; here the subject is only the money after checkout. For when a custom platform is justified at all, start with the custom e-commerce platform guide.

In this guide

• Three layers: provider, ledger, payout engine
• Commission models and where each fits
• The vendor ledger
• Settlement timing and release rules
• Refunds, chargebacks and negative balances
• Payout operations and failures
• Tax and reporting duties
• Reconciliation
• Build, buy or configure: alternatives and selection criteria
• AI in marketplace settlement
• What delivery record exists, and what does not
• Limits of this guide
• Frequently asked questions
• Next step

Three layers: provider, ledger, payout engine

Most settlement problems come from mixing up three jobs.

• The payment provider charges the shopper, holds regulated funds, verifies vendors and sends money to their bank accounts. Marketplace products such as Stripe Connect and Adyen for Platforms onboard sellers, split payments and manage payouts.
• Your ledger records why each amount belongs to whom: order lines, commission, fees, discounts, refunds, reserves and adjustments. It is the source for vendor statements, finance reports and support answers.
• Your payout engine decides when a balance is released and asks the provider to move it, then records the result.

The provider's balances show what can move today, not why a vendor received less than expected or what a refund did to last month's commission. That is the ledger's job, never a spreadsheet's.

Commission models and where each fits

Whatever the model, write the commission rules as data, not code: a rate table keyed by vendor, category and date, with an effective-from date on every change. Store the rate used on each order line, because a refund three months later must reverse the commission that was charged then, not today's rate.

The vendor ledger

Treat money movements the way accountants do. Martin Fowler's accounting patterns describe it well: balances come from entries, and a mistake is corrected by a new adjusting or reversing entry, never by editing the old one. For a marketplace that means:

• One entry per event. An order line paid, commission charged, provider fee allocated, refund issued, chargeback received, reserve held, reserve released, payout sent, payout returned.
• Double entry. Each entry moves an amount between two accounts, such as buyer funds to vendor pending, or vendor pending to platform commission, so the total always balances to zero.
• Balances per vendor in three states. Pending (earned but inside the delivery or return window), available (payable on the next run) and reserved (held against refunds and disputes). Stripe describes pending and available balances for connected accounts in the same terms.
• Links to the source. Every entry carries the order, line, refund or dispute it came from, plus the provider's transaction reference.

Such a ledger answers in minutes why a payout, why a deduction and what is still owed.

Refunds, chargebacks and negative balances

Refunds and disputes arrive after money has moved, which is why they need rules before launch.

• Refund per vendor line. A refund reverses that line's vendor share and, under your policy, its commission. Other vendors in the basket are untouched.
• Chargebacks. The provider takes the disputed amount back from whichever account the charge was made on. If the vendor was already paid, the platform carries the gap until the vendor's balance covers it.
• Negative balances are normal. Show the amount, the reason and the date to the vendor, offset it against future earnings automatically, and escalate only when it ages. Stripe notes that a connected account with a negative balance receives no payouts until it turns positive, and that the platform's own balance may be reserved to cover accounts it is responsible for.
• Decide who carries losses. In each provider's settings, decide whether the provider or the platform is liable for a vendor's negative balance, and price your commission with that decision in mind.

Payout operations and failures

Plan payouts for the unhappy paths:

• Bank details change. Treat any change of payout details as a risk event: confirm it, hold the next payout briefly and log who changed what.
• Returned payouts. A rejected bank transfer returns the amount to the vendor's available balance, with a task for the vendor to fix the details.
• Currencies. Record the order currency, the settlement currency and the rate used on each conversion, so statements match what reached the bank.
• Statements. Give each vendor a downloadable statement per payout: orders, commission, fees, refunds, reserves and adjustments that add up to the amount paid.

Tax and reporting duties

Platforms that process sellers' income carry reporting duties in several regions. In the EU, DAC7 requires digital platform operators to collect and verify information about their sellers and report it to tax authorities. In the United States, online marketplaces acting as third-party settlement organisations file Form 1099-K for sellers above the IRS reporting threshold. Capture the seller data at onboarding and keep payout totals per seller and year in the ledger, so reports are a query. Confirm current thresholds with a tax adviser.

Reconciliation

Reconcile three views every day: your ledger, the provider's balance transactions and the bank. Match each payout to its ledger entries and to the bank deposit, flag any difference, and close the day only when unmatched items have an owner. Post summarised entries to the finance system; our guide to ERP, CRM and e-commerce integration covers that link. Tests before launch should include generated baskets with several vendors, partial refunds, a chargeback after payout, a returned payout and a currency conversion, all ending with a ledger that balances to zero.

Build, buy or configure: alternatives and selection criteria

Four criteria decide it: how unusual your commission and reserve rules are, how many currencies and countries you settle in, who carries losses from disputes, and how much of the reporting finance needs every month. Netbase has delivered commerce platforms on WooCommerce, Magento 2, Laravel and headless commerce, and in custom development the client owns the IP created for it. Most Netbase projects are delivered on fixed-price contracts after discovery. The commercial offer for a full build is our e-commerce marketplace solution, delivered through e-commerce development.

When software agents place orders, every automated refund still needs a traceable entry; see our agentic commerce readiness guide.

What delivery record exists, and what does not

• RB Marketplace. A Laravel multi-vendor marketplace for West Africa and the diaspora, where vendors see earnings, commission deductions and payout requests, and the admin controls commission and payouts (RB Marketplace record).
• An EU fashion-tech marketplace. Netbase built a multi-vendor marketplace for an anonymous EU client, with Stripe Connect carrying split payments and vendor payouts (EU marketplace case).
• A multi-vendor module outside a classic marketplace. For a loyalty and rewards company in Dubai, Netbase delivered a reward shop platform with a multi-vendor module, fulfilment routing and a points-plus-cash checkout (loyalty reward shop record).

What does not exist. No published Netbase record describes a custom settlement engine, a reserve policy or a tax-reporting build, and none publishes a payout, reconciliation or dispute figure. The ledger, release and reconciliation practices above come from delivery practice and the cited provider documentation, not from a measured outcome.

Limits of this guide

• Payment, tax and consumer rules differ by country; the sources are cited as examples of obligations to design for, not as a complete list. Take legal and tax advice.
• Stripe and Adyen are named as examples of platform payment services, not as recommendations over other providers.

Next step

Share your commission model, payment regions and payout calendar, and we will book a solution review to sketch the ledger and the settlement flow. You can also see how Netbase works in retail and e-commerce or read more Netbase insights.

Related services and solutions