Guide-linked quiz · Hard Level
Accounting Fraud Detection with Machine Learning Quiz
Learn how statistical screens and machine learning can flag accounting patterns, why an alert is not proof, and how auditors evaluate detection systems.
Question 1 of 8
What does a high fraud-risk model score establish?
Preview every question8 questions
Answers and explanations appear as you take the quiz.
- What does a high fraud-risk model score establish?
- A score flags a pattern for investigation, not proof
- A pattern is suspicious only if a model labels it fraud
- A high score confirms that a specific journal entry was intentionally falsified
- The model score is sufficient evidence for an accusation
- When is Benford’s law a poor fit for a dataset?
- Benford’s test works equally for assigned invoice IDs
- A restricted amount range makes naturally occurring digit assumptions stronger
- Assigned identifiers and constrained prices may not fit Benford assumptions
- A digit mismatch proves that someone fabricated transactions
- Why can accuracy be misleading for rare fraud detection?
- A model with high accuracy must have found enough rare fraud cases
- Majority-class accuracy can hide missed rare cases
- Class imbalance guarantees high recall
- Majority predictions necessarily identify rare manipulation
- What does a Beneish M-score provide?
- A deterministic cutoff with the same interpretation for every industry and period
- An M-score proves intentional falsification
- The M-score replaces supporting audit evidence
- The M-score is a screening signal, not a fraud finding
- Why use time-aware evaluation splits for fraud models?
- Time splits reduce leakage from future information
- Randomly mix future and past cases to simulate deployment
- Use later filing revisions as features because they improve historical fit
- Train on later labels to predict earlier decisions
- Which metric estimates the share of inspected alerts that are relevant within a fixed review capacity?
- Recall across all cases without considering the number staff can inspect
- Overall accuracy alone predicts review workload
- Precision at review capacity informs alert workload
- AUC tells exactly how many staff hours are needed
- What should an investigator do with a flagged journal entry?
- A flagged entry should be removed before audit review
- Trace an entry to documents and assess business context
- Compare only with peer companies and skip the underlying source records
- An unusual entry is proof of intent
- Why might a legitimate transaction appear anomalous?
- A historical average match makes a transaction valid regardless of context
- A baseline deviation always indicates an error in the training data
- Only misconduct produces deviations from a baseline
- Legitimate activity can be unusual relative to a baseline
Keep testing yourself
More quizzes picked for your level.