16.09.2015 Views

The Importance of Channel Data Integrity - Zyme Solutions

Zyme Solutions integrate channel data and program performance data to provide clean, validated and actionable knowledge in simple dashboards and within Salesforce.com to help executives make enterprise-grade decisions. See more at: http://www.zyme.com/solutions/applications-api-s-and-integration

Zyme Solutions integrate channel data and program performance data to provide clean, validated and actionable knowledge in simple dashboards and within Salesforce.com to help executives make enterprise-grade decisions. See more at: http://www.zyme.com/solutions/applications-api-s-and-integration

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Revenue Recognition Challenges in the High-tech<br />

Industry: <strong>The</strong> <strong>Importance</strong> <strong>of</strong> <strong>Channel</strong> <strong>Data</strong> <strong>Integrity</strong><br />

A White Paper by<br />

<strong>Zyme</strong> <strong>Solutions</strong>, Inc.<br />

May 2009<br />

About <strong>Zyme</strong><br />

<strong>Zyme</strong> is the leading provider <strong>of</strong> hosted channel data integrity services for global technology companies<br />

that sell through indirect channels. On behalf <strong>of</strong> these companies, <strong>Zyme</strong> processes and validates millions<br />

<strong>of</strong> private point-<strong>of</strong>-sale and inventory transactions each week from nearly 2,000 distribution and retail<br />

channel partners in 175 countries. <strong>Zyme</strong> supports its customers with verified channel sales and inventory<br />

data for mission-critical business processes such as revenue recognition, SOX compliance, incentive and<br />

rebate payments, sales commissioning, and supply chain planning. <strong>Zyme</strong> serves clients through a unique<br />

Service-ON-S<strong>of</strong>tware <strong>of</strong>fering that combines a best-in-class channel data processing s<strong>of</strong>tware platform<br />

with domain-deep analyst teams, earning <strong>Zyme</strong> an unparalleled reputation for value in the industry. For<br />

more information, call 1-877-262-8993 or visit www.zymesolutions.com.


Executive Overview<br />

High-tech companies that sell through indirect channels face many challenges when deciding<br />

on a revenue recognition policy. <strong>The</strong>y must comply with regulations, ensure access to accurate<br />

and timely channel sales data, and maintain robust systems and processes that support<br />

revenue accounting. Company finance departments need to evaluate the pros and cons <strong>of</strong> the<br />

“sales-in” vs. “sales-out” approach for revenue recognition. While the sales-out approach is<br />

considered to be more conservative, and may benefit companies by leading to lower required<br />

reserves, it poses implementation challenges because it is dependent on self-reported<br />

distributor information and lacks because the company lacks control over information accuracy.<br />

Transitioning from a sales-in to a sales-out approach is a significant effort, but one that can be<br />

managed by systematically on-boarding channel partners, consolidating and validating partners’<br />

point-<strong>of</strong>-sale (POS) and inventory data, and using a compliance scorecard to ensure timeliness<br />

and data quality. Partner compliance in providing timely and accurate POS and inventory data<br />

enables companies to perform an accurate reconciliation <strong>of</strong> sales-in vs. sales-out data. Such<br />

data forms the basis <strong>of</strong> inventory valuation, while rigorous monitoring <strong>of</strong> variances between<br />

calculated and reported inventory can provide valuable insights.<br />

Background<br />

<strong>The</strong> technology industry has a complex, global, multi-tier distribution channel, and continuous<br />

technological innovation, which drives short product lifecycles and constant price pressure. Due<br />

to the pace <strong>of</strong> technological change, most products are sold with a right <strong>of</strong> return; many hightech<br />

manufacturers also <strong>of</strong>fer some type <strong>of</strong> price protection, ship and debit, or back-end rebate<br />

program based on sales volume.<br />

<strong>The</strong>se industry characteristics make proper revenue recognition a challenge, and one that is<br />

