Using Drones in Internal and External
Using Drones in Internal and External
Robert A. Nehmer
Oakland University
ABSTRACT: Recently the FAA relaxed restrictions on the use of drones or Unmanned Aircraft Systems (UASs) for
commercial purposes. Markets for commercial drone use are in the technology trigger phase of the Gartner Group’s
Hyper Cycle, with developments occurring rapidly in real estate, agriculture (farming), the film industry, insurance,
and other areas. Examination and inspection applications of drones have been proposed in heavy industry and cell
tower inspection. Previous research suggests an incremental structure for implementing technological innovations
such as continuous auditing (CA). In this paper these proposals are expanded to include the additional requirements
to add drone technologies. This structure is extended here by (1) defining the use of drones in audit environments,
with emphasis on the continuous versus occasional use of drone technologies, (2) extending the technical adoption
architecture to include the use of drones, and (3) considering the types of drone usages amenable to both internal
and external audits. A specific architecture is proposed here to prototype inventory counts in large warehouses or
open-air inventories and that satisfies the suggested requirements. Additionally, this proposal adds value to the
current research by extending the discussion of technology adoption in the Alles, Kogan, and Vasarhelyi (2008)
paper to include the use of drones in many different audit environments by enumerating the usage types of drones in
audit settings and by considering the prototype of such a system.
Keywords: audit evidence; drones; internal and external auditing; audit automation; continuous auditing.
INTRODUCTION
R
ecently the FAA relaxed restrictions on the use of drones or Unmanned Aircraft Systems (UASs) for commercial purposes,
with some restrictions. Markets for commercial drone use are in the technology trigger phase of the Gartner Group’s Hyper
Cycle, with developments occurring in real estate, agriculture (farming), the film industry, insurance, and other areas.
Inspections and examinations are conducted with the assistance of drones in agriculture, heavy industry, and communications.
Currently in the U.S., commercial users are required to apply for and receive a Section 333 grant of exception from the FAA. The
FAA has issued a blanket grant of exception for all commercial flights below 400 feet for those users who have been granted a
Section 333 exception. Furthermore, commercial users of drones are required to obtain a drone pilot license and undergo continuing
professional education course work. Drones that are less than 50 pounds are considered for personal or leisure use and do not require
that the owners be pilots. However, these drones must be registered with the FAA and must be flown within sight of the drone
navigator at all times. There are also numerous local ordinances and restrictions about drone use in various municipalities.
Heisey et al. (2013) propose an initial software architecture to support nationwide commercial drone use. Alles, Kogan,
and Vasarhelyi (2008) propose a structure for implementing the technology of continuous auditing (CA). In this paper these
proposed structures are combined and extended to consider the additional requirements when adding drone technologies to the
audit. The Alles et al. (2008) structure focuses on adding CA software in ERP environments. This is extended by (1) defining
the use of drones in traditional audit and CA environments, emphasizing the continuous versus occasional use of drone
technologies; (2) extending the technical CA architecture to include the use of drones; and (3) considering the types of drone
The authors acknowledge the participants at the 2016 SET Research Workshop, the 2016 38th WCARS symposium, and the 2017 SET Midyear Meeting
for their comments and support.
Editor’s note: Accepted by Dan Palmon.
Submitted: October 2016
Accepted: February 2017
Published Online: February 2017
99
100 Appelbaum and Nehmer
TABLE 1
The Six Principal Activities of DSR Applied to the Application of Drones in Audit Activities
Principal Activity of DSR The Application of Drones in Audit Activities (as discussed in this paper)
Problem identification and motivation Other domains are using drones for inspection and observation to reduce costs, improve
efficiencies, and provide more efficient inspections. Why not the audit function?
Define the objectives of the solution The objective is to see whether drones may be integrated in the audit, given current
regulations.
Design and development of an artifact A process is proposed based on extant research and that allows auditors to adopt drones to
the extent desired (and allowed by the audit standards).
Demonstration of the solution A demonstration is proposed—that of a warehouse inventory. A framework is provided to
guide this future research application.
Evaluation of the solution The performance of the drone(s) will be evaluated for cost efficiencies and benefits/
drawbacks.
Communication of the results As this project progresses, papers will result that motivate future research.
usages amenable to both internal and external audits. A specific architecture is proposed here to prototype inventory counts in
large warehouses or open-air inventories and that satisfies the proposed requirements. This proposal adds value to the current
research by extending the discussion in the Alles et al. (2008) paper to include the use of drones in continuous audit
environments by enumerating the usage types of drones in audit settings and by considering the prototypes of such systems.
The methodology used in this paper is design science research (DSR), the science of the creation of information artifacts.
The paper follows the design science approach introduced by Hevner, March, Park, and Ram (2004) and Peffers, Tuunanen,
Rothenberger, and Chatterjee (2007). This paper also follows the discussion in Geerts (2011), which discusses the
methodology and its six major activities. Not all six activities need to be included in a single proposal of research (Peffers et al.
2007, 73–74). DSR expands to fit research projects that can span many researchers, articles, and decades of development. The
six principal activities are:
1. Problem identification and motivation.
2. Define the objectives of a solution.
3. Design and development of an artifact that meets (some of ) the solution objectives.
4. Demonstration of the solution.
5. Evaluation of the solution.
6. Communication of the problem and the solution (usually an article).
This paper is mainly concerned with the first three activities of DSR; those of identifying the problem, defining the
objectives, and developing and designing an artifact. Table 1 describes the six DSR activities as suggested in this paper for
auditor drone use.
The paper is divided into sections as follows: First, problem identification and motivation are discussed in the literature
review section. Defining the objectives of a solution are discussed in the sections on developing a framework for drone use in
auditing and the use of drones in audit automation and continuous auditing (CA) environments. A general design and
development of a solution is presented in the section on extending the technical/formal CA environment to include drones.
Possible future demonstrations of the solution are described in the section on the warehousing drone architecture prototype. The
paper then concludes and discusses future research.
LITERATURE REVIEW
When examining extant audit academic literature, it seems that there is no mention to date regarding the use of drones by
the profession or in research. However, this paper while in process has stimulated discussion of drones in an Artificial
Intelligence (AI) audit context (Issa, Sun, and Vasarhelyi 2016). A recent short AICPA blog discusses the potential use of
drones by CPA firms given the new federal regulations (Morriss 2016). In the realm of audit or accounting practitioner
publications, there appears to be one white paper about drones by PwC (2016a) in Poland and a short article in the Journal of
Accountancy (Ovaska-Few 2017). Regarding practitioner articles, blogs, and popular press about drones in other industries, the
coverage is extensive. This section begins by discussing the available practitioner publications on drone use that are relevant to
the framework, and then continues with a review of the audit literature regarding newer forms of audit evidence and audit
automation.
and cameras in smart phones and other personal devices. The technology of capturing the pixelated images and deriving
objective value from them has been a recent focus of research (Metaxas and Zhang 2013). Algorithms can process and interpret
dynamic and static images in an automated fashion. The field of image analysis has been exploding to address various business
objectives. Interviews and observations may be video recorded and subsequently processed and analyzed for verbal and
nonverbal clues.
TABLE 2
The Clarification of the Audit Procedures for Obtaining Audit Evidence
Based on SAS No. 106.20-.42 (AICPA 2006)
Procedure Method
Inspection of Records or Documents Pull samples of records and trace/verify/match
Inspection of Tangible Assets Physical inventory, walk through, open boxes
Observation Stand/sit with worker(s) and observe
Inquiry Written or oral interviews
Confirmation Verify account balances
Recalculation Extract and recalculate figures to verify
Re-performance Re-perform procedures to verify
Analytical Procedures Scanning and statistics
quantitative than the procedures in Table 2 and may require a reengineering of the audit evidence collection process (Alles et al.
2008). In a more electronic and continuous evidence collecting environment, the audit procedures stand in contrast to the earlier
traditional approaches, as shown in Table 3 (adapted from Teeter et al. [2010]).
Although many of these continual evidence collection processes are in place at such firms as Siemens Corporation (Alles et
al. 2006), physical observation and inquiry are still inferred processes in the continuous method. That is, the auditor is deducing
and not observing the actual activities, inventory at hand, and asset condition. These areas of the audit evidence collection
process, although enhanced by RFIDs and process flows, often require physical or manual observation to verify the relevant
assertions of existence, occurrence, and valuation (SAS No. 106.08, AICPA 2006). Any process that would directly connect
the auditor with the audit process is more reliable (SAS No. 106.08, AICPA 2006).
For Inspection of Tangible Assets, SAS No. 106.29 (AICPA 2006) declares that this process consists of a physical
examination of the assets. It may provide appropriate audit evidence about their existence, but not the rights and obligations. It
may assist in the determination of valuation by providing information about the asset(s’) condition. This inspection, if involving
actual inventory counts, requires observation or inquiry accompanying this activity. The auditor may want to open containers to
ascertain the amount of goods or ensure that they are not empty.
AU Section 331 (AICPA 1972) on Inventories provided similar guidelines regarding inventory procedures, whether to
sample inventory count observations or to do a complete count. When inventories are conducted manually by the entity, the
auditor should physically be there to observe, test, and inquire. If the entity has kept frequent perpetual inventory checks, the
auditor’s observations may occur either during or after the audit. Verification of automated inventory systems with RFID
TABLE 3
Audit Procedures Comparison
Modified from Teeter et al. (2010)
Procedure ‘‘Traditional’’ Method Continuous Method
Inspection of Records Pull samples of records and trace/verify/match Evaluate entire datasets in ERP
or Documents
Inspection of Tangible Physical inventory, walk through, open boxes RFID tagging
Assets
Observation Stand/sit with worker(s) and observe Use process mining to verify work flows
Inquiry Written or oral interviews Monitor processes and controls, identify process
violators for examination
Confirmation Verify account balances Link data streams
Recalculation Extract and recalculate figures to verify Monitor all data and run calculations
automatically at intervals desired
Re-performance Re-perform procedures to verify Automatically replicate all transactions and
identify exceptions
Analytical Procedures Scanning and statistics Filter real-time data with continuity equations
and statistics
FIGURE 1
Phases of the Audit where Drone Usage Is Suggested with Minimal Infrastructure Change
tracking follows this guidance. For such automated inventory systems, often the auditor may observe a sample of the inventory
count.
Observation (SAS No. 106.30, AICPA 2006) consists of looking at a process or procedure being performed by others. For
example, watching the process of inventory counting or controls processing constitutes observation. However, the observation
is only valid for the point in time that it occurs and is constrained by the fact that being observed may affect how the activities
are performed.
The Inventories (AICPA 1972) guidelines and Observation (AICPA 2006) as audit procedures support the assertions of
existence, occurrence, and valuation. Existence and occurrence are interchangeable and answer the questions if the assets really
exist at the balance sheet date or did a transaction or physical control actually transpire. Valuation involves validating the
condition of assets to substantiate their claimed economic value. For example, an auditor may want to observe the count of
widgets to verify the claimed amount or ascertain the condition of the roof of an office building owned by the entity to
substantiate its claimed economic value.
AU-C Section 501, Audit Evidence—Specific Considerations for Selected Items (AICPA 2015), expands on the process of
inventory observation that was summarized in Section 331 (AICPA 1972) of the standards. The auditor is to evaluate the
inventory procedures, observe the inventory, inspect the inventory, and perform test counts. If the physical inventory is
conducted at a date other than that of the financial statements, the auditor should perform the observation on another date and
then perform backtracking or forwarding audit procedures to calculate the inventory count. A similar process should occur if
the count occurs at a time that the auditor cannot be physically present. If the inventory is held by a third party, the auditor
should seek confirmations if physical inspection is not possible.
Based on the discussion in the ‘‘Literature Review’’ section and on the standards, drones appear to show promise in these
two areas of evidence collection: physical inspection and observations. Note that physical inspection and observations are
components of the larger audit process shown in Figure 1. In the typical engagement plan, drones could augment the audit team
promptly with inspections and valuations at the substantive testing phase and reoccurring cycle inspections during the interim/
continuous phase. Physical inspections consist of inventory verification and re-performance and asset evaluation. Observations
consist of watching employees and areas of interest, and they are closely related to the use of video cameras/stationary cameras.
It is helpful to regard inspection and observation as they relate to earlier research of manual and cognitive tasks that are
either routine or nonrepetitive (Issa et al. 2016). Tasks can be categorized as follows: routine manual, nonroutine manual,
routine cognitive, and nonroutine cognitive. Routine tasks require little judgement or thought processes, whereas cognitive
tasks require thought and analysis. Routine tasks are repeated frequently with little, or at least predictable, variation whereas
nonrepetitive tasks may have variation and unpredictability. The simplest and most easily automated tasks are those considered
to be manual-routine, and the most difficult to automate are the cognitive-nonrepetitive, as illustrated in Table 4.
TABLE 4
The Progression of Automation in the Context of Task Type
Adopted from Issa et al. (2016)
Process Task Attributes Manual Cognitive
Routine Easily automated Moderately hard to automate
Nonrepetitive Moderately hard to automate Hard to automate
Those tasks undertaken by the auditor that are manual and routine could easily be automated to supplement the auditor in
fulfillment of audit tasks. However, even though tasks such as inventory observation and verification may seem to be routine
and ordinary, the auditor should verify the veracity and accuracy of the drone video feeds and subsequent software analysis.
Ideally, the automation of these tasks could free the auditor to engage in more complex and challenging tasks that are cognitive
and nonrepetitive (Oldhouser 2016).
Manned (piloted) drones could be considered initially as an extension of a physical auditor, with unmanned (autonomous)
drones eventually assisting as continuous evidence collectors, pending audit standards revision—see Table 5. In this paper, a
manned drone is a drone that is piloted by a person online either nearby or remotely. An unmanned drone is a drone that is not
piloted at all—it is completely autonomous, a bot drone. If the standards would allow a bot drone to operate independently as
an extension of the auditor, when reexamining AU-C Section 501 (AICPA 2015), the paragraphs that address when and where
the auditor should be present for inventory observations will become superfluous, as either an unmanned or manned drone
could be present as an extension of the auditor, regardless of the human auditor’s location at that time.
Furthermore, auditor safety would cease to be an issue at observations, which could be regarded as manual-nonrepetitive
tasks. Specifically, by using drones the auditor could feasibly never miss an inventory count—the auditor could be at two places
at once, particularly if the site of the inventory count is unsafe.
TABLE 5
Physical Inspection Standards from AU-C Section 501. A20-30 (AICPA 2015) and Drones
where ‘‘Manned’’ Drones Are Piloted and ‘‘Unmanned’’ Drones Are Autonomous
Current Physical Audit Audit Procedure with Manned Audit Procedure with
Procedure Drone Unmanned Drone
Physical Inventory:
1. Evaluate Verifying that certain Drone could capture images of Drone could capture images of
procedures and controls are in flow charts and read/analyze flow charts and read/analyze
compliance. results. results.
2. Observe Observe/watch the procedure. Drone could observe and watch Drone could observe and watch
the procedure, as directed or the procedure based on video
piloted by the auditor. input and sensor tracking.
3. Inspect Visually and/or physically Drone could observe the worker Drone could observe and watch
inspect the inventory. physically inspecting or the inspection based on video
observe/view the inventory input and sensor tracking.
condition itself.
4. Perform May need to recount inventory; Drone could recount inventory Drone is recounting inventory
re-perform inventory if needed—data feed all the time—data feed
numbers. automatically into audit app automatically into audit app
that re-performs the process. that re-performs the process.
Occurrence:
1. Observe Watch process or control Drone may watch process or Drone could watch and follow
activity. control activity. based on video input and
analysis.
Valuation:
1. Inspect Visually inspect the asset for Visually inspect the asset for Drone could visually inspect
impairment. impairment, safety is not an based on video feed and GPS
issue. sensors.
FIGURE 2
Audit Automation
Both external and internal auditors could advance the use of drones in inventory, observation, and valuation. These are the
areas where drones may easily augment auditor tasks with minimal disruption and infrastructure development. The drones may
be regarded as flexible and mobile cameras, not unlike those that are already mounted typically in numerous locations in most
warehouses. Not all audit tasks can or should be assisted by drone evidence collection. The ease of drone adoption for an audit
task would depend on the task type, with the cognitive-nonrepetitive tasks being the last to automate. The audit objectives may
be different—the external auditor is merely verifying evidence to substantiate the eventual audit opinion, and the internal
auditor is seeking evidence that will support an evaluation of operational efficiency.
Drones could not only inspect inventory regarding existence and condition, they could also observe inventory processes.
Video feeds could be processed with recognition software and be evaluated by the auditor (Issa et al. 2016). Requests for
opening containers could be texted by the auditor or drone pilot who is guiding the drone. Observation could be continual for
an automated drone, thereby expanding the scope of this examination to an automated routine task from a manual routine task
(Issa et al. 2016). Both contexts for drone applications are expanded in the sections that follow.
FIGURE 3
Audit Procedures, Audit Automation, and CA
reports are already captured and integrated in functions that are themselves already automated. Additional factors include the
increasing complexity of business transactions and the increased emphasis on the risks associated with the use of information
for strategic decision-making purposes across the enterprise. Value is also derived from the audit objectives themselves such as
getting the audit procedure performed more quickly or being able to test entire populations thereby avoiding some of the pitfalls
of sampling. Automation also adds value by allowing the use of real-time alarms that can be used to help mitigate audit risk.
Automation also allows evidence to be aggregated across procedures to give a bigger picture view of the current sufficiency and
competence of the evidence collected through the automated portion of the audit program.
The next quadrant is the Development component of the Alles et al. (2008) framework. The first component in the
framework in this quadrant is the use of senior executive champions or supporters to back the audit automation projects. These
champions should identify and engage project stakeholders including business process owners, internal auditors, and IT
personnel. Verification of the proposal should be completed by an audit professional who is external to the development team.
The next two processes of the Development quadrant determine a critical divide between audit automation and continuous
auditing. Formalization is a process by which audit procedures can be reduced to descriptions that are capable of automation. If
these procedures are automated and are run in time to support audit decision making, then they are capable of being CA. To
create as many opportunities as possible to develop a CA system, the audit process itself needs to be reengineered to collect
formalizable procedures together and to separate them from the parts of the audit program that will remain manual.
The third quadrant is Implementation. The first component is the architecture that is further broken down into structure
(integrated or distributed), access (direct or intermediated), and platform (common to the business or separate). Since the audit
software is most likely going to be hosted on its own system and not the enterprise system, the audit hardware and software
must be carefully secured. This includes security from super users at the business since the platform will likely be run by the
business IT to reduce network bottleneck issues and network security concerns. Logical access will need to be carefully
controlled and logged. The software will tend to fall either into the category of continuous control monitoring or continuous
data assurance. Alles et al. (2008) clarify further that this union of the two software categories defines CA.
The final quadrant, Management, consists of baseline monitoring and scalability. Baseline monitoring develops a set of
baseline measurement norms for the automated audit process that can then be used to check on changes in the underlying
expected pattern. Scalability refers to the ability to design collections of parameters that are useful for many different audit
automation uses and then leverage the generic collections in designing other audit automation solutions.
Before discussing an extension of the framework to include drone technologies, a few additional concepts should be
introduced that are necessary for this process, Figure 3 clarifies the relationship between audit procedures as discussed in the
previous section and audit automation (automated audit procedures) and continuous auditing. Audit procedures include both
manual and automated procedures. Not all automated audit procedures rise to the level of continuous auditing. Figure 4
illustrates the relationship between audit automation, audit drone technologies, and CA. The figure depicts audit drone
technologies and CA as subsets of audit automation, with other types of audit automation as a filler for areas that are neither
drones nor CA, but are still classified as audit automation. Finally, Figure 5 illustrates the architecture and components of audit
FIGURE 4
Audit Drones and Audit Automation
drone technologies as used hereafter. They consist of a mandatory flight and maneuverability component, mandatory video or
camera, mandatory data storage, the optional ability to manipulate objects, and other sensors.
FIGURE 5
Drone Architecture
FIGURE 6
Audit Drone Automation
development of audit drone automation is more of realizing efficiencies of the internal resources. The drones are used to
enhance and extend the auditor’s ability to observe, inspect, and evaluate. Drones will be used in situations where this
enhancement of auditors’ abilities can be successfully leveraged to extend scarce audit staff and provide additional value to the
enterprise from the extensions. Formalizations are embedded in the drone technology itself: stabilizers, video capabilities,
storage, etc. At this level of drone implementation, reengineering of the audit plan is not necessary since only certain aspects of
the audit processes are being automated.
In the third quadrant, Implementation, there are also some notable refinements of the original audit automation framework.
The architecture is really the drone technology as a drone platform. Few audit firms or internal audit departments will be
modifying, let alone building, their own drones. So developments in available drone architectures should be followed in a broad
way by the audit function, but the auditor is generally more concerned with the available sensors on the drone since these are
collecting the audit evidence. The sensors are the means for downloading or streaming the evidence.
Security issues are still important to follow, but the drone will be operated by or under the management of the auditor.
Potential hijacking of the drone or interference with its data feed are possibilities but probably unlikely at present. The audit
function must track emerging drone security issues nonetheless. The software component in the original framework becomes a
procedure development component here. The audit procedure for using the drone in the specific audit situation needs to be
developed in a careful and controlled manner. Discussion of this is deferred until the next section when we present a
warehousing drone prototype.
The Management quadrant is also modified to a considerable extent. Baselining and scalability are not so important with
drones because they are not operating as controls themselves but as audit procedures. An exception to this is possible if a
continuous unmanned drone is deployed, in which case baselining of the situation in its normative state is still important.
Scalability will also not be an issue in this paper in the way drones are deployed, since we are considering the use of individual
drones for specific procedures. It is possible to develop concepts of deploying fleets of drones, but that is suggested for future
research. One important component of managing audit drones is the overall oversight of the drone projects that are being
developed and deployed. Here we consider oversight in the frame of a portfolio of audit automation development efforts and
their implementation over time. Management controls from the COBIT framework are useful here where the audit function is
managing its own audit operations. The other component here, which completes the framework, is assuring incremental audit
value from the use of drones. This will require value metrics that again can be developed with insights from the COBIT
framework. Finally, these modifications to the automation framework provide the objectives of a successful audit drone
FIGURE 7
Projected Steps toward Integration of Drones in the Audit
automation project solution in the sense of design science research. In the next section these objectives are used to construct an
artifact, a warehouse drone architecture prototype.
getting some insights on minimal drone capacities, video resolution, battery, control console characteristics, etc. With
experience, the choice of the drone architecture will become more routine and predictable. The security issues should be
minimal at this stage. The drone equipment must be physically secured when not in use. Procedure development will be
matched to the extent of the video evidence that the auditor has planned to get from the use of the drone. The flight plan around
and through the warehouse should be formulated, as well as procedures for collecting enough evidence to assess the condition
of the inventory.
Because drones are flexible and scalable, the audit team could purchase or rent a limited number of drones and use them
in a small, segregated portion of the warehouse, on an experimental or trial basis utilizing the framework processes suggested
here. Or the audit team could contract a drone consultant to pilot the drones in the same experimental fashion. In any event,
when this small trial succeeds in demonstrating the viability for using drones as an extension of the auditor for inspections,
the audit team can then devote additional resources toward expanding their drone program. If the trial fails, the auditors may
easily dispose of the drones at minimal expense and return to manual counts because they did not make huge infrastructure
changes.
The Management quadrant includes the oversight of the warehouse drone project as part of the portfolio of projects that the
audit function is managing. If the project is coming in over budget or the development time is more than planned, then there
should be a mechanism to potentially end the project. Once the project has been implemented, the metrics designed to measure
its value should be taken and assessed to see whether the project is delivering the value additions it was designed to deliver.
Successes should be recorded in the audit knowledge base. Failures should also be recorded. Design changes to the procedures
or changes in the value metrics can be considered in failure situations before a project is scrapped.
could increase or decrease audit risk, depending on the degree of controls compliance. This issue is touched upon here in this
paper but should be explored in future research.
It should be noted that when drones function as sensor or RFID tag readers, drones do not resolve the issues that plague
sensor readings. That is, RFID tags may not be tagging everything and, also, they may not tag or correlate with the correct item.
However, drones may ease the difficulty of verifying the RFID readings either at a first pass or at a confirmatory pass.
Additionally, the development of appropriate metrics to capture value gain is critical. Once many projects are
implemented, testing the realization of the value gain is also critical. A broader exploration of the audit automation framework
will also be necessary in a rapidly developing audit automation universe. Development of audit artifacts using the design
science research methodology to guide project development will help assure a cohesive development process and a coherent
discussion of developments across academic and professional fields. By observing these suggested best practices for adoption
of automation, drones could really invade the audit profession.
REFERENCES
Alles, M., G. Brennan, A. Kogan, and M. A. Vasarhelyi. 2006. Continuous monitoring of business process controls: A pilot
implementation of a continuous auditing system at Siemens. International Journal of Accounting Information Systems 7 (2): 137–
161.
Alles, M. G, A. Kogan, and M. A. Vasarhelyi. 2008. Audit Automation for Implementing Continuous Auditing: Principles and Problems.
Working paper, Rutgers, The State University of New Jersey.
American Institute of Certified Public Accountants (AICPA). 1972. Inventories. Statement on Auditing Standards No. 1. AU Section 331.
New York, NY: AICPA.
American Institute of Certified Public Accountants (AICPA). 2006. Audit Evidence. Statement on Auditing Standards No. 106. AU
Section 326. New York, NY: AICPA.
American Institute of Certified Public Accountants (AICPA). 2015. Audit Evidence—Specific Considerations for Selected Items.
Statement on Auditing Standards No. 122. AU-C Section 501. New York, NY: AICPA.
Banker, S. 2016. Drones and Robots in the Warehouse. Available at: https://www.forbes.com/sites/stevebanker/2016/06/24/drones-and-
robots-in-the-warehouse/#77cac8356c3b
Benson, J. 2015. Monsanto’s Airborne Pesticide Drones Coming Soon: FAA Approves Unmanned, Poison-Spraying Helicopters.
Available at: http://www.naturalnews.com/050197_pesticide_drones_chemical_agriculture_FAA.html
Boughtin, J. 2016. A broader view of drones. Realtor Magazine (May/June): 10–15.
Brown-Liburd, H., and M. A. Vasarhelyi. 2015. Big data and audit evidence. Journal of Emerging Technologies in Accounting 12 (1): 1–
16. doi:10.2308/jeta-10468
Christensen, C. 2013. The Innovator’s Dilemma: When New Technologies Cause Great Firms to Fail. Boston, MA: Harvard Business
Review Press.
Crovitz, L. G. 2016. While Amazon Waits, Drones Fly. Available at: https://www.wsj.com/articles/while-amazon-waits-drones-fly-
1466976049
Federal Aviation Administration (FAA). 2016. Summary of Small Unmanned Aircraft Rule (Part 107). Available at: http://www.rtca.org/
files/Part_107_Summary.pdf
Foy, H. 2016. PwC to Deploy Drone Army. Available at: http://www.irishtimes.com/business/technology/pwc-to-deploy-drone-army-1.
2640692
Geerts, G. L. 2011. A design science research methodology and its application to accounting information systems research. International
Journal of Accounting Information Systems 12 (2): 142–151. doi:10.1016/j.accinf.2011.02.004
Hammer, M. 1990. Reengineering work: Don’t automate, obliterate. Harvard Business Review (July/August): 104–112.
Heisey, C. W., A. G. Hendrickson, B. J. Chludzinski, R. E. Cole, M. Ford, L. Herbek, M. Ljungberg, Z. Magdum, D. Marquis, A.
Mezhirov, J. L. Pennell, T. A. Roe, and A. J. Weinert. 2013. A reference software architecture to support unmanned aircraft
integration in the national airspace system. Journal of Intelligent & Robotic Systems 69 (1/4): 41–55. doi:10.1007/s10846-012-
9691-8
Hevner, A., S. T. March, J. Park, and S. Ram. 2004. Design science in information systems research. Management Information Systems
Quarterly 28 (1): 75–105.
Issa, H., T. Sun, and M. A. Vasarhelyi. 2016. Research Ideas of Artificial Intelligence in Auditing: The Formalization of Audit and
Workforce Supplementation. Working paper, Rutgers, The State University of New Jersey.
Metaxas, D., and S. Zhang. 2013. A review of motion analysis methods for human nonverbal communications computing. Image and
Vision Computing 31 (6/7): 421–433. doi:10.1016/j.imavis.2013.03.005
Mims, C. 2016. Drones Have a Role in Your Company’s Future. Available at: https://www.wsj.com/articles/drones-have-a-role-in-your-
companys-future-1467000061
Morriss, J. 2016. Drones on the Horizon for CPA Firms in 2017. Available at: http://blog.aicpa.org/2016/09/drones-on-the-horizon-for-
cpa-firms-in-2017.html#sthash.Ug1UWSIy.dpbs
Oldhouser, M. C. 2016. The Effects of Emerging Technologies on Data in Auditing. Doctoral dissertation, University of South Carolina.
Ovaska-Few, S. 2017. Drones Set To Invade Accounting Profession. Available at: http://www.journalofaccountancy.com/newsletters/
2017/jan/drones-invade-accounting-profession.html.
Palazzi, C. E. 2015. Drone indoor self-localization. In Proceedings of the First Workshop on Micro Aerial Vehicle Networks, Systems, and
Applications for Civilian Use, 53–54, Florence, Italy, May 18.
Parasuraman, R., T. B. Sheridan, and C. D. Wickens. 2000. A model for types and levels of human interaction with automation. IEEE
Transactions on Systems, Man, and Cybernetics. Part A, Systems and Humans 30 (3): 286–297. doi:10.1109/3468.844354
Pasztor, A., and G. Wells. 2016. As Drone Rules Near, More Debate Looms. Available at: https://www.wsj.com/articles/as-drone-rules-
near-more-debate-looms-1466379413
Peffers, K., T. Tuunanen, M. A. Rothenberger, and S. Chatterjee. 2007. A design science research methodology for information systems
research. Journal of Management Information Systems 24 (3): 45–77. doi:10.2753/MIS0742-1222240302
PricewaterhouseCoopers (PwC). 2016a. Global Market for Commercial Applications of Drone Technology Valued at over $217 bn.
Available at: http://press.pwc.com/News-releases/global-market-for-commercial-applications-of-drone-technology-valued-at-over–
127-bn/s/AC04349E-C40D-4767-9F92-A4D219860CD2
PricewaterhouseCoopers (PwC). 2016b. Clarity from Above. Available at: http://www.pwc.pl/en/publikacje/2016/clarity-from-above.html
Public Company Accounting Oversight Board (PCAOB). 2010. Audit Evidence. PCAOB Auditing Standard No. 15. Washington, DC:
PCAOB.
Schutzer, D. 2015. Do Drones Have a Role in Financial Services? Available at: http://fsroundtable.org/do-drones-have-a-role-in-
financial-services/
Srivastava, R. P., and G. R. Shafer. 1992. Belief-function formulas for audit risk. The Accounting Review 67 (2): 249–283.
Swedberg, C. 2014. Iron Mountain to Introduce RFID-Ready Boxes for Records Storage. Available at: http://www.rfidjournal.com/
articles/view?12386/&utm_medium%3Dnewsfeed_rss
Teeter, R. A., M. G. Alles, and M. A. Vasarhelyi. 2010. The remote audit. Journal of Emerging Technologies in Accounting 7 (1): 73–88.
Vasarhelyi, M. A. 2013. Formalization of standards, automation, robots, and IT governance. Journal of Information Systems 27 (1): 1–11.
doi:10.2308/isys-10347
Vasarhelyi, M. A., and F. B. Harper. 1991. The continuous audit of online systems. Auditing: A Journal of Theory & Practice 10 (1):
110–125.
Warren, J. D., Jr., K. C. Moffitt, and P. Byrnes. 2015. How Big Data will change accounting. Accounting Horizons 29 (2): 397–407.
doi:10.2308/acch-51069
Yoon, K., L. Hoogduin, and L. Zhang. 2015. Big Data as complementary audit evidence. Accounting Horizons 29 (2): 431–438. doi:10.
2308/acch-51076