B2B Marketplaces: The Accounting Question Behind Every Transaction

Whether the marketplace books gross transaction volume as revenue or only its take-rate depends on whether it takes on meaningful risk and control in the transaction, such as inventory risk, pricing control, or responsibility for fulfillment, or whether it's simply facilitating a transaction between two independent parties. A controller who applies this test consistently across every transaction type on the platform, rather than defaulting to whichever presentation makes revenue look larger, keeps the books defensible if the marketplace is ever audited or goes through diligence for a fundraise or sale.

A marketplace that collects payment from a buyer and holds it before paying out the seller is, for that window of time, holding money that belongs to someone else, similar to the custodial fund question a payments platform faces. That held balance needs to be tracked separately from the platform's own operating cash, and a controller who conflates the two can hand leadership a balance sheet that looks healthier than the platform's actual financial position really is.

Many marketplaces charge a different take-rate depending on the product category, deal size, or whether a transaction came through an assisted sales process versus self-serve, and a controller who tracks realized take-rate by category, not one company-wide blended average, tells leadership which parts of the marketplace are actually generating the healthiest margin and which are being subsidized by volume from higher-take categories.

Say a large transaction closes and the seller expects payout, but the buyer's payment hasn't fully cleared or is subject to a dispute window. A marketplace that pays sellers out before it has actually received cleared funds is taking on credit risk on every transaction, and a controller tracking payout timing against actual funds received catches that gap before it becomes a real loss on a disputed or reversed transaction. A fractional CFO decides how much of that risk the marketplace should absorb to keep sellers happy versus how much payout timing should be tightened to protect the platform's own cash.

The national median salary for accountants and auditors is $83,680 a year, a real cost to weigh for a marketplace still proving out its take-rate model¹. For an early marketplace with modest transaction volume, a fractional CFO who sets the gross-versus-net policy and reviews it periodically can often cover the need alongside outsourced bookkeeping. Once transaction volume and held seller funds both grow meaningfully, the daily reconciliation discipline of a dedicated controller becomes necessary, not optional, given how directly errors here touch money that isn't the platform's own.

Say the marketplace wants to raise a funding round or pursue an acquisition offer based on its transaction volume. An investor or acquirer doing diligence will look hard at whether gross-versus-net revenue treatment has been applied consistently, whether held seller funds have ever been commingled with operating cash, and whether payout risk has been managed deliberately, since any of the three, handled carelessly, can raise real questions about the quality of the business's own financial controls. A marketplace that has had a controller enforcing this discipline from early on walks into that diligence process with a much stronger story to tell than one reconstructing the answers from old records under real time pressure.

An investor or acquirer doing diligence on a marketplace will typically look for these things:

• Gross versus net revenue treatment applied consistently across every transaction type, not chosen case by case.
• Held seller funds tracked separately from operating cash, with no history of commingling.
• Realized take-rate reported by category, instead of one blended company-wide average.
• Seller payout timing compared against actual cleared funds, with a deliberate policy on how much credit risk the platform absorbs.

A marketplace often launches with one take-rate across the board for simplicity, then discovers as it scales that some categories can support a higher take-rate than others based on how much value the platform adds versus how commoditized the underlying transaction is. A controller who has been tracking realized take-rate and margin by category from early on gives the fractional CFO real data to work from when it's time to introduce category-specific pricing, instead of guessing at what each category can actually bear based only on anecdote from a handful of seller conversations picked up here and there in passing.