SIGNIFICANT ACCOUNTING POLICIES (Policies)

6 Months Ended

Dec. 31, 2018

Accounting Policies [Abstract]

Principles of Consolidation

The financial statements presented herein reflect the consolidated financial position of Park City Group, Inc. and our subsidiaries. All inter-company transactions and balances have been eliminated in consolidation.  

Use of Estimates

The preparation of consolidated financial statements in conformity with U.S. generally accepted accounting principles requires management to make estimates and assumptions that materially affect the amounts reported in the consolidated financial statements. Actual results could differ from these estimates. The methods, estimates, and judgments the Company uses in applying its most critical accounting policies have a significant impact on the results it reports in its financial statements. The Securities and Exchange Commission has defined the most critical accounting policies as those that are most important to the portrayal of the Company’s financial condition and results and require the Company to make its most difficult and subjective judgments, often because of the need to make estimates of matters that are inherently uncertain. Based on this definition, the Company’s most critical accounting policies include: revenue recognition, goodwill, other long-lived asset valuations, income taxes, stock-based compensation, and capitalization of software development costs.

Adoption of ASC Topic 606, "Revenue from Contracts with Customers"

In May 2014, the Financial Accounting Standards Board (“FASB”) issued ASU 2014-09, “Revenue from Contracts with Customers” (“ASC 606”). ASC 606 clarifies the accounting for revenue arising from contracts with customers and specifies the disclosures that an entity should include in its financial statements. During 2016, the FASB issued certain amendments to the standard relating to the principal versus agent guidance, accounting for licenses of intellectual property identifying performance obligations as well as the guidance on transition, collectability, noncash consideration and the presentation of sales and other similar taxes. We adopted ASC 606 using the modified retrospective method on July 1, 2018.

The effect of applying ASC 606 did not result in an opening balance adjustment to retained earnings or any other balance sheet accounts because the Company: (1) identified similar performance obligations under ASC 606 as compared with deliverables and separate units of account previously identified; (2) determined the transaction price to be consistent; and (3) concluded that revenue is recorded at the same point in time, upon performance under both ASC 605 and ASC 606. The adoption of ASC 606 did not require significant changes in our internal controls and procedures over financial reporting and disclosures. However, we made enhancements to existing internal controls and procedures to ensure compliance with the new guidance.

Revenue Recognition

We recognize revenue 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 revenue, 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 revenue when a performance obligation is satisfied. We account for a contract based on the terms and conditions the parties agree to, the contract has commercial substance and collectability of consideration is probable. 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.

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.

For performance obligations where control is transferred over time, revenue is 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. Revenue related to fixed-price contracts for application development and systems integration services, consulting or other technology services is recognized as the service is performed using the output method, under which the total value of revenue is recognized based on each contract’s deliverable(s) as they are completed and when value is transferred to a customer. Revenue related to fixed-price application maintenance, testing and business process services is recognized based on our right to invoice for services performed for contracts in which the invoicing is representative of the value being delivered, in accordance with the practical expedient in ASC 606-10-55-18.

If our invoicing is not consistent with the value delivered, revenue is recognized as the service is performed based on the method described above. The output method measures the results achieved and value transferred to a customer, 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. Revenue related to fixed-price hosting and infrastructure services is recognized based on our right to invoice for services performed for contracts in which the invoicing is representative of the value being delivered, in accordance with the practical expedient in ASC 606-10-55-18. If our invoicing is not consistent with value delivered, revenue is recognized on a straight-line basis unless revenue is earned and obligations are fulfilled in a different pattern. The revenue recognition method applied to the types of contracts described above provides the most faithful depiction of performance towards satisfaction of our performance obligations.

Revenue related to our software license arrangements that do not require significant modification or customization of the underlying software is recognized when the software is delivered as control is transferred at a point in time. For software license arrangements that require significant functionality enhancements or modification of the software, revenue for the software license and related services is recognized as the services are performed in accordance with the methods described above. In software hosting arrangements, the rights provided to the customer, such as ownership of a license, contract termination provisions and the feasibility of the client to operate the software, are considered in determining whether the arrangement includes a license or a service. Revenue related to software maintenance and support is generally recognized on a straight-line basis over the contract period.

Revenue related to transaction-based or volume-based contracts is recognized over the period the services are provided in a manner that corresponds with the value transferred to the customer to-date relative to the remaining services to be provided.

From time to time, we may enter into arrangements with third party suppliers to resell products or services. In such cases, we evaluate whether we are the principal (i.e. report revenue on a gross basis) or agent (i.e. report revenue on a net basis). In doing so, we first evaluate whether we control the good or service before it is transferred to the customer. If we control the good or service before it is transferred to the customer, we are the principal; if not, we are the agent. Determining whether we control the good or service before it is transferred to the customer may require judgment.

