Hi Nisha,
Thank you for finally identifying the four reservations behind the credit memos. After reviewing Expedia's own records — both the Partner Central system and the email correspondence I have from Expedia's support teams — I am formally disputing all four memos in full and asking you to void them. The evidence below is drawn entirely from Expedia's own documentation.
The four memos you listed on Apr 13 total 208,992.79 THB, not ~186,000:
| Reservation | Guest | Memo amount (THB) |
|---|---|---|
| 2349105939 | Fabienne Menzen | 72,112.78 |
| 2356705173 | Liviu Craciun | 79,280.09 |
| 2293553587 | Selin Kalyoncu | 22,527.96 |
| 2357240861 | Jacqueline Lindgren | 35,071.96 |
| Total | 208,992.79 |
| Reservation | Guest | Status in Partner Central | Amount paid to me | Memo charged to me |
|---|---|---|---|---|
| 2349105939 | Fabienne Menzen | Canceled Dec 11, 2025 | THB 0.00 | 72,112.78 |
| 2356705173 | Liviu Craciun | Canceled Dec 24, 2025 | THB 0.00 | 79,280.09 |
| 2357240861 | Jacqueline Lindgren | Canceled Dec 27, 2025 | THB 0.00 | 35,071.96 |
| 2293553587 | Selin Kalyoncu | Checked out | THB 65,139.73 | 22,527.96 |
Please explain how "relocation costs" can be valid for three reservations that Expedia's own system records as Canceled and for which Expedia never paid Baan Tropicana a single THB.
Note also: reservation 2293553587 shows a sidebar ID of #2360150211 in Partner Central but appears in your email as 2293553587. Please clarify this discrepancy.
The following messages were sent by me through Partner Central's messaging center and are timestamped in Expedia's own system:
Every one of these messages predates the guest's arrival and used the exact channel Expedia provides for partner-guest coordination.
The following points are drawn from emails sent by Expedia, which I have on file:
Expedia's reservation services team (signed "Frank S., Reservation Support Services") wrote to guest Liviu Craciun on Dec 25, 2025 at 12:17 PM, informing him the property could not honor his Dec 27 booking. Expedia's own email offered to relocate him at no additional cost to him. Expedia's choice of words — "Temporary Closure" — acknowledges the closure was known to Expedia.
Expedia sent me a "Cost Involved for Expedia Relocation" email on Dec 25 at 1:13 PM, naming Liviu Craciun and citing the reason as "Temporary Closure." But my Partner Central message notifying Expedia that the villas were full had already been sent on Dec 24 at 7:09 PM — more than 17 hours before Expedia's own relocation email.
Expedia had the notification. Expedia proceeded with relocation anyway. I am now being charged for a cost Expedia chose to incur after I notified them.
On Dec 26, 2025, 9:39 AM, Mickole Yesid of the Expedia Group lodging support team opened case 147713339 regarding reservation 2357240861 (Jacqueline Lindgren). In that case email, Expedia wrote:
"We can also confirm the reservation since it is viewable in Expedia Partner Central and there is evidence of your communication with the guest through the Expedia Partner Central message center with this regards."
This is Expedia confirming in writing, on an official case, that my closure notice is documented in your own system. Expedia cannot now claim I failed to notify when Expedia's own support team already documented otherwise.
In your Apr 13, 2026 email, you wrote:
"A temporary closure was placed on this property, and as a result the above guests were relocated. The amounts listed above correspond to the relocation costs. Since no relocation invoices have been issued, these amounts have instead been reflected as credit memos, which is why they have been applied."
This is Expedia's own admission that the 208,992.79 THB is not backed by actual invoices from replacement properties. On what basis were the amounts calculated? Which specific alternative properties did Expedia book the guests into, on which dates, at which rates, and at what actual invoiced cost? Absent that documentation, these are unsubstantiated charges, not documented relocation costs.
Please provide, for each of the four reservations:
If no such documentation exists, the credit memos cannot stand.
Partner Central shows this reservation was Canceled on Dec 11, 2025 for a stay of Dec 28 – Jan 8. My earliest closure-related notification to Expedia was Dec 24, 2025 (Craciun thread) and my explicit closure statement ("we closed all our villas with Expedia") was Dec 26. A cancellation that occurred almost two weeks before any closure cannot have been caused by that closure. Please explain on what basis a 72,112.78 THB relocation cost was attributed to a cancellation that predates the event Expedia cites as its cause.
Partner Central shows this reservation as Checked out with THB 65,139.73 paid for a stay of Jan 5 – Jan 20, 2026. If the guest stayed at Baan Tropicana, there was no relocation — the guest did not go to a replacement property. On what basis is a 22,527.96 THB relocation cost charged for a guest who completed her stay at my property? Additionally, your email references ID 2293553587 but Partner Central shows sidebar ID #2360150211 for this guest; please confirm which reservation the memo actually attaches to.
My Partner Central message went out Dec 24, 7:09 PM. Expedia's "Cost Involved for Expedia Relocation" email to me went out Dec 25, 1:13 PM. Expedia had the notice and chose to proceed with a paid relocation anyway. 79,280.09 THB is not a cost I caused — it is a cost Expedia elected to incur after receiving my notification.
On Dec 26, 2025 at 22:14 (Thailand time) I confirmed in writing that Expedia had agreed to process a refund to the guest. I then formally consented in writing on Dec 26 and again Dec 31, 2025, that Jacqueline Lindgren was entitled to a refund in full for the whole period of her reservation. That consent applies to refunding the guest — returning the guest's own money. It does not constitute, and must not be interpreted as, consent for Expedia to charge Baan Tropicana 35,071.96 THB for an unrelated relocation transaction with a replacement property. Refund-to-guest and relocation-cost-billed-to-partner are two separate financial events; my consent extended only to the first.
My Partner Central message for reservation 2357240861, timestamped Fri Dec 26: "Please call me asap, I've tried to get through on Thai number. Every time I'm told there was a problem trying again."
Expedia's own Thailand support infrastructure failed at the critical moment I was escalating.
Across all four message threads on the disputed reservations, there is no communication from Expedia notifying me of a relocation, presenting a cost breakdown, or seeking my acknowledgment. Credit memos of 208,992.79 THB were created without a single notification through the very channel Expedia itself provides for partner-guest coordination — the same channel Mickole Yesid confirmed (section 3c) contains my closure notices.
During that four-month period, Expedia continued to block payments I was owed (Louis Bischof, 2298137210). The specifics were not withheld because they were unknown — they were withheld despite my repeated, documented requests across multiple cases.
I formally dispute all four credit memos referenced in your Apr 13, 2026 email — reservations 2349105939, 2356705173, 2293553587, 2357240861, totaling 208,992.79 THB — in full. The evidence above is drawn entirely from Expedia's own Partner Central records and Expedia's own email correspondence, including Mickole Yesid's Dec 26, 2025 case email 147713339, which explicitly confirms my closure notice is in Expedia's system.
I respectfully request a written response within 5 business days, along with direct contact details for my Market Manager. My mobile is available 24/7: +66 64 1600 381.
Thank you,
Jon Buckley
Baan Tropicana (11530693)