ASC 606 Revenue Recognition for Merchant of Record Platforms

Introduction#

If you run a Merchant of Record flow, cash movement is not your revenue policy. Under ASC 606, the hard part is that customer payment, processor settlement, and the point when revenue is actually earned can sit on different dates and in different records.

That mismatch can create reporting risk for MoR teams. A platform can collect funds and see processor activity, yet still need a different recognition outcome under GAAP because Topic 606 ties revenue to what was promised and when that promise was satisfied. The standard is commonly applied through a five-step model. In practice, the real work is control: which contract governs, what the performance obligation is, what data proves satisfaction, and who signs off when the facts are mixed.

For a Merchant of Record, legal responsibility matters, but it does not answer the accounting question on its own. The red flag is simple: if your contract language, order-to-cash cycle, and settlement data tell different stories, do not force them into one policy just because the operational flow feels familiar. That is especially true when processor data only tells the cash side of the story. In Adyen-based setups, for example, the processor may hold the records needed for the cash portion of the order-to-cash cycle, but you still need separate evidence for recognition timing and journal support.

This guide is for compliance, legal, finance, and risk owners who need a control-first way to handle the ASC 606 revenue recognition problem in a Merchant of Record platform. The goal is not to turn it into a giant accounting project before the basics are stable. It is to help you reach a repeatable close position using records you already own or can reasonably produce.

Before you start#

Before the later steps are useful, make sure you have three things:

• Access to the contract with the customer terms that actually govern the sale
• A clear view of your payment and settlement records across the order-to-cash cycle
• Named owners in finance, legal, and risk for policy calls and exceptions

Start with one recent transaction and ask three questions: what document defines the promise, what event proves that promise was satisfied, and what record supports the cash movement? If those answers come from different places, that is normal. If nobody can connect them, stop and fix that before month end.

The rest of the guide follows a practical sequence: map contracts and performance obligations, set principal versus agent and transaction price rules, build close controls and an evidence pack, then assign ownership and escalation rules. The outcome should be a working structure, not just theory. You want decision steps, approval boundaries, escalation triggers, and a copy-paste month-end checklist tied to operating records that auditors can trace.

What changes under ASC 606 when you are the Merchant of Record#

Under ASC 606, the main change for a Merchant of Record is not the five-step model itself. It is the need to document control, performance obligations, and revenue presentation choices for each arrangement with traceable records.

1. Evaluate each arrangement on its own facts. Reseller and platform arrangements can produce different accounting outcomes based on specific facts and circumstances, especially when third parties are involved. Identify the specified distinct good or service being transferred, then tie it to the governing contract and your order-to-cash records.

2. Run principal-versus-agent analysis at the specified good or service level. This judgment often drives the presentation outcome even when operations look similar. ASC 606-10-55-36A points the analysis to the specified goods or services, so your support should show what was transferred, who controlled it before transfer, and what operating evidence supports that conclusion. If contract terms and operating behavior conflict, treat that as a red flag and escalate to a CPA before finalizing policy.

3. Use IFRS 15 alignment for consistency, not as a shortcut. Alignment can help across jurisdictions, but you still need a GAAP-ready Topic 606 rationale and support. If terms change through contract modifications, reassess rather than carrying forward the prior conclusion.

If you want a deeper dive, read ASC 606 for Merchant-of-Record Platforms: Principal vs Agent Revenue Recognition.

What to prepare before month one close#

Before month one close, make your ASC 606 judgments traceable from contract to entry without manual reconstruction.

Step 1: Assemble a minimum evidence set. Keep one compact evidence pack for each contract type or selling motion you expect in month one. Include the contract with the customer, a payment flow map, clear performance-obligation definitions, and the rule used to determine transaction price. If discounts, credits, or variable amounts apply, document how they affect recognized revenue, not just billing display.

Run a trace test on one sample order before close. Follow customer acceptance through billing, processor records, and the draft accrual output. If you cannot show where the performance obligation is identified and satisfied, you are not ready for close.

Step 2: Define system-of-record boundaries. Assign one authoritative source per close question and write it down with the exact reports or exports the team will use. Keep cash movement evidence separate from revenue-recognition evidence so settlement timing does not override ASC 606 logic. Avoid using multiple exports for the same metric in the same close cycle.

Step 3: Create a control log for Topic 606 judgments. For each judgment, record the owner, approval date, review cadence, related contract template or market, and where the conclusion is documented. Include the supporting evidence used for that conclusion.

