Control testing
Controls must be properly designed to be effective. In an ethical audit, control design focuses on whether the controls apply to all cases or if the controls are created with intentional overrides and loopholes. The audit team can test for areas where controls are designed with a way for management to override or bypass them and for times when controls are ignored completely. For example, purchasing is an area where unethical acts can occur. In a control design review, auditors should look for controls around gathering bids, making selections, conducting IT security assessments, and negotiating contracts. If the policies allow for deviation from the policy, the team should consider these as a possible way to override the control. Consider this example. A purchasing control states, “All software purchases over $250,000 require the purchasing team to issue a request for proposals (RFPs). At least three RFPs should be considered. The RFP process is not required if the team believes only one provider can meet their needs.”
Testing the control with an ethical audit perspective shows the control is designed with several loopholes:
- The materiality threshold is high, as many purchases will be below $250,000.
- The dollar amount does not consider whether this is a one-time purchase or the total contractual agreement from a recurring charge tied to a subscription.
- The amount does not specify if this includes only the software or if services are included.
- The control provides an override for skipping the RFP if the team thinks only one vendor meets their needs without requiring any due diligence.
The control is poorly designed, as it allows the organization to choose vendors without considering alternatives. Unethical managers could award contracts to friends disguised as the only choice available. They could also commit the organization to contracts well above the intended material threshold and still meet the criteria design of the control as written.
The next step in testing the control, the team could then gather an inventory of critical applications currently in use and tie these back to contracts. As a test procedure, they can test the following attributes:
- What was the total cost for the software, including all services and consulting, for the first year and the total cost of the contract?
- How many of these purchased systems have a total cost within the contract period above the threshold?
- Were any systems purchased without an RFP? What was the rationale?
- Is due diligence required by an independent team when claiming the sole source exemption?
- Are purchases that bypass the intent of the control coming from the same department or individuals?
These types of exceptions can point to a culture willing to make unethical choices. Controls like this one are designed to allow people to intentionally bypass the point of the control. Often, the reason given for controls like this is to allow the organization some flexibility, to make decisions quickly, and to allow managers to get business done. In reality, this allows for bad practices and sends the message that the organization will allow managers to bend the rules if it serves their needs.
Transactional testing
In an ethical audit, we can test for fraud red flags to indicate that unethical practices may be present. Common fraud red flags also appear in transactional testing, and this level of detailed testing can expose larger issues. Audit teams can quickly test large data populations using data analytics to look for red flags. However, the existence of a red flag is only an indicator of the potential for fraud.
Using the purchasing example, we could test for payments made to software companies. Certain payments made for software can be classified as either an operating expense or a capital expense, depending on the nature of the software and expense type. Suppose we notice that all software expenses are capitalized. In that case, this is a red flag since many software providers offer software as a service (SaaS), and SaaS subscription payments are an operating expense. Some companies attempt to capitalize all software expenses to inflate assets and overstate profitability.