A rejected TM30 submission usually appears at the worst possible moment: a guest has just arrived, the reporting window is moving, and the immigration portal gives little useful explanation. The question, why do submissions get rejected, rarely has one answer. Sometimes the information does not match the passport. Sometimes the accommodation record is incomplete. And sometimes the official system is simply unavailable or fails to process a valid request.
The practical goal is not to guess at the error screen. It is to identify whether the problem is guest data, property data, account status, timing, or the government portal itself. Once you separate those possibilities, most TM30 issues become much quicker to resolve.
Why Do TM30 Submissions Get Rejected?
A TM30 report connects two records: the foreign guest’s identity and the address where they are staying. Thai Immigration needs both sides to be consistent. If a required field is missing, formatted differently than expected, or conflicts with information already in the system, the submission may be rejected or remain unprocessed.
For hosts handling occasional stays, a single typo can be the whole problem. For hotels, apartments, and property managers handling a higher volume of arrivals, the bigger risk is inconsistent workflow. One staff member may enter an abbreviated address, another may use a different arrival date, and a third may submit a report that was already filed.
A rejection message can also be misleading. An official portal timeout, login failure, or stalled page does not necessarily mean Immigration has rejected the report. It may mean the request never reached the system, or that the response was interrupted before a confirmation was displayed. That distinction matters. Repeatedly resubmitting without checking can create duplicate-reporting problems.
Incorrect Passport Details
Passport data is the most common place to start. The name, passport number, nationality, date of birth, visa or entry details where required, and arrival information must be entered exactly as the system expects.
Small variations can matter. A passport number with a mistaken letter or digit will not match the guest record. A first name and middle name entered in the wrong field may cause a mismatch. Dates can also cause trouble when someone uses a different format or confuses the date of arrival in Thailand with the date the guest arrived at the accommodation.
Passport scans create another avoidable issue. A blurred image, glare over the passport number, a cropped machine-readable zone, or handwriting over key fields can lead to incorrect extraction or require manual review. Before submitting, make sure the image is clear, complete, and current. A clean photo taken in good light is usually enough.
Names deserve extra care. Use the spelling printed in the passport rather than a preferred spelling, nickname, or name order used on a booking platform. If the passport contains multiple given names, do not decide that one is optional unless the form’s field rules clearly require it.
Address and Accommodation Record Problems
The property must be correctly registered before the guest report can be accepted. This is where independent landlords and foreign residents responsible for a home can run into trouble. You may have the right guest details but still be unable to report if the property, house number, unit, or responsible party details are not aligned with the Immigration account.
Use the address format associated with the registered accommodation record. Do not assume that an informal condo name, building nickname, or shortened street address will be recognized. Unit numbers, village numbers, subdistricts, districts, and provinces can be especially easy to mix up.
There is a trade-off here. Entering more detail is not always better if it differs from the registered record. Accuracy and consistency matter more than trying to make the address sound complete. When a property has changed ownership, management, address registration, or account holder, confirm the underlying accommodation setup before reporting new arrivals.
Hotels and larger operators should establish one approved address reference for each property and unit. That gives staff a reliable source rather than asking every person to type the address from memory.
Arrival Dates, Departure Dates, and Timing
TM30 reporting is time-sensitive. In most cases, the responsible host or accommodation provider must report a foreign guest’s stay within 24 hours of arrival at the property. Waiting until the next business day, collecting details later, or assuming a weekend changes the requirement can put a report at risk.
The date itself must also reflect the event being reported. A guest may have entered Thailand days or weeks earlier and then moved to your hotel, apartment, or house today. For the TM30 report, what matters is the guest’s arrival at your accommodation, not necessarily their international arrival date.
Check the situation carefully when a guest returns after traveling, changes rooms, extends a stay, or moves between properties under the same operator. The reporting obligation can depend on the specific movement and current accommodation. If the circumstances are unusual, do not rely on what happened with a previous guest or a previous trip. Confirm the appropriate reporting treatment with the relevant immigration office.
Duplicate or Already-Submitted Reports
Not every failed attempt means the report is missing. If a staff member, owner, agent, or prior accommodation manager has already submitted a report for the same guest and stay, a new attempt may be flagged as a duplicate.
This happens often when multiple people have access to the same account or when a guest sends their passport to more than one contact. It also happens after a slow portal session. Someone sees no confirmation, submits again, and then learns the first request was recorded after all.
Before making another submission, check your dashboard, receipt history, and any available confirmation record. Keep a simple internal process: one person submits, one shared record shows the status, and everyone knows where the confirmation is stored. For a small landlord, that can be a folder and a spreadsheet. For a busy property, it should be part of the check-in workflow.
Account Access and Official Portal Failures
The Thai Immigration system can be slow, unavailable, or difficult to use during high-demand periods. Login problems, session expirations, loading errors, and failed responses are operational issues, not necessarily compliance failures on your side.
Still, the host remains responsible for reporting correctly and on time. Take screenshots of error messages and record the time of your attempts. This helps your team troubleshoot and creates a useful record if the portal is unavailable. Avoid relying on a browser tab that has been open for hours, especially if multiple staff members use the same credentials.
A managed submission workflow can reduce this friction by checking the data before sending it, tracking the request, and retrying when the official system does not respond. TM30.io is designed for exactly this practical problem: turn a passport image into a completed submission and retain confirmation once it is accepted.
A Fast Check Before You Submit
A short review can prevent most avoidable rejections. Confirm that the passport image is readable, the name and passport number match exactly, and the guest’s arrival date at your property is correct. Then verify that the accommodation address matches the registered record and that nobody else has already filed the same report.
For recurring operations, build these checks into check-in rather than treating TM30 as an end-of-day task. Ask for the passport at arrival, capture a clear image immediately, and submit while the guest details and arrival time are fresh. This reduces last-minute data entry and gives you time to resolve a portal problem before the reporting window closes.
When a Rejection Needs More Than a Retry
Retrying makes sense when the official portal has clearly timed out or returned a technical error. It is not the right answer when the same submission repeatedly fails. Repeated failure usually points to a data mismatch, an account configuration issue, or a reporting scenario that needs clarification.
Review the exact fields first. If they appear correct, compare the property details with the official account record. If the issue involves a changed owner, an unregistered unit, an unusual travel pattern, or unclear reporting responsibility, contact the relevant Immigration office for guidance rather than submitting guesses.
The most reliable TM30 process is simple: capture accurate details at check-in, use the registered property record, submit promptly, and keep the confirmation. That leaves you with less time spent fighting a government portal and more confidence that each guest report is properly handled.