I am new to Tiller, and over the past week or so there are COUNTLESS duplicate transactions showing up, however they have different Transaction IDs. I am wondering if this is caused by one day Tiller imports all transactions including those Pending, and the next day it re-posts the transaction once it is cleared? Any tips on managing duplicates other than conditional formatting based on the transaction ID (which I’ve seen suggested elsewhere).
Are these all coming in from one bank?
Welcome to Tiller @william.caster.jr , that is indeed odd. We have the best customer service team who can help you with why this might be doing it.
I’d recommend reaching out to our support team via the chat window in the lower right corner of the Console at https://my.tiller.com/
-Alice
Tiller Evangelist
Yes all one bank and one credit card (separate institutions experiencing the same thing).
If you check the column to the right that tells you the date each record was brought in, are the duplicates all coming in on different days? Does it bring in a fresh round of duplicates if you refresh?
I saw this recently and there seemed to be a bug in the Google sheet connection and each refresh brought in new duplicates with new dates and different IDs. We started a new sheet and re-fed the data in, and that stopped the issue. There was some migration needed to copy over the Category and AutoCat sheets (and any other customizations) to the new Google Sheet unfortunately. We did abandon some historical data that had been categorized by hand to avoid spending too much time on it.
Most of them are coming in on DIFFERENT days, which is why I was thinking it was posted once when it was a pending transaction on my account, and again when it was cleared. Refreshing didn’t bring more duplicates back in, but didn’t remove the other ones. Would this bug be resolved by moving to a new spreadsheet or not?
Are you getting each transaction twice or more than twice?
I would first try feeding the trouble accounts to a new spreadsheet to see if you see the same behavior there or not to isolate where the error is originating from.
This is an issue with your data feeds that our team will need to troubleshoot. @TillerAlice shared how to reach us above, but here’s a guide on duplicates and how they happen.
1 Like