Principal vs agent SaaS revenue recognition is the ASC 606 judgment of whether your company controls a specified good or service before it reaches the customer. If it does, you are the principal and report revenue gross. If you only arrange for another party to provide it, you are the agent and report your fee or commission net.
This article gives you a way to decide, for each third-party product in your contracts, whether gross or net presentation is supportable and what to put on file to defend it. You will see a worked hypothetical where one $100,000 sale becomes either $100,000 or $20,000 of revenue, a table of contract patterns that push each way, and a worksheet you can copy into your close process.
"The conclusion is a judgment about control. It is not a score from a checklist."
— Aleksandar Stojanovic, CEO & Founder at FiscallionKey takeaways
- The unit of analysis is each specified good or service, not the whole contract, so one bundle can produce both gross and net answers.
- Invoicing the customer and collecting the cash do not settle the question. Control of the specified service does.
- Gross versus net changes revenue, growth and gross margin percentage, but not the gross profit dollars on the same sale.
Control of the specified service decides gross or net
ASC 606 asks whether the nature of your promise is to provide the good or service yourself or to arrange for someone else to provide it. PwC's revenue guide frames this as two steps: identify the specified good or service, then assess whether you control it before it transfers to the end customer.
Specified goods or services are viewed from the end customer's side. PwC notes they are not necessarily the same as your performance obligations. A marketplace operator may promise access to the marketplace, but the specified good is the product the customer buys on it.
Under Deloitte's roadmap, a principal obtains control of one of three things:
- A good or asset from the other party that it then transfers to the customer.
- A right to a service performed by the other party, which lets you direct that party to serve the customer on your behalf.
- A good or service from the other party that you combine with other goods or services to create the specified good or service.
Holding legal title only momentarily does not necessarily mean you control a good. In remarks on a consultation, SEC staff described not objecting to a gross conclusion where the registrant could direct another provider and customers had no contract with that provider. The speaker noted these are personal views, not the Commission's.
Then come the indicators in ASC 606-10-55-39: primary responsibility for fulfillment, inventory risk, and discretion in setting price. The guidance Deloitte quotes from ASU 2016-08 is explicit that they do not override the control assessment and should not be treated as a checklist. In practice, indicators are evidence, not a checklist.
Two more points matter for a SaaS founder. First, PwC states the assessment is not a policy election: you cannot choose net presentation because it looks tidier. Second, Deloitte explains that the analysis sits at the specified good or service level, so a single contract can contain both principal and agent elements.
How to run the assessment on a third-party product
Work through each third-party product in your contracts in this order.
- List the specified goods or services. Split the customer contract into distinct items from the customer's view: your platform, the third-party tool, implementation, training, support.
- Ask which route to control applies. Do you receive the good, hold a right to direct the vendor's service, or combine the vendor's service into something you deliver?
- Test the control conclusion against the indicators. Look at who is responsible for acceptability, who bears risk before a customer exists, and who sets price. Weigh them by relevance, not by count.
- Check what the customer actually agreed to. Which terms, such as a vendor end user license agreement, govern the service? Who handles outages, credits and warranties?
- Write the conclusion per specified service. Record gross, net, or split, with the facts relied on and the contract clauses.
- Model both presentations. Your forecast and board deck should show what changes if the conclusion changes.
Implementation work rarely changes the answer by itself. Deloitte's SaaS reseller spotlight says setup, configuration, data migration, integration and training services typically do not represent a significant integration service.
The same sale looks very different in revenue and margin
Take a clearly hypothetical case. You sell a one-year subscription to a third-party tool for $100,000, and you pay the vendor $80,000. The cash and the gross profit are identical either way.
| Hypothetical $100,000 sale | Gross (principal) | Net (agent) |
|---|---|---|
| Revenue | $100,000 | $20,000 |
| Cost of revenue | $80,000 | $0 |
| Gross profit | $20,000 | $20,000 |
| Gross margin | 20% | 100% |
That is same cash, same gross profit, with a fivefold swing in the top line and a margin percentage that changes completely. Scale this across a reseller line and your growth rate, margin mix and revenue-based comparisons all move.
Regulators treat the stakes seriously. When ASIC announced that Data#3 changed its policy after a review, it reported a $1.67 billion decrease to revenue for the year to 30 June 2023 and no impact to profit before tax. That case concerned an Australian listed company under AASB 15, not a US private SaaS company, but the mechanics are the same.
An Accounting Review study by Du, Louis, Schmidt and Wang found that before ASC 606, firms with principal-versus-agent exposure were more likely to receive revenue-related SEC comment letters and paid higher audit fees, and that these differences declined after adoption. The authors also suggest additional disclosure may help. If you report under IFRS 15 rather than US GAAP, the IFRS Interpretations Committee software reseller agenda decision walks through a fact pattern but did not conclude whether that reseller was principal or agent, because the answer requires judgment.
Contract patterns that push toward gross, net, or a split
These are hypothetical patterns drawn from the fact patterns in Deloitte's SaaS reseller guidance. None is an automatic outcome. Your own facts decide.
| Hypothetical pattern | Facts that point toward gross | Facts that point toward net |
|---|---|---|
| Resale of a third-party SaaS subscription | You can direct the vendor's service as an input and the customer contracts only with you | The customer accepts the vendor's terms, the vendor owns uptime and credits, and the service continues if your reseller agreement ends |
| Third-party component embedded in your product | You significantly integrate it, customers contract only with you, you fix issues, and you pay a fixed fee regardless of what you charge | The component is passed through with little integration and the vendor remains the visible provider |
| Bundle of implementation, training and a third-party subscription | You deliver the implementation and training yourself, so those items may be gross | The third-party subscription may be net, so the bundle is split by specified service |
Deloitte's own illustration of a reseller with full pricing discretion still concluded agent, because the vendor, not the reseller, continued to control the service. The same guidance notes that pricing discretion alone is not definitive, and that a commitment to a sales volume shortfall is typically viewed more like a variable commission than true inventory risk.
The reverse case matters for you as a vendor. In PwC's marketplace example, a software company sells through an online marketplace, sets the price and handles customer service. The marketplace never obtains control of the product, so the software company recognizes the full price paid by the end customer and records the marketplace's fee as an expense.
When a bundle is split, you also need an allocation approach. Deloitte describes two acceptable models for allocating the transaction price when you are principal for some items and agent for others, and says the better fit depends on whether you effectively have one customer or two.
What the conclusion does to your metrics and board deck
Once the accounting conclusion is made, the finance question is how it flows into the numbers you manage.
- Growth and revenue mix. Gross-reported pass-through lines grow revenue without growing gross profit. Net-reported lines shrink revenue but not profit.
- Gross margin percentage. Mixing pass-through resale with subscription revenue drags the blended margin down. Report the lines separately so the core product margin stays legible.
- CAC payback and LTV. If these use gross margin, pass-through lines will distort them. Use a gross profit basis by revenue line.
- ARR and net revenue retention. ARR is a management metric, not a GAAP figure. Define in writing whether it includes third-party pass-through amounts.
- Valuation conversations. The Accounting Review authors note that firms are often valued on revenue, so a gross-or-net change can alter how your top line reads even when profit does not.
"Your board deck should show GAAP revenue as concluded, with pass-through billings on a separate, labelled line. That keeps the discussion on gross profit dollars and decisions, not on the headline."
— Aleksandar Stojanovic, CEO & Founder at FiscallionWhat to do next
- Inventory every third-party product that appears in a customer contract, from your ledger and contract list.
- Write a short memo per specified service with the control analysis, facts relied on and clause references.
- Standardize contract terms where you can. Make it clear who the customer's counterparty is, who owns fulfillment, and who sets price.
- Run both presentations in the forecast so a change in conclusion is a switch, not a rebuild.
- Define ARR and margin reporting for pass-through lines before the next board cycle.
- Review the memo with your auditor before the close in which the treatment first appears.
Common mistakes and the replacement move
| Mistake | Replacement move |
|---|---|
| Treating invoicing or collecting cash as proof of control | Anchor on control of the specified service. Deloitte's reseller example notes invoicing alone does not decide it |
| Scoring the three indicators like a checklist | Use them as evidence for the control conclusion, weighted by relevance |
| Concluding at the contract level | Conclude per specified good or service and allow a split |
| Overweighting pricing discretion | Remember an agent can have pricing discretion in some cases, per ASC 606-10-55-39(c) |
| Choosing net or gross as a policy preference | Support the answer with facts, because it is not a policy election |
| Never revisiting after a new bundle | Reassess when contract terms or what you deliver change |
Practical asset: gross-versus-net assessment worksheet
Copy this into your close folder and complete one per specified good or service. It is open to read and reuse in full.
| Question | Evidence to attach | Leans gross | Leans net |
|---|---|---|---|
| What exactly is the specified good or service the customer buys? | Customer contract, order form | You deliver it | You arrange for another party to deliver it |
| Do you obtain the good, a right to direct the service, or integrate it? | Vendor agreement, product architecture notes | Any one of the three | None of the three |
| Who is responsible for fulfillment and acceptability? | Support terms, vendor end user license agreement | You | Vendor |
| Who bears risk before a customer exists? | Purchase commitments, minimums | You, through real commitments | Vendor, or only volume-linked payments |
| Who sets the customer price, and how much discretion? | Price lists, reseller agreement | You, combined with other facts | Vendor, or limited discretion |
| What happens if your agreement with the vendor ends? | Termination clauses | Service stops or you can redirect it | Vendor keeps serving existing customers |
Then record:
- Conclusion per specified service: gross, net, or split.
- Reviewer and date: who signed off and when.
- Allocation approach: if split, which method and why.
- Reassessment trigger: the contract or product change that reopens the analysis.
Remember the table is a record of evidence, not a scoring sheet. Rows leaning one way do not add up to an answer.
Where senior finance judgment fits
Your accountant or bookkeeper can maintain the ledger and may well write the technical memo. The gap we usually see is ownership of the consequences: forecast, margin reporting, board framing and the next bundle decision.
Fiscallion works above the ledger and is not a bookkeeping firm. We turn reliable accounting data into forecasts, scenarios and board decisions for B2B SaaS companies at $5-100M ARR. Each client works directly with Aleksandar Stojanovic at the CFO layer: senior-partner ownership on every engagement, not an account-manager or junior-team handoff. His approach draws on FP&A leadership experience gained through the growth of a SaaS company to €100M ARR.
If you want the gross-or-net conclusion carried through your accrual close and models, see how Fiscallion approaches accrual accounting for B2B SaaS.
FAQ
How do we determine whether to report our SaaS revenue gross or net as a principal or agent?
Start with the specified good or service, not the contract total. Then ask whether you control it before it transfers to the customer, using the three routes to control and the indicators as supporting evidence. If you control it, report gross. If you arrange for another party to provide it, report net.
What contract evidence do auditors expect to support a principal vs agent revenue classification?
Confirm the exact list with your auditor, but the useful evidence maps to the guidance. That means the customer contract, the vendor or reseller agreement, and the vendor's end user license terms. It also means support and credit responsibilities, pricing authority, purchase commitments and termination clauses. A short memo linking those facts to the control conclusion ties it together.
Can our current accountant handle gross versus net revenue reporting, or do we need specialized SaaS accrual support?
Your accountant may be fully capable of the analysis, and Fiscallion works alongside existing accountants and bookkeepers. The question is whether someone with senior judgment owns the contract-level conclusion and its effect on forecasts, margin reporting and board materials. Because it is not a policy election, it needs accountable ownership either way.
When should we reassess our principal or agent status after adding new third-party bundles?
Reassess when the facts behind the conclusion change, since the analysis is per specified good or service. Typical triggers are a new third-party product in a bundle, a change in who contracts with the customer, a change in fulfillment or support responsibility, new purchase commitments, or a change in pricing authority. Write the trigger into the original memo so the review is routine.
The decision to document
Gross or net is not decided by who sends the invoice. It is decided by who controls the specified service before it transfers, and the answer can differ inside one bundle.
Write down the conclusion per service, model both presentations, and define how pass-through lines enter ARR and margin. Then a new bundle becomes a review item, not a surprise at the next audit or board meeting.
