Skip to main content

White-Label SaaS Reseller Bookkeeping: Principal vs. Agent Revenue Recognition

7 min readMike ThriftMike Thrift
White-Label SaaS Reseller Bookkeeping: Principal vs. Agent Revenue Recognition

Zendesk's research is blunt about it: half of customers will walk after a single bad service experience. If you're reselling someone else's SaaS product under your own logo, that statistic should worry you twice — because you're on the hook for the support experience, but you don't control the software behind it. That split between what you're responsible for and what you actually control is exactly what trips up the bookkeeping too.

White-label SaaS reselling has become one of the fastest ways for agencies, indie developers, and vertical-market founders to add recurring revenue without building a product from scratch. You take someone else's mature software, rebrand it, and sell it to your customers as if it were your own. It's a genuinely good business model. But the accounting underneath it is quietly more complicated than a normal subscription business, because every dollar that touches your bank account isn't necessarily a dollar you earned.

How the White-Label SaaS Model Actually Works

In a white-label arrangement, a software provider grants you a license — usually non-exclusive and non-transferable — to market and sell their platform under your own branding. You handle sales, customer relationships, and often first-line support. The provider handles the infrastructure, the code, and the uptime guarantee (99.9% is the common SLA benchmark in these contracts).

The economics vary a lot depending on how the deal is structured:

  • Revenue-share resellers pay the platform a cut of what they collect — typically somewhere in the 20-50% range, depending on volume and how much value-add support you provide.
  • Wholesale/fixed-cost resellers pay a flat per-account or per-seat cost regardless of what they charge the end customer, and keep the entire spread. Margins here can run 40-80% depending on the niche, since you're free to price your own markup.
  • Referral/affiliate-style splits pay a percentage — sometimes 50% for the first 12 months, sometimes a smaller recurring cut like 20% for the life of the customer.

None of these are hard rules; they're negotiated per contract. But the structure you sign determines how you're required to book the revenue, which is where most reseller bookkeeping goes wrong.

The Real Bookkeeping Question: Are You a Principal or an Agent?

This is the single most consequential decision in white-label SaaS bookkeeping, and it's governed by ASC 606's principal-versus-agent guidance. The question isn't philosophical — it changes what number shows up as your top-line revenue.

You're a principal if you control the service before it reaches the customer. Indicators include: you're primarily responsible for fulfilling the promise to the customer, you have discretion in setting the price the customer pays, and you carry some form of delivery or performance risk. If that's you, you record the full amount the customer pays as revenue, and the platform's cut as a cost of goods sold or direct expense.

You're an agent if you're really just arranging for someone else to provide the service — the underlying provider controls the software, sets material terms, and you're earning a fee or commission for bringing in the customer. If that's you, you only record your net commission as revenue. The gross amount that passes through you isn't yours to recognize.

Get this backwards and your financial statements lie to you. Recording gross revenue when you're actually an agent inflates your top line and makes your margins look thin and confusing. Recording net revenue when you're actually a principal understates how much business you're really doing — which matters a lot if you're ever trying to raise money, get a loan, or sell the company, since buyers and lenders read revenue, not gross transaction volume.

The test isn't per-contract, either — it's per performance obligation. If your white-label deal bundles the core software (which the provider controls) with implementation or support services (which you actually deliver), you may need to split the transaction: net recognition on the software, gross recognition on the parts you genuinely control.

Where the Numbers Get Messy: Payouts, Fees, and Chargebacks

Even once you've settled the gross-versus-net question, day-to-day bookkeeping for a reseller business has a structural problem: the money that lands in your bank account is never the same number as the revenue you earned.

A typical payout from your white-label platform partner has several deductions baked in before it ever hits your account:

  • The platform's revenue-share or wholesale cost
  • Payment processing fees
  • Refunds issued to your end customers
  • Chargebacks, which reverse a sale and usually carry their own penalty fee from the payment processor

If you just book "cash received" as revenue, you'll systematically misstate both your top line and your margins, and your books won't reconcile against what your platform partner reports to you. The fix is to record each component separately: gross billed revenue, the platform's fee or revenue share as a cost line, refunds and chargebacks as contra-revenue or a dedicated expense category, and only the net remainder as the actual bank deposit. That's more line items than a typical small business needs to track, but it's the only way your P&L will match reality — and the only way you'll notice if your chargeback rate is quietly eating your margin.

This is also where plain-text, version-controlled bookkeeping earns its keep. A white-label reseller's monthly close involves reconciling one payout number against four or five underlying components — gross sales, platform fees, refunds, chargebacks, and your net cut. Beancount.io lets you model that structure directly in your ledger with explicit accounts for each piece, so a payout discrepancy shows up as a diff you can actually read, not a mystery variance buried in a spreadsheet formula.

Contract Terms That Determine Your Accounting Treatment

Before you sign a white-label agreement, read it with your bookkeeper, not just your lawyer. A few clauses directly dictate how you'll need to book transactions:

  • Payment terms and invoicing schedule — how often you're paid, in what currency, and what happens on late payment from either side.
  • License grant language — does it describe you as reselling, sublicensing, or acting as an agent? Courts and auditors will look at the substance of the deal, but the contract's own language is the first signal.
  • Support and SLA responsibilities — who owns first-line support affects the "primarily responsible for fulfillment" test under ASC 606.
  • Term and termination — most white-label deals run 1-3 years with a 30-90 day termination notice. Know this date; it affects how you should treat any deferred setup fees or annual prepayments on your books.
  • IP ownership — the provider almost always retains full IP rights. This matters less for revenue recognition and more for how you'd account for any capitalized development costs (you generally can't capitalize software you don't own).

A Simple Monthly Reconciliation Routine

Whatever your revenue-recognition treatment, build a monthly habit around these steps:

  1. Pull the platform partner's payout report and your own sales log for the period.
  2. Confirm gross billed revenue matches what you invoiced or what the platform charged on your behalf.
  3. Separately log the platform's fee/revenue-share, refunds, and chargebacks as distinct line items.
  4. Confirm the net remainder matches your actual bank deposit.
  5. Flag any chargeback rate creeping upward — it's often an early signal of a support or fulfillment problem your platform partner should know about.

Skipping this reconciliation is how resellers end up surprised at tax time by a revenue number that doesn't match their bank statements, or worse, by a principal-vs-agent treatment that was wrong for a whole fiscal year.

Keep Your Reseller Books Clear From Day One

White-label SaaS reselling is a strong business model precisely because the software is someone else's problem — but your revenue recognition, chargeback tracking, and payout reconciliation are entirely your own. Beancount.io gives resellers plain-text, version-controlled accounting where every fee, refund, and revenue-share deduction is its own explicit entry, not a black box you have to reverse-engineer from a bank statement. Get started for free and keep your books as transparent as the margin you're actually earning.

Share this article