2018年2月28日 星期三

【審計】【STEM】KPMG審計觀點:區塊鏈衝擊傳統事務所,KPMG將數位轉型探索全新的審計模式


KPMG審計觀點:區塊鏈衝擊傳統事務所,KPMG數位轉型探索全新的審計模式

14 二月 2017

區塊鏈所帶來的分散式帳本Distributed Ledger TechnologyDLT,具有透明、不可竄改並且不需要中介者的特性,正好衝擊了傳統審計與確信服務的人員的工作內容。面對區塊鏈、Fintech及大數據等技術出現,安侯建業積極備戰。


「如果區塊鏈真的發展起來,以後審計人員不懂區塊鏈的話,是沒有辦法做審計的。」安侯建業審計部營運長陳振乾這麼說道。區塊鏈所帶來的分散式帳本,具有透明、不可竄改並且不需要中介者的特性,正好衝擊了傳統審計與確信服務的人員的工作內容。面對區塊鏈、Fintech及大數據等技術出現,安侯建業積極備戰。陳振乾表示,他們正延攬非典型的審計人才,要將傳統Auditor的角色與組織,轉型成數位架構(Digital Architecture),更要發展大數據平臺Clara。他透露,區塊鏈固然會對審計造成十足的破壞力,但審計的工作並不會消失新的審計模式將出現,安侯建業正積極布局,尋找數位浪潮的下一步。

「對審計部門來說,2017大概可以定義為數位轉型的一年,邁向審計4.0。」陳振乾回顧了過去審計的技術演進,審計1.0是使用算盤、2.0是計算機、3.0則是電腦,現在的4.0則是運用平臺跟大數據分析,來完成服務。今年的安侯建業全球數位轉型的第一步,就是優先發展Clara智慧互動平臺,導入數位運算與分析的引擎,試圖優化跟客戶之間的互動模式。

打造大數據平臺「Clara」,發展客戶即時互動的新服務模式
Clara系統的目標就是要建一個平臺,跟客戶做即時性的互動。」過去,安侯建業與客戶經常有頻繁的資料往來,而這些資料的溝通需要透過E-mail或是USB裝置進行傳輸。跟各個企業間的資料交換光要達到便利性,又要兼顧安全隱私,是一個極大的挑戰。

發展Clara平臺的目的就在於可以即時、便利又安全地傳遞資料。除了增進跟客戶之間的資料傳輸的品質之外,Clara還會有資料運算、智慧分析的引擎,「透過Clara系統,可以將跟客戶的互動萃取下來。」目前安侯建業正跟IBM Watson合作,發展Clara平臺的人工智慧的分析能力。

陳振乾表示,傳統審計是信任客戶會把系統做好,然後由審計人員去驗證他們的系統,透過抽樣資料去查核,並推論到母體。

但是大數據分析則是全然不同的概念。「假若一萬筆資料,哪些是Outliers(異常樣本),這些Outliers代表什麼意義,你對資料的特性要完全了解。」這顛覆了過去稽核的工作模式,因此他們正在延攬懂資料的分析師來協助,一起解讀資料,並用視覺化呈現趨勢,然後點出每一個Outlier所代表的意義,用這種方式來完成審計。

「客戶的資料進來,就可以經過大數據分析的過程,得到一些洞見跟觀察,跟客戶分享。」陳振乾解釋道,過去的客戶服務往往見樹不見林。如今,透過Clara平臺,可以將確信服務這件事提升到另一個層次,它將在審計證據、資料應用、客戶應用上,協助安侯建業的服務。

將體質轉換成數位架構,尋找會計與資訊背景的通才
除了建構大數據平臺外,安侯建業也開始尋求第二步的數位轉型計畫,就是人才招募,要重構整體體質,逐步轉成數位架構。

陳振乾坦言,現在的審計服務,若單靠傳統人才是無法應付的。隨著科技元素的增加,需要在傳統會計能力之外,再跨資訊、資工、數理或資料分析背景的跨界人才。他表示,兩年前,安侯建業就開始進行人才招募的計畫,目前已經招攬了近30位有會計背景,又有資訊背景的通才。安侯建業要透過這些人才,進行事務所內部的數位轉型,倚賴他們對資料萃取方式、資料分析的訓練,再結合傳統的稽核服務,創造出審計的新價值

他形容,未來的稽核人員都要像建築師一樣,能夠善用資源、運籌帷幄,「稽核人員就會像建築師的角色,去找懂土木、懂燈光的人來幫忙蓋房,這就是我們稽核業務的轉型。」他說。

