Imported bank transaction dates do not match the date of the transactions in the bank

Thank you for raising your concern about the date differences between your downloaded transaction data and what appears on your bank statement.
​
You may notice that some transaction dates in your downloaded data are different from what you see on your online banking or statements. This is not an error in our system, but rather a result of how banking data is structured and shared.
​
Why This Occurs
​
Banks use two different date types for transactions:
• Booking Date - When the transaction is officially recorded in the bank's system.
• Value Date - When the money actually becomes available or unavailable in your account.
​
Our system receives the booking date through secure open banking standards, whilst your bank displays the value date on your statements and online banking. This can create date differences between the two.
​
This is standard behaviour across the banking industry when using open banking APIs. The open banking regulations require us to use the booking date, as this is the mandatory field that all banks must provide consistently.
​
What This Means for You
Your transaction data remains accurate - it's simply using a different (but equally valid) date reference point.
​
Example
If the transactions in your bank have a date in January, but the transaction dates imported are in December. You would reconcile these transactions in December.