XML 33 R22.htm IDEA: XBRL DOCUMENT
v3.10.0.1

Basis of presentation (Policies) | 9 Months Ended
--- | ---
Sep. 30, 2018
Accounting Policies [Abstract] |
Basis of Presentation | The accompanying unaudited interim consolidated financial statements of PAR Technology Corporation (the “Company” or “PAR”) have been prepared in accordance with U.S. generally accepted accounting principles (“GAAP”) for interim financial statements and the instructions to Form 10-Q and Article 10 of Regulation S-X pertaining to interim financial statements. Accordingly, they do not include all information and footnotes required by GAAP for annual financial statements. In the opinion of management, such unaudited interim consolidated financial statements include all normal and recurring adjustments necessary for a fair presentation of the results for the interim periods included in this Quarterly Report on Form 10-Q (“Quarterly Report”). Operating results for the three and nine months ended September 30, 2018 are not necessarily indicative of the results of operations that may be expected for any future period. Certain amounts for prior periods have been reclassified to conform to the current period classification.
Use of Estimates | The preparation of unaudited interim consolidated financial statements requires management of the Company to make a number of estimates, judgments and assumptions relating to the reported amounts of assets and liabilities and the disclosure of contingent assets and liabilities at the date of the unaudited interim consolidated financial statements and the reported amount of revenues and expenses during the period. Primary areas where financial information is subject to the use of estimates, assumptions and the application of judgment include revenue recognition, accounts receivable, inventories, accounting for business combinations, contingent consideration, equity compensation, goodwill and intangible assets, and taxes. Actual results could differ from those estimates.
Revenue Recognition | We generally expense sales commissions when incurred because the amortization period would be less than one year or the total amount of commissions would be immaterial. Commissions are recorded in selling, general and administrative expenses (SG&A). We elected to exclude from the measurement of the transaction price all taxes assessed by governmental authorities that are both imposed on and concurrent with a specific revenue-producing transaction and collected by the Company from a customer (for example, sales, use, value added, and some excise taxes). In May 2014, the Financial Accounting Standards Board ("FASB") issued ASU 2014-09, Revenue from Contracts with Customers, codified as ASC Topic 606 (“ASC 606”). The FASB issued amendments to ASC 606 during 2016. ASC 606 requires additional disclosures regarding the nature, amount, timing and uncertainty of revenue and related cash flows arising from contracts with customers. ASC 606 is effective for annual and interim reporting periods beginning after December 15, 2017. Two adoption methods are permitted under ASU 2014-09. The new standard may be adopted through either retrospective application to all periods presented in our consolidated financial statements (full retrospective) or through a cumulative effect adjustment to retained earnings at the effective date (modified retrospective). The Company adopted the new standard effective January 1, 2018 using the modified retrospective method. We reviewed significant open contracts with customers for each revenue source. Our revenue is derived from Software as a Service (SaaS), hardware and software sales, software activation, hardware support, installations, maintenance, professional services, contracts and programs. ASC 606 requires us to distinguish and measure performance obligations under customer contracts. Transaction prices are allocated to each distinct performance obligation and recognized as revenue when, or as, the performance obligation is satisfied. Performance obligations are satisfied over time as work progresses or at a point in time. We evaluated the potential performance obligations within our Restaurant/Retail reporting segment (Brink/POS, SureCheck, and PixelPoint) and evaluated whether each deliverable or promise met the ASC 606 criteria to be considered distinct performance obligations. Revenue in the Restaurant/Retail reporting segment is recognized at a point in time for software, manufactured or “purchased for re-sale” hardware (such as terminals, peripherals printers, card readers and other accessories), installations and “pass through licenses”. Revenue on these items are recognized when the customer obtains control of the asset. This generally occurs upon delivery and acceptance by the customer or upon installation or delivery to a third party carrier for onward delivery to customer. Additionally, revenue in the Restaurant/Retail reporting segment relating to subscription services for software, SaaS, Advanced Exchange, on-site support and other services is recognized over time as the customer simultaneously receives and consumes the benefits of the Company’s performance obligations. Our support services are stand-ready obligations that are provided over the life of the contract, which typically ranges from 12 months to 60 months. We offer installation services to our customers for hardware and software for which we primarily hire third-party contractors to install the equipment on our behalf. We pay the third-party contractors an installation service fee based on an hourly rate as agreed upon between us and contractor. When third party installers are used, we determine whether the nature of our promises are performance obligations to provide the specified goods or services ourselves (principal) or to arrange for the third party to provide the goods or services (agent). In our customer arrangements, we are primarily responsible for providing a good or service, we have inventory risk before the good or service is transferred to the customer, and we have discretion in establishing prices. We are the principal in the arrangement and record installation revenue on a gross basis. At times we will offer maintenance services at different prices for customers based on the life of the service, which typically ranges from 12 to 60 months. The support services are a ‘stand-ready obligation’ satisfied over time on the basis that customer consumes and receives a benefit from having access to our support resources, when and as needed, throughout the contract term. For this reason, the support services are recognized ratably over the term since we satisfy our obligation to stand ready by performing these services each day. Our contracts typically require payment within 30 to 90 days from the shipping date or installation date, depending on our terms with the customer. For all sales not bundled with other performance obligations, the Company determines selling price based on the following table.
Restaurant and Retail
Performance Obligation | Stand-alone Selling Price | Cost Plus Margin
Hardware | X |
Pass Thru Hardware (Terminals, Printers, Card Readers, etc.) |  | X
Hardware Support (i.e., Advanced Exchange) |  | X
Installation |  | X
Maintenance |  | X
Software | X |
Software Updates |  | X
Professional Services / Project Management |  | X
Software Activation |  | X
Our revenue in the Government reporting segment is recognized over time as control is generally transferred continuously to our customers. Revenue generated by the Government reporting segment is predominantly related to services provided, however, revenue is also generated through the sale of materials, software, hardware, and maintenance. For the Government reporting segment cost plus fixed fee contract portfolio, revenue is recognized over time using costs incurred to date to measure progress toward satisfying our performance obligations. Incurred cost represents work performed, which corresponds with, and thereby best depicts, the transfer of control to the customer. Contract costs include labor, material, overhead and general & administrative expenses. Profit is recognized on the fixed fee portion of the contract as costs are incurred and invoiced. Long-term fixed price contracts and programs involve the use of various techniques to estimate total contract revenue and costs. For long-term fixed price contracts, we estimate the profit on a contract as the difference between the total estimated revenue and expected costs to complete a contract and recognize that profit over the life of the contract. Contract estimates are based on various assumptions to project the outcome of future events. These assumptions include: labor productivity and availability; the complexity of the work to be performed; the cost and availability of materials; and the performance of subcontractors. Revenue and profit in future periods of contract performance are recognized using the aforesaid assumptions and adjusting the estimate. Allocating the transaction price varies based on the performance obligations within a specific contract as the stand-alone selling price of the software and maintenance/support is not always discernable. Once the services provided are determined to be distinct or not distinct, we evaluate how to allocate the transaction price. Generally, the Government reporting segment does not sell the same good or service to similar customers and the contract performance obligations are unique to each government solicitation. The performance obligations are typically not distinct. In cases where there are distinct performance obligations, the transaction price would be allocated to each performance obligation on a standalone basis. Cost plus margin is used for the cost plus fixed fee contract portfolios, and residual is used for the fixed price and time & materials contracts portfolios. In determining when to recognize revenue, we analyze whether our performance obligations in our contracts are satisfied over a period of time or at a point in time. In general, our performance obligations are satisfied over a period of time. However, there may be circumstances where the latter or both scenarios could apply to a contract. We usually expect payment within 30 to 90 days from the date of service, depending on our terms with the customer.

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

