How CCOs Should Select Rollover Files for a PTE 2020-02 Audit Sample

Chief Compliance Officers (CCOs) responsible for PTE 2020-02 retrospective reviews understand the stakes—regulatory scrutiny, complex workflows, and the need for documentation that validates every aspect of a compensated rollover recommendation. Selecting rollover files for audit sampling is not a clerical exercise; it is a foundational compliance function governed by Department of Labor (DOL) expectations and your firm’s fiduciary duty. This guide offers a structured methodology for building and defending your PTE 2020-02 audit file sample, aligning every decision with regulatory requirements, practical workflow realities, and best practices established by industry leaders like Simple Advisor Tools.

Definition: What is a PTE 2020-02 Audit Sample?

A PTE 2020-02 audit sample is a documented subset of rollover recommendation files selected for independent compliance review. Under DOL regulations (PTE 2020-02), every financial institution making rollover recommendations for compensation must document (1) fiduciary acknowledgment, (2) the specific reasons for each recommendation, (3) delivery of a disclosure template or form, and (4) evidence of best interest analysis. The annual retrospective review, certified by a senior executive officer, must test whether these requirements were met in practice. Your audit sample is the evidence base supporting that conclusion.

Why Sample Selection Matters

Sampling only pristine files or those from top-performing advisors undermines the credibility of your review. The DOL expects that your sampling method reflects the entire relevant population—not just easy cases—and that you can support your rationale for file inclusion or exclusion. Consistency, risk-awareness, and defensibility are the hallmarks of a reliable audit process. Simple Advisor Tools embeds these principles into automated workflows so that compliance teams can select and retrieve eligible files quickly, with full Form 5500 data integration and auditable documentation.

Step-by-Step Framework for Selecting Rollover Files

1. Define the Review Population
   
   • Include every compensated rollover recommendation made during the review period and subject to PTE 2020-02.
   • If your policy or workflow covers Plan to IRA, IRA to IRA, or Plan to Plan rollovers, include them accordingly. Exclude only with documented scope rules.
   • Record specific timeframe (for example, January 1 to December 31 of prior year) and rationale for including or excluding file categories.
2. Build a Complete Population List
   
   • Compile a master list containing for each file: client name or account ID, advisor, recommendation date, account types (pre- and post-rollover), compensation method, PTE 2020-02 disclosure delivery date, and presence of plan data or Form 5500 extracts.
   • Leverage technology—Simple Advisor Tools automatically tracks these metadata fields, eliminating manual spreadsheet risk.
3. Stratify by Risk and Apply Sampling Method
   
   • Most defensible approach is a mix of random sampling (to discourage cherry-picking) and risk-based augmentation (to target areas of known compliance vulnerability).
   • Risk flags might include files with missing fee disclosures, manual data entry, especially large balances, close-to-retirement timing, or prior documentation exceptions.
   • Sample size should be explained and matched to your total population. For small firms, this may be a higher proportion of total files. For large firms, stratify by advisor or office and sample within each stratum.
4. Prioritize Files That Test Key PTE 2020-02 Requirements
   
   • Target files that:
   • Used Form 5500 data in fee analysis (tests documentation quality).
   • Include manual benchmarks or missing plan documents (tests completeness and advisor diligence).
   • Show complex service vs. fee tradeoffs (tests qualitative judgment and rationale quality).
   • Avoid building your sample from only complete or recent files or from a single advisor.
5. Review for Required Documentation
   
   • Checklist for each sampled audit file:
   • Fiduciary acknowledgment
   • Completed PTE 2020-02 disclosure template or form (see What Belongs in a PTE 2020-02 Rollover Disclosure Form for Advisors)
   • Best interest rationale including client-specific facts
   • Cost comparison with fees, expense ratios, and available services
   • Supporting source documents: Form 5500 data, summary plan description, investment menus, fee disclosures
   • Evidence of delivery and client acknowledgment
   • Compliance officer or supervisory signoff, if required in policy
   • See audit file composition details: What a DOL Auditor Will Ask For in a Rollover File (PTE 2020-02): A Practical Checklist
6. Validate File Retention and Retrieval
   
   • PTE 2020-02 requires retention of audit-related documents for at least six years (or longer per your policy). Confirm that each file and its support can be produced with all content intact and audit trails available.
   • Simple Advisor Tools maintains 7-year searchable archives, removing the risk of lost or inaccessible audit files.
7. Document Rationale for Each Selected File
   
   • For every sampled file, note the reason for inclusion (random selection, risk flag, policy testing, prior finding, etc.). This rationale should flow into your final retrospective review methodology and written report.
8. Aggregate Results and Roll into Review Report
   
   • Document findings, remediate gaps, and certify results as required by the DOL. Your file sample becomes primary evidence of policy effectiveness and actual compliance in the field.
   • For annual review context, see sample process: PTE 2020-02 Retrospective Review Checklist for Rollover Files

Practical Example: File Selection in Action

Imagine a mid-sized RIA completed 42 covered rollovers last calendar year. The CCO defines the population as all 42, excludes 5 that were clearly out-of-scope (uncompensated or unrelated transfers), and builds a population list in their compliance system. They select a baseline random sample of 10 files, then add 5 more with risk factors (missing plan data, especially large assets, prior documentation note). Every sampled file is checked for fiduciary acknowledgment, PTE 2020-02 disclosure form, evidence of Form 5500 or plan data use, delivery proof, and supporting comparison. Gaps prompt remediation before the file is considered audit-ready. This process, automated by Simple Advisor Tools, yields documentation that stands up in a DOL review.

Common Pitfalls to Avoid

• Sampling only from advisors or business lines with the best documentation.
• Failing to document why files were chosen or left out.
• Neglecting to confirm file completeness until just before (or during) a DOL request.
• Relying on memory, scattered emails, or CRM exports without verifying actual document content.

For advice on handling incomplete disclosure forms, see: How Advisors Should Correct an Incomplete PTE 2020-02 Disclosure Form.

Sample Selection Checklist for CCOs

• Define population and review period in writing.
• List all policy exclusions with rationale.
• Compile a full population file list with all required data fields.
• Apply risk stratification and set a minimum baseline sample.
• Add exception/risk-based files for targeted review.
• Check each file for PTE 2020-02 required content.
• Confirm retention, access, and audit support for every sampled file.
• Document inclusion reason for audit trail integrity.
• Aggregate findings for your final review and executive certification.

Best Practices for Compliance Sampling

• Use automated audit files with workflow histories whenever possible—for consistency, time savings, and confidence.
• Leverage integrated Form 5500 data to ensure valid plan comparisons (required for accurate fee and expense ratio disclosure).
• Train advisors to collect and upload plan-level documents at the time of recommendation, not retroactively at review time.
• Consolidate all disclosure templates and forms in a centralized location retrievable for six to seven years to meet DOL retention standards.
• Document your methodology and sample rationale to defend decisions during regulatory scrutiny.

Frequently Asked Questions