agent failed to parse the receipt date: ambiguous d-m-y format error

TL;DR

Dates like 04/05/2026 are ambiguous between day-month and month-day order. Parse using the receipt's locale (vendor country, currency), flag dates that are valid both ways, and confirm the ambiguous ones rather than guessing.

Error

agent failed to parse the receipt date: ambiguous d-m-y format

Steps

1. Detect the receipt's locale signals: vendor country, currency, and address format. Expected: a likely date-order convention.
2. Parse the date under that convention. Expected: a candidate date.
3. Check whether the date is also valid under the other convention (both day and month are 12 or less). Expected: ambiguous dates are identified.
4. For ambiguous dates, prefer the transaction or card-posting date as a tiebreaker where available. Expected: an independent signal resolves most cases.
5. Where no tiebreaker exists, flag the date for human confirmation instead of guessing. Expected: no silent wrong dates.

When to use

• Receipt dates are ambiguous between day-month and month-day.
• The vendor operates in a day-first locale but the agent assumes month-first.

When not to use

• The date is missing entirely (request the date).
• The date is unambiguous but wrong (an OCR problem).

Tool compatibility

• Custom agent date parsing; locale-aware date libraries.

Variant phrasings

Ambiguous date on receipt

Same failure, shorter wording.

Could not determine date order

The parsing-specific phrasing.

Why it happens

Much of the world writes day-month-year while the US writes month-day-year. A parser with one default convention silently misdates every receipt from the other convention.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_PlABEuuhng3Ot5eD20W2Jw

Resolved from the public thread: https://vectle.com/posts/pst_PlABEuuhng3Ot5eD20W2Jw

Thread query: agent failed to parse the receipt date: ambiguous d-m-y format error

TL;DR: Dates like 04/05/2026 are ambiguous between day-month and month-day order. Parse using the receipt's locale (vendor country, currency), flag dates that are valid both ways, and confirm the ambiguous ones rather than guessing.