Auditor
Internal controls and fraud risk questions
171 questions on Internal controls and fraud risk for auditors, easiest first.
Easy 54
- One person doing everythingeasy
- The fraud triangleeasy
- Type of control: bank reconciliationeasy
- Test of controls or substantive testeasy
- Reporting a significant control deficiencyeasy
- Payroll fraud warning signeasy
- Lapping fraudeasy
- What a walkthrough iseasy
- Audit trail in Indian accounting softwareeasy
- The five COSO componentseasy
- Picking the preventive controleasy
- Recording sales in the right periodeasy
- The maker-checker principleeasy
- Why only reasonable assuranceeasy
- Internal audit in the Three Lines Modeleasy
- An automated controleasy
- What makes a control "key"easy
- Purpose of a DoA matrixeasy
- Safeguarding cash and stockeasy
- Checking invoice number gapseasy
- What a vigil mechanism iseasy
- Why mandatory leave helpseasy
- A control that finds errors latereasy
- Objective or activityeasy
- Why asking is not testingeasy
- What reperformance meanseasy
- The main ITGC areaseasy
- Purpose of an access revieweasy
- Testing access for leaverseasy
- An input edit checkeasy
- Testing a once-a-year controleasy
- What counts as a deviationeasy
- SOC 1 or SOC 2easy
- Type 1 or Type 2easy
- Defining a material weaknesseasy
- Backups that were never restoredeasy
- A failed overnight jobeasy
- Developers moving code to productioneasy
- Tolerable deviation rateeasy
- The three kinds of occupational fraudeasy
- Most common versus most costlyeasy
- How fraud is usually foundeasy
- What skimming iseasy
- Clocking in for a friendeasy
- Declaring a conflict of interesteasy
- Classifying a kickbackeasy
- A common behavioural red flageasy
- Fraud or erroreasy
- What professional skepticism meanseasy
- Counting stock through the yeareasy
- Claiming the same bill twiceeasy
- A gifts registereasy
- Why assess fraud riskeasy
- Stopping altered chequeseasy
Medium 65
- Relying on internal auditmedium
- Spotting an IT general controlmedium
- Compensating for limited staffmedium
- Reporting fraud under the Companies Actmedium
- Spotting an entity-level controlmedium
- Working out residual riskmedium
- Good design, poor operationmedium
- A review that is too coarsemedium
- The COSO principle on fraudmedium
- Getting around approval limitsmedium
- An email asking to change bank detailsmedium
- Relying on a system reportmedium
- Ongoing or separate monitoringmedium
- Designing a stock countmedium
- Controlling cash at a retail storemedium
- A credit limit blockmedium
- Duplicates that slip pastmedium
- Before claiming input tax creditmedium
- A control that costs too muchmedium
- Directors and internal financial controlsmedium
- Limits of self-assessmentmedium
- Journals posted at odd timesmedium
- Applying a price tolerancemedium
- Audit committee and controlsmedium
- Sampling a monthly controlmedium
- One failure in the samplemedium
- Testing at interimmedium
- Relying on last year's automated testmedium
- How to test an automated matchmedium
- CUECs in a SOC reportmedium
- A SOC report that ends earlymedium
- A carved-out data centremedium
- Where to pick changes frommedium
- An access review with no removalsmedium
- Emergency changesmedium
- A shared "accounts" loginmedium
- Limits of watching a controlmedium
- When a fixed control can be testedmedium
- Getting to the root causemedium
- Judging how bad a deficiency ismedium
- What makes a sample biggermedium
- An automated control and master datamedium
- The reviewer was on leavemedium
- The list given for the access reviewmedium
- A middleman companymedium
- Signs of bid riggingmedium
- A cashier with many voidsmedium
- Claims just under the limitmedium
- Controlling company cardsmedium
- Who to interview firstmedium
- Keeping evidence usablemedium
- Looking at a suspect's laptopmedium
- Handling an anonymous tipmedium
- Insuring against employee theftmedium
- Two employees, one bank accountmedium
- Overtime that looks oddmedium
- Good stock sold as scrapmedium
- Working out an overpaymentmedium
- An agent who wants offshore paymentmedium
- Analytics on invoice traitsmedium
- Thinking like a fraudstermedium
- Why have a fraud response planmedium
- A vendor back from the deadmedium
- Refunds going to one cardmedium
- Invoices older than their POmedium
Hard 52
- A fraud risk that is always presenthard
- Required responses to management overridehard
- An undisclosed related party purchasehard
- Sales spike then credit noteshard
- Benford’s law in audit analyticshard
- Reporting on internal financial controlshard
- When two people colludehard
- Evidence a review really happenedhard
- A compensating control that falls shorthard
- A shared superuser accounthard
- Residual risk above appetitehard
- Controls with three finance staffhard
- A report whose logic changedhard
- Finding a shell vendorhard
- A preparer who can approvehard
- A control mapped to the wrong riskhard
- When the CEO says skip ithard
- Controls over a key spreadsheethard
- The worst access combinationhard
- Overrides nobody reviewshard
- Controls across an ERP migrationhard
- Small deficiencies that add uphard
- A weakness with no error foundhard
- When the auditor finds the errorhard
- Change management failedhard
- Too many people with accesshard
- A control that never ranhard
- Sample rate below, upper limit abovehard
- An exception in the SOC reporthard
- A SOC report for the wrong systemhard
- Using management's testinghard
- Controls in a SaaS ERPhard
- When a test of one is enoughhard
- Data lost between systemshard
- Is it a material weakness?hard
- Emergency superuser accesshard
- Reserves released when neededhard
- Expenses moved to the balance sheethard
- Confirming cash directlyhard
- Money that goes round in a circlehard
- Bringing in legal counselhard
- Offering leniency in an interviewhard
- Before confronting a suspecthard
- When the CFO is suspectedhard
- Too many fraud alertshard
- Corporate liability for bribes in Indiahard
- Management refuses confirmationshard
- Customers who confirm fake saleshard
- A video call from the "CEO"hard
- Money counted in two bankshard
- An approver who clicks too fasthard
- Counting all branches at oncehard