Rollover Audit Exception Log: What CCOs Should Record Before Closing an Item

In the realm of rollover compliance, a thorough audit exception log is essential when tracking, resolving, and closing exceptions under PTE 2020-02. For chief compliance officers (CCOs), every closed item in the log must serve as an auditable record—demonstrating not just that remediation took place, but precisely what was fixed, who reviewed it, why it mattered, and what evidence supports closure. Regulators such as the Department of Labor (DOL) expect the exception log to be a core part of the audit file, not a peripheral administrative note.

This detailed guide, based on industry expertise, links PTE 2020-02 requirements to practical exception log design and workflow. We focus on fields, documentation types, and stepwise retention protocols that keep compliance teams exam-ready and defensible. All recommendations align with DOL exception handling expectations and are field-tested in the real-world workflows of Simple Advisor Tools users.

Definition: Rollover Audit Exception Log

A rollover audit exception log is a standardized record, integrated into the compliance audit file, that tracks every deviation from normal documentation workflow for retirement plan-to-IRA, IRA-to-IRA, or plan-to-plan rollover analyses. Its purpose is to show a complete remediation lifecycle: identification, risk assessment, corrective action, review, final approval, and retention.

Why Exception Closure Documentation Matters Under PTE 2020-02

Regulatory requirements mandate that rollover recommendations be supported by audit-ready documentation demonstrating fiduciary duty, disclosure, and thorough comparison (fees, services, alternatives). When a gap occurs—missing Form 5500 data, unsigned acknowledgment, absent fee breakdown—a CCO must prove:

• The issue was identified and categorized
• Its risk to best interest or prohibited transaction standards was assessed
• Remediation was performed and verified
• The evidence supports that the recommendation complies with DOL rules

An audit file with weak or incomplete exception closure increases the risk of regulatory findings, penalties, or retrospective compliance failures. This is especially critical as PTE 2020-02 documentation expectations persist even after the vacatur of the 2024 DOL Retirement Security Rule.

Key Fields Every Exception Log Entry Must Include

Standardization of exception closure fields ensures both internal clarity and external audit defensibility. The following requirements distill best practices for CCOs managing rollover files:

• Exception ID: Unique tracking number tied to each rollover audit file
• Client name & account: Sufficient to locate the exact recommendation
• Date identified: When the exception was recorded
• Who identified: Advisor, paraplanner, operations, or compliance staff
• Control violated: Named workflow requirement (e.g., missing fee comparison, incomplete disclosure form, unsigned acknowledgment)
• Description: Plain language summary of what was missing or deficient
• Source evidence: Document or screenshot demonstrating the gap
• Risk assessment: Whether the issue affected fiduciary analysis, client disclosure, or was administrative only
• Owner: Individual responsible for tracking and closing the item
• Corrective action: Detailed remediation steps taken (such as revised template uploaded, signature obtained, updated analysis report)
• Compensating evidence: If direct fix is not possible, alternate documentation attached
• Approval: Reviewer name, role (CCO, principal), and closure date
• Retention detail: Location and instructions for fast file retrieval in exams

Step-by-Step Exception Closure Process

1. Identify and Record: Log detailed nature of the deficiency as soon as it is found
2. Classify the Risk: Assess impact (administrative, disclosure quality, best interest)
3. Assign Owner: Designate an individual to own remediation and set a timeline
4. Remediate: Perform corrective action—obtain missing data, update templates/forms, secure required signatures, revise service or fee comparisons
5. Document Evidence: Attach all supporting files: revised reports, updated acknowledgment forms, signed disclosure templates
6. Obtain Approval: Independent final review by a CCO or compliance delegate; note reviewer and date
7. Record Retention: Store log entry and all evidence in central audit file repository (accessible for DOL, FINRA, or SEC exam as needed)

Illustrative Rollover Exception Log Examples

• Missing 5500 Fee Data: Exception noted manual entry when plan sponsor’s Form 5500 was unavailable. Closure required documentation of addendum, second-source verification, and a revised fee comparison in the audit report.
• Unsigned Disclosure Form: Initial rollover recommendation included report but not the signed acknowledgment of delivery. Closure required uploading the executed template/form, with evidence of delivery date and verifier identity.
• Service Comparison Gap: Analysis initially compared only expense ratios. Closure after updating the report to reflect investment services, planning features, and other qualitative benefits between current plan and proposed IRA.
• Unresolved Conflict Disclosure: Item remained open until the conflicts of interest section of the PTE 2020-02 disclosure was properly completed and the compliance file updated with the final signed form.

Minimum Closure Standards Under DOL Expectations

For each closed exception, the audit log should answer six core questions in writing:

1. What was the specific deficiency?
2. Why was it significant for fiduciary duty or best interest review?
3. Who reviewed the exception and what is their compliance role?
4. What remediation occurred—explicit detail, not a vague reference?
5. Is the fix complete (all fields and documents present)?
6. What documentation set supports final closure?

This approach prepares advisory firms to respond confidently to DOL and industry audits, showcasing defensible rollover analysis workflows in real time.

Exam-Ready Exception Logs: Additional Fields to Strengthen Defensibility

• Timeline fields: Date opened, escalation, remediation, and close
• Decision fields: Initial finding, disposition, closure rationale
• Evidence cross-references: Document/file names, version history, audit file path
• Root cause indicators: Whether a pattern exists (repeated issue across files)
• Client impact markers: Was recommendation changed, delivery delayed, or new disclosure issued due to this exception?

Building these fields into compliance technology—such as the audit-ready templates inside Simple Advisor Tools—removes guesswork and ensures every log entry is exam-grade.

Checklist: Before Closing Any Rollover Exception

• Describe the exception in one clear sentence
• Reference the exact rollover file, by client and date
• Name the specific workflow control or regulatory requirement affected
• Assess and record compliance risk (PTE 2020-02, prohibited transaction, disclosure gap)
• Attach or precisely reference corrective documentation
• Identify and sign-off by the reviewer (with date and role noted)
• Ensure closure evidence is in final, searchable form, not draft
• Explain why the issue is resolved in substance—not just fixed procedurally

Retention and Retrieval Standards

Audit exception logs must be maintainable for at least seven years and immediately retrievable during exams. The closure record should live in the central compliance system alongside the supporting audit-ready PDF, Form 5500 data, and all signed templates or forms—never as informal notes in email or chat threads. Simple Advisor Tools ensures these requirements through built-in 5500 data retention and encrypted documentation storage.

Practical Takeaways for CCOs and Compliance Teams

• Never mark an item closed until all fields (including reviewer and evidence) are filled
• Use standardized templates and forms for remediation and closure
• Regularly test your system’s ability to produce complete exception logs on demand
• Integrate exception logs into both proactive annual reviews and retrospective sample audits

For added context on building an audit-ready file, see our related posts on what a DOL auditor will ask for in a rollover file and