Tax Audit & Compliance

Chapter 10
Analytical Procedures and Tax Data Analytics

Advance Diploma in Tax Consultancy Management
Tax Audit & Compliance   •   Advance Diploma

Analytical Procedures and Tax Data Analytics

Introduction and Context

Tax audit is not limited to checking whether individual invoices, receipts, or ledger entries exist. A modern tax audit also asks whether the reported information is economically plausible, internally consistent, complete, and comparable with relevant evidence. Analytical procedures provide a structured way of answering these questions.

Analytical procedures involve the evaluation of financial and non-financial information through analysis of plausible relationships, comparisons, ratios, trends, reconciliations, benchmarks, and exception reports. Tax data analytics extends this approach by using spreadsheets, databases, statistical techniques, visualisation tools, and automated tests to examine large volumes of transactions.

The purpose is not to prove that every unusual result represents non-compliance. An anomaly is an indicator for further investigation, not a conclusion. A fall in gross margin may result from genuine price competition, a change in product mix, or an accounting error. Similarly, a large input tax credit claim may be legitimate, incorrectly classified, duplicated, or supported by fictitious documentation. Professional judgement is therefore essential.

In practice, analytical procedures support three stages of tax work:

  1. Planning: identifying high-risk areas and allocating audit effort.
  2. Substantive testing: selecting transactions and balances for detailed examination.
  3. Completion and reporting: assessing whether unresolved differences affect the reliability of the tax return.

Learning Objectives

By the end of this chapter, the learner should be able to:

  • explain the role and limitations of analytical procedures in tax compliance;
  • calculate and interpret important tax and financial ratios;
  • analyse trends, benchmarks, exceptions, and unusual transactions;
  • perform reconciliations between accounting records, tax returns, invoices, and third-party information;
  • use data visualisation to communicate risk clearly;
  • distinguish an anomaly, an error, an indicator, and an established tax finding;
  • design an evidence-based investigation while respecting confidentiality and data-governance requirements; and
  • evaluate the use of automation and artificial intelligence in tax analytics.

1. The Nature and Purpose of Analytical Procedures

Analytical procedures compare recorded or reported amounts with expectations. An expectation may be based on:

  • prior-period results;
  • budgets or management forecasts;
  • industry or peer benchmarks;
  • operational drivers, such as units sold or employee numbers;
  • relationships within the financial statements;
  • tax return information;
  • customs, payroll, banking, or third-party records; or
  • independently reconstructed amounts.

The strength of an analytical procedure depends on the quality of the expectation, the reliability of the data, the precision of the comparison, and the auditor’s understanding of the business.

A useful analytical procedure has four elements:

ElementQuestion addressed
ExpectationWhat amount or relationship should reasonably exist?
ComparisonHow does the reported result differ from the expectation?
ThresholdWhat size or pattern of difference requires attention?
InvestigationWhat evidence explains or confirms the difference?

For example, if a retailer reports sales of CU 12 million and cost of sales of CU 10.8 million, the gross profit is CU 1.2 million. The gross profit margin is calculated as follows:

Gross profit margin = (Sales − Cost of sales) ÷ Sales × 100

Thus:

Gross profit margin = (12,000,000 − 10,800,000) ÷ 12,000,000 × 100 = 10%

Here, CU means currency units. The formula assumes that sales and cost of sales are measured on a consistent basis and relate to the same period. A 10% margin is not inherently suspicious. It becomes meaningful only when compared with prior years, product mix, industry conditions, and supporting records.

Analytical procedures may be used at different levels:

  • High-level review: total turnover, tax payable, and major expense categories.
  • Account-level analysis: revenue by product, expenses by supplier, or input tax by tax code.
  • Transaction-level testing: duplicate invoices, unusual dates, round amounts, or transactions just below approval thresholds.
  • Network analysis: links between taxpayers, directors, addresses, bank accounts, or suppliers.

2. A Risk-Based Analytical Framework

A disciplined tax analytics process prevents the auditor from treating every unusual item as equally important. A practical framework is shown below.

Step 1: Define the tax question

The question should be specific. Examples include:

  • Is declared sales turnover complete?
  • Are input tax credits supported by valid purchases?
  • Are related-party payments correctly disclosed?
  • Does payroll expense agree with employment and withholding records?
  • Are expenses deductible under the applicable tax law?

Step 2: Identify relevant data

Potential sources include the general ledger, trial balance, sales and purchase registers, tax returns, invoice files, bank statements, payroll systems, inventory records, point-of-sale data, customs declarations, and third-party confirmations.

