PTEC » Topics » Revenue Recognition.

This excerpt taken from the PTEC 10-K filed Dec 14, 2006.
Revenue Recognition.   The Company licenses software under non-cancelable license agreements and provides services including non-recurring engineering, maintenance (consisting of product support services and rights to unspecified upgrades on a “when-and-if available” basis), and training.

Revenues from software license agreements are recognized when persuasive evidence of an arrangement exists, delivery has occurred, the fee is fixed or determinable, and collection is probable. The Company uses the residual method to recognize revenue when an agreement includes one or more elements to be delivered at a future date and vendor specific objective evidence (“VSOE”) of fair value exists for each undelivered element. VSOE of fair value is generally the price charged when that element is sold separately or, for items not yet being sold, it is the price established by management that will not change before the introduction of the item into the marketplace. Under the residual method, the VSOE of fair value of the undelivered element(s) is deferred and the remaining portion of the arrangement fee is recognized as revenues. If VSOE of fair value of one or more undelivered elements does not exist, revenues are deferred and recognized when delivery of those elements occurs or when fair value can be established. Revenue from arrangements that include rights to unspecified future products is recognized ratably over the term of the respective agreement.

The Company recognizes revenue related to the delivered products or services only if the above revenue recognition criteria are met, any undelivered products or services are not essential to the functionality of the delivered products and services, and payment for the delivered products or services is not contingent upon delivery of the remaining products or services.

Royalty revenues from OEMs and ODMs are generally recognized in each period based on estimated consumption by the OEMs and ODMs of products containing the Company’s software, provided that all



other revenue recognition criteria have been met. The Company normally recognizes revenue for all consumption prior to the end of the accounting period. Since the Company generally receives quarterly royalty reports from OEMs and ODMs approximately 30 to 60 days following the end of a quarter, it has put processes in place to reasonably estimate the royalty revenues, including obtaining estimates of production from our OEM and ODM customers, utilizing historical experience, and other relevant current information. The Company had accrued royalty revenue balances of $0.7 million and $1.8 million from our OEM and ODM customers as of September 30, 2006 and September 30, 2005, respectively. To date the variances between estimated and actual revenues have been immaterial.

For volume purchase agreements (“VPAs”) the Company recognizes revenues for units estimated to be consumed by the end of the following accounting quarter, to the extent that the customer has been invoiced for such consumption prior to the end of the current quarter and provided all other revenue recognition criteria have been met. Estimates are recorded based upon customer forecasts. Amounts that have been invoiced under VPAs and relate to consumption beyond the following accounting quarter, which the Company has determined to be not fixed or determinable, are recorded as deferred revenues.

During fiscal year 2005 and fiscal year 2006, the Company had increasingly relied on the use of paid-up software license agreements with its customers in which they pay a fixed upfront fee for an unlimited number of units subject to certain Phoenix product or design restrictions (paid-up licenses). Revenues from such paid-up license arrangements are generally recognized upfront provided all other revenue recognition criteria have been met. Approximately 50% and 43% of total net revenues were recognized on this basis in the fiscal year 2006 and 2005, respectively. Effective September 2006, the Company has decided to eliminate the practice of entering into paid-up licenses.

Non-recurring engineering service revenues are recognized on a time and materials basis, on a completed contract basis, or when contractual milestones are met. Contractual milestones involve the use of estimates and approximate the percentage-of-completion method. Software maintenance revenues are recognized ratably over the maintenance period, which is typically one year. Training and other service revenues are recognized as the services are performed. Amounts billed in advance for licenses and services that are in excess of revenues recognized are recorded as deferred revenues.

Wikinvest © 2006, 2007, 2008, 2009, 2010, 2011, 2012. Use of this site is subject to express Terms of Service, Privacy Policy, and Disclaimer. By continuing past this page, you agree to abide by these terms. Any information provided by Wikinvest, including but not limited to company data, competitors, business analysis, market share, sales revenues and other operating metrics, earnings call analysis, conference call transcripts, industry information, or price targets should not be construed as research, trading tips or recommendations, or investment advice and is provided with no warrants as to its accuracy. Stock market data, including US and International equity symbols, stock quotes, share prices, earnings ratios, and other fundamental data is provided by data partners. Stock market quotes delayed at least 15 minutes for NASDAQ, 20 mins for NYSE and AMEX. Market data by Xignite. See data providers for more details. Company names, products, services and branding cited herein may be trademarks or registered trademarks of their respective owners. The use of trademarks or service marks of another is not a representation that the other is affiliated with, sponsors, is sponsored by, endorses, or is endorsed by Wikinvest.
Powered by MediaWiki