Skip to main content
Airbnb collects and remits some taxes on behalf of hosts in many jurisdictions. When that happens, your PMS may or may not record those taxes on the booking - and if you do not tell PX about it, audits will flag them as MISSING_TAX findings. The Airbnb Tax Remittance card sits at the top of the Tax Configuration page, subtitled Tell us how Airbnb handles taxes for your properties. It asks up to three questions, each revealed once you answer the one above it.
The setting is stored in PX only. PX does not push it back to your PMS or to Airbnb. It exists purely to inform PX’s audit logic.
Airbnb remittance card

Airbnb Tax Remittance, configured as Yes / same for all / all guest taxes

The card expands automatically while nothing is saved, and collapses to a one-line summary afterwards. Before you configure it the summary reads Not configured yet; once saved it reports what you chose, for example Airbnb remits taxes for 12 properties across 3 groups.

Does Airbnb collect and remit any taxes for you?

  • Yes - Airbnb handles some or all tax payments. Answering Yes reveals the next question.
  • No - I pay all taxes myself. Audits then expect every tax on every Airbnb booking, and there is nothing else to configure.
If Airbnb remits at least one tax on at least one of your listings, answer Yes.

Does Airbnb handle tax remittance the same way for all your properties?

  • Yes, same for all - I’ll choose which taxes once, applies to every property.
  • No, it differs by property - I’ll set up groups of properties with different tax remittance.
Choose No when remittance is jurisdiction-specific. For example, Airbnb remits Texas state hotel tax on your Texas listings but not on your California listings.

Which taxes does Airbnb remit?

This question only appears on the same for all path:
  • All guest taxes - Every tax charged to guests. Audits skip every tax check on Airbnb bookings.
  • Only specific taxes - I’ll choose which ones. Opens a checklist of every tax PX has on file, so you can tick the ones Airbnb remits.
The quick path is three clicks: Yes, then Yes, same for all, then All guest taxes, then Save.

Property groups

On the differs by property path, the card switches to Set up your property groups. Click Add a property group (then Add another property group) to build as many as you need. Each group holds a set of properties and its own tax choice: A property belongs to at most one group. The property picker greys out anything already assigned and tells you how many, for example 3 already in other groups, so you cannot double-assign by accident.
Properties you never assign to a group are not covered. The card warns you with <n> properties not covered and explains that Airbnb will not remit taxes for them. Add them to a group, or create a new one, before saving.

Custom taxes

Airbnb sometimes remits a tax that does not exist as a separate line in your PMS catalog. Inside the Only specific taxes checklist, Add a custom tax records those with a name and a rate. Custom taxes appear in their own Custom taxes section of the checklist, where you can edit or delete them. They are stored only on the remittance record and do not appear in your account-level taxes. They exist purely so PX knows to expect them on Airbnb bookings and does not flag an UNEXPECTED_TAX.

Saving

The footer shows Not saved yet until the first save, then Last saved with the date and time.
  • Save - stays disabled until the configuration is valid.
  • Discard - appears only while you have unsaved changes, and returns the card to the last saved state.
  • Reset to default - clears the configuration back to unconfigured.
If something is incomplete, a hint appears above the buttons instead of a silent failure. The two you are most likely to see:
  • No properties selected yet - add at least one property to a group before saving.
  • <n> empty groups will be removed on save.

How an audit applies remittance

For each Airbnb booking:
  1. Is there a remittance record for this account? If not, audit normally.
  2. Does this booking’s listing fall under the remittance scope (all properties, or a group it belongs to)?
  3. For each tax PX would normally check, is that tax in the remitted list? If yes, skip the check on this booking.
  4. Treat each custom tax as expected on the booking, so PX no longer flags an UNEXPECTED_TAX for it.

Common setups

Single jurisdiction, full remittance. Yes / Yes, same for all / All guest taxes. The simplest setup, and the one most single-market operators want. Multi-state operator. Yes / No, it differs by property / one group per state, each with its own tax selection. Hybrid. Yes / Yes, same for all / Only specific taxes. Airbnb remits state lodging tax everywhere, but city-level taxes remain your responsibility.

When to update it

Update the card whenever:
  • A new state or county is added where Airbnb remits.
  • Airbnb changes its remittance behavior. This happens occasionally, so watch for sudden spikes in MISSING_TAX findings on Airbnb bookings.
  • You add a listing in a new jurisdiction.
  • A tax that used to be remitted becomes your responsibility, or the reverse.
There is no re-run requirement. The next audit picks up the new configuration automatically.

Validation rules

  • Each property can appear in at most one group.
  • Custom taxes need both a name and a rate. Empty values are rejected.
  • Empty groups are dropped when you save.
  • There is one Airbnb remittance record per account, so saving always replaces the previous configuration.