Note 1 – Summary of Significant Accounting Policies

Nature of Operations

VASCO Data Security International, Inc. and its wholly owned subsidiaries design, develop, market and support hardware and software security systems that manage and secure access to information assets. VASCO has operations in Austria, Australia, Belgium, Brazil, China, France, India, Japan, The Netherlands, Singapore, Switzerland, the United Arab Emirates, the United Kingdom, and the United States (U.S.).

Basis of Presentation

The accompanying unaudited condensed consolidated financial statements include the accounts of VASCO Data Security International, Inc. and its subsidiaries and have been prepared pursuant to the rules and regulations of the Securities and Exchange Commission regarding interim financial reporting. Accordingly, they do not include all of the information and notes required by generally accepted accounting principles for complete financial statements and should be read in conjunction with the audited consolidated financial statements included in the company’s Annual Report on Form 10-K for the year ended December 31, 2012.

In the opinion of management, the accompanying unaudited condensed consolidated financial statements have been prepared on the same basis as the audited consolidated financial statements, and include all adjustments, consisting only of normal recurring adjustments, necessary for the fair presentation of the results of the interim periods presented. All significant intercompany accounts and transactions have been eliminated. The operating results for the interim periods presented are not necessarily indicative of the results expected for a full year.

Principles of Consolidation

The consolidated financial statements include the accounts of VASCO Data Security International, Inc. and its wholly owned subsidiaries. All significant intercompany accounts and transactions have been eliminated in consolidation.

During 2011, our wholly-owned Dutch subsidiary, DigiNotar B.V., was declared bankrupt. The court-appointed trustee is responsible for the business activities, administration and liquidation of DigiNotar B.V. Accordingly, related assets, liabilities and activities are reflected in discontinued operations.

Estimates and Assumptions

The preparation of financial statements in conformity with accounting principles generally accepted in the U.S. requires management to make estimates and assumptions that affect the reported amounts of assets and liabilities and disclosure of contingent assets and liabilities at the date of the financial statements and the reported amounts of revenue and expenses during the reporting period. Actual results could differ from those estimates.

Foreign Currency Translation and Transactions

The financial position and results of the operations of the majority of the company’s foreign subsidiaries are measured using the local currency as the functional currency. Accordingly, assets and liabilities are translated into U.S. Dollars using current exchange rates as of the balance sheet date. Translation adjustments arising from differences in exchange rates are charged or credited to other comprehensive income. Revenue and expenses are translated at average exchange rates prevailing during the year. Gains and losses resulting from foreign currency transactions are included in the condensed consolidated statements of operations in other income (expense).

The financial position and results of operations of our operations in Singapore and Switzerland are measured in U.S. Dollars. For these subsidiaries, gains and losses that result from foreign currency transactions are included in the consolidated statements of operations in other income (expense).

For the three and six months ended June 30, 2013, foreign currency transactions resulted in losses of $0 and $91, respectively, compared to losses of $49 and gains of $46 for the same period in 2012.

Revenue Recognition

We recognize revenue in accordance with Financial Accounting Standards Board (FASB) Accounting Standards Codification (ASC) 985-605, Software – Revenue Recognition, ASC 985-605-25, Revenue Recognition – Multiple Element Arrangements, and Staff Accounting Bulletin 104.

Revenue is recognized when there is persuasive evidence that an arrangement exists, delivery has occurred, the fee is fixed or determinable and collection of the revenue is probable.

In multiple-element arrangements, some of our products are accounted for under the software provisions of ASC 985-605 and others under the provisions that relate to the sale of non-software products.

In our typical multiple-element arrangement, the primary deliverables include:

a client component (i.e., an item that is used by the person being authenticated in the form of either a new standalone hardware device or software that is downloaded onto a device the customer already owns),

host system software that is installed on the customer’s systems (i.e., software on the host system that verifies the identity of the person being authenticated) or licenses for additional users on the host system software, if the host system software had been installed previously, and

post contract support (“PCS”) in the form of maintenance on the host system software or support.

Our multiple-element arrangements may also include other items that are usually delivered prior to the recognition of any revenue and incidental to the overall transaction, such as initialization of the hardware device, customization of the hardware device itself or the packaging in which it is delivered, deployment services where we deliver the device to our customer’s end-use customer or employee and, in some limited cases, professional services to assist with the initial implementation of a new customer.

