App Management — RevRec

Configure Recurly RevRec to handle App Store and Google Play Store subscription data through contract grouping, an exclusive POB, data rules, and the App Management integration.

Recurly RevRec can handle subscription data from both the Apple App Store and the Google Play Store. A few straightforward configurations — contract grouping, an exclusive performance obligation, a set of data rules, and the App Management integration job — get your app store data flowing in and recognizing revenue correctly. This page walks through each one in order.
Part of Recurly RevRec — learn more

Definition

Recurly RevRec can handle subscription data from both the Apple App Store and the Google Play Store. To manage app store data, you set up a handful of straightforward configurations in Recurly RevRec that group the data, assign a performance obligation, transform it with data rules, and pull it in through an integration job.

Key benefits

Streamlined data management Group app store data by subscription source for accurate, efficient handling.
Flexible revenue recognition Define an exclusive POB for app store data, recognizing revenue on an over-time basis.
Enhanced data rules Copy Google fees to the App Fees attribute and assign distinct account numbers for Apple and Google Store data.
Seamless integration Flow app store data into Recurly RevRec with the App Management integration.

Grouping configuration

Configure your system to group order lines based on the subscription's source — Apple App Store or Google Play Store.

App store data is organized by subscription, so you'll create two separate grouping rules using the contract grouping feature:

  • Apple Store grouping rule: set the grouping attribute to Source = Apple Store.
  • Play Store grouping rule: set the grouping attribute to Source = Play Store.

This setup ensures order lines are accurately grouped by subscription source.

Performance obligation

Define an exclusive Performance Obligation (POB) for app store data, where revenue is recognized over time.

This POB — called App Subscription — is automatically assigned to any order line in a contract that meets the Recurly RevRec rules for either Play Store or Apple Store data.

The POB rules are based on the source of the data, ensuring that all order lines with the specified source are grouped under the App Subscription POB.

ImportantThe hierarchy of these rules is critical to guaranteeing the correct obligation is applied.

Data rule configuration

To ensure accurate revenue recognition, configure data rules that transform your app store data correctly. You'll copy the sell price from Google Fees lines into the App Fees attribute and assign the proper account numbers for Play Store and Apple Store data. There are four data rules.

Data rule 1 — Copy Google fees to App Fees

Copies the sell price from Google Fees lines into the App Fees attribute.

Rule

Application attributeFormula
App FeesLine.SellPrice

Criteria

FieldOperatorValue
Plan=Google Fees

Data rule 2 — Zero out Google fees

Sets the sell price of the Google Fees plan to zero to avoid duplicative charges.

Rule

Application attributeFormula
App Fees0

Criteria

FieldOperatorValue
Plan=Google Fees

Data rule 3 — Assign account numbers for Play Store data

Applies the appropriate account number for all order lines with a source of Play Store.

Rule

Application attributeFormula
Liability Account23100
Revenue Account33200

Criteria

FieldOperatorValue
Source=Play Store

Data rule 4 — Assign account numbers for Apple Store data

Applies the appropriate account number for all order lines with a source of Apple Store.

Rule

Application attributeFormula
Liability Account23000
Revenue Account33000

Criteria

FieldOperatorValue
Source=Apple Store

App Management integration

Once your data rules are configured, run the App Management integration job. This integration pushes all processed app store data into Recurly RevRec.

1

Open the integration job

Go to Import/Export → Scheduled Jobs → App Management Integration.

2

Run the job

Ensure the job is active, then select Run to execute the integration.



Did this page help you?