Reg E Dispute Intake Form
Use this Reg E Dispute Intake Form to capture an EFT error claim, the disputed transaction details, and the consumer statement needed to start an investigation.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Banking · Credit Unions · Fintech · Consumer Financial Services
Overview
This Reg E Dispute Intake Form template captures the information a financial institution needs to open and track a consumer Electronic Fund Transfer error claim. It is organized around the consumer acknowledgement, contact details, account and transaction specifics, the dispute reason, and any supporting documents or notes that help the investigator understand what happened.
Use this template when a consumer reports an unauthorized transaction, an incorrect EFT amount, a missing transfer, an ATM issue, or another Regulation E error that needs formal review. The structure helps staff collect the date noticed, the transaction date, the merchant or payee name, and the consumer’s statement in a consistent format that supports an audit trail and reduces follow-up questions.
Do not use this form as a general complaint log for non-EFT issues, card chargebacks, loan disputes, or account servicing requests that do not require a Reg E investigation. It is also not the right place to collect unnecessary PII or sensitive data that the institution will not use. Keep the form focused on the minimum necessary fields, use clear required-versus-optional labels, and add conditional logic only where it helps the consumer provide the facts that apply to their specific dispute.
Standards & compliance context
- The form supports Regulation E intake by capturing the consumer’s dispute reason, transaction details, and date noticed in a structured way that can feed an investigation record.
- Collect only the minimum necessary PII and explain the purpose of each contact field to align with data minimization principles.
- If the form is public-facing, make the fields and labels accessible and readable enough to support WCAG 2.1 AA expectations.
- If the intake is used in a regulated workflow, retain an audit trail showing when the claim was submitted, what was disclosed, and who handled the case.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Submission Notice and Consent
This section sets expectations for the consumer, explains contact permissions, and records that the submission is intended to start a dispute review.
- I understand this form is for Regulation E / EFT error claims and that the information provided will be used to investigate my dispute.
- I consent to being contacted about this dispute if additional information is needed.
- Submission type
Consumer and Contact Information
This section identifies who is filing the claim and how the institution can reach them without collecting unnecessary PII.
- Full name
- Preferred contact method
- Email address
- Phone number
- Mailing address
Account and Transaction Details
This section captures the specific EFT record that needs review so investigators can locate the transaction quickly.
-
Account ending in
Enter only the last 4 digits of the account number.
- Transaction type
- Date of transaction
- Transaction amount
- Merchant or payee name
- ATM location
Error or Dispute Reason
This section documents why the consumer believes the transaction is wrong and preserves the timeline needed for investigation.
- What is the issue?
- Date you noticed the error
- Describe what happened
- Statement about authorization
- Have you already contacted the merchant, payee, or financial institution about this issue?
Supporting Information
This section gives the consumer a place to attach evidence and add context without forcing every case to include the same documents.
- Supporting documents
- Additional notes
How to use this template
- 1. Configure the submission notice to explain that the form starts a Reg E dispute review, what contact methods may be used, and what happens after the consumer submits it.
- 2. Set the consumer and contact fields to collect only the PII needed to reach the filer and match the claim to the correct account, using the account suffix instead of the full account number when possible.
- 3. Build the transaction section with date pickers, numeric inputs, and short text fields so the consumer can enter the disputed EFT details without guessing at formatting.
- 4. Use conditional logic in the dispute reason section so follow-up prompts appear only when relevant, such as an unauthorized statement, attempted resolution details, or an ATM location.
- 5. Review the supporting documents and notes, then route the submission to the investigation owner with an audit trail that records the intake time, source, and any consent to contact.
Best practices
- Mark only the fields you truly need as required, and keep supporting documents optional unless your workflow depends on them.
- Use a date picker for transaction date and date noticed, and use a numeric field for transaction amount to avoid formatting errors.
- Ask for the account suffix instead of the full account number when that is enough to identify the account internally.
- Include a plain-language line that tells the consumer what happens after submission, including who will contact them and by which method.
- Use progressive disclosure so unauthorized claims, ATM disputes, and merchant disputes each reveal only the follow-up fields that apply.
- Capture the consumer’s statement in their own words when possible, because that helps investigators understand the timeline and intent.
- Avoid collecting unrelated PII, such as SSN or date of birth, unless your internal process specifically requires it and you disclose why.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What kinds of disputes does this form cover?
This template is for consumer claims involving electronic fund transfer errors under Regulation E, such as unauthorized transactions, incorrect amounts, duplicate debits, or ATM-related issues. It is designed to capture the facts needed to open an investigation, not to decide the claim on the spot. If the issue is a card chargeback, payroll error, or a non-EFT banking complaint, a different intake form may fit better.
Who should complete this form?
The consumer should complete it whenever possible, because the form asks for the unauthorized transaction statement, date noticed, and attempted resolution details. A branch associate, call center agent, or back-office specialist can also complete it while documenting the consumer’s responses. If someone else submits on the consumer’s behalf, the submission should clearly note that relationship and any consent to contact.
How often is this form used?
Use it each time a consumer reports a separate EFT error or dispute that needs investigation. If multiple transactions are part of the same event, the form can be customized to allow one submission with multiple line items or a linked case record. Avoid combining unrelated disputes into one record unless your workflow and audit trail can still track each transaction clearly.
What information is essential versus optional?
The essential fields are the consumer identity, contact method, account suffix, transaction details, dispute reason, date noticed, and the consumer’s statement of the error. Supporting documents and additional notes are useful but should remain optional unless your process truly needs them. Under data minimization principles, do not add sensitive fields unless they are necessary for the investigation.
Does this form need consent language or a disclosure?
Yes, if you collect PII or contact information, the submission notice should explain what will happen after submission and how the consumer may be contacted. The form should also make clear whether the consumer is authorizing follow-up by phone, email, or mail. If your workflow records an audit trail, note that in the notice so the consumer understands how the intake will be handled.
What are common mistakes when using this template?
Common mistakes include using free-text fields for dates or amounts, making every field required, and failing to capture the date the consumer noticed the error. Another frequent issue is omitting the unauthorized transaction statement, which can slow the investigation. The form should also avoid asking for unnecessary data such as full account numbers or unrelated personal details.
Can this template be customized for branch, call center, or online intake?
Yes, and it should be adapted to the channel that collects it. Online versions can use conditional logic and progressive disclosure, while branch or call center versions may need clearer prompts and internal guidance. You can also add routing fields, case status, or internal owner fields if they support your investigation workflow and audit trail.
How does this compare with an ad-hoc email or phone note?
An ad-hoc note often misses required facts, uses inconsistent wording, and makes it harder to prove what the consumer reported and when. This template standardizes the intake so staff collect the same core fields every time and can route the case faster. It also reduces back-and-forth by prompting for the transaction details and supporting information up front.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
Workforce software that meets employees where they are with calendar sync, pay, PTO, and schedules in one easy workflow.
-
Discover 7 common intranet platform failures that exclude frontline workers—and the specific capabilities that close the gap for deskless teams.
-
Frontline managers juggle disconnected scheduling, time, and leave systems. Learn why the coordination tax compounds and how a shared data layer removes it.
-
Improve employee productivity with actionable strategies, modern collaboration tools, and a digital workplace that boosts efficiency.
Ready to use this template?
Get started with MangoApps and use Reg E Dispute Intake Form with your team — pricing built for small business.