That is what lets you react when terms or pricing logic change. You can quickly identify which conclusion is affected and who must review it.

Step 4: Pre-agree escalation paths. Name finance, legal, and risk/compliance approvers before month one starts. Define what triggers escalation, such as new contract language, new markets, pricing-rule changes, or repeated close exceptions. If legal terms and operational evidence diverge, pause and escalate before finalizing policy.

If you use automated revenue reports, treat them as operational output, not evidence on their own. Automation can help with accrual accounting and ASC 606/IFRS 15 reporting, but it does not replace the evidence pack or control ownership.

You might also find this useful: A Guide to Revenue Recognition for SaaS Companies.

Step 1 map contracts and performance obligations to the order-to-cash cycle#

Map each contract to observable order-to-cash events at the performance-obligation level so recognition decisions are traceable in practice. Under ASC 606, Step 1 is identifying the contract with a customer, Step 2 is identifying performance obligations, and Step 5 is recognizing revenue when or as the performance obligation is satisfied. Build your map so each obligation is tied to the event that shows control transferred.

If one contract template supports different product motions, split recognition logic by obligation type instead of forcing one rule across all flows. The legal paper may be the same, but the satisfaction event may not be.

Build a contract-to-event map#

For each contract type or selling motion, capture the same fields:

• contract template name and version
• performance obligation in plain English
• your conclusion: point in time or over time
• the exact order-to-cash event tied to satisfaction
• the evidence retained for that event
• the transaction-level ID linking contract, billing line, and journal output
• any transaction price note that affects recognized amount

Document proof, not just labels#

Do not stop at labeling an obligation. Record the specific evidence for the recognition trigger and make sure it aligns to when control transfers to the customer.

Use one sample order per contract type as a trace check: accepted terms, billed item, trigger event record, journal line. If that path depends on manual reconstruction, the map is not ready.

Related: Subscription Revenue Recognition for Bundles and Discounts: ASC 606 Allocation Rules.

Step 2 set principal vs agent and transaction price rules#

Treat this as a control judgment first: in a Merchant of Record flow, principal versus agent under ASC 606 depends on who controls the good or service before transfer to the customer, not on contract labels or who collected cash.

Build the principal versus agent table#

Use one decision table per selling motion, market, or contract variant when operating facts differ. Pair contract terms with operating evidence so the conclusion is based on how the flow actually works.

Treat this as a documented judgment, not a weighted scorecard. If indicators are mixed, do not force a numeric result, and do not rely on contract naming alone.

Checkpoint: sample one real order per scenario and confirm the evidence supports who fulfilled, who set final price, and how revenue was presented. If that requires a manual narrative rebuild, the classification is not close-ready.

Define transaction price rules before exceptions show up#

Write the transaction price policy before the edge cases arrive. ASC 606 treats variable consideration and changes in transaction price as explicit topics, so define both in policy and approvals.

For each adjustment type, document what it is, when it changes revenue, what evidence is required, and who approves exceptions. At minimum, cover standard discounts, customer credits, and variable components.

• For preapproved commercial discounts, document the allowed terms and the accounting treatment finance approved.
• For nonstandard discounts or credits, retain the approval and note how they changed the timing or amount of revenue.
• For changes to customer terms, market structure, or seller responsibilities, route the issue to legal and capture CPA review before policy sign-off.

Tool settings can support processing, but they do not establish the ASC 606 conclusion by themselves.

Escalate mixed indicators and preserve the judgment memo#

Use a hard if-then rule: if control indicators are mixed, or facts are inconsistent across markets for the same flow, escalate and pause policy finalization until legal and CPA review.

Keep a separate judgment memo for each scenario. Include the ASC 606 logic, the GAAP position, operating facts, evidence reviewed, approvers, and effective date, then revisit the memo when contracts or business models change so the audit trail stays current.

This pairs well with our guide on What is a Merchant of Record (MoR) and How Does It Work?.

Step 3 build the month-end close controls and evidence pack#

Build the close so revenue journals are posted only after processor activity, subledger output, and accrual entries reconcile, and the ASC 606 judgment is reproducible.

Assemble one close pack from source to journal#

Create one month-end pack per material selling motion or processor setup. Include processor exports, subledger outputs, final revenue journals, and the reconciliation tying them together. If you run multiple processors, reconcile each one separately before rolling up to the general ledger.

For Stripe flows, reconcile fee logic by pricing model rather than as a flat deduction. Standard pricing can include 2.9% + 30¢ for domestic cards, with add-ons like +0.5% for manually entered cards, +1.5% for international cards, and +1% for currency conversion. Managed Payments adds 3.5% per successful transaction in addition to standard processing fees, and country-specific pricing can supersede listed Managed Payments tables.

Require posting checkpoints before revenue journals go final#

Use explicit sign-off gates before final posting:

If completeness, cutoff, or classification is unresolved, hold the final revenue posting.

Add a monthly variance review for performance-obligation mix, transaction price adjustments, and reversal patterns. Large shifts can be commercial, but they can also indicate mapping breaks or policy drift.

Automation can help at scale (for example, Stripe Revenue Recognition), but keep manual review checkpoints for high-risk judgments and exceptions. Archive the same audit bundle each close cycle: source reports, reconciliations, journal support, exception approvals, and final reviewer sign-off.

We covered this in detail in Merchant of Record for Platforms and the Ownership Decisions That Matter.

Step 4 assign ownership and escalation across finance legal and risk#

ASC 606's five-step model tells you what to assess, but it does not assign decision owners. Your team still needs an internal governance layer across finance, legal, and risk. Keep that layer explicit and documented so contract, pricing, and revenue-policy decisions are reviewed before they create close noise.

Anchor ownership to the ASC 606 steps#

Use the model as the shared frame: Step 1 covers identifying the contract, Step 4 covers allocating transaction price to performance obligations, and Step 5 covers recognizing revenue when or as obligations are satisfied. Then map your internal owners to those decisions in your own policy documentation, since that assignment is an operating choice rather than a rule stated in the standard excerpts.

Define escalation in policy, not in hindsight#

Set escalation criteria in writing for changes that could alter your ASC 606 conclusion, contract interpretation, or control execution. Keep the criteria visible to teams that ship contract and pricing changes so accounting review happens before go-live, not after month-end exceptions.

Keep a durable decision record#

Track each escalated decision in a consistent log with the issue, conclusion, approvers, and decision date. That record helps prevent policy drift and makes your month-end evidence easier to trace back to the underlying ASC 606 judgment.

Common mistakes that create audit surprises and how to recover#

Most audit surprises in this area come from repeatable control failures, not unusual accounting edge cases. Use these four checks to recover before you finalize close.

1. Mistake: treating payment receipt as recognized revenue.

Recovery: Re-anchor recognition to when the performance obligation is satisfied. Payment can support evidence of an arrangement, but you still need support that delivery or service completion occurred. For each material revenue stream, confirm you can show the contract terms, the trigger event, and the record that supports satisfaction.

1. Mistake: using one global policy when contract or control patterns differ.

Recovery: Segment policy by scenario, then retest your close outputs against those scenarios. If market setup, terms, or control patterns changed, do not assume legacy mapping still applies.

1. Mistake: assuming automation equals compliance.

Recovery: Use automation to improve accuracy and reduce manual effort, but keep explicit judgment reviews in your close process. Add specialist sign-off points when facts change, indicators are mixed, or outputs cannot be explained from the contract and recognition logic.

1. Mistake: finalizing journals with incomplete close evidence.

Recovery: Enforce a minimum evidence checklist before final posting, including current terms, recognition support, proof of delivery or service completion, reconciliations, and documented exception approvals. If required support is missing, hold the journal and log the gap.

For a step-by-step walkthrough, see How to Choose a Merchant of Record Partner for Platform Teams. Want a quick next step? Browse Gruv tools.

Final takeaway and copy-paste checklist#

Use a close checklist that mirrors ASC 606's five-step structure and your actual records. At minimum, anchor it to Step 1: Identify the Contract With a Customer, Step 2: Identify the Performance Obligations in the Contract, and Step 5: Recognize Revenue When or as the Performance Obligation is Satisfied, and make sure your support also covers presentation and disclosures.

1. Confirm the contract is identified and current. For each customer contract, keep the version you relied on for the period.
2. Map obligations to recognition. Document each performance obligation and the point at which revenue is recognized when or as it is satisfied.
3. Document key judgments in writing. Keep the reasoning, support, and approvals together so the conclusion is reviewable.
4. Keep records traceable end to end. Your close file should let another reviewer follow the path from contract terms to the recorded revenue outcome.
5. Reassess when facts change. If contract terms or operating facts shift, reopen the analysis before carrying the prior conclusion forward.
6. Archive a repeatable file. Retain the full support so the same conclusion can be reproduced in a future period.

Related reading: Building Subscription Revenue on a Marketplace Without Billing Gaps. Want to confirm what's supported for your specific country/program? Talk to Gruv.