The import parser checks whether a calendar date exists. A value such as April 31 remains invalid even when its year, month and day are in the selected order.
- Compare the raw date with the bank’s original transaction record or statement.
- Check whether the file’s date convention was reversed or a spreadsheet conversion altered the value.
- Repair the working copy only after identifying the actual source date, then read and preview it again.
An invalid date can also come from an account summary or identifier mapped as Date. Inspect the source column before assuming the bank recorded an impossible day.
Preserve the original evidence
Keep the untouched export alongside the corrected working copy. If you need support, provide the affected line number, raw date and expected date from the statement.
Do not round a nonexistent day down to the end of the month as a convenience. That can move the transaction into the wrong period. If the true date remains unknown, leave the row unresolved until the source can be confirmed, while continuing review of other valid rows where the workflow allows it.
Was this article helpful?
Tell us whether this answered the question you came with.