The payment provider and card network set the applicable process. This checklist is an organizational aid, not a promise of success or a replacement for the instructions attached to the dispute. The issuing bank generally decides the outcome in the ordinary card-dispute process described by the processor.
First, confirm what is being disputed
Identify the processor account, transaction reference, disputed amount, currency, cardholder name as available and associated case. Check whether the dispute concerns the full payment or only part of it. One funeral case can involve several payers and transactions, so the case total alone does not identify the disputed charge.
Read the reason and supporting claim carefully. A complaint about an unrecognized payment requires a different explanation from a complaint that a credit was not processed. A disagreement about a service description should not receive a packet focused solely on proof that a card was used.
Stripe's response guidance explains that response windows and evidence requirements depend on the dispute and network. Record the actual deadline shown for your case, assign an owner and leave time for review. Do not substitute a generic deadline copied from an article.
Create a short factual chronology
List the relevant events in order: agreement, payment, service or merchandise delivery, changes, complaint, refund activity and dispute notice. Use dates from the records. If a note was entered later, preserve that distinction rather than making it appear contemporaneous.
Keep descriptions neutral. “Family requested a change on this date” is more useful than an emotional characterization of the person. If the cardholder and arranging contact differ, explain the relevant roles without assuming that authority for disposition proves authority to use someone else's payment card.
The chronology should point to supporting records. It is an organizing page, not a substitute for evidence. A statement that the firm completed its work needs appropriate records for the particular claim being addressed.
Match documents to the reason
| Claim category | Records to review for relevance |
|---|---|
| Payment not recognized | Transaction details, receipt and relevant payer communications |
| Service not received | Agreed scope and appropriate dated service documentation |
| Service not as described | Accepted selections, disclosed terms and documented changes |
| Duplicate payment | References and records distinguishing the transactions |
| Credit not processed | Refund approval, processor refund reference and status |
| Cancelled service | Applicable policy, agreement and relevant cancellation record |
These are starting points. Follow the provider's requirements for the exact reason. Do not assume that a document helpful for one category is sufficient for another, or that an operational authorization settles a payment dispute.
Stripe's example evidence packets illustrate how evidence can be organized around different claims. Adapt the structure rather than copying an unrelated business's explanation into a funeral transaction.
Keep the accepted version of the agreement
Use the statement and terms the relevant party actually reviewed at the time, together with documented changes. A current website policy may differ from the policy in effect when the payment was made. Do not present a later revision as the earlier agreement.
For a changed selection, include the relevant change record and acceptance where applicable. The evidence should explain why an invoice differs from an earlier estimate. An unexplained mismatch can make an otherwise accurate packet difficult to follow.
The FTC's Funeral Rule guidance addresses funeral pricing and disclosures. It does not guarantee that a price document will win a card dispute. Treat accurate pricing records as part of responsible case work and evaluate their relevance to the processor's actual request.
Check refunds before taking another action
Locate any refund already initiated and distinguish requested, pending, completed or failed status according to the provider's records. A note saying “refund family” is not proof that the processor completed it. Preserve the reference and the amount.
If the payment is formally disputed, follow the processor's guidance before issuing a separate refund or replacement payment. Ask how the existing dispute affects the available action. Do not create a second financial event simply because staff want to resolve the complaint quickly.
Keep family communication respectful and factual. If the matter is resolved directly, retain the relevant communication and still complete the required processor process. A conversation with the cardholder does not automatically close a formal dispute in the provider's system.
Limit unrelated information
Review the packet for unnecessary identity numbers, card information, unrelated medical details and private correspondence. Include what is relevant to the claim through the provider's approved submission channel. Do not upload the entire funeral file merely because it is available.
Use clear labels and a readable sequence. A reviewer should be able to identify the payment, understand the claim and find the supporting page without opening a case-management account. Where the provider requires embedded documents, a link to an internal folder is not equivalent to submitting the evidence.
Stripe's guidance says its response is forwarded when submitted and cannot then be amended through the ordinary submission flow. Other providers may differ. Verify the current rules and review the final packet before the authorized employee submits it.
A fictional partial-credit dispute
A family paid an itemized account and later received approval for a partial credit after a changed selection. The office recorded the approval, but a staff handoff left uncertainty about whether the refund was processed. A dispute then arrives concerning that amount.
The owner first identifies the exact payment and checks the processor's refund record. The team assembles the original selection, documented change, credit approval, relevant communication and actual transaction status. The explanation distinguishes approval from completed processing rather than treating them as the same event.
If the refund was completed, the packet uses its reference and dates. If it was not, the owner follows the provider's instructions for the live dispute. The team does not invent a completion date or use a newly entered note as if it were the original record.
Review and submit deliberately
Have the responsible employee verify that the amount, case and payment reference agree throughout the packet. Check the provider's current file-type, size and submission rules. Remove duplicate pages that add no relevant information, while retaining the supporting material needed for the claim.
Record the submission date, submitting employee, evidence version and confirmation. Assign someone to monitor the outcome and any further instructions. Submission is a milestone, not a final accounting result.
When the decision arrives, reconcile the financial effect with the case account and accounting records. Keep the outcome and fees traceable. Avoid reporting the dispute as resolved financially merely because staff uploaded a response.
Improve the underlying records
Afterward, ask what was difficult to retrieve. Was the accepted statement unclear? Did staff confuse a promised refund with a completed one? Was the payer's role missing? Turn those findings into targeted process changes rather than asking employees to collect unnecessary information from every family.
FuneralHQ's features include case documents and payments. In a demonstration, ask how your team would retrieve the relevant agreement, transaction reference and change record. This guide does not claim that FuneralHQ automatically submits or wins disputes.
Use the blank evidence inventory to organize relevant records. Keep completed packets in approved storage and follow the processor's live instructions for the transaction in question.
The FuneralHQ advantage
The family balance and the books should agree
FuneralHQ keeps card and ACH activity, payment plans, case balances, and QuickBooks Online connected so staff can answer the family and accounting can reconcile the same record.
We will work through a real example with you, from the first details to the finished record.
See it on one of your casesAbout the FuneralHQ Editorial Team
This guide was written by the FuneralHQ Editorial Team, the in-house team behind funeral home software used by independent firms to run cases, documents, payments, and QuickBooks sync in one record. Our editorial standards explain how we review product claims, outside sources, automation, updates, and corrections.