Step 3: Assess data quality

Before analysis, check whether the data is complete, accurate, consistently coded, and free from unexplained gaps. Important checks include:

  • record counts compared with control totals;
  • date range and period completeness;
  • duplicate transaction identifiers;
  • missing tax identification numbers;
  • invalid or inconsistent tax codes;
  • negative or zero values where they are not expected; and
  • agreement between subledgers and the general ledger.

Step 4: Establish an expectation

The expectation should be transparent and reproducible. It may be a ratio, trend, benchmark, independent calculation, or reconciliation.

Step 5: Identify exceptions

Exceptions can be identified using absolute differences, percentage differences, rule-based filters, statistical outliers, or combinations of indicators.

Step 6: Investigate and corroborate

The auditor should obtain explanations and supporting evidence. An explanation is not automatically evidence. It must be assessed against contracts, invoices, delivery records, payment information, correspondence, and other reliable sources.

Step 7: Conclude proportionately

The conclusion should distinguish among:

  • no exception identified;
  • exception explained and supported;
  • exception requiring additional testing;
  • probable error requiring correction; and
  • suspected deliberate non-compliance requiring escalation under applicable law and professional procedures.

3. Ratios Used in Tax Analysis

Ratios convert absolute amounts into relationships that can be compared across time, entities, or business units. They are useful because size differences can otherwise obscure risk.

3.1 Tax-to-turnover ratio

Tax-to-turnover ratio = Tax reported ÷ Taxable turnover × 100

This ratio may indicate changes in the effective tax burden. Interpretation depends on tax rates, exemptions, losses, incentives, timing differences, and the composition of taxable and non-taxable income. It should not be confused with the statutory tax rate.

3.2 Effective income tax rate

Effective tax rate = Income tax expense ÷ Accounting profit before tax × 100

The formula assumes that income tax expense and accounting profit relate to the same reporting period. The result may differ from the statutory rate because of permanent differences, temporary differences, tax losses, exempt income, credits, and uncertain tax positions.

For tax compliance, the auditor may also compare taxable income with accounting profit:

Tax reconciliation difference = Accounting profit before tax − Taxable income

The sign and interpretation depend on the jurisdiction’s tax rules and the presentation convention used in the tax computation.

3.3 Input tax credit ratio

Input tax credit ratio = Eligible input tax claimed ÷ Taxable purchases × 100

This ratio is meaningful only where the denominator is defined consistently and the purchases are measured on a tax-exclusive or tax-inclusive basis as required by the relevant tax system. A high ratio may be legitimate for a business with substantial taxable purchases, but it may also indicate misclassified private costs, exempt purchases, duplicate claims, or invalid invoices.

3.4 Expense-to-sales ratio

Expense-to-sales ratio = Expense category ÷ Sales revenue × 100

A sudden increase in repairs, professional fees, travel, or related-party charges may warrant examination. However, inflation, expansion, one-off projects, or changes in accounting policy may explain the movement.

3.5 Payroll ratio

Payroll ratio = Payroll cost ÷ Sales revenue × 100

Payroll data may be compared with withholding tax, social contribution, employee counts, and working hours. A falling payroll ratio in a labour-intensive business may indicate outsourcing, incomplete payroll recording, or operational change.

3.6 Inventory and margin relationships

Inventory analysis may use turnover:

Inventory turnover = Cost of sales ÷ Average inventory

where:

Average inventory = (Opening inventory + Closing inventory) ÷ 2

The formula assumes that opening and closing inventory are measured consistently. A very low turnover may indicate obsolete or overstated inventory; a very high turnover may indicate understated closing inventory or unusually rapid sales. Neither conclusion is valid without examining purchasing, production, sales, and stock-count evidence.

4. Trend Analysis and Benchmarking

Trend analysis examines movement over time. It may use absolute changes, percentage changes, indexed values, or moving averages.

The percentage change from a previous period is:

Percentage change = (Current amount − Prior amount) ÷ Prior amount × 100

The prior amount must not be zero. If it is zero, the change should be described using absolute amounts or another suitable measure rather than a percentage.

Worked example: trend interpretation

A company reports the following information:

YearSales (CU)Cost of sales (CU)Gross margin
Year 18,000,0005,600,00030.0%
Year 29,600,0007,488,00022.0%
Year 310,560,0008,976,00015.0%

Year 3 sales increased by:

