On a receipt from many European countries 07.08.26 is read day first, so 7 August 2026, but the same digits on a slip from a US vendor can mean July 8. Decode the pattern before you enter the date: note the separator, check which number can exceed 12, and then write the date in your own log as year, month, day.
What patterns will you meet on a multi-country trip?
Travelling by rail through three countries in a week, you will see several styles in your pile. The table lists the ones that cause trouble, using the same hypothetical day, 7 August 2026, so you can see how each looks.
| Style on the receipt | How it is usually read | Risk |
|---|---|---|
| 07.08.26 | Day, month, two-digit year | Low in day-first countries, high if the vendor is American |
| 08/07/2026 | Month first for US vendors, day first elsewhere | High: both numbers are 12 or lower |
| 2026/08/07 | Year, month, day | Low, but a few systems print year, day, month |
| 7 Aug 2026 | Month spelled out | None |
| 07-08-26 14:35 | Date with 24-hour time | Same date risk, but the time helps |
Does the 24-hour clock help or hurt?
It helps once you notice it. A receipt time-stamped 00:20 belongs to the night after the day your itinerary shows, so an entry dated 7 August at 00:20 may have been paid after midnight on the 6th. Compare with a hotel or train booking: if your sleeper train left at 22:40 on the 6th and the snack receipt says 00:20, it was bought on the 7th.
What is the two-digit year trap?
A date like 07.08.26 has three numbers that can all be 12 or below on a few days of the year, and a sheet may read the last one as a day. When you copy dates by hand, always expand the year to four digits, and read the receipt aloud as you type it: seven, August, twenty twenty-six.
A worked example: three cities, one week
Say you spend €64.50 on a train ticket, €38.20 on dinner and €12.80 on museum entry. The sum is €115.50. The three slips read 04.09.26, 09/04/26 and 2026-09-05. Your itinerary says you left on 3 September and returned on 6 September. The first reads 4 September, because day-first fits the itinerary. The second, 09/04/26, would be 9 April read day-first, which is far outside the trip, but September 4 read month-first, which is inside it, so that vendor used month-first order. The third is unambiguous, 5 September.
- Entry 1: 2026-09-04, train, €64.50.
- Entry 2: 2026-09-04, dinner, €38.20, flagged because the printed date was ambiguous.
- Entry 3: 2026-09-05, museum, €12.80.
How do you confirm a doubtful date?
- Compare with your itinerary or booking emails.
- Sort the pile by the order you actually spent and see whether the dates run forwards.
- Match the amount against your card statement and treat its posting date as a range, since it can lag the purchase.
- If two readings still fit, write both in the note and mark the line to check.
What if the month is written in another language?
A month name in a language you do not read is easy to misjudge, because abbreviations in different languages can look alike while naming different months. When you are not certain of a word, trust the digits you can read and check them against your itinerary instead of guessing from how the word looks. Keep a note in the line, such as month word unclear, and revisit it when you are home and can look it up properly.
Closing habit
Keep one rule for your records: year-first dates with dashes, the original currency amount, and the euro amount charged. SpendixAI can store a different currency on each expense with totals in a base currency, but it is built around India and INR, so treat that as an idea to copy in your own sheet rather than a service for European accounts.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

