Well, @sharpdrivetek, I believe we must agree to disagree. In my view, this is not a case of transactions Manager cannot properly resolve, but of transactions where there is nothing to resolve. When there is sufficient information to create a situation requiring resolution, Manager places the transaction into Suspense. But that implies the program cannot properly resolve either the debit or the credit leg of the transaction. In the situation being discussed, neither can be identified, which is what makes the transaction meaningless.
Nevertheless, Manager still preserves what has been entered, conforming to the Guide. But that Guide is about clearing the Suspense account, not about everything that can happen when erroneous entries are made. The fact is, placing one of these meaningless transactions into Suspense would require the program to generate other transactions to balance the credit or debit to Suspense. And that would make the problem worse, as I mentioned before. The current approach (1) preserves any data entered, (2) avoids corrupting either the balance sheet or P&L statement, (3) prevents additional, artificial ledger entries, yet (4) still provides easy detection of the error in the tab listings.
That is why I don’t consider this a bug. @lubos is free to make a different decision, of course.