區塊鏈讓資料無法造假,但交易可以!
許多人都預言,區塊鏈將會取代許多中介角色(如:稽核人員),它更被稱為「信任機器(Trust Machine)」,面臨這股來勢洶洶的區塊鏈大浪,陳振乾坦言確實對審計會有很大的衝擊,尤其確信服務的關鍵就是信任,一旦信任可被取代,代表著審計必須尋找到新的服務方向。他表示,技術或許不是最大的難題,最困難的是產業的轉型、人的心態以及新的信任機制。

當資料真實性已經不再需要驗證時,稽核人員確實省了不少時間。因為目前的中介成本有很大部分都是在確認文件的真偽。「區塊鏈確實可以把99%的文書驗證的工作去除,但我們要去處理的部份,就是交易是不是真的,變成需要一個獨立的角色去看這件事。」他表示,金融業未來也許很多交易都選擇用區塊鏈完成,而安侯建業扮演的角色就是去保證此交易為真。

交易是不是真的,就會變成我們關注的議題。」他表示,詐騙還是會存在,只是以不同的形式存在。未來的詐騙集團,打一通電話,是不可能騙到錢的,而是要有一個交易來呈現這筆詐騙交易

除了稽核業務的轉型之外,整體產業也都在改變。他以國稅局為例,國稅局過去是不知道個人稅務資料如何,所以去查核,但現在有區塊鏈作為一個透明化的分散式帳本,再也不需要傳統查稅人員去查稅,只消把資料撈出來,頂多做一些異常解讀罷了。

「如果客戶以後資料都在區塊鏈上,造假的風險就會降低很多,當然一定也會有新的詐騙方式出來。」他強調,資料本身因為區塊鏈而成為無法竄改的紀錄,但不代表交易無法造假。因此,稽核人員仍然有存在的價值與意義

一旦區塊鏈普及,各種底層協定紛紛出籠後,稽核人員不能只懂區塊鏈的基本原理,而是要去懂每一種區塊鏈協定的差異、模式。客戶的交易,可能分別在AB兩種不同區塊鏈內完成,因此稽核人員必須理解跨區塊鏈間的運作模式。「審計人員要去了解一個公司裡面,可能有五種不同區塊鏈應對的模式,每一種他所產生的資料模式會如何。」這是稽核人需具備的能力。

在各界大力擁護區塊鏈作為落實透明化交易的手段時,另一個新興的議題是「隱私」,這也是陳振乾特別關注的。他認為,當區塊鏈發展到一定程度時,或許會出現如網路被遺忘權的類似結果。「我覺得技術的發展也會是個擺盪的過程,區塊鏈也許20年發展後,就會倒回來:我有被刪除權。」他說,交易的軌跡是否要一直保留?保留的期限有多長?這都涉及了人性的挑戰,而非技術層面的障礙。

如同近期,日本的一名罪犯向日本最高法院要求行使「被遺忘權」,希望可以將他過去曾犯過的罪行報導在網路上刪除一樣。區塊鏈是否也會成為另一種個人隱私的累贅,在探討區塊鏈的優點時,更應該思考技術最終可能會帶來的反噬

2018年2月27日 星期二

【資料科學】淺談探索式資料分析 -- 從一個資安小故事談起


淺談探索式資料分析 -- 從一個資安小故事談起

原文

【AI】AI=會計師末日?


AI=會計師末日?


審計密探CIA: Bittermelon

人工智能(AI)再次掀起會計人不安,事緣某財經雜誌最近做了個專題報道,探討AI如何搶人類飯碗,當中一篇更講述Big 4在此領域的應用和發展。


所謂太陽底下無新事,不妨先回顧一下歷史。早於三、四十年前,個人電腦不像現時普及,人手造帳仍然盛行,但當時不少人已預言,電腦將取代會計師。理由很簡單,電腦快而準,而且節省人手。如大型企業年結要做關帳,不說別的,只簡單地將帳簿上每個帳目的結餘抄入試算表,然後將借貸兩方加總,若順利沒有差異,至少要花上1個小時,若不幸兩方不平衡,更需花時間找出原因。反觀現在,人手造帳幾乎成絕響電腦會計系統平靚正,關帳只在彈指之間。電腦在人手配置上更顯絕對優勢,以前大型企業的會計部,配備過百人是常態,現在閣下公司又有多少會計部同事?


