How Is Guest Identity Notification Done in Hotels?

A guest has arrived at the hotel.

Reception took their ID.

Entered their record into the PMS.

Gave them their room.

The guest went up to the room.

Is the check-in complete?

From an operational standpoint, largely yes.

But from the official-process standpoint, it may not yet be complete.

Because in accommodation facilities in Turkey, guest registration is not just a record made in the hotel's own PMS or reservation system.

There is a separate legal obligation to report the identity and arrival-departure details of guests to the relevant law enforcement system.

This system is generally run through:

KBS — the Identity Notification System (Kimlik Bildirim Sistemi)

So from the hotel's perspective, the real check-in chain should be thought of as:

Reservation
↓
Guest arrival
↓
ID check
↓
PMS record
↓
KBS notification
↓
Room handover
↓
Changes during the stay
↓
Check-out
↓
Departure record

The basic principle here is this:

A PMS record and an official identity notification are not the same transaction.

Hotel management needs to make these two systems work in harmony with each other.

1. Why Do Hotels Make Guest Identity Notifications?

The core legal framework in Turkey is Identity Notification Law No. 1774.

The Law imposes obligations concerning the recording of the identity details of people staying in places of accommodation such as:

• hotels,
• motels,
• inns,
• guesthouses,
• camps,
• campsites,
• holiday villages

and similar.

This scope does not include only Turkish citizens.

The notification system applies to people staying at the facility, whether:

local or foreign.

In addition, the distinction between paid and free accommodation does not remove the obligation.

So situations like:

"This guest isn't paying"

or

"The hotel owner's guest"

should not automatically be treated as outside the registration obligation.

The basic logic is that the answer to:

Who is staying at the facility?

is recorded accurately and kept current.

2. What Is KBS?

KBS is the abbreviation of Kimlik Bildirim Sistemi (the Identity Notification System).

It is the system that allows accommodation facilities to report the relevant identity and accommodation details to law enforcement units electronically.

That is why it is not right to see KBS as:

"Just another program at reception."

KBS is actually one of the hotel's legal compliance systems.

The PMS is the hotel's operating system.

KBS is the official notification system.

The two serve different purposes.

3. What Is the Difference Between PMS and KBS?

This distinction is especially important for new hotel investors.

PMS — Property Management System

Manages the hotel's operations such as:

• reservations,
• rooms,
• rates,
• folios,
• check-in,
• check-out,
• housekeeping,
• guest profiles.

KBS — the Identity Notification System

Used to report to the law enforcement system the information required under legislation about the people staying.

So:

Recording the guest in the PMS = making the KBS notification

is not the case.

However, in well-built hotel technology, the data flow between the two systems can be made as automatic and controlled as possible.

4. Identity Notification Is Not Just a Reception Job

At first glance, because the transaction is done at reception, responsibility seems to belong to the reception department.

But the whole system involves:

• hotel management,
• front office,
• the night shift,
• IT/PMS,
• KVKK (data protection),
• operating procedures.

For example, if a receptionist enters the wrong passport number, the problem is operational.

If the KBS connection isn't working, the problem may be technical.

If staff forget to notify, the problem is training.

If unauthorized staff can see guest identity details, the problem is data security.

So:

The KBS transaction is done at reception; the KBS system must be set up by management.

5. Set Up the KBS Process Before the Hotel Opens

After the guest has arrived at the door, you shouldn't start researching:

"How did we connect to KBS?"

KBS preparation should be in the pre-opening checklist.

Before opening, at least the following should be completed:

• the process with the facility's relevant law enforcement unit,
• responsible operator/manager details,
• required user and system access,
• computer and internet infrastructure,
• PMS integration, if there is one,
• the reception procedure,
• user permissions,
• test transactions.

The first real guest should not be the system test.

6. Resolve the Responsible Operator Issue Before Opening

Under Law No. 1774, there is also a notification obligation concerning the responsible operators of accommodation facilities.

That is why, before the facility opens, the answer to:

Who is this business's responsible operator?

should be clear.

If the responsible person later changes in the business, this too must be notified according to the relevant procedure.

So a change of general manager or operations manager is not only a matter of:

• internal company matters,
• payroll,
• the organization chart.

It may also require some official records to be updated.

7. Distinguish the Police Zone from the Gendarmerie Zone

Not all hotels in Turkey fall under the responsibility area of the same law enforcement unit.

A facility may be in:

a police jurisdiction

or

a gendarmerie jurisdiction.

That is why one of the first questions before opening should be:

"Which law enforcement unit is competent for our facility's identity notifications?"

This distinction matters particularly for facilities operating in rural or tourist regions.

The relevant system access and method of application should be set up correctly according to the law enforcement jurisdiction in which the facility is located.

8. Don't Enter Identity Details by Guesswork

The basis of the guest record is accurate identity information.

For Turkish citizens, the required information is taken from the identity document.

For foreign guests, the required information is recorded from the passport or the relevant travel/identity document.

With foreign guests in particular, it is possible for fields such as:

• first name,
• surname,
• birth details,
• nationality,
• passport/document number

to be entered incorrectly.

For example, characters like:

0 / O

1 / I

can easily be confused.

That is why reception staff should enter data in a controlled way from the document rather than going by:

"The guest told me, I typed it."

9. Registering Foreign Guests Requires More Care

The name structures of foreign guests visiting Turkey don't always resemble Turkish identity structures.

For example, there may be:

• multiple given names,
• multiple surnames,
• different alphabets,
• different passport formats.

In the gendarmerie KBS facility application, separate data entries are provided for foreign guests, such as entering the full identity details and using the passport serial number in the document serial number field.

That is why, in hotels with a high proportion of foreign guests, front-office training must cover this subject specifically.

10. The Booking Holder and the Person Staying Are Not the Same Thing

This is a very important operating rule.

The reservation on Booking.com may have been made by:

Ahmet Yılmaz

But the room may be occupied by:

Ahmet Yılmaz + Ayşe Yılmaz

The booking may even have been made by a company.

Or the reservation may have been created by a tour operator.

From the KBS perspective the key question is not:

Who made the reservation?

but:

Who is actually staying at the facility?

So the registration process for the people staying in the room must be carried out correctly.

11. If Two People Stay in the Same Room, Register Both Guests

For example:

Room 101

is a double.

The reservation was made in one person's name.

Two people arrived at check-in.

Taking only the booking holder's ID details is not an adequate operating approach.

All the people staying need to be included in the required registration and notification processes.

That is why the reception SOP should include the check:

"Compare the number of people on the reservation with the number actually staying."

12. Don't Assume Child Guests Are Outside the System

One common mistake in family bookings is registering only the adults.

Yet, for people actually staying at the facility, age on its own should not be used as an assumption that removes the registration obligation.

The documents and data method to be used for registering children should follow the relevant current practice.

So when the PMS shows:

2 adults + 1 child

but KBS has only two people, that is an inconsistency to be checked.

13. Don't Forget Guests Staying for Free

For example, the following may be staying free of charge:

• a friend of the hotel owner,
• an influencer,
• a journalist,
• an agency representative,
• a complimentary guest,
• a staff member's relative.

No invoice being issued, or the room rate being zero, does not mean:

the person is not staying at the hotel.

The logic of the identity notification system should be thought of in terms of accommodation, not payment collection.

14. Assess Day-Use Separately Too

Some hotels may offer:

• day-use rooms,
• shower/changing rooms,
• short-term room use.

The gendarmerie's current KBS facility application includes a system for notifying, with a "day use" option, people who use the facility on a daily basis without renting a room.

So an automatic assumption like:

"They didn't stay the night, no notification needed"

should not be made.

If the business has a day-use model, the KBS procedure should be clarified before opening.

15. Make Notification a Part of the Check-In Operation

The safest method is not to leave KBS as:

"A job to do when there's time at night."

The ideal operation can be built like this:

Guest arrives
↓
ID is taken
↓
Document is checked
↓
PMS record is made
↓
KBS transaction is completed
↓
It is verified
↓
The room moves to active occupancy

That way, the risk of forgetting decreases.

16. The "We'll Send Them All in a Batch at Night" Logic Is Risky

When the hotel is busy, reception staff may say:

"Let's just enter them in the PMS for now, we'll do KBS at night."

This method creates operational risk.

Because at night:

• shifts can change,
• staff can forget,
• the system can fail,
• an ID may be missing,
• the room may have changed,
• the guest may have left early.

The gendarmerie's current KBS technical documentation states explicitly that, under normal conditions, the person staying must be entered into the system at the moment they check in to the facility.

So the most correct system is:

To tie the guest's entry to real-time notification as far as possible.

17. Don't Mistake the 72-Hour Technical Allowance for a Normal Operating Rule

In the KBS technical application, because of technical glitches, entries may be allowed retroactively within a certain period.

But this is not an operating standard of the kind:

"It's fine if we notify within three days."

Technical tolerances like this should not replace the normal workflow.

The hotel's procedure should be built on:

notification at the time of entry.

A technical fault should be managed as a separate exception procedure.

18. Create a Separate Procedure for Group Arrivals

Imagine a 30-person tour group arrives.

The coach is at the door.

The guests are tired.

Everyone wants a room key at the same time.

Reception doing every record one by one at that moment can gridlock the operation.

In the KBS system, there may be arrangements that allow advance notification for confirmed group arrivals whose details are already available.

That is why creating a:

Group Arrival SOP

is very valuable in group hotels.

For example:

T-24 hours

Rooming list check.

T-6 hours

ID/data check.

Arrival

Matching documents to people.

After check-in

PMS ↔ KBS reconciliation.

19. The Room Number Must Be Correct

An identity notification is not only the information:

"This person is in the hotel."

Other information related to the accommodation operation matters too.

That is why, when a room change is made, you shouldn't say:

"PMS updated, done."

You should also check how the change is to be handled on the KBS side under current practice.

Night-time room changes in particular can be a source of errors for this reason.

20. Don't Forget the Check-Out Transaction

The identity notification system is not only an entry notification.

Law No. 1774 provides for the keeping of the arrival and departure records of people staying.

So the system should not work as:

There is a check-in
but
no check-out.

When the guest leaves, the PMS and KBS records must be consistent.

21. Update the Systems Together for Early Departures

The guest's booking may be for:

10–14 August

But they may leave on 12 August.

If the reservation was closed in the PMS on 12 August, the departure record on the KBS side must also reflect the real situation.

The same applies to operations such as:

• extending a reservation,
• early departure,
• room change.

That is why the front-office SOP should include the check:

PMS change → is there a KBS impact?

22. Don't Process a No-Show Guest as a Staying Guest

There is a reservation.

The guest did not arrive.

This person is:

the reservation holder

but

not a person staying at the hotel.

So reservation data and actual accommodation data must not be mixed up.

This distinction matters for the accuracy of both the PMS and the official notification system.

23. Don't Skip the Process for Walk-In Guests

With guests who arrive without a reservation, reception may want to act quickly.

For example, the approach of:

"The room is empty, let them go up first, we'll take the ID later"

is not right.

The standard check-in procedure should also be applied to walk-in guests:

ID → registration → notification → payment/guarantee procedure → room handover.

24. Even with PMS–KBS Integration, Set Up a Control Mechanism

Some hotel software can offer integrations that make KBS transactions easier.

This is a major operational advantage.

But:

Automation does not remove responsibility.

An integration may have failed to send a transaction because of:

• a connection error,
• a missing field,
• wrong data,
• a system outage.

That is why, in the system:

Sent

and

successfully accepted

should not be treated as the same thing.

Where possible, successful/failed notification status should be tracked.

25. Carry Out a Daily PMS–KBS Reconciliation

There is a very effective check in this system.

Every night or at end of day, you can compare:

the number of in-house guests in the PMS

with

the active guest records in KBS.

For example:

PMS:

18 rooms / 31 guests

KBS:

30 active guests

One person is missing.

This is where the system should raise an alarm.

So the daily check question should be:

"Is everyone physically in the hotel right now correctly registered in KBS?"

26. Add a KBS Check to the Night Audit

The night audit is not only a check of:

• folios,
• the cash register,
• POS,
• room rates,
• revenue.

An official-record check can also be carried out on the front-office side.

For example, a Night Audit Checklist:

• ☐ Today's check-ins are complete.
• ☐ KBS notifications are complete.
• ☐ There are no failed notifications.
• ☐ Room changes were checked.
• ☐ Early departures were processed.
• ☐ The in-house headcount matches.
• ☐ Foreign guest records were checked.
• ☐ Check-out records are complete.

This small check can prevent serious compliance errors.

27. Decide in Advance What You Will Do If the System Goes Down

The internet is down.

KBS can't be reached.

The PMS integration isn't working.

What will you do?

The answer to this question should be written before the incident happens.

A KBS Outage Procedure can be created.

For example:

1. The time of the outage is recorded.
2. The guest's required details are taken securely.
3. The PMS record is completed.
4. The technical problem is reported to IT/the manager.
5. When the system is back up, pending notifications are sent.
6. Successful transmission is checked.
7. The outage record is closed.

That way, a system failure does not turn into an uncontrolled excuse of:

"KBS wasn't working."

28. Don't Open KBS Transactions to Every Employee

Identity details are sensitive operational data.

So not all hotel staff need access to KBS or PMS guest profiles.

Authorization should be done on the principle of:

access as required by the role.

For example, housekeeping staff do not need to see a guest's passport number.

Neither does technical service.

So:

What matters is not whether an employee can access the information, but whether they actually need it.

29. Don't Confuse ID Photocopying with KBS

This distinction is very important.

The hotel having an obligation to report identity details to the official system does not mean:

the right to photocopy an identity document without limit or to store its image.

Identity notification is a separate legal obligation.

The processing and storage of personal data must be assessed separately under KVKK.

That is why a hotel should not collect more data than necessary by saying:

"We need it for KBS."

We will cover this subject in detail in the next article:

17. How Should Guest Data Be Managed in Hotels under KVKK?

30. Don't Keep Passport Images on Phones

A risky practice can be seen in small hotels in particular:

Reception staff photograph the passport with a personal phone.

Then they send it to a WhatsApp group.

Later it is entered into the PMS.

This method can create a serious data security risk.

Guest identity data should not be held uncontrolled:

• on personal phones,
• in WhatsApp groups,
• in folders everyone can access,
• in open documents on the reception desk.

The operation may be fast.

But data security can be lost.

31. Don't Leave ID Documents on the Reception Desk

During a busy check-in, the following can be left stacked on the reception desk:

• passports,
• ID cards,
• registration forms.

This can lead to:

• documents getting mixed up,
• being handed to the wrong person,
• unauthorized people seeing the details.

That is why data security should be considered even in the design of the reception.

The guest's ID should be handled in the flow of:

take → check → process → return securely.

32. OCR Can Be Useful in Hotels with a High Proportion of Foreign Guests

In city and boutique hotels with many foreign guests, manually entering passport details can create:

• lost time,
• typing errors,
• queues.

A suitable PMS and secure ID/passport reading systems can make it easier to transfer fields such as:

• name,
• date of birth,
• passport number,
• nationality.

But when choosing the technology, not only speed but also:

• data security,
• KVKK,
• integration,
• access permissions,
• retention policy

should be assessed.

33. Don't Lose Control While Shortening Check-In Time

In modern boutique hotels, one of the goals is fast check-in.

The guest:

doesn't want to wait 10 minutes at reception.

That's right.

But skipping the identity notification process in the name of speed is not right.

With good technology:

speed + accuracy + compliance

can be achieved at the same time.

For example:

Pre-arrival data
+
passport/ID reading
+
PMS integration
+
KBS integration
+
automatic checks

can shorten check-in time significantly.

34. Create a Responsibility Matrix for KBS

For example:

In a small boutique hotel, two people might do all of these tasks.

That's no problem.

What matters is:

that it is clear who does which check.

35. Create a KBS Compliance File

I recommend having a small Identity Notification Compliance File in the hotel.

Section 1 — Facility

• relevant law enforcement details,
• facility registration details,
• responsible operator details.

Section 2 — System

• KBS access details,
• PMS integration details,
• authorized users.

Passwords should not be kept openly in this file.

Section 3 — SOPs

