What to do first
Identify the charge, explain why it appears wrong, and ask for a correction, credit, refund, or written explanation.
Start with the Billing Dispute for Incorrect ChargeHow this guide was prepared
This guide is written to help readers handle a customer service message with enough context to choose, customize, and send the right template.
- Prepared for the Customer Service category, with links back to 14 related templates so readers can choose a matching format.
- Checked for practical include-and-avoid guidance, including 5 include points and 4 avoid points when available.
- Reviewed for cautious wording around records, policies, timing, and follow-up steps before a reader sends the message.
Read more about Simple Letter Templates or review the general-use disclaimer.
When to use this letter or template
- Use this guide when a company, seller, carrier, or support team needs enough detail to handle dispute a billing error in writing.
- Use it before contacting support so the order, account, date, problem, and requested resolution are easy to find.
- Use it when you need a written record for a refund, billing, delivery, return, or service issue.
Email, portal, or online message
Use email, chat transcript, or a support form when the company needs order numbers, attachments, screenshots, or tracking details.
Printed letter or signed note
Use a printed letter only when the company requests mailed documentation or when you need a formal written record.
Before you send
Save screenshots and confirmation numbers before closing support forms or chats.
What to include and what to avoid
Include
- Account, order, or invoice number.
- Charge date and amount.
- Expected amount.
- Supporting record.
- Requested correction.
Avoid
- Combining multiple unrelated issues.
- Missing deadlines.
- Assuming intent.
- Deleting statements or receipts.
Billing dispute evidence checklist
A record-keeping checklist for describing an incorrect charge and requesting a specific resolution.
- Account, invoice, order, or transaction identifier without including unnecessary sensitive numbers.
- Charge date, posted amount, and the amount being disputed.
- A concise explanation of why the charge appears incorrect.
- Receipt, confirmation, cancellation, return, or prior-support evidence.
- The specific correction, refund, explanation, or documentation requested.
- The response deadline or process stated by the provider, if one exists.
- The date, channel, and representative used for each contact.
- Copies of the final dispute, attachments, replies, and case numbers.
This checklist is general information, not legal or financial advice. Follow the provider's dispute process and any rules that apply to the account or payment method.
Tone examples
Neutral
Identify the charge, explain why it appears wrong, and ask for a correction, credit, refund, or written explanation.
Polite
Dear BrightBox Support, I am disputing the May 3 charge connected to Order #BB-48192. My receipt shows $42, but my statement shows $62. Please review and provide a correction or explanation.
Follow-up
Follow up after the company's response window or sooner if a payment-provider deadline is approaching.
Situation-specific advice
First support contact
Give the order, account, tracking, invoice, or purchase details before explaining the problem.
Refund or billing issue
Name the charge, amount, date, expected correction, and records that support the request.
Delayed response
Follow up with the original case number or message date so support can reopen the right record.
Mistakes to avoid and next step
Mistakes to avoid
- Combining multiple unrelated issues.
- Missing deadlines.
- Assuming intent.
- Deleting statements or receipts.
FAQ
Can I copy the example exactly?
Yes, but replace names, dates, account details, and any wording that does not match your situation.
Should I print it or email it?
Use the channel the school, employer, landlord, office, or company accepts, and keep a dated copy.
Is this advice?
No. These guides provide general writing help only; rules, forms, deadlines, policies, and requirements can vary.