(10,560,000 − 9,600,000) ÷ 9,600,000 × 100 = 10%

Cost of sales increased by 20%, while gross margin fell from 22% to 15%. This pattern may reflect increased input costs, discounting, inventory errors, sales recorded without corresponding cost, or incomplete purchases. It is an investigation signal, not proof of omitted income.

Benchmarking compares an entity with a suitable reference group. Good benchmarks control for relevant differences such as industry, geography, size, business model, accounting policy, and tax regime. A benchmark drawn from a large manufacturer may be inappropriate for a small service provider.

Benchmarking can be:

  • internal: comparing branches, products, or periods within the entity;
  • external: comparing the entity with similar taxpayers;
  • operational: comparing financial amounts with non-financial drivers; or
  • regulatory: comparing reported values with statutory thresholds or required rates.

Benchmarking should be used cautiously where the population is small, data definitions differ, or the business is unusual.

5. Reconciliations as Completeness and Accuracy Tests

A reconciliation explains the relationship between two records that should agree or be capable of being bridged. It is one of the most powerful procedures for identifying omitted, duplicated, or misclassified information.

5.1 Sales-to-tax-return reconciliation

A basic bridge may be expressed as:

Accounting sales = Taxable sales + Exempt sales + Zero-rated sales + Other reconciling items

The precise categories depend on the tax system. Reconciling items should be documented individually, not placed in a general unexplained balance.

5.2 Purchases-to-input-tax reconciliation

The auditor may compare the purchase register with input tax claimed. Differences may arise from:

  • purchases outside the tax period;
  • blocked or restricted input tax;
  • exempt purchases;
  • capital items treated under special rules;
  • credit notes;
  • imports recorded separately; or
  • duplicate or missing invoices.

5.3 Payroll reconciliation

Payroll expense may be reconciled to gross wages, benefits, withholding declarations, employer contributions, and the number of employees. Timing differences and accrued wages should be clearly identified.

5.4 Bank and cash reconciliation

Bank deposits can provide an independent indicator of revenue completeness. The analysis must account for loans, capital contributions, transfers between accounts, refunds, and non-business receipts. Treating all unexplained deposits as taxable sales is inappropriate without evidence of their nature.

6. Exception Testing and Anomaly Detection

Exception testing applies defined rules to identify records requiring review. Common tests include:

TestPossible risk indicated
Same invoice number, supplier, date, and amount appears twiceDuplicate claim
Invoice date outside the tax periodIncorrect period or fabricated document
Missing supplier tax numberInvalid or incomplete documentation
Round-number transactionsEstimation, manual entry, or artificial recording
Transactions just below approval thresholdPossible threshold avoidance
Credit notes without original invoicesUnsupported reduction of liability
Unusual weekend or holiday postingsManual or irregular processing
Payments to dormant or unrelated accountsMisappropriation or fictitious supplier
Negative sales or purchasesReversal, credit note, or data error
Multiple suppliers share an address or bank accountPossible related-party or circular arrangement

Duplicate-claim testing

A duplicate test can use a composite key consisting of supplier identifier, invoice number, invoice date, and amount. Exact matching is useful but insufficient. Duplicates may differ slightly because of spelling, punctuation, tax-inclusive versus tax-exclusive amounts, or rounding. Fuzzy matching can identify similar records, but every match requires human review.

Benford’s law and digit analysis

Digit analysis may be used as an exploratory technique. Benford-type distributions can be informative in naturally occurring transaction populations spanning several magnitudes, but they are unsuitable for assigned numbers, fixed prices, telephone numbers, invoice sequences, or small and highly constrained datasets. A departure from an expected digit pattern is not evidence of fraud by itself.

Outlier methods

An outlier is an observation unusually distant from the rest of a population. One common descriptive measure is the z-score:

z = (x − μ) ÷ σ

where x is the observation, μ is the population or sample mean as defined by the analysis, and σ is the corresponding standard deviation. The result has no currency unit because both numerator and denominator are measured in the same units.

A z-score is less reliable when the distribution is highly skewed or contains extreme values. Robust alternatives, such as the median and interquartile range, may be more appropriate. Outlier thresholds should be selected with reference to the purpose, population, and consequences of false positives.

7. Visualisation for Tax Investigation

Visualisation helps an auditor detect patterns that may be difficult to see in tables. Useful visualisations include:

  • line charts for turnover and tax trends;
  • stacked bars for taxable, exempt, and zero-rated sales;
  • scatter plots comparing sales with purchases or payroll;
  • heat maps showing risk by branch, period, or supplier;
  • box plots for expense distributions;
  • network diagrams showing shared addresses, bank accounts, or directors; and
  • waterfall charts explaining tax reconciliations.