電腦那麼好,按理會計師早應乞食,為何近幾十年人數不減反增?答案只有一個,世界在變,會計師也與時並進簿記並非會計師的唯一工作,其他還包括制定稅務計劃、管理財務資產、安排融資、編製管理報表、監察預算執行情況、評審投資項目、處理收購合併,和定內控程序等,電腦不單沒有搶去飯碗,更協助我們提升服務水平。如編製財務報告,以前需時以小時甚至天計,現在按一下鍵,所有報告即時準備妥當。


AI無疑比電腦更兇猛,因它懂得學習,一旦學懂了會計師一切技能後,就可以將我們踢走。可是,究竟有多少人認真探討過,AI可以全面取代會計師嗎?


或許我們先看AI目前的發展。如畢馬威採用IBM Watson的認知計算技術,為客戶分析結構化和非結構化財務數據。所謂結構化,即是將數據安排得整整齊齊,儲存到數據庫時已經被定義,不論是欄位、格式和佔用大小等都固定。相反,非結構化數據就是一堆亂七八糟的資料,格式可以是電郵、報告及影片等。IBM Watson其中一個厲害之處,是通過學習能解讀非結構化數據,正如會計師閱讀各式各樣的財務報告,然後從中抽出有用的數據做分析。


又如德勤與Kira Systems合作,為會計、稅務和審計引入AIKira Systems其中一個強項,就是通過學習以識別各類文件。如物業租賃合同,系統能列出合同名稱、各簽約方名稱、物業資料如地址和面積、簽約日期、具體條款如租賃期和租金。系統還可自動檢查,找出有問題或遺漏條款,甚至可能不符合法律的條文。


從上述兩個例子可見,目前AI的強項能像人類般閱讀和分析數據,而且做得更好。人類身體有極限,亦容易受情緒影響表現,機械卻能不眠不休地工作,而且任勞任怨不會罷工。


會計師豈非末日?非也!根據牛津大學早前的研究指出,在可見將來,AI在感知及操控能力、創造力和社交能力三方面難與人腦匹敵。然而,會計師日常的工作,不單是閱讀和分析,我們需要具備良好的社交能力,如與企業內各部門合作,共同制定和執行財政預算,以及與銀行維持良好合作關係。我們也要創造能力,這裡說的當然不是造假數,而是想辦法解決企業遇到的種種問題,包括稅務、收購合併,以至日常營運等。會計既是科學又是藝術,會計師不單需要科學家頭腦,同時要具備藝術家的氣質。個人認為,AI不單不會取代會計師,更協助我們將服務提升至另一層次。立此存照,將來看看瓜瓜的預測是否正確。  

2018年2月26日 星期一

【電腦稽核】IS Audit Basics: The Core of IT Auditing

IS Audit Basics: The Core of IT Auditing

電腦稽核領域的專業證照而言,我想大多人直覺聯想到是CISA(國際電腦稽核師)CISSP(國際資訊安全管理師),但是這兩項證照主要領域為資訊系統稽核IS Auditing)、資訊科技治理(IT Governance)或是資訊科技安全(IT Security)。對於電腦稽核的另一重要應用領域:電腦輔助查核技術(CAATS: Computer-Assisted Audit Techniques),涉入的並不多。

Tommie Singleton, CISA, CGEIT, CPA
ISACA Journal Volume 6, 2014

With the advent of the latest wave of information technologies such as big data, social media, technologies as a service and the cloud in general, it is worth taking the time to revisit the basics of IT audit. Usually, when such new technologies arise, the issues are the same as something in the past, and the way to address the emerging technology is to do what IT auditors always do when faced with challenges of new technologies. We go back to the core of IT auditing and what IT auditing is all about. It is about identifying risk and the appropriate controls to mitigate risk to an acceptable level.

Three Things an IT Audit Is Not
But first, especially for those new to the profession and for those outside our profession, it should be noted what IT auditing is not. It is not about ordinary accounting controls or traditional financial auditing. That knowledge and skill set served the audit profession well from the beginning of auditing in the middle ages (with exchequers and other forms of auditing) until the introduction of computing systems in the 1950s. In fact, before 1954, it was possible for an auditor to use a very similar audit program from day one of his/her career until he/she retired. To put it simply, the use of computers in accounting systems introduced a new source of risk associated with accounting processes and information (i.e., data). And, it introduced the need for those who understand this new “thing” to identify and mitigate the risk.

