Categorized Transactions appearing in Suspense

I noticed this month an increase in the number of suspense transactions appearing under Find & recode and when I tried to clear them, I found out that many of them were already categorized a long time ago.

I tried to investigate the issue, but I couldn’t understand what led to this and the screenshots will only demonstrate what I was able to see at the time.

Unfortunately, I had to clear these transactions ASAP so I did and therefore, I cannot assess whether this bug persists in the current version.

I also didn’t cross check Suspense Account against Find & recode so I’m not able to do so at the moment after I cleared all transactions – unfortunately

1 Like

AFAIK Find & Recode doesnt support accounts which have sub-ledgers such as Accounts receivables, payables, employee clearing accounts etc.
So the transactions shown as suspense might not belong to Suspense account, but it might be transactions of a customer, supplier, employee or any other special account or capital account.
And i think Find & Recode is obsolete. Looks like Batch Recode will support all this in future.

Don’t know if its the issue or not but the accounts appear to be different.
Fixed Assets, Cost’ v ‘Fixed Assets, at cost’ maybe?

1 Like

Agreed, but it shouldn’t display Suspense because that wouldn’t be right

I’m not sure since I just clicked Edit then Update and it went away all by itself.

But looking at the first image, it does have a different name which is something to consider.

1 Like

I went back to these transactions and indeed, it now says Fixed Assets, Cost.

I assume that this was a remnant of the old method of Batch Create operation which used to accept subsidiary accounts inside the Account field.

Looking at History I believe I created this custom Control Account since at one point in time, using the default control account wasn’t supported for some reason so I had to create custom control accounts for everything. And since Find & recode doesn’t support Control Accounts, I had to use Batch Update and I must have missed some tabs.

I believe @lubos once mentioned that using a Subsidiary Account together with a wrong Control Account wasn’t going to cause any problems since Manager was supposed to fix these errors by itself, so I’m going to keep this in bugs until otherwise notice from @lubos.

1 Like

Sorry but most of your explanation seems to be user-error and not a “bug”. As such I moved it to uncategorized because it is unclear why this would be a bug.

By definition, A software bug is a problem causing a program to crash or produce invalid output.

The original entries were correct at the time they were entered. Future updates cannot render data that were valid under previous versions invalid in later versions – that’s counterproductive.

Such inconsistencies much be dealt with in the backend and not exposed to the user.

Also @eko, please read this:

So unless the developer backs out of this, this is a bug

1 Like