2.2.0.7 false Revenue Recognition 006030 - Disclosure - Revenue Recognition true false false false 1 USD false false u000 Standard http://www.xbrl.org/2003/iso4217 USD iso4217 0 u002 Divide http://www.xbrl.org/2003/iso4217 USD iso4217 http://www.xbrl.org/2003/instance shares xbrli 0 u001 Standard http://www.xbrl.org/2003/instance shares xbrli 0 $ 2 Notes to the Financial Statements [Abstract] 0 epay_NotesToFinancialStatementsAbstract epay false na duration No definition available. false false false false false true false false false false false false 1 false false false false 0 0 false false false xbrli:stringItemType string No definition available. false 3 Revenue Recognition 1 us-gaap_RevenueRecognitionPolicyTextBlock us-gaap true na duration No definition available. false false false false false false false false false false false label false 1 false false false false 0 0 <div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">Note 3—Revenue Recognition</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: Times New Roman">Software Arrangements</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 36pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">The Company recognizes revenue on its software license arrangements when four basic criteria are met: persuasive evidence of an arrangement exists, delivery of the product has occurred, the fee is fixed and determinable and collectability is deemed probable. The Company considers a fully executed, non-cancelable agreement or a customer purchase order to be persuasive evidence of an arrangement. Delivery is deemed to have occurred upon transfer of the product title to the customer or the completion of services rendered. The Company considers the arrangement fee to be fixed and determinable if it is not subject to adjustment and if the customer has not been granted extended payment terms. Excluding our long term contract arrangements for which revenue is recorded on a percentage of completion basis, extended payment terms are deemed to be present when any portion of the software license fee is due in excess of 90 days after the date of product delivery. In arrangements that contain extended payment terms, software revenue is recorded as customer payments become contractually due, assuming all other revenue recognition criteria have been met. The Company considers the arrangement fee to be probable of collection if its internal credit analysis indicates that the customer will be able to pay contractual amounts as they become due.</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 36pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">The Company’s software arrangements may contain multiple revenue elements, such as software licenses, professional services, hardware and post-contract customer support. For multiple element software arrangements which qualify for separate element treatment, revenue is recognized for each element when each of the four basic criteria is met; excluding post-contract customer support, this is typically upon delivery or completion of professional services. Revenue for post-contract customer support agreements is recognized ratably over the term of the agreement, which is generally one year. Revenue is allocated to each element, excluding the software license, based on vendor specific objective evidence of fair value (“VSOE”). VSOE is limited to the price charged when the element is sold separately or, for an element not yet being sold separately, the price established by management having the relevant authority. The Company does not have VSOE for its software licenses since they are seldom sold separately. Accordingly, revenue is allocated to the software license according to the residual value method. Under the residual value method, revenue equal to VSOE of each undelivered element is deferred and recognized upon delivery of that element. Any “residual” arrangement fee is allocated to the software license. This has the effect of allocating any sales discount inherent in the arrangement to the software license fee.</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 36pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">Certain of the Company’s software license arrangements require significant customization and modification and involve extended implementation periods and as such do not qualify for separate element treatment. These arrangements are typically accounted for using percentage of completion contract accounting. In such arrangements, since the Company is able to make reasonably reliable estimates of progress toward completion, revenue is recognized over the life of the project as work is performed. Revenue earned in each reporting period is determined based on the percentage of labor hours incurred on the project as a percentage of total estimated labor hours. Customer payment milestones for both software and professional services fees on these long-term arrangements typically occur on a periodic basis over the period of project completion.</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: Times New Roman">Non-Software Arrangements</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 36pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">For arrangements governed by general revenue recognition literature, such as with the Company’s hosted or SaaS offerings or equipment and supplies only sales, the Company recognizes revenue when four basic criteria are met; these criteria are similar to those governing software transactions: persuasive evidence of an arrangement exists, delivery has occurred or services have been rendered, the arrangement fee is fixed or determinable and collectability is reasonably assured.</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 36pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">For arrangements consisting of multiple elements, revenue is allocated to each element based on a selling price hierarchy. The selling price of each element is based on VSOE if available, third party evidence (“TPE”) if VSOE is not available or estimated selling price (“ESP”) if neither VSOE or TPE are available. TPE is determined based on selling prices charged by unrelated third party vendors for similar deliverables when sold separately. The residual method of allocation is no longer permitted and, instead, arrangement consideration is allocated at the inception of the arrangement to all deliverables using the relative selling price method.  The relative selling price method allocates any discount in the arrangement proportionately to each deliverable based on the relative proportion of each deliverable’s selling price to the total arrangement fee.  The Company is typically unable to establish TPE as it is unable to obtain sufficient information on vendor selling prices to substantiate TPE. The objective of ESP is to estimate the price at which the Company would transact if the deliverable were sold separately rather than as part of a multiple element arrangement. The Company’s determination of ESP considers several factors including actual selling prices for similar transactions, gross margin expectations and ongoing pricing strategy. The Company plans to formally analyze its ESP determinations on at least an annual basis.</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 36pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">Whether a deliverable represents a separate unit of accounting, thus resulting in discrete revenue recognition as the revenue recognition criteria for that deliverable are met, is dependent on whether the deliverable has value to the customer on a standalone basis. A deliverable is deemed to have standalone value if it is sold separately by the Company or any other vendor or if the deliverable could be resold by the customer. Additionally, in an arrangement that includes a general right of return related to delivered items, delivery or performance of any undelivered items must be considered probable and substantially within the control of the Company.</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 36pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">Up-front fees paid by the customer, even if non-refundable, that do not have stand alone value are deferred and recognized as revenue over the period of performance. The Company periodically charges up-front fees, generally related to installation and integration services, in connection with certain of its hosted or SaaS offerings. These fees are deferred and recognized as revenue ratably over the estimated customer relationship period, which is generally five years, and the revenue recognition period associated with these fees normally commences upon customer implementation.</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 36pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">The Company expenses contract origination costs and incremental direct costs as incurred.</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: Times New Roman">Arrangements Including Both Software and Non-Software Deliverables</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 36pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">Periodically, the Company will enter into an arrangement that contains both software and non-software deliverables. In such a transaction, the aggregate arrangement consideration is allocated to the software deliverables and non-software deliverables as a group, using the relative selling prices of each of the deliverables based on the aforementioned selling price hierarchy. After this allocation is completed, the arrangement consideration allocated to the software deliverables is further allocated using the residual value method described above.</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 36pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">Regardless of the allocation methodology or the nature of the deliverables, the Company limits the amount of revenue that can be recognized for delivered items to the amount that is not contingent on future deliverables or subject to customer specified return or refund rights.</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div><table style="FONT-SIZE: 10pt; FONT-FAMILY: times new roman" cellspacing="0" cellpadding="0" width="100%" align="center" border="0"><tr valign="top"><td style="WIDTH: 12.2pt"><div><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">  </font></div></td><td><div align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: Times New Roman">Customer Returns</font></div></td></tr></table></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 45pt; MARGIN-RIGHT: 0pt" align="left"><font style="DISPLAY: inline; FONT-SIZE: 10pt; FONT-FAMILY: Times New Roman">The sales value of customer returns are estimated and accrued for based upon return authorizations issued and past history. Actual returns, in the aggregate, have been consistent with management’s expectations and have historically not been significant.</font></div><div style="DISPLAY: block; MARGIN-LEFT: 0pt; TEXT-INDENT: 0pt; MARGIN-RIGHT: 0pt" align="justify"> </div> Note 3—Revenue Recognition Software Arrangements The Company recognizes revenue on its software license arrangements when four basic criteria false false false us-types:textBlockItemType textblock Describes an entity's accounting policy for revenue recognition. If the entity has different policies for different types of revenue transactions, the policy for each material type of transaction should be disclosed. If a sales transaction has multiple element arrangements (for example, delivery of multiple products, services or the rights to use assets) the disclosure may indicate the accounting policy for each unit of accounting as well as how units of accounting are determined and valued. The disclosure may encompass important judgment as to appropriateness of principles related to recognition of revenue. The disclosure also may indicate the entity's treatment of any unearned or deferred revenue that arises from the transaction. Reference 1: http://www.xbrl.org/2003/role/presentationRef -Publisher SEC -Name Staff Accounting Bulletin (SAB) -Number Topic 13 -Section B -Paragraph Question 1 Reference 2: http://www.xbrl.org/2003/role/presentationRef -Publisher AICPA -Name Accounting Principles Board Opinion (APB) -Number 22 -Paragraph 8, 12, 13 false 1 2 false UnKnown UnKnown UnKnown false true