Improve Fee and Tax classification and reconciliation in the Orders API
Currently, custom Fees and Taxes configured at the property level can be retrieved through the Fees endpoint. However, their type is returned as CUSTOM, which does not clearly distinguish between a fee and a tax.
Although the Orders API returns these items under fees.otherFees, using the fee UID to retrieve their configuration does not guarantee that partners can reliably classify every line item as a Fee or Tax.
Additionally, taxes collected directly by Airbnb can appear in the Order response without a UID, only providing the name. This makes it difficult for partners to identify and classify these amounts reliably.
Furthermore, totalTaxesAmount is currently calculated based on tax amounts on rent and taxation amounts on custom fees / taxes. If neither rent nor fees has a calculated tax amount, totalTaxesAmount remains zero, even when tax-related line items exist in fees.otherFees.
Requested improvement
Provide a clear and consistent classification to distinguish Fees from Taxes, including custom configurations.
Provide an identifier or classification for channel-collected taxes, even when no Hostfully fee UID exists.
Standardize how totalTaxesAmount is calculated so partners can reliably reconcile tax amounts against the individual line items in the Order response.
Phung Dang
shared this idea