X
- Definition Disclosure of accounting policy for basis of accounting, or basis of presentation, used to prepare the financial statements (for example, US Generally Accepted Accounting Principles, Other Comprehensive Basis of Accounting, IFRS). + References No definition available. + Details
Name: | us-gaap_BasisOfAccountingPolicyPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for revenue from contract with customer. + References Reference 1: http://www.xbrl.org/2003/role/exampleRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -SubTopic 10 -Section 50 -Paragraph 4 -Subparagraph (e) -URI http://asc.fasb.org/extlink&oid=84158767&loc=d3e18823-107790 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -URI http://asc.fasb.org/topic&trid=49130388 + Details
Name: | us-gaap_RevenueFromContractWithCustomerPolicyTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- Definition Disclosure of accounting policy for the use of estimates in the preparation of financial statements in conformity with generally accepted accounting principles. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 12 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6191-108592 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 11 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6161-108592 Reference 3: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 9 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6143-108592 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 1 -Subparagraph (b) -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e5967-108592 Reference 5: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 4 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6061-108592 Reference 6: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 8 -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e6132-108592 Reference 7: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 275 -SubTopic 10 -Section 50 -Paragraph 1 -Subparagraph (c) -URI http://asc.fasb.org/extlink&oid=99393423&loc=d3e5967-108592 + Details
Name: | us-gaap_UseOfEstimates
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration