You cannot edit or delete this transaction because payments have been made against it
The program is blocking your edit because a payment or receipt is linked to that invoice or bill, so the link must be removed first.
“You cannot edit or delete this transaction because payments have been made against it.”
This message is a guard, not an error. The software is telling you that the transaction you are trying to change or remove has already been paid, at least in part. An invoice with a receipt against it, or a bill with a payment against it, cannot simply be deleted, because doing so would leave the payment pointing at nothing and your books out of balance.
In plain language: the transaction is locked because something else depends on it. Nothing is broken. You just have to undo the dependency before the software will let you touch the original entry.
Which transactions does this affect?
The block appears most often on customer invoices and supplier bills. Once a customer payment, a receipt, or a bill payment is applied, the parent document becomes protected. The same logic can apply to other linked pairs, such as a deposit against an order.
The rule is consistent across accounting systems, including Sage 50 (sold as Peachtree in the US and Simply Accounting in Canada) and QuickBooks: money in must stay matched to the document it paid.
How do you unlock the transaction?
Work in reverse order. Remove the payment first, then edit or delete the original transaction.
Start by finding the payment that was applied. Open the customer or supplier account and look through their activity for the receipt or payment in question. Void or delete the payment, or unapply it if your version allows that. Once no payment is linked, the invoice or bill should open for editing or deletion.
If the period has been closed, you may need to reopen it temporarily, or post a correcting entry instead. Whether you can reopen a closed period depends on your version and your accounting controls, so check with whoever manages your books before doing so.
Is deleting the right move at all?
Often, no. If the invoice was paid and the payment was real, deleting both leaves a gap in your history. A credit note or an adjusting entry is usually the cleaner fix. It preserves the audit trail and keeps your bank reconciliation intact.
Our engineers’ general advice: delete only when the transaction was a genuine mistake and never should have existed. Correct, rather than delete, when the transaction was real but wrong.
What if the payment is in a closed period?
This is where it gets awkward. You may not be able to remove the payment without reopening the period, which may not be allowed. In that case, post the correction in the current period instead. A credit note dated now, applied against the same account, achieves the same result without disturbing closed books.
What if the link is wrong and nothing should be blocking you?
Occasionally the message appears when no visible payment exists. That usually means a link inside the data is stale or damaged, perhaps from an interrupted posting or an interrupted conversion. This is a data problem rather than a workflow problem, and it is not something to force through by hand.
If you suspect that, stop making changes and take a backup. Then get the file looked at before more postings build on top of the bad link. We offer a free evaluation of files in this state, and if the link turns out to be damage rather than a real payment, repairing it is a routine job.