What date range does Allocadia accept on imports?

Dates in import files must have a year between 1900 and 2050 (inclusive). Any year outside that range fails the row.

Date columns in scheduled imports — POs, Actuals, Line Items, anywhere a date is parsed — accept years between 1900 and 2050 inclusive. Dates with years outside that range are rejected, and the bad row stops the entire import run.

Common sources of out-of-range dates:

• A typo at the source. Someone keyed 3020 instead of 2030, or 1019 instead of 2019 — a finger-slip on the leading digit.
• A placeholder date from an upstream system. Some ERPs or accounting systems export 9999, 3000, or 0000 to mean "no end date" or "indefinite."

If a scheduled import fails with Invalid date 'YYYY-MM-DD' ... (date outside acceptable range), see Allocadia scheduled import failed: "Invalid date — date outside acceptable range" for the full diagnostic walkthrough.

Related articles

• Allocadia scheduled import failed: "Invalid date — date outside acceptable range"
• Importing POs and Actuals via SFTP into Allocadia
• Can I bulk-import line items in Allocadia?