Journal Entry Testing: PCAOB Standards, Risk Factors, and Analytics

Journal entry testing is the set of audit procedures required by PCAOB AS 2401 and AICPA AU-C Section 240 to address the risk that management overrides controls by recording improper journal entries or other adjustments. The work moves through a predictable arc: understand how entries flow through the client’s system, build risk-based criteria, isolate a targeted sample using data analytics, and vouch each selected entry back to its source documentation. Every step has to be documented, because the PCAOB’s inspection findings return to journal entry procedures year after year.

Why the Standards Require It

Management occupies a position no other employee does. Executives can directly manipulate accounting records and prepare misleading financial statements by sidestepping controls that otherwise work as designed. AS 2401 treats this as a given rather than something auditors evaluate case by case. Every audit must include procedures addressing management override, regardless of how strong the control environment appears.1Public Company Accounting Oversight Board. AS 2401 – Consideration of Fraud in a Financial Statement Audit

The standard identifies two ways fraud reaches the financial statements through entries. The first is recording unauthorized entries during the year or at period end. The second is adjustments that never appear as formal journal entries at all: consolidating adjustments, report combinations, and reclassifications folded directly into financial statement drafts.1Public Company Accounting Oversight Board. AS 2401 – Consideration of Fraud in a Financial Statement Audit That second category is easy to miss. Entries posted straight to financial statement drafts bypass the general ledger, and a team that only tests the ledger will never see them.

AS 2401 requires four specific steps: understand the entity’s financial reporting process and the controls over journal entries and adjustments; identify and select entries and adjustments for testing; determine when during the audit to test them; and inquire of individuals involved in financial reporting about inappropriate or unusual activity related to entries.1Public Company Accounting Oversight Board. AS 2401 – Consideration of Fraud in a Financial Statement Audit For non-issuer audits, AU-C Section 240 imposes parallel requirements, and the procedures are effectively the same.

AS 2301 adds a related obligation: build unpredictability into procedures from year to year. Vary the entries you select, adjust timing, and occasionally test items outside your usual parameters. Testing the same accounts the same way each December tells anyone paying attention exactly which entries will never be examined.

Understand the Process Before Selecting Anything

Do not pick a single entry for testing before you understand how entries move through the system. AS 2401 is explicit on this point, and skipping it is one of the most common deficiencies the PCAOB reports on inspection.2Public Company Accounting Oversight Board. Audit Focus – Journal Entries

AS 2110 spells out what to understand about the period-end financial reporting process: how transaction totals reach the general ledger, how entries are initiated, authorized, recorded, and processed, and how recurring and nonrecurring adjustments make it into the annual and quarterly financial statements.3Public Company Accounting Oversight Board. AS 2110 – Identifying and Assessing Risks of Material Misstatement

Concretely, map out who can initiate entries into the general ledger or transaction systems, what approvals are required before posting, whether entries are created online with no physical trail or prepared on paper and uploaded in batches, and whether preformatted templates or automated exception reports exist for entries that fail control checks.1Public Company Accounting Oversight Board. AS 2401 – Consideration of Fraud in a Financial Statement Audit Then identify every source of adjustments that reaches the financial statements outside the general ledger. Consolidating entries, intercompany eliminations, and top-side adjustments made in spreadsheets or reporting tools all belong on that list.

The ledger itself contains entry types with very different risk profiles. Routine postings such as payroll runs or sales are typically system-generated and flow through standardized automated controls. Manual entries recorded outside those automated sub-ledgers carry more risk because they depend on human judgment and are easier to manipulate without detection.

What Makes an Entry High Risk

