Find & Fix Duplicate Charges
Now and then a card gets charged and the sale doesn't line up behind it. The customer's statement says one thing, your day says another, and at closing the batch won't match. Find & Fix Duplicate Charges is the screen that sorts that out.
It lists charges sitting at your processor that don't have a matching sale in TORO, works out what most likely happened to each one, and gives you the one button that fixes it.
To open it: Dashboard → Transactions tab → Find & Fix Duplicate Charges card. When your card machine is integrated with TORO, the drawer close window also has a Find & Fix Duplicate Charges button, and if the card totals don't match it opens this screen for you before you close.
Why a Charge Ends Up Loose
The most common cause is worth understanding.
When the card machine approves a payment, TORO goes back to the processor to confirm it. If that confirmation can't get through — even for a second, on a flaky connection — the customer's card has already been charged, and a cashier who rings the sale up again as Cash or Other to get the customer out the door leaves that charge loose.
So when TORO can't reach the processor to double-check an approved payment, it accepts the approved payment, tells you plainly not to run the card again, and asks you to check it here before you close the drawer.
Reading the List
Each row is a charge at the processor, with TORO's read on what it is. The two you'll act on:
CHARGED, RUNG AS CASH → RELINK (or whichever tender the sale was rung as). The card really was charged, and the sale was rung as Cash or Other. The customer paid once, by card. Press RELINK Charge to Sale #___ and TORO moves the sale onto the card payment.
Nothing is charged again and nobody is refunded. All this does is correct how the sale was paid, so your day matches the processor's deposit.
A genuine duplicate. The customer really was charged twice. VOID This Charge gives back the one that shouldn't be there.
Rows already voided, or already refunded, are marked as such so you don't work them twice.
The Warning You Should Not Click Past
If you press VOID on a charge TORO has flagged for RELINK, it stops you with a warning. Read it.
Voiding one of those refunds a customer who only ever paid once — you're out the money — and leaves the sale on your books recorded against money nobody handed over. It's a loss in both directions. The screen steers you to RELINK instead, which is almost always what you actually want.
When the Sale Was Never Saved
Sometimes there is no sale to relink to, because the sale never got saved at all — the card machine took a few seconds too long, TORO gave up waiting, and the cashier closed the ticket. The charge still went through.
TORO can rebuild that sale for you. The row reads MISSING TRANSACTION → Located with N items, and View Proposed Transaction shows you exactly what it is going to record before it records anything: the items that were on the ticket, the customer, the cashier who rang it, the time it happened, and any discount that was applied to a line. Press Create This Transaction and it is saved. The card is not charged again.
If anything looks wrong, use Manually Build Transaction in TORO instead — same rebuild, but you can add or remove items and change a discount first.
The total has to match the charge exactly. If the items add up to less, TORO fills the difference with a Miscellaneous line so the sale still balances. If they add up to more, it tells you it is OVER and will not let you record it until you take something off — a sale worth more than the money you were paid would leave your books wrong.
Changing a discount
Both rebuild screens show a Discount column, so you can see what came off each line (a dash means nothing came off). On the build screen, select a line and press Edit Discount to set or clear it — it opens the same discount window you use at the register, with the same limits.
This matters when a rebuilt sale comes out OVER: a missing or mis-applied discount is the usual reason.
The Other Buttons
- Manually Build Transaction in TORO — for a charge where no sale exists at all, so you can construct the matching sale.
- View Sale #___ — opens the sale a charge is tied to. On a likely-duplicate row it reads View Likely Duplicate Transaction, and on a missing-sale row View Proposed Transaction.
- View Payment on PayaConnect — opens the charge at your processor, when you want to see it from their side.
- View Trace — the technical record, for when support asks.
- Open Batch Analysis Tool — jumps across to the batch tool if you're chasing a whole day rather than one charge.
Right-click any charge to copy its processor key, its payment ID, or all of its details at once. That's the one to remember when support asks you to read a long code over the phone.
When to Run It
Before you close the drawer, on any day where a card payment behaved oddly — a terminal that hung, a "not in the batch" message, anything a cashier rang as Cash after the card had already gone through.
It's much easier to fix on the day. Once the batch has settled and the deposit has landed, you're reconciling against a bank statement instead of a screen.