Before you delete: is deleting the right fix?
Delete a transaction only when it shouldn't be in your books at all, for example something you imported by mistake or an exact duplicate. In these cases, don't delete:
The transaction is real but in the wrong category or account. Change its category instead. The bank side stays the same, so your reconciliations aren't affected. If it was categorized to a duplicate bank account that only exists in your chart of accounts, see Cleaning up a duplicate bank account.
You see duplicates from a bank feed. Check first with Find duplicate transactions in Puzzle. If many came from the same connection, contact us rather than deleting them one by one.
It's a manual journal entry. Use How to Delete or Void a Manual Journal Entry instead.
How to delete a transaction
Go to "Transactions" on the lefthand side of your Puzzle account.
Find the transaction in question (make sure the date picker reflects the range you want to apply).
You can also filter by amount.
To delete the transaction, click the check box on the far left.
A "Remove" option with a trash can icon will pop up on the bottom of the page.
You can then choose to remove it.
If you can't delete it
It's confirmed (green check). Uncheck the green check so it turns blue, then remove it.
It's included in a bank reconciliation (Accounting / Bank Recs). Go to that reconciliation and "Reopen" it, delete the transaction, then redo the reconciliation. If the reconciliation has already been approved, or deleting would change other accounts you've reconciled, contact us before reopening anything.
It's linked to another transaction, for example a transfer between your accounts, a credit card payment, or a Stripe payout deposit. Don't unlink it to get around this. Contact us with the date, amount and account.
Removing a customer payment shows "Something went wrong". This can happen when the payment sits on a deposit that's linked to a Stripe payout. Don't delete the deposit or unlink it. Contact us with the payment's date and amount, and we'll look into it.


