4. SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES (Policies)	9 Months Ended
Jun. 30, 2016
Accounting Policies [Abstract]
Cash and Cash Equivalents	Cash and Cash Equivalents The Company considers all highly liquid investments with an original maturity of three months or less to be cash equivalents. At June 30, 2016 and September 30, 2015, cash and cash equivalents include cash on hand and cash in the bank. The Company maintains its cash in accounts held by large, globally recognized banks which, at times, may exceed federally insured limits as guaranteed by the Federal Deposit Insurance Corporation (FDIC). The FDIC insures these deposits up to $250,000. At June 30, 2016, $552,048 of the Company’s cash balance was uninsured, and on September 30, 2015, $1,743,406 was uninsured. The Company has not experienced any losses in such accounts.
Basic and Diluted Net Loss per Common Share	Basic and Diluted Net Loss per Common Share Basic loss per share is computed by dividing net loss available to common shareholders by the weighted average number of common shares outstanding during the reporting period. The weighted average number of shares is calculated by taking the number of shares outstanding and weighting them by the amount of time that they were outstanding. Diluted earnings per share reflects the potential dilution that could occur if stock options, warrants, and other commitments to issue common stock were exercised or equity awards vest resulting in the issuance of common stock that could share in the earnings of the Company. Diluted loss per share is the same as basic loss per share during periods where net losses are incurred since the inclusion of the potential common stock equivalents would be anti-dilutive as a result of the net loss.
Concentration of Credit Risk	Concentration of Credit Risk and Customer Concentrations All of the Company’s cash and cash equivalents are maintained in regional and national financial institutions. The Company has exposure to credit risk to the extent that its cash and cash equivalents exceed amounts covered by the U.S. federal deposit insurance; however, the Company has not experienced any losses in such accounts. In management’s opinion, the capitalization and operating history of the financial institutions are such that the likelihood of material loss is remote. During the three and nine months ended June 30, 2016, one customer made up 100% of revenues. Management believes the loss of this customer would have a material impact on the Company’s financial position, results of operations, and cash flows.
Revenue Recognition	Revenue Recognition Software license revenue is generally recognized when a signed contract or other persuasive evidence of an arrangement exists, the software has been electronically delivered, the license fee is fixed or is measured on a paid user basis, and collection of the resulting receivable is probable. When contracts contain multiple elements wherein Vendor-Specific Objective Evidence (“VSOE”) exists for all undelivered elements, we account for the delivered elements in accordance with the “Residual Method.” VSOE of fair value for maintenance and support is established by a stated renewal rate, if substantive, included in the license arrangement or rates charged in stand-alone sales of maintenance and support. Revenue from subscription license agreements, which include software, rights to unspecified future products and maintenance, is recognized ratably over the term of the subscription period. When the fair value of VSOE of post contract customer support cannot be determined, the revenue is recognized ratably over the contract period. In June 2014, the Company entered into an agreement to provide software and support to a third party for which no VSOE for any elements is known. Delivery of the use of the license was not achieved until December 2015; the only remaining undelivered element was post contract support services, and accordingly, the revenues will be recognized on a pro rata basis prospectively over the remaining 30 months of the related contracts. Deferred revenue results from fees billed to or collected from customers for which revenue has not yet been recognized. The Company has deferred revenue from one customer of $896,186 as of June 30, 2016 and $1,125,000 as of September 30, 2015.
Research and Development and Software Development Costs	Research and Development and Software Development Costs Capitalization of certain software development costs are recorded after the determination of technological feasibility. Based on our product development process, technological feasibility is determined upon the completion of a working model. To date, costs incurred by us from the completion of the working model to the point at which the product is ready for general release do not have technological feasibility. Accordingly, we have charged all such costs to research and development expense in the period incurred. Our research and development costs incurred in our continuing operations for the three months ended June 30, 2016 and 2015 were $140,962 and $27,195, respectively, and for the nine months ended June 30, 2016 and 2015 were $378,605 and $68,845, respectively.
Recent Accounting Announcements	Recent Accounting Announcements The Financial Accounting Standards Board (“FASB”) issues Accounting Standards Updates (“ASU”) to amend the authoritative literature in the Accounting Standards Codification (“ASC”). There have been a number of ASUs to date that amend the original text of ASC. The Company believes those updates issued to date either (i) provide supplemental guidance, (ii) are technical corrections, (iii) are not applicable to the Company or (iv) are not expected to have a significant impact on the Company. In February 2016, the FASB issued ASU 201602, Leases (Topic 840), to increase transparency and comparability among organizations by recognizing lease assets and lease liabilities on the balance sheet and disclosing key information about leasing arrangements. The amendments in this standard are effective for fiscal years beginning after December 15, 2018, including interim periods within those fiscal years, for a public entity. Early adoption of the amendments in this standard is permitted for all entities and the Company must recognize and measure leases at the beginning of the earliest period presented using a modified retrospective approach. The Company is currently in the process of evaluating the effect this guidance will have on its financial statements and related disclosures. In June 2016, the FASB issued ASU 2016-13, Financial Instruments — Credit Losses (Topic 326). This ASU requires financial assets (or groups of financial assets) measured at amortized cost basis to be presented at the net amount expected to be collected, among other provisions. The provisions of this ASU are effective for fiscal years, and interim periods within those fiscal years, beginning after December 15, 2019. Early adoption is permitted as of fiscal years beginning after December 15, 2018, including interim periods within those fiscal years. The Company should generally apply the amendment on a modified retrospective basis through a cumulative-effect adjustment to retained earnings as of the beginning of the first reporting periods in which the amendment is effective. The Company is currently in the process of evaluating the effect this guidance will have on its financial statements and related disclosures. In March 2016, the FASB issued ASU 2016-09, Compensation — Stock Compensation (Topic 718). This ASU simplifies several aspects of the accounting for share-based payment transactions, including the income tax consequences, classification of awards as either equity or liabilities, and classification on the statement of cash flows. The provisions of this ASU are effective for fiscal years, and interim periods within those fiscal years, beginning after December 15, 2016. Early adoption is permitted. The Company should apply the amendment using transition guidance for each aspect of the ASU. The Company is currently in the process of evaluating the effect this guidance will have on its financial statements and related disclosures. In January 2016, the FASB issued ASU 2016-01, Financial Instruments — Overall (Subtopic 825-10): Recognition and Measurement of Financial Assets and Financial Liabilities. This ASU makes targeted improvements to the accounting for, and presentation and disclosure of, financial assets and liabilities. The ASU further requires separate presentation of financial assets and financial liabilities by measurement category on the balance sheet or the accompanying notes to the financial statements. The provisions of this ASU are effective for fiscal years, and interim periods within those fiscal years, beginning after December 15, 2017. Early adoption is permitted based upon guidance issued within the ASU. The Company should apply the amendment prospectively, with a cumulative-effect adjustment to the balance sheet as of the beginning of the fiscal year of adoption. The Company is currently in the process of evaluating the effect this guidance will have on its financial statements and related disclosures. In May 2014, the FASB issued ASU 2014-09, Revenue from Contracts with Customers (Topic 606). On August 12, 2015, the FASB issued ASU 2015-14, Revenue from Contracts with Customers (Topic 606) to defer the effective date to December 15, 2017 for annual reporting periods beginning after that date. The FASB also permitted early adoption of the standard, but not before the original effective date of December 15, 2016. The amendments in ASU 2014-09 will be added to the Accounting Standards Codification as Topic 606, Revenue from Contracts with Customers, and will supersede the revenue recognition requirements in Topic 605, Revenue Recognition, as well as some cost guidance in Subtopic 605-35, Revenue Recognition - Construction-Type and Production-Type Contracts. The core principle of ASU 2014-09 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 this core principle, the guidance provides that an entity should apply the following steps: (1) identify the contract(s) 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, or as, the entity satisfies a performance obligation. Notably, the existing requirements for the recognition of a gain or loss on the transfer of non-financial 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 in ASU 2014-09. The new standard allows for two methods of adoption: (a) full retrospective adoption, meaning the standard is applied to all periods presented, or (b) modified retrospective adoption, meaning the cumulative effect of applying the new standard is recognized as an adjustment to the fiscal 2017 opening retained earnings balance. In March 2016 through May 2016, the FASB issued ASU 2016-08, Revenue from Contracts with Customers (Topic 606): Principal versus Agent Considerations (Reporting Revenue Gross versus Net), ASU 2016-10, Revenue from Contracts with Customers (Topic 606): Consensuses of the FASB Emerging Issues Task Force and ASU 2016-12, Revenue from Contracts with Customers (Topic 606): Narrow-Scope Improvements and Practical Expedients. ASU 2016-08, 2016-10 and 2016-12 clarify implementation guidance and introduce practical expedients, and are effective upon adoption of ASU 2014-09. The Company is currently in the process of evaluating the effect this guidance will have on its financial statements and related disclosures.