IT auditing is also not compliance testing. Some believe IT auditors are about making sure people conform to some set of rules—implicit or explicit—and that what we do is report on exceptions to the rules. Actually, that is management’s job. It is not the compliance with rules that is of interest to IT auditors. IT auditors are examining whether the entity’s relevant systems or business processes for achieving and monitoring compliance are effective. IT auditors also assess the design effectiveness of the rules—whether they are suitably designed or sufficient in scope to properly mitigate the target risk or meet the intended objective.

Compliance failures are important to IT auditors, but for reasons beyond the keeping of rules. A compliance failure can be, and often is, the symptom of a bigger problem related to some risk factor and/or control, such as a defective system or business process, that can or does adversely affect the entity. Thus, to the IT auditor, compliance failures are much more about risk (ultimately) than the rules themselves.
【關注systems or business processes

It is also passé to automatically or casually consider IT considerations of an audit to be out of scope because it is not explicitly related to some stated requirement, or to consider an audit to be a waste of time. The fact is IT can and does adversely affect business processes or financial data in ways of which management may not be adequately aware.

ISACA thanks Tommie for his years of service to the Journal and the association. Your words have influenced many professionals and will continue to do so. Wishing you the very best as you end this chapter and begin the next!

Unique Inherent Risk
IT presents risk factors (風險因子) that are unique to accounting, auditing and systems. That is, IT itself brings risk to the entity regarding its systems, business processes and financial/accounting processing. That risk is unique to IT and without IT being present, that risk would not exist—at least not to the same level. It takes a professional, such as an IT auditor, to identify and assess the inherent risk associated with IT.

Those risk factors include systems-related issues, such as systems development, change management (變更管理) and vulnerabilities, and other technology-specific factors. Apart from the IT professional, such risk can go unnoticed, to the detriment of the entity. For example, a university had the following experience related to its financial aid systems.

The university’s IT department wrote its own code for financial aid. The university had a great deal of financial aid available as a private institution, leading to the majority of students receiving some form of aid. The experienced IT auditor, seeing these facts, identified certain inherent risk associated with financial aid including the accuracy of the code, the possibility of a bug in the code, and the possibility of fraudulent code that needed to be addressed, examined and mitigated. However, management of the university did not recognize any risk and assumed the IT department had done its due diligence and everything about the financial aid code was acceptable. A few years later, the university accidentally discovered a bug in the code that was causing calculations of financial aid to be overstated. Millions of dollars of financial aid had been awarded over those years in error, and the institution had some financial problems causing it to abandon some of its programs. This case is offered to illustrate the need to identify and assess the inherent risk associated with IT to the entity.

Given that almost all entities employ some level of IT, the day has come when these entities truly need an IT auditor to evaluate their inherent risk of IT. IT auditors are particularly trained and skilled at doing that task. IT auditors are capable of identifying the nature and risk of IT technologies and systems.

Back to the emerging technologies issues, the place to start with them is to properly assess the nature, specificity and assessed level of risk. Once this process is thought through diligently, the IT auditor and others can begin to put together adequate controls to satisfactorily mitigate risk.

The Role of Controls

One of the main reasons for a control is to mitigate some identified risk. The way to deal with an inherent risk that is at a level higher than what is acceptable is to implement an effectual control to mitigate that risk to an acceptable level.

That being said雖然如此, there are some points to remember about controls and the role they play in IT auditing, or auditing in general. First, IT auditors need to be wary of false security by a control that is effective enough to mitigate the risk to an acceptable level. While experienced IT auditors are generally good at this exercise, management and others may not be as adept at understanding the reality of a control.

On the other hand, IT auditors should remember and keep in mind that controls introduce a cost and a benefit. The cost is almost always in real dollars—cost of identifying, designing, implementing and managing the control. The cost can also be an impact cost of inconvenience or operational efficiency in slowing down a process. Some of the latter is not so much a concrete observation as it is an understanding of, and taking into account, the impact of a control. A key for IT auditors has been seeking a balance between these costs (real/concrete and impact) and benefits. Benefits can also be real and concrete—understanding the relative difference in having the control operate effectively and doing without it. That balance is easier to describe than to discern effectually.

For instance, an organization wants to implement an effective password policy for the length of life for passwords. The common wisdom is that the life should be inversely correlated with the amount of risk associated with unauthorized access (未授權存取). That is, if there is a high risk associated with unauthorized access, the life should be short (e.g., 90 days for an online bank account). However, once that policy is implemented, there could be an unintended cost associated with forgotten passwords due to the frequency of changes in them. The result could be users frequently forgetting passwords and having to use entity resources for assistance in obtaining access—a cost that includes delays and frustration, among other results. Thus, the key is due diligence in assessing the real net benefit of a control.