A good tax dashboard should display the period, population, unit of measurement, filters, data source, and definition of each metric. Colour should be used consistently. Red should not automatically mean fraud; it should mean that a defined condition has been triggered.

Visualisation can mislead when axes are truncated, categories are incomparable, scales are inconsistent, or totals are omitted. Every chart should answer a defined audit question.

8. Interpreting Results Without Overstatement

Professional interpretation requires a distinction between evidence and inference. The following hierarchy is useful:

ResultAppropriate interpretation
Unusual ratioThe relationship differs from expectation.
Exception identifiedA defined rule has been triggered.
Explanation receivedManagement or taxpayer has offered a reason.
Explanation corroboratedIndependent evidence supports the reason.
Error establishedSufficient evidence demonstrates incorrect reporting.
Deliberate evasion suspectedFacts justify escalation, but formal procedures remain necessary.

The auditor should consider false positives and false negatives. A false positive consumes resources and may unfairly damage a taxpayer’s reputation. A false negative allows non-compliance to remain undetected. Thresholds should therefore be risk-based rather than arbitrary.

A useful investigation record contains:

  1. the analytical question;
  2. data sources and extraction date;
  3. definitions and assumptions;
  4. test logic or code;
  5. exceptions identified;
  6. explanations obtained;
  7. corroborating evidence;
  8. unresolved issues; and
  9. the conclusion and next action.

9. Applied Case: Illustrative Retail Tax Review

Background

The following is an illustrative case. Meridian Home Supplies, a medium-sized retailer, reported taxable sales of CU 15 million and claimed input tax of CU 1.44 million for the year. The business operates three branches and uses a central purchasing system.

Problem

The tax adviser noticed that taxable sales increased by 18%, but declared output tax increased by only 7%. The input tax claim increased by 35%. Management stated that the difference resulted from expansion and higher inventory purchases.

Analysis

The adviser performed five procedures:

  1. compared sales, purchases, and tax by branch and month;
  2. reconciled the sales register to the tax return;
  3. tested purchase invoices for duplicates and invalid tax identifiers;
  4. compared gross margin with the prior year; and
  5. plotted input tax by supplier.

The analysis identified the following matters:

  • one branch’s sales register exceeded reported taxable sales by CU 420,000;
  • 14 purchase records matched on supplier, invoice number, date, and amount, with total claimed input tax of CU 38,000;
  • several high-value purchases were coded as ordinary inventory although they were capital assets subject to different treatment;
  • gross margin fell from 27% to 19%; and
  • a new supplier accounted for 22% of input tax but had no delivery records in the files initially provided.

Approach and solution

The adviser did not immediately classify the differences as deliberate evasion. The branch manager explained that a software interface had excluded one branch’s final-quarter sales from the tax-return export. System logs and point-of-sale totals supported this explanation, establishing a likely reporting error of CU 420,000.

The duplicate invoices were investigated against original documents and payment records. Ten were confirmed as duplicate claims, while four were legitimate recurring invoices with different delivery periods. The confirmed duplicate input tax was reversed.

The capital purchases were reclassified after examining purchase contracts and asset registers. The new supplier provided delivery notes, warehouse receipts, and bank-payment evidence. The supplier relationship was therefore unusual but not unsupported. However, the gross-margin decline remained unresolved because inventory records did not reconcile to the year-end count.

Outcome

Meridian corrected the omitted sales and duplicate claims. The capital-item treatment was amended. A physical inventory count and extended cost-of-sales testing were recommended before finalising the tax position. The final conclusion was that the analytics identified material reporting weaknesses and some errors, but did not by themselves establish intentional tax fraud.

Learning points

  • A reconciliation can identify an omission more reliably than a general ratio.
  • Duplicate detection must distinguish exact matches from legitimate repeated transactions.
  • A new supplier is a risk indicator, not proof of a fictitious supplier.
  • Several moderate indicators may justify expanded testing when they point to the same process weakness.
  • Conclusions must reflect the quality and extent of corroborating evidence.

10. Technology, Automation, and Artificial Intelligence

Tax analytics commonly uses spreadsheet models, SQL queries, audit software, enterprise-resource-planning extracts, and dashboard tools. Automation is particularly effective for repetitive procedures such as duplicate detection, period testing, tax-code validation, and reconciliation.