In multiple-element arrangements that include a hardware client device, we allocate the selling price among all elements, delivered and undelivered, based on our internal price lists and the percentage of the selling price of that element, per the price list, to the total of the estimated selling price of all of the elements per the price list. Our internal price lists for both delivered and undelivered elements were determined to be reasonable estimates of the selling price of each element based on a comparison of actual sales made to the price list for each item delivered and to vendor specific objective evidence (“VSOE”) for undelivered items.

Undelivered elements primarily are PCS. The method by which we determine VSOE has validated that the price lists are reasonable estimates of the selling price for PCS. The estimated selling price of PCS items is based on an established percentage of the user license fee attributable to the specific software and is applied consistently to all PCS arrangements. The percentage we use to establish VSOE, which is also generally consistent with the percentage used in the price list, is developed using the “bell curve method”. This method relies on historical data to show that at least 80% of renewals are within 15% of the median renewal percentage rate.

In multiple-element arrangements that include a software client device, we account for each element under the standards of ASC 985-605 related to software. When software client device and host software are delivered elements, we use the Residual Method (ASC 605-25) for determining the amount of revenue to recognize for token and software licenses if we have VSOE for all of the undelivered elements. Any discount provided to the customer is applied fully to the delivered elements in such an arrangement. VSOE of fair value of PCS agreements is based on customer renewal transactions for the initial two years on a worldwide basis. In sales arrangements where VSOE of fair value has not been established, revenue for all elements is deferred and amortized over the life of the arrangement.

For transactions other than multiple-element arrangements, we recognize revenue as follows:

Hardware Revenue and License Fees: Revenue from the sale of computer security hardware or the license of software is recorded upon shipment or, if an acceptance period is allowed, at the latter of shipment or customer acceptance. No significant obligations or contingencies exist with regard to delivery, customer acceptance or rights of return at the time revenue is recognized.

Maintenance and Support Agreements: Maintenance and support agreements generally call for us to provide software updates and technical support, respectively, to customers. Revenue on maintenance and technical support is deferred and recognized ratably over the term of the applicable maintenance and support agreement.

Services: Revenue is recognized ratably over the period in which the service is provided.

Consulting and Education Services: We provide consulting and education services to our customers. Revenue from such services is recognized during the period in which the services are performed.

We recognize revenue from sales to distributors and resellers on the same basis as sales made directly to customers. We recognize revenue when there is persuasive evidence that an arrangement exists, delivery has occurred, the fee is fixed or determinable and collection of the revenue is probable.

For large-volume transactions, we may negotiate a specific price that is based on the number of users of the software license or quantities of hardware supplied. The per unit prices for large-volume transactions are generally lower than transactions for smaller quantities and the price differences are commonly referred to as volume-purchase discounts.

All revenue is reported on a net basis, excluding any sales taxes or value added taxes.

Cash and Cash Equivalents

Cash and cash equivalents are stated at cost plus accrued interest, which approximates fair value. Cash equivalents are high-quality short term money market instruments, with original maturities of three months or less. Cash and cash equivalents are held by a number of U.S. and non-U.S. commercial banks and money market investment funds.

Accounts Receivable and Allowance for Doubtful Accounts

The credit-worthiness of customers (including distributors and resellers) is reviewed prior to shipment. A reasonable assurance of collection is a requirement for revenue recognition. Verification of credit and/or the establishment of credit limits are part of the customer contract administration process. Credit limit adjustments for existing customers may result from the periodic review of outstanding accounts receivable. The company records trade accounts receivable at invoice values, which are generally equal to fair value.

We maintain allowances for doubtful accounts for estimated losses resulting from the inability of our customers to make payments for goods and services. We analyze accounts receivable balances, customer credit-worthiness, current economic trends and changes in our customer payment timing when evaluating the adequacy of the allowance for doubtful accounts. The allowance is based on a specific review of all significant past-due accounts. If the financial condition of our customers deteriorate, resulting in an impairment of their ability to make payments, additional allowances may be required.

Inventories

Inventories, consisting principally of hardware and component parts, are stated at the lower of cost or market. Cost is determined using the first-in-first-out (FIFO) method. We write down inventory when it appears that the carrying cost of the inventory may not be recovered through subsequent sale of the inventory. The company analyzes the quantity of inventory on hand, the quantity sold in the past year, the anticipated sales volume in the form of sales to new customers as well as sales to previous customers, the expected sales price and the cost of making the sale when evaluating the valuation of our inventory. If the sales volume or sales price of a specific model declines significantly, additional write downs may be required.

Property and Equipment

