Proof of Travel
In October 2025, Karin Lindqvist, a Swedish national booked on Lufthansa's ARN-FRA-EZE routing, was held at Frankfurt Airport check-in when the agent couldn't verify her departure documentation for Argentina. Her travel file included a valid Swedish passport, a confirmed inbound booking, and a Skyscanner itinerary export she intended as proof of onward travel. The Skyscanner document contained no PNR locator code. The agent queried it and found nothing in the GDS. She was referred to the duty supervisor.
The incident reflects a compliance gap that appears consistently among European travellers bound for Buenos Aires. This case study unpacks the document failures, the corrected filing, and the regulatory basis behind Argentina's enforcement practice.
The Document Gap: What Lindqvist Carried and What the Requirement Demanded
Argentina's Dirección Nacional de Migraciones enforces a departure-documentation requirement for most visa-exempt non-MERCOSUR nationals under Ley de Migraciones 25.871 and its implementing regulations. Carriers are instructed via IATA Timatic to verify proof of onward travel before boarding. Lufthansa applies this check at FRA for all EZE-bound passengers.
The following table sets out Lindqvist's initial document set against the compliance standard:
| Document field | Lindqvist's file | Compliance standard |
|---|---|---|
| Inbound booking | Confirmed Lufthansa PNR, GDS-verifiable | Compliant |
| Departure documentation | Skyscanner PDF, no PNR | Non-compliant |
| PNR locator present | No | Required |
| GDS-verifiable | No | Required |
| Name consistency | N/A (no PNR to check) | Must match passport exactly |
| Date within 90-day stay | N/A | Required |
| Document format | Fare comparison export | Confirmed booking required |
The compliance failure sat entirely at the departure document row. A Skyscanner export is a fare comparison output. It doesn't constitute a confirmed reservation and carries no booking reference resolvable in any carrier's global distribution system.
What Argentina Accepts as Valid Departure Proof
A dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without paying for the flight. This definition is the operational boundary between compliant and non-compliant documents.
The accepted departure document set for a visa-exempt non-MERCOSUR national includes:
- A confirmed onward flight with a live, GDS-verifiable PNR in the passenger's name
- A confirmed Buenos Aires-Montevideo ferry crossing (Buquebus or Colonia Express) with a verifiable booking reference
- A confirmed overland departure into Chile, Uruguay, or Brazil carrying a reference the officer can query
The following aren't accepted regardless of presentation format: fare-comparison exports, unconfirmed OTA holds, screenshot-based itineraries, or any document without a booking reference that resolves in the GDS.
The Corrected Document Set
The duty supervisor at FRA advised Lindqvist that she needed a confirmed booking reference before boarding could proceed. She used Proof of Travel's booking service to obtain a confirmed dummy ticket PNR, which was delivered by email within the hour. The corrected filing looked as follows:
| Document field | Corrected file | Status |
|---|---|---|
| Inbound booking | Confirmed Lufthansa PNR | Compliant |
| Departure documentation | Confirmed dummy ticket with live PNR | Compliant |
| PNR locator present | Yes, GDS-verifiable | Compliant |
| GDS-verifiable | Yes | Compliant |
| Name consistency | Matches passport exactly | Compliant |
| Date within 90-day stay window | Yes | Compliant |
| Document format | Confirmed booking confirmation | Compliant |
She caught the next FRA-EZE service without further disruption.
Carrier Enforcement Across Principal EZE Routes
Lindqvist's experience at FRA is consistent with enforcement patterns across all major European and North American hubs serving EZE. The table below summarises the principal carriers and their verification approach:
| Carrier | Departure hub | Route | Verification method |
|---|---|---|---|
| Lufthansa | FRA | ARN/various-FRA-EZE | Timatic at check-in |
| Air France | CDG | CDG-EZE | Timatic at check-in |
| British Airways | LHR | LHR-EZE | Timatic at check-in |
| Iberia | MAD | MAD-EZE | Timatic at check-in |
| KLM | AMS | AMS-EZE | Timatic at check-in |
| American Airlines | JFK, MIA | JFK/MIA-EZE | Timatic at check-in |
| LATAM | SCL, GRU | Regional to EZE | Internal system |
| Aerolíneas Argentinas | Various South American hubs | Regional to EZE | Internal system |
All six intercontinental carriers in this table reference the IATA Timatic system, which instructs them to confirm departure documentation before boarding for Argentina. LATAM and Aerolíneas apply equivalent checks on South American routes.
Three Compliance Principles for Argentina-Bound Travel
Three principles apply consistently across Argentina-bound routing compliance:
1. Departure confirmation requires a PNR. A fare-comparison export, search screenshot, or unconfirmed hold doesn't satisfy the requirement regardless of airline, date, or route shown. A PNR that resolves in the GDS is the minimum.
2. Payment isn't the variable. A dummy ticket doesn't require the traveller to pay for an actual flight. It requires a confirmed PNR that resolves in the GDS. That's what constitutes proof of onward travel under Argentina's entry framework.
3. The PNR must be live at the time of presentation. A booking with a past departure date, or one whose PNR has been cancelled, won't pass verification. See the onward ticket PNR validity case study for the document lifecycle and how long different booking types remain GDS-active.
For a comparable incident on a South American routing, the Colombia onward ticket compliance case study covers an analogous check-in hold on an Iberia routing through MAD and is useful context for multi-country South America trip planning.
Frequently asked questions
Does Argentina require a paid return ticket, or does a dummy ticket satisfy the requirement?
A dummy ticket satisfies the requirement. What Migraciones and carriers verify is a live PNR, not a payment record. A confirmed booking that resolves in the GDS is compliant whether the traveller paid the full fare or used a PNR booking service.
Can a non-MERCOSUR traveller enter Argentina without any departure documentation?
A traveller may pass the primary desk without being asked, but the requirement exists and carriers enforce it at check-in before boarding. Arriving at FRA, LHR, CDG, or AMS without departure documentation creates a boarding risk before the traveller reaches Argentina.
Does the departure booking need to be a flight, or will a ferry or bus ticket work?
A confirmed Buquebus or Colonia Express ferry crossing from Buenos Aires to Montevideo satisfies the requirement. A confirmed overland coach booking with a verifiable reference also works. The document must contain a booking reference an officer can query.
What constitutes a compliant PNR for Argentina departure purposes?
A PNR that's live (not cancelled or past its ticketed date), in the correct passenger name matching the passport, for a route departing Argentina within the authorised stay window, and verifiable in the GDS. A dummy ticket from a reputable booking service meets all four conditions.
What's the carrier's exposure if they board a passenger who is refused entry?
Under IATA Resolution 830d and Argentine Migraciones regulations, the carrier bears the cost of returning a refused passenger to the point of origin. That carrier liability is what makes check-in agents thorough about departure documentation for Argentina-bound flights.
To avoid the Frankfurt scenario, book a verified onward ticket with a live PNR before your next Argentina departure.