• check-in,
• foreign guests,
• groups,
• day-use,
• room change,
• early departure,
• system outage.

Section 4 — Controls

• daily reconciliation,
• error logs,
• corrective actions.

Section 5 — Training

• front-office training,
• new staff orientation,
• update training.

This structure provides operating discipline more than it serves inspection.

36. Manage the Identity Notification Process with Decision Gates

We can apply the decision gates system we use in this series to KBS as well.

Decision Gate 1 — Facility

Is our competent law enforcement unit clear?

Yes → Move on to KBS setup.

No → First verify the police/gendarmerie jurisdiction.

Decision Gate 2 — System

Are KBS access and the technical infrastructure working?

Yes → Move on to the PMS process.

No → Complete it before taking the first guest.

Decision Gate 3 — Guest

Who is actually staying?

Clear → Move on to the ID check.

Unclear → Don't settle for the booking holder; identify the real occupants.

Decision Gate 4 — Identity

Were the required identity details taken correctly?

Yes → Move on to registration.

No → Complete the details.

Decision Gate 5 — PMS

Was the guest recorded correctly in the PMS?

Yes → Move on to KBS.

No → Fix the PMS record first.

Decision Gate 6 — KBS

Was the notification completed successfully?

Yes → Move on to the room/stay check.

No → Resolve the error or apply the outage procedure.

Decision Gate 7 — Change in Stay

Has there been a change in room, dates, or stay status?

No → Proceed.

Yes → Check the impact on PMS and KBS.

Decision Gate 8 — Check-Out

Has the guest really left?

Yes → Complete the departure records.

No → Keep the stay active.

Decision Gate 9 — End of Day

Do the PMS and KBS records match?

Yes → Close the Night Audit.

No → Find the difference and fix it.

Decision Gate 10 — Data Security

Is only authorized staff accessing identity data?

Yes → Continue ongoing monitoring.

No → Fix the permissions and data flow.

This last gate never closes as long as the hotel is open.

37. 15 Common KBS Mistakes Made in Hotels

1. Mistaking the PMS record for the KBS notification

The two systems get confused.

2. Registering only the booking holder

Other people staying in the room are forgotten.

3. Assuming children are outside the system

The actual number of occupants doesn't match.

4. Not reporting free guests

Payment is confused with accommodation.

5. Leaving KBS transactions to the night

Notifications get forgotten.

6. Mistaking the technical tolerance for the normal notification period

The exception becomes daily practice.

7. Entering foreign passport details incorrectly

The identity data is wrong.

8. Making room changes only in the PMS

The systems drift apart.

9. Forgetting early departures on the KBS side

Active stay records get corrupted.

10. Not preparing for group arrivals

Reception gridlocks and the error rate rises.

11. Trusting the integration 100 percent

Failed notifications go unnoticed.

12. Not doing a daily reconciliation

Gaps are noticed days later.

13. Giving KBS access to unnecessary staff

A data security risk arises.

14. Circulating passport photos on WhatsApp

Control of personal data is lost.

15. Not providing KBS training when staff change

The operation becomes dependent on individuals.

38. Hotel KBS Checklist

Before Opening

• ☐ The competent law enforcement unit has been identified.
• ☐ The responsible operator notification has been assessed/completed.
• ☐ KBS registration is complete.
• ☐ User access has been created.
• ☐ The PMS integration, if any, has been tested.
• ☐ The internet infrastructure has been tested.
• ☐ A backup internet connection has been considered.
• ☐ Reception computers are ready.
• ☐ The KBS SOP is ready.
• ☐ Staff have been trained.

Check-In

• ☐ The people actually staying have been identified.
• ☐ ID/passport has been checked.
• ☐ Details have been entered correctly.
• ☐ The PMS record is complete.
• ☐ The KBS notification has been made.
• ☐ Successful transmission has been verified.
• ☐ The room number is correct.
• ☐ The stay dates are correct.

Special Cases

• ☐ There is a foreign guest procedure.
• ☐ There is a child guest procedure.
• ☐ There is a complimentary guest procedure.
• ☐ There is a day-use procedure.
• ☐ There is a group arrival procedure.
• ☐ There is a walk-in procedure.
• ☐ There is a room change procedure.
• ☐ There is an early departure procedure.
• ☐ There is a stay extension procedure.