4. SUMMARY OF SIGNIFICANT ACCOUNTING POLICIES (Policies)

9 Months Ended

Jun. 30, 2016

Cash and Cash Equivalents

The Company considers all highly liquid investments with an original maturity of three months or less to be cash equivalents. At June 30, 2016 and September 30, 2015, cash and cash equivalents include cash on hand and cash in the bank. The Company maintains its cash in accounts held by large, globally recognized banks which, at times, may exceed federally insured limits as guaranteed by the Federal Deposit Insurance Corporation (FDIC). The FDIC insures these deposits up to $250,000. At June 30, 2016, $552,048 of the Company’s cash balance was uninsured, and on September 30, 2015, $1,743,406 was uninsured. The Company has not experienced any losses in such accounts.

Basic and Diluted Net Loss per Common Share

Basic and Diluted Net Loss per Common Share

Basic loss per share is computed by dividing net loss available to common shareholders by the weighted average number of common shares outstanding during the reporting period. The weighted average number of shares is calculated by taking the number of shares outstanding and weighting them by the amount of time that they were outstanding. Diluted earnings per share reflects the potential dilution that could occur if stock options, warrants, and other commitments to issue common stock were exercised or equity awards vest resulting in the issuance of common stock that could share in the earnings of the Company. Diluted loss per share is the same as basic loss per share during periods where net losses are incurred since the inclusion of the potential common stock equivalents would be anti-dilutive as a result of the net loss.

