Consider a hypothetical applicant, Ilse Verhoeven, a Dutch freelance translator planning three weeks in Sri Lanka, landing at Bandaranaike International Airport (CMB) near Colombo. She holds a one-way flight, an approved online travel authorisation, and a hotel booking for four nights. She is missing one document. 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 case examines where that gap would surface.

The facts of the case

Ilse's file, as she assembles it before departure:

  • A passport with comfortable validity beyond her intended stay.
  • A travel authorisation obtained online before travel.
  • Four nights of accommodation confirmed, with the remainder undecided.
  • A one-way ticket to Colombo.
  • No booked departure from Sri Lanka.

Nothing in this file is improper. It is, however, incomplete in a way that carries consequences at two different checkpoints. The authorisation process and the airline operate independently, and approval at one does not bind the other.

The rules themselves vary by nationality and are revised from time to time. Ilse's first obligation is to consult the official source for her own passport. For US citizens, the Sri Lanka country page on travel.state.gov summarises entry conditions, and other governments publish equivalents. This article does not restate any specific rule as current, and it is general guidance, not legal or immigration advice.

Checkpoint one: the airline at the point of departure

The first test occurs not in Sri Lanka but at Ilse's departure airport. Airlines screen passengers against destination requirements, commonly using IATA's Timatic data. Where the data indicates that proof of onward or return travel is expected, the check-in agent asks for it.

An agent has a commercial reason to ask. A carrier that transports a passenger who is then refused entry can bear the consequences, and it doesn't take that risk lightly. For that reason the airline's position is often stricter than the officer's.

Ilse's one-way ticket is the fact pattern that triggers the question. She can answer it in two ways: by purchasing a refundable flight out, or by holding a reservation that resolves in the airline's system. The second route is the purpose of a dummy ticket. It must still be a live record, in her exact passport name, with a date consistent with her stay.

Checkpoint two: the officer on arrival

At Colombo, the officer's interest is different. They examine the passport, the authorisation, the stated purpose of the visit, and, where asked, the plan to leave. The question is rarely about the booking's fare status. It is about whether the traveller's account is coherent.

Document Airline at departure Officer at arrival
Passport and authorisation Verified against destination rules Verified and stamped
Onward booking Often requested, looked up live Sometimes requested, often just asked about
Accommodation Rarely requested May be asked for
Funds Rarely requested May be asked for

The table illustrates a pattern, not a guarantee. Practice varies by airline, airport and officer, and no checklist substitutes for the official instruction.

Where Ilse's file fails, and how to repair it

Three defects commonly arise in files like hers.

The booking lapses. An unpaid reservation is held on the airline's own timer. If Ilse books weeks ahead and does not look again, the record may have expired by check-in. The remedy is a check of the airline's manage-booking page on the day before departure. Our case study on how long an onward ticket PNR remains valid sets out the mechanics.

The name differs. The booking must reproduce the passport name exactly. Abbreviations, omitted middle names and transposed fields are the usual causes of a failed match.

The date contradicts the plan. If her stated stay is three weeks and the booking departs in four days, an officer will reasonably ask. If it departs after the period allowed, the booking offers no protection at all.

Variations worth noting

The same file looks different under other facts. Were Ilse arriving from a connection, with a second airline handling the final leg to Colombo, that carrier would apply its own check, and she would need the proof available at the transfer point as well as at origin. Were she holding a return ticket already, the onward question would not arise at all, and the booking would double as her evidence of departure.

Were she to leave by sea or by a later flight from a different city, the booking would serve as evidence of capacity to leave rather than a statement of the exact route. That distinction matters in conversation. A traveller who says, accurately, that the reservation demonstrates a means of departure and that the final route is undecided, presents a coherent position. A traveller who claims the route is fixed when it is not, creates a contradiction that can later be tested.

Record-keeping completes the picture. Ilse should retain the passport page, the authorisation, the accommodation confirmation and the booking reference in one place, accessible without a data connection. Each document answers a separate question, and the file is only as strong as its weakest member.

Documentary conclusion

Ilse's case turns on a simple principle: each checkpoint asks a different question of the same file. The airline asks whether the record exists today. The officer asks whether the story is consistent. A proper onward booking answers both, and an improper one answers neither.

For a wider treatment of what counts as acceptable evidence, see the document compliance case study on proof of onward travel.

Travellers who need a reservation that resolves on the airline's system can request an onward ticket through the booking page.