System Outage

• ☐ There is an outage procedure.
• ☐ The outage time is recorded.
• ☐ Pending notifications are listed.
• ☐ They are sent once the system is back.
• ☐ A success check is carried out.

Check-Out

• ☐ The actual departure time has been checked.
• ☐ The PMS record has been closed.
• ☐ The KBS departure has been completed.
• ☐ Early departures have been updated.
• ☐ Extensions have been updated.

End of Day

• ☐ The PMS in-house list has been pulled.
• ☐ KBS records have been checked.
• ☐ Headcounts have been compared.
• ☐ Missing notifications have been checked.
• ☐ Erroneous records have been checked.
• ☐ The Night Audit checklist is complete.

Data Security

• ☐ KBS access is role-based.
• ☐ User accounts are personal.
• ☐ Access for departing staff is closed.
• ☐ ID images are not stored without control.
• ☐ Personal phones are not used.
• ☐ IDs are not shared over WhatsApp.
• ☐ No open ID documents are left at reception.
• ☐ PMS access is role-based.
• ☐ Consistency with the KVKK system is checked.

39. The Right Guest Identity Notification Flow

Let's summarize the whole process in a single flow:

Reservation
↓
The guest arrives at the facility
↓
Identifying the people who will actually stay
↓
ID / passport check
↓
PMS record
↓
KBS notification
↓
Successful notification check
↓
Room handover
↓
Tracking changes during the stay
↓
Room change / extension / early departure check
↓
Check-out
↓
KBS departure record
↓
Daily PMS – KBS reconciliation
↓
Night Audit
↓
Correcting errors and gaps
↓
Record and access security
↓
Continuous compliance

The basic principle here:

Manage the actual stay, not the reservation.

Conclusion

Guest identity notification is one of those hotel processes that looks small but does not tolerate errors.

The transaction may technically take a few minutes.

But behind it are:

Identity Notification Law No. 1774
+
KBS
+
PMS
+
front-office operations
+
law enforcement notification
+
KVKK
+
information security.

That is why saying:

"Reception already does it"

is not enough.

In a well-run business, the process depends not on a person but on a system.

When a receptionist leaves, the KBS system must not break.

When the night shift changes, a notification must not be forgotten.

When the internet goes down, it must be known what to do.

When a group of 30 arrives, reception must not gridlock.

A foreign guest's passport details must be entered correctly.

A room change must not remain different in the two systems.

And at the end of the day, management must be able to answer this question:

"Is everyone actually staying in my hotel right now correctly registered?"

If you can confidently say yes to this question, the system is working.

I sum up the identity notification system in hotels with this equation:

Correct ID + correct person + correct room + correct time + correct notification + daily reconciliation + secure data management = a healthy KBS operation

And there is an important point especially for small boutique hotels:

A hotel may be small; the importance of identity notification does not shrink.

In a six-room hotel and in a 300-room resort alike, the basic logic of the system is the same:

To know accurately who is staying at the facility and to report it in line with legislation.

Hotel Investment Guide — Volume III: Official Processes & Compliance

In this article I covered guest identity notification in hotels, from the investor's and operator's perspective, under the headings of:

• Identity Notification Law No. 1774,
• KBS,
• PMS,
• local and foreign guests,
• group arrivals,
• day use,
• check-in and check-out,
• system outages,
• daily reconciliation,
• the night audit,
• personal data security.

In Hotel Investment Guide — Volume III, I address guest records more comprehensively, together with licensing, operations, staff, data management, KVKK, and the continuous official compliance system.

The aim is not only to answer the question "How do you enter a guest into KBS?" but to show how an error-resistant identity notification system is built in a hotel.

Important Note: The legislation on identity notification, the technical operation of KBS, data fields, electronic connection methods, and law enforcement practices may change over time. Implementation details may also differ depending on whether the facility is in a police or gendarmerie jurisdiction. This article is for general information only. Before the hotel opens or KBS is implemented, the current process should be verified against Identity Notification Law No. 1774 and with the Police or Gendarmerie unit to which the facility is attached.