Renate Fischer, a German marketing consultant en route from Munich to Phnom Penh via Kuala Lumpur, reached the AirAsia check-in desk with a printed PDF she believed was her onward ticket. It was a fare comparison page, generated by a travel search site, showing a flight that had never been booked. The agent could not locate a passenger name record for it in the reservation system, and Fischer was held at check-in until she produced a genuine booking. A dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without paying for the flight. Fischer's document was not that. It was a screenshot dressed up as one.

Cambodia is not the strictest entry regime in Southeast Asia, but its requirement for proof of onward or return travel is standard, and the gap between what travellers believe satisfies it and what a reservation system can actually verify is where most compliance failures originate. I have reviewed enough of these cases to say the pattern rarely changes: the document looks convincing to the traveller and resolves to nothing the moment anyone queries it.

The document gap

The table below sets out what Fischer presented against what Cambodia's entry conditions, and the airline's own check-in requirements, actually call for.

Field Fischer's document What Cambodian entry conditions require
Passenger name record Absent Present, matching passport identity
Bookable in a GDS No Yes, queryable on request
Travel date Listed, but not held Within the permitted 30-day stay
Payment status Irrelevant to the check Irrelevant; the ticket need not be paid
Issuing entity A comparison website An airline or authorised travel agent
Route validity Plausible on paper Must correspond to an operating service
Verifiability at the desk None Immediate, on query

Six of seven fields failed. Notably, payment status is not one of the failures. Cambodian immigration, like most border authorities operating this kind of rule, does not care whether the onward ticket has been paid for in full. It cares whether the record exists and resolves.

What a compliant document looks like instead

Field Compliant onward ticket
Passenger name record Matches passport exactly
Bookable in a GDS Yes
Travel date Within Cambodia's permitted stay, typically 30 days on the e-visa
Payment status Not required to be paid; a held reservation suffices
Issuing entity Airline, authorised agent, or a service producing a genuine PNR
Route validity Corresponds to an actual scheduled service
Verifiability at the desk Confirmed by GDS query in seconds

Once Fischer replaced the comparison-site PDF with a genuine reservation, the second check-in attempt resolved in under a minute. Nothing about the underlying requirement changed. Only the document did.

Where enforcement actually sits

Cambodia's own immigration checks are not the primary enforcement point in most cases like this. Carrier liability is. Under the industry framework airlines operate within, a carrier that boards a passenger later refused entry at the destination bears the cost of returning them, so check-in staff have a direct financial incentive to verify onward travel before departure, regardless of how strictly the destination border itself enforces the rule.

Enforcement point Frequency of check Basis
Departure check-in (any carrier) Frequent Carrier liability for denied entry
Phnom Penh / Siem Reap / Sihanoukville immigration Occasional National entry conditions
Poipet / Bavet land crossings Inconsistent Same conditions, lighter enforcement
Smaller land crossings (e.g. Cham Yeam) Rare, visa-on-arrival status checked more closely Same conditions

Our broader analysis of country-by-country onward ticket border checks covers how this enforcement pattern, airline first, border second, holds across most of the region, not just Cambodia.

The three principles this case illustrates

A confirmed PNR is required, not a paid ticket. A comparison-site printout or unpaid airline hold that has expired will not resolve when queried, and both fail for the same underlying reason: nothing exists in the system to find. Third, timing matters as much as existence; a booking dated outside the permitted stay can raise questions of its own, even when it's otherwise genuine.

None of this requires legal advice or a travel agent's intervention to get right. It requires a document that exists in a system someone can query. If you'd rather not assemble one from a comparison site by mistake, you can book a real onward ticket in two minutes and remove the ambiguity entirely.

For readers tracking how long a booking like this stays valid before departure, our PNR validity compliance case study addresses the shelf life question directly. IATA's Timatic compliance reference and the UK government's foreign travel advice for Cambodia are both primary sources worth consulting ahead of a trip, and neither is a substitute for checking current requirements directly before travel.

Frequently asked questions

Why did the airline check Fischer's ticket rather than Cambodian immigration?

Because carrier liability places the cost of a denied entry on the airline, not the destination country. Check-in is frequently the first and most consistent enforcement point.

Does it matter that Fischer's ticket had not been paid for?

No, and this is a common misunderstanding. Payment status is not the variable being checked. Existence and verifiability in a reservation system are.

Would a different document, such as a hotel booking, have satisfied the requirement?

No. Accommodation does not demonstrate onward travel, which is specifically what the entry condition addresses.

Is Cambodia's enforcement consistent across all its airports and land borders?

No. Airport check-in tends to be the most consistent point of enforcement; land crossings are comparatively inconsistent and vary by individual officer.

What is the minimum a traveller needs to avoid Fischer's situation?

A confirmed reservation, under the traveller's own name, dated within the permitted stay, and verifiable on query. It does not need to be a paid ticket.