PCAOB staff guidance identifies specific characteristics that distinguish entries most likely to involve fraud. These form the backbone of your selection criteria, and getting them right decides whether testing targets the entries that matter or wastes time on routine postings.

  • Unusual accounts: Entries posted to unrelated, seldom-used, or unexpected accounts, such as a large expense coded to a miscellaneous revenue line.
  • Unusual preparers: Entries recorded by individuals who do not typically make journal entries, particularly senior managers or executives with no operational reason to touch the ledger.
  • Period-end and post-closing entries: Entries recorded at the end of a reporting period or as post-closing adjustments, especially those with little or no explanation.
  • Missing account numbers: Entries made before or during financial statement preparation that lack account numbers.
  • Round numbers or consistent endings: Amounts that suggest an estimate or arbitrary figure rather than a calculation tied to source documentation.2Public Company Accounting Oversight Board. Audit Focus – Journal Entries

Timing

Entries recorded in the final days before the books close deserve extra attention. That window concentrates accruals, estimates, and last-minute adjustments, all of which depend heavily on management judgment. Entries posted outside standard business hours raise questions about oversight and segregation of duties. An entry posted at 11 p.m. on a Saturday may have a legitimate explanation, but it warrants a closer look than one posted during working hours.

Amounts Near Thresholds

Entries recorded just below an approval threshold are a classic fraud indicator. If the company requires VP approval for any adjustment over $100,000, a string of $99,500 entries from the same preparer is not a coincidence. The same logic applies to entries falling just under your materiality threshold. When several high-risk characteristics overlap in one entry, a round-dollar amount posted by an executive to an unusual account on the last day of the quarter, the combination demands immediate investigation.

Using Data Analytics To Select Entries

Modern ERP systems produce millions of entries a year, so manual scanning of the full population is not possible. Computer-assisted audit techniques and specialized analytics software let you process the complete general ledger file and isolate entries that match your risk criteria.

Start by extracting the entire population of journal entries from the client’s system into a standardized format. Completeness of that extract matters enormously. Entries missing from the file cannot be caught by any filter you build, and the PCAOB has flagged failure to test completeness of the population as a recurring inspection deficiency.2Public Company Accounting Oversight Board. Audit Focus – Journal Entries Reconcile the total debits and credits in your extract to the trial balance before you filter anything.

Filters

Build queries on the risk characteristics identified during planning. Typical filters isolate entries by posting date (last week of the quarter, weekends, holidays), by preparer (user IDs belonging to executives or employees outside the accounting function), by account (suspense, infrequently used, intercompany), and by amount (round numbers, amounts near approval thresholds). Layering filters reduces millions of records to a manageable subset of potentially anomalous entries.

Analytical Techniques

Beyond filtering, statistical techniques surface patterns invisible to the eye. Benford’s Law is one of the more useful. In naturally occurring numerical data sets, the digit 1 appears as the leading digit roughly 30% of the time, and 9 less than 5% of the time. When someone fabricates numbers manually, the resulting distribution almost never conforms to that expected pattern. A Benford analysis on journal entry amounts, compared to the expected distribution, points to accounts or entry types that may contain manipulated data. A deviation does not prove fraud, but it tells you where to look.

Gap analysis examines sequential entry numbering for breaks in the sequence. Missing numbers may indicate deleted or voided transactions. Straightforward, but easy to overlook, particularly in systems where year-end entries use a separate numbering sequence from routine postings.

Trend analysis adds a time dimension, flagging unusual spikes in activity for a specific account, preparer, or entry type during periods that historically show low volume. A sudden surge in accrual entries during the final week of the quarter, when prior quarters showed a steady daily pace, deserves investigation.

The output is a prioritized list ranked by concentration of risk indicators. That list is your testing sample. The goal is not random sampling but targeted selection driven by where fraud risk is highest.

Substantively Testing Each Selected Entry

With a prioritized sample in hand, the work shifts to detailed examination. For each entry, retrieve the complete supporting documentation: invoices, contracts, internal memos, board resolutions, or whatever should exist given the nature of the transaction.

Authorization and Classification

Check the preparer and approver against the company’s delegation of authority. Someone approving an entry above their authorization limit is a control deficiency regardless of whether the underlying transaction is legitimate. Verify that the accounts debited and credited make sense for the transaction described. A capital expenditure booked as an operating expense distorts both the income statement and balance sheet; it may be an innocent error or a deliberate attempt to smooth earnings.

