XML 20 R9.htm IDEA: XBRL DOCUMENT v3.3.1.900
RECENT ACCOUNTING PRONOUNCEMENTS
 3 Months Ended
Dec. 31, 2015
RECENT ACCOUNTING PRONOUNCEMENTS [Abstract]  
RECENT ACCOUNTING PRONOUNCEMENTS

NOTE B- RECENT ACCOUNTING PRONOUNCEMENTS

 

In May 2014, FASB issued ASU 2014-09 Revenue from Contracts with Customers (Topic 606). ASU 2014-09 affects any entity using U.S. GAAP that either enters into contracts with customers to transfer goods or services or enters into contracts for the transfer of nonfinancial assets unless those contracts are within the scope of other standards (e.g., insurance contracts or lease contracts). This ASU will supersede the revenue recognition requirements in Topic 605, Revenue Recognition, and most industry-specific guidance. This ASU also supersedes some cost guidance included in Subtopic 605-35, Revenue Recognition—Construction-Type and Production-Type Contracts. In addition, the existing requirements for the recognition of a gain or loss on the transfer of nonfinancial assets that are not in a contract with a customer (e.g., assets within the scope of Topic 360, Property, Plant, and Equipment, and intangible assets within the scope of Topic 350, Intangibles—Goodwill and Other) are amended to be consistent with the guidance on recognition and measurement (including the constraint on revenue) in this ASU.

 

The core principle of the guidance is that an entity should recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. To achieve that core principle, an entity should apply the following steps:

Step 1: Identify the contract(s) with a customer.

Step 2: Identify the performance obligations in the contract.

Step 3: Determine the transaction price.

Step 4: Allocate the transaction price to the performance obligations in the contract.

Step 5: Recognize revenue when (or as) the entity satisfies a performance obligation.

For a public business entity, the amendments in this ASU are effective for annual reporting periods beginning after December 15, 2017, including interim periods within that reporting period. Early application is not permitted. The FASB has proposed a one year delay in the effective date of this amendment. The Company is currently analyzing the impact of the guidance on its financial statements.

An entity should apply the amendments in this ASU using one of the following two methods:

Retrospectively to each prior reporting period presented and the entity may elect any of the following practical expedients:

• For completed contracts, an entity need not restate contracts that begin and end within the same annual reporting period.
• For completed contracts that have variable consideration, an entity may use the transaction price at the date the contract was completed rather than estimating variable consideration amounts in the comparative reporting periods.
• For all reporting periods presented before the date of initial application, an entity need not disclose the amount of the transaction price allocated to remaining performance obligations and an explanation of when the entity expects to recognize that amount as revenue.

Retrospectively with the cumulative effect of initially applying this ASU recognized at the date of initial application. If an entity elects this transition method it also should provide the additional disclosures in reporting periods that include the date of initial application of:

• The amount by which each financial statement line item is affected in the current reporting period by the application of this ASU as compared to the guidance that was in effect before the change.
• An explanation of the reasons for significant changes.