<SEC-DOCUMENT>0001193125-14-421990.txt : 20150203
<SEC-HEADER>0001193125-14-421990.hdr.sgml : 20150203
<ACCEPTANCE-DATETIME>20141121170155
<PRIVATE-TO-PUBLIC>
ACCESSION NUMBER:		0001193125-14-421990
CONFORMED SUBMISSION TYPE:	CORRESP
PUBLIC DOCUMENT COUNT:		1
FILED AS OF DATE:		20141121

FILER:

	COMPANY DATA:	
		COMPANY CONFORMED NAME:			ACTUATE CORP
		CENTRAL INDEX KEY:			0001062478
		STANDARD INDUSTRIAL CLASSIFICATION:	SERVICES-PREPACKAGED SOFTWARE [7372]
		IRS NUMBER:				943193197
		STATE OF INCORPORATION:			DE
		FISCAL YEAR END:			1231

	FILING VALUES:
		FORM TYPE:		CORRESP

	BUSINESS ADDRESS:	
		STREET 1:		951 MARINERS ISLAND BOULEVARD
		CITY:			SAN MATEO
		STATE:			CA
		ZIP:			94404
		BUSINESS PHONE:		650.645.3000

	MAIL ADDRESS:	
		STREET 1:		951 MARINERS ISLAND BOULEVARD
		CITY:			SAN MATEO
		STATE:			CA
		ZIP:			94404

	FORMER COMPANY:	
		FORMER CONFORMED NAME:	ACTUATE SOFTWARE CORP
		DATE OF NAME CHANGE:	19980527
</SEC-HEADER>
<DOCUMENT>
<TYPE>CORRESP
<SEQUENCE>1
<FILENAME>filename1.htm
<TEXT>
<HTML><HEAD>
<TITLE>CORRESP</TITLE>
</HEAD>
 <BODY BGCOLOR="WHITE">

 <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">November&nbsp;21, 2014 </P>