Another consideration is that an entity has a business or purpose for which it is in operation. That purpose needs to be part of the consideration. It is easy to lose sight of the unintended impact on operations.

Generally speaking, the higher the inherent risk, the higher the interest should be in a control to mitigate that risk. IT auditors need to, therefore, consider the level of inherent and residual risk when conveying recommendations for controls.

Last, controls are often embedded in technologies or systems. That fact alone suggests that IT auditors need to be involved in assisting with the design where independence allows it. It also suggests a high importance for using IT auditors to assess the effectiveness of the internal control system. How can the control embedded in IT be properly assessed without an IT subject-matter expert providing assistance in understanding how effectively the control operates?

Understanding the Real Residual Risk (剩餘風險)
One of the issues with analyzing risk is that it is usually relative and subject to judgment. All constituents want controls to be “good enough” so that things will be “okay.” But, what is “good enough” and what is “okay”? Risk is not usually subject to an absolute measurement.

Bad managers have a tendency to misjudge or misapply controls and risk. Concerned with surviving and making a profit, they sometimes do not see the reality of residual risk and rush ahead only to encounter a bad result. Or, they get paranoid and avoid a perfectly acceptable risk and take no action to their detriment. Good managers, however, understand the reality of residual risk, and usually make the right decisions and often have a contingency plan (應變計畫) should the risk come to the forefront. One of the challenges for IT auditors is to help managers be good or great managers by understanding the real residual risk and taking the appropriate action related to it.

One challenge in understanding the reality of residual risk is to properly assess risk and controls holistically. First, some controls are not IT and there is a tendency by some to overlook a manual control that has the potential to mitigate an IT-related risk. For instance, review and reconciliation by a controller may adequately reduce/mitigate the risk of unauthorized access to data and databases. That is, if someone were able to compromise the access controls, or lack thereof, and compromise data in a financial/accounting database, any error or fraud created would be caught promptly and corrected. Thus, the residual risk may be relatively low considering the manual control.

Second, a residual risk that exists in one area may be addressed by an effective control in another area. For instance, it may be that a firewall has inadequate protection against an outsider coming through the perimeter and hacking into the system. It would be easy to jump to conclusions about the high-level residual risk related to financial data and financial reporting, for example; however, if the entity has strong access controls at the network layer (網路層) (e.g., a strong Active Directory control matrix and logical segregation of duties), at the application layer (應用層), and over the operating system and database access, what are intruders going to do once they gain access through the perimeter? Therefore, it is crucial to do a mental walk-through of how the perceived residual risk will play out if it becomes reality, to determine if it is a real residual risk. This example assumes the audit objective was related to financial reporting. Obviously, if this situation were one where the audit objectives were related to systems in general (internal audit) or the firewall in particular, the residual risk would be real and need attention. Either way, the firewall is broken and probably needs to be fixed.

Scoping the residual risk means the IT auditor also needs to have a mental map of all the broken things in the IT space and which ones are real/relevant and which ones are broken; but out of scope. (The truth is, all IT audits will likely unveil several things, but they may not all be in scope.)

It is also crucial that the IT auditor develop a rational argument for why something found in the IT audit needs to be addressed and remediated, and ensure that it makes sense from a business perspective. The tendency of IT auditors is to find broken things and want them all fixed because they are broken. However, IT auditors need to examine from a business perspective what really needs to be fixed. The rationale should be a reasonable, realistic, business-oriented scenario of a relatively high risk that would come to fruition.

These issues illustrate the need for IT auditors to be effective communicators.

Conclusion
What IT auditors do is usually contained in risk and control arenas. Therefore, it is critical that IT auditors be adept at understanding, analyzing and communicating results related to risk and controls and what we do.


2018年2月25日 星期日

【IT】Introduction to Data Analysis for Auditors and Accountants

Introduction to Data Analysis for Auditors and Accountants

By Alexander Kogan, PhD, Miklos A. Vasarhelyi, PhD and Deniz Appelbaum

February 2017


In Brief

The audit world is changing. Technology has transformed business processes (企業流程) and created a wealth of data that can be leveraged by accountants and auditors with the requisite mindset. Data analysis can enable auditors to focus on outliers and exceptions, identifying the riskiest areas of the audit. The authors introduce the process, with a review of some emerging approaches and compilation of useful resources for auditors new to the topic.

* * *

