Find approved journals that never reached the ledger

List adjustments approved for the reporting period, including manual journals, schedule-generated entries, and reporting-layer adjustments. Record the approval reference, intended entity and date, amount, and person responsible for implementation. Keep proposed or rejected adjustments outside the approved population so the final check does not treat every review comment as an entry that should have posted.

Compare the approved list with actual ledger references and the reporting adjustment register. Approval and posting are separate events. A task can be marked complete because the reviewer accepted the calculation even though the entry remains a draft, failed validation, or was posted to a different period. The completion evidence should identify the actual result.

Ask whether the entry is still in draft, awaiting another authorization, rejected, canceled, or superseded. Inspect the application's actual status and retain supporting evidence. Where the approval was conditional, confirm that the condition was resolved before posting. An entry can be appropriately unposted if the approved decision changed, but the change needs its own reference.

PCAOB AS 2401 considers journal entries and other adjustments throughout the financial reporting process. For this internal completeness check, include adjustments that live outside the formal ledger as well as ordinary journals. A final statement correction can be missing even when the ledger posting queue is empty.

Match more than the journal description. Compare the entity, accounting date, currency, accounts, dimensions, and approved amount. A posted entry with the same title can be an earlier version or a different month's recurring adjustment. Retain the calculation version that the approval covered and compare it with the posted lines.

In a hypothetical close, a $12,000 September adjustment is approved and then posted with an October date. The posting reference exists, but September statements do not contain the accepted adjustment. Have the accountant determine the correction and review any October effect. Marking the September task complete based only on the journal's existence would miss the reporting error.

Before posting a replacement, search for the original entry and any scheduled retry or batch result. A preparer may have posted the journal while another person's tracking sheet remained stale. A second posting can turn a documentation problem into an accounting error. Establish the actual ledger state before acting.

If an automated process partially succeeded, reconcile its accepted and rejected references separately. Cancel or resolve pending actions through the supported workflow when a manual replacement is approved. Record the relationship between the original request, replacement, and any reversal. The next reviewer should not have to infer why several similar entries exist.

Regenerate affected trial balances, schedules, and statement drafts once the approved entries are complete. Compare the reporting version's source timestamp or identifier with the final posting population. An entry can be correctly recorded yet absent from a PDF exported earlier. Verify the actual file intended for release.

Retain the approved adjustment list with final posting references and explanations for any canceled or unposted items. Transfer unresolved accounting decisions to the release reviewer rather than silently removing them from the queue. The final record should show which approved changes reached the reported numbers and which matters still require an explicit decision.