complicated further by the lack <strong>of</strong> timely, complete, and accurate sales and inventory data from<br />

channel partners. Too <strong>of</strong>ten, critical revenue recognition decisions are made without adequate<br />

visibility into channel sales activity, which creates audit and regulatory compliance exposure for<br />

high-tech companies. Improving the accuracy, timeliness, and transparency <strong>of</strong> channel sales<br />

data has therefore become an important objective for finance and sales departments.<br />

Revenue Recognition Policies in the High-Tech Industry<br />

Based on a variety <strong>of</strong> business criteria, including price volatility, product lifecycle, and stock<br />

rotation predictability, high-tech manufacturers must select one <strong>of</strong> two approaches to<br />

recognizing revenue:<br />

1) Sales-in, or “ship-to,” in which revenue is recognized at the time <strong>of</strong> sale by the<br />

manufacturer to the distributor or retailer<br />

2) Sales-out, or “sell-through,” in which revenue is recognized when the product ships from<br />

the distributor to the reseller or end customer


Before discussing the advantages and drawbacks <strong>of</strong> each method, it’s important to examine two<br />

relevant publications: SAB 104, published by the SEC; and FAS 48, published by the Financial<br />

Accounting Standards Board (FASB).<br />

SAB 104: Revenue Recognition<br />

<strong>The</strong> staff believes that revenue generally is realized or realizable and earned when all <strong>of</strong> the<br />

following criteria are met:<br />

• Persuasive evidence <strong>of</strong> an arrangement exists,<br />

• Delivery has occurred or services have been rendered,<br />

• <strong>The</strong> seller's price to the buyer is fixed or determinable, and<br />

• Collectibility is reasonably assured.<br />

FAS 48: Revenue Recognition When the Right <strong>of</strong> Return Exists<br />

If an enterprise sells its product but gives the buyer the right to return the product, revenue<br />

from the sales transaction shall be recognized at time <strong>of</strong> sale only if all <strong>of</strong> the following<br />

conditions are met:<br />

a) <strong>The</strong> seller's price to the buyer is substantially fixed or determinable at the date <strong>of</strong><br />

sale.<br />

b) <strong>The</strong> buyer has paid the seller, or the buyer is obligated to pay the seller and the<br />

obligation is not contingent on resale <strong>of</strong> the product.<br />

c) <strong>The</strong> buyer's obligation to the seller would not be changed in the event <strong>of</strong> theft or<br />

physical destruction or damage <strong>of</strong> the product.<br />

d) <strong>The</strong> buyer acquiring the product for resale has economic substance apart from that<br />

provided by the seller.<br />

e) <strong>The</strong> seller does not have significant obligations for future performance to directly<br />

bring about resale <strong>of</strong> the product by the buyer.<br />

f) <strong>The</strong> amount <strong>of</strong> future returns can be reasonably estimated (paragraph 8).<br />

FAS 48 further states that when companies choose to recognize revenue at the time <strong>of</strong><br />

sale using the ship-to method, the amount <strong>of</strong> future returns must be estimated and<br />

companies must accrue any costs or losses expected from returns.<br />

<strong>The</strong> Sales-in, or Ship-to, Method<br />

In the ship-to model, revenue recognition is triggered by shipments that are typically tracked in<br />

the manufacturer’s ERP system, rather than by data from channel partners. Relying on ship-to<br />

data from internal back-end systems, rather than on sell-through data from external partners,<br />

also means that the timing <strong>of</strong> revenue recognition for any given period can be quick and<br />

straightforward. However, with this approach:<br />

<br />

!


• Companies need to establish a methodology for estimating product returns and to<br />

establish reserves in accordance with FAS 48.<br />

• <strong>The</strong>re may be delays in receiving reported inventory, and reconciling to calculated<br />

inventory may be complex.<br />

• Companies must evaluate whether partner-reported inventory levels are reasonable in<br />

