Your R&D partner just wired you $130,000 — half the joint development costs plus your cut of the product profit. You book it as revenue, your top line jumps, and your lender smiles. Then your auditor asks one question — was your partner actually your customer? — and the whole entry unravels. In a collaborative arrangement, money from a partner is not automatically revenue, and getting the answer wrong distorts every margin a reader computes from your income statement.
This guide explains how ASC 808, Collaborative Arrangements, splits revenue, costs, and IP between R&D partners: what qualifies, the ASC 606 customer test that decides what counts as revenue, where each participant books its share, and the mistakes that draw audit adjustments.
What counts as a collaborative arrangement
ASC 808 applies to a joint operating activity with two or more parties where every participant is both an active participant and exposed to significant risks and rewards that depend on the commercial success of the activity. Three features must all be present:
- A joint operating activity. The parties pursue a shared commercial goal together — developing a drug candidate, co-developing software, jointly producing a film, or operating a shared facility.
- Active participation by everyone. Each party takes a real role: one performs the research while the other manufactures and sells, or both contribute distinct development work. A passive investor writing a check is not a participant.
- Shared risk and reward. Each party's payoff rises and falls with the commercial outcome. Fixed-fee service providers and licensors collecting guaranteed royalties regardless of success generally fail this test.
One more scoping rule matters: the activity must not be conducted primarily through a separate legal entity. If you formed a joint venture corporation and operate through it, you are in consolidation or equity-method territory under ASC 810 or ASC 323, not ASC 808.
Classic small-business shapes include a biotech startup pairing with an established manufacturer, two software shops co-developing a product one of them will sell, and a hardware startup splitting development costs with its contract manufacturer.
ASC 808 covers presentation and disclosure — not recognition
Here is the surprise most first-time readers miss: ASC 808 provides no recognition or measurement guidance of its own. It tells you where things go on the income statement and what to disclose, but not when to record them or at what amount. For recognition and measurement you must analogize to other authoritative literature — most often ASC 606 — or, where no analogy fits, adopt a reasonable, rational, and consistently applied accounting policy.
That gap is exactly why the FASB issued ASU 2018-18 in November 2018, effective for public companies in fiscal years starting after December 15, 2019 and for private companies a year later. It clarifies the interaction between ASC 808 and ASC 606: when a collaborative participant is a customer for a distinct good or service, the transaction is accounted for fully under ASC 606. Everything else stays under ASC 808's presentation rules and your own documented policy.
Note what the update deliberately left out: transactions directly related to either participant's third-party sales, and non-revenue transactions between participants, still have no dedicated recognition rule. Your policy election covers them, so write it down before the auditor asks.
The ASC 606 customer test, unit by unit
The customer test is applied at the unit of account level — each distinct good or service, or bundle — not to the arrangement as a whole. One collaboration can easily produce some units inside ASC 606 and others outside it. For each unit, ask two questions:
- Are you transferring a distinct good or service? Use ASC 606's own distinctness guidance. R&D services, a license to IP, and manufactured product are evaluated separately.
- Is the counterparty a customer for that unit? A customer is a party that contracts to obtain goods or services that are an output of your ordinary activities in exchange for consideration. If you routinely sell R&D services to others and your partner contracted for exactly that, your partner is your customer for that unit — even though you are collaborators on the overall project.
When both answers are yes, the full ASC 606 machinery applies to that unit: recognition, measurement, presentation, and disclosure. When either answer is no, ASC 808 forbids presenting the consideration as revenue from contracts with customers. Instead you present it by analogy or policy — typically as a reduction of the related expense or as other income, as the example below shows.
Worked example: how each participant books its share
Suppose DevCo and SellerCo sign a 50/50 joint development and marketing agreement. DevCo performs all R&D; SellerCo reimburses half. SellerCo markets, manufactures, and sells the finished product and pays DevCo half its profit as a royalty. This year DevCo incurs $200,000 of R&D. SellerCo records $1,000,000 of sales with $400,000 of cost of goods sold and $200,000 of marketing expense, leaving $400,000 of profit. SellerCo pays DevCo $300,000: $100,000 of R&D reimbursement plus $200,000 of profit share.
SellerCo: gross third-party sales, split collaborator payment
Transactions with third parties follow the principal-versus-agent guidance in ASC 606. SellerCo controls the product sold to customers, so it is the principal and reports 100 percent of sales, cost of sales, and marketing expense gross. The $300,000 payment to its collaborator is then split by nature: the $200,000 profit share lands in cost of goods sold, and the $100,000 R&D reimbursement lands in R&D expense.
| SellerCo income statement | Amount |
|---|---|
| Sales | $1,000,000 |
| Cost of goods sold ($400,000 + $200,000 profit share) | ($600,000) |
| Marketing expense | ($200,000) |
| R&D expense (cost-share reimbursement) | ($100,000) |
| Net earnings | $100,000 |
In your books, the two halves of that payment look like ordinary expense postings tagged to the collaboration:
2026-01-01 open Assets:Checking USD
2026-01-01 open Expenses:RD:Collaboration USD
2026-01-01 open Expenses:COGS:Collaboration-Profit-Share USD
2026-04-10 * "DevCo" "50% cost-share reimbursement, Q1 joint R&D"
Expenses:RD:Collaboration 100000.00 USD
Assets:Checking -100000.00 USD
2026-04-10 * "DevCo" "50% profit share on collaboration product sales"
Expenses:COGS:Collaboration-Profit-Share 200000.00 USD
Assets:Checking -200000.00 USDDevCo: it depends on the customer test
DevCo records its full $200,000 of R&D expense — it performed the work. How it presents the $300,000 received from SellerCo depends entirely on whether SellerCo is its customer.
If SellerCo is a customer: DevCo routinely sells R&D services to others, so the development work is an output of its ordinary activities. DevCo applies ASC 606 and presents the full $300,000 received — reimbursement and profit share alike — as revenue. It reports no third-party sales, cost of sales, or marketing expense, because it is not the principal on those transactions.
| DevCo income statement (customer) | Amount |
|---|---|
| Revenue | $300,000 |
| R&D expense | ($200,000) |
| Net earnings | $100,000 |
If SellerCo is not a customer: DevCo is a product company whose ordinary output is finished devices, not R&D services. ASC 606 does not apply, so none of the $300,000 may be called revenue from contracts with customers. The likely presentation: the $100,000 reimbursement reduces R&D expense, and the $200,000 profit share appears as other income.
| DevCo income statement (not a customer) | Amount |
|---|---|
| R&D expense ($200,000 − $100,000 reimbursement) | ($100,000) |
| Other income (profit share) | $200,000 |
| Net earnings | $100,000 |
Net earnings are identical either way — but revenue differs by $300,000. Any reader screening on revenue growth, gross margin, or revenue multiples sees a completely different company depending on which presentation you chose. That is why the customer test is the highest-stakes judgment in the arrangement.
The matching DevCo-side bookkeeping for the not-a-customer outcome nets the reimbursement against expense and isolates the profit share:
2026-01-01 open Assets:Checking USD
2026-01-01 open Expenses:RD:Collaboration USD
2026-01-01 open Income:Other:Collaboration-Profit-Share USD
2026-03-15 * "Lab vendor" "Q1 joint R&D spend under collaboration agreement"
Expenses:RD:Collaboration 200000.00 USD
Assets:Checking -200000.00 USD
2026-04-10 * "SellerCo" "50% cost-share reimbursement, Q1 R&D"
Assets:Checking 100000.00 USD
Expenses:RD:Collaboration -100000.00 USD
2026-04-10 * "SellerCo" "50% profit share on collaboration product sales"
Assets:Checking 200000.00 USD
Income:Other:Collaboration-Profit-Share -200000.00 USDThird-party sales: gross or net
Both participants sell nothing to each other here — the end customer buys from SellerCo. ASC 808 sends every participant to the ASC 606 principal-versus-agent guidance for third-party transactions: whoever controls the good or service before it transfers to the customer reports gross revenue and gross cost; the other reports only its net share of the economics.
In practice the selling participant is usually the principal and the development participant reports nothing from the third-party sale itself — its economics arrive through the collaborator payment, presented as the customer test dictates. The error to avoid is double-counting: if SellerCo reports the full $1,000,000 of sales, DevCo must not also report a revenue line derived from those same sales unless its ASC 606 analysis genuinely supports it.
Cost reimbursements and profit shares, side by side
| Payment | Customer (ASC 606 applies) | Not a customer (ASC 808 + policy) |
|---|---|---|
| R&D cost reimbursement | Revenue, recognized per ASC 606 | Reduction of R&D expense |
| Profit share / royalty on sales | Revenue, recognized per ASC 606 | Other income (or analogous line) |
| Upfront license fee for distinct IP | Revenue per ASC 606 if distinct and customer | Policy election, disclosed |
Two subtleties deserve attention. First, an upfront license fee is its own unit of account: a license to functional IP transferred to a customer can be ASC 606 revenue even when the surrounding cost-sharing is not. Second, whatever policy you elect for out-of-scope units must be applied consistently across periods and disclosed — auditors test the consistency, not just the choice.
Disclosure: tell readers what you did
ASC 808's disclosure requirements apply regardless of which side of the customer test you land on. For each material collaborative arrangement, disclose the nature and purpose of the arrangement, your rights and obligations, the accounting policy you applied — including where each class of collaborator payment appears on the income statement — and the amounts involved. Units accounted for under ASC 606 additionally carry that standard's disclosure requirements.
For a small business, a short footnote covering the arrangement's economics, the customer conclusion and why, and a table of where each payment landed will satisfy most reviewers. The conclusion matters more than the length: state plainly whether your partner is your customer for each distinct good or service and why.
Common mistakes that draw adjustments
- Calling every partner payment revenue. Reimbursements and profit shares from a non-customer presented as top-line revenue overstate growth and margins. Run the customer test per unit of account before choosing a line.
- Netting third-party sales. The principal reports gross sales and gross costs. Recording only your net profit share as revenue understates both and breaks comparability.
- Treating the arrangement as one unit. A collaboration with R&D services, a license, and manufactured supply has at least three units to evaluate. Bundling them into a single conclusion misapplies the guidance.
- No written policy for out-of-scope units. ASC 808 requires a reasonable, rational, consistently applied policy where no analogy fits. An undocumented choice made at year-end looks like earnings management even when it is correct.
- Skipping the separate-entity check. If operations run through a jointly owned company, ASC 808 likely does not apply at all — consolidation or the equity method does.
Your month-end checklist
Before you close a period containing collaboration activity, walk through these steps: confirm the arrangement still meets all three ASC 808 criteria and is not run through a separate entity; list each distinct good or service and record your customer conclusion with reasoning; verify the principal on third-party sales reports gross; place each collaborator payment on its correct line — revenue, expense reduction, or other income; and reconcile the footnote amounts to the ledger. Do that every quarter and the auditor's hardest question becomes your easiest answer.
