Skip to main content

Dates from transaction fields to support date accurate transactions

Feature Request

Some banks do not properly support sending transaction dates as each transaction happened.

There are 4 different dates from the bank: valueDateTime, ValueDate, booking Date Time, and bookingDate. The expectation is that value date matches when the transaction happened, and booking date matches when the bank confirmed it. Sadly, there is nothing forcing the bank to share value dates over the open banking api's, so some banks don't.

The good news is that transaction fields will have an accurate date which can be extracted.

Imagine you wanted to record buying an engadgement ring for your partner and you really bought it on a Friday however the export to Lunch Flow has a date of Monday which is clearly not accurate.

Posted by Daniel ·
Status: Completed2 comments

Log in to comment and vote

Comments2

  • Amr from Lunch Flow changed status to Completed
    Team•

    Dec 22, 2025

    Pinned

    Hey 👋

    Wanted to share an update: you can now configure whether to use booking or value dates on individual accounts 😄

    Feel free to give it a try, and as always, keep the feedback coming!

  • Amr from Lunch Flow

    •

    Aug 29, 2025

    Hey @Daniel ,

    Just capturing our Discord discussion here.

    This has only come up in Tesco bank from GoCardless so far, so if you’re open to reconnecting your Tesco bank, I can ask the GoCardless team to check and perhaps fix this so the dates come through the expected fields in their response schema.

    If we find this is happening more often, or there’re GoCardless limitations to them fixing this, happt to look into the fix of making this dynamic as you proposed.