|
|
|
|
| 極具爭(zhēng)議 電梯銷售收入何時(shí)確認(rèn)? |
| 發(fā)布時(shí)間：2011/11/22 來源： 閱讀次數(shù)：488 |
| |
| 根據(jù)會(huì)計(jì)準(zhǔn)則的規(guī)定，在日常經(jīng)營活動(dòng)中企業(yè)能確認(rèn)為營業(yè)收入的內(nèi)容可分為如下幾類：銷售商品收入、提供勞務(wù)收入、讓渡資產(chǎn)所有權(quán)收入、租賃收入和建造合同收入五類。其中，前三類在《14號(hào)——收入》準(zhǔn)則中規(guī)范；租賃收入在《21號(hào)——租賃》準(zhǔn)則中規(guī)范；建造合同收入則在《15號(hào)——建造合同》準(zhǔn)則中進(jìn)行了規(guī)范。準(zhǔn)則的規(guī)定貌似清晰，但我們?cè)趯?shí)際執(zhí)行過程中卻存在一些問題?！ ∈杖腩悇e的邊界問題 比如我們經(jīng)常遇到一些客戶，承接了一項(xiàng)工程，這些工程需要用到自己生產(chǎn)的產(chǎn)品，還需要對(duì)產(chǎn)品進(jìn)行軟件系統(tǒng)集成，最后還要安裝該項(xiàng)產(chǎn)品，最后將工程移交給客戶，移交之后還可能對(duì)軟件按服務(wù)年限收取一定的服務(wù)費(fèi)?！ ?duì)于這個(gè)案例，我們到底如何來認(rèn)定業(yè)務(wù)的性質(zhì)，屬于是銷售產(chǎn)品還是提供勞務(wù)或是建造合同，甚至是長期租賃呢？實(shí)際上現(xiàn)在很多的系統(tǒng)集成并需要配備軟件的企業(yè)都存在我所述的問題，另外還有其他很多令人糾結(jié)的情況?！ ”热?，銷售產(chǎn)品并附有安裝義務(wù)的合同如果安裝時(shí)間較長的話，到底是銷售合同還是安裝勞務(wù)合同？準(zhǔn)則講解中舉例電梯銷售的安裝需要安裝完畢后才確認(rèn)為銷售收入，但如果電梯安裝需要很長時(shí)間，是否可分開為先銷售電梯在發(fā)出存貨且對(duì)方驗(yàn)收立即確認(rèn)銷售收入，然后安裝勞務(wù)按照勞務(wù)提供進(jìn)度確認(rèn)勞務(wù)收入？如果合同中有相關(guān)分段收費(fèi)時(shí)能否考慮？ 比如，軟件公司銷售為客戶的定制軟件，是屬于銷售產(chǎn)品，還是屬于提供勞務(wù)的合同？我們?cè)诰牌滠浖恼泄蓵邪l(fā)現(xiàn)是被認(rèn)定為銷售商品，但金蝶軟件公司招股書則認(rèn)為是提供勞務(wù)?！ ”热纾彻句N售產(chǎn)品，先收回制作成本，然后在以后年度每年以服務(wù)費(fèi)形式分期收款，是應(yīng)該當(dāng)作分期收款的商品銷售，還是當(dāng)作未來提供勞務(wù)收入，或者是說直接定義為租賃收入？租賃是融資租賃或者是經(jīng)營租賃？ 如此等等，這些東西在我們作審計(jì)時(shí)常常會(huì)碰到，客戶有其自己的考慮，甚至經(jīng)常會(huì)隨著自己的業(yè)績(jī)要求而改變確認(rèn)方式，當(dāng)然他們也會(huì)按自己的目的去改變合同條款，但交易實(shí)質(zhì)往往并沒有任何區(qū)別?！ ∈杖氪_認(rèn)條件的問題 任何一種收入的確認(rèn)，基本都要滿足風(fēng)險(xiǎn)轉(zhuǎn)移、利益很可能流入和所有權(quán)與管理權(quán)轉(zhuǎn)移三個(gè)條件，另外就是收入和成本的可計(jì)量。歸類之后實(shí)質(zhì)就是交易實(shí)質(zhì)完成和可計(jì)量?jī)蓚€(gè)問題。 對(duì)于交易實(shí)質(zhì)完成的判斷，其實(shí)不是那么好判斷的，在日常中大家常常會(huì)用到的標(biāo)準(zhǔn)包括：法律形式和經(jīng)驗(yàn)判斷。法律上會(huì)有一些條款，但這些條款哪些是實(shí)質(zhì)條款，哪些是常識(shí)條款？比如規(guī)定由退貨權(quán)，在銷售貨物之后的退貨權(quán)期間到底能不能因此判斷風(fēng)險(xiǎn)義務(wù)轉(zhuǎn)移？法律條文和經(jīng)驗(yàn)常常是不一致的。又比如我前面舉例電梯銷售，如果合同中規(guī)定了電梯款和安裝費(fèi)款，并且按照經(jīng)驗(yàn)發(fā)出電梯都能安裝成功，那么發(fā)出電梯是否可以確認(rèn)銷售收入？ 對(duì)于可靠計(jì)量的問題，也有一些疑慮。很多時(shí)候企業(yè)外購產(chǎn)品給客戶系統(tǒng)集成后去安裝中央控制室，如果當(dāng)作安裝勞務(wù)的形式或建造合同形式，確認(rèn)進(jìn)度又可能不一致。首先，如果確認(rèn)為勞務(wù)合同的話，那么設(shè)備銷售款我認(rèn)為必單獨(dú)分離出來確認(rèn)銷售收入；如果確認(rèn)為建造合同的話，設(shè)備會(huì)進(jìn)入建造合同總額，但一定不能按照工程成本投入量來確認(rèn)完工進(jìn)度，否則完工進(jìn)度可操縱性太強(qiáng)?！ ∮捎诤芏鄦栴}我都沒想清楚，可能我這個(gè)日記會(huì)讓一些人本來覺得清楚得，搞得跟我一樣糊涂，我先表示歉意，但我覺得先被我弄糊涂了，如果再有個(gè)明白人來指點(diǎn)清理一下，可能大家都會(huì)比以前更清楚?！ 【W(wǎng)友熱評(píng)： aegis：收入確認(rèn)的事，干活時(shí)不能深究，深究時(shí)不能干活?！ 《抛?、比如，銷售產(chǎn)品并附有安裝義務(wù)的合同如果安裝時(shí)間較長的話，到底是銷售合同還是安裝勞務(wù)合同？準(zhǔn)則講解中舉例電梯銷售的安裝需要安裝完畢后才確認(rèn)為銷售收入，但如果電梯安裝需要很長時(shí)間，是否可分開為先銷售電梯在發(fā)出存貨且對(duì)方驗(yàn)收立即確認(rèn)銷售收入，然后安裝勞務(wù)按照勞務(wù)提供進(jìn)度確認(rèn)勞務(wù)收入？如果合同中有相關(guān)分段收費(fèi)時(shí)能否考慮？ 很多客戶簽該類合同的時(shí)候，一般都會(huì)約定，貨到了，簽收之后付款如70%，安裝完畢25%（或+運(yùn)行合格后合計(jì)），保修期滿最后付5%；我認(rèn)為可以分別銷貨和安裝確認(rèn)?！ ?、比如，軟件公司銷售為客戶的定制軟件，是屬于銷售產(chǎn)品，還是屬于提供勞務(wù)的合同？我們?cè)诰牌滠浖恼泄蓵邪l(fā)現(xiàn)是被認(rèn)定為銷售商品，但金蝶軟件公司招股書則認(rèn)為是提供勞務(wù)。 按《企業(yè)會(huì)計(jì)準(zhǔn)則應(yīng)用指南-收入》五提供勞務(wù)收入確認(rèn)條件的具體應(yīng)用，（三）為特定客戶開發(fā)軟件的收費(fèi)，在資產(chǎn)負(fù)債表日根據(jù)開發(fā)的完工程度確認(rèn)收入?！ ?、比如，某公司銷售產(chǎn)品，先收回制作成本，然后在以后年度每年以服務(wù)費(fèi)形式分期收款，是應(yīng)該當(dāng)作分期收款的商品銷售，還是當(dāng)作未來提供勞務(wù)收入，或者是說直接定義為租賃收入？租賃是融資租賃或者是經(jīng)營租賃？ 我覺得要視先收回制作成本占總應(yīng)當(dāng)收款比例確認(rèn)收入確認(rèn)條件。如果大部分都收回了，且確實(shí)提供了后續(xù)服務(wù)，那么分別銷售商品跟服務(wù)費(fèi)確認(rèn)。如果僅合同條款規(guī)定是服務(wù)費(fèi)收入，但不需要或僅需要提供非常少的服務(wù)，那么不應(yīng)當(dāng)確認(rèn)服務(wù)費(fèi)收入。 國稅函[1998]390號(hào) 國家稅務(wù)總局關(guān)于電梯保養(yǎng)、維修收入征稅問題 花農(nóng)：推薦一個(gè)專業(yè)網(wǎng)站，http://www.revenuerecognition.com/ linwq1284： 關(guān)于電梯銷售收入確認(rèn)時(shí)點(diǎn)問題 電梯企業(yè)現(xiàn)狀： 電梯安裝，現(xiàn)在有兩種，一種必須國家檢驗(yàn)機(jī)關(guān)，驗(yàn)收合格才能投入使用。另一種不是在公共場(chǎng)合，包括高層住宅，只要廠檢就可以?！ ‰娞萜髽I(yè)，生產(chǎn)要一個(gè)生產(chǎn)特殊資質(zhì)，安裝又要安裝資質(zhì)，并且在各地安裝公司都要在各地有資質(zhì)或備案，如果沒有資質(zhì)是不能安裝。往往一個(gè)集團(tuán)內(nèi)是一個(gè)子公司生產(chǎn)電梯，另外各地有數(shù)個(gè)子公司是安裝公司?！ ∮捎谫Y質(zhì)原因，電梯企業(yè)，除了一部分是附安裝條款，但是絕大部分銷售合同與安裝合同是分開的?！ ⊥牵骸 ′N售合同是生產(chǎn)企業(yè)與客戶簽訂買斷合同，但是仍可能10%款項(xiàng)要等安裝調(diào)試完才付，主要原因是客戶擔(dān)心零配件調(diào)換。電梯款往往是幾十萬甚至上百萬元?！ “惭b合同，安裝企業(yè)與客戶簽合同，付款按簽合同、安裝完成等幾個(gè)階段收費(fèi)，安裝費(fèi)一般也不高，幾萬元。 兩個(gè)合并范圍內(nèi)獨(dú)立的公司，簽訂獨(dú)立的合同。 這時(shí)候收入確認(rèn)的標(biāo)準(zhǔn)問題： 1、是否要等安裝完成確認(rèn)收入？理由：從合并層面，兩個(gè)子公司視同一個(gè)主體兩個(gè)部門。因?yàn)楦鱾€(gè)部門你可以操縱，并且電梯只有安裝完客戶才能使用。 2、各自確認(rèn)，即生產(chǎn)企業(yè)按發(fā)貨驗(yàn)收確認(rèn)收入，安裝按完工百分比確認(rèn)收入。理由各自都符合收入確認(rèn)原則?！ 〉沁@樣做，監(jiān)管層到時(shí)會(huì)說你操縱利潤，不謹(jǐn)慎。又是會(huì)計(jì)師的責(zé)任！ 3、另外安裝按完工百分比，其實(shí)也很難，因?yàn)槊總€(gè)合同只有幾萬元，沒辦法分開到底是要如何分?jǐn)偘惭b工人的工資，因?yàn)榘惭b工人不是有活才付工資，沒有活也要付工資。 對(duì)上述問題1、2，請(qǐng)各位大蝦給予指正，也敬請(qǐng)財(cái)政部準(zhǔn)則專家給予指導(dǎo)?！ 『?jiǎn)單思考： 這些要從業(yè)務(wù)形式分析業(yè)務(wù)實(shí)質(zhì)來判斷，再根據(jù)準(zhǔn)則的要求來確認(rèn)，這是需要專業(yè)判斷?！ ∫苍S從幾個(gè)方面都有道理，但實(shí)質(zhì)還應(yīng)是差異不大的。實(shí)務(wù)還是需要把各種業(yè)務(wù)形式理清楚，分類梳理，找出業(yè)務(wù)關(guān)健或?qū)嵸|(zhì)地方，根據(jù)準(zhǔn)則的要求進(jìn)行專業(yè)判斷！ 如電梯銷售，主要看安裝是不是銷售的必要條件之一（不管是幾個(gè)合同，幾家單位及如何付款）?！ ∪畿浖?，主要是判斷軟件的所有權(quán)（終身使用權(quán)）和有限期間使用權(quán)，研發(fā)、定制、安裝及后續(xù)服務(wù)等，按要合同主要部分、限制條款等規(guī)定，根據(jù)準(zhǔn)則的風(fēng)險(xiǎn)、計(jì)量、分期要求來判斷?！ ★w草：會(huì)計(jì)第一大問題?！ ∠旅孢@篇文章對(duì)理解這個(gè)問題有幫助： New Revenue-Recognition Rules: The Apple of Apple's Eye? The computer company and other tech outfits are likely to cash in on revenue-recognition changes if the new regs take on an international flavor. September 16, 2009 While Steve Jobs was preparing to introduce the new Apple iPod nano last week, the company's chief accountant, Betsy Rafael, was sending off a second letter to the Financial Accounting Standards Board related to revenue recognition. At issue: how FASB might rework the rules related to recognizing revenue for software that's bundled into a product and never sold separately. The rule is especially important to Apple because it affects the revenue related to two of the company's most successful products — the iPod and the iPhone. If FASB's time line holds to form, and the rules are recast in 2010 the way Apple hopes they will be, the company could be able to book revenue faster, yielding less time between product launches and associated revenue gains. In theory, a successful launch — and its attendant revenue — would drive up Apple's earnings, and possibly stock price, in the same quarter the product is introduced, according to several news reports that came out earlier this week. Apple and other tech companies have been lobbying for a rewrite of the so-called multiple deliverables, or bundling, rule for quite some time. They argue that current U.S. generally accepted accounting principles make it hard for product makers to reap the full reward of successful products quickly. That's mainly because U.S. GAAP is stringent about when and how companies recognize revenue generated by software sales. "The requirements are that when you sell more than one product or service at one time, you have to break down the total sale value in[to] individual pieces. Establishing the individual values under U.S. GAAP is solely a function of how the company prices those products and services over time," PricewaterhouseCoopers's Dean Petracca told CFO in an earlier interview. Contracts typically include such multiple "deliverables" as hardware, software, professional services, maintenance, and support — all of which are valued and accounted for differently. The complex accounting rule has left many product makers waiting for a chance to voice their displeasure at the standards, and the most recent comment period saw such giants as Xerox, IBM, Dell, and Hewlett-Packard — as well as relative newcomers like Palm and Tivo — make their case to FASB. In all, 34 companies wrote to FASB during the month-long comment period that ended in August to register their opinions on the accounting treatment of multiple elements. A broader revenue-recognition discussion paper was issued by FASB and the International Accounting Standards Board in December 2008 for a six-month comment period. The boards are currently reviewing the comments, and an exposure draft on revenue recognition, which is the penultimate step to a new global rule, is expected out next year. Regarding the issue of multiple deliverables, most technology companies would like to see FASB move closer to international standards with regard to bundled software, and drop the requirement for vendor-specific objective evidence. Under GAAP, VSOE of fair value is preferable when available, according to Sal Collemi, a senior manager at accounting and audit firm Rothstein Kass. Basically, VSOE is equivalent to the price charged by the vendor when a deliverable is sold separately — or if not sold separately, the price established by management for a separate transaction that is not likely to change, explains Collemi. Third-party evidence of fair value, such as prices charged by competitors, is acceptable if vendor-specific evidence is unavailable. Many technology companies argue that it is sometimes impossible to measure the fair value of a component that is not sold separately, but rather is an integral part of the product — as is the Apple software for the iPod series of products. At the same time, international financial reporting standards require companies to use the price regularly charged when an item is sold as the best evidence of fair value. The alternative approach, under IFRS, is the cost-plus margin, says Collemi. That is, the IFRS puts the onus on management to value a product component based on what it costs to manufacture the piece plus the profit-margin share built into the item. Management usually bases its valuation on historic sales as well as current market-established sale prices. The cost-plus margin is not allowed under GAAP. With respect to bundled components, the IFRS focuses on "the substance of the transaction and the thought process and ingredients that go into the transaction," contends Collemi, who says the standard's objective is to make economic sense out of the transaction. FASB's take on the subject is more conservative: the U.S. rule maker calls for objective evidence to establish value. Some critics say the IFRS approach invites abuse, because it's based on management assumptions. But Collemi contends that GAAP accounting is filled with rules and interpretations that require management estimates, and that the burden is on management to produce the correct numbers. What's more, auditors are in place to act as a backstop to verify the processes used to arrive at management estimates. "If management is following the spirit of the transaction and doing the right thing," adds Collemi, "then it is up to auditors to challenge the estimates." 原文地址：http://www.cfo.com/article.cfm/14440468/1/c_2984368?f=rsspage |
|
|
|
|
|
