A full building, several condos, or a portfolio of villas can turn TM30 compliance into a daily administrative problem fast. This multi property reporting guide shows property owners and accommodation operators how to organize reports across locations without losing track of deadlines, guest records, or submission receipts.
The core requirement is straightforward: the person responsible for providing accommodation must report a foreign national’s stay to Thai Immigration within the required timeframe, commonly understood as 24 hours after arrival. The operational reality is less simple. Guests arrive late, reservations change, passport photos are unclear, and the government portal may be slow or unavailable just when reports need to be filed.
For a single home, a manual process may be manageable. Across multiple properties, it needs to become a system.
What makes multi-property TM30 reporting difficult
The challenge is not simply the number of guests. It is the number of moving parts: different addresses, different staff members, separate property registrations, check-ins at different times, and records that need to be available later if a guest or immigration officer asks for proof.
A manager who relies on inbox searches, paper passports, and memory will eventually miss something. That does not mean the team is careless. It means the workflow has no reliable control point.
Multi-property reporting also creates an ownership question. Who is responsible for filing at each location? It may be the legal owner, a registered hotel operator, a building manager, or a person appointed to manage the accommodation. Define this clearly for every property before a guest checks in. If responsibility is vague, reports tend to wait until someone has time, which is exactly how deadlines are missed.
Local processes and immigration office requirements can vary. Keep your property registration details and reporting authority records current, and confirm the process that applies to your type of accommodation and area. A good operating system supports compliance, but it does not replace checking your obligations when circumstances change.
Build one reporting workflow for every property
The most effective approach is to standardize the guest journey from booking to confirmation. Each property can have different room types, staff, and check-in methods, but the reporting steps should remain consistent.
Start by assigning every location a clear property name and address format. Avoid informal labels such as “Sukhumvit unit” or “beach house 2” if multiple people use the records. Use the same name in reservation systems, internal trackers, and TM30 reporting records. A small naming inconsistency can lead to a report being filed under the wrong address.
Next, collect the same guest information at every property. This normally includes the passport image or scan and the stay details needed for the report. Passport data should be reviewed before submission, especially the guest’s full name, nationality, passport number, arrival information, and dates. Automation can reduce data entry, but a blurry image or an incorrect check-in date still creates a bad filing.
Then create a deadline trigger. The trigger should begin when the foreign guest physically arrives at the property, not when they made the reservation or completed an online booking. For late-night arrivals, make sure the team knows whether the report is queued immediately, handled by an overnight process, or reviewed first thing in the morning within the reporting window.
Finally, store the submission confirmation in one place. Receipts should be easy to find by guest name, passport number, property, and arrival date. If your records only show that “someone submitted it,” you may have difficulty resolving a later question.
A practical property-level checklist
For each new foreign guest, your internal process should confirm four things:
The correct accommodation address and responsible property are selected.The passport image is readable and the extracted details match the document.The arrival date and stay information are entered correctly.A submission receipt or confirmation is saved after the report is completed.
This is not paperwork for its own sake. It gives staff a repeatable final check before an error becomes a compliance issue.
Centralize visibility, not just data entry
Many operators make the mistake of giving each site its own reporting method. One building uses a spreadsheet, another sends passport photos through chat, and a third logs into the official portal manually. That may work temporarily, but it prevents a manager from seeing what is pending across the business.
A centralized dashboard or tracker should show every property, each foreign guest arrival, the filing status, and the confirmation record. The goal is not to monitor staff excessively. It is to make exceptions visible early.
For example, a manager should be able to spot that five guests arrived at one apartment building but only four reports have confirmations. That difference might be a duplicate booking, a canceled stay, or an unsubmitted TM30. Without a central view, it can remain unnoticed.
The level of detail depends on the size of your operation. A landlord with three units may only need a simple shared process and a secure receipt folder. A hotel or large serviced-apartment operator may need role-based access, daily exception reports, and a formal handover between front desk and compliance staff. The principle stays the same: one source of truth, with every filing tied to the correct property.
Plan for exceptions before they happen
The normal check-in is not where most reporting failures occur. Problems arise when the guest extends a stay, changes rooms or properties, returns after travel, arrives without a readable passport image, or checks in while the reporting system is unavailable.
Create an exception process that staff can follow without waiting for a manager. It should answer three questions: what information is missing, who must resolve it, and when must the report be submitted once the issue is fixed.
System downtime deserves special attention. Government portals can be slow or unresponsive, and refreshing a page repeatedly is not a reliable business process. Keep a record of attempted submissions and use a reporting method that can retry when the immigration system becomes available. The point is not to create more work for staff. It is to avoid a missed filing because a website failed at the wrong moment.
TM30.io can help here by extracting required information from a passport photo or scan, preparing the report, submitting it through the Thai Immigration system, and retaining confirmation records. For multi-property operators, the practical value is consistency: staff can use a mobile-friendly workflow while management retains visibility over completed reports.
Set staff roles that match your operation
A good process separates collection, review, and oversight without making every report slow. Front desk staff or hosts can collect passport details at check-in. A designated compliance owner can review exceptions and incomplete records. Management can monitor overdue or failed submissions rather than manually handling every guest.
Do not assume everyone understands TM30 requirements because they work in hospitality. Include the process in onboarding, especially for weekend staff, temporary reception teams, and co-hosts. Give them plain instructions for foreign arrivals, document quality, property selection, and what to do if a guest refuses or delays providing a passport image.
It also helps to set a daily cut-off review. At a fixed time, check all foreign arrivals across properties against submitted confirmations. This catches gaps while they are still easy to correct. For properties with frequent arrivals, run the review more than once a day.
Keep records useful and secure
Passport information and immigration receipts are sensitive operational records. Limit access to people who need it, avoid scattering files across personal devices, and use a consistent retention policy based on your legal and business requirements. Convenience should not mean leaving guest documents in an unprotected chat thread.
Your records should also be usable under pressure. If a guest needs proof of reporting for an immigration-related task, or if your team needs to verify a prior filing, searching should take minutes, not an afternoon. Organizing files by property and arrival date is helpful, but searchable guest and receipt records are better.
A portfolio grows more manageable when compliance stops depending on one person’s memory. Set the workflow once, train the people who use it, and give every property the same clear path from check-in to confirmed TM30 receipt.