The advent of inexpensive computational power and storage, as well as the progressive computerization of organizational systems, is creating a new environment in which accountants and auditors must practice. This article aims at introducing basic data analysis concepts to enable accounting professionals to understand how to navigate within this new environment. Specifically, the focus will not be on auditing and accounting standards and their current required procedures, but rather on what the profession can progressively achieve with data analytics. Most analytical procedures, in the right circumstances, may be applicable to the entire audit process, from risk assessment to test of details. What follows is a step-by-step overview (Exhibit 1) of best practices for the process of applying analytics, with an emphasis on audit by exception (ABE).

The Steps in the Process:
l   Flowcharting the process.
l   Choosing and extracting the data.
l   Understanding the population.
l   Understanding the fields with descriptive statistics.
l   Exploratory data analysis (探索式資料分析).
l   Choice of analytic methods and alternative approaches.
l   Confirmatory data analysis (驗證性資料分析) and finding outliers.
l   Evaluating results evaluation and integrating with traditional findings.

Flowcharting the process.
Understanding the elements of a certain cycle or application is essential for selecting data and understanding risk. Many tools are available for flowcharting (流程圖製作), such as Tableau Public, QlickSense, and RapidMiner, all of which are free. Flowcharting is also possible in Microsoft Excel or PowerPoint. Exhibit 2 shows a sample flowcharting process taken from an insurance company.

