Is there a way to use transaction dates instead of posting dates on Tiller?

I searched the Tiller Community and this seems to be an already requested feature. My understanding is that both Tiller and Empower uses Yodlee. However, Empower uses the transaction date for each transaction while Tiller used the post date. I would like Tiller to also use the Transaction date. Is there a way to do this on Tiller without manually changing the dates for every transaction yet? Are you working on this feature?

I added a column for the transaction date on my Transactions sheet and have been manually entering dates. Would LOVE if that data could be captured automatically.

Great question. This would be a great update to have.

Yeah, this is a good idea. Transaction date would be preferable to post date even if it gets added to our sheets days later. It would save the exercise I do at the begging of every month to backdate things to the previous month when the expense was actually incurred.

I looked at Yodlee’s API documentation for the date field:

“The value provided will be either postDate or transactionDate. postDate takes higher priority than transactionDate, except for the investment container as only transactionDate is available. The availability of postDate or transactionDate depends on the provider site. Applicable containers: bank, creditCard, investment, insurance, loan.”

For something like a written check, a bank can only know the date the check was presented to be cashed. Yodlee and Empower will never know when the check was actually used as payment in a transaction.

I would like to have a separate transaction date column that would reflect my idea of the transaction date. Like Autocat for the category column, I want an Autodate to automatically generate a date (usually by copying the feed’s date column) to be edited as need be. My guess is that most transaction dates would be correct, and most of the remainder “close enough”. What I really need is a way to tell my reports to use this new column rather than the Date column in the feed.

This isn’t a feature we’re working on @kkapdolee and as @rdsteed noted we use “Date” and this is what it means:

“The value provided will be either postDate or transactionDate. postDate takes higher priority than transactionDate, except for the investment container as only transactionDate is available. The availability of postDate or transactionDate depends on the provider site. Applicable containers: bank, creditCard, investment, insurance, loan.”"

Thanks. May I ask why you aren’t working on this? Do you think postDate is better than transactionDate? Can we take a community vote on this?

Tiller is never going to be able to determine when a transaction occurred from your perspective. (See my earlier comment)

Many Tiller reports make use of the Date column. It would be possible to support a transaction date column as well.

Revising all of the reports (currently hard wired to for a column named “Date”) to also support a “TransactionDate” column as an option would require a significant effort, and it would still require manual editing of the Transaction Date.

I’ve requested that my Barclays Master Charge account send me an immediate email alert whenever my card is authorized. “Scraping” these messages allows me to record credit card transaction dates, which can later be pasted into the Transactions sheet. Those are the tDates I most care about.

Wouldn’t this be fairly straightforward to add? Yodlee provides both a postDate and transactionDate: Yodlee API v1.1 | Transactions Resource | Yodlee Developer Portal . You could have it so if the “Posted Date” and “Transaction Date” columns are present, you can fill them.

The only more difficult part would be if we could have an option to be able to set “Date” to prioritize the transaction date if present, and then whatever “date” is otherwise.

I find it really jarring that some of my credit cards show the posted date when it’s not when I actually made the purchase. Looking at Bank of America for example, they do provide both the posted and transaction date (But Date is filled as the posted date).

Straightforward is subjective :wink: but we’re taking this into consideration as we work through improvements, specifically to our Yodlee integration.

It would be help to allow the user to select the date type if both are available (perhaps at the account level). For a monthly spend or budgeting analysis - using Posted Date over Transaction Date doesn’t give an accurate picture of spending habits. I’m looking for this information primarily for credit card spend.

I really agree with @okratracks here. I understand if Tiller doesn’t want to change the default for the user, but being able to choose postDate or transactionDate on a per user or account basis would be very helpful. I have several accounts that have a postDate that is 1-2d late normally compared to the actual transactionDate, which is how I’d prefer to track my finances.

Furthermore, I think features like this are a strength of Tiller, helping deobfuscate these confusing APIs out there (Yodlee et al.) while helping us maintain the power of a spreadsheet. While I’m sure we cannot expect these banks and the APIs we use to surface all the data perfectly, when available it would be nice to add data that lets us model our finances the way we actually think about them.

Honestly, this kind of guided flexibility is exactly why I chose Tiller over the Mints and YNABs of the world. Those tools make the decision for you; a raw spreadsheet leaves you to figure everything out alone. Tiller’s sweet spot is curating a set of sane, well-considered options and then letting us customize further from there. Treating transactionDate as one of those first-class supported options, rather than something users have to work around, feels squarely in line with that philosophy.

Love the product :heart:

Thanks for the feedback and glad you’re loving it. If you haven’t already I recommend searching through the Feature Requests category to see if this already exists and vote for it, if not you can add it as a feature request. I can see this being handy for other folks as well.