Trace each entry back to its source transaction to confirm the recorded amount reflects a real economic event. This is where many fraudulent entries fall apart. A legitimate entry has a trail: a purchase order, a vendor invoice with matching quantities and prices, a receiving report. An entry created solely to move numbers around rarely has documentation that survives scrutiny.

Examine Supporting Documents With Skepticism

Look for signs of alteration: inconsistent fonts, mismatched dates, correction fluid, digital editing artifacts. When documents are copies of copies, request originals. For electronic documentation, check metadata including timestamps, user logs, and modification history to confirm the document was created when and by whom it claims.

Missing or inadequate documentation on a high-risk entry is a serious finding. It typically requires immediate discussion with management and, depending on circumstances, escalation to the audit committee. Absence of evidence is not evidence of absence, but in the context of a high-risk entry, it shifts the burden squarely onto management to explain.

Inquiry

When documentation is ambiguous or incomplete, inquire of the people involved. These conversations often reveal whether an unusual entry had a legitimate business purpose or was an attempt to manipulate the statements. The inquiry requirement in AS 2401 is not optional: auditors must ask individuals involved in financial reporting about inappropriate or unusual activity related to journal entries.1Public Company Accounting Oversight Board. AS 2401 – Consideration of Fraud in a Financial Statement Audit Confirm that each tested entry was properly posted and is accurately reflected in the trial balance.

Failure to find sufficient evidence supporting a high-risk entry has direct consequences. It may require expanding the sample, performing compensating procedures, or, if the effect is material and uncorrected, modifying the audit opinion.

Documenting the Work and Reporting Findings

Work papers for journal entry testing have to tell a complete story. Document the methodology used for selection, tying the final sample back to the risk filters and analytics performed. For every entry tested, record what was found: whether it was properly supported, authorized at the appropriate level, and classified correctly. Record a conclusion for each individual entry, not just a blanket statement covering the sample as a whole.

The papers should include an overall conclusion about the effectiveness of controls over journal entries and the resulting risk of material misstatement. Control deficiencies identified along the way must be communicated to management, and, when significant or material, to the audit committee.

Findings that suggest potential fraud or intentional misstatement trigger a separate reporting obligation. AS 2401 requires the auditor to communicate possible fraud to the appropriate level of management, and, when senior management’s integrity is in question, directly to the audit committee.1Public Company Accounting Oversight Board. AS 2401 – Consideration of Fraud in a Financial Statement Audit That communication must happen promptly and confidentially. The number and nature of unsupported or unauthorized entries you identify feed directly into the overall audit risk assessment. A pattern of unexplained entries concentrated in year-end periods, even if individually immaterial, may collectively indicate a systemic problem that affects the opinion.

PCAOB Inspection Deficiencies To Avoid

The PCAOB publishes the deficiencies it finds most frequently, and journal entry testing appears repeatedly. The most common failures:

  • Skipping the process understanding: Beginning selection and testing without an understanding of the financial reporting process and controls over entries.
  • Not selecting entries for testing: Failing to identify and select entries addressing the risk of material misstatement from fraud.
  • Incomplete populations: Not testing whether the extracted population is complete, so entries could be missing from the data set entirely.
  • Arbitrary scope limitations: Testing only some of the entries meeting the fraud criteria without documenting a reason for excluding the rest.
  • Weak rationale for criteria: Failing to document how the risk factors in AS 2401 led to the specific criteria used, including whether manual versus automated entries were considered.2Public Company Accounting Oversight Board. Audit Focus – Journal Entries

The pattern is consistent. Teams either rush past the foundational steps or narrow their scope without justification. The most effective way to survive an inspection is to document reasoning at every decision point: why you chose the criteria you did, why any entries meeting those criteria were excluded, and what you concluded about each entry you tested.