Concentration of Credit Risk

Concentration of Credit Risk and Customer Concentrations

All of the Company’s cash and cash equivalents are maintained in regional and national financial institutions. The Company has exposure to credit risk to the extent that its cash and cash equivalents exceed amounts covered by the U.S. federal deposit insurance; however, the Company has not experienced any losses in such accounts. In management’s opinion, the capitalization and operating history of the financial institutions are such that the likelihood of material loss is remote.

During the three and nine months ended June 30, 2016, one customer made up 100% of revenues. Management believes the loss of this customer would have a material impact on the Company’s financial position, results of operations, and cash flows.

Revenue Recognition

Revenue Recognition

Software license revenue is generally recognized when a signed contract or other persuasive evidence of an arrangement exists, the software has been electronically delivered, the license fee is fixed or is measured on a paid user basis, and collection of the resulting receivable is probable. When contracts contain multiple elements wherein Vendor-Specific Objective Evidence (“VSOE”) exists for all undelivered elements, we account for the delivered elements in accordance with the “Residual Method.” VSOE of fair value for maintenance and support is established by a stated renewal rate, if substantive, included in the license arrangement or rates charged in stand-alone sales of maintenance and support. Revenue from subscription license agreements, which include software, rights to unspecified future products and maintenance, is recognized ratably over the term of the subscription period. When the fair value of VSOE of post contract customer support cannot be determined, the revenue is recognized ratably over the contract period. In June 2014, the Company entered into an agreement to provide software and support to a third party for which no VSOE for any elements is known. Delivery of the use of the license was not achieved until December 2015; the only remaining undelivered element was post contract support services, and accordingly, the revenues will be recognized on a pro rata basis prospectively over the remaining 30 months of the related contracts. Deferred revenue results from fees billed to or collected from customers for which revenue has not yet been recognized.

