Bank statements

Wallet export shows failed transactions: how to leave them out

A forum-style answer on keeping failed, pending and refunded rows from inflating your wallet spending, with a worked ₹ example and a SUMIFS formula.

Editorial illustration for Wallet export shows failed transactions: how to leave them out

The question: my wallet's transaction export lists failed payments along with real ones, so my spending total is too high, how do I exclude them? Most exports carry a column for the kind of entry and a column for its outcome. Filter on the outcome before you add anything, and your total will stop counting money that never left.

What we would do, in order

  1. Open the export and read the header row. Look for columns that describe the kind of entry, such as payment, top-up or refund, and the outcome, such as success, failed or pending. Names differ between wallets, so use whatever yours calls them.
  2. List the distinct values in the outcome column. In Excel, copy the column to a spare area and use Remove Duplicates; in Google Sheets, =UNIQUE(C2:C500) does it.
  3. Decide what each value means for your total. Success counts. Failed does not. Pending is undecided until it settles.
  4. Total with a formula that names the outcome rather than deleting rows. That way the evidence stays in the sheet.
  5. Compare with your bank statement or wallet balance before you trust the number.

A worked example with made-up numbers

DateTypeStatusAmount in ₹
02 MarPaymentFailed450
02 MarPaymentSuccess450
04 MarPaymentSuccess1,200
06 MarPaymentPending180
08 MarRefundSuccess300

Adding every payment row blindly gives 450 + 450 + 1,200 + 180 = ₹2,280. That is too high by ₹630, because the failed ₹450 and the pending ₹180 never left your balance. Counting only successful payments gives 450 + 1,200 = ₹1,650. Subtract the successful refund of ₹300 and your real spend is ₹1,350.

With types in column B, outcomes in column C and amounts in column D, the formulas are:

  • =SUMIFS($D$2:$D$500,$B$2:$B$500,"Payment",$C$2:$C$500,"Success")
  • =SUMIFS($D$2:$D$500,$B$2:$B$500,"Refund",$C$2:$C$500,"Success")
  • Net spend: the first result minus the second

What about pending rows?

Leave them out of the total, but do not forget them. Add =COUNTIFS($C$2:$C$500,"Pending") somewhere visible and look again after a few days. A pending item usually becomes either success or failed once the other side responds. If it still shows pending after a long time, check your own wallet balance and raise it with the wallet's support, quoting the date and amount.

Why does the same payment appear twice?

Often a failed attempt and a successful retry are both in the export, as in the 02 Mar rows above. The amounts match, but only one is real. A formula that filters on outcome handles it; a rule that deletes rows with matching amounts would wrongly delete genuine repeat purchases, like two identical canteen payments on one day.

Honest limits

I have not seen your export, so treat the column names as examples. If your wallet has no outcome column at all, you will have to compare it with the bank or card entry for the same day.

If you would rather not maintain formulas, SpendixAI takes statements as PDF, CSV or Excel and shows every row for review before saving, so you can delete a failed row yourself at that point. we would not assume any tool will read your wallet's outcome column unaided, so look at the review screen.

One more trap: exports sometimes include the same transaction twice when you download overlapping date ranges, for example the first to the fifteenth and then the tenth to the thirtieth. Those rows are identical, success and all, and a status filter will not catch them. Sort by date and reference or description and look at runs of identical lines before you total.

Final check

  • Outcome values listed and understood
  • Totals use SUMIFS on the outcome, not deleted rows
  • Pending rows counted and revisited
  • Total compared with the wallet balance or bank entry
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports