Revenue recognition schedules - export
Unlock revenue insights with the Revenue Recognition Schedules export feature.
Overview
Required plan
This feature is no longer available for activation.
Definition
Recurly’s Revenue Recognition Schedules export is your gateway to detailed revenue amortization data. This legacy solution, although no longer available for new purchases, continues to aid existing users in listing all schedules from each charge or credit alongside vital revenue amortization details. Visit our Legacy Solution page for more insight and consider exploring the new Recurly Revenue Recognition for a more robust experience.
Ensure to configure the Revenue Recognition feature properly to find this export in your admin console, exclusive to sites with this feature enabled.
Filters
Invoice Status Filter
All
- Overview: Accommodates every invoice generated on your Recurly site, regardless of the status.
Charge
- Overview: Encompasses charge invoices awaiting a payment attempt.-
Credit
- Overview: Denotes credit invoices.
e line items persist in the account history, with the owed balance cleared from the account.
Time Range Filter
Detail: Harness the invoice_created_at date column in the export to display all schedules stemming from invoices conceived within the chosen timeframe.
Exports table
To help you identify and organize information effectively, the export provides a structured table that contains the following columns:
| Id | Example | Description |
|---|---|---|
| revenue_schedule_id | 224934254870915 | The unique identifier of the revenue schedule. |
| invoice_number | 192880 | The invoice number visible in the Recurly UI. |
| invoice_date | 2017-06-01 00:00:00 UTC | The date when the invoice was created. |
| invoice_state | paid, processing, open, failed | The current state of the invoice. |
| account_code | 11734 | The account code being charged for this invoice. |
| accounting_code | monthly_fee | Internal accounting code for a specific invoice line item. This value will only populate if you define an accounting code for the line item. Accounting codes can be defined for all line items. |
| line_item_id | 3a6ae2555a2e2a76c077604bf5b90457 | Unique internal identifier for the adjustment. Also referred to as line_item_uuid or adjustment_uuid in other exports. |
| line_item_start_date | 2017-06-01 12:00:00 UTC | Bill cycle start date for a specific invoice line item. Equivalent to line_item_start_date in the deprecated Invoices export. |
| line_item_end_date | 2017-07-01 12:00:00 UTC | Bill cycle end date for a specific invoice line item. This date will not exist for custom charges (one-time). |
| origin | plan, add_on, credit, charge | The original source for a line item. A credit created from an original charge will have the value of the charge's origin. |
| days | 31 | The number of days between line_item_start_date and line_item_end_date. |
| amount_per_day | 4.88 | The total amount divided by the number of days. |
| total_amount | 1000 | The total amount of the charge to be recognized for this schedule, in other words, "subtotal after discounts". |
| currency | USD | The currency of the line item. |
| schedule_type | at_range_start, evenly | The method in which revenue is recognized for that schedule, as defined in the plan settings for revenue recognition. |
| revenue_recognition_date | 2017-06-05 00:00:00 UTC | The date revenue is recognized. Only populated if the schedule type is at_range_start or at_rate_end. |
| deferred_revenue_balance | evenly | Reflects the total remaining deferred revenue to be recognized as of the date the export is requested. |
| arrears | 0 | The portion of the line item that applies to the past, i.e., before the time range "start date". |
| month_1 | 20 | The total amount recognized in a specific month. Note that the first month will be the current month. |
| month_2 | 20 | The total amount recognized in a specific month. The second column will be the month after the current month. |
| month_3, etc. | 20 | The total amount recognized in a specific month. There will be a column for each month after the current month, creating 12 columns of months in total. |
| future_revenue | 90 | Revenue to be recognized in the future past 12 months from the current month. |
| invoice_origin | purchase, refund | The event that created the invoice. Invoices issued before the Credit Invoices feature was enabled on your site will have either purchase or refund as the value. Once Credit Invoices is enabled, new origins like renewal, immediate_change, and write_off will appear. |
Version 2 - 11/1/2018
- Modification to the arrear and deferred revenue calculations.
Updated 2 months ago