TeleNav 2015 Annual Report Download - page 55

Download and view the complete annual report

Please find page 55 of the 2015 TeleNav annual report below. You can navigate through the pages in the report by either clicking on the pages listed below, or by using the keyword search tool below to find specific information within the annual report.

Page out of 170

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170

Table of Contents
We derive product revenue from the delivery of customized software and royalties earned from the distribution of this customized software
in certain automotive navigation applications. We generally recognize customized software revenue using the completed contract method of
contract accounting under which revenue is recognized upon delivery to, and acceptance by, the automobile manufacturer of our on-board
navigation solutions. We generally recognize royalty revenue as the software is reproduced for installation in vehicles, assuming all other
conditions for revenue recognition have been met. We recognize services revenue from our brought-in connected automotive navigation
solutions monthly based on monthly subscriptions, which are subject to a maximum annual fee. This revenue represented less than 5% of overall
automotive navigation solutions revenue. In January 2015, GM launched the new version of its OnStar RemoteLink® mobile application
powered by our location-based services platform. We earn a one-time royalty for each new vehicle owner who downloads the RemoteLink®
application. We record the royalty earned as deferred revenue and recognize this service revenue over the estimated service period.
We derive services revenue from the delivery of search and display advertising impressions. We recognize revenue when the related
advertising services are delivered based on the specific terms of the advertising contract, which are commonly based on the number of ad
impressions delivered, or clicks, drives or actions by users on mobile advertisements.
We also derive services revenue from subscriptions to access our mobile navigation services, which are generally provided through our
wireless carrier customers that offer our services to their subscribers or through application stores. Our wireless carrier customers pay us based
on several different revenue models, including (1) a revenue sharing arrangement that may include a minimum fee per end user, (2) a monthly or
annual subscription fee per end user, or (3) based on usage. Our end users who subscribe to our services through application stores pay us a
monthly or annual subscription fee.
We recognize monthly fees related to our mobile navigation services in the month we provide the services. We defer amounts received or
billed in advance of the service being provided and recognize the deferred amounts when the monthly service has been provided. We recognize
revenue for fixed fees for any number of subscribers receiving our services as part of bundles monthly on a straight-line basis over the term of
the agreement. Our agreements do not contain general rights of refund once the service has been provided. We also establish allowances for
estimated credits subsequently issued to end users by our wireless carrier customers.
We recognize as services revenue the amount our wireless carrier customers report to us as we provide our services, which are net of any
revenue sharing or other fees earned and deducted by our wireless carrier customers. We are not the principal provider when selling access to our
mobile navigation services through our wireless carrier customers as the subscribers directly contract with our wireless carrier customers. In
addition, we may earn a fixed fee or fixed percentage of fees charged by our wireless carrier customers and our wireless carrier customers have
the sole ability to set the price charged to their subscribers for our service. Our wireless carrier customers have direct responsibility for billing
and collecting those fees from their subscribers and we and our wireless carrier customers may offer subscribers a free trial for our service. For
end users who purchase our mobile navigation services through application stores, we utilize the application store billing process. We provide
tiered pricing to certain of our wireless carrier customers based on the number of paying end users in a given month, which may result in a
discounted fee per end user depending on the number of end users. Revenue recognized is based on the discounted fees earned for a given
period.
In certain instances, due to the nature and timing of monthly revenue and reporting from our customers, we may be required to make
estimates of the amount of revenue to recognize from a customer for the current period. For example, certain of our wireless carrier customers do
not provide us with sufficient monthly individual subscriber billing period details to allow us to compute the allocation of monthly service fees
to the individual end user’s service period, and in such cases we make estimates of any required service period revenue cutoff. In addition, if we
fail to receive an accurate revenue report from a wireless carrier customer for the month, we will need to estimate the amount of revenue that
should be recorded for that month. These estimates may require judgment, and we consider certain factors and information in making these
estimates such as:
If we are unable to reasonably estimate recognizable revenue from a customer for a given period, we defer recognition of revenue to the
period in which we receive and validate the customer’s revenue report and all of our revenue recognition criteria have been met. If we have
recorded an estimated revenue amount, we record any difference between the estimated revenue and actual revenue in the period when we
receive the final revenue reports from our customer, which typically occurs within the following month. To date, actual amounts have not
differed materially from our estimates.
44
subscriber data supplied by our wireless carrier customers;
customer specific historical subscription and revenue reporting trends;
end user subscription data from our internal systems; and
data from comparable distribution channels of our other customers.