RippleThe question that costs a hotel the most time is not "what did they pay". It is "what did they pay for".
When the money lives with the payment provider and the booking lives in the PMS, matching them is a monthly job somebody does by eye — and every unmatched line is either a guest who was charged twice or revenue nobody recognised. Ripple records the transaction against the folio at the moment it happens, so the match is not a task.
A history, not a running total that gets edited.
Financial activity on a folio is recorded as an append-only history rather than edited in place. A correction is a new entry that says what it corrects, so the folio can be read as a sequence of things that happened — which is what makes a disputed bill answerable rather than arguable.
- Charges, payments, adjustments and refunds recorded in sequence
- A correction appears as an entry rather than replacing what it corrects
- Every entry attached to the stay it belongs to
Where this shows up.
Three moments where a folio being one record changes the outcome.
- Check-out is one screen
- What is owed and what has been paid are visible at the counter, and the payment is taken there against the same folio.
- A disputed charge has an answer
- Because entries are added rather than overwritten, the sequence of what was charged, when, and what was later adjusted is still readable.
- Deposits are not chased
- A deposit taken at the point of booking is already on the folio when the guest arrives, rather than reconciled from a provider report.