Source
Revenue reporting & accounting handoff — found from sitemap — Metronome
Checked for Metronome on 10 Nov 2026
- Page
- https://docs.metronome.com/guides/reporting-insights/financial-reporting/asc-606-revenue-recognition
- Checked
- 10 Nov 2026, 11:48 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:b5026a86264e6b9f0943104f88b0bfc270c9db7ad797b095f827f3e1ac7a9800
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Asc606 guide Report an error
“This guide explains U.S. GAAP’s ASC 606 Revenue from Contracts with Customers in practical terms and helps illustrate how each step of the standard connects to Metronome’s data model and product features.”
-
Not revenue recognition platform Report an error
“Metronome itself is not a revenue recognition platform and does not generate revenue journal entries or make accounting determinations.”
-
Customer responsibility Report an error
“You are solely responsible for determining and applying your revenue recognition policies. Metronome recommends that you consult with qualified accounting and revenue recognition professionals to ensure compliance with applicable standards.”
-
Daily granularity Report an error
“Daily granularity of usage and service delivery”
-
Breakdowns Report an error
“Breakdowns by product, customer, commitment, and revenue category”
-
Contract object Report an error
“Metronome maintains a centralized contract object containing pricing, terms, product access, commitments, credits, and billing schedules, with flexible rate structures and preserved version history.”
-
Supported pricing models Report an error
“Pay-as-you-go Prepaid usage commitments Subscriptions with usage-based overage Enterprise credits with tiered pricing Bundled or hybrid pricing structures Seats and seats with overages pricing models”
-
Obligation tags Report an error
“Obligation tags in the data model to flag each charge or usage event”
-
Real time ingest Report an error
“Ingesting billions of usage events via APIs”
-
Audit trail Report an error
“Every billed amount links back to original usage, applied rate, and adjustments, with consistent tags and an immutable audit trail.”
-
Reconciliation systems Report an error
“Reconciliations with systems such as Salesforce, Stripe, ERPs, and customer data warehouses”
-
Breakage forecasting Report an error
“Ability to track and estimate unused commitments and credit rollovers for future revenue impact analysis.”
-
Contract ID field Report an error
“Unique contract ID field in all relevant data exports and API calls”
-
Contract version history Report an error
“Store version history to retain contract amendments without overwriting historical data”
-
Contract hierarchy Report an error
“Support contract hierarchy to provide linkage of contracts (treat multiple related agreements as one contract from an accounting perspective) if needed”
-
Parent child linkage Report an error
“Metronome supports the linkage of related contracts through its parent-child account linkage feature, in which multiple contract IDs can be linked together.”
-
Modification tracking Report an error
“Metronome can track modifications and maintain version history and an audit trail for such amendments, but you must ultimately decide how to treat them under ASC 606.”
-
Obligation mapping Report an error
“Product and rate card structure allows mapping SKUs/usage metrics to specific obligation categories or obligation ID”
-
Retroactive tagging Report an error
“Ability to retroactively tag historical data if obligations change”
-
Price capture fields Report an error
“Granular price capture provides separate fields for fixed, variable, discounts, credits”
-
Currency handling Report an error
“Currency handling supported by storing original and functional currency amounts”
-
Historical allocation data Report an error
“the ability to retain raw amounts even after pricing changes in case a customer’s SSP changes and allocations are needed for past periods”
-
Billed vs earned views Report an error
“Billed vs. earned views in exports to separate invoicing from recognition”
-
Long term retention Report an error
“Long-term retention of usage and billing data for audit lookbacks”
-
Export options Report an error
“This data is accessible via Metronome’s APIs or data export functionality and can be integrated into external revenue subledgers, ERPs, or custom reports exportable as CSVs.”
-
Data model fields Report an error
“Invoice timestamps (invoices.start_timestamp, invoices.end_timestamp) to define service periods Line item attributes (line_items.product_id, line_items.commit_id) for product-level revenue recognition Credit and balance ledger entries to support treatment of prepaid, postpaid, free credits, and expirations”
-
On demand recognition Report an error
“Revenue recognition: Recognized at the time of invoicing, as usage is incurred.”
-
Prepaid commit recognition Report an error
“Revenue recognition: Prepayment deferred initially; recognized as revenue as credits are consumed.”
-
Prepaid expiration entry type Report an error
“balances_ledger.entry_type = 'prepaid_segment_expiration' indicates credit expiration”
-
Postpaid trueup mapping Report an error
“invoices.type = 'CONTRACT_TRUEUP' balances_ledger.entry_type = 'postpaid_trueup'”
-
Free credits treatment Report an error
“Revenue recognition: Not deferred or recognized as revenue. May offset recognized revenue as contra-revenue.”
-
Invoice status recognized Report an error
“invoices.status = 'FINALIZED': used for recognized revenue invoices.status = 'DRAFT': used for revenue accruals”
-
Custom fields sku Report an error
“Metronome clients can define performance obligations at the SKU level using custom fields, which are available in data exports for revenue allocation and categorization.”
-
Rate card capabilities Report an error
“Rate cards define default pricing, and can accommodate tiered pricing, composite charges, commit-specific pricing, scheduled price changes, and dynamic overrides.”
-
Contract framework support Report an error
“Multi-year ramp deals Opt-out and renewal clauses Access schedules for commitments Parent-child account structures a.k.a. account hierarchy”
-
Recognition timing model Report an error
“Metronome, as a usage-based platform, generally aligns with point in time recognition as usage occurs. However, it also supports subscriptions and seats which are typically recognized over time.”
-
Salesforce contract export Report an error
“You can also use the Metronome to Salesforce integration to automatically export metronome__Contract__c and metronome__Commit__c data objects into Salesforce which contain contract ID, customer, rate card, name, start/end dates, and usage statement schedule frequency, as well as commit details like type, priority, total amount, and current balance.”
-
Salesforce invoice line item Report an error
“The metronome__Invoice_Line_Item__c data object contains Quantity__c, Unit_Price__c, Product_Type__c, and Total__c”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Billing Engineer Plans, pricing models & subscription lifecycle
- The Billing Engineer Revenue reporting & accounting handoff
- The Finance Lead Plans, pricing models & subscription lifecycle
- The Finance Lead Revenue reporting & accounting handoff
- The SaaS Founder Plans, pricing models & subscription lifecycle
- The SaaS Founder Invoices & e-invoicing compliance
- The SaaS Founder Revenue reporting & accounting handoff
- The Service-Business Owner Plans, pricing models & subscription lifecycle
- The Service-Business Owner Revenue reporting & accounting handoff
- The Skeptic Plans, pricing models & subscription lifecycle
- The Skeptic Revenue reporting & accounting handoff
- The Tax Adviser Plans, pricing models & subscription lifecycle
- The Tax Adviser Revenue reporting & accounting handoff