Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.pxaccounting.com/llms.txt

Use this file to discover all available pages before exploring further.

Tax configuration in PX has three independent layers. Knowing which layer to touch is the difference between a five-minute change and an afternoon of debugging.

The three layers

PMS mirror

Read-only view of taxes from your PMS. Change them in your PMS, not in PX.

Channel sync overrides

PX-only. Per-tax, per-channel toggles for which channels a tax syncs to. Stored in PX, not pushed to your PMS.

Airbnb tax remittance

PX-only. Tells PX which taxes Airbnb collects and remits, so audits exclude them. Stored in PX, not pushed to your PMS.
The two writable layers (channel sync overrides and Airbnb tax remittance) are stored inside PX only. PX never writes back to your PMS. If you need to change a rate or applicability rule, change it in your PMS.

Why three layers?

Real-world tax setups need all three:
  1. The rates and applicability - the lodging tax is 9.5%, applies to accommodation only, applies to stays under 30 nights. This lives in your PMS.
  2. Sync behavior per channel - the same tax may sync to your direct channel but not to Booking.com because Booking.com cannot pass through the rate. PX provides a channel override layer you maintain inside PX so audits know what to expect on each booking.
  3. Marketplace remittance - Airbnb collects and remits some taxes on your behalf in many jurisdictions. Audits should not flag those taxes as missing on Airbnb bookings.
PX combines all three to decide what to expect on a given booking.

How an audit uses tax configuration

For each reservation:
  1. Look up the property’s PMS taxes (account-level + listing-level overrides).
  2. For each tax, check channel sync overrides - does this tax sync to this booking’s channel?
  3. If the channel is Airbnb, check Airbnb remittance - does Airbnb remit this tax?
  4. If the tax is expected, compare the recorded amount on the booking to the calculated amount.
  5. Emit a finding when expected and actual diverge.
Each finding labels which layer drove the expectation.

Where to start

If you are just connecting your PMS:
  1. Open Tax Configuration.
  2. Refresh the PMS mirror so the latest rates are loaded.
  3. Confirm the taxes look right.
  4. Walk through the Airbnb tax remittance wizard if it is shown for your PMS.
  5. Add channel sync overrides for any tax that should not flow to a given channel.
The exact buttons, what gets refreshed, and whether the Airbnb remittance wizard appears all depend on which PMS is connected. See your PMS’s Connect page for the specifics. You can run audits without doing any of this, but you will see a lot of MISSING_TAX and UNEXPECTED_TAX findings until tax configuration matches reality.