Revenue Recognition	3 Months Ended
Mar. 31, 2018
Notes
Revenue Recognition	5. Revenue Recognition We generate our revenues from (i) fees charged in connection with the installation and set-up of our software platform; (ii) ongoing monthly processing fees and (ii) technology fees. Our revenue recognition policy follows the guidance from Accounting Standards Codification (“ASC”) 605, “Revenue Recognition,” and Accounting Standards Update (“ASU”) 2009-13, “Multiple-Deliverable Revenue Arrangements,” which provides guidance on the recognition, presentation, and disclosure of revenue in financial statements. We recognize revenues when all of the following criteria are satisfied: (i) persuasive evidence of an arrangement exists; (ii) the price is fixed or determinable; (iii) collectability is reasonably assured; and (iv) the service has been performed or the product has been delivered. Collectability is assessed based on a number of factors, including the creditworthiness of a client, the size and nature of a client’s website and transaction history. Amounts billed or collected in excess of revenue recognized are included as deferred revenue. An example of this deferred revenue would be arrangements where clients request or are required by us to pay in advance of delivery. In April 2016, the FASB issued “ASU 2016 - 10 Revenue from Contract with Customers (Topic 606): identifying Performance Obligations and Licensing.” The amendments in this Update do not change the core principle of the guidance in Topic 606. Rather, the amendments in this Update clarify the following two aspects of Topic 606: identifying performance obligations and the licensing implementation guidance, while retaining the related principles for those areas. Topic 606 includes implementation guidance on (a) contracts with customers to transfer goods and services in exchange for consideration and (b) determining whether an entity’s promise to grant a license provides a customer with either a right to use the entity’s intellectual property (which is satisfied at a point in time) or a right to access the entity’s intellectual property (which is satisfied over time). The amendments in this Update are intended to render more detailed implementation guidance with the expectation to reduce the degree of judgement necessary to comply with Topic 606. The amendments in this Update affect the guidance in ASU 2014-09, Revenue from Contracts with Customers (Topic 606), which is not yet effective. The effective date and transition requirements for the amendments in this Update are the same as the effective date and transition requirements in Topic 606 (and any other Topic amended by Update 2014-09). ASU 2015-14, Revenue from Contracts with Customers (Topic 606): Deferral of the Effective Date, defers the effective date of Update 2014-09 by one year. We are currently evaluating the impact that this updated guidance will have on our results of operations, cash flows or financial condition. In November 2016, the FASB issued ASU 2016-20, an amendment to ASU 2014-09, Revenue from Contracts with Customers (Topic 606). This ASU addressed several areas related to contracts with customers. This topic is not yet effective and will become effective with Topic 606. We are currently evaluating the impact this topic will have on our financial statements.

Revenue Recognition

3 Months Ended

Mar. 31, 2018

5. Revenue Recognition

We generate our revenues from (i) fees charged in connection with the installation and set-up of our software platform; (ii) ongoing monthly processing fees and (ii) technology fees.

Our revenue recognition policy follows the guidance from Accounting Standards Codification (“ASC”) 605, “Revenue Recognition,” and Accounting Standards Update (“ASU”) 2009-13, “Multiple-Deliverable Revenue Arrangements,” which provides guidance on the recognition, presentation, and disclosure of revenue in financial statements. We recognize revenues when all of the following criteria are satisfied: (i) persuasive evidence of an arrangement exists; (ii) the price is fixed or determinable; (iii) collectability is reasonably assured; and (iv) the service has been performed or the product has been delivered. Collectability is assessed based on a number of factors, including the creditworthiness of a client, the size and nature of a client’s website and transaction history. Amounts billed or collected in excess of revenue recognized are included as deferred revenue. An example of this deferred revenue would be arrangements where clients request or are required by us to pay in advance of delivery.

In April 2016, the FASB issued “ASU 2016 - 10 Revenue from Contract with Customers (Topic 606): identifying Performance Obligations and Licensing.” The amendments in this Update do not change the core principle of the guidance in Topic 606. Rather, the amendments in this Update clarify the following two aspects of Topic 606: identifying performance obligations and the licensing implementation guidance, while retaining the related principles for those areas. Topic 606 includes implementation guidance on (a) contracts with customers to transfer goods and services in exchange for consideration and (b) determining whether an entity’s promise to grant a license provides a customer with either a right to use the entity’s intellectual property (which is satisfied at a point in time) or a right to access the entity’s intellectual property (which is satisfied over time). The amendments in this Update are intended to render more detailed implementation guidance with the expectation to reduce the degree of judgement necessary to comply with Topic 606. The amendments in this Update affect the guidance in ASU 2014-09, Revenue from Contracts with Customers (Topic 606), which is not yet effective. The effective date and transition requirements for the amendments in this Update are the same as the effective date and transition requirements in Topic 606 (and any other Topic amended by Update 2014-09). ASU 2015-14, Revenue from Contracts with Customers (Topic 606): Deferral of the Effective Date, defers the effective date of Update 2014-09 by one year. We are currently evaluating the impact that this updated guidance will have on our results of operations, cash flows or financial condition.

In November 2016, the FASB issued ASU 2016-20, an amendment to ASU 2014-09, Revenue from Contracts with Customers (Topic 606). This ASU addressed several areas related to contracts with customers. This topic is not yet effective and will become effective with Topic 606. We are currently evaluating the impact this topic will have on our financial statements.

SERIESONE, INC S-1/A