Journal entry testing is a required response to fraud risk under auditing standards (AU-C 240 / ISA 240 / PCAOB AS 2401). The objective is to identify journal entries and adjustments that could result in a material misstatement due to fraud, particularly management override.

A common misconception is that materiality cannot be used in journal entry testing. That is not accurate.

Materiality remains foundational to auditing. What standards prohibit is mechanically excluding journal entries in a way that undermines the fraud response. Our Journal Entry Workpaper applies materiality in a structured, cumulative, and risk-aligned manner that preserves qualitative judgment and aggregate evaluation.

This article explains:

• How the threshold is established

• How expected and unexpected offsets are treated

• Why a cumulative methodology is used

• How the approach aligns with auditing standards

• How this is documented in the workpaper

• Where the auditor sets the threshold in the UI

• Why revenue and expense are evaluated separately

High-Level Overview

When the auditor selects their testing population (Unusual Revenue or Unusual Expense), they have the option to enter performance materiality directly in the UI.

Once entered, this amount is used to evaluate whether unexpected offset combinations should be considered for further testing. It does not impact the initial identification of unusual combinations.

Important considerations:

• Offsets can be positive or negative values.

• The system uses the absolute value of amounts for evaluation.

• All unexpected offsets below the threshold are accumulated using their absolute values.

Materiality is therefore evaluated on an aggregate absolute-value basis, which is the most conservative approach. What is determined to be immaterial is assessed in total — not individually.

1. Setting the Materiality Threshold

The module allows two methods:

Option 1: Fixed Dollar Amount (Takes Priority)

A defined dollar threshold entered by the auditor.
If populated, it overrides the percentage-based calculation.

Option 2: Percentage of Total Revenue or Expense

If no fixed amount is entered, the threshold is calculated as a percentage of:

• Total revenue (for revenue-side analysis), or

• Total expense (for expense-side analysis)

This ensures proportionality relative to entity size.

Importantly, this threshold functions as a scoping tool, not as an automatic exclusion rule.

The threshold is set at the time the workpaper is requested and can be adjusted by the auditor as needed.

Logic Calculations

Below is a detailed explanation of how the logic is applied.

Expected Offsets Are Excluded from the Immaterial Calculation

Expected offsets reflect normal accounting relationships, such as:

• Revenue → Cash

• Revenue → Accounts Receivable

• Expense → Cash

• Expense → Accounts Payable

Because journal entry testing responds to fraud risk — particularly management override — these expected patterns are excluded from the immaterial scoping calculation.

No threshold is applied to expected offsets.

They remain fully subject to testing consideration.

This ensures compliance with standards requiring evaluation of journal entries susceptible to fraud and avoids mechanically filtering structurally normal activity.

Unexpected Offsets Use a Cumulative Materiality Approach

Unexpected combinations (e.g., Revenue → Accrued Liabilities, Expense → Deferred Revenue) may indicate:

• Reclassification entries

• Manual overrides

• Accrual manipulations

• Fraud risk indicators

Rather than applying a blunt dollar filter, the workpaper:

1. Sorts unexpected offsets from smallest to largest (based on absolute value).

2. Accumulates them progressively.

3. Scopes out combinations only until aggregate impact exceeds the threshold.

4. Flags the combination that crosses the threshold — and all larger combinations — for detailed testing.

This preserves risk sensitivity while eliminating noise.

Because aggregation is performed using absolute values, positive and negative entries cannot offset one another to artificially reduce cumulative impact.

Revenue and Expense Are Evaluated Separately

Revenue and expense populations are analyzed independently.

Each has:

• Its own threshold

• Its own unexpected combinations

• Its own cumulative scoping calculation

This prevents cross-masking between large expense populations and unusual revenue offsets (or vice versa).

Example: $73,000 Threshold

Assume a $73K threshold for unexpected revenue offsets.

Offsets A, B, and C are scoped out because their cumulative total ($70K) remains below $73K.

Once Offset D pushes the cumulative total above the threshold, it — and all larger offsets — are treated as material for detailed testing.

Alignment with Auditing Standards

Auditing standards require testing journal entries for evidence of possible material misstatement due to fraud.

They do not require:

• Testing 100% of journal entries

• Ignoring materiality

• Eliminating professional judgment

Materiality is embedded in the concept of “material misstatement.”

However, materiality cannot be applied mechanically. It should not:

• Exclude entries solely because they fall below a fixed amount

• Override qualitative risk factors

• Ignore cumulative effects

The cumulative methodology supports standards by:

• Evaluating aggregate impact (consistent with misstatement aggregation principles in AU-C 450)

• Preserving qualitative judgment

• Maintaining full evaluation of expected flows

• Focusing detailed testing where aggregate unusual activity becomes material

Auditors retain the ability to override the threshold when qualitative factors warrant further investigation.

How This Is Documented in the Workpaper

The materiality logic is transparently documented within the Journal Entry Workpaper.

You can view the scoping analysis in:

• Revenue Scoping tab

• Expense Scoping tab

Each tab displays:

• Total revenue or total expense used as the population base

• The materiality threshold applied (fixed dollar or calculated percentage)

• A listing of unexpected offset combinations

• Individual absolute amounts per combination

• Cumulative totals

• Clear identification of which combinations are scoped in vs. scoped out

The exact point where cumulative totals exceed the threshold is visible within the tab, creating a clear audit trail of:

• Threshold applied

• Method used

• Population evaluated

• Scoping determination

This supports inspection readiness because the scoping decision is transparent, systematic, and reproducible.

Closing Perspective

Journal entry testing should not be a volume exercise.
It should be a risk-based exercise.

By combining:

• Structural logic (expected vs. unexpected offsets)

• Proportional thresholds

• Cumulative aggregation

• Absolute-value conservatism

• Transparent documentation

• Auditor override capability

the Journal Entry Workpaper supports a fraud-focused, standards-aligned, and defensible approach to journal entry scoping.