Fishbowl: "Transaction already posted" — can't delete a POS sale

What triggers it

You are trying to delete a POS transaction that has already been exported to your connected accounting system. The message may name the system that received it. Once a sale has been sent to QuickBooks or Xero, Fishbowl treats it as committed to your books and will not let you erase the Fishbowl side out from under it.

Why Fishbowl blocks it

Deleting the transaction here would only remove it in Fishbowl. The matching record on the accounting side stays put, because that record was posted in a separate system that Fishbowl does not reach back into. You would end up with revenue, tax, and a payment sitting in your general ledger with no corresponding Fishbowl sale, and with inventory that may have already been relieved for goods now tied to a sale that no longer exists in Fishbowl. That mismatch is exactly what breaks reconciliation, so Fishbowl refuses the delete instead of quietly creating it.

What to do

Reverse it, do not delete it. Issue a refund against the original transaction, or post a reversing entry that offsets it. This is an accounting correction, not a simple undo: you are leaving the original record in place and adding its mirror image so the two net to zero. Both Fishbowl and your accounting system then hold a complete, matching history, and any inventory that was relieved gets returned through the refund rather than stranded.

If it is already reconciled or exported

If the sale has already been reconciled or bank-matched on the accounting side, do not delete anything in either system to make them agree. Correct it with a refund or reversing entry dated appropriately, and let the reversal flow through the same export path the original used. That keeps the audit trail readable and keeps your inventory valuation and your ledger in step, which is the whole point of running Fishbowl and your accounting system as one reconciled pair.