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.

When you run an audit, PX inspects every reservation in scope and runs three classes of checks. The exact mix depends on your PMS - some checks rely on accounting data only certain PMSes expose - but every audit covers all three categories at a high level.

Class 1 - cross-system validation

When your PMS has a built-in accounting engine, PX cross-checks its postings against your business model. This catches discrepancies between what the PMS recorded and what your management agreement says should have happened. Class 1 is available where the PMS exposes a usable accounting feed. Where it is not, PX falls back to Class 2 and Class 3, which together cover the same ground using a different approach.

Class 2 - data consistency

PX validates that the numbers your PMS reports reconcile against themselves and against your tax and commission configuration. Examples of what this catches:
  • Taxes that should have been collected but were not.
  • Fees and commissions whose amounts do not match the configuration.
  • Bookings with payment anomalies (missing, duplicated, or unbalanced).
  • Bookings whose totals do not match the sum of their charges.
  • Calendar overlaps and bookings that look stale.
Class 2 runs on every PMS PX supports.

Class 3 - business model validation

PX takes the per-charge data your PMS provides and checks it against the business model you have assigned. This is where ledger balance and owner statement reconciliation findings come from. Class 3 only runs for properties that have an assigned, active business model. Class 3 covers questions like:
  • Does the owner payout we calculated match the payout the PMS recorded?
  • Are charges recognized on the dates the business model says they should be?
  • Does the commission rate applied match the rate in the model?

What does not get checked

PX is an accounting and trust audit tool. It does not check pricing decisions, channel performance, forecasting, marketing, or guest communication. Pricing and revenue management belong elsewhere.

Severity and verdicts

Every check produces a finding with a severity (error, warning, or info) and a contribution to the audit’s overall verdict (clean, underpaid, or overpaid). See Understanding findings for how to read individual findings.

In-product reference

The in-app audit results page shows the specific check name, expected amount, actual amount, and reasoning for every finding. That is the canonical reference for what a given finding means and how to triage it.