Reply to topic

Skrooge potential duplicates issues, improvements

User avatar skierpage
Registered Member
Posts
15
Karma
0
OS
Hi. I entered a bunch of charitable donations into Skrooge, many made online with my credit card, on the same day that I donated. I then imported the QFX file from my bank for the same period, resulting in a lot of duplicate operations. So Go > Open potential duplicates... , however this does not show most of the duplicate pairs. I think I know why, elsewhere smankowski commented
The "Open potential duplicate" function opens a page with operations having same amounts and same dates.

(^ This information needs to go in the Skrooge handbook in both the menu description and the section on merge operations which doesn't mention the feature). The problem is the date of the QFX transactions in Skrooge is the <DTPOSTED> from the QFX file, usually one or two days after the date that I made the payment. So none of the transaction pairs appear in "Operations potentially duplicated".

There's another date in the QFX file, <DTUSER>, that better matches the date I made and entered the payment, but I don't think that survives the import into Skrooge. I tried viewing the "Creation date" column, but that weirdly shows "Tomorrow" for the imported QFX operations (a bug?)

Quicken 2012 handles imported transactions differently. It seems to have more lenient matching that better matches up manual and imported transactions even if there's a date discrepancy, and it shows the imported transactions in a separate list showing either New or Match. After review you can "Accept" the downloaded transactions; the transactions that Match somehow get auto-merged. I think there's a way to hold back some transactions or edit them to increase the likelihood they match, but I've forgotten the details. I think all of these are better approaches than what Skrooge does. You could imagine Skrooge highlighting potential matches when you select an operation in "operations potentially duplicated" based on amount, date being "close" and maybe even Payee partial matches (e.g. "Mozilla Foundation" and "PAYPAL *MOZILLAFOUN" are the same operation). I think Quicken also only displays one date, as I recall it's also the posted date.

Thanks for any comments. Should I file some of these as enhancement requests?
User avatar smankowski
Moderator
Posts
945
Karma
7
OS
skierpage wrote:Hi. I entered a bunch of charitable donations into Skrooge, many made online with my credit card, on the same day that I donated. I then imported the QFX file from my bank for the same period, resulting in a lot of duplicate operations. So Go > Open potential duplicates... , however this does not show most of the duplicate pairs. I think I know why, elsewhere smankowski commented
The "Open potential duplicate" function opens a page with operations having same amounts and same dates.

(^ This information needs to go in the Skrooge handbook in both the menu description

You are right and I did it.
skierpage wrote:and the section on merge operations which doesn't mention the feature).

The merge function is something else. You can merge 2 operations having different dates and/or amount. So, I won't modify this chapter.
skierpage wrote:The problem is the date of the QFX transactions in Skrooge is the <DTPOSTED> from the QFX file, usually one or two days after the date that I made the payment. So none of the transaction pairs appear in "Operations potentially duplicated".

There's another date in the QFX file, <DTUSER>, that better matches the date I made and entered the payment, but I don't think that survives the import into Skrooge. I tried viewing the "Creation date" column, but that weirdly shows "Tomorrow" for the imported QFX operations (a bug?)

The creation date is the date when the operation has been created in Skrooge. This can help when you search the last added operation.
You are right , Skrooge uses date_posted instead is possible else date_initiated.
I can propose you to possible corrections:
1- Skrooge uses always date_initiated. To be honest, I don't remember why I used date_posted.
2- I add a new option in settings to choose which date to use.
skierpage wrote:Quicken 2012 handles imported transactions differently. It seems to have more lenient matching that better matches up manual and imported transactions even if there's a date discrepancy, and it shows the imported transactions in a separate list showing either New or Match. After review you can "Accept" the downloaded transactions; the transactions that Match somehow get auto-merged. I think there's a way to hold back some transactions or edit them to increase the likelihood they match, but I've forgotten the details. I think all of these are better approaches than what Skrooge does. You could imagine Skrooge highlighting potential matches when you select an operation in "operations potentially duplicated" based on amount, date being "close" and maybe even Payee partial matches (e.g. "Mozilla Foundation" and "PAYPAL *MOZILLAFOUN" are the same operation). I think Quicken also only displays one date, as I recall it's also the posted date.

Thank you for this request. I added it in my TODO list. https://phabricator.kde.org/T10793
skierpage wrote:Thanks for any comments. Should I file some of these as enhancement requests?
[/quote][/quote]


Skrooge, a personal finances manager powered by KDE
Image
User avatar smankowski
Moderator
Posts
945
Karma
7
OS
Do you have an answer concerning this?

The creation date is the date when the operation has been created in Skrooge. This can help when you search the last added operation.
You are right , Skrooge uses date_posted instead is possible else date_initiated.
I can propose you to possible corrections:
1- Skrooge uses always date_initiated. To be honest, I don't remember why I used date_posted.
2- I add a new option in settings to choose which date to use.


Skrooge, a personal finances manager powered by KDE
Image
User avatar skierpage
Registered Member
Posts
15
Karma
0
OS
smankowski wrote:
skierpage wrote:The problem is the date of the QFX transactions in Skrooge is the <DTPOSTED> from the QFX file, usually one or two days after the date that I made the payment. So none of the transaction pairs appear in "Operations potentially duplicated".

There's another date in the QFX file, <DTUSER>, that better matches the date I made and entered the payment, but I don't think that survives the import into Skrooge. I tried viewing the "Creation date" column, but that weirdly shows "Tomorrow" for the imported QFX operations (a bug?)


You are right , Skrooge uses date_posted instead is possible else date_initiated.
I can propose you to possible corrections:
1- Skrooge uses always date_initiated. To be honest, I don't remember why I used date_posted.
2- I add a new option in settings to choose which date to use.

Hmmm, I don't know. American Express has only DTPOSTED. It seems several VISA paper/PDF statements have both "Transaction date" and "Post date" columns, but only one of my banks supplies DTUSER as well as DTPOSTED in its QFX download. I think for that one bank DTUSER matches Transaction date. So I think the preference should be use DTUSER as the operation date if available, otherwise DTPOSTED, and document this in the handbook ;) . (I'm not sure what you mean by "date_initiated.") Adding an option to prefer one over the other might be more than necessary.

Thanks for caring!
User avatar smankowski
Moderator
Posts
945
Karma
7
OS
I already commited this correction: Use <DTUSER> if existing else <DTPOSTED>.
You should have it in Skrooge 2.19.0.


Skrooge, a personal finances manager powered by KDE
Image

 
Reply to topic

Bookmarks



Who is online

Registered users: adriannao, Baidu [Spider], Bing [Bot], claydoh, dimzev, Google [Bot], louis94, Majestic-12 [Bot], Snudl