The Company has deferred revenue from one customer of $896,186 as of June 30, 2016 and $1,125,000 as of September 30, 2015.

Research and Development and Software Development Costs

Research and Development and Software Development Costs

Capitalization of certain software development costs are recorded after the determination of technological feasibility. Based on our product development process, technological feasibility is determined upon the completion of a working model. To date, costs incurred by us from the completion of the working model to the point at which the product is ready for general release do not have technological feasibility. Accordingly, we have charged all such costs to research and development expense in the period incurred. Our research and development costs incurred in our continuing operations for the three months ended June 30, 2016 and 2015 were $140,962 and $27,195, respectively, and for the nine months ended June 30, 2016 and 2015 were $378,605 and $68,845, respectively.

Recent Accounting Announcements

Recent Accounting Announcements

The Financial Accounting Standards Board (“FASB”) issues Accounting Standards Updates (“ASU”) to amend the authoritative literature in the Accounting Standards Codification (“ASC”). There have been a number of ASUs to date that amend the original text of ASC. The Company believes those updates issued to date either (i) provide supplemental guidance, (ii) are technical corrections, (iii) are not applicable to the Company or (iv) are not expected to have a significant impact on the Company.

In February 2016, the FASB issued ASU 201602, Leases (Topic 840), to increase transparency and comparability among organizations by recognizing lease assets and lease liabilities on the balance sheet and disclosing key information about leasing arrangements. The amendments in this standard are effective for fiscal years beginning after December 15, 2018, including interim periods within those fiscal years, for a public entity. Early adoption of the amendments in this standard is permitted for all entities and the Company must recognize and measure leases at the beginning of the earliest period presented using a modified retrospective approach. The Company is currently in the process of evaluating the effect this guidance will have on its financial statements and related disclosures.

In June 2016, the FASB issued ASU 2016-13, Financial Instruments — Credit Losses (Topic 326). This ASU requires financial assets (or groups of financial assets) measured at amortized cost basis to be presented at the net amount expected to be collected, among other provisions. The provisions of this ASU are effective for fiscal years, and interim periods within those fiscal years, beginning after December 15, 2019. Early adoption is permitted as of fiscal years beginning after December 15, 2018, including interim periods within those fiscal years. The Company should generally apply the amendment on a modified retrospective basis through a cumulative-effect adjustment to retained earnings as of the beginning of the first reporting periods in which the amendment is effective. The Company is currently in the process of evaluating the effect this guidance will have on its financial statements and related disclosures.

In March 2016, the FASB issued ASU 2016-09, Compensation — Stock Compensation (Topic 718). This ASU simplifies several aspects of the accounting for share-based payment transactions, including the income tax consequences, classification of awards as either equity or liabilities, and classification on the statement of cash flows. The provisions of this ASU are effective for fiscal years, and interim periods within those fiscal years, beginning after December 15, 2016. Early adoption is permitted. The Company should apply the amendment using transition guidance for each aspect of the ASU. The Company is currently in the process of evaluating the effect this guidance will have on its financial statements and related disclosures.