Property and equipment are stated at cost. Depreciation is computed using the straight-line method over the estimated useful lives of the related assets ranging from three to seven years. Additions and improvements are capitalized, while expenditures for maintenance and repairs are charged to operations as incurred. Gains or losses resulting from sales, disposals, or retirements are recorded as incurred, at which time related costs and accumulated depreciation are removed from the accounts.

Goodwill and Other Intangibles

We account for goodwill and indefinite-lived intangible assets in accordance with ASC Topic 350-20, Goodwill and Other. Indefinite-lived intangible assets include proprietary technology, patents, trademarks and other intangible assets. Intangible assets other than patents with definite lives are amortized over the useful life, generally three to seven years for proprietary technology. Patents are amortized over the life of the patent, generally 20 years in the U.S.

We assess the impairment of goodwill and intangible assets with indefinite lives each year-end or whenever events or changes in circumstances indicate that the carrying value may not be recoverable. Factors considered important which could trigger an impairment review include significant underperformance relative to expected historical or projected future operating results, significant changes in the manner of our use of the acquired assets or the strategy for our overall business, and significant negative industry or economic trends. Once identified, the amount of the impairment is computed by comparing carrying value of the assets to fair value. Fair value for goodwill and intangible assets is determined using our stock price which is a level 1 valuation, as defined in ASC 820-10, Fair Value Measurements and Disclosures.

Research and Development Costs

Costs for research and development, principally the design and development of hardware, and the design and development of software prior to the determination of technological feasibility, are expensed as incurred on a project-by-project basis.

Software Development Costs

We capitalize software development costs in accordance with ASC 985-20, Costs of Software to be Sold, Leased, or Marketed. Research costs and software development costs, prior to the establishment of technological feasibility, determined based upon the creation of a working model, are expensed as incurred. Our software capitalization policy defines technological feasibility as a functioning beta test prototype with confirmed manufacturability (a working model), within a reasonably predictable range of costs. Additional criteria include receptive customers, or potential customers, as evidenced by interest expressed in a beta test prototype, at some suggested selling price. Our policy is to amortize capitalized costs by the greater of (a) the ratio that current gross revenue for a product bears to the total of current and anticipated future gross revenue for that product or (b) the straight-line method over the remaining estimated economic life of the product, generally two to five years, including the period being reported on. No software development costs were capitalized during the three and six months ended June 30, 2013.

Income Taxes

We account for income taxes under the asset and liability method. Deferred tax assets and liabilities are recognized for the future tax consequences attributable to differences between the financial statement carrying amounts of existing assets and liabilities and their respective tax bases and operating loss and tax credit carryforwards. We measure deferred tax assets and liabilities using enacted tax rates expected to apply to taxable income in the years in which those temporary differences are expected to be recovered or settled. We recognize the effect of a change in tax rates on deferred tax assets and liabilities in income in the period that includes the enactment date.

We monitor our potential income tax exposures as required by ASC 740-10, Income Taxes.

We have significant net operating loss carryforwards in the U.S. and other countries which are available to reduce the liability on future taxable income. A valuation reserve has been provided to offset some of these future benefits because we have not determined that their realization is more likely than not.

Fair Value of Financial Instruments

At June 30, 2013 and December 31, 2012, our financial instruments were cash equivalents, accounts receivable, accounts payable and accrued liabilities. The estimated fair value of our financial instruments has been determined using level one inputs as defined in ASC 820, Fair Value Measurements and Disclosures. The fair values of the financial instruments were not materially different from their carrying amounts at June 30, 2013 and December 31, 2012.

Accounting for Leases

All of our leases are operating leases. Rent expense on facility leases is charged evenly over the life of the lease, regardless of the timing of actual payments.

Stock-Based Compensation

We have stock-based employee compensation plans, described in Note 10. ASC 718-10, Stock Compensation requires us to estimate the fair value of restricted stock granted to employees, directors and others and to record compensation expense equal to the estimated fair value. Compensation expense is recorded on a straight-line basis over the vesting period.

Warranty

Warranties are provided on the sale of certain of our products and an accrual for estimated future claims is recorded at the time revenue is recognized. We estimate the cost based on past claims experience, sales history and other considerations. We regularly assess the adequacy of our estimates and adjust the amounts as necessary. Our standard practice is to provide a warranty on our hardware products for either a one or two year period after the date of purchase. Customers may purchase extended warranties covering periods from one to four years after the standard warranty period. We defer the revenue associated with the extended warranty and recognize it into income on a straight-line basis over the extended warranty period. We have historically experienced minimal actual claims over the warranty period.