Tracking AirBNB Resolution submittals on a booking in OR?

Is there a way to best track an AirBNB resolution request and related payout on a specific booking?  I tried to convert a booking to 'manual charges' but once the payout came through there was duplicate charge now showing on the booking.    Looking for recommendations or how others may be managing this process for items like early check-in fees or pet fees as an example that occur AFTER the booking has been created.  Thanks in advance!

Hi,

In the past running Channel bridge would be our first recommendation, but as of the week we have a new transaction sync option you can opt into if you'd like. This should automatically handle importing those fees and preventing and sort of discrepancies between OwnerRez and Airbnb.

We made a post recently about this sync option here:

https://www.ownerrez.com/blog/airbnb-transaction-sync-api-integrated-third-party-websites-dismissed-alerts-hosted-website-options#sync

~Caleb

How does the new API handled the PM lock?  As an example,  we do receive resolution payouts for previous bookings that were already paid to the owner.   PS:  I have enabled the new sync today!

A PM lock should prevent any and all changes to the financials of a given booking. This is no exception with channel bridge or the API transaction sync.

A PM lock should prevent any and all changes to the financials of a given booking. This is no exception with channel bridge or the API transaction sync.

Hm. Not sure I like that. That should probably be looked at and thought through again by the OR team, because it has the potential to get things out of balance. (At least in the past, with Channel Bridge, we were notified when a booking had a PM lock, so that we could go through and manually update it or unlock it and re-run Channel Bridge for just that booking.)

With Transaction Sync, you will receive an email alert if a deposit is unable to update a booking due to PM lock. You then unlock the booking, retry the deposit, and finally relock the booking. 

We decided it was better to notify you and give you the tools to fix the problem, rather than magically circumvent the restrictions everyone has come to know and rely upon. 🙂