Embassy teams do not judge a flight reservation only by how attractive the PDF looks. They look at whether the route, dates, passenger details and booking reference make sense together. A reservation can look clean but still raise doubts if the airline record is missing, the travel dates clash with the visa form, or the route feels built only for paperwork.
Before submission, think like a verifier. Can the booking reference be checked? Does the itinerary match the purpose, appointment timing and planned return? Would a real traveler choose this routing? Does the PDF look system-generated and complete, not edited or cropped? These details decide whether the reservation supports the file or quietly weakens it.
- Passenger name matches the passport and visa form.
- Route supports the country, city and purpose of travel.
- Arrival and return dates match the cover letter and supporting documents.
- PNR or booking reference is easy to identify.
- Reservation status looks active and logical for the document type.
- PDF is complete, readable and not edited-looking.
Create Your Flight Reservation for Visa
How Embassy Verification Teams Read a Flight Reservation
A flight reservation earns trust when it behaves like part of a real visa file, not like a separate attachment added at the last minute. Verification teams usually start with one practical question: does this itinerary support the story the application is already telling?
A PDF is reviewed as evidence, not decoration
A polished PDF helps readability, but it does not make a reservation believable on its own. Verification teams are not checking whether the document looks attractive. They are checking whether the details stand up to basic review.
For a Schengen tourist visa, the reservation should support the main destination, entry plan and return intention. If the form says the applicant will spend most of the trip in France but the flight lands in Italy with no onward logic, the reservation creates friction. For a UK Standard Visitor visa, the itinerary should support a temporary visit. A one-way arrival with no return or onward journey may invite closer review unless the situation explains it.
- Who is traveling.
- Where the trip begins.
- Where the traveler will enter.
- When the traveler plans to arrive.
- When the traveler plans to leave or travel onward.
- Which airline and flight numbers are involved.
- Which booking reference can be checked.
If any of these details are hidden, unclear or inconsistent, the reservation becomes harder to trust. A decorative layout cannot fix a missing booking reference. A clean logo cannot fix a route that contradicts the visa form.
Passenger identity is the first credibility layer
Passenger identity is the first place where small mistakes become visible. Embassy teams may compare names across the passport, visa form, appointment confirmation, travel insurance, invitation letter and flight reservation. A small mismatch can slow review even when the trip itself is valid.
The reservation should follow the passport name, not a casual name. Name order can vary by airline system, but the names should be complete and recognizable. Problems begin when a surname is missing, a middle name disappears, or the order makes the passenger look like a different person.
Applicants with long names, multiple surnames, compound names, patronymics or special characters need extra care. Airline formatting may simplify some characters, but identity should remain obvious. Families and groups should check every traveler, not only the main applicant.
This matters across many visa routes. A UAE resident applying for a Schengen visa from Dubai should make sure the reservation matches the passport and residence permit. An Indian applicant applying for a Canadian visitor visa should not use a shortened office name on the reservation if the visa form uses the full passport name. A family applying together should check children’s names, spouses’ surnames and passenger order carefully.
Before submission, compare the reservation against the passport biodata page directly. Do not rely on memory. Check spelling, sequence, title and every traveler included in the file.
A PNR must survive basic verification
A booking reference or PNR gives the reservation practical weight because it connects the PDF to a booking record. Embassy teams may not check every PNR, but the reservation should be ready if they do.
The code should not feel like random text placed on a document. It should relate to the airline, route, passenger name and travel dates shown on the PDF. If the PNR produces no recognizable itinerary, shows different dates, or appears disconnected from the airline listed, the reservation loses strength fast.
Timing matters here. If the reservation is created too early, it may not remain visible long enough. If it is created too late, the applicant may miss a mismatch. The safest approach is to review the PNR close to submission and confirm the PDF still matches the booking details.
A verification-friendly PNR does not need to expose every airline-system detail to be useful. Some systems show limited fields. Some show only surname and route. Others show flight numbers, baggage notes or booking status. That is normal. The important part is that the visible record does not contradict the visa file.
If the PDF shows Delhi to Paris from 4 May to 15 May, the PNR should not open a different city pair or a different date range. If the passenger name on the reservation is Maria Lopez, the record should not point to another passenger. If the route includes a return segment, that segment should remain visible where it matters.
The trip should make sense without a long explanation
A genuine-looking flight reservation should make sense quickly. The route should not require a long explanation before it feels believable. For a Spanish tourist visa, a reservation from Lahore to Madrid with a clear return two weeks later is easy to understand. A route that jumps across unrelated cities without support may still be valid travel, but the visa file must explain it.
The same applies to business travel. If the invitation is for a three-day meeting in Berlin, a 28-day stay across several countries needs supporting context. Transit choices matter too. Real travelers use layovers, but avoid routes that create unnecessary transit or immigration questions.
A simple test works well: could someone understand the trip in five seconds? Origin, destination, purpose, arrival, return. If the answer is yes, the reservation is doing its job.
For family visits, the reservation should respect the host location and invitation period. For student or exam travel, it should sit close to the official dates. For medical travel, it should support the appointment window and practical recovery time. Each purpose has its own normal rhythm, and the flight reservation should match that rhythm.
A route can be unusual and still valid, but unusual details need support. A return from a different city, a long layover, a multi-country route or a departure airport far from the applicant’s residence should not appear without logic somewhere in the file.
The Flight Reservation Details That Must Match Across the Visa File
A flight reservation does not sit alone in a visa application. It is checked against the dates, purpose, route and personal details declared elsewhere. If one part of the file says one thing and the reservation says another, the issue becomes credibility, not just a flight detail.
Compare the reservation against the visa form
The visa form is usually the main reference point. The flight reservation should support that form, not compete with it. If the form says the applicant arrives in Paris on 12 July, the reservation should not show Amsterdam on 10 July without a clear reason. If the form says the trip is eight days, the reservation should not quietly show a 17-day stay.
- Full passenger name.
- Date of birth, if shown.
- Passport number, if shown.
- Arrival date.
- Departure date.
- Destination country.
- First entry airport.
- Return or onward flight.
- Trip duration.
- Booking reference or PNR.
If the passport says “Jonathan Michael Carter,” the visa form should not say “John Carter” while the reservation says “Jonathan M. Carter.” Some differences may be explainable, but clean consistency is stronger. If the reservation includes date of birth or passport number, those fields should match exactly.
The same principle applies to destination and trip duration. If the visa form lists Italy as the main destination but the reservation only shows Spain, the file needs a clear travel plan connecting those details. If the form asks for intended arrival and departure dates, the reservation should support those dates or explain any overnight-flight difference.
Do not treat the reservation as a last-page attachment. Treat it as a document that will be compared against every major claim in the application.
Arrival and departure dates must support the travel plan
Flight dates should match the purpose of the trip. The arrival date should make sense for when the activity begins. The departure date should make sense for when the activity ends.
For a conference, arriving one or two days early can be reasonable. Arriving three weeks early needs support. For a family visit, the dates should match the invitation and host availability. For a short tourist trip, the dates should fit the applicant’s profile, leave approval and funds.
The return or onward journey is especially important. For short-stay visas, it helps show a planned exit. If the application depends on temporary stay intent, the reservation should show where the trip ends.
Before submission, place travel dates side by side: visa form, flight reservation, invitation or event date, leave approval, travel insurance, accommodation and return date. The dates do not always need to be identical, but they must make practical sense together. If the flight arrives one day before hotel starts, explain the gap. If insurance ends before the return flight, fix it. If leave approval ends before the applicant returns, the file becomes harder to trust.
Date alignment is one of the simplest ways to make a flight reservation for visa look genuine. It tells the reviewer that the document was built for the real file, not copied from an old plan.
The route must align with the country being requested
The route should support the country where the applicant is applying, especially when the visa type depends on entry, stay or main destination. For Schengen visas, the reservation should support the main destination or first entry logic. For single-country visas, the route should be even cleaner.
If the applicant applies for a UK visitor visa, a flight into London and return from London is easy to understand. A route into another country with unclear movement to the UK creates extra questions. For Canada, Australia, New Zealand, the United States and other long-haul destinations, the route should look like a realistic travel pattern.
Transit countries can also affect credibility. If the itinerary creates a possible need for transit permission, the embassy may notice. A route that creates extra immigration complications can weaken an otherwise clear file.
Flight and accommodation should also align. The flight should not show arrival in Lisbon while the first night of stay is in Vienna without an internal travel explanation. The same applies to departure: if the return flight leaves from a different city, the itinerary should show how the applicant gets there.
A strong route usually answers three questions quickly: why this entry airport, why this embassy or country, and how the return or onward flight shows that the trip ends as claimed.
Passport validity and flight dates can quietly create doubt
Passport validity is easy to overlook. If the passport expires too close to the return date, the reservation may draw attention to a separate problem. Some countries expect passport validity beyond the planned stay. Transit countries may also have their own expectations.
If the reservation includes passport details, they must match the current passport exactly. This matters after passport renewal, name changes or family applications. A wrong passport number can make the booking look disconnected from the applicant’s identity.
If the applicant recently renewed a passport, confirm the reservation uses the new document. If an old passport number appears anywhere in the file, correct it. A reservation with the old passport number can look like a booking for a different identity, even when the traveler is the same person.
Passport validity also interacts with route. A transit point may have its own passport-validity expectations. A multi-country route may require the passport to satisfy more than one control point. The flight reservation should work with the passport, not expose a practical travel problem.
PNR and Airline-System Signals That Make a Reservation Easier to Verify
A flight reservation becomes stronger when the details on the PDF can be checked against a booking record. For embassy verification teams, the PNR is the bridge between the uploaded document and the reservation record.
What a verification-friendly PNR should show
A verification-friendly PNR should connect clearly to the trip shown in the visa file. When checked, the visible details should support the same passenger, route, dates and airline information shown on the reservation PDF. The display does not need to look identical across every airline website or booking platform, because systems vary. The core details should not conflict.
- Passenger name.
- Departure and arrival airports.
- Flight date.
- Airline name.
- Flight number.
- Booking status.
- Return or onward segment.
- Reservation reference.
If the visa file shows Emily Carter traveling from Delhi to Rome from 10 August to 22 August, the PNR should not show a one-way flight from Mumbai to Milan on 14 August. Even if both routes involve Italy, the mismatch creates confusion.
Do not confuse airline codes with agency references
Many flight documents show more than one code: airline PNR, booking reference, reservation number, agency reference, order ID, invoice number or internal tracking code. These codes are not always equal.
An agency reference may help the provider locate the order. An invoice number may support payment. But embassy-style verification usually needs a code connected to the airline or booking record. If the PDF contains several codes, the checkable booking reference should be easy to identify.
Do not manually edit codes into a PDF. Any edited-looking reference can damage trust. The booking reference should appear naturally within the reservation details.
The problem is not having multiple codes. The problem is unclear labeling. If the PDF shows “Reference,” “Order ID,” and “Reservation Number,” the most useful code should be obvious. A reviewer should not have to guess which number connects to the itinerary.
For multi-airline routes, display differences are normal. One airline may show limited details while another shows the full itinerary. The reservation should still make the booking reference and route logic clear enough for basic review.
Reservation status affects confidence
Reservation status tells the reviewer whether the booking still exists in a useful form. Wording may vary: booked, confirmed, held, reserved, active or pending ticketing. The wording should make sense for the type of reservation. If the embassy asks for a reservation, a booked or held itinerary with a real PNR can support the purpose without requiring a paid ticket unless the checklist specifically asks for one.
The status should also match what appears when the booking reference is checked. If the PDF says confirmed but the record shows cancelled, the document loses credibility. If the PDF shows one route but the PNR opens a different route, the status no longer helps.
A vague status can create uncertainty. If the PDF says only “itinerary created” but does not show a booking reference, airline, flight number or booking state, it may feel more like a travel plan than a reservation. That distinction matters when the file relies on travel proof.
Status also matters for the return or onward segment. If the outbound segment appears but the exit segment is missing or unclear, the reservation may not support temporary-stay intent as strongly.
A realistic hold window is stronger than a dead booking
A reservation can look perfect on paper and still fail its purpose if it is no longer checkable. The PDF may have clean formatting, correct dates and a visible PNR, but if the booking record has disappeared before review, the document becomes weaker.
Consider the appointment date, upload deadline, biometrics date, expected review timing, weekends, holidays and visa-center transfer time. Create or refresh the reservation close enough to submission while leaving time to review every detail.
This is especially relevant where documents move through an external visa center before embassy review. The file may be collected on Monday but reviewed later. A reservation that expires too quickly may not support the file during the actual verification window.
A perfect-looking dead booking is not helpful. Embassy teams care more about whether the reservation can be checked and understood than whether the PDF looks visually premium.
Route Choices That Make a Flight Reservation Look Like a Real Travel Plan
A reservation looks more believable when the route feels like something a real traveler would choose. The strongest route is usually simple, explainable and aligned with where the applicant lives, where they are going and why they are applying.
Departure airport should match the applicant’s real location
The departure airport should fit the applicant’s actual starting point. If the applicant lives in Delhi and the employment letter, bank statement and address proof all place them in Delhi, a Delhi departure is easy to read. A Mumbai departure can also make sense if the file explains why.
Applicants living outside their passport country need even more care. If a Canadian citizen lives in Dubai and applies for a French visa from the UAE, the flight reservation should usually start from Dubai or Abu Dhabi unless the file clearly explains a different route.
The issue is not that applicants must always fly from the nearest airport. Major international airports, better connections, family positioning, work travel or airline availability can explain a different departure city. The key is that the file should not leave the reviewer wondering why the journey begins somewhere unrelated to the applicant’s residence story.
Students, temporary workers and residents abroad should use the current residence context, not only nationality. If the application is filed from the UAE, Singapore, the UK or Canada, the reservation should usually reflect that current travel base unless the cover letter explains otherwise.
Layovers and transit countries affect credibility
Direct flights are easy to understand, but layovers are not a problem by themselves. Real travelers use connecting flights because of price, route availability and airport access. The concern begins when the layover makes the route feel forced or creates additional transit complications.
A Delhi to Paris flight through Doha or Dubai can look normal. A short tourist trip to France with multiple unrelated stops across distant regions may feel less natural. If the route creates extra immigration or transit questions, it may distract from the main visa purpose.
Transit questions become more sensitive when the applicant has limited travel history or a tight visa timeline. If the route requires changing airports, collecting baggage, staying overnight or meeting separate transit rules, the reservation should not create a hidden travel obstacle.
A simple connection is usually stronger than a clever route. The flight reservation for visa should help the officer understand the trip, not ask them to solve a routing puzzle.
Return flights matter even when a paid ticket is not required
Many visa systems do not require applicants to buy a paid ticket before approval, but a return or onward reservation can still support temporary stay intent. The exit segment helps show that the trip has an endpoint. It should match the cover letter, leave approval, funds and intended stay.
If the return date sits far beyond the stated purpose, the reservation may weaken the file. If the application says a ten-day visit but the reservation shows five weeks, the officer may question which trip is real.
The return segment should also be easy to find. If the PDF hides the return leg on another page, uses unclear formatting or shows only outbound travel, the document may not support the exit plan clearly enough. A genuine-looking reservation makes the planned departure from the destination visible.
Multi-city reservations can help or hurt
Multi-city travel can be valid for tourism, business, family or Schengen trips, but the documents must explain movement. Hotels, internal travel, invitation addresses and final departure should all support the route. A complicated route without evidence can look built for the visa file instead of a traveler.
For Schengen trips, multi-city logic should be especially clean. The main destination, first entry and exit country should make sense together. If the applicant applies through France, enters Italy, stays longest in Germany and exits Spain, the travel plan must make that sequence understandable. Otherwise, the reservation may create questions about where the application belongs.
For business travel, multi-city movement should follow meetings or company activity. For family visits, it should follow host locations. For tourism, it should follow a believable travel pace. A route can be complex, but it should not feel random.
- Departure city fits residence or work location.
- Arrival city fits the first real destination.
- Transit does not create avoidable visa questions.
- Return or onward segment supports temporary stay.
- Multi-city movement is explained by the itinerary.
- The route looks like something a real traveler would choose.
Date Strategy for Embassy Timing
Date strategy is where many weak reservations fail. The reservation date, appointment date, intended departure, expected processing time and return date should all work together.
The reservation date should not fight the appointment date
If the reservation is created too early, it may not stay active long enough. If it is created too late, the applicant may not have time to fix errors. The best timing is close enough to submission to remain relevant and early enough to review calmly.
For applicants with visa-center appointments, the reservation should be fresh around appointment day. For online portals, it should match the final upload. For courier submissions, it should still make sense when the file is delivered. Timing should follow the document path.
Travel dates should reflect realistic processing time
A departure date immediately after the appointment can look unrealistic unless the purpose is urgent and supported. The applicant needs time for decision, passport return, final ticketing and travel preparation. A strong reservation respects that sequence.
Urgency can be real: medical appointments, exams, business events or family emergencies may require tight timing. But urgency should be documented. Without a clear reason, a departure date too close to submission can make the file look rushed.
Stay length should match the applicant’s profile
A long stay can be valid, but it needs support. A full-time employee with ten days of approved leave should not show a 30-day stay without explanation. A family visit can be longer when the invitation, funds and home obligations support it. A business trip should follow the event schedule.
Stay length also affects funds and accommodation. A reservation showing a longer trip implies higher travel cost, more nights, longer insurance coverage and more time away from home. If the supporting documents do not carry that burden, a shorter and clearer reservation may look more genuine.
Date changes should be managed cleanly
If the appointment, invitation, hotel, insurance or travel purpose changes, update the reservation and related documents together. Do not submit a new flight reservation with an old cover letter. Do not upload multiple conflicting reservation versions.
Version control matters. Keep one final reservation for submission. Remove older PDFs from the upload folder or printed document pack. If a new reservation is created after a date change, check that the visa form, cover letter and insurance now match the new timeline.
PDF Presentation Details That Help a Reservation Feel Verifiable
Presentation does not replace verification, but it affects how easily the document can be reviewed. A good PDF should be clean, complete and readable without looking manually edited.
The PDF should be clean without looking edited
Verification teams may notice cropped screenshots, mismatched fonts, pasted codes, inconsistent spacing or missing sections. A professional reservation should look system-generated. It should not look like a screenshot stitched together or a PDF manually altered to fit the application.
Clean does not mean overdesigned. A simple, readable reservation is stronger than a heavily decorated document with unclear fields. The document should make verification easier, not distract with unnecessary design.
Important fields should be easy to find
The first page should make the important details visible quickly: passenger name, route, dates, airline, flight numbers, booking reference and return or onward segment. If the reviewer has to search for every field, the document feels weaker.
If the reservation spans multiple pages, the first page should still establish the core trip. Supporting pages can show segments or conditions, but the reviewer should not need to hunt for the passenger identity or travel dates.
Screenshots and cropped itineraries look weaker
A full reservation PDF is usually stronger than a cropped screenshot because it preserves context. Screenshots can hide important details, cut off return segments or make the document look assembled rather than issued.
Cropped documents are also harder to compare against the visa form. If the booking reference, return segment, date line or passenger name is partly cut off, the reservation may look incomplete even if the original booking is valid.
File naming and upload quality matter
Use a clean file name and confirm the uploaded PDF opens correctly. If the portal compresses or crops the document, check readability. The booking reference, name and route should remain visible after upload.
Good file names reduce accidental upload mistakes. Use one final version and avoid confusing labels such as “reservation-new-final-final2.” For printed files, keep the reservation with the visa form, cover letter and itinerary so the timeline is easy to follow.
Red Flags That Make a Flight Reservation Look Fabricated
Red flags do not always prove fraud, but they create doubt. A professional flight reservation for visa should avoid avoidable signals that make verification harder.
PNR cannot be found or shows different details
If the booking reference cannot be connected to a recognizable itinerary, or if it shows different passenger, route or date details, the reservation becomes difficult to trust. Always check the PNR before submission where checking is available.
A missing record may happen for several reasons, including expiry, cancellation, wrong code or checking through the wrong channel. Whatever the cause, the result is the same: the reservation becomes harder to rely on. If the booking cannot be checked and the visa file depends on it, refresh or correct the document before submission.
The reservation contradicts the applicant’s own story
If the cover letter says a short conference trip but the reservation shows a long unexplained stay, the file creates its own doubt. If the form says one arrival city and the reservation shows another, the officer must interpret the mismatch.
Contradictions are more damaging than missing detail because they ask the reviewer to choose between two versions of the trip. The flight reservation should reduce interpretation, not create it.
The route looks built for paperwork, not travel
A route with unnecessary backtracking, strange transit, unsupported city changes or unrealistic layovers can look like a document created to satisfy a checklist rather than a real travel plan. Choose the route a real traveler would reasonably use.
This is especially important for applicants from high-scrutiny profiles. When the rest of the file already needs to prove credibility, the route should be disciplined. Simple, logical and supported usually wins over complicated.
The reservation looks reused, altered or too generic
Old templates, generic formatting, missing passenger details, cropped screenshots or edited-looking codes can weaken trust. The reservation should look specific to the applicant and trip.
Reused-looking documents are risky because they suggest the reservation was not created around the actual travel plan. A genuine-looking reservation should reflect the applicant’s name, route, dates and purpose clearly enough that it feels file-specific.
Final Pre-Submission Audit
Before upload or appointment day, run the reservation through a final audit. The goal is not to overcomplicate the file. The goal is to remove obvious verification problems before someone else finds them.
Five-minute identity check
Compare the reservation with the passport biodata page and visa form. Check full name, spelling, name order, date of birth if shown, passport number if shown, and every traveler in a family or group file.
If the reservation includes a title, gender marker or date of birth, check those too. Small identity differences can create more friction than applicants expect, especially when the file is reviewed quickly.
Route-and-date cross-check
Compare arrival, departure, destination, stay length, insurance, accommodation, invitation, leave approval and cover letter. If any document gives a different timeline, fix it or explain it clearly.
Use the visa form as the anchor. The reservation should support the form, and the supporting documents should support both. If the form was updated after the reservation was created, check the flight dates again.
PNR verification check
Check that the booking reference is visible and logically connected to the itinerary. If multiple codes appear, identify the one that matters. Make sure the route and dates on the PDF match what the record supports.
If the reservation status is no longer useful, refresh before submission. If the PNR display is limited but still supports the core route and passenger, the document may still be usable. The key is whether it creates confidence or confusion.
Real-traveler test
Ask whether the itinerary looks normal for the applicant’s purpose, profile, budget and destination. If the route needs a long explanation to make sense, simplify it or support it better.
This test catches problems that technical checks miss. A reservation can have the right name and PNR but still look weak if the trip itself feels unrealistic. Embassy verification is not only about codes. It is also about whether the document supports a believable travel plan.
- Name and passport details are correct.
- Route matches the country and purpose.
- Dates match the form and cover letter.
- Return or onward journey is visible where needed.
- Booking reference or PNR is easy to find.
- PDF is complete and readable.
- No old or conflicting version remains in the file.
Submit a Flight Reservation That Can Stand Up to Embassy Review
A genuine-looking flight reservation is not loud. It is clean, consistent and easy to verify. It confirms the applicant’s identity, supports the visa route, respects the dates in the file, shows a clear return or onward plan and avoids unnecessary document friction.
BookForVisa is built for applicants who need a professional flight reservation for visa that fits the file they are actually submitting. Prepare the route and dates first, check the supporting documents, then use a reservation that makes the travel plan easier for embassy teams to understand.
Create Your Flight Reservation for Visa
Frequently Asked Questions
What makes a flight reservation look genuine to embassies?
It looks genuine when passenger identity, route, travel dates, booking reference or PNR, reservation status and PDF presentation all support the same visa file.
Does a flight reservation need a PNR?
A booking reference or PNR makes the reservation easier to verify and more useful. The code should connect logically to the passenger, route and dates shown in the visa file.
Can a clean PDF still look weak?
Yes. A polished PDF can still look weak if the PNR cannot be checked, dates conflict with the visa form, or the route does not match the travel purpose.
What details should match across the visa file?
The passenger name, passport details if shown, arrival date, return date, destination, route, stay length and cover-letter explanation should all match or be clearly explained.
Is a return flight important for embassy review?
For short-stay visas, a return or onward segment often helps show that the trip has a planned exit. It should match the stated stay length and supporting documents.
What makes a reservation look fabricated?
Red flags include an unfindable PNR, conflicting flight details, edited-looking codes, cropped screenshots, generic templates, wrong passenger details or a route that contradicts the application story.
Can BookForVisa prepare a genuine-looking reservation?
Yes. BookForVisa can prepare a professional flight reservation for visa aligned with your intended route, travel dates and supporting document timing.
Does a genuine-looking reservation guarantee visa approval?
No. It supports the travel-plan evidence, but approval depends on the full application, including eligibility, purpose, funds, ties and officer assessment.
Friendly reminder: BookForVisa provides temporary travel-proof documents for planning and visa application support. Requirements vary by embassy, visa category, route and applicant situation. A flight reservation for visa can support a file, but it does not promise approval, boarding or entry.
