Prove a journal export is complete before audit sampling

Before exporting journals, ask the auditor to confirm the entities, ledgers, periods and entry types required. Distinguish an accounting date from a creation or posting timestamp. A journal entered in January with a December accounting date can appear in one date-filtered extract and disappear from another. Record the requested convention with the file.

Discuss system-generated entries, manual journals, consolidation entries and adjustments held outside the operating ledger. Identify which system supplies each population. The company's task is to provide the requested information accurately; the auditor decides which procedures and selections are appropriate. Do not remove entries because the preparer expects them to be uninteresting.

Save the report name, selected entities, filters, extraction time and source-system version where available. Retain an original export before sorting, joining or reformatting it. Preserve journal identifiers and line identifiers, including leading zeros. Explain whether one row represents a journal header, a posting line or an aggregated balance.

PCAOB AS 1105 requires auditors in covered engagements to address the accuracy, completeness and appropriate detail of company-produced information used as evidence. Your extraction record helps the auditor understand the file; it does not replace the auditor's work. For another auditing framework, ask the engagement team what evidence it requires.

Compare row counts, distinct journal counts, debit totals and credit totals with independently obtained source reports for the same population. Reconcile by entity and period before relying on an overall total. A file containing balanced entries can still be incomplete: equal debits and credits establish arithmetic balance, not population completeness.

Consider a hypothetical ledger with $8.4 million of debits and $8.4 million of credits. An export missing a balanced $600,000 journal contains $7.8 million on each side and still nets to zero. The missing gross activity becomes visible only when the extract is compared with the corresponding ledger totals and entry population.

Explain opening balances, closing entries, currency conventions and other legitimate differences in a bridge. Keep excluded categories identifiable and have their treatment agreed. An unexplained adjustment added to the export would make it harder to establish what the source system actually contained.

Look for truncated downloads, omitted pages, hidden filters and spreadsheet row limits. If a report arrives in several files, show how their date or identifier ranges fit together without gaps or overlapping rows. Retain part numbers and totals so another person can reproduce the combination.

When joining account descriptions or user names, compare the population before and after the join. A one-to-many match can duplicate posting lines; an unmatched lookup can silently remove them. Keep unmatched records in an exception list and reconcile counts and amounts after every transformation supplied to the auditor.

Give the auditor the original extract, any clearly labeled transformed copy, extraction settings and reconciliation. Identify unresolved differences before selections are made. Obtain the audit team's direction if the population needs correction; changing the file silently can break the connection between a selected item and its supporting record.

If the ledger changes after delivery, provide a dated list of added, reversed or amended journals and the revised control totals. Preserve the earlier file and document which version supersedes it. The handoff should make the population reproducible without suggesting that a reconciled export guarantees the accuracy of every underlying transaction.