XML 41 R12.htm IDEA: XBRL DOCUMENT
v3.20.2

Revenue Recognition | 6 Months Ended
--- | ---
Jun. 30, 2020
Revenue from Contract with Customer [Abstract] |
Revenue Recognition | NOTE 4. REVENUE RECOGNITION: In May 2014, the FASB issued ASU 2014-09, Revenue from Contracts with Customers (Topic 606). ASU 2014-09 supersedes the revenue recognition requirements under Topic 605, Revenue Recognition, and most industry-specific guidance throughout the Industry Topics of the ASC. 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 an entity expects to be entitled in exchange for those goods or services. The new guidance will significantly enhance comparability of revenue recognition practices across entities, industries, jurisdictions and capital markets. Additionally, the guidance requires improved disclosures as to the nature, amount, timing and uncertainty of revenue that is recognized. In May 2016, the FASB issued ASU No. 2016-12, Revenue from Contracts with Customers (Topic 606)—Narrow-Scope Improvements and Practical Expedients. This update clarifies the objectives of collectability, sales and other taxes, noncash consideration, contract modifications at transition, completed contracts at transition and technical correction. The amendments in this update affect the guidance in ASU 2014-09. In September 2017, the FASB issued additional amendments providing clarification and implementation guidance. The Company adopted ASC 606 effective January 1, 2018 using the modified retrospective method which would require a cumulative effect adjustment for initially applying the new revenue standard as an adjustment to the opening balance of retained earnings and the comparative information would not require to be restated and continue to be reported under the accounting standards in effect for those periods. The adoption of ASC 606 represents a change in accounting principle that will more closely align revenue recognition with the delivery of the Company’s services and will provide financial statement readers with enhanced disclosures. 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 achieve this core principle, the Company applies the following five steps:
1) | Identify the contract with a customer
A contract with a customer exists when (i) the Company enters into an enforceable contract with a customer that defines each party’s rights regarding the services to be transferred and identifies the payment terms related to these services, (ii) the contract has commercial substance and, (iii) the Company determines that collection of substantially all consideration for services that are transferred is probable based on the customer’s intent and ability to pay the promised consideration. The Company applies judgment in determining the customer’s ability and intention to pay, which is based on a variety of factors including the customer’s historical payment experience or, in the case of a new customer, published credit and financial information pertaining to the customer.
2) | Identify the performance obligations in the contract
Performance obligations promised in a contract are identified based on the services that will be transferred to the customer that are both capable of being distinct, whereby the customer can benefit from the service either on its own or together with other resources that are readily available from third parties or from the Company, and are distinct in the context of the contract, whereby the transfer of the services is separately identifiable from other promises in the contract. To the extent a contract includes multiple promised services, the Company must apply judgment to determine whether promised services are capable of being distinct and distinct in the context of the contract. If these criteria are not met the promised services are accounted for as a combined performance obligation.
3) | Determine the transaction price
The transaction price is determined based on the consideration to which the Company will be entitled in exchange for transferring services to the customer. To the extent the transaction price includes variable consideration, the Company estimates the amount of variable consideration that should be included in the transaction price utilizing either the expected value method or the most likely amount method depending on the nature of the variable consideration. Variable consideration is included in the transaction price if, in the Company’s judgment, it is probable that a significant future reversal of cumulative revenue under the contract will not occur. None of the Company’s contracts as of December 31, 2019 contained a significant financing component.
4) | Allocate the transaction price to performance obligations in the contract
If the contract contains a single performance obligation, the entire transaction price is allocated to the single performance obligation. However, if a series of distinct services that are substantially the same qualifies as a single performance obligation in a contract with variable consideration, the Company must determine if the variable consideration is attributable to the entire contract or to a specific part of the contract. For example, a bonus or penalty may be associated with one or more, but not all, distinct services promised in a series of distinct services that forms part of a single performance obligation. Contracts that contain multiple performance obligations require an allocation of the transaction price to each performance obligation based on a relative standalone selling price basis unless the transaction price is variable and meets the criteria to be allocated entirely to a performance obligation or to a distinct service that forms part of a single performance obligation. The Company determines standalone selling price based on the price at which the performance obligation is sold separately. If the standalone selling price is not observable through past transactions, the Company estimates the standalone selling price taking into account available information such as market conditions and internally approved pricing guidelines related to the performance obligations.
5) | Recognize revenue when or as the Company satisfies a performance obligation
The Company satisfies performance obligations either over time or at a point in time. Revenue is recognized at the time the related performance obligation is satisfied by transferring a promised service to a customer. Disaggregation of Revenue from Entities. The following table disaggregates gross revenue by entity for the six months ended June 30, 2020 and 2019:
|  | For the Six Months Ended |
|  | June 30, 2020 |  |  | June 30, 2019 |
ATGC India |  | $ | 114,184 |  |  | $ | 177,105 |
Ameri 100 California |  |  | 6,733,692 |  |  |  | 5,684,839 |
Ameri 100 Arizona |  |  | 1,843,565 |  |  |  | 4,852,187 |
Ameri 100 Canada |  |  | 214,578 |  |  |  | 346,349 |
Ameri 100 Georgia |  |  | 3,168,466 |  |  |  | 6,610,680 |
Bigtech Software |  |  | 39,170 |  |  |  | 177,542 |
Ameri 100 Consulting Pvt Ltd |  |  | 179,406 |  |  |  | 56,392 |
Ameri Partners |  |  | 5,564,408 |  |  |  | 3,796,159 |
Total revenue |  | $ | 17,857,469 |  |  | $ | 21,701,253 |
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. Revenues also include the reimbursement of out-of-pocket expenses. We may enter into arrangements that consist of multiple performance obligations. Such arrangements may include any combination of our deliverables. To the extent a contract includes multiple promised deliverables, we apply judgment to determine whether promised deliverables are capable of being distinct and are distinct in the context of the contract. If these criteria are not met, the promised deliverables are accounted for as a combined performance obligation. For arrangements with multiple distinct performance obligations, we allocate consideration among the performance obligations based on their relative standalone selling price. Standalone selling price is the price at which we would sell a promised good or service separately to the customer. When not directly observable, we typically estimate standalone selling price by using the expected cost plus a margin approach. We typically establish a standalone selling price range for our deliverables, which is reassessed on a periodic basis or when facts and circumstances change. 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. Prior to the adoption of the New Revenue Standard on January 1, 2018, revenues were earned and recognized when all of the following criteria were met: evidence of an arrangement existed, the price was fixed or determinable, the services had been rendered and collectability was reasonably assured. Contingent or incentive revenues were recognized when the contingency was satisfied and we concluded the amounts were earned. Volume discounts were recorded as a reduction of revenues as services were provided. Revenues also included the reimbursement of out-of-pocket expenses. For the six months ended June 30, 2020 and June 30, 2019, sales to five major customers accounted for approximately 48% and 46% of our total revenue, respectively. For the six months ended June 30, 2020, five of our customers contributed 19%, 10% ,7% and 6% of our revenue, and for the six months ended June 30, 2019, five of our customers contributed 14%,11%,9% and 6% of our revenue.

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