Artificial intelligence and machine-learning systems may classify transactions, identify unusual clusters, extract invoice fields, or predict which records merit review. These tools can increase coverage, but they introduce risks:

  • biased training data may produce biased risk scores;
  • opaque models may be difficult to explain;
  • poor data quality may create confident but incorrect results;
  • models may drift when business or tax rules change; and
  • automated recommendations may be mistaken for findings.

Human review remains necessary for material conclusions, taxpayer communication, and enforcement decisions. A model should be validated on relevant data, monitored for error rates, documented, and subject to access controls. Sensitive tax information must be protected through lawful collection, least-privilege access, secure storage, retention controls, and audit trails.

11. Professional, Ethical, and Regulatory Considerations

Tax analytics involves confidential financial and personal information. Practitioners should comply with applicable tax law, privacy law, professional standards, and organisational policies. Important principles include:

  • use data only for an authorised purpose;
  • preserve the integrity and original form of evidence;
  • maintain an audit trail of transformations and calculations;
  • separate factual observations from professional opinions;
  • avoid discriminatory or irrelevant profiling;
  • provide a fair opportunity for explanations and corrections; and
  • escalate suspected misconduct through lawful procedures.

Independence and professional scepticism are also essential. An auditor should neither accept explanations uncritically nor assume that unusual results prove wrongdoing. Where a conclusion depends on a benchmark or model, the limitations should be disclosed.

12. Best-Practice Workflow

A robust tax data-analytics engagement should follow these practices:

  1. define the compliance objective before extracting data;
  2. document the population, period, fields, and data owner;
  3. preserve raw data and separately store transformed data;
  4. reconcile extracted totals to source-system control totals;
  5. use multiple analytical procedures rather than one indicator;
  6. prioritise exceptions by amount, likelihood, and potential tax effect;
  7. investigate with independent and contemporaneous evidence;
  8. record false positives and refine the test where appropriate;
  9. obtain review by a suitably competent person; and
  10. communicate findings in language proportionate to the evidence.

The best analytical procedure is not necessarily the most sophisticated one. A simple, well-designed reconciliation may be more reliable and defensible than a complex predictive model that cannot be explained.

Chapter Summary

Analytical procedures and tax data analytics help practitioners assess completeness, accuracy, plausibility, and compliance across large volumes of financial information. Ratios reveal relationships, trend analysis identifies movements, benchmarks provide comparative context, reconciliations expose omissions and classification differences, and exception testing highlights transactions requiring investigation. Visualisation improves pattern recognition and communication.

An anomaly is not automatically an error, and an error is not automatically deliberate evasion. Sound tax work requires defined questions, reliable data, transparent methods, corroborating evidence, professional scepticism, and proportionate conclusions. Automation and artificial intelligence can improve coverage and efficiency, but they require validation, governance, confidentiality controls, and human oversight.

Key Terms

Analytical procedure: Evaluation of financial or non-financial information through analysis of plausible relationships and comparisons.

Anomaly: An observation that differs from an established expectation or pattern.

Benchmark: A reference measure used for comparison with an entity, period, or transaction group.

Completeness: The extent to which all relevant transactions and balances have been recorded and reported.

Exception testing: Application of defined rules to identify records requiring review.

Expected value: An amount or relationship developed as a reasonable basis for comparison.

False negative: A test result that fails to identify an issue that actually exists.

False positive: A test result that indicates risk although no underlying issue exists.

Gross profit margin: Gross profit expressed as a percentage of sales revenue.

Input tax credit: Tax on eligible purchases that may be offset against output tax under applicable law.

Outlier: An observation unusually distant from the general pattern of a population.

Reconciliation: A documented explanation of the relationship between two records or balances.

Ratio analysis: Analysis based on relationships between financial or operational quantities.

Tax analytics: Use of data, technology, and analytical methods to support tax compliance and decisions.

Taxable turnover: Revenue subject to tax under the applicable rules.

Trend analysis: Examination of changes in amounts or relationships over time.

Validation: Assessment of whether data, calculations, or analytical models are reliable and fit for purpose.

Visualisation: Graphical presentation of data to reveal relationships, patterns, and exceptions.

Review Questions

Short Answer Questions

  1. What is the purpose of an analytical procedure in a tax audit?
  2. Distinguish between an anomaly and an established tax error.
  3. State two data-quality checks that should be performed before tax analytics.
  4. What is a reconciliation, and why is it useful for completeness testing?
  5. Identify two ethical risks associated with automated tax analytics.

