Follow guest charges, payments and balances clearly.

Review the folio alongside the stay

A guest folio brings together charges and their financial records. Staff can review the stay's accepted amounts and the balance still requiring action rather than treating a reservation status as a payment status.

Use a private-room stay and a dorm-bed stay in the demonstration. Check which charges belong to the guest, what was accepted and whether the relevant issued record retains its source information when later work changes. A hotel POS charge added to a folio is still a charge, not proof of receipt.

Keep payment evidence separate from confirmation

A booking confirmation, a guest's browser return or a POS folio posting does not establish that money arrived. The current local workflows distinguish evidenced payment records from pending or unknown external outcomes.

For a manually recorded external payment, confirm the reference and the staff member's evidence. For a gateway-based flow, the relevant merchant access, authenticated provider evidence and live acceptance must be established separately. No real gateway collection is enabled by the marketing website.

Use a small synthetic balance example

Consider an illustrative folio with a posted charge of ₹2,000 and an evidenced payment of ₹500. Assuming no other charges, refunds or adjustments, the remaining balance is ₹1,500. These amounts are a demonstration example, not a room rate, product price or approved tax calculation.

Ask the operator to locate the source charge, payment record and remaining balance. Then show a payment attempt with no verified outcome and check that it is not silently counted as received. Record observed behaviour and unresolved dependencies; this exercise is not a claim that a new test passed.

Keep corrections and issued documents understandable

The local implementation includes invoices, credit notes, evidenced refunds and retained issued-document information. A correction should be reviewed through the permitted process with the original financial evidence still understandable.

Walk through a cancellation or adjustment using synthetic records. Review what remains payable, what is eligible for refund, who may approve the action and which document records it. Do not equate a requested refund with a completed external refund or a credit note with money returned to the guest.

Approve tax, numbering and close for the property

The software's configurable tax snapshots and document workflows do not decide the property's applicable treatment. Have the authorized property adviser review sample charges, tax examples, invoice details, numbering and correction policy before activation.

Include business-date close and the resulting records in the walkthrough. Reconcile the guest balances and unresolved payment outcomes against their evidence. This page makes no GST-compliance, statutory-filing, accounting-certification or recovery-time guarantee.

• Identify who may post charges, record payments and approve corrections.
• Confirm the property's actual invoice and tax examples before live use.
• Distinguish deposits, guest balances, refund requests and completed refunds.
• Review external-service dependencies and an incident contact before rollout.

Prepare an AU-PMS billing walkthrough

Bring fictional examples of a deposit, part payment, room or bed charge, ancillary sale, cancellation and refund. Use the local demonstration to check the workflow and identify policy or access that still needs confirmation. Please do not send real guest records, payment credentials or bank details in an initial enquiry.

Live payment processing, OTA and email connections require the relevant authorization, configuration and acceptance. Current product scope and pricing should be agreed in writing; no fixed plan or measured financial saving is asserted here.

Questions to work through.