order to ensure that companies’ ability to estimate returns is not impaired.<br />

A ship-to policy may expose companies to risks <strong>of</strong> excess or insufficient reserves for returns,<br />

particularly as trends in returns diverge from the estimates upon which reserves were based.<br />

<strong>The</strong> Sales-out, or Sell-through, Method<br />

<strong>The</strong> sell-through method is considered the more conservative <strong>of</strong> the two revenue recognition<br />

policy options. Because revenue is not recognized until products ship to the end customer,<br />

typically the company does not need to maintain reserves against revenue for estimated<br />

returns. <strong>The</strong> sell-through method does, however, rely on POS and inventory data that is selfreported<br />

by channel partners. <strong>Channel</strong> partners vary widely in their ability and willingness to<br />

report this data in an automated fashion, and reporting standards may vary regionally for<br />

channel partners located around the globe. Given these challenges, this self-reported data may<br />

not be as reliable, accurate, and timely as companies desire for revenue recognition.<br />

Transitioning from a Sales-in to a Sales-out Revenue Recognition Policy<br />

Given the advantages <strong>of</strong> the sales-out revenue recognition model, many companies review their<br />

contractual arrangements with channel partners, such as price protection and return policies,<br />

and determine that a sales-out policy is more appropriate than a sales-in policy. Transitioning to<br />

a sales-out model for revenue recognition poses several challenges and can take between three<br />

and six months.<br />

For example, a common barrier to transitioning to the sales-out model is the lack <strong>of</strong> data from<br />

channel partners in emerging markets such as Asia-Pacific and Latin America. In order to<br />

maximize the number <strong>of</strong> channel partners that report data, it is important to onboard them using<br />

their own systems and tools. While many distributors in these markets do not send data via EDI,<br />

they typically have their own transaction systems that generate invoices, issue purchase orders,<br />

and record sales and inventory positions. Thus, it is worthwhile for companies to set up a<br />

process that can accept channel partner data in a variety <strong>of</strong> formats (including Excel, text, and<br />

XML), sent via e-mail or SFTP.<br />

To facilitate the transition from a sales-in to a sales-out revenue recognition policy and minimize<br />

the audit risks involved, companies can additionally take the following steps:<br />

• Get channel partners on board in a systematic fashion and ensure that channel partners<br />

submit the correct data at the necessary level <strong>of</strong> frequency, accuracy, detail, and<br />

timeliness to meet sell-through revenue recognition requirements.<br />

<br />

"


• Cleanse data to ensure the accuracy <strong>of</strong> date formats, product names, contract<br />

manufacturer names, and end customer names.<br />

• Establish a robust data validation process—including sales-in, sales-out (SISO)<br />

reconciliation and trend analyses—to ensure the accuracy <strong>of</strong> reported quantities and<br />

prices; documenting this process is important for SOX compliance.<br />

• Follow up with partners on a weekly basis to resolve exceptions identified during the<br />

validation process.<br />

• Generate partner compliance scorecards to drive ongoing data quality improvements.<br />

This compliance scorecard should (at minimum) measure whether or not distributors<br />

have reported data on time, accurately, and completely, with no missing fields.<br />

• Apply complex pricing rules to POS and inventory data, using the rules to value<br />

inventory and test POS-based calculations, such as semiconductor special pricing or<br />

ship and debit functionality.<br />

Sales-in, Sales-out (SISO) Reconciliation—A Key Step Toward Sales-out Revenue<br />

Recognition<br />

As mentioned above, reconciling sales-in and sales-out data is an important step in the accurate<br />

valuation <strong>of</strong> channel inventory, which is critical for accurate revenue recognition. Best practices<br />

include:<br />

• Roll-forward assessing <strong>of</strong> channel inventory<br />

• Identifying/monitoring SISO exceptions and flagging them so that analysts can work with<br />

channel partners to reconcile them<br />

• Reviewing trends in calculated vs. partner-reported inventory<br />

