XML 51 R11.htm IDEA: XBRL DOCUMENT v3.19.3
REVENUE RECOGNITION
9 Months Ended
Sep. 30, 2019
REVENUE RECOGNITION [Abstract]  
REVENUE RECOGNITION
NOTE 4.
REVENUE RECOGNITION:

Revenue Recognition. We recognize revenues as we transfer control of deliverables (products, solutions and services) to our customers in an amount reflecting the consideration to which we expect to be entitled. To recognize revenues, we apply the following five step approach: (1) identify the contract with a customer, (2) identify the performance obligations in the contract, (3) determine the transaction price, (4) allocate the transaction price to the performance obligations in the contract, and (5) recognize revenues when a performance obligation is satisfied. We account for a contract when it has approval and commitment from all parties, the rights of the parties are identified, payment terms are identified, the contract has commercial substance and collectability of consideration is probable. We apply judgment in determining the customer’s ability and intention to pay based on a variety of factors including the customer’s historical payment experience.

For performance obligations where control is transferred over time, revenues are recognized based on the extent of progress towards completion of the performance obligation. The selection of the method to measure progress towards completion requires judgment and is based on the nature of the deliverables to be provided.
 
Revenues related to fixed-price contracts for application development and systems integration services, consulting or other technology services are recognized as the service is performed using the cost to cost method, under which the total value of revenues is recognized on the basis of the percentage that each contract’s total labor cost to date bears to the total expected labor costs. Revenues related to fixed-price application maintenance, testing and business process services are recognized based on our right to invoice for services performed for contracts in which the invoicing is representative of the value being delivered. If our invoicing is not consistent with value delivered, revenues are recognized as the service is performed based on the cost to cost method described above. The cost to cost method requires estimation of future costs, which is updated as the project progresses to reflect the latest available information; such estimates and changes in estimates involve the use of judgment. The cumulative impact of any revision in estimates is reflected in the financial reporting period in which the change in estimate becomes known and any anticipated losses on contracts are recognized immediately.
 
Revenues related to our time-and-materials, transaction-based or volume-based contracts are recognized over the period the services are provided either using an output method such as labor hours, or a method that is otherwise consistent with the way in which value is delivered to the customer.

We assess the timing of the transfer of goods or services to the customer as compared to the timing of payments to determine whether a significant financing component exists. As a practical expedient, we do not assess the existence of a significant financing component when the difference between payment and transfer of deliverables is a year or less. If the difference in timing arises for reasons other than the provision of finance to either the customer or us, no financing component is deemed to exist. The primary purpose of our invoicing terms is to provide customers with simplified and predictable ways of purchasing our services, not to receive or provide financing from or to customers. We do not consider set up or transition fees paid upfront by our customers to represent a financing component, as such fees are required to encourage customer commitment to the project and protect us from early termination of the contract.

Trade Receivables, Contract Assets and Contract Liabilities. We classify our right to consideration in exchange for deliverables as either a receivable or a contract asset. A receivable is a right to consideration that is unconditional (i.e., only the passage of time is required before payment is due). For example, we recognize a receivable for revenues related to our time and materials and transaction or volume-based contracts when earned regardless of whether amounts have been billed. We present such receivables in “Trade accounts receivable, net” in our consolidated statements of financial position at their net estimated realizable value. A contract asset is a right to consideration that is conditional upon factors other than the passage of time. Contract assets are presented in “Other current assets” in our consolidated statements of financial position and primarily relate to unbilled amounts on fixed-price contracts utilizing the cost to cost method of revenue recognition. Our contract liabilities, or deferred revenue, consist of advance payments and billings in excess of revenues recognized. We classify deferred revenue as current or noncurrent based on the timing of when we expect to recognize the revenues. The noncurrent portion of deferred revenue is included in “Other noncurrent liabilities” in our consolidated statements of financial position.
 
Allowance for Doubtful Accounts. We maintain an allowance for doubtful accounts to provide for the estimated amount of receivables that may not be collected. The allowance is based upon an assessment of customer creditworthiness, historical payment experience, the age of outstanding receivables and other applicable factors. We evaluate the collectability of our trade accounts receivable on an on-going basis and write off accounts when they are deemed to be uncollectable.