10 keys to due diligence in the tech sector

Due diligence is a key element in any company purchase and sale process. Its objective is to validate all the information provided to the buyer. Each sector has its peculiarities and the tech sector is no exception. Here are 10 observations made by McGaldrey, an expert in DD services in the technology sector. Last year it performed more than 150 DD of software and hardware companies.

1. Complexities with software revenues:

Software revenue recognition remains the most common and most complex problem in the IT industry. The concepts are very difficult to understand and equally difficult to apply. The easy part of software revenue recognition is that even if it has an impact on EBITDA impact and reported revenue, it does not affect the timing of cash flows.

2. Staged proceedings:

Los compradores y vendedores están realizando más «due dilliegence» y la identificación de los problemas más importantes de manera anticipada. Se nos pregunta con frecuencia, para fasear  nuestra diligencia, abordar primero las áreas de reconocimiento de ingresos (ingresos diferidos) y, a veces la capitalización del desarrollo de software. Si estos temas pasan el examen, a continuación nos piden analizar  la calidad de las ganancias.

Software or SaaS:

Is the business to sell software or SaaS model services? There is sometimes confusion about this question, especially now that many companies are selling both alternatives. The accounting issues are very different depending on the answer.

4. SaaS installation costs:

It seems natural to think that revenue is recognized when services are delivered to customers. That couldn't be further from the truth when setting up or implementing a SaaS Client. Instead, suspend rational thinking and recognize configuration revenue over the length of the contract term and the estimated time of customer relationships, this may mean that instead of recognizing configuration revenue in the first month or two of a contract, it could be recognized over the next seven years, if the customer is expected to have this period of relationship.

5. What about the hardware?

Considering the level of knowledge, we often encounter surprises when inventory and cost of sales are sometimes incorrectly recorded in hardware companies, as they are often overlooked to focus on the most common risk areas.

6. Los ingresos diferidos «haircut»:

El concepto de que los ingresos diferidos pueden desvanecerse o recibir un significativo «Haircut» como resultado de la operación es difícil de entender. Por lo general, los ingresos diferidos en el balance de cierre de «Oldco» salta de un acantilado con la aplicación contable de las compras según el PCGA de EE.UU. en el balance de apertura de la «newco». Para elaborar la contabilidad, los mantenimientos diferidos, suscripciones o los ingresos de implementación se reducen al coste de la prestación del servicio, sumando  un razonable margen. El comprador debe entender este concepto y aplicarlo en el  modelo de los futuros ingresos y ganancias, así como la estructura de la convenios de préstamo (si la transacción es apalancada).

7. Capitalised software development costs:

Investors want to know what the company's EBITDA looks like with and without capitalizing software development costs. A common misconception is that management teams sometimes fail to recognize that the accounting treatment representing capitalization of software development is typically different for software companies and SaaS companies.

8. Working capital or an effective working exchange rate:

The idea of stagnant working capital seems old hat today, but it is very nuanced in the technology industry, due to the treatment of deferred revenue, where the focus is on its life cycle and seasonal accounting. If you have historically not recorded deferred revenue in accordance with US GAAP, the design or establishing working capital and subsequent workaround can be very complicated. We work with investors who run the gamut for the treatment of deferred revenue with respect to working capital, from excluding it entirely, to adjusting for the cost of providing future services (see observation. 6), to including the entire lack of adjustment. In the absence of good benchmarks for establishing working capital, sometimes the solution lies in estimating cash instead.

9. Sell-side due diligence:

A medida que el proceso para la venta de un negocio se vuelve cada vez más estandarizado, los vendedores están incluyendo cada vez más «sell-side due diligence» como parte del proceso. Una » Sell-side due diligence» ayuda a descubrir  cuestiones desconocidas en las que los compradores están involucrados (por ejemplo, el reconocimiento de los  ingresos por software), apoya o aumenta el valor  de la propuesta del  vendedor, y ayuda a disminuir el riesgo de una rotura de acuerdo.

10. Taxes really matter:

The tax ramifications on financial diligence and earnings quality are particularly severe in the software industry. Rules and regulations for sales taxes, which must be included in EBITDA, can vary from state to state or country to country. If a company is unable to recover taxes from customers, the corresponding amounts should be considered a reduction of EBITDA or at least considered a debt similar to an account payable (with interest and penalties) by the vendor at closing.