In January 2016, the FASB issued ASU 2016-01, Financial Instruments — Overall (Subtopic 825-10): Recognition and Measurement of Financial Assets and Financial Liabilities. This ASU makes targeted improvements to the accounting for, and presentation and disclosure of, financial assets and liabilities. The ASU further requires separate presentation of financial assets and financial liabilities by measurement category on the balance sheet or the accompanying notes to the financial statements. The provisions of this ASU are effective for fiscal years, and interim periods within those fiscal years, beginning after December 15, 2017. Early adoption is permitted based upon guidance issued within the ASU. The Company should apply the amendment prospectively, with a cumulative-effect adjustment to the balance sheet as of the beginning of the fiscal year of adoption. The Company is currently in the process of evaluating the effect this guidance will have on its financial statements and related disclosures.

In May 2014, the FASB issued ASU 2014-09, Revenue from Contracts with Customers (Topic 606). On August 12, 2015, the FASB issued ASU 2015-14, Revenue from Contracts with Customers (Topic 606) to defer the effective date to December 15, 2017 for annual reporting periods beginning after that date. The FASB also permitted early adoption of the standard, but not before the original effective date of December 15, 2016. The amendments in ASU 2014-09 will be added to the Accounting Standards Codification as Topic 606, Revenue from Contracts with Customers, and will supersede the revenue recognition requirements in Topic 605, Revenue Recognition, as well as some cost guidance in Subtopic 605-35, Revenue Recognition - Construction-Type and Production-Type Contracts. The core principle of ASU 2014-09 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 this core principle, the guidance provides that an entity should apply the following steps: (1) identify the contract(s) 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, or as, the entity satisfies a performance obligation. Notably, the existing requirements for the recognition of a gain or loss on the transfer of non-financial 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 in ASU 2014-09. The new standard allows for two methods of adoption: (a) full retrospective adoption, meaning the standard is applied to all periods presented, or (b) modified retrospective adoption, meaning the cumulative effect of applying the new standard is recognized as an adjustment to the fiscal 2017 opening retained earnings balance. In March 2016 through May 2016, the FASB issued ASU 2016-08, Revenue from Contracts with Customers (Topic 606): Principal versus Agent Considerations (Reporting Revenue Gross versus Net), ASU 2016-10, Revenue from Contracts with Customers (Topic 606): Consensuses of the FASB Emerging Issues Task Force and ASU 2016-12, Revenue from Contracts with Customers (Topic 606): Narrow-Scope Improvements and Practical Expedients. ASU 2016-08, 2016-10 and 2016-12 clarify implementation guidance and introduce practical expedients, and are effective upon adoption of ASU 2014-09. The Company is currently in the process of evaluating the effect this guidance will have on its financial statements and related disclosures.

- Definition

Disclosure of accounting policy for cash and cash equivalents, including the policy for determining which items are treated as cash equivalents. Other information that may be disclosed includes (1) the nature of any restrictions on the entity's use of its cash and cash equivalents, (2) whether the entity's cash and cash equivalents are insured or expose the entity to credit risk, (3) the classification of any negative balance accounts (overdrafts), and (4) the carrying basis of cash equivalents (for example, at cost) and whether the carrying amount of cash equivalents approximates fair value.

+ References + Details

- Definition

Disclosure of accounting policy for its research and development and computer software activities including the accounting treatment for costs incurred for (1) research and development activities, (2) development of computer software for internal use, (3) computer software to be sold, leased or otherwise marketed as a separate product or as part of a product or process and (4) in-process research and development acquired in a purchase business combination.

+ References + Details

- Definition

Disclosure of accounting policy for revenue recognition. If the entity has different policies for different types of revenue transactions, the policy for each material type of transaction is generally disclosed. If a sales transaction has multiple element arrangements (for example, delivery of multiple products, services or the rights to use assets) the disclosure may indicate the accounting policy for each unit of accounting as well as how units of accounting are determined and valued. The disclosure may encompass important judgment as to appropriateness of principles related to recognition of revenue. The disclosure also may indicate the entity's treatment of any unearned or deferred revenue that arises from the transaction.

+ References + Details