See how ScaleXP works with Xero or QuickBooks.
In a 15- or 30-minute demo, we’ll show the relevant workflows using example data and discuss how they could apply to your finance process. Complex requirements? Discuss them with us first.
Key takeaways
Short answer: A party is a principal, and reports revenue gross, if it controls the SaaS service before it is transferred to the end customer; otherwise it is an agent and reports only its commission or margin, net. For a SaaS vendor selling through resellers, the same analysis decides who its customer is: the reseller, so revenue is the price charged to the reseller, or the end user, so revenue is the end-user price with the reseller's margin as a selling cost.
The answer changes reported revenue, gross margin and every growth ratio built on them, without changing a dollar of cash. Finance teams selling through channel partners, referral partners or cloud marketplaces need to make the call contract by contract type and document it.
The principal or agent conclusion decides whether revenue is reported at the full price paid by the end customer or at the net amount kept. Take a $50,000 subscription sold through a partner who keeps $10,000. Reported revenue is either $50,000 or $40,000 for the vendor, and either $50,000 or $10,000 for the partner, depending on the analysis.
For a SaaS company, that difference flows into ARR, gross margin, revenue multiples and board reporting. Two companies with the same economics can report very different top lines. Auditors therefore expect a written analysis for each type of channel arrangement.
The question is common enough that the IASB issued Clarifications to IFRS 15 in April 2016 covering principal versus agent considerations, effective from January 1, 2018, and the IFRS Interpretations Committee finalized an agenda decision on a software reseller in April 2022. ASC 606 applies the same control-based principle for US GAAP reporters.
A party is a principal if it controls the specified good or service before it is transferred to the customer. The first step is to identify the specified service, which for SaaS is usually the right to access the software for the subscription term. The second is to assess whether the party controls that right before the end customer receives it.
The standards give three indicators that a party is a principal:
These indicators support the control assessment rather than replace it. No single indicator decides the outcome, and the weight given to each depends on the facts. Inventory risk is less common in SaaS, where licenses are often provisioned only when a customer signs, so fulfillment responsibility and pricing discretion tend to carry more weight.
A principal recognizes revenue at the gross amount of consideration it expects from the customer and records what it pays the other party as a cost. An agent recognizes revenue at the net amount it keeps, the commission or margin, at the point it has arranged for the service to be provided.
The table below shows the effect for an illustrative arrangement: the end customer pays $50,000 a year, and the reseller pays the vendor $40,000.
| Scenario | Party | Revenue | Cost or expense | Margin kept |
|---|---|---|---|---|
| Reseller is principal | Reseller | $50,000 | $40,000 cost of sales | $10,000 |
| Reseller is agent | Reseller | $10,000 | None | $10,000 |
| Reseller is vendor's customer | Vendor | $40,000 | None | $40,000 |
| Reseller is vendor's agent | Vendor | $50,000 | $10,000 selling expense | $40,000 |
Source: illustrative figures, not customer data.
Cash and margin are identical across the scenarios. Only reported revenue and the line where the partner's share appears change.
For a vendor, the principal or agent analysis of the reseller determines who the vendor's customer is. If the reseller obtains control of the subscription, sets the end-user price and takes responsibility for the customer relationship, the reseller is the vendor's customer. The vendor recognizes the price it charges the reseller, over the subscription term.
If the reseller only introduces the end user, and the vendor contracts directly with that end user, sets the price and provides the service and support, the reseller is acting as the vendor's agent. The vendor recognizes the end-user price as revenue and treats the reseller's share as a cost of selling. A referral fee paid for introducing a customer can also be a cost to obtain a contract, which may need to be capitalized and amortized.
Reseller margins should not be treated as discounts by default. A payment to a party that is the vendor's customer usually reduces revenue; a payment to an agent that is not the customer is usually an expense.
Sales through a cloud marketplace raise the same question with an extra party. The vendor typically lists the product, the end customer buys through the marketplace, and the marketplace bills the customer and keeps a fee.
The analysis depends on the contract terms: who the end customer contracts with, who sets the price, and who is responsible for the service. Where the vendor sets the price, provides the service and has a direct agreement with the end customer, the vendor may conclude that the end user is its customer, report revenue gross and record the marketplace fee as an expense. Where the marketplace sets terms and contracts with the end user, the marketplace may be the vendor's customer, and revenue is the net amount the vendor receives. Each marketplace agreement should be read on its own terms rather than assumed to match another.
When the reseller is the vendor's customer, the vendor still needs to decide when revenue starts. Under sell-in, the vendor recognizes revenue based on what it sells to the reseller. Under sell-through, it waits until the reseller sells to the end user.
For SaaS, the subscription is a service delivered over time, so revenue generally begins when the access is provisioned and the service period starts, which is usually when the end user is activated. Terms such as price protection, rebates, rights of return or payment that depends on the reseller's own sales are variable consideration. When those terms make the amount highly uncertain, the constraint on variable consideration can delay revenue until sell-through.
Our ASC 606 audit checklist for SaaS lists the other documents auditors usually ask for, and our guides to ASC 606 in SaaS companies and IFRS 15 in SaaS companies cover the wider five-step model.
Once finance has decided whether channel revenue is gross or net, the invoices in the ledger reflect that decision, and the remaining work is recognizing each subscription over its term. ScaleXP builds revenue schedules from your invoice data in Xero or QuickBooks, with contract details from HubSpot, Salesforce or Pipedrive, and prepares the revenue journals. The journals are posted once finance approves them, so the principal or agent judgment stays with the finance team.
See how the schedules and journals work on the revenue recognition automation for Xero and QuickBooks page.
Principal versus agent comes down to control of the SaaS service before it reaches the end customer. Identify the specified service, weigh fulfillment responsibility, inventory risk and pricing discretion, and decide whether revenue is gross or net. For vendors, the same analysis tells you whether your customer is the reseller or the end user. Document the conclusion for each type of arrangement and apply it consistently.
A reseller is a principal if it controls the SaaS service before it is transferred to the end customer, and an agent if it only arranges for the vendor to provide it. Indicators of control are primary responsibility for fulfillment, inventory risk and discretion in setting the price. The indicators support the control assessment; no single one decides it.
Gross reporting records revenue at the full amount the end customer pays, with the amount paid to the other party recorded as a cost. Net reporting records only the commission or margin the party keeps. Principals report gross and agents report net. The choice changes reported revenue and gross margin percentages, but not cash or the dollar margin.
It depends on who the vendor's customer is. If the reseller is the customer, the vendor recognizes the lower price it charges the reseller, so the margin does not appear in its revenue. If the reseller is the vendor's agent, the vendor recognizes the end-user price and records the reseller's share as a selling expense.
Cloud marketplace sales need a principal or agent analysis based on the marketplace agreement. Where the vendor sets the price, provides the service and contracts with the end customer, it may report revenue gross and record the marketplace fee as an expense. Where the marketplace contracts with the end user and sets terms, the marketplace may be the vendor's customer.
When the reseller is the customer, subscription revenue generally starts when access is provisioned and the service period begins, and is recognized over the term. Price protection, rebates, return rights or payment tied to the reseller's own sales are variable consideration. If they make the amount highly uncertain, revenue may be delayed until the reseller sells through to the end user.
Sources (checked October 2026): IFRS Foundation, IFRS 15 Revenue from Contracts with Customers; IFRS Foundation, Clarifications to IFRS 15; IFRS Foundation, Principal versus Agent: Software Reseller (IFRS 15).
More revenue recognition scenarios
How ScaleXP does this
ScaleXP builds revenue recognition schedules from your CRM contracts and prepares the journals for Xero or QuickBooks. Finance approves them before they’re posted. See how revenue recognition works in ScaleXP →
Close-time estimator
Your accounting system
How long does your close take today? Working days, roughly
Which of these do you still do manually? Select all that apply
Which of these takes the most time? Pick one
Your estimate
Your 3–5 day Xero or QuickBooks close could be closer to 2.5 days
Deferred revenue is where you would feel it first. ScaleXP prepares the schedules and journals for each task you selected from your live Xero or QuickBooks data. What stays with your team is the review and the posting decision.
Cue Technology saves 3–5 finance-team days a month. Xero customer
““Making the month-end revenue recognition process simplified.”
Revenue recognition
See how ScaleXP builds revenue schedules and journals from your invoice data.
In a 15- or 30-minute demo, we’ll show the relevant workflows using example data and discuss how they could apply to your finance process. Complex requirements? Discuss them with us first.