Choosing and extracting the data.
With the risks in mind, the next step is to choose the data fields (資料欄位) to be extracted and examined. This type of analysis is not very different from what would be done on a traditional audit. A progressively increasing number of audit apps are being sold or shared that can serve to simplify the audit task (e.g., http://www.capterra.com/audit-software/). Unfortunately, providers have not yet standardized around the AICPA’s Audit Data Standards (ADS) or any other common standard. Nevertheless, many audit software providers (e.g., ACL and CaseWare) have extensive libraries of scripts (腳本) that can be adapted to various data formats, as well as extraction software that allows for access to traditional data and enterprise resource planning (ERP) systems (e.g., SAP and Oracle).

Understanding the population.
It is very important for the sake of completeness to understand the nature, distribution, and limitations of the population to be tested. Understanding the scope and limitations of the data is imperative, as it enables an accountant to choose the most appropriate and effective analytical technique.

Understanding the fields with descriptive statistics.
The examination of key fields for their characteristics and statistical parameters (e.g., maximum, minimum, median, variance) and data availability (e.g., missing values) is probably the most important initial task, but one that is often underappreciated or even neglected.

Exploratory data analysis.
Modern tools of visualization (e.g., Tableau or Excel) allow for data exploration that helps auditors carefully choose where to place their analytic efforts and which assertions to test. Auditors can focus more extensive testing on the areas highlighted as highest risk.

Choice of analytic methods and alternative approaches.
A great number of analytic methods have been applied to audits in a research mode (Deniz Appelbaum, Alexander Kogan, and Miklos Vasarhelyi, Analytics for External Auditing: A Literature Review, Rutgers CARLab, 2016) and are being progressively adopted by CPA firms. Exhibit 3 provides examples of several analytic methods. Given this variety of choices, auditors need to know the data as intimately as possible, as well as understand the specific analytic task, in order to reduce the pool of potential analytical methods.

Confirmatory data analysis and finding outliers.
Having identified the riskiest areas of the audit, an auditor should next use some of the techniques discussed above to evaluate the data. These techniques are used first to infer analytic models to provide audit benchmarks or expectations; the actual values are then compared with the benchmarks. Any significant deviations should be investigated by auditors. For example, regression analysis can be used to derive a model for the revenue account based on archival data. The values calculated by this model should be compared against the actual revenue amounts, and any significant differences investigated.

Evaluating results evaluation and integrating with traditional findings.
Ideally, the outliers should be segregated from the population for more detailed audit examination, as discussed above. In such an audit by exception (ABE) approach (Exhibit 4), an auditor’s attention is more focused on the problematic transactions rather than a traditional sample pool (which may or may not identify problematic transactions). Theoretically, ABE provides a more efficient and effective approach for identifying questionable numbers.

Because this examination process is not sample-based but exception-based, it represents a significant departure from the currently prevalent audit practice of statistical sampling. The main difference between the ABE and a sample-driven audit is how the subset to be examined is obtained. Both approaches start with the entire population, but an ABE tests every transaction and ultimately focuses only on those transactions that present problems (Exhibit 5), whereas a statistical sample does not test every transaction, as the sample purportedly represents the diversity and content of the entire population. If, however, the error-prone transactions as determined by the ABE tests represent, for example, less than .15% of the population, a sample of 60 transactions may or may not include even one data point that is significantly deviant, whereas every one of these .15% outlier transactions would be flagged for detailed testing by an ABE.

Nevertheless, many auditors and accountants may not initially feel comfortable with conducting an ABE of 100% of the population, unless this ABE examination were to be accompanied by a traditional statistical sample. The results of the ABE would then be examined in detail, just as currently the samples pulled are tested, with the findings compared and reported.

It is worth remembering that sampling became an accepted audit practice during a time when data sets were expanding in size but auditors were still examining transactions manually. Detailed examinations of entire datasets were infeasible at that time. Now that automated audit software capable of testing datasets rapidly with minimal manual involvement from the auditor exists, this obstacle is no longer an issue.

Emerging Approaches

Although many of them have not yet been included auditors’ daily repertoire nor codified in audit standards, there are many emerging data analytics approaches that could assist with the audit process. Some of these are shown in Exhibit 3. The most promising of these approaches are described below.

Predictive analytics (預測分析).
Carefully validated and highly accurate predictive analytic models for aggregated accounting numbers can be used by auditors to reduce the time-consuming effort of disaggregated testing if the predicted values and the values of management assertions are sufficiently close.

Deep learning (深度學習).
The large audit firms are investing significant resources into the use of artificial intelligence to take advantage of their past experiences and industry knowledge. For example, data from working papers can be used to create automatic protocols for certain audit judgments, such as bad debt estimation, lease classification, and identification of abnormal contracts. Deep learning uses this knowledge in tandem with more advanced methods, such as neural networks (類神經網路), to represent the deeper structure of events and conditions in multiple layers of the neural network. Another term associated with deep learning is cognitive computing認知運算,” a blend of automation and human interpretation. Deep learning requires tremendous computational storage and power, however, since the learning occurs by combining human expertise with enormous amounts of data. Many businesses outsource deep learning projects to contractors and research centers, such as IBM Watson. It is conceivable that in the near future an “Auditor Watson” could exist that would assist accounting firms with financial and operational audits.

Blockchain/Smart contracts (智能合約).
The recent development of the virtual currency Bitcoin has been facilitated by a technology known as blockchain that can keep data public and replicates many transactions in a network using encryption methods. This methodology may presage a fundamental change in methods of data storage and validation. Smart contracts associated with blockchain might be able to automatically execute contract features without human intervention. For example, the contract between the auditor and the firm may dictate that if an outlier is larger than 100% of the median value of the transactions, it must be stopped and examined by human eyes; blockchain could theoretically flag such outliers and refer them to an auditor.

Text mining文件探勘;文本探勘.
The emergence of big data, and the mixing of large corporate datasets and external, unstructured data, allows for highly promising machine understanding of text that may one day provide great validation for management-supplied numbers and support new audit products, such as continuous auditing and monitoring from external data. Of note is the fact that three of the largest audit firms have employed legal discovery tools or developed methods to text mine information from converted PDF documents to create deep learning inputs.

Tools and Information Sources

More than 700 firms audit public companies, and many more audit or examine other entities. Smaller firms do not have the extensive financial and human resources that larger ones have, and thus may not be able to leverage data analytics technology to the same extent. There are, however, many sources of free software and educational materials that are currently available. A selection of these resources, in addition to commercially available tools, is listed below.

The open source R software has one of the largest library of applications available. Free software such as R and Weka are used nationwide in university courses and by some research and technology firms, but are somewhat frowned upon by accounting firms because they are not validated. These concerns are not without merit, since open source software can be clumsier and less user friendly than proprietary software, but their utility should not be ignored. In addition, while a basic knowledge of statistics and information technology is becoming essential for all accountants, other, more specialized functions can be contracted to other experts, perhaps online.

Proprietary tools such as Audit Command Language (ACL) and Interactive Data Extraction and Analysis (IDEA), as well as generic statistical software such as Statistical Analysis System (SAS) and Statistical Package for the Social Sciences (SPSS), are frequently used by large businesses and large firms. Furthermore, the capabilities and scope of these packages are constantly evolving, requiring that accountants and auditors have sufficient knowledge of analytics.

Large firms typically retrain their professionals through internal courses about their own approaches to auditing and are progressively trying to introduce audit analytics into this process. Four decades ago, each one of the then-Big Eight had its own IT audit packages, but today the Big Four use vendor-provided software such as ACL and IDEA. This convergence will likely also take place with the emerging statistical and visualization toolsets being developed.

A major difference in today’s environment is the power of group sourcing and the diffusion of the Internet. Powerful education mechanisms are emerging, ranging from free public resources to online Masters of Accountancy programs in audit analytics, some of which are financed by major firms (“KPMG, Villanova, Ohio State Launch First-Of-Its-Kind Data and Analytics Master’s Degree to Prep Data-Age Auditors,” KPMG, Aug. 4, 2016, http://bit.ly/2jWihzN).

A Growing Phenomenon
The advent of data analytics and big data is not a fad; it is a real phenomenon driven by new technologies being adopted by many businesses. Accountants and auditors are currently very far behind the curve. The profession will inevitably be forced to modernize audit approaches by corporate processes that are not auditable by traditional methods, accounting packages that can perform without manual intervention, and pressure from clients for more value in the audit engagement.

This article provides a general introduction to modern analytic methods and sources of information and education for accountants. Further resources can be found at http://raw.rutgers.edu/CPAjrefs.html.


2018年2月24日 星期六

【審計】【審計抽樣】HOW DOES CLASSICAL VARIABLES SAMPLING (傳統的變量抽樣) WORK?

HOW DOES CLASSICAL VARIABLES SAMPLING (傳統的變量抽樣) WORK?

By Maire Loughran

Adapted from Wiley CPA
運用在證實測試的統計抽樣(=變量抽樣Variables sampling)可分為:
l   機率與金額大小成比率法(PPS sampling technique),及
l   傳統的變量抽樣(Classic Variable Sampling),而傳統的變量抽樣常用的方法(method)又可分為:
n   單位平均估計法(Mean-Per-Unit Estimation)
n   差額估計法(Difference Estimation)
n   比率估計法(Ratio Estimation)
n   Regression Estimation

When using classical variables sampling, auditors treat each individual item in the population as a sampling unit. This method is most like the statistics classes you had to take in high school and college. You use this method to evaluate your entire population based on your sample data. You can use three common types of classical variables sampling estimators:
1.          mean-per-unit,
2.          ratio, and
3.          difference.

Mean-per-unit uses the familiar statistical concept of mean. For instance, if you add 10 + 30 + 50 to get 90, and then divide 90 by 3 (the number of values in this example), you get 30, which is the mean. As an auditor, you apply this statistical concept to evaluate characteristics of your total population. Taking the average value (mean) of items in your sample, you can estimate the true population value.

For example, you have a total population of 3,000 items in accounts receivable, and your sample size is 50. Adding up the individual values of the 50 items, you get a total of $2,000; therefore, your mean is $40 (2,000/50). Your mean estimate of the true value of accounts receivable is $120,000 ($40 x 3,000).

Considering this data with your sampling risk, confidence level, and error rate, if your confidence level is 95 percent and your error rate is 10 percent, you can say that you’re 95 percent confident that the total value of accounts receivable is $120,000, plus or minus $12,000 ($120,000 times your error rate of 10 percent).

The mean-per-unit method is a very good one to use if you don’t have the underlying documents that support the account balance--if, for instance, your client’s balance sheet shows a total for accounts receivable, but the individual invoices supporting the balance aren’t available.

Another method of classical variables sampling is ratio estimation, which applies the sample ratio to an entire population. If your sample for any of your client’s accounts shows errors of $1,000 in a total sample of $10,000, your misstatement ratio is 10 percent (1,000/10,000).

You would then apply this ratio to the entire population. If the entire population totals $50,000, your projected misstatement, which is an estimation of the misstatement in the entire population, is $5,000 ($50,000 x 10 percent).

【交叉相乘】
1,000 : 10,000
X : 50,000
X = 5,000 = projected misstatement

For sampling risk, if projected misstatement doesn’t exceed expected error, you can reasonably conclude that actual misstatement doesn’t exceed your tolerable misstatement.

l   projected misstatement v. expected error

Lastly, difference is another classical variables sampling method. It’s similar to ratio estimation, except it incorporates the items in the population. For example, your population consists of 5,000 items and your sample consists of 1,000 items. Your audit procedures find errors totaling $500. The projected misstatement is $2,500 [($500/1000) x 5,000 items].

【交叉】
500 : 1,000 items
X : 5,000 items
X = 2,500 = projected misstatement



Law and Tax Notes 2022/1/9

===================================   違章建築 拆除通知單 是否為 行政處分 ?(108.4.1) https://legal.chcg.gov.tw/07other/other01_con.asp?topsn=4179&...