• Analyzing the potential causes <strong>of</strong> any variances in calculated vs. partner-reported<br />

inventory<br />

In addition to improving inventory valuation, SISO reconciliation also helps companies make<br />

more accurate price protection payments.<br />

<strong>The</strong> calculated inventory for SISO reconciliation is computed as follows:<br />

Previous week’s calculated inventory<br />

+ Sales-in<br />

– Shipments in transit<br />

– Sales-out (sell-through, POS)<br />

– Returns<br />

– Cross-shipments and other adjustments<br />

= Current week’s calculated inventory<br />

<br />

#


Minimizing Risks in Revenue Recognition<br />

Each <strong>of</strong> the two revenue recognition approaches entails some risks that can lead to overly<br />

conservative or overly aggressive sales and revenue reporting. Companies with a sales-in<br />

policy risk under- or over-estimating reserves, while companies with a sales-out policy are at<br />

risk <strong>of</strong> misstating revenues due to inaccuracies in data reported by channel partners. As<br />

discussed above, to mitigate these risks, technology companies should begin by automating<br />

partner data collection and improving channel data integrity through a robust data consolidation<br />

and validation process.<br />

Once companies are receiving cleansed and validated channel partner data in an automated<br />

manner, they can begin a regular process to reconcile calculated vs. partner-reported inventory<br />

and conduct a trend analysis on the variances. A trend analysis can reveal issues that may<br />

have a material impact on revenue recognition. For example, an increasing positive variance, as<br />

shown in the graph below, may mean either that some POS data is missing altogether (as when<br />

a single warehouse <strong>of</strong> a given distributor consistently fails to report inventory), or it may mean<br />

that certain categories <strong>of</strong> inventory are not being reported (perhaps product masters were not<br />

properly updated).<br />

Figure 1: An increasing positive variance in calculated vs. reported inventory<br />

Conversely, a close convergence between calculated and reported inventory indicates that no<br />

systemic problems exist; therefore, variations are likely due to issues either in the transit time<br />

model or in the timing <strong>of</strong> POS vs. inventory reports.<br />

Figure 2: A close convergence between calculated and reported inventory<br />

<br />

$


Conclusion<br />

While the high-tech industry uses both the sales-in and sales-out revenue recognition policies,<br />

the sales-out approach <strong>of</strong>fers some important advantages: It is seen as more conservative,<br />

revenues are seen as more reflective <strong>of</strong> actual market dynamics, and it enables companies to<br />

decrease reserves against returns. Transitioning from a sales-in to a sales-out approach,<br />

however, can be a challenge. Ensuring accurate, reliable, and timely data from sales channel<br />

partners and establishing a robust SISO reconciliation process are important steps in<br />

addressing this challenge. To minimize risks in revenue recognition, technology companies<br />

should focus on increased automation, improved channel data integrity, and enhanced analysis<br />

<strong>of</strong> channel sales data, no matter what revenue recognition policy they follow.<br />

<br />

<br />

<br />

This document contains proprietary information <strong>of</strong> <strong>Zyme</strong> <strong>Solutions</strong>, Inc., based on the experience and research <strong>of</strong> <strong>Zyme</strong> and its<br />

partners, and may not be reproduced without prior consent from <strong>Zyme</strong> <strong>Solutions</strong>, Inc. While every attempt has been made to ensure<br />

that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. <strong>The</strong><br />

information contained in this document is subject to change without notice. <strong>Zyme</strong> does not accept responsibility for any kind <strong>of</strong> loss<br />

resulting from the use <strong>of</strong> information contained in this document. Further, <strong>Zyme</strong> is not, by means <strong>of</strong> this document, rendering<br />

business, financial, investment, or other pr<strong>of</strong>essional accounting advice or services. Before making any decision or taking any action<br />

that may affect your business, you should consult a qualified pr<strong>of</strong>essional advisor.<br />

<br />

%

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!