How to Settle Redeemed Courtesies With Partners Monthly

What does "settling" monthly courtesies actually mean?

Settling means closing the books with every partner who sent you customers: counting how many redemptions each one generated, figuring out the commission you owe, and leaving that payment on record. In a restaurant with several active partners (a tour guide, a content creator, an Airbnb host), doing this by hand in a spreadsheet is exactly where mistakes creep in: a redemption that never got logged, a commission calculated wrong, a payment that was already made but nobody marked it.

Vórax, Skyline's tool for venues, solves this differently: settlement with partners without spreadsheets, with a WhatsApp-ready statement and payment history.

This guide is for whoever runs a restaurant (or rooftop, or club) that already has courtesies published and partners recommending them, and needs a clear monthly process to pay them without headaches.

Why does a manual spreadsheet close fail?

The problem isn't the spreadsheet itself. It's that the data is born in three different places (the redemption at the venue, who originated it, how much is owed) and someone has to stitch them together by hand, month after month.

• The redemption gets logged in a notebook or at the register, not in the same sheet where the partner is tracked.
• Nobody writes down in the moment who brought the customer, so later someone has to guess or ask around.
• The commission gets calculated differently each time because the month changes or whoever is doing the math changes.
• The payment history lives somewhere else, in screenshots, in random transfers.

With Vórax this changes because the platform captures the data at the only moment it actually exists: when the traveler redeems the courtesy.

How does each redemption get recorded from the start?

Before thinking about the monthly close, it helps to understand that every courtesy you publish carries the origin of whoever brought it in. This is what Vórax calls attribution: each referral shows who sent it, with a partner ranking by people served and spending.

This means you don't have to reconstruct anything at the end of the month. The data is already there, redemption by redemption, from day one.

Example: a restaurant in Poblado

Picture a restaurant with three active courtesies: a welcome drink, a complimentary dessert and a discount on the bill. A tour guide recommends the drink to travelers on their route, a local creator shows off the dessert in their posts, and an ambassador with their own page shares the discount. Every time someone redeems, the system already knows which courtesy it was, which partner originated it, and how much that person spent.

How do you prepare the monthly close step by step?

Step 1: Review the partner ranking for the month

Go into the panel and look at the partner ranking, sorted by people brought in and verified spending. Without building anything manually, you see who brought the most customers that month and how much they spent.

Step 2: Confirm the invoice-verified spending

After each redemption, the venue records people served and invoice-verified spending, and sees the benefit per courtesy. This is what lets you calculate commissions on real numbers, not estimates.

Step 3: Let the system build the statement

This is where what used to take hours in a spreadsheet gets resolved: settlement with partners without spreadsheets generates a WhatsApp-ready statement, with the redemption detail and the amount owed per partner.

Step 4: Send the statement and pay

You send the statement to the partner via WhatsApp directly from the flow Vórax gives you. The partner sees exactly how many redemptions they generated and how much they're owed.

Step 5: Log the payment in the history

Every payment gets saved in the payment history. The next time you settle, you don't need to remember what was already paid: the system already has it.

What happens if a partner claims a redemption they don't see reflected?

Because attribution is stored redemption by redemption (who originated it, when, with which courtesy), you can review the detail with the partner without relying on anyone's memory. This avoids the typical "I brought more people than I'm being paid for" arguments that are common when the record lives in a notebook or in scattered WhatsApp messages.

What does this look like in a real case?

A restaurant in Provenza (Medellín) published a courtesy and, in one month, got 32 customers from 9 redemptions thanks to the partner network that recommended it. That's the kind of result you need to be able to settle without friction: there's no point generating new traffic through partners if the account close afterward turns into an administrative bottleneck.

How does this compare with running accounts on a spreadsheet?

What do you need to have ready before your first close with Vórax?

• Your courtesies published, with the commission you set for each one.
• Active partners recommending (guides, creators, ambassadors, Airbnb hosts).
• The habit of scanning the QR at every redemption, so the record is complete starting at the counter.
• A fixed day each month to review the ranking and send statements, so the process becomes routine instead of a last-minute scramble.

What if you don't have partners recommending your venue yet?

The monthly close only makes sense once partners are already bringing in customers. If your restaurant doesn't have courtesies published yet, the first step is deciding what you'll offer (a drink, a dessert, a discount) and what commission you're willing to pay per referred customer. From there, the partner network and local creators can start recommending you, and the system builds the rest of the settlement process on its own.

What to do now

If your restaurant already has active courtesies and partners recommending them, go to your Vórax panel and review this month's ranking before building the next statement by hand.