Journal entry testing filter for AU-C 240 criteria.

Is anything in this data worth a closer look?

Paste ledger lines, choose the criteria, and get the entries flagged for weekend dates, period end, round amounts, unusual users and thin descriptions.

  • Runs in your browser
  • Nothing stored or sent
  • Free, no sign-up
General ledger journal entry lines
Criteria to apply

These are characteristics AU-C 240 describes as typical of inappropriate entries. Which to apply, and how tightly, is a judgment based on your understanding of the entity's financial reporting process and the fraud risks identified.

Lines flagged
10 of 12
6 entries in the file
Debits and credits
$328,600.35 / $328,600.35
Net $0.00
Entries that do not balance
0
Net of lines per entry ID is not zero
OK
Every entry in the file balances
That supports the extract being internally consistent. It does not prove the extract is the whole ledger: reconcile the population to the trial balance activity.
Lines flagged by test
TestLines
Weekend posting date2
Near or after period end4
Round amount6
Unusual or infrequent user4
Missing or thin description2
At or above amount threshold4
Seldom-used account10
Flagged lines, most criteria first
RowEntryDateAmountAccountUserWhy flagged
8JE-220401/04/2027 Mon$48,000.00Bad debt expensecfoNear or after period end; Round amount; Unusual or infrequent user; Missing or thin description; At or above amount threshold; Seldom-used account
9JE-220401/04/2027 Mon-$48,000.00Allowance for doubtful accountscfoNear or after period end; Round amount; Unusual or infrequent user; Missing or thin description; At or above amount threshold; Seldom-used account
2JE-220112/31/2026 Thu$250,000.00Revenue - ServicescfoNear or after period end; Round amount; Unusual or infrequent user; At or above amount threshold; Seldom-used account
3JE-220112/31/2026 Thu-$250,000.00Deferred revenuecfoNear or after period end; Round amount; Unusual or infrequent user; At or above amount threshold; Seldom-used account
6JE-219312/19/2026 Sat$15,000.00Consulting expensejleeWeekend posting date; Round amount; Seldom-used account
7JE-219312/19/2026 Sat-$15,000.00Accrued expensesjleeWeekend posting date; Round amount; Seldom-used account
12JE-216611/24/2026 Tue$9,500.00MealsjleeSeldom-used account
13JE-216611/24/2026 Tue-$9,500.00CashjleeSeldom-used account
4JE-218812/14/2026 Mon$4,820.35Office suppliesjleeSeldom-used account
10JE-215011/10/2026 Tue$1,280.00RepairsmchenSeldom-used account
How this was worked out
Work shownrecomputed as you type
Weekend: date falls on Saturday or Sunday (calendar day of the week, not the system's post date)
Period end: date on or after (period end − 5 days), which includes post-closing dates
Round: |amount| ≥ unit and |amount| ÷ unit is a whole number
User: not on the usual-preparer list (or, with no list, a user with one line in the file)
Population check: each entry ID's lines should net to zero; total debits less total credits = $0.00

A flag is a reason to look at the entry, not a conclusion. Select flagged items for testing, trace each to support and approval, and record the criteria, the population completeness work and the results in the workpaper.

Turning the AU-C 240 characteristics into filters

Testing journal entries is a required response to the risk of management override of controls, which exists on every audit. AU-C 240 describes the characteristics of inappropriate entries in its application material, and the usual way to apply them is to filter the ledger on each characteristic and then examine what remains. The journal entry testing guide covers the whole procedure: understanding the financial reporting process, proving the population complete, choosing criteria, and documenting the results.

What each filter tests

  • Weekend posting date. Entries dated on a Saturday or Sunday in a business that does not work weekends. It uses the entry date in the data, which is not always the date the entry was keyed.
  • Near or after period end. Entries in the last days of the period and anything dated after it, which covers entries recorded at period end and post-closing entries.
  • Round amount. Amounts that are an exact multiple of a unit you choose, such as 1,000. A round amount alone is weak, but it is a recognized characteristic of inappropriate entries.
  • Unusual or infrequent user. Entries by anyone who is not on the list of usual preparers, which reflects entries made by individuals who typically do not make journal entries.
  • Missing or thin description. Entries with little or no explanation.
  • Seldom-used account. Accounts with very few lines in the file. Use a full-year ledger for this filter, because a short extract makes every account look seldom used.
  • Amount threshold and repeated amounts. Large items, for example at or above performance materiality, and identical amounts that recur.

Limits

No standard prescribes a set of filters, and no filter set finds every inappropriate entry. Entries made by a user with legitimate access, on a weekday, at a non-round amount and with a full description, will pass every test here. The tool does not test whether entries are supported or approved, which is the substantive work after selection. The population is whatever you paste, so the completeness work stays with you. See the AU-C 240 summary for the standard and the Benford's law analyzer for a distribution test on the same amounts.

Illustrative figures only. Check the result against your firm's methodology before relying on it.

Common questions

What journal entries should an auditor test under AU-C 240?

AU-C 240 requires the auditor to test the appropriateness of journal entries and other adjustments, and to select entries made at the end of the reporting period and consider testing throughout the period. The criteria come from the auditor's understanding of the entity and the fraud risks identified. The standard describes typical characteristics of inappropriate entries, including unusual or seldom-used accounts, entries by people who do not normally post them, entries at period end or after closing with little explanation, and round or consistently ending numbers.

Does a flag mean the entry is wrong?

No. A weekend date, a round amount or a thin description is a reason to look, and most flagged entries will have an ordinary explanation. The test narrows a large population to entries worth tracing to support and approval. Record how each selection was resolved.

How do I get the data out of QuickBooks?

Run the Journal report for the full period, with the columns date, transaction number, name, memo or description, account and debit and credit, and export it to Excel. Put the columns in the order the tool expects, show debits as positive and credits as negative, and add the user who created each entry if the audit log has it. Whatever you export, show that it is the complete ledger before testing.

How do I show the journal entry population is complete?

Roll the opening trial balance forward by the net activity in the journal data, account by account, and compare it with the ending trial balance. The difference should be zero for every account. Also check that debits equal credits, that entry numbers are continuous where the system assigns them, and that the dates cover the whole period and any post-closing entries. The tool checks the balance of each entry for you.

Will the standard change?

Yes. SAS 151, The Auditor's Responsibilities Relating to Fraud in an Audit of Financial Statements, supersedes AU-C 240 for audits of periods ending on or after December 15, 2028, with early implementation permitted. Until a firm adopts it, AU-C 240 is the standard for nonissuer audits.

Runs in your browser. The figures you type are not sent to CORAA or stored. Check the result against your firm's methodology before relying on it.

Related audit calculators

For US CPA firms

Join the CORAA waitlist

CORAA AI drafts audit working papers from your client’s QuickBooks books and does the first pass: lead schedules, tie-out, memos, draft notes and letters. CORAA Network reviewers clear every finding. Your firm reviews and signs.

  • First audit free, so you can judge the quality on a real file
  • Flat fee by entity size; messy books included
  • We work only with CPA firms, never their clients
See how it works →

* required