nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Transaction Description/Payee Truncation

MSStateDawg

My local bank conducted a system upgrade in September 2021. Upon doing so, they changed the description of transactions so that the merchant name is at the end of the description string and it's being partially truncated by Quicken upon download.

Example of how it's coming across:

POS DEB 1439 12/22/21 15674088MERCHANTNAME #1366CITYSTATE

This is being truncated by Quicken to:

POS DEB 1439 12/22/21 15674088ME

As you'd expect, this is breaking payee renaming rules.

I've asked the bank to fix this by returning to the format they used prior to the system upgrade (i.e. merchant name at the beginning of the description) but I don't know if they'll go to the trouble.

Has anyone else encountered this issue and identified a fix/workaround?

Is there any way to configure Quicken so that it doesn't truncate the description?

Thanks.

Find more posts tagged with

Comments

Chris_QPW

Unless they also put the payee's name in the memo, there isn't anything that can be done about it.
The OFX standard that Quicken uses has a max of 32 characters. In fact, it is probably truncated before Quicken ever sees it.

MSStateDawg

Chris_QPW said:

Unless they also put the payee's name in the memo, there isn't anything that can be done about it.
The OFX standard that Quicken uses has a max of 32 characters. In fact, it is probably truncated before Quicken ever sees it.

Well, yeah, there's something that can be done about it. The bank can put the merchant name back at the beginning of the string.

Chris_QPW

Yes, I should have said there isn't anything Quicken Inc can do about it. The bank certainly can change it.