X
- Definition The entire disclosure of revenue from contract with customer to transfer good or service and to transfer nonfinancial asset. Includes, but is not limited to, disaggregation of revenue, credit loss recognized from contract with customer, judgment and change in judgment related to contract with customer, and asset recognized from cost incurred to obtain or fulfill contract with customer. Excludes insurance and lease contracts. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -URI http://asc.fasb.org/topic&trid=49130388 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 10 -URI http://asc.fasb.org/extlink&oid=121604090&loc=SL49130551-203045 Reference 3: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 13 -Subparagraph (b)(2) -URI http://asc.fasb.org/extlink&oid=121604090&loc=SL49130556-203045 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 12 -Subparagraph (b) -URI http://asc.fasb.org/extlink&oid=121604090&loc=SL49130554-203045 Reference 5: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 9 -URI http://asc.fasb.org/extlink&oid=121604090&loc=SL49130550-203045 Reference 6: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 12 -Subparagraph (e) -URI http://asc.fasb.org/extlink&oid=121604090&loc=SL49130554-203045 Reference 7: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 12 -Subparagraph (a) -URI http://asc.fasb.org/extlink&oid=121604090&loc=SL49130554-203045 Reference 8: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 12 -Subparagraph (d) -URI http://asc.fasb.org/extlink&oid=121604090&loc=SL49130554-203045 Reference 9: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 15 -URI http://asc.fasb.org/extlink&oid=121604090&loc=SL49130558-203045 Reference 10: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -SubTopic 10 -Section 50 -Paragraph 12 -Subparagraph (c) -URI http://asc.fasb.org/extlink&oid=121604090&loc=SL49130554-203045 + Details
Name: | us-gaap_RevenueFromContractWithCustomerTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration