> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Create Approval Flows for Guest Refunds
- URL: https://blog.jestor.com/approval-flows-guest-refunds/
- Published: 2026-09-15T20:27:01.000Z
- Updated: 2026-09-15T20:27:01.000Z
- Author: Bruno Bannach

Creating approval flows for guest refunds means a refund request routes automatically based on its value and reason, with a documented decision trail — instead of being approved verbally or inconsistently depending on who's handling the guest at the time. In **Jestor**, this uses standard **Approvals** structure applied to refund requests.

Refund requests carry real financial and reputational stakes in short-stay operations — inconsistent handling here directly affects both margins and guest trust.

## What inconsistent refund handling costs

- Different staff approving similar refund requests differently
- No documented reason or decision trail for why a refund was granted or denied
- No value threshold determining when a manager needs to get involved
- Refunds processed without connecting back to the original booking's terms

## How structured refund approval works

- Refund requests connect directly to the original booking and its terms
- **Alçada** rules route based on refund value or reason, escalating as needed
- The decision and its rationale stay permanently attached to the guest's record
- Approved refunds can connect to the relevant financial posting

## Why Jestor fits this use case

- Refund decisions become consistent, since alçada rules apply the same way every time
- Every decision stays documented, useful for both quality review and disputes
- Value-based routing means small refunds move fast, larger ones get appropriate scrutiny
- The refund history connects to the guest's broader record for future reference

| Refund value             | Approval routing             |
| ------------------------ | ---------------------------- |
| Small, routine           | Fast, single-approver path   |
| Larger or unusual reason | Escalated for manager review |

## Frequently Asked Questions

**Is every refund decision documented automatically?** Yes, the decision and rationale stay attached to the record. More at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

**Can refund thresholds vary by reason, not just value?** Yes, alçada rules can combine multiple criteria.

**Does the approved refund process the actual payment?** No, Jestor structures the approval; payment execution stays with the ERP or payment provider.

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.