Proof of Travel
Consider a traveler booked on a one-way flight to Bali who tries to check in online the night before departure. The airline's system flags the booking and asks for proof of onward travel before it will issue a boarding pass. This is the moment a dummy ticket, also called an onward ticket, is supposed to solve: a real PNR booked for visa or border-check purposes without paying for the flight. When that PNR won't verify on the airline's own site, the traveler is left with hours, not days, to fix it.
This is a document problem, not a travel problem, and it has a fairly narrow set of causes. Understanding which one applies determines whether the fix takes five minutes or requires a new booking entirely.
Why airline verification systems reject a valid-looking PNR
Airlines don't manually review every onward-ticket screenshot. Most rely on automated document-and-entry-requirement checks, and many carriers reference IATA's Timatic database to determine what a passenger needs to show for a given destination and nationality combination. A booking can look complete to a human and still fail that automated check for reasons that have nothing to do with whether the flight exists.
The most common causes fall into a few buckets:
| Symptom | Likely cause | Typical fix |
|---|---|---|
| PNR not found on airline site | Booked through a different carrier or a consolidator/GDS the airline's own portal doesn't query | Verify directly through the operating carrier, not the booking agent |
| PNR found but marked "unconfirmed" | Reservation is a hold, not a ticketed booking | Confirm ticketing status with the issuing agent before travel |
| Name mismatch error | Passport name doesn't match the name on the reservation exactly | Correct the booking name to match the passport, including middle names |
| Booking shows as expired | Reservation hold period lapsed before departure | Rebook closer to the travel date |
| System shows no record at all | Booking reference or airline code entered incorrectly | Recheck the confirmation code against the original booking email |
A name mismatch is worth flagging on its own, since it's the cause travelers are least likely to expect. Immigration and check-in systems generally match against the passport exactly, including middle names and diacritics, so a booking made through a third party with a slightly different name format can fail verification even though the reservation itself is entirely valid.
What a valid onward-ticket PNR actually needs to contain
For the booking to hold up at check-in or at a border desk, it generally needs a confirmed status rather than a hold, a name matching the traveler's passport, a route consistent with the visa or entry requirement being satisfied, and a travel date that hasn't lapsed. Missing any one of these is usually what triggers a rejection, even when the underlying reservation is genuine. This is also why a document that looks fine on a phone screen can still fail: the airline's system is checking structured fields, not a rendered PDF.
Step-by-step: what to do when verification fails
- Confirm which system is rejecting the booking. A failure on the airline's own manage-booking page is different from a failure at the physical check-in desk, and the fix depends on which one it is.
- Recheck the booking reference and the airline code separately. A single transposed character in either field produces a "not found" result that looks identical to a genuinely invalid booking.
- Contact the issuing agent or the airline actually operating the flight, not the airline whose logo appears on the itinerary if it was a codeshare. Verification against the marketing carrier's site sometimes fails even when the operating carrier's system shows the reservation correctly.
- If the reservation has lapsed or was never ticketed, treat it as gone rather than salvageable. Rebooking is usually faster than trying to resurrect an expired hold.
- Keep the confirmation email and a screenshot of the booking record as a backup, separate from relying on the airline's live lookup tool, in case the system is temporarily unavailable rather than genuinely rejecting the document.
Airlines retain broad discretion here. Lufthansa's general conditions of carriage state that the airline may refuse transport if a passenger cannot produce the documents required for entry, transit, or exit at the relevant destination, which extends to onward-travel proof where the destination country requires it.
When the airline is right and the booking really is the problem
Not every rejection is a system glitch. If a booking was never actually issued a ticket number, or if the hold period quoted at the time of booking has passed, the airline's system is correctly identifying a document that won't hold up further down the line either, at immigration or during a visa interview. In that case, the honest fix is a new confirmed booking, not repeated attempts to force the same reservation through.
It's worth being direct here: no amount of resubmitting a failed screenshot fixes a reservation that was never ticketed in the first place.
Preventing the problem before departure day
Most verification failures are avoidable with a small amount of lead time. Book the confirmed PNR early enough that a name correction or a reissue is still possible before travel, rather than the night before. Match the reservation name to the passport at the moment of booking, not after a rejection forces the issue. And reconfirm the record once, close to the travel date, rather than assuming a booking made weeks earlier is still sitting there untouched.
That last point matters more than it sounds. Bookings are not static. Reservations move through GDS systems on their own internal timelines, and a status that was fine two weeks ago is not a guarantee of a status that holds today. A five-minute recheck the day before travel catches almost everything on the symptom table above.
None of this replaces reading the specific destination's entry requirement. A booking that verifies perfectly can still fail to satisfy a country's actual rule if the route or dates don't match what that country asks for. Verification and compliance are related questions, not the same one.
Frequently asked questions
Can I use the same onward ticket for both the airline check-in and a visa application?
Often yes, provided the booking stays confirmed and the travel date remains valid through both uses. Check the reservation's hold or expiry terms before relying on it twice.
Does a screenshot of a booking work if the airline system can't find it live?
Sometimes, but it's the weaker option. A live-verifiable PNR is generally more reliable than a static image, since staff can be asked to look up the record directly.
Will a codeshare flight number cause verification problems?
It can. Checking against the marketing carrier's booking tool instead of the operating carrier's system is a common cause of a "not found" result.
Travelers who want to see how border officers approach this same verification question from the other side can review our compliance case study on verifying an onward ticket PNR, and the Emirates check-in document review walks through one carrier's specific process end to end.
None of this needs to become a last-minute scramble. Book a confirmed onward ticket that verifies cleanly on the airline's own system before departure day arrives.