Repair duplicate-payment register
Compare observed link and counter transactions against one approved repair order.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Repair-order reference | Provider payment reference | Collection channel | Observed amount | Verified provider status | Investigation owner | Resolution evidence |
|---|---|---|---|---|---|---|
| RO-example-1 | Link-example-1 | Payment link | 1200 | Captured, example only | Office-role | Check against counter capture |
| RO-example-1 | Counter-example-1 | Counter | 1200 | Captured, example only | Office-role |
- Starting records are fictional examples, not merchant evidence.
- Keep private documents and actual contacts in your approved business system. Use internal reference codes here.
- Missing required fields indicate an unresolved record. Filled fields do not prove authorization, completion, compatibility or compliance.
- Export to approved business storage. Browser edits are cleared on reload.
Check the repair order and the provider payment record before charging at pickup. A customer who paid through yesterday’s text link should not face a second collection because the counter screen still shows an old balance. Match the actual transaction to the repair order, confirm its status, and resolve the mismatch before asking for another payment.
Use with this guide
split-payment reconciliation guide
The split-payment reconciliation guide explains the separate allocations when more than one payment is intentional.
processor changeover reconciliation
Use processor changeover reconciliation when the original and duplicate payments belong to different accounts.
Browse the complete auto repair guides and worksheets.
Start with the repair order, not the bank screenshot
The current invoice reference, approved total of the repair order, payment-link reference and counter transaction reference should all be stored against the customer’s personal details within your approved shop system. The public worksheet should only include the internal codes for the payment and not a screenshot of the customer’s card details showing that money has been removed from their account. The status of the payment can only be verified by checking the provider’s record of the transaction.
Square’s failed-payment guidance distinguishes a pending card charge from a completed payment. A canceled or interrupted attempt might leave a temporary hold visible to the customer. Do not call every pair of bank entries a duplicate sale. Compare the provider references, amounts and statuses first. Ask support to explain an uncertain record before deciding whether another collection or a refund is appropriate. The split-payment reconciliation guide explains the separate allocations when more than one payment is intentional.
Sources for this section: Square: troubleshoot failed payments and pending charges
Reconcile the amount against one approved invoice
You can fill out the fields for the duplicate-payment register for each payment transaction observed. The fields needed for recording duplicate payments are for the repair order linked to the payment, the reference of the payment, the payment channel, the amount of the payment, the status of the payment with the provider, the investigator for the payment and for the payment also evidence for the solution of the problem. The fields for the link payment and the counter payment have to be filled out completely. Missing evidence has to be left unresolved.
Consider an illustrative repair invoice of $1,200. A captured payment-link transaction for $1,200 and a captured counter transaction for $1,200 represent $2,400 collected against one $1,200 bill. The apparent excess is $1,200 before checking refunds or other authorized work. A pending authorization for $1,200 beside one captured $1,200 payment is a different situation. The status changes the action, even though the visible amounts match.
Assign the correction and prevent a second refund
If the investigation confirms an excess collection, assign one person to the approved correction. Record the original payment being refunded and the new refund reference. Stripe’s refund documentation states refunds return to the original payment method and distinguishes pending, successful and failed refund states. Those are Stripe-specific procedures. Obtain the equivalent instructions from your actual processor rather than treating a replacement card or cash reimbursement as interchangeable.
Check for an existing dispute or refund before submitting another action. Stripe documents a risk of duplicate reimbursement when a pending refund overlaps with a dispute. Tell the customer the verified status and the next update you own. Avoid promising an issuer posting time the provider has not confirmed. Update the repair-order balance only from the resolved collection and refund evidence.
Sources for this section: Stripe: refund destinations, funding, statuses and failures
Fix the handoff between remote payment and pickup
Using the payment provider’s test environment, test a completed payment link, a payment that fails part way, and a payment that is only partially successful. Observe what the counter shows in each case. Does the invoice balance get updated? Are you able to see the payment reference on the invoice? Who is responsible for dealing with an unknown status? Note down your results for your specific shop software and payment gateway.
Keep the pickup checklist short: open the current repair order, inspect its payment history, verify the remaining balance and collect only the approved unpaid amount. Review duplicate cases during the weekly office meeting. Track the cause, such as stale balance, missing reference or an interrupted payment, rather than blaming the customer. A clean process reduces correction work without requiring another software subscription. Use processor changeover reconciliation when the original and duplicate payments belong to different accounts.
Primary sources
BlueFinch last reviewed these sources on October 4, 2026. Payment rules and state requirements can change.
- Square: troubleshoot failed payments and pending charges
- Stripe: refund destinations, funding, statuses and failures
Use this page for general business information. It is not legal, tax, or accounting advice.