<P STYLE="margin-top:12pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">Mr.&nbsp;Stephen Krikorian </P> <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">Accounting Branch Chief </P>
<P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">Division of Corporate Finance </P> <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">Securities and Exchange Commission
</P> <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">Washington, D.C. 20549 </P> <P STYLE="font-size:12pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%" VALIGN="top" ALIGN="left"><B>Re:</B></TD>
<TD ALIGN="left" VALIGN="top"><B>Actuate Corporation </B></TD></TR></TABLE> <P STYLE="margin-top:0pt; margin-bottom:0pt; margin-left:4%; font-size:10pt; font-family:Times New Roman"><B>Form 10-K for the fiscal year ended December&nbsp;31, 2013 </B>-
<B>Filed March&nbsp;7, 2014 </B> </P> <P STYLE="margin-top:0pt; margin-bottom:0pt; margin-left:4%; font-size:10pt; font-family:Times New Roman"><B>Form 10-Q for the quarterly period ended June&nbsp;30, 2014</B> - <B>Filed August&nbsp;7, 2014 </B>
</P> <P STYLE="margin-top:0pt; margin-bottom:0pt; margin-left:4%; font-size:10pt; font-family:Times New Roman"><B>Forms 8-K furnished on August&nbsp;6, 2014,&nbsp;May&nbsp;1, 2014 and February&nbsp;4, 2014</B> </P>
<P STYLE="margin-top:0pt; margin-bottom:0pt; margin-left:4%; font-size:10pt; font-family:Times New Roman"><B>File No. 000-24607</B> </P> <P STYLE="margin-top:12pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">Dear
Mr.&nbsp;Krikorian: </P> <P STYLE="margin-top:6pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">We are writing in response to the letter from the Securities and Exchange Commission (the &#147;Commission&#148;) dated
October&nbsp;23, 2014 (the &#147;Comment Letter&#148;) in which the Staff of the Commission (the &#147;Staff&#148;) requested certain information regarding the above-referenced filings. For your convenience, the numbering of this response
corresponds to the section headings and numbering used by the Staff in the Comment Letter. </P> <P STYLE="margin-top:12pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">The Company acknowledges that the adequacy and accuracy of
disclosures in our filings with the Commission are our responsibility. We acknowledge that the Staff&#146;s comments or changes to our disclosures in response to the Staff&#146;s comments do not foreclose the Commission from taking any action with
respect to our filings. We also understand that the Staff&#146;s comments may not be asserted as a defense in any proceeding initiated by the Commission or any person under the federal securities laws of the United States. </P>
<P STYLE="margin-top:18pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Form 10-K for the fiscal year ended December&nbsp;31, 2013 </U></I></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Consolidated Financial Statements </U></I></P> <P STYLE="margin-top:6pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Note 13.
Geographic Information, page F-42 </U></I></P> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%">&nbsp;</TD>
<TD WIDTH="4%" VALIGN="top" ALIGN="left"><I>1.</I></TD>
<TD ALIGN="left" VALIGN="top"><I>We note your disclosure of &#147;North America&#148; revenue. Please tell us what consideration you gave to ASC 280-10-50-41, which requires you to disclose revenues for the United States, your country of domicile.
</I></TD></TR></TABLE> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>We respectfully advise the Staff that in future filings we will quantitatively disclose the revenue attributed to the
United States consistent with ASC 280-10-50-41 in response to the Staff&#146;s comment. The added disclosure has been included in our footnotes commencing with our Form 10-Q filing for the fiscal quarter ended September&nbsp;30, 2014.</B> </P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:4%; font-size:10pt; font-family:Times New Roman"><B>Below is an illustration of the proposed disclosure:</B> </P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:4%; font-size:10pt; font-family:Times New Roman"><I>&#147;Revenues by geographical region are as follows (in thousands):</I> </P>
<P STYLE="font-size:12pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="92%" BORDER="0" STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" ALIGN="center">


<TR>
<TD WIDTH="67%"></TD>
<TD VALIGN="bottom" WIDTH="3%"></TD>
<TD></TD>
<TD></TD>
<TD></TD>
<TD VALIGN="bottom" WIDTH="3%"></TD>
<TD></TD>
<TD></TD>
<TD></TD>
<TD VALIGN="bottom" WIDTH="3%"></TD>
<TD></TD>
<TD></TD>
<TD></TD>
<TD VALIGN="bottom" WIDTH="3%"></TD>
<TD></TD>
<TD></TD>
<TD></TD></TR>
<TR STYLE="font-family:Times New Roman; font-size:8pt">
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom" COLSPAN="6" ALIGN="center" STYLE="border-bottom:1.00pt solid #000000"><I>Three&nbsp;Months&nbsp;Ended<BR>September 30,</I></TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom" COLSPAN="6" ALIGN="center" STYLE="border-bottom:1.00pt solid #000000"><I>Nine months Ended<BR>September 30,</I></TD>
<TD VALIGN="bottom">&nbsp;</TD></TR>
<TR STYLE="font-family:Times New Roman; font-size:8pt">
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom" COLSPAN="2" ALIGN="center" STYLE="border-bottom:1.00pt solid #000000"><I>2014</I></TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom" COLSPAN="2" ALIGN="center" STYLE="border-bottom:1.00pt solid #000000"><I>2013</I></TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom" COLSPAN="2" ALIGN="center" STYLE="border-bottom:1.00pt solid #000000"><I>2014</I></TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom" COLSPAN="2" ALIGN="center" STYLE="border-bottom:1.00pt solid #000000"><I>2013</I></TD>
<TD VALIGN="bottom">&nbsp;</TD></TR>


<TR BGCOLOR="#cceeff" STYLE="font-family:Times New Roman; font-size:10pt">
<TD VALIGN="top"> <P STYLE="margin-left:1.00em; text-indent:-1.00em; font-size:10pt; font-family:Times New Roman"><I>Revenues:</I></P></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom"></TD></TR>
<TR STYLE="font-family:Times New Roman; font-size:10pt">
<TD VALIGN="top"> <P STYLE="margin-left:1.00em; text-indent:-1.00em; font-size:10pt; font-family:Times New Roman"><I>North America (1)</I></P></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><I>$</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>18,029</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><I>$</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>25,679</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><I>$</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>55,234</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><I>$</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>80,231</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD></TR>
<TR BGCOLOR="#cceeff" STYLE="font-family:Times New Roman; font-size:10pt">
<TD VALIGN="top"> <P STYLE="margin-left:1.00em; text-indent:-1.00em; font-size:10pt; font-family:Times New Roman"><I>Europe, Middle East, and Africa (EMEA)</I></P></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><I>&nbsp;</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>5,106</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><I>&nbsp;</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>5,082</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><I>&nbsp;</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>15,880</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><I>&nbsp;</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>17,675</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD></TR>
<TR STYLE="font-family:Times New Roman; font-size:10pt">
<TD VALIGN="top"> <P STYLE="margin-left:1.00em; text-indent:-1.00em; font-size:10pt; font-family:Times New Roman"><I>Asia Pacific and others</I></P></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><I>&nbsp;</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>1,134</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><I>&nbsp;</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>1,530</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><I>&nbsp;</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>3,754</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><I>&nbsp;</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>4,205</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD></TR>
<TR STYLE="font-size:1px; ">
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD>&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD>&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD>&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD>&nbsp;</TD></TR>
<TR BGCOLOR="#cceeff" STYLE="font-family:Times New Roman; font-size:10pt">
<TD VALIGN="top"></TD>
<TD VALIGN="bottom"><FONT STYLE="font-size:8pt">&nbsp;&nbsp;</FONT></TD>
<TD VALIGN="bottom"><I>$</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>24,269</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD>
<TD VALIGN="bottom"><FONT STYLE="font-size:8pt">&nbsp;&nbsp;</FONT></TD>
<TD VALIGN="bottom"><I>$</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>32,291</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD>
<TD VALIGN="bottom"><FONT STYLE="font-size:8pt">&nbsp;&nbsp;</FONT></TD>
<TD VALIGN="bottom"><I>$</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>74,868</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD>
<TD VALIGN="bottom"><FONT STYLE="font-size:8pt">&nbsp;&nbsp;</FONT></TD>
<TD VALIGN="bottom"><I>$</I></TD>
<TD VALIGN="bottom" ALIGN="right"><I>102,111</I></TD>
<TD NOWRAP VALIGN="bottom"><I>&nbsp;&nbsp;</I></TD></TR>
<TR STYLE="font-size:1px; ">
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"> <P STYLE="border-top:3.00px double #000000">&nbsp;</P></TD>
<TD VALIGN="bottom"> <P STYLE="border-top:3.00px double #000000">&nbsp;</P></TD>
<TD>&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"> <P STYLE="border-top:3.00px double #000000">&nbsp;</P></TD>
<TD VALIGN="bottom"> <P STYLE="border-top:3.00px double #000000">&nbsp;</P></TD>
<TD>&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"> <P STYLE="border-top:3.00px double #000000">&nbsp;</P></TD>
<TD VALIGN="bottom"> <P STYLE="border-top:3.00px double #000000">&nbsp;</P></TD>
<TD>&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"> <P STYLE="border-top:3.00px double #000000">&nbsp;</P></TD>
<TD VALIGN="bottom"> <P STYLE="border-top:3.00px double #000000">&nbsp;</P></TD>
<TD>&nbsp;</TD></TR>
</TABLE> <P STYLE="font-size:12pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%" VALIGN="top" ALIGN="left"><I>(1)</I></TD>
<TD ALIGN="left" VALIGN="top"><I>Approximately 95% and 97% of the North America revenue in the three and nine months ended September&nbsp;30, 2014 and 2013, respectively, is attributed to the United States.&#148; </I></TD></TR></TABLE>

<p Style='page-break-before:always'>
<HR  SIZE="3" style="COLOR:#999999" WIDTH="100%" ALIGN="CENTER">

 <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Form 10-Q for the quarterly period ended June&nbsp;30, 2014 </U></I></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Condensed Consolidated Financial Statements </U></I></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Note 1. Summary of Significant Accounting Policies </U></I></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Revenue Recognition, page 8 </U></I></P> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%">&nbsp;</TD>
<TD WIDTH="4%" VALIGN="top" ALIGN="left"><I>2.</I></TD>
<TD ALIGN="left" VALIGN="top"><I>We note your disclosures throughout your filing regarding the transition from perpetual licenses to a subscription model. Please explain what you mean by &#147;subscription model&#148; and tell us more about your
subscription agreements. In this regard, it is unclear to us whether the subscription model includes term licenses, software-as-a service or something else. Given this change in your business model please tell us how your current revenue recognition
policy reflects your new offerings and how they are accounted for. </I></TD></TR></TABLE> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>We respectfully advise the Staff that by
&#147;subscription model&#148; we are referring to time-based licensing arrangements whereby the customer is licensing our products for use only during a specific timeframe. After the expiration of such timeframe, they no longer have the ability to
use the product, unless they choose to renew the subscription license. These subscription licenses can come in one of two forms, either as a hosted software as a service (SAAS) offering, whereby Actuate hosts the software on our servers for the
benefit of the customer, or as an &#147;on-premise&#148; subscription, where the customer installs and maintains the software on their own servers. The large majority of our subscription licenses sold are of the latter, on-premise variety. For SAAS
and on-premise subscriptions, the revenue is recognized as follows:</B> </P> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="14%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><B>&#149;</B></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><B></B><B>SAAS revenue is recognized ratably over the term of the SAAS subscription arrangement. The full fee is recognized in the services revenue line on the income statement. This is due to the fact that Actuate is
providing a service element to the customer by hosting the software and we are unable to establish VSOE for the hosted element of the transaction. Therefore, we are unable to break out the total fee into the separate elements of license,
maintenance, and hosting services and are forced to record the entire amount in services revenue. </B></TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="14%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><B>&#149;</B></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><B>In the case of on-premise subscriptions, we only have two elements, license and maintenance. We are able to break down the total transaction into these two discreet elements. Consequently, on-premise subscription
license revenue is recognized on the license revenue line of the income statement while the maintenance component is recognized in the services revenue line. The maintenance component is recognized ratably over the term of the maintenance
arrangement. The license component is typically recognized ratably over the term of the subscription license in cases where we are unable to establish VSOE for the maintenance element. However, in certain instances, if we are able to establish VSOE
and satisfy the stringent criteria governing time based licenses, (including those stipulated in Technical Practice Aid 5100.54 entitled &#147;Fair Value of PCS in a multi-year time-based license and software revenue recognition&#148;), we may
recognize the license revenue component entirely at the time of contract execution. </B></TD></TR></TABLE> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>We respectfully advise the Staff
that we will enhance our discussion of the accounting treatment for subscription licenses in future filings by replacing the discussion from the &#147;Summary of Significant Accounting Policies&#148; section found at the bottom of Page 8 of our 10-Q
for the period ended June&nbsp;30, 2014, and replacing it with the following:</B> </P> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:17%; font-size:10pt; font-family:Times New Roman"><I>&#147;In addition to licenses sold on a perpetual
basis, Actuate also sells its products on a time-based arrangement. In these time-based licensing arrangements, the customer is licensing our products for use only during a specific timeframe. After the expiration of such timeframe, they no longer
have the ability to use the product, unless they choose to renew the subscription license. The time-based licenses are sold either as on-premise, time-based offerings or as hosted Software-as-a-Service (SaaS) offerings. The on-premise subscription
transactions are broken down into separate license and maintenance components. The license component is typically recognized ratably over the term of the underlying arrangement as license revenue while the maintenance component is recognized ratably
over the term of the underlying arrangement in services revenue in the Company&#146;s Condensed Consolidated Statement of Operations. In certain instances, if we are able to establish VSOE and satisfy the stringent criteria governing time based
licenses, we may recognize the license revenue component of these on-premise subscriptions entirely at the time of contract execution. </I></P>
 <p STYLE="margin-top:0pt;margin-bottom:0pt ; font-size:8pt">&nbsp;</P> <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman" ALIGN="center">2 </P>


<p Style='page-break-before:always'>
<HR  SIZE="3" style="COLOR:#999999" WIDTH="100%" ALIGN="CENTER">

 <P STYLE="margin-top:0pt; margin-bottom:0pt; margin-left:17%; font-size:10pt; font-family:Times New Roman"><I>In our SaaS Subscriptions, Actuate hosts and maintains the software on behalf of the
customer. Actuate recognizes revenue on these licenses ratably over the term of the underlying arrangement. Revenues from Actuate&#146;s SaaS offerings are reported as services revenue in the Company&#146;s Condensed Consolidated Statement of
Operations.&#148; </I></P> <P STYLE="margin-top:18pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Note 6. Goodwill and Other Purchased Intangible Assets, page 17 </U></I></P>
<P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%">&nbsp;</TD>
<TD WIDTH="4%" VALIGN="top" ALIGN="left"><I>3.</I></TD>
<TD ALIGN="left" VALIGN="top"><I>We note your disclosure that there have been no significant events or circumstances that may have impacted the valuation of goodwill subsequent to the assessment performed on October&nbsp;1, 2013. Please tell us how
you considered the following when making this determination: </I></TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="14%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><I>&#149;</I></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><I>There has been a significant decline in your market capitalization as a result of the decline in the fair value of your common stock. In this regard, we note that your stock price was $7.41 on October&nbsp;1, 2013
compared to $4.77 as of June&nbsp;30, 2014. </I></TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="14%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><I>&#149;</I></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><I>The decline in license and maintenance revenue as well as the fact that you operated at a loss in the three and six-months ended June&nbsp;30, 2014. </I></TD></TR></TABLE>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>We respectfully advise the Staff that our statement indicating that there had been no significant events or circumstances affecting the
valuation of goodwill was based on the guidance listed in the FASB Codification. The applicable sections of the Codification stipulate the following:</B> </P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:21%; font-size:10pt; font-family:Times New Roman"><B><I><U>Step One</U> </I></B></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:21%; font-size:10pt; font-family:Times New Roman"><B><I>350-20-35-4 The first step of the goodwill impairment test, used to identify potential impairment, compares the fair value of a
reporting unit with its carrying amount, including goodwill. </I></B></P> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:21%; font-size:10pt; font-family:Times New Roman"><B><I>350-20-35-5 The guidance in paragraphs 350-20-35-22 through
35-24 shall be considered in determining the fair value of a reporting unit. </I></B></P> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:21%; font-size:10pt; font-family:Times New Roman"><B><I>350-20-35-6 If the fair value of a reporting
unit exceeds its carrying amount, goodwill of the reporting unit is considered not impaired, thus the second step of the impairment test is unnecessary. </I></B></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:21%; font-size:10pt; font-family:Times New Roman"><B><I>350-20-35-8 If the carrying amount of a reporting unit exceeds its fair value, the second step of the goodwill impairment test shall be
performed to measure the amount of impairment loss, if any. </I></B></P> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:21%; font-size:10pt; font-family:Times New Roman"><B><I><U>Determining the Fair Value of a Reporting Unit</U>
</I></B></P> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:21%; font-size:10pt; font-family:Times New Roman"><B><I>350-20-35-22 The fair value of a reporting unit refers to the price that would be received to sell the unit as a whole in
an orderly transaction between market participants at the measurement date. Quoted market prices in active markets are the best evidence of fair value and shall be used as the basis for the measurement, if available. However, the market price of an
individual equity security (and thus the market capitalization of a reporting unit with publicly traded equity securities) may not be representative of the fair value of the reporting unit as a whole. </I></B></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:21%; font-size:10pt; font-family:Times New Roman"><B><I>350-30-35-14 &#151; An intangible asset that is subject to amortization shall be reviewed for impairment in accordance with the
Impairment or Disposal of Long-Lived Assets Subsections of Subtopic <U>360-10</U> by applying the recognition and measurement provisions in paragraphs <U>360-10-35-17 through 35-35</U>. In accordance with the Impairment or Disposal of
Long&#150;Lived Assets Subsections of Subtopic <U>360-10</U>, an impairment loss shall be recognized if the carrying amount of an intangible asset is not recoverable and its carrying amount exceeds its fair value. After an impairment loss is
recognized, the adjusted carrying amount of the intangible asset shall be its new accounting basis. Subsequent reversal of a previously recognized impairment loss is prohibited. </I></B></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:21%; font-size:10pt; font-family:Times New Roman"><B><I><U>Measurement of an Impairment Loss</U> </I></B></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:21%; font-size:10pt; font-family:Times New Roman"><B><I>360-10-35-17 &#151; An impairment loss shall be recognized only if the carrying amount of a long-lived asset (asset group) is not
recoverable and exceeds its fair value. The carrying amount of a long-lived asset (asset group) is not recoverable if it exceeds the sum of the undiscounted cash flows expected to result from the use and eventual disposition of the asset (asset
group). That assessment shall be based on the carrying amount of the asset (asset group) at the date it is tested for recoverability, whether in use (see paragraph 360-10-35-33) or under development (see paragraph 360-10-35-34). An impairment loss
shall be measured as the amount by which the carrying amount of a long-lived asset (asset group) exceeds its fair value. </I></B></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:21%; font-size:10pt; font-family:Times New Roman"><B><I>360-10-35-21 A long-lived asset (asset group) shall be tested for recoverability whenever events or changes in circumstances indicate
that its carrying amount may not be recoverable. The following are examples of such events or changes in circumstances: </I></B></P> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="21%">&nbsp;</TD>
<TD WIDTH="5%" VALIGN="top" ALIGN="left"><B><I>a.</I></B></TD>
<TD ALIGN="left" VALIGN="top"><B><I>A significant decrease in the market price of a long-lived asset (asset group) </I></B></TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="21%">&nbsp;</TD>
<TD WIDTH="5%" VALIGN="top" ALIGN="left"><B><I>b.</I></B></TD>
<TD ALIGN="left" VALIGN="top"><B><I>A significant adverse change in the extent or manner in which a long-lived asset (asset group) is being used or in its physical condition </I></B></TD></TR></TABLE>
 <p STYLE="margin-top:0pt;margin-bottom:0pt ; font-size:8pt">&nbsp;</P> <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman" ALIGN="center">3 </P>


<p Style='page-break-before:always'>
<HR  SIZE="3" style="COLOR:#999999" WIDTH="100%" ALIGN="CENTER">


<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="21%">&nbsp;</TD>
<TD WIDTH="5%" VALIGN="top" ALIGN="left"><B><I>c.</I></B></TD>
<TD ALIGN="left" VALIGN="top"><B><I>A significant adverse change in legal factors or in the business climate that could affect the value of a long-lived asset (asset group), including an adverse action or assessment by a regulator
</I></B></TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="21%">&nbsp;</TD>
<TD WIDTH="5%" VALIGN="top" ALIGN="left"><B><I>d.</I></B></TD>
<TD ALIGN="left" VALIGN="top"><B><I>An accumulation of costs significantly in excess of the amount originally expected for the acquisition or construction of a long-lived asset (asset group) </I></B></TD></TR></TABLE>
<P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="21%">&nbsp;</TD>
<TD WIDTH="5%" VALIGN="top" ALIGN="left"><B><I>e.</I></B></TD>
<TD ALIGN="left" VALIGN="top"><B><I>A current-period operating or cash flow loss combined with a history of operating or cash flow losses or a projection or forecast that demonstrates continuing losses associated with the use of a long-lived asset
(asset group) </I></B></TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="21%">&nbsp;</TD>
<TD WIDTH="5%" VALIGN="top" ALIGN="left"><B><I>f.</I></B></TD>
<TD ALIGN="left" VALIGN="top"><B><I>A current expectation that, more likely than not, a long-lived asset (asset group) will be sold or otherwise disposed of significantly before the end of its previously estimated useful life. The term more likely
than not refers to a level of likelihood that is more than 50 percent. </I></B></TD></TR></TABLE> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>Based on this guidance, as part of our
Goodwill impairment review performed in October 2013, we determined that at that time the fair value of Actuate (based on the quoted market price) significantly exceeded its carrying value, including goodwill. At that time we had also performed a
supplemental analysis to determine the market price at which our carrying value would equal the fair value of the Company. Based on our calculation, we determined that the Company&#146;s fair value would equal its carrying value when the quoted
stock market price was approximately $2.69 per share. Although our stock has decreased significantly over the past 9 months since that calculation was made, at no time has the stock price come close to dropping below that threshold. We further
advise the Staff that in October 2014 we completed our Goodwill impairment testing for the current year and have determined that the fair value of the company continues to exceed its carrying value, although admittedly by a narrower margin than seen
in prior years. As of October&nbsp;1, 2014 the Company&#146;s fair value based on the quoted stock market price was approximately $185.2 M, compared to its carrying value of $113.8 M.</B> </P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>In regards to the broader category of definite lived intangibles, we respectfully advise the Staff that management reviewed the balances of
our definite-lived intangible assets (which include Purchased Technology, Customer Lists, and Leases) internally. It is important to note that the balances are related to our Content Services and Analytics technologies. Both of these technologies
remain an integral part of our sales strategy going forward and are expected to continue to drive significant revenues for the Company in the future. Based largely on these factors, Management has concluded that the fair value of our current
intangible balances exceeds the carrying value and is recoverable. </B></P> <P STYLE="margin-top:18pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Note 8. Deferred Revenue, page 23 </U></I></P>
<P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%">&nbsp;</TD>
<TD WIDTH="4%" VALIGN="top" ALIGN="left"><I>4.</I></TD>
<TD ALIGN="left" VALIGN="top"><I>Please explain the decrease in deferred revenue between December&nbsp;31, 2013 and June&nbsp;30, 2014. In this regard, tell us why there was a decrease in deferred revenue considering that your maintenance renewal
rate is in excess of 90% and your new revenue model appears to require prepayment of subscription fees. </I></TD></TR></TABLE> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>We
respectfully advise the Staff that there are many variables that affect the deferred revenue balances of the Company at the end of any particular period. The maintenance renewal rate and the prepayment of subscriptions are only two factors among
many. In reality, to date, subscriptions have had little effect on the deferred revenue balance due to the fact that the transition is still very much in its early stages and therefore remains a very small percentage of the overall deferred balance.
Maintenance, however, is the major component of the deferred revenue balance and changes in that area of business directly and significantly affect the overall deferred revenue balance. It is important to remember, however, that the renewal rate is
only one of many significant factors to keep in mind when analyzing the maintenance deferred revenue. Some of the other major factors that affected the decrease in deferred revenue from 12/31/13 to 6/30/14 include the following: </B></P>
<P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="14%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><B>&#149;</B></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"> <P ALIGN="left" STYLE="font-family:Times New Roman; font-size:10pt"><B>Seasonal impact of maintenance renewal bookings &#150; from a historical perspective, it is not unusual for the Company to experience a significant
drop in the deferred revenue balance from the end of the fourth quarter to the end of the second quarter. In prior years we have typically seen decreases of 5-7% in the deferred balance during this period. The reason for the decrease is principally
due to the fact that the fourth quarter tends to have the highest amount of maintenance renewal bookings and billings of all our fiscal quarters. As those bookings amortize over the next
</B></P></TD></TR></TABLE>
 <p STYLE="margin-top:0pt;margin-bottom:0pt ; font-size:8pt">&nbsp;</P> <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman" ALIGN="center">4 </P>


<p Style='page-break-before:always'>
<HR  SIZE="3" style="COLOR:#999999" WIDTH="100%" ALIGN="CENTER">


<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="17%">&nbsp;</TD>
<TD VALIGN="top"> <P STYLE="font-family:Times New Roman; font-size:10pt"><B>
twelve months we experience an overall decline in the balance throughout the year. The maintenance bookings in Q4 tend to be higher than other quarters partly due to the fact that many customers
tend to synchronize their maintenance agreements to coincide with the end of the calendar year. Also, Q4 tends to have overall higher license sales, which contribute to the maintenance balances attributable to that period. </B></P></TD></TR></TABLE>
<P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="14%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left">&#149;</TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><B>Timing of maintenance renewals &#150; The timing of when a particular maintenance renewal booking is made also has a significant impact on the deferred revenue balance. The amount of &#147;pull-forwards&#148;
experienced in any particular quarter is highly variable. A pull-forward refers to an instance where the Company secured and booked a maintenance renewal order in a quarter preceding the quarter in which the current maintenance renewal term expires.
Pull-forwards have a direct impact on deferred revenue but there is no revenue taken in the period in which they are booked, because the start date has not yet occurred. Actuate experienced a high volume of pull-forwards in the fourth quarter of
2014 as compared to those seen in the quarter ended 6/30/14. These Q4 pull forwards tended to inflate the deferred revenue balance at the end of Q4. If these maintenance renewals were booked in the period in which they began, the deferred revenue
balance would have been much lower at 12/31/13. We believe that the high level of pull forwards experienced in the fourth quarter were caused primarily by the following two factors:</B> </TD></TR></TABLE>
<P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="23%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><B>&#149;</B></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><B></B><B>Incentive plans tend to end at the end of the fiscal year and are largely based on bookings volume. Therefore, our Maintenance Renewal reps are incented to pull-forward as many renewal orders as possible
toward the end of the fiscal year. </B></TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="23%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><B>&#149;</B></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><B></B><B>Customers tend to prefer renewal terms that start on the first day of the fiscal year and tend to co-term their maintenance renewals towards that date. Therefore, there is a much larger number of renewal
orders that begin on the first day of Q1 than at the beginning of any other quarter. These early-quarter renewals are much more likely to be pulled-forward. </B></TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="14%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left">&#149;</TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><B>Declines &#150; The deferred revenue balance would have decreased for any maintenance renewal terms that expired in the first 6 months of 2014 and were not renewed for the prospective year. As you pointed out, we
reported that we experienced a decline rate of approximately 10% during the first 6 months of 2014.</B> </TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="14%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left">&#149;</TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><B>First Year Maintenance &#150; offsetting the decreases to the deferred revenue would be the first year maintenance added for any new license transactions secured in the first 6 months of 2014. Any new license
transactions booked in that period would serve to increase the deferred revenue balance by an amount equal to any maintenance tied to that license order.</B> </TD></TR></TABLE>
<P STYLE="margin-top:18pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Management&#146;s Discussion and Analysis of Financial Condition and Results of Operations </U></I></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Overview, page 24 </U></I></P> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%">&nbsp;</TD>
<TD WIDTH="4%" VALIGN="top" ALIGN="left"><I>5.</I></TD>
<TD ALIGN="left" VALIGN="top"><I>Please consider expanding your overview in future filings to include a more detailed assessment of whether the trends and uncertainties of transitioning from your legacy product suite to your new product offerings
will have, or are reasonably likely to have, a material impact on the company&#146;s liquidity, capital resources or results of operations. See Item&nbsp;303 of Regulation S-K. For additional guidance, consider Section III of SEC Release
No.&nbsp;33-8350. </I></TD></TR></TABLE> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>We respectfully advise the Staff that we have mentioned our transition from our legacy product
suite to our new Birt iHub product offering repeatedly throughout our recent SEC filings to ensure that the reader is aware of the transition. However, we understand that the Staff would like to see more detailed discussion on the specifics of the
transition. Therefore, in future filings we will augment the current discussion of the subscription transition currently seen on page 24 of our 10-Q filing for the period ended June&nbsp;30, 2014 and replace it with the following language:</B> </P>
 <p STYLE="margin-top:0pt;margin-bottom:0pt ; font-size:8pt">&nbsp;</P> <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman" ALIGN="center">5 </P>


<p Style='page-break-before:always'>
<HR  SIZE="3" style="COLOR:#999999" WIDTH="100%" ALIGN="CENTER">

 <P STYLE="margin-top:0pt; margin-bottom:0pt; margin-left:17%; font-size:10pt; font-family:Times New Roman"><I>&#147;We continue to transition from our legacy e.Reports/iServer product suite to our new
BIRT iHub product offerings. We no longer proactively pursue sales of our legacy e.Reports products and as a consequence we are experiencing a decrease in license revenues generated by our e.Report/iServer products. We expect this decrease to be
mitigated by increases in license revenue generated by our successor BIRT iHub offerings over time. Over time, BIRT iHub is expected to become the dominant contributor to license and maintenance revenues. However, during this transition we may
experience delays in adoption of our BIRT iHub offerings by our customers which can adversely impact our license revenues. As a result of this transition we are experiencing and will likely experience the following effects: </I></P>
<P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="23%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><I>&#149;</I></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><I>License revenues will be adversely affected &#150; As sales of our legacy products decline over the next several periods, it will have a negative impact on total license revenue growth. We expect that total license
revenues derived from our e.Reports products will eventually approach zero over a protracted period of time. </I></TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="23%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><I>&#149;</I></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><I></I><I>Maintenance revenues will be negatively impacted &#150; As existing projects using our legacy products come to their natural end of life, it is likely that those customers will increasingly decline the
maintenance related to those projects. We have already experienced this impact in recent periods and expect to see additional impact in the coming fiscal periods. </I></TD></TR></TABLE>
<P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="23%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><I>&#149;</I></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><I></I><I>Cash balances and operating cash flows will be negatively impacted by the decreased license and maintenance sales associated with our legacy products. </I></TD></TR></TABLE>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:17%; font-size:10pt; font-family:Times New Roman"><I>Because of the impacts noted above, we expect that the transition from our legacy products to our new Birt iHub products will have a
negative impact on the Company&#146;s liquidity, capital resources and results of operations until such time that our sales of the new Birt iHub products rise to such a volume that they serve to compensate for the impact.&#148; </I></P>
<P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%">&nbsp;</TD>
<TD WIDTH="4%" VALIGN="top" ALIGN="left"><I>6.</I></TD>
<TD ALIGN="left" VALIGN="top"><I>We note your disclosures on page 25 regarding transition to a subscription model. Please tell us what consideration was given to disclosing how this transition will occur. In this regard, we note that in your
earnings call transcript you have indicated that subsequent to July&nbsp;1, 2014 new customers will only be able to purchase subscription-based offerings. </I></TD></TR></TABLE>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>We respectfully advise the Staff that we have mentioned our transition to a subscription based model repeatedly throughout our recent SEC
filings to ensure that the reader is aware of the transition. However, we understand that the Staff would like to see more detailed discussion on the specifics of the transition. Therefore, in future filings we will augment the current discussion of
the subscription transition currently seen on page 25 of our 10-Q filing for the period ended June&nbsp;30, 2014 by replacing it with the following language:</B> </P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:17%; font-size:10pt; font-family:Times New Roman"><I>&#147;In the past Actuate priced and sold its products primarily on a perpetual basis. However, we are seeing a shift in customer&#146;s
purchasing behavior for enterprise software. This shift appears to favor a subscription pricing model. Therefore, we recently announced that we were actively transitioning and accelerating our primary pricing model to a subscription model. We
believe that this shift will increase customer product acquisition and will result in smoother, cyclical revenues over the medium-to-long term. Generally speaking, these subscription licenses will be recognized ratably over the subscription service
period. The subscription model provides more flexibility for our customers to use our software and we believe is in line with current market trends. We believe subscription-based license should provide an easier adoption of commercial software for
open source BIRT users and provide our customers&nbsp;with timely access to Actuate&#146;s latest product releases. We are currently in the process of transitioning to this new subscription model. Following are some of the specific guidelines that
we have implemented as part of this transition: </I></P> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="23%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><I>&#149;</I></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><I></I><I>We intend that new sales opportunities identified after July&nbsp;1, 2014 will be sold as subscription licenses. </I></TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="23%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><I>&#149;</I></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><I></I><I>We have adjusted the compensation plans for our sales representatives to incent them to convert perpetual license opportunities identified before July&nbsp;1 to subscription licenses. </I></TD></TR></TABLE>
<P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="23%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><I>&#149;</I></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><I></I><I>All perpetual license offers made prior to July&nbsp;1, 2014 will expire on December&nbsp;31, 2014. If the transaction is concluded prior to that time we will allow the license to be sold on a perpetual basis.
</I></TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="23%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><I>&#149;</I></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><I></I><I>Going forward, existing perpetual license projects will be able to add additional perpetual capacity to existing projects. </I></TD></TR></TABLE>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:17%; font-size:10pt; font-family:Times New Roman"><I>It is our intention to enforce the transition to a subscription model based on the guidelines stipulated above. However, it is likely that
we could have exceptions to this policy in the short term as we undergo the transition. We expect this transition to be substantially complete by 2017. </I></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:17%; font-size:10pt; font-family:Times New Roman"><I>There are several key characteristics that differentiate prospective subscription license models from our prior, perpetual based model.
Some of those characteristics are as follows: </I></P> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="23%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><I>&#149;</I></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><I></I><I>Average selling prices for subscription licenses tend to be considerably lower than perpetual licenses. Consequently, during our conversion to a subscription model we will experience significantly lower
revenues, operating income, and initial cash flows, which will likely adversely affect our cash balances and cash flow from operations for the next several years. </I></TD></TR></TABLE>
<P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="23%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><I>&#149;</I></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><I></I><I>In subscription arrangements the customer does not own the software, but rather is paying for the right to use the software for a specific subscription term. Consequently, subscription licenses tend to be
recurring in nature, whereas perpetual licenses are not, as the customer purchases the software outright. Due to their ratable treatment, the transition to a subscription model may result in net operating losses or lower net profits in future
periods. </I></TD></TR></TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="23%">&nbsp;</TD>
<TD WIDTH="2%" VALIGN="top" ALIGN="left"><I>&#149;</I></TD>
<TD WIDTH="1%" VALIGN="top">&nbsp;</TD>
<TD ALIGN="left" VALIGN="top"><I></I><I>Subscription revenue going forward is expected to be usually taken ratably over the subscription period, whereas perpetual licenses were usually taken up front. Consequently, we have seen and expect to
continue to see a marked decline in our license revenue for the next several years. </I></TD></TR></TABLE> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:17%; font-size:10pt; font-family:Times New Roman"><I>Because of the impacts noted
above, we expect that the transition from our perpetual sales model to our new subscription licensing model will have a negative impact on the Company&#146;s cash flows, liquidity, capital resources and results of operations until such time that our
sales of the new subscription licenses rise to such a volume that they serve to compensate for the impact.&#148; </I></P> <P STYLE="font-size:6pt; margin-top:0pt; margin-bottom:0pt">&nbsp;</P>
 <p STYLE="margin-top:0pt;margin-bottom:0pt ; font-size:8pt">&nbsp;</P> <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman" ALIGN="center">6 </P>


<p Style='page-break-before:always'>
<HR  SIZE="3" style="COLOR:#999999" WIDTH="100%" ALIGN="CENTER">


<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%">&nbsp;</TD>
<TD WIDTH="4%" VALIGN="top" ALIGN="left"><I>7.</I></TD>
<TD ALIGN="left" VALIGN="top"><I>In addition, we note discussion on page 41 that you are determining new metrics to gauge the status of your business model transition. Please consider disclosing these metrics in future filings.
</I></TD></TR></TABLE> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>We respectfully advise the Staff that we are still evaluating and calculating the metrics related to our new
subscription model. We intend to incorporate reporting of any new metrics into our 10-K filing for the period ended December&nbsp;31, 2014.</B> </P>
<P STYLE="margin-top:18pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Results of Operations </U></I></P> <P STYLE="margin-top:6pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Revenues, page 28
</U></I></P> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%">&nbsp;</TD>
<TD WIDTH="4%" VALIGN="top" ALIGN="left"><I>8.</I></TD>
<TD ALIGN="left" VALIGN="top"><I>Considering the transition from perpetual license to a subscription model, tell us what consideration was given to separately disclosing the amounts of revenue for products and services based on whether the revenue
arose from perpetual license sales or from your new subscription model. </I></TD></TR></TABLE> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>We respectfully advise the Staff that we have
given extensive and thorough consideration to separately disclosing the amounts of revenue for product and services based on whether the revenue arose from perpetual license sales or from recurring streams, such as subscriptions. We have determined
that it would be useful to the investor community to present the revenue in that way. Consequently, we intend to inform the investor community that we will be changing the classification of revenue on the face of our Income Statement to better
reflect this new view. The new classification categories that we intend to show on the income statement will be as follows:</B> </P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:17%; font-size:10pt; font-family:Times New Roman"><I>License Revenue &#150; includes revenue related to perpetual licenses and other licenses not expected to recur </I></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:17%; font-size:10pt; font-family:Times New Roman"><I>Recurring Revenue &#150; includes all revenue that is expected to recur, including all maintenance, on-premises subscription revenue and
Saas Revenue </I></P> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:17%; font-size:10pt; font-family:Times New Roman"><I>Professional Services/Training Revenue </I></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>We intend to begin showing the new classification beginning with our 10-K filing for the period ended December&nbsp;31, 2014. Although a
great deal of time and effort has already been invested in order to recast the revenue numbers for the past 5 years into this new view, we are still in the process of finalizing those numbers.</B> </P>
<P STYLE="margin-top:18pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman"><I><U>Forms 8-K furnished on August&nbsp;6, 2014,&nbsp;May&nbsp;1, 2014 and February&nbsp;4, 2014 </U></I></P>
<P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%">&nbsp;</TD>
<TD WIDTH="4%" VALIGN="top" ALIGN="left"><I>9.</I></TD>
<TD ALIGN="left" VALIGN="top"><I>We note that you adjust GAAP diluted shares for what the &#147;share amounts would have been if they were calculated using non-GAAP results.&#148; Please explain the nature of the adjustments made to arrive at
non-GAAP diluted shares and tell us what consideration was given to providing a reconciliation from GAAP to non-GAAP diluted shares. See Item&nbsp;101(a) of Regulation G. </I></TD></TR></TABLE>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>We respectfully advise the Staff that the Company makes two different adjustments to GAAP diluted net shares in any particular quarter in
order to calculate the number of Non-GAAP diluted shares.</B> </P> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:8%; font-size:10pt; font-family:Times New Roman"><B>The following table represents the adjustment from GAAP diluted to
non-GAAP diluted shares for the periods referenced in your inquiry:</B> </P> <P STYLE="font-size:12pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="84%" BORDER="0" STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" ALIGN="center">


<TR>
<TD WIDTH="76%"></TD>
<TD VALIGN="bottom" WIDTH="3%"></TD>
<TD></TD>
<TD></TD>
<TD></TD>
<TD VALIGN="bottom" WIDTH="3%"></TD>
<TD></TD>
<TD></TD>
<TD></TD>
<TD VALIGN="bottom" WIDTH="3%"></TD>
<TD></TD>
<TD></TD>
<TD></TD></TR>
<TR STYLE="font-family:Times New Roman; font-size:8pt">
<TD VALIGN="bottom" NOWRAP> <P STYLE="border-bottom:1.00pt solid #000000; width:45.90pt; font-size:8pt; font-family:Times New Roman">(In thousands)</P></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom" COLSPAN="2" ALIGN="center" STYLE="border-bottom:1.00pt solid #000000">Q2-14</TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom" COLSPAN="2" ALIGN="center" STYLE="border-bottom:1.00pt solid #000000">Q1-14</TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom" COLSPAN="2" ALIGN="center" STYLE="border-bottom:1.00pt solid #000000">Q4-13</TD>
<TD VALIGN="bottom">&nbsp;</TD></TR>


<TR BGCOLOR="#cceeff" STYLE="font-family:Times New Roman; font-size:10pt">
<TD VALIGN="top"> <P STYLE="margin-left:1.00em; text-indent:-1.00em; font-size:10pt; font-family:Times New Roman">Shares used in GAAP diluted per share calculation (a)</P></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom" ALIGN="right">46,692</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom" ALIGN="right">47,699</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom" ALIGN="right">51,360</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;&nbsp;</TD></TR>
<TR STYLE="font-family:Times New Roman; font-size:10pt">
<TD VALIGN="top"> <P STYLE="margin-left:1.00em; text-indent:-1.00em; font-size:10pt; font-family:Times New Roman"><U>Adjustment 1</U>: Dilutive potential common shares</P></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom" ALIGN="right">1,069</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;</TD>
<TD NOWRAP VALIGN="bottom" ALIGN="right">&#151;&nbsp;&nbsp;</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;</TD>
<TD NOWRAP VALIGN="bottom" ALIGN="right">&#151;&nbsp;&nbsp;</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;&nbsp;</TD></TR>
<TR BGCOLOR="#cceeff" STYLE="font-family:Times New Roman; font-size:10pt">
<TD VALIGN="top"> <P STYLE="margin-left:1.00em; text-indent:-1.00em; font-size:10pt; font-family:Times New Roman"><U>Adjustment 2</U>: Unamortized SBC expense shares (add-back)</P></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom" ALIGN="right">243</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;</TD>
<TD NOWRAP VALIGN="bottom" ALIGN="right">&#151;&nbsp;&nbsp;</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom" ALIGN="right">635</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;&nbsp;</TD></TR>
<TR STYLE="font-size:1px; ">
<TD VALIGN="bottom"></TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD>&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD>&nbsp;</TD>
<TD VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD VALIGN="bottom"> <P STYLE="border-top:1.00px solid #000000">&nbsp;</P></TD>
<TD>&nbsp;</TD></TR>
<TR STYLE="font-family:Times New Roman; font-size:10pt">
<TD VALIGN="top"> <P STYLE="margin-left:1.00em; text-indent:-1.00em; font-size:10pt; font-family:Times New Roman">Shares used in non-GAAP diluted per share calculation (b)</P></TD>
<TD VALIGN="bottom"><FONT STYLE="font-size:8pt">&nbsp;&nbsp;</FONT></TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom" ALIGN="right">48,004</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><FONT STYLE="font-size:8pt">&nbsp;&nbsp;</FONT></TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom" ALIGN="right">47,699</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;&nbsp;</TD>
<TD VALIGN="bottom"><FONT STYLE="font-size:8pt">&nbsp;&nbsp;</FONT></TD>
<TD VALIGN="bottom">&nbsp;</TD>
<TD VALIGN="bottom" ALIGN="right">51,995</TD>
<TD NOWRAP VALIGN="bottom">&nbsp;&nbsp;</TD></TR>
</TABLE> <P STYLE="font-size:6pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%" VALIGN="top" ALIGN="left">(a)</TD>
<TD ALIGN="left" VALIGN="top">The Company reported GAAP net losses in the first quarter and the second quarters of Fiscal 2014. As a result, diluted shares reported under GAAP were equal to basic shares outstanding. In accordance with ASC
260-10-55-3B, potential common shares were excluded from diluted shares in computation of GAAP diluted EPS, because to do so would be anitdilutive. </TD></TR></TABLE>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%" VALIGN="top" ALIGN="left">(b)</TD>
<TD ALIGN="left" VALIGN="top">The Company reported GAAP and non-GAAP net losses during the first quarter of 2014. Potential common shares were excluded from GAPP and non-GAAP diluted shares in computation of diluted EPS, because to do so would be
anitdiultive. </TD></TR></TABLE>
 <p STYLE="margin-top:0pt;margin-bottom:0pt ; font-size:8pt">&nbsp;</P> <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman" ALIGN="center">7 </P>


<p Style='page-break-before:always'>
<HR  SIZE="3" style="COLOR:#999999" WIDTH="100%" ALIGN="CENTER">

 <P STYLE="margin-top:0pt; margin-bottom:0pt; margin-left:13%; font-size:10pt; font-family:Times New Roman"><B><U>Adjustment 1: Dilutive potential common shares</U> </B></P>
<P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:13%; font-size:10pt; font-family:Times New Roman"><B>The Company applies the treasury stock method, using the guidance provided in ASC 260-10-45-16, &#147;</B><B><I>Earnings Per Share
(EPS)</I></B><B>&#148;, for calculating its GAAP diluted shares outstanding. The Company increases its GAAP basic shares outstanding by the number of additional common shares that would have been outstanding if the dilutive potential common shares
had been issued (&#147;Common Share Equivalents&#148;). These potential common shares are only added if doing so would prove to be dilutive. In cases where GAAP and non-GAAP results are either both profitable or both unprofitable, no adjustment to
GAAP dilutive shares is necessary to arrive at a non-GAAP dilutive share total. However, in cases where our GAAP results are unprofitable and non-GAAP results are profitable an adjustment is necessary. This is because GAAP basic shares and GAAP
fully diluted shares are identical when in a loss position as any addback of potential common shares would be anti-dilutive. However, since the pro-forma results are profitable the potential shares would be dilutive and therefore should be added
back to non-GAAP basic shares in order to arrive at total Non-GAAP diluted shares. </B></P> <P STYLE="margin-top:18pt; margin-bottom:0pt; margin-left:13%; font-size:10pt; font-family:Times New Roman"><B><U>Adjustment 2: Unamortized SBC expense
shares (add-back)</U></B> </P> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:13%; font-size:10pt; font-family:Times New Roman"><B>The guidelines set forth in the FASB codification stipulate that an adjustment should be made to GAAP
diluted shares to add-back common share equivalents associated with unamortized share-based compensation (&#147;SBC&#148;) expense. This add-back is related to stock compensation costs attributed to future services that are not yet recognized. Since
those shares are not yet &#147;earned&#148; the FASB mandates that we reduce the number of outstanding shares attributable to these unamortized share based expenses. In other words, under the treasury stock method these unamortized expenses are
considered to be an additional source of proceeds that the Company can use to repurchase its own stock from the pool of outstanding shares. As a result of this adjustment, GAAP diluted shares outstanding are <U>reduced</U> by utilizing these
potential proceeds. </B></P> <P STYLE="margin-top:6pt; margin-bottom:0pt; margin-left:13%; font-size:10pt; font-family:Times New Roman"><B>Conversely, for non-GAAP reporting, the Company adds back the equivalent shares associated with unamortized
SBC expense to its GAAP diluted share amount. The reason for this <U>increase</U> or add-back is because SBC expense is excluded from the Company&#146;s non-GAAP operating results (the numerator in the EPS formula) in arriving at non-GAAP EPS.
Accordingly, the potential buy-back benefit associated with these unamortized SBC shares as reflected in the GAAP diluted share amount is also excluded from the calculation of non-GAAP EPS (the denominator in the EPS formula). By adding the
equivalent shares associated with the unamortized SBC expense to the GAAP diluted shares, the Company properly aligns the impact of SBC expense in both the numerator and the denominator of its non-GAAP EPS.</B> </P>
<P STYLE="margin-top:12pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">Should you have any further questions, please do not hesitate to call me at (650)&nbsp;645-3494. </P>
<P STYLE="margin-top:12pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">Sincerely, </P> <P STYLE="margin-top:12pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">/s/ Daniel Gaudreau </P>
<P STYLE="line-height:3.0pt;margin-top:0pt;margin-bottom:2pt;border-bottom:1px solid #000000;width:31%">&nbsp;</P> <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">Daniel Gaudreau </P>
<P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman">Senior Vice President, Operations and Chief Financial Officer </P> <P STYLE="font-size:12pt;margin-top:0pt;margin-bottom:0pt">&nbsp;</P>
<TABLE STYLE="BORDER-COLLAPSE:COLLAPSE; font-family:Times New Roman; font-size:10pt" BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="100%">
<TR>
<TD WIDTH="4%" VALIGN="top" ALIGN="left">cc:</TD>
<TD ALIGN="left" VALIGN="top">Ms.&nbsp;Tamara Tangen, Staff Accountant, Division of Corporate Finance </TD></TR></TABLE> <P STYLE="margin-top:0pt; margin-bottom:0pt; margin-left:4%; font-size:10pt; font-family:Times New Roman">Ms.&nbsp;Christine
Davis, Assistant Chief Accountant, Division of Corporate Finance </P>
 <p STYLE="margin-top:0pt;margin-bottom:0pt ; font-size:8pt">&nbsp;</P> <P STYLE="margin-top:0pt; margin-bottom:0pt; font-size:10pt; font-family:Times New Roman" ALIGN="center">8 </P>

</BODY></HTML>
</TEXT>
</DOCUMENT>
</SEC-DOCUMENT>