Long Answer Questions

  1. Explain how ratios, trends, and benchmarks can be combined to assess tax-compliance risk. Include the limitations of each technique.
  2. Describe a complete workflow for investigating an unusual input tax credit ratio.
  3. Explain why a duplicate-invoice test requires both automated matching and professional review.
  4. Discuss how visualisation can improve tax-audit decision-making and how poorly designed charts can mislead.
  5. Evaluate the benefits and risks of using artificial intelligence in tax compliance analytics.

Analytical / Application Questions

  1. A business reports sales of CU 20 million and cost of sales of CU 17 million in Year 1. In Year 2, sales rise to CU 22 million and cost of sales rises to CU 19.8 million. Calculate the gross profit margin for each year and explain what additional evidence you would seek.
  2. A purchase register contains two invoices with the same supplier and amount but different invoice numbers. Explain the tests needed before classifying them as duplicate claims.
  3. A taxpayer’s bank deposits exceed reported sales by CU 600,000. Develop a reconciliation approach that distinguishes potentially taxable receipts from loans, transfers, refunds, and capital contributions.

Multiple Choice Questions with Answers

Question 1

Which statement best describes an analytical procedure?

A. A comparison of information with a reasonable expectation to identify unusual relationships

B. A conclusion that every unusual transaction is fraudulent

C. A replacement for all detailed substantive testing

D. A method restricted to checking invoice arithmetic

Correct Answer: A. A comparison of information with a reasonable expectation to identify unusual relationships

Question 2

A business has sales of CU 12,000,000 and cost of sales of CU 10,800,000. What is its gross profit margin?

A. 5%

B. 10%

C. 12%

D. 90%

Correct Answer: B. 10%

Question 3

Which item is most directly useful in testing for duplicate input tax claims?

A. Supplier, invoice number, date, and amount

B. The colour used in the tax dashboard

C. The age of the company’s directors

D. The statutory tax rate alone

Correct Answer: A. Supplier, invoice number, date, and amount

Question 4

What is the most appropriate interpretation of an unusual ratio?

A. It proves deliberate tax evasion

B. It is an indicator requiring evaluation and, where appropriate, further evidence

C. It should always be ignored

D. It automatically requires a penalty

Correct Answer: B. It is an indicator requiring evaluation and, where appropriate, further evidence

Question 5

Which condition makes a percentage-change calculation problematic?

A. The current amount is larger than the prior amount

B. The prior amount is zero

C. Both periods use the same currency

D. The amounts relate to consecutive periods

Correct Answer: B. The prior amount is zero

Question 6

Which is an example of a reconciliation?

A. Comparing a sales register with sales reported on a tax return and explaining differences

B. Selecting a chart colour without reviewing data

C. Assuming all bank deposits are taxable sales

D. Deleting transactions that do not fit a benchmark

Correct Answer: A. Comparing a sales register with sales reported on a tax return and explaining differences

Question 7

A z-score measures:

A. The legal tax rate applicable to a transaction

B. The distance of an observation from a mean in standard-deviation units

C. The total amount of input tax claimed

D. The number of invoices issued by a supplier

Correct Answer: B. The distance of an observation from a mean in standard-deviation units

Question 8

Why may Benford-type digit analysis be unsuitable for fixed-price transactions?

A. Fixed prices do not necessarily arise from naturally varying amounts

B. It can calculate tax only in foreign currency

C. It always identifies every duplicate invoice

D. It requires no transaction data

Correct Answer: A. Fixed prices do not necessarily arise from naturally varying amounts

Question 9

Which is an appropriate governance control for an AI tax-risk model?

A. Allowing the model to make unexplained final enforcement decisions

B. Validating performance, documenting assumptions, and maintaining human oversight

C. Removing access controls to increase efficiency

D. Using historical data without checking for bias

Correct Answer: B. Validating performance, documenting assumptions, and maintaining human oversight

Question 10

A new supplier accounts for a large share of input tax but has delivery records and bank-payment evidence. What is the most proportionate conclusion?

A. The supplier is automatically fictitious

B. The supplier is an unusual risk indicator, but the available evidence supports further balanced evaluation

C. All input tax from the supplier must be rejected immediately

D. No further review is ever needed

Correct Answer: B. The supplier is an unusual risk indicator, but the available evidence supports further balanced evaluation

Tax Audit & Compliance
Chapter 10 of 15