New Cloudbeds Accounting System and getTransactions changes

• Related Changelog notification can be found here:
• Cloudbeds API and Accounting API Differences and examples are included in the following subpages.
• Related FAQs can be found below.

URGENT: On Feb 1 we are releasing the new accounting service, this includes changes to getTransactions endpoint which may affect your integration.

On Feb 1 we are releasing the new accounting service, which includes changes to getTransactions endpoint. The getTransactions endpoint will continue to provide transactional data for properties, but will be enriched. The totals of the transactions still sum to the right amount, though calculations made at an individual transaction level may be affected. Please see the FAQ and Examples below for additional information.

Examples

• Example 1: Update Room Price and Routed Transactions
• Example 2: Void Transactions
• Example 3: Delete a Reservation
• Example 4: Update Accommodation Type
• Example 5: Void Adjustments

FAQs

Question: How will the data be changed in getTransactions after a property is using the Cloudbeds New Accounting System?
Answer: Because the Cloudbeds Accounting System is immutable, there are times when more transactions will be created for a given event than had been previously. Examples of those can be found in the Examples

Question: How will I know if a customer is using the new accounting system for their transactional data?
Answer: There will be a new attribute included in the getTransactions response when a location is using the new accounting system for transactional data. (attribute TBD)