XML 35 R25.htm IDEA: XBRL DOCUMENT
v3.5.0.2

Significant Accounting Policies (Policies) | 6 Months Ended
--- | ---
Jun. 30, 2016
Accounting Policies [Abstract] |
New Accounting Pronouncements, Policy [Policy Text Block] | Accounting Standards Update (“ ASU”) 2016-13 , "Financial Instruments - Credit Losses: Measurement of Credit Losses on Financial Instruments.” Issued in June 2016, ASU 2016-13 removes the thresholds that companies apply to measure credit losses on financial instruments measured at amortized cost, such as loans, receivables, and held-to-maturity debt securities. Under current U.S. GAAP, companies generally recognize credit losses when it is probable that the loss has been incurred. The revised guidance will remove all current recognition thresholds and will require companies to recognize an allowance for lifetime expected credit losses. Credit losses will be immediately recognized through net income; the amount recognized will be based on the current estimate of contractual cash flows not expected to be collected over the financial asset’s contractual term. ASU 2016-13 also amends the credit loss measurement guidance for available-for-sale debt securities. For public business entities, ASU 2016-13 is effective for financial statements issued for fiscal years and for interim periods within those fiscal years beginning after December 15, 2019. Institutions will be required to apply the changes through a cumulative-effect adjustment to their retained earnings as of the beginning of the first reporting period in which the guidance is effective. Management is currently evaluating the impact that this ASU will have on the Company’s consolidated financial statements. ASU 2016-10, “ Revenue from Contracts with Customers (Topic 606)-Identifying Performance Obligations and Licensing.” Issued in April 2016, ASU 2016-10 clarifies ASC Topic 606, “Revenue from Contracts with Customers" with respect to (i) identifying performance obligations; and (ii) the licensing implementation guidance. Since the amendments in ASU 2016-10 affect the guidance in ASU 2014-09, “Revenue from Contracts with Customers (Topic 606),” which is not yet effective, this ASU will become effective when ASU 2014-09 becomes effective. The amendments of ASU 2016-10 are effective for interim and annual periods beginning after December 15, 2017. Earlier application is permitted only as of annual reporting periods beginning after December 15, 2016, including interim reporting periods within that reporting period. Management is currently evaluating the impact that this ASU will have on the Company’s consolidated financial statements. ASU 2016-09, “ Compensation-Stock Compensation (Topic 718)-Improvements to Employee Share-Based Payment Accounting.” Issued in March 2016, ASU 2016-09 seeks to reduce complexity in accounting standards by simplifying several aspects of the accounting for share-based payment transactions, including (1) accounting for income taxes; (2) classification of excess tax benefits on the statement of cash flows; (3) forfeitures; (4) minimum statutory tax withholding requirements; (5) classification of employee taxes paid on the statement of cash flows when an employer withholds shares for tax withholding purposes; (6) the practical expedient for estimating the expected term; and (7) intrinsic value. The amendments of ASU 2016-09 are effective for interim and annual periods beginning after December 15, 2016. Management is currently evaluating the impact that this ASU will have on the Company’s consolidated financial statements. ASU 2016-08, “Revenue from Contracts with Customers (Topic 606): Principal versus Agent Considerations (Reporting Revenue Gross versus Net).” Issued in March 2016, ASU 2016-08 clarifies certain principal versus agent considerations within the implementation guidance of ASC Topic 606, “Revenue from Contracts with Customers.” Since the amendments in ASU 2016-08 affect the guidance in ASU 2014-09, “Revenue from Contracts with Customers (Topic 606),” which is not yet effective, this ASU will become effective when ASU 2014-09 becomes effective. The amendments of ASU 2016-08 are effective for interim and annual periods beginning after December 15, 2017. Earlier application is permitted only as of annual reporting periods beginning after December 15, 2016, including interim reporting periods within that reporting period. Management is currently evaluating the impact that this ASU will have on the Company’s consolidated financial statements. ASU 2016-05 , “Derivatives and Hedging (Topic 815): Effect of Derivative Contract Novations on Existing Hedge Accounting Relationships.” Issued in March 2016, ASU 2016-05 clarifies that a change in the counterparty to a derivative instrument that has been designated as a hedging instrument under ASC Topic 815 does not, in and of itself, require de-designation of that hedging relationship, provided that all other hedge accounting criteria continue to be met. The amendments of ASU 2016-05 are effective for interim and annual periods beginning after December 15, 2016. Management is currently evaluating the impact that this ASU will have on the Company’s consolidated financial statements. ASU 2016-02, “Leases (Topic 842).” Issued in February 2016, ASU 2016-02 will require organizations that lease assets (lessees) to recognize on the balance sheet the assets and liabilities for the rights and obligations created by the lease for all leases with a term of more than 12 months. The recognition, measurement and presentation of expenses and cash flows arising from a lease are not significantly changed under ASU 2016-02. There will continue to be differentiation between finance leases and operating leases. For finance leases, a lessee will be required to (i) recognize a right-of-use asset and a lease liability, initially measured at the present value of the lease payments, in the statement of financial position; (ii) recognize interest on the lease liability separately from amortization of the right-of-use asset in the statement of income; and (iii) classify repayments of the principal portion of the lease liability within financing activities and payments of interest on the lease liability within operating activities on the statement of cash flows. For operating leases, a lessee will be required to (i) recognize a right-of-use asset and a lease liability, initially measured at the present value of the lease payments, in the statement of financial position; (ii) recognize a single lease cost, calculated so that the cost of the lease is allocated over the lease term on a generally straight-line basis; and (iii) classify all cash payments within operating activities in the statement of cash flows. The accounting applied by the lessor in a lease transaction remains largely unchanged from previous U.S. GAAP. ASU 2016-02 is effective for fiscal years beginning after December 15, 2018. Management is currently evaluating the impact that this ASU will have on the Company’s consolidated financial statements. ASU 2016-01, “ Financial Instruments-Overall (Subtopic 825-10): Recognition and Measurement of Financial Assets and Financial Liabilities (An Amendment of the Financial Accounting Standards Board (“FASB”) Accounting Standards Codification).” Issued in January 2016, ASU 2016-01 is intended to enhance the reporting model for financial instruments to provide users of financial statements with improved decision-making information. The amendments to ASU 2016-01 include: (i) requiring equity investments, except those accounted for under the equity method of accounting or those that result in the consolidation of an investee, to be measured at fair value, with changes in fair value recognized in net income; (ii) requiring a qualitative assessment to identify impairment of equity investments without readily determinable fair values; and (iii) clarifying that an entity should evaluate the need for a valuation allowance on a deferred tax asset related to available-for-sale securities in combination with the entity’s other deferred tax assets. The amendments of ASU 2016-01 are effective for interim and annual periods beginning after December 15, 2017. Management is currently evaluating the impact that this ASU will have on the Company’s consolidated financial statements. ASU 2015-05, “ Customer’s Accounting for Fees Paid in a Cloud Computing Arrangement.” Issued in April 2015, ASU 2015-05 provides guidance on how customers should evaluate whether cloud computing arrangements contain a software license that should be accounted for separately. A customer that determines that such an arrangement contains a software license must account for the license consistently with the acquisition of other software licenses. If an arrangement does not contain a software license, then the customer is required to account for it as a service contract. As a result, all software licenses within the scope of this guidance will be accounted for consistently with other licenses of intangible assets. The guidance is effective for annual and interim periods beginning after December 15, 2015. Entities can elect to apply the guidance either retrospectively or prospectively to all cloud computing arrangements entered into or materially modified after the effective date. ASU 2015-05 became effective for the Company on January 1, 2016 and was applied using the prospective transition method. The adoption of ASU 2015-05 did not have a material impact on the Company’s consolidated financial statements. ASU 2015-02, “ Consolidation (Topic 810): Amendments to the Consolidation Analysis .” Issued in February 2015, ASU 2015-02 is intended to improve targeted areas of consolidation guidance for legal entities such as limited partnerships, limited liability companies and certain entities involved in securitization transactions. ASU 2015-02 focuses on the consolidation criteria for reporting organizations that are required to evaluate whether they should consolidate certain legal entities. The new standard simplifies and improves current U.S. GAAP by: (i) placing more emphasis on risk of loss when determining a controlling financial interest; (ii) reducing the frequency of the application of related-party guidance when determining a controlling financial interest in a VIE; and (iii) changing consolidation conclusions for companies in several industries that typically make use of limited partnerships or VIEs. ASU 2015-02 became effective for the Company on January 1, 2016. The adoption of ASU 2015-02 did not have a material impact on the Company’s consolidated financial statements. ASU 2014-09, “Revenue from Contracts with Customers (Topic 606).” Issued in May 2014, ASU 2014-09 will add FASB ASC Topic 606, Revenue from Contracts with Customers, and will supersede revenue recognition requirements in FASB ASC Topic 605, Revenue Recognition and certain cost guidance in FASB ASC Topic 605-35, Revenue Recognition – Construction-Type and Production-Type Contracts. ASU 2014-09 provides a framework for revenue recognition that replaces the existing industry and transaction-specific requirements under the existing standards. ASU 2014-09 requires an entity to apply a five-step model to determine when to recognize revenue and at what amount. The model specifies that revenue should be recognized when (or as) an entity transfers control of goods or services to a customer at the amount to which the entity expects to be entitled. Depending on whether certain criteria are met, revenue should be recognized either over time, in a manner that depicts the entity’s performance, or at a point in time, when control of the goods or services is transferred to the customer. ASU 2014-09 provides that an entity should apply the following steps: (1) identify the contract(s) with a customer; (2) identify the performance obligations in each contract; (3) determine the transaction price; (4) allocate the transaction price to the performance obligations in each contract; and (5) recognize revenue when, or as, the entity satisfies a performance obligation. In addition, the existing requirements for the recognition of a gain or loss on the transfer of non-financial assets that are not in a contract with a customer are amended to be consistent with the guidance on recognition and measurement in ASU 2014-09. The amendments of ASU 2014-09 may be applied either retrospectively to each prior reporting period presented or retrospectively with the cumulative effect of initially applying ASU 2014-09 recognized at the date of initial application. If the transition method of application is elected, the entity should also provide the additional disclosures in reporting periods that include the date of initial application regarding (1) the amount by which each financial statement line item is affected in the current reporting period and (2) an explanation of the reasons for significant changes. ASU 2015-14, “Revenue from Contracts with Customers (Topic 606)-Deferral of the Effective Date,” issued in August 2015, defers the effective date of ASU 2014-09 by one year. ASU 2015-14 provides that the amendments of ASU 2014-09 become effective for interim and annual periods beginning after December 15, 2017. Earlier application is permitted only as of annual reporting periods beginning after December 15, 2016, including interim reporting periods within that reporting period. Management is currently evaluating the impact that this ASU will have on the Company’s consolidated financial statements, as well as the most appropriate method of application; however, regardless of the method of application selected, the adoption of ASU 2014-09 is not expected to have a material impact on the Company’s consolidated financial statements.

X
- References No definition available. + Details
Name: | us-gaap_AccountingPoliciesAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy pertaining to new accounting pronouncements that may impact the entity's financial reporting. Includes, but is not limited to, quantification of the expected or actual impact. + References No definition available. + Details
Name: | us-gaap_NewAccountingPronouncementsPolicyPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration