How is the "Quicken Name" field in transactions formed.

Banjo47

Is it just the first unique characters in a statement name? Is it better to use QN in renames than individual tokens? What's the purpose of QN?

jacobs

@Banjo47 There are "local" renaming rules, which are the ones you create yourself in Quicken, and there are the back-end or server-based renaming rules. They're supposedly community based, but how Quicken gathers and applies such data is hidden; you can't see or know how the server-based rules are set up, other than seeing the end results.

If you can create your local renaming rule based on the "Statement Name" -- the name coming directly from the financial institution -- then you can ignore the "Quicken Name". But if the Statement Name isn't something you can parse, sometimes creating a rule based on the Quicken Name is better, or the only way. For instance, if the financial institution transmits a Payee name of "HomeDepot123456", you can't use that for a renaming rule because the numbers after the name will be different on different transactions, and there is no delimiter (like a space, hyphen/slash, etc.) to create. a rule based on the alphabetic portion. But if the Quicken Name is "Home Depot", then you're in business.   

Banjo47

That's what I was looking for -- thanks.

Banjo47

Thank you. May 4 helpful but didn't answer how QN is formed other than "the name Quicken's back-end server thinks might be a more usable name". Can't narrow community search using Quicken Name, but you gave me idea to search under renaming rules. I'll try that.

jacobs

@Banjo47 There are "local" renaming rules, which are the ones you create yourself in Quicken, and there are the back-end or server-based renaming rules. They're supposedly community based, but how Quicken gathers and applies such data is hidden; you can't see or know how the server-based rules are set up, other than seeing the end results.

If you can create your local renaming rule based on the "Statement Name" -- the name coming directly from the financial institution -- then you can ignore the "Quicken Name". But if the Statement Name isn't something you can parse, sometimes creating a rule based on the Quicken Name is better, or the only way. For instance, if the financial institution transmits a Payee name of "HomeDepot123456", you can't use that for a renaming rule because the numbers after the name will be different on different transactions, and there is no delimiter (like a space, hyphen/slash, etc.) to create. a rule based on the alphabetic portion. But if the Quicken Name is "Home Depot", then you're in business.   

Banjo47

That's what I was looking for -- thanks.