We provide customers with assurance that the related deliverable will function as the parties intended because it complies with agreed-upon specifications. General updates or patch fixes are not considered an additional performance obligation in the contract.

Variable consideration is estimated using either the sum of probability weighted amounts in a range of possible consideration amounts (expected value), or the single most likely amount in a range of possible consideration amounts (most likely amount), depending on which method better predicts the amount of consideration to which we may be entitled. We include in the transaction price variable consideration only to the extent it is probable that a significant reversal of revenue recognized will not occur when the uncertainty associated with the variable consideration is resolved. Our estimates of variable consideration and determination of whether to include estimated amounts in the transaction price may involve judgment and are based largely on an assessment of our anticipated performance and all information that is reasonably available to us.

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 Accounts Receivable and Contract Balances

We classify our right to consideration in exchange for deliverables as either a receivable or a contract asset (unbilled receivable). 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 revenue related to our 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. 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, judgement, and other applicable factors.

A contract asset is a right to consideration that is conditional upon factors other than the passage of time. Contract assets are presented in current and other assets in our consolidated balance sheets and primarily relate to unbilled amounts on fixed-price contracts utilizing the output method of revenue recognition. The table below shows movements in contract assets:

	Contract assets
Balance – September 30, 2018	$	5,005,395
Revenue recognized during the period but not billed		1,571,453
Amounts reclassified to accounts receivable		(673,802	)
Other		-
Balance – December 31, 2018	$	5,903,046	(1)

(1) Contract asset balances for December 31, 2018 includes a current and long-term contract asset, $2,727,921, and $3,175,125, respectively.

Our contract assets and liabilities are reported in a net position at the end of each reporting period. The difference between the opening and closing balances of our contract assets and deferred revenue primarily results from the timing difference between our performance obligations and the customer’s payment. We receive payments from customers based on the terms established in our contracts, which may vary generally by contract type.

The table below shows movements in the deferred revenue balances (current and noncurrent) for the period:

	Contract liability
Balance – September 30, 2018	$	2,115,539
Amounts billed but not recognized as revenue		1,362,981
Revenue recognized related to the opening balance of deferred revenue		(807,224	)
Other		-
Balance – December 31, 2018	$	2,671,296

Our contract assets and liabilities are reported in a net position on a contract by contract basis at the end of each reporting period. The difference between the opening and closing balances of our contract assets and deferred revenue primarily results from the timing difference between our performance obligations and the customer’s payment. We receive payments from customers based on the terms established in our contracts, which may vary generally by contract type.

Disaggregation of Revenue

The table below presents disaggregated revenue from contracts with customers by customer geography and contract-type. We believe this disaggregation best depicts the nature, amount, timing and uncertainty of our revenue and cash flows that may be affected by industry, market and other economic factors:

	For the Six Months Ended December 31 2018
Geography	Subscription & support		Professional services		Transaction based		Total
North America	$	8,217,716	$	1,854,737	$	1,408,896	$	11,481,349
International		—		—		25,882		25,882
Total	$	1,854,737	$	1,434,778	$	11,507,231	$	11,507,231

Earnings Per Share

Basic net income per common share (“Basic EPS”) excludes dilution and is computed by dividing net income applicable to common shareholders by the weighted average number of common shares outstanding during the period. Diluted net income per common share (“Diluted EPS”) reflects the potential dilution that could occur if stock options or other contracts to issue shares of common stock were exercised or converted into common stock. The computation of Diluted EPS does not assume exercise or conversion of securities that would have an antidilutive effect on net income per common share.

The following table presents the components of the computation of basic and diluted earnings per share for the periods indicated:

	Three Months Ended				Six Months Ended
	December 31,				December 31,
	2018		2017		2018		2017
Numerator
Net income applicable to common shareholders	$	1,538,997	$	1,187,518	$	2,358,795	$	1,401,208
Denominator
Weighted average common shares outstanding, basic		19,822,000		19,487,000		19,804,000		19,455,000
Warrants to purchase common stock		553,000		851,000		670,000		885,000
Weighted average common shares outstanding, diluted		20,375,000		20,338,000		20,474,000		20,340,000
Net income per share
Basic	$	0.08	$	0.06	$	0.12	$	0.07
Diluted	$	0.08	$	0.06	$	0.12	$	0.07

Reclassifications

Certain prior year amounts have been reclassified to conform with the current year’s presentation. These reclassifications have no impact on the previously reported results.