mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-10 04:02:38 -05:00
[Bug]: Importing CSV fails to parse date in specific account only #2831
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2831
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cjfagerstrom on GitHub (Jan 17, 2026).
Verified issue does not already exist?
What happened?
I have confirmed with two different CSV files that I can import the data into other accounts, but there is one specific account that fails to parse the date and says that field is empty and will not import the CSV data. Sample CSV attached.
Problem account:
Testing importing transactions to another account:
How can we reproduce the issue?
Unsure - haven't seen the issue and seems to be isolated to a specific account.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Brave
Operating System
MacOS
@db-src commented on GitHub (Jan 18, 2026):
At the risk of asking a silly question, did you actually select the columns to look in for each field, in real use? Because in your "Problem account:" screenshot, you have not, but in the "another account" screenshot you did.
Actual remembers this per account after you've done it, hence why your other accounts work, but you have to do it the first time for any given account.
@matt-fidd commented on GitHub (Jan 20, 2026):
I imagine @db-src is correct here, make sure the CSV import settings are correctly configured
@cjfagerstrom commented on GitHub (Jan 21, 2026):
Yes, I did. This is what I got when I tried to import the file. My initial suspicion is that it's failing because I just created this account, but I'm trying to import data with dates that pre-date the initial creation date of this account.
However, it does not appear to be in issue with the initial creation date of the account as a test with a future-dated transaction failed to import with the same error.
@matt-fidd commented on GitHub (Jan 21, 2026):
@cjfagerstrom it looks like you're using the incorrect date format. You're using
MM/DD/YYYYbut your data is inMM/DD/YY(2 digit year) format.@cjfagerstrom commented on GitHub (Jan 21, 2026):
@matt-fidd Then why does it import into other accounts?
@cjfagerstrom commented on GitHub (Jan 21, 2026):
Oh wait - I see what you're saying. I've never adjusted that field to my recollection, but it's possible I did a long time ago.
@matt-fidd commented on GitHub (Jan 21, 2026):
In your other account
In your failing account
@cjfagerstrom commented on GitHub (Jan 21, 2026):
Yeah - I just saw that. I've honestly never noticed that field. I don't remember adjusting it on the other accounts, and I created 3 other accounts at the same time and when I check the other 3, they all defaulted to YY. Only this one went to YYYY.
@StephenBrown2 commented on GitHub (Jan 22, 2026):
Actual will try to figure out the right format for the file you import the first time, and then save that format for later, so you probably didn't do it manually, but at least first tried importing a file with that format to that account.