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.

PX Accounting connects to one PMS at a time. The connection lives on the Settings page under PMS Connection. Pick yours below.

Connect Guesty

OAuth with Client ID and Client Secret.

Connect OwnerRez

One-click OAuth.

Connect Hospitable

Personal Access Token.

Connect Uplisting

API key from Uplisting settings.

Connect Hostaway

Account ID and Secret Key.

Connect Hostfully

Agency-level API key.

Connect Lodgify

API key from Lodgify settings.

What gets synced

The first time you connect, PX pulls:
  • Properties - one record per listing, including name, address, thumbnail, capacity, and active/inactive flag.
  • Owners (when present in the PMS) - mapped to properties so you can see the owner inline on each property.
Reservations and financial data are fetched on demand when you open a property’s Reservations tab or run an audit. PX caches selectively to keep audits fast and stay under PMS rate limits.

Webhooks

PX registers webhooks with your PMS at connection time so changes (new bookings, cancellations, listing updates) flow in without waiting for a sync. You can verify webhook health on the Integration Status panel under Settings.

What PX is not

PX does not keep its own ledger or bookkeeping system. It reads your PMS data and audits it against your business model and tax configuration. Where your PMS exposes journal entries (some do, some do not), PX uses them. Where it does not, PX works from per-charge data to compute what the postings should look like for audit purposes only.

Switching PMSes

PX supports one active PMS per account. Switching providers requires deleting the existing credentials from Settings before connecting a new one. Historical data tied to the old PMS stays in place; new syncs populate against the new provider.

Rate limits

PX respects PMS rate limits. If you hit one (most common when running large audits), the UI shows a 429 banner with a countdown - the affected button stays disabled until the cooldown finishes.