Reg E Audit Documentation
Reg E Evidence Package Checklist — What Examiners Expect in Every Dispute File
When examiners sample Reg E cases, they expect a complete, organized evidence package for each one. Banks managing disputes in spreadsheets, email, and core notes typically cannot produce this package on demand — which is itself a compliance finding.
The seven components of a complete Reg E evidence package
A complete Reg E case file is not a spreadsheet row or a core system note. It is a structured package that can be handed to an examiner and tell the complete story of the dispute from intake to resolution.
Original dispute intake record
The intake record documents the initial error notice received from the consumer. It must capture the date of receipt — which starts the investigation clock — the account number, the disputed transaction details, the reported error amount, and the method of notice (oral or written).
Examiners look for
- Exact date and time the error notice was received
- Method of notice: oral (phone, in-branch) or written
- Name of the staff member who received the notice
- Disputed transaction amount, date, and type
- Account number and consumer identification
Spreadsheet and email control risk
Intake records created in email, core system notes, or separate branch logs are not connected to the investigation record. Examiners who request the original intake for a case frequently find banks cannot produce a single, dated intake document.
Deadline path applied and documented basis
The evidence package must show which investigation deadline path was applied to the case and why. Examiners verify that the correct path was selected based on transaction type and account age — not that it was simply applied without documentation.
Examiners look for
- Which deadline path was applied: 10-day, 20-day, 45-day, or 90-day
- Transaction type used to determine the path: ACH, POS, foreign-initiated
- Account age at the time of receipt for new account path determinations
- Calculated deadline dates for investigation completion and all related notices
- Any change to the deadline path and the documented reason for the change
Spreadsheet and email control risk
Spreadsheets may show a deadline date, but they rarely document which path was applied or why. When examiners ask why a 45-day path was used instead of 10-day, the answer must exist in the case record — not in a staff member's memory.
Required letters with proof of send
Regulation E requires written notices at specific points in every investigation. The evidence package must include a copy of each letter that was required and sent, together with proof of send and the date sent. Missing or late letters are among the most common exam findings.
Examiners look for
- Confirmation of receipt letter with date sent
- Provisional credit notice with amount, availability date, and send date (if credit was issued)
- Final resolution letter at the conclusion of a case found in the consumer's favor
- No-error explanation including consumer's right to request relied-upon documents (if bank found no error)
- Reversal notice with date sent and scheduled debit date (if provisional credit was reversed)
Spreadsheet and email control risk
Letters generated in email or word processing tools outside the case record are not automatically linked to the case. Proof of send — whether postal confirmation or email delivery — is rarely captured at all. Banks frequently cannot show examiners when a letter was sent or prove it was sent on time.
Provisional credit history
For any case where provisional credit was issued, the evidence package must document the full lifecycle: the amount credited, the date made available, the notification sent, whether the investigation concluded in the consumer's favor or not, and if not, the reversal notice timing and debit date.
Examiners look for
- Amount of provisional credit issued and date made available to the consumer
- Provisional credit notice sent on or before the credit date
- Final disposition: credit was made permanent (investigation found in consumer's favor) or reversed
- If reversed: reversal notice sent at least 5 business days before the debit date
- Actual debit date if provisional credit was reversed
Spreadsheet and email control risk
Provisional credit is often tracked in the core banking system separately from the dispute investigation record. Banks managing Reg E in spreadsheets frequently cannot link the credit issuance, notice timing, and reversal history to a single case document.
Investigation notes and supporting documentation
The investigation notes document what the bank actually did to investigate the error: what was reviewed, what was contacted, what was analyzed, and what conclusion the investigation reached. Supporting documents include transaction records, network responses, and any other evidence the bank relied on.
Examiners look for
- Dated notes documenting each investigative step taken
- Source documents the bank reviewed: transaction records, merchant data, network dispute responses
- Any third-party contacts made during the investigation
- Explanation of why the bank reached its conclusion based on the evidence reviewed
- Any exculpatory or contradictory information and how it was addressed
Spreadsheet and email control risk
Investigation notes entered into a spreadsheet cell are not structured evidence. There is no timestamp, no attachment mechanism, and no way to verify the notes were written contemporaneously. Examiners expect a documented investigation trail, not a summary cell.
Resolution decision and documented basis
The evidence package must include the final resolution decision — error found in the consumer's favor, no error found, or partial error — and the documented basis for that decision. This is the record a bank defends during an examination.
Examiners look for
- Final resolution outcome: error found, no error found, or partial error
- Date the investigation was completed relative to the applicable deadline
- Documented basis for the decision referencing the evidence reviewed
- Required letter sent at conclusion: final resolution letter or no-error explanation
- Consumer's right to request documents relied upon if no error was found
Spreadsheet and email control risk
Spreadsheets may record an outcome — Yes/No/Partial — but they rarely capture the documented basis for the decision. When examiners ask why a case was closed as no error found, the answer must be in the case record, not in an email thread.
Complete case package export
When examiners request case files, banks must be able to produce a complete, organized package for each case on demand. This means all six elements above assembled into a single coherent file — not a collection of emails, spreadsheet rows, and core system screenshots gathered after the fact.
Examiners look for
- All required documents assembled in a single package per case
- Documents organized and legible for examiner review
- Produced without delays that suggest the bank assembled the package after the request
- Complete record for every case in the sample, not just selected cases
Spreadsheet and email control risk
Assembly after the fact is the single most common Reg E exam finding for banks managing disputes in spreadsheets, email, and core notes. Examiners know post-hoc assembly when they see it — gaps in timing, inconsistent formatting, and missing items give it away.
Why Reg E evidence assembly fails in spreadsheets and email
The evidence package problem is not a documentation discipline problem. It is a systems problem. When the components of a case file exist in five different places, no amount of process discipline produces a clean package on demand.
Case files distributed across multiple systems
Intake is in the core. Letters are in email. Provisional credit is in a separate tracking sheet. Investigation notes are in a shared folder. No single document assembles the complete picture.
No proof of send captured at letter generation
Letters printed and mailed or sent from a personal email account leave no automatic proof of send linked to the case. Reconstructing send dates after an exam request requires searching email archives.
Provisional credit tracked separately from the dispute
Core system entries for provisional credit are not linked to the dispute intake record. The investigation file and the credit history are in separate systems with no connective thread.
Investigation notes are unstructured and unverifiable
Freeform notes in a spreadsheet cell, a core memo field, or a shared document have no timestamp, no author attribution, and no mechanism for verifying they were written during the investigation rather than after a request.
Cannot produce a complete package on demand
Assembling a complete case file from distributed sources takes hours per case. Examiners who request thirty cases at once expose this gap immediately. The time required to respond is itself evidence of the control deficiency.
How KohltSoft assembles the evidence package
- All seven evidence components are captured in one case record from intake through resolution
- Letters are generated within the case and proof of send is captured automatically
- Provisional credit issuance, notification, and reversal history are attached to the case timeline
- Investigation notes are timestamped and linked to the case record
- The audit timeline shows every action taken, by whom, and when — immutably
- Complete case packages are exportable on demand for any case in any date range
Frequently Asked Questions
What documents does a bank need for a Reg E exam?
Examiners expect a complete evidence package for each case reviewed: the original dispute intake record with the date received, the deadline path applied and its documented basis, all required letters with proof of send, the complete provisional credit history, investigation notes and supporting documents, and the final resolution decision with documented basis. Banks that cannot produce this package on demand typically have a control deficiency finding.
What is a Reg E examiner evidence package?
A Reg E examiner evidence package is a complete, organized case file assembled for each dispute investigation. It includes the intake record, deadline path documentation, all required Reg E letters with proof of send, provisional credit history, investigation notes, and the resolution decision with its documented basis. When examiners request case samples, banks must produce these packages on demand.
What are the most common Reg E audit findings?
The most common Reg E audit findings include: missing or late required letters (particularly provisional credit notices and reversal notices), inability to produce complete case documentation on demand, incorrect deadline path applied to the dispute type or account age, provisional credit not issued within the required window, and investigation notes that do not document the basis for the bank's decision.
How should banks document Reg E dispute investigations?
Reg E dispute documentation should be centralized in a single case record that captures: the date the error notice was received, the deadline path calculated from intake, all required letters with send dates and proof of send, provisional credit issuance and notification, dated investigation notes with supporting documents, and the final resolution decision with its documented basis. Documentation created after an exam request rather than contemporaneously with the investigation is a common finding.
See a sample Reg E evidence package
Request a demo to see how KohltSoft assembles a complete, examiner-ready evidence package for a Reg E dispute case using your bank's dispute types.
Request a DemoRegulation E compliance reference: This page describes documentation requirements under 12 CFR § 1005.11 (Electronic Fund Transfer Act). For legal interpretation, refer to the official regulation at consumerfinance.gov/rules-policy/regulations/1005/11/ and ecfr.io/Title-12/Section-1005.11. KohltSoft does not provide legal advice.