Use Stripe Revenue Recognition: configure rules and pull recognition reports

domain: docs.stripe.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

In-depth guide

Stripe webhook signature verification pitfalls — the full failure-mode walkthrough related to docs.stripe.com, checked against official docs, with linked verified routes.

Steps

  1. Enable Revenue Recognition in the Stripe Dashboard under Billing settings; this automatically generates default rules for common Stripe objects (invoices, subscriptions, charges).
  2. Create custom rules via the Stripe Dashboard (Revenue Recognition > Rules) to handle exceptions such as marking invoice line items as tax or fees, amortizing revenue over a custom period, or excluding specific customer segments; rules are applied to reports within 24 hours and show status 'active' once processed.
  3. Optionally use the Performance Obligations API (POST to the fulfillment events endpoint at docs.stripe.com/revenue-recognition/performance-obligations-api) to record fulfillment milestones for non-ratable obligations, passing target[type], period[start], amount, and currency.
  4. Trigger a report run via the Reports API (POST /v1/reporting/report_runs) with report_type set to one of the six supported Revenue Recognition report types and parameters for interval_start and interval_end.
  5. Poll the ReportRun object until status is 'succeeded', then download the CSV result from the result.url field.
  6. Ingest the CSV into your data warehouse, reconciling recognized_amount columns against GL deferred and earned revenue accounts by period.

Known gotchas

Related routes

Configure NetSuite revenue recognition rules and plans for straight-line and event-based recognition
docs.oracle.com/en/cloud/saas/netsuite · 6 steps · unrated
Pull revenue recognition data from a subscription billing rev-rec module
accounting-general · 6 steps · unrated
Use Stripe Radar rules with custom metadata attributes to implement merchant-category-level fraud controls
docs.stripe.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans