forum.mthbuilt.com

First off, love the program, keep up the great work.

My technical issue - when I'm listing out my account, or when I attempt to run a report (Top 20) - it lists the Payee as "Dbt Purchase" as imported from my QIF file... the memo lists out the detail (Dunkin Donuts for example). Is there a way to harness the information I'm importing to show the Memo data as the Payee, or possibly alter the reporting capabilities that would list out by the memo? I looked at the Import/Export Data Matching, but it appears to only affect the Payee (NAME) field.

I tried writing a custom report, but I'm a Linux guy, not a SQL guy Is this an issue with the way my bank is exporting the data, and is there a work-around? Any help you could provide would be great, thanks!

There was a request a while back I think from someone from Australia to add a refactoring function to swap Payee and Memo fields on transactions, his bank consistently generated statements with a meaningless payee but memo field actually had some information.

I think it is similar to what you are describing ? Would that close this issue if we add this ?

I think that would work, I think the only concern I would have is if the Memo field is Null. For example, here is an excerpt from my OFX file (I removed the address/towns):

...
<NAME>POS PURCHASE
<MEMO>STOP &amp; SHOP #630 ADDRESS TOWN
...
<NAME>DBT PURCHASE
<MEMO>DUNKIN #340368 Q35 TOWN STATE
...

So those have a useless NAME field but a MEMO field I'd love to have information on. But for example, I wouldn't want to swap any fields for this type of transaction:
...
<NAME>PAYPAL TRANSFER
...

As there is no MEMO field available. I'm sure this is obvious to you, but I want to provide as much info as possible for you to add this feature, being a lowly end-user. If you need more information or samples, please let me know and I will be happy to give you what I can. Thank you so much for your response.

Thanks, we will check that memo field does have valid information before swapping. What transactions to swap (leaving paypal intact but changing db payment) will be up to the user obviously, you can filter transactions or do a multiple transaction select before running swap refactor.

We will add this to the feature pipeline, should be in in build 31/32 timeframe